SAP AR Aging Report: AR Open Items + Aging 360

What this report answers

PostNow.ai's AR Open Items + Aging 360 (FICO-13) is the working list for credit control and the receivables line of the month-end pack. It answers:

• How much is overdue at the key date, per customer and company code, and how is it spread across your buckets?
• Which customers push DSO up this month? DSO is a ratio you calculate; this report gives you its receivables side, item by item.
• Which overdue items belong to which dunning area, so each collections team works its own list?
• Which credits are payments on account or credit memos waiting to be applied rather than money the customer still owes?

Each row is one open customer item: company code, customer, name and country, document number, type and dates, baseline date, payment terms, Days 1 discount, amounts in local and document currency, debit/credit indicator, item text, dunning area and reconciliation account. Aging buckets are derived in Excel from the key date you choose; the report delivers the dates they are built on.

FBL5N and S_ALR_87012168: the SAP standard way, and where it stops

PostNow.ai reads the same customer open items that FBL5N (Customer Line Items) shows as open at a key date, cleared, or all items. For aging, SAP ships S_ALR_87012168, Due Date Analysis for Open Items, which groups customer items into due and not-due intervals, and S_ALR_87012178, Customer Open Item Analysis by Balance of Overdue Items, which analyses customers by their overdue balance in up to five intervals. On S/4HANA the Fiori app Days Sales Outstanding (F1741) shows DSO.

The dunning run (F150, with procedures configured in FBMP) decides who gets a letter at which level; it does not produce an aging you can work. And each standard report stops at a list: a collections workbook with your buckets, an owner per customer and notes from the last call still means exporting, fixing signs and rebuilding every month.

SAP tables behind it: BSID, KNB1 and the dunning fields

PostNow.ai's FICO-13 joins BSID (open customer items) to KNA1 for name and country, KNB1 for the company-code data, T003T for document type texts and T001 for the company name.

• BSID vs BSAD. BSID is the secondary index of open customer items, BSAD the cleared ones. On S/4HANA both are read-only compatibility views that read the Universal Journal (ACDOCA).
• Dunning fields on the item. MABER is the dunning area (delivered), MANST the dunning level, MADAT the date of the last dunning notice and MANSP a dunning block. KNB5 holds the customer's dunning data per company code and dunning area. Dunning areas exist so that parts of one company code, a division or sales organisation, can dun separately.
• Customer company-code data. KNB1 carries the reconciliation account (AKONT, delivered) and the accounting clerk (BUSAB). If your collectors are organised by clerk, have a designer add BUSAB, MANST and MADAT in the visual builder and the list sorts itself by owner and dunning stage.
• Due date fields. Baseline date ZFBDT plus the days in the payment terms ZTERM give the net due date, exactly as on the vendor side.

Checks to run before you send the list to collections

1. Signs. For a customer, S (debit) is the invoice side and H (credit) is a payment on account or a credit memo. Net them per customer before you rank anyone by overdue balance.
2. Partial payments vs residual items. With a partial payment, the invoice and the payment both stay open: the invoice still shows its full amount in its old bucket and the payment sits beside it as a credit. With residual item processing, the invoice is cleared and a new item is created for the remainder; check the dates on that new item before you treat it as current.
3. Down payment requests. Special G/L indicator F marks a down payment request, a noted item that updates no balance. Received down payments post to their own reconciliation account. Split by Recon Account, or add the special G/L indicator, so neither ends up in trade AR.
4. Key date and cleared items. BSID holds what is open today. For a month-end aging pulled later, add the BSAD items cleared after the key date and keep posting date ≤ key date.
5. Dunning area. If the column is blank on every row, your company code does not use dunning areas; do not split the list on it.
6. Currency. Age and total on local currency within a company code; quote document currency to the customer.

How PostNow.ai runs it

In PostNow.ai the report runs from the Report Library in the Excel add-in. You select by company code, customer, fiscal year, posting date, baseline date, document number, document type and dunning area, with SAP value help, and the rows land in your sheet read-only from your own SAP session. Share the saved report to Team Reports and each collector refreshes it for their own dunning area each morning, with the same columns and the same selection. The vendor-side twin is AP Open Items + Aging; for the full documents behind a customer balance, use GL Line Items 360.