Workday · Financials · Report
Payables, as of any date
Ask what payables was on a past date and most systems rebuild backwards through every late edit since. The stored answer keeps three month-ends here, and two of them are the roll-forward’s own endpoints.
◆ Three month-endstwo of them already promised.
| Accounts payable, as of | Balance |
|---|---|
| 31 March 2026 | 512,700.00 |
| 30 April 2026 | 495,000.00 |
| 31 May 2026 | 684,550.00 |
April’s balance is the roll-forward’s opening and May’s is its closing, which is what an as-of store owes the pages around it: not new numbers, the same numbers, available for any date. The aging buckets the May figure; this page remembers all three. Sample values are illustrative, never client data.
◆ The owned answerthe same store the aging reads.
Open items are stored per day on the supplier star; the balance is their daily sum, kept. The as-of hub collects this pattern across every platform, and the subledger joins the ledger’s own as-of page here.
Use case
Problem
Auditors ask for the payables balance as it stood, the system rebuilds it from current open items, and late invoices make the rebuilt answer drift from what was reported.
What we build
Daily stored balances from the open-item store, pinned to the roll-forward’s endpoints, answering any date as a filter.
What you get
As-of answers that match what was signed at the time, subledger and ledger agreeing on every date, and audit requests that end in minutes.
What was payables on the day the auditor picked?
We build the daily store that answers in one read.
Terms on this page
- AP
- Accounts payable, the money owed to suppliers.
- as-of balance
- The balance on a stated past date, stored not rebuilt.
- daily store
- One balance row per day, derived from open items.
- the pin
- Month-ends matching the roll-forward’s endpoints exactly.
- late invoice
- The edit that makes rebuilt history lie.