The ledger, as of any date
Ask for last March’s balance and most systems rebuild it backwards from today, inheriting every later fix. The stored answer stays what it was, and this page proves it with three month-ends payroll already published.
◆ One account, three month-endsthe accrual balance payroll already published.
| 2100 · Accrued payroll, as of | Balance |
|---|---|
| 31 March 2026 | 4,500,345.00 |
| 30 April 2026 | 4,551,330.00 |
| 31 May 2026 | 4,663,142.08 |
Three dates, three balances, and every one is a number this catalog already proves: they are the monthly labor totals the payroll module publishes, seen from the ledger’s side. An as-of answer that ties to another module’s history is the whole point of storing rather than rebuilding. Sample values are illustrative, never client data.
◆ Why stored beats rebuiltthe same argument, every platform.
Rebuilding a past balance from today minus activity inherits every later correction and reclass, which is how two runs of the same question disagree. This catalog documents the identical failure on SAP open items and Oracle stock; the as-of hub collects the family, and the ledger joins it here.
◆ The owned answerfct_ledger_balance, daily, derived and kept.
The GL star’s balance fact is derived from lines and stored per day, so as-of is a filter, audits read the number that was true then, and the monthly proof pins each stored day to the lines beneath it.
- GL
- General ledger, the books this module lands and proves.
- SAP
- The sibling platform; its as-of failures are documented in this catalog.
- as-of balance
- The balance on a stated past date, stored not rebuilt.
- rebuilt balance
- Today minus activity; drifts with every correction.
- daily balance fact
- One stored row per account, worktag set, and day.
- the as-of family
- This catalog’s cross-platform pattern for past dates.