Direct answer

Accounts receivable ageing groups unpaid customer items by how far they are from or past their due date at a specified reporting date. Finance uses the view to prioritize collections, understand overdue concentration and discuss cash-flow risk. Ageing alone does not prove a balance is uncollectible: disputes, unapplied payments, credit memos and customer terms must be checked.

Choose the right reporting date

An ageing report is meaningful only with a clearly stated key date. It should distinguish invoices that are not yet due from overdue invoices, and explain whether buckets are driven by net due date or another approved basis. A report generated later may give different answers because new payments, credits or postings have occurred.

How the intervals work

A common illustrative layout includes current, 1–30 days past due, 31–60 days, and more than 60 days. These intervals are company-defined reporting choices, not mandatory SAP-wide bucket defaults. SAP receivables analysis may offer due-date, overdue or ageing-oriented views depending on application and deployment.

A practical customer example

At month-end, a customer has three open items: an invoice of ₹50,000 due next week, an unpaid ₹18,000 invoice overdue by 12 days, and a ₹7,000 invoice overdue by 47 days. With the chosen key date, the first belongs in the current bucket, the second in the 1–30-day overdue bucket, and the third in the 31–60-day bucket. The ₹25,000 overdue total still requires checking payments in transit and disputed amounts.

Finance and collections teams review customer balances and payment evidence.
Finance and collections teams review customer balances and payment evidence.

Why the original due date matters

Invoice date is not necessarily due date. Contractual payment terms, baseline dates, credit memos and approved changes influence when payment is expected. A collector who calls the customer before checking those facts risks escalating a balance that is not truly delinquent.

Use the view to manage exceptions

Collections should separate routine reminders from disputed invoices, short payments, unallocated cash and known insolvency risks. Investigate credit balances as well as overdue debit balances. An invoice can appear old because a receipt was posted on account without matching the corresponding open item.

Illustrative ageing timeline linking bucket age, collection response and accountable role.
Illustrative ageing timeline linking bucket age, collection response and accountable role.

Governance and process ownership

Accounts receivable analysts assemble accurate open-item data; collectors own follow-up; sales teams help resolve commercial disputes; credit managers monitor concentration; and Finance reviews provisions and reporting policy. A controller should reconcile the ageing totals to relevant customer balances at a consistent cutoff.

Questions a consultant should ask

Which due-date definition drives the report? Are partial payments and residual items shown consistently? How are disputes and unapplied cash distinguished? Are the bucket thresholds appropriate to the business? Can teams drill from a summary into the underlying invoice and clearing documents? Test these scenarios before trusting ageing reports in decision meetings.

Read next

Bad Debt and Customer Write-Off Concepts; Incoming Payment Processing; Customer Account Clearing; Customer Invoice Accounting. Return to SAP FI / FICO.

Official SAP References