Aging reports in Business Central

Aging reports are the standard analytical lens for accounts receivable and accounts payable — how old are the open balances, where is the risk concentrated, where is the cash-flow opportunity. Business Central ships several aging reports with configurable buckets, dimension filters, and Excel / PDF export. Understanding them is essential for AR/AP-led teams.

Customer aging — the standard. The Aged Accounts Receivable report:

• Lists every customer with an open balance as of a chosen date.
• Splits each customer's balance into aging buckets — typically 0–30 days, 31–60, 61–90, over 90, with the report date as the anchor.
• Aging based on due date (the default) or document date depending on the parameter.
• Per-customer totals with overall company total.
• Outputs as printed report, PDF, or Excel for deeper analysis.

Buckets are configurable per run — for tight cash-flow management you might use weekly buckets (0–7, 8–14, 15–21, 22+ days); for general aging the monthly buckets are standard.

Vendor aging — the mirror. The Aged Accounts Payable report has the same structure for vendor open balances. Used by AP teams to prioritise payment runs, identify ageing supplier liabilities, and manage cash-out timing.

Dimensions and filters. Aging reports accept filters: customer / vendor selection, salesperson, department dimension, payment terms. Useful when one team handles strategic accounts separately from the rest.

Currency. Multi-currency tenants see aging in:

• Local currency — converted at posting rates.
• Original currency — the customer's transactional currency.

Toggleable per run. For multi-currency analysis, the currency-converted view is the standard.

Detail vs summary. Two flavours:

• Summary — one row per customer, aging-bucket totals across.
• Detail — one row per open document, with aging-bucket allocation. Used for investigating large accounts or specific overdue invoices.

As-of date. Aging is typically run as-of the current date, but the report supports historical as-of dates — useful for reproducing audit positions, comparing aging over time, or analysing collection performance.

Integration with reminders. Aging reports identify the customers and amounts that need reminder action. The reminder routine consumes the same underlying ledger data and proposes reminders for entries past their due date.

Integration with Power BI. Pre-built Power BI templates for BC include aging visualisations:

• AR aging heatmap (customer × bucket).
• Trending aging over time.
• Top-overdue customers list.
• AR-as-% of total revenue by month.
• DSO (Days Sales Outstanding) trend.

For interactive analysis, Power BI is preferable to the static aging report.

DSO and DPO. Beyond aging buckets, two derived metrics:

• DSO (Days Sales Outstanding) — average time to collect, computed as AR / average daily revenue. Trend matters more than absolute value.
• DPO (Days Payable Outstanding) — average time taken to pay, AP / average daily expense.

Standard health-of-AR/AP signals. BC doesn't ship native DSO/DPO reports; they're computed in Power BI or Excel from the underlying data.

Common pitfalls.

• Aging by document date instead of due date — looks worse than reality for customers with long payment terms. Default to due date.
• Ignoring credit memos — credit memos reduce open balance; aging that doesn't apply them shows inflated outstanding.
• Customer with only payments on account — appears with negative balance, sometimes confusing. Investigate the application status.
• Stale aging — running once a quarter and reacting only at quarter-end. Run weekly during active collections.

Operational reality. Aging reports are the daily currency of credit / collections / treasury work. Embed them into the morning routine; act on them; iterate the collection process based on what they show.