Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Aged write-off

Updated on January 18, 2022

Accounting supports the aging, automatic scheduling, and processing of open receivable (debit) and payable (credit) write-off suspense entries associated with work objects.

Service level rules define the schedule for aging open payable (credit) and receivable (debit) suspense entries in the system. Different aging schedules can be defined for receivables and payables in either business or calendar days. The accounting application ships with a sample configuration for these aging parameters.

When a flow opens a suspense entry, it references a rule to calculate the scheduled resolution date of the receivable or payable and begins the aging process. The scheduled resolution date for a case is calculated using the outstanding value at the time of creation and the aging service level rules.

Service level rules also define the schedule for the actual writing off the aged entries. When a suspense entry is opened, the entry is immediately assigned to the FinAging work queue where it ages until the entry is either closed or until the service level expires. If the service level expires, the application transfers the entry to the FinWriteOff work queue. To actually write off entries from the work queue, you call the FinBatchWriteoff activity.

Operators, with privileges, can reschedule suspense entries for an earlier write-off by transferring them directly to the FinWriteOff work queue during the research process. Conversely, you can postpone the write-off by selecting the entry from the FinWriteoff work queue and using the reschedule option to select a new service level for the entry and automatically transfer it back to the aging work queue.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us