Receivables reporting

Receivables reporting answers three questions: what do customers owe, how much of it is late, and is collection getting better or worse? The first two are operational, used daily by collections. The third is a management question, usually answered with the days sales outstanding (DSO) KPI. All three rely on the same line items, so their accuracy depends on everything in the earlier lessons: correct due dates, prompt clearing and sensible handling of differences.

Line items and balances

Manage Customer Line Items shows open items at a key date with net due date, days overdue, dunning level and block. Display Customer Balances shows balances by period. For a collector preparing a call to Great Lakes Fleet Services, a saved view of open items sorted by net due date, with dunning level and dispute reason columns, is the most useful single screen.

Aging

An aging view groups open items into buckets by days overdue at a key date: not yet due, 1–30, 31–60, 61–90, over 90. SAP S/4HANA offers analytical Fiori apps for overdue receivables and aging; the exact app names and availability vary by release and license, so check the Fiori apps reference library for your system. Whatever the tool, the buckets are only as good as the net due dates on the items.

Days sales outstanding

DSO estimates how many days of sales are sitting in receivables. A common formula is DSO = receivables at period end ÷ credit sales for the period × days in the period. If Contoso has 2,713,000 USD in receivables at the end of a 90-day quarter with credit sales of 8,100,000 USD, DSO is 2,713,000 ÷ 8,100,000 × 90 ≈ 30 days. SAP's analytical apps calculate DSO with their own definitions; when comparing with the legacy ECC report, agree the formula first, because two correct formulas can give different numbers.

A collector's daily routine

1. Open the saved view of overdue items, sorted by amount and days overdue.
2. Check unapplied cash for the customer before calling; the "overdue" invoice may already be paid.
3. Review dunning level and any dispute or block reason on each item.
4. Record the outcome of the call (promise to pay, dispute, wrong contact) where the team keeps collection notes.
5. Escalate items over the agreed age to sales and credit management.

In Public Edition the same reporting ideas apply, and the apps available follow SAP's delivered scope; in Private Edition the project decides which analytical apps and roles to activate. Either way, ask the reporting team which app is the agreed source of truth for aging and DSO, so testers and managers look at the same numbers.

Comparing with ECC after migration

At go-live, Dan will be asked whether receivables in SAP S/4HANA match ECC. The total open balance per customer at the cutover key date must match exactly. Aging buckets should match too, provided the migrated items kept their original baseline dates and terms. DSO may differ slightly if the formula differs. Plan this comparison as a formal test with Luis's cutover plan, not as an afterthought.