Give each date a clear meaning
Operations may ask which day a settlement belongs to. Finance may ask what had been recorded by a particular cutoff. Those questions need different date bases. An agreed timeline lets both teams explain a changed balance without arguing over a field labelled only “date”.
The Ledger Rocket approach
Ledger Rocket supports processed-date balance history. Value-date history uses a separately configured value-date model. These views distinguish processing time from business-occurrence time. Use the selected balance view for historical comparisons, and agree reporting-close evidence separately with the finance team.
Work through these cases
- Fix a processing cutoff. Then introduce an event after that cutoff with an earlier business date. Compare the expected result on both configured date bases.
- Add a correction and follow its relationship to the original activity.
- Confirm the source cutoff and account population used in each view.
Discuss your flow
Prepare a timeline with an on-time event, a late event and a correction. Write the expected balance for each date basis before the walkthrough.
Book a demo