Skip to main content

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

Accounting cutoff

Updated on January 18, 2022

The accounting component supports the use of warning and cutoff times for accounting transactions. This enables your organization to put a logical stop time to accounting and then run end-of-day accounting feeds and reconciliation and balance reports.

You can use multiple cutoff rules to configure different accounting extraction and feed schedules. You can activate cutoff in two modes:

  • Standard – Allows you to continue researching and processing cases but prevents accounting transactions from posting until a specified release time is reached. In most instances, work on the case can continue until a workflow or transaction point is reached where processing cannot advance until the transaction is posted. At installation, this is the default cutoff mode.
  • Future – Allows you to continue researching and processing cases and continue posting transactions after the day’s cutoff has been reached. When processing in this cutoff mode, debit and credit transactions in the step are posted to the accounting posting file with the next business day’s date as the posting date. This means that the accounting feed must be extracted by posting date, which is the date the transactions should post, not the posting timestamp, which is when the transaction was written to the accounting posting file. The online display shows both the date and time written to the posting file and the date specified for actual posting, so you know what was done between the cutoff and the next business day. This method also works well for weekend processing.
Note: Transactions held for cutoff are always held as balanced transactions. Debits and credits are not separated prior to posting.

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