Your AR Forecast Is Wrong If It Assumes Everyone Pays on Time

Most MSP cash-flow forecasts treat an invoice due in 30 days as cash in 30 days. Real clients do not behave that way. Some pay early, many pay a week or two late, a few need a reminder, and a handful dispute a line and pay after it is fixed. When the forecast ignores that, cash arrives later and lumpier than expected, usually right before payroll and vendor bills come due.

Why Is an AR Forecast Wrong When It Assumes On-Time Payment?

An accounts receivable (AR) forecast is a projection of when outstanding invoices will turn into cash. The simple version assumes every invoice is paid on its due date. That is almost never true, so the forecast is wrong in a predictable direction: it shows money earlier than it arrives.

The problem is sharper for MSPs, because your costs are not flexible. Vendors bill you monthly on their schedule, payroll runs on a calendar, and neither waits for a client's payment. A forecast that is a few weeks optimistic can turn into a cash shortage even when the business is profitable.

What Are Actual Payment Patterns?

Payment patterns are the real history of how long clients take to pay, measured from invoice date to the day cash is received. Useful measures include:

• Days to pay: the average and the spread for each client, not just the average.
• Percent paid on time: how often a client pays by the due date.
• Aging buckets: how much sits at 1 to 15, 16 to 30, and 30-plus days past due.
• Dispute and partial payment rate: how often an invoice is questioned or only partly paid.
• Seasonal timing: slower payment around year end, fiscal year changes, or holidays.

A client who always pays 12 days late is predictable. That is far more useful to a forecast than a due date they ignore.

How Do You Build a Forecast From Payment History?

1. Pull 12 months of paid invoices: invoice date, due date, paid date, and amount.
2. Calculate days to pay per client: note the typical range, not just the average.
3. Group clients into segments: for example, pays on time, 1 to 15 days late, 16 to 30 days late, 30-plus days late.
4. Apply each segment's timing to open invoices: estimate what share of each month's billing arrives in each week.
5. Adjust for known events: a client's fiscal year end, a pending dispute, or a large one-time invoice.
6. Compare forecast to actual every week: update the segments as clients drift.

Illustrative example, not a benchmark: an MSP invoices $100,000 a month on net 30 terms. Its payment history sorts into four segments.

The on-time forecast shows $100,000 collected by day 30. The pattern-based forecast shows $50,000 by day 30, $80,000 by day 45, and $95,000 by day 60. That $50,000 difference at day 30 is the gap that surprises people.

What Causes Late Payments You Can Influence?

Some lateness is just client behavior. Some of it is yours to fix:

• Invoice errors: a wrong quantity or price gets held while the client questions it.
• Unclear invoices: clients delay payment when they cannot tell what a line is for.
• Late invoicing: an invoice sent on day 10 of the month starts the clock late.
• Friction in how clients pay: extra steps slow payment.
• No follow-up routine: invoices that never get a reminder tend to age.

Accuracy matters most. An invoice that matches the agreement and what you delivered is paid, while one with a questionable line sits in a queue. Gradient Reconcile compares vendor invoices against your agreements, so the invoices you send reflect what you actually deliver, and fewer get held up in questions.

How Should You Use a Pattern-Based Forecast?

• Set a cash buffer to match the gap: if collections routinely lag by two to three weeks, keep enough cash to cover it.
• Line up vendor payments with realistic inflows: know which weeks are tight before they arrive.
• Flag drifting clients early: a client moving from 10 days late to 25 days late is a signal to call.
• Review it weekly: a forecast that is updated each week stays close to reality.

FAQ

What is an AR forecast?

A projection of when your outstanding invoices will turn into cash, usually by week or month.

What is days to pay?

The number of days between sending an invoice and receiving payment, measured per client or per segment.

How many months of payment history should I use?

Twelve months is a good starting point because it captures seasonal patterns. Use more if your client base is large and stable.

Why does my cash flow feel tight when my business is profitable?

Because profit counts invoices when issued, while cash counts payments when received. If clients pay later than the forecast assumes, the shortfall lands on your own bills.

How often should I update the forecast?

Weekly, comparing what you expected with what actually arrived.