BI Analytics — AR Aging (Receivables Aging)
Who can do this
Section titled “Who can do this”Available on the Elite plan with the billing feature active, currently in beta with selective customer access.
Where to find it
Section titled “Where to find it”Path: BI Analytics > Billing & Payments > Receivables Aging tab
| KPI | What it tells you |
|---|---|
| **Average DSO** | Amount-weighted days from invoice to payment (or today for unpaid) |
| **Realization %** | Confirmed revenue / production value |
| **Average billing lag** | Days from work to invoice — context for collections |
How to use it
Section titled “How to use it”Daily collections priority
Section titled “Daily collections priority”- Sort by 60+ aging bucket desc
- Top clients are today’s call list
- Drill in to see which specific invoices
- Note any with payment plans or known disputes
DSO trend per client
Section titled “DSO trend per client”- Filter to one client, period = last 12 months
- DSO column shows trend
- Decide if payment terms need renegotiation
Health chips most common here
Section titled “Health chips most common here”Slow payment, High overdue, AR aging risk, Payment deteriorating, Poor collection; Fast payer (positive).
Troubleshooting
Section titled “Troubleshooting”DSO is blank for one client
Section titled “DSO is blank for one client”No confirmed invoices in the period — nothing to compute against.
Fast payer chip showing on a client with overdue invoices
Section titled “Fast payer chip showing on a client with overdue invoices”Fast payer is a longer-trailing signal; current overdue is recent. A formerly-fast payer can develop current overdue. Investigate the relationship change.
Can I export the AR aging?
Section titled “Can I export the AR aging?”Yes — the table export gives you the full per-client / per-bucket grid.
How is DSO computed?
Section titled “How is DSO computed?”Amount-weighted across paid + confirmed-unpaid invoices. Paid: (paid date − invoice date) × net amount. Unpaid: (today − invoice date) × outstanding. Weighted by amount so one large slow invoice cannot be hidden by many small fast ones.