Open items as of a past date

The auditor wants receivables aged as they stood at year end. The system recomputes that answer backwards from today, every time, and SAP’s own support notes document the cases where the recomputation is wrong.

RuleStore open items as a daily snapshot you own. An as-of question should read history, not rebuild it.

Neverhand an auditor a key-date report as evidence without saying it is a reconstruction. Reproducibility is the whole point of evidence.

◆ What goes wrongthe recomputation, and the support notes about it.

S/4HANA stores the current clearing state of every item. When a line-item report is asked for open items at a past key date, it starts from now and works backwards: discard documents entered after the date, add back items cleared since. There is no stored picture of the past to consult, only arithmetic against the present.

The recomputation mostly works, and SAP support notes 2457349, 2211987, 1921682, and 3660611 document where it does not: cleared items shown as open, open items missed at the key date. Practitioners have asked for a dependable historical aging on the community forums for over fifteen years, and the accepted answer is still a hand-built reconstruction from the cleared-item tables.

◆ Why finance feels itthe numbers this breaks are the audited ones.

The question	What reconstruction does to it
Aging at the prior year end	Recomputed on request, subject to the documented defects, and different if run again after later postings.
Days sales outstanding trend	Needs open balances at many past dates. Each one is its own reconstruction; the trend inherits every defect.
Audit evidence	Cannot be reproduced exactly at a later date. An auditor asking twice can get two answers.
Restatement questions	Backdated and reversed documents change what the reconstruction returns for dates they cross.

◆ The owned answera daily open-item snapshot, stored once, read forever.

The build is a daily snapshot of open items in your warehouse: one row per open item per day, written by the extraction pipeline and never recomputed. Aging as of any date is a filter. The number for last year end is the same number next year, because it is stored, not derived.

-- receivables aging as of any date, from the stored snapshot
SELECT aging_bucket, SUM(open_amount) AS open_amount
FROM fct_open_item_day
WHERE snapshot_date = DATE '2025-12-31'
  AND ledger = 'receivables'
GROUP BY 1 ORDER BY 1

This is the same discipline this catalog documents for Oracle receivables and for Workday headcount: the transactional system knows now, and the past belongs in a store you own. The cross-platform pattern has its own page, the system only knows now.

Use case

Problem

Auditors and lenders ask for open items as they stood at past dates, and the key-date reports reconstruct the answer with documented defects and no reproducibility.

What we build

A daily open-item snapshot in your warehouse, written by the extraction pipeline and never recomputed, with aging built on top.

What you get

Aging as of any date that returns the same answer every time it is asked, with every band drillable to the items inside it.

Can you reproduce last year end’s aging today?

We ship the daily snapshot that makes the answer stored, exact, and repeatable.

Talk to us

Terms on this page

SAP: The vendor. Systems, Applications, and Products in data processing.
HANA: SAP’s in-memory database, the platform S/4 runs on.
ERP: Enterprise resource planning, the system of record for operations and finance.
open item: An invoice or payment not yet cleared against its counterpart.
key date: The past date a report is asked to reconstruct.
clearing: Matching an open item to the document that settles it.
snapshot: A dated copy of a table state, kept so the past stays queryable.
aging bucket: A band of days overdue, such as 31 to 60 days.