Receivables Aging Forecast

A business has $500,000 in invoices less than 30 days overdue, and if historical evidence suggests 70% will be paid next month, a simple forecast projects $350,000 collected and $150,000 remaining, before new invoices and adjustments. The result needs refinement for large unusual accounts.

Start with a clean aging report, where Stripe describes unpaid invoices grouped by age ranges such as 0-30, 31-60 and 61-90 days, and confirm whether age is measured from invoice date or due date, because the answer changes the buckets. Reconcile the opening total to the receivables ledger, since unapplied payments, credit notes and disputed invoices can overstate collectible balances, and fix known errors before applying a forecast percentage.

Choose the question, because a forecast of future bucket balances differs from a cash-collection forecast, with the first able to include new invoices and the second tracking receipts from a defined opening population. Use historical transitions by estimating how much of each bucket was paid, credited, written off or rolled to an older bucket in comparable past periods, and avoid assuming previous-month rates are universal.

A collections-forecasting guide from Rex describes applying past aging-bucket collection behaviour or forecasting individual invoices from customer payment patterns, though its claim that one method is always most accurate is vendor commentary, not a universal guarantee. Identify large invoices separately, because one $200,000 disputed account can dominate a bucket and distort an average, so use current customer evidence and dispute status alongside statistical rates.

An illustrative one-month collection estimate is opening bucket balance times expected collection share, so at $500,000 and 70% the estimate is $350,000, and the remaining $150,000 should be forecast by expected credits, rollover and continuing collection rather than assumed to become bad debt. Track timing, since a payment expected in week one and one expected at month-end have different effects on liquidity, so a monthly aging forecast may need a more detailed cash companion.

Separate contractual due date from likely payment, because a customer often paying 10 days late may need a realistic cash date while the legal balance still follows its contract terms. Account for new sales and invoices, since to forecast the whole closing receivables aging the invoices expected during the period and their likely payment timing must be added, otherwise the model only describes attrition of the opening book.

Use cohorts when patterns differ, because government buyers, subscriptions, project milestones and retail invoices may have different payment behaviour, but do not split data so finely that estimates become unstable. Review write-offs and provisions separately, since a forecast that cash will arrive late is not automatically an accounting conclusion about impairment and the relevant accounting policy and evidence should be followed.

Check for seasonal changes, as year-end holidays, tax periods and a known customer system migration can delay payment, so label overrides and revisit them after actual receipts arrive. Update each period by comparing predicted collections and aging migration with actuals, then explain misses from timing, disputes, data errors or changing customer mix, and recalibrate the model.

Avoid using the forecast as a collection permission, since it should guide accurate follow-up and not trigger fees or pressure beyond agreements and applicable rules. Present uncertainty, because a range or scenario can be more useful than one precise-looking number when a few large invoices dominate, and for an owner the aging forecast shows how much cash may arrive from money already owed and how much may become older, supporting a cash plan and earlier problem-solving with customers.