RunwayDigest

What a Founder Should Look at When AR Starts Stretching

April 30, 2026 · 9 min read

Key takeaways

  • AR starts stretching when revenue takes longer to turn into cash.
  • Growing AR can be normal, but aging, overdue, or less reliable AR can weaken cash safety.
  • DSO shows the collection trend; the overdue list shows where to act.
  • AR is a point-in-time snapshot, so temporary improvement is not always structural improvement.
  • Founders should connect AR movement to runway, spending decisions, and downside control.

AR starts stretching when revenue is taking longer to turn into cash.

That is the simple definition.

AR means accounts receivable: money customers owe the company after revenue has been earned or invoiced.

Stretching does not simply mean AR is growing.

Growing AR can be normal.

If revenue grows, receivables often grow too.

The real question is whether receivables are growing faster, aging longer, slipping further away from expected receipt dates, or becoming less reliable as a source of cash.

That distinction matters.

A company can show stronger revenue and still become more cash-fragile if the cash takes longer to arrive.

That is what founders should watch when AR starts stretching.

AR stretching is about distance from cash

Accounts receivable can look safe because it sits close to revenue.

The customer exists.

The invoice may already be issued.

The amount is visible.

The company may reasonably expect payment.

But AR is not cash.

Until the money arrives, the company is still funding the gap.

Payroll still needs to be paid.

Suppliers still need to be paid.

Cloud bills, contractors, taxes, debt payments, inventory, delivery costs, and customer support do not always wait for collections.

So the practical question is not only:

How much AR do we have?

It is:

How far is that AR from usable cash?

When AR starts stretching, the distance between the revenue story and the cash story may be widening.

That is the signal.

The common founder mistake

The common mistake is treating higher AR as a normal side effect of growth without checking why it is growing.

Sometimes that view is correct.

A growing B2B company will often carry more AR.

A larger customer base usually creates more invoices.

Enterprise customers may have formal payment processes.

Payment terms may be part of the business model.

None of that automatically means something is wrong.

But it becomes dangerous when the explanation stops there.

“Revenue is growing, so AR is growing.”

That sentence may be true.

It may also hide the real cash issue.

AR can grow because the business is growing.

AR can also grow because customers are paying more slowly.

AR can grow because payment terms are getting longer.

AR can grow because invoices are not being sent on time.

AR can grow because approvals, purchase orders, disputes, or customer-side cash issues are delaying payment.

AR can grow because one large customer is becoming a bigger part of the cash plan.

The same balance can tell very different stories.

Founders should not ask only whether AR increased.

They should ask why it increased.

The number alone is not enough

The total AR number is a snapshot.

That is useful, but incomplete.

A large AR balance at one point in time may simply reflect a strong billing month.

A sudden decline in AR may reflect a successful early collection push.

Neither number, by itself, tells you whether the underlying cash conversion has improved.

This is similar to runway.

A runway number can look precise and still be badly read if the assumptions underneath it are weak.

AR is the same.

The balance matters, but the quality underneath matters more.

Two companies can both show $1 million of AR.

In one company, most of it may be current, diversified, due soon, and historically reliable.

In another company, a large portion may be overdue, concentrated in one customer, tied to a dispute, blocked by documentation issues, or sitting in a country where cash cannot easily be remitted.

Those are not the same cash situation.

A particularly important case is trapped or restricted collections.

A company may show AR from a customer in a country where foreign currency cannot be sent out due to local policy or capital controls.

The AR may remain on the books for years.

On paper, it is still an asset.

In cash reality, it may not be usable cash.

At some point, if recovery becomes unlikely, the company may need to recognize a credit loss or write the receivable off.

That is an extreme case, but it shows the point clearly.

AR is not just a balance.

It is a claim on future cash, and the quality of that claim matters.

Start with DSO and the overdue list

If a founder can only look at two things when AR starts stretching, start with these:

DSO and the overdue list.

DSO, or days sales outstanding, shows how long it takes to collect revenue after it is recognized or invoiced.

It is not perfect.

But it is useful because it shows whether the company’s revenue-to-cash cycle is getting slower.

If DSO was 45 days, then moved to 60, then 75, that is a real signal.

The overdue list is more concrete.

It shows who has not paid when expected.

Together, these two views answer the first practical questions:

Is the overall collection cycle getting longer?

And which customers are creating the risk?

That combination matters because averages can hide problems.

A company may have a stable average DSO while one large customer is slipping badly.

Or the overdue list may look manageable while the overall collection trend is quietly worsening.

Founders should use both.

DSO shows the trend.

The overdue list shows where to act.

What to check when AR starts stretching

When AR starts stretching, a founder should review at least five areas.

First, compare AR growth with revenue growth.

If revenue is up 10% and AR is up 10%, the movement may be normal.

If revenue is up 10% and AR is up 30%, the company should look more closely.

That does not automatically mean there is a problem.

But it does mean revenue is not becoming cash at the same speed.

Second, review DSO.

Look at the current month.

Look at the prior month.

Look at the last three to six months.

Look at the same period last year if the business has seasonality.

A year-over-year view helps avoid overreacting to seasonal billing cycles.

A moving average helps separate noise from trend.

This is worth building into the monthly format.

Do not look at only one point in time.

Look at whether the collection cycle is actually moving.

Third, review AR aging.

Current AR is different from 30-day overdue AR.

30-day overdue AR is different from 90-day overdue AR.

Old AR is not just “still collectible.”

It may be a signal of process issues, dispute risk, customer weakness, or poor ownership.

Fourth, review customer concentration.

If one or two customers make up a large share of AR, their payment behavior can affect runway.

A large customer may have low default risk but high timing risk.

That means they may pay eventually, but not when the company needs the cash.

Fifth, review terms and process.

Are payment terms getting longer?

Has the company moved from prepayment to post-payment?

Are invoices sent after delivery, after acceptance, or after customer approval?

Are purchase order requirements delaying payment?

Are disputes increasing?

Is sales offering terms that create finance pressure?

AR stretching is rarely just one number.

It is usually a mix of revenue growth, terms, billing process, customer behavior, and cash timing.

Why “why” matters more than the balance

If AR is stretching, the most important question is why.

This is the part finance should investigate before the monthly review.

A founder does not need only the balance.

They need the reason.

AR increased because revenue grew.

AR increased because invoices were sent late.

AR increased because a large customer changed payment behavior.

AR increased because payment terms became longer.

AR increased because a customer is disputing part of the invoice.

AR increased because a country-level payment restriction trapped cash.

AR increased because the company pushed hard for early collections last month, making this month look worse by comparison.

These are different stories.

They require different actions.

A billing process issue may require internal cleanup.

A slow enterprise process may require better documentation and follow-up.

A customer concentration issue may require more conservative forecasting.

A credit issue may require tighter terms.

A trapped cash issue may require a different view of usable cash.

A temporary billing spike may require no major action.

The balance tells you that something changed.

The reason tells you what to do.

Do not mistake a managed snapshot for structural improvement

AR is a point-in-time number.

That matters.

A company can make AR look better temporarily.

It can push for early collections.

It can delay billing.

It can collect aggressively before month-end.

It can benefit from one large receipt.

It can show a lower AR balance at the review date without fixing the underlying collection cycle.

That is why DSO trend, overdue movement, and expected receipts matter.

If AR falls once, but DSO has not structurally improved, the issue may not be solved.

If overdue customers pay one month but then stretch again the next month, the pattern still matters.

If early collections were achieved by pulling future cash into the current period, the next period may be weaker.

A better review asks:

Did AR improve because the process improved?

Or did the company simply control the snapshot?

This is where founders need to be careful.

A good-looking AR balance can flatter the cash story.

The real question is whether revenue is consistently becoming cash on a more reliable timeline.

When AR stretching matters most

AR stretching matters most when cash timing already matters.

That includes B2B companies selling to larger customers.

Enterprise customers can be attractive.

They bring larger contracts, stronger logos, and credibility.

But they can also bring longer payment terms, purchase orders, procurement steps, vendor onboarding, invoice requirements, and delayed approvals.

The growth story improves.

The cash cycle may get heavier.

AR stretching also matters during rapid growth.

When revenue rises quickly, delivery costs, hiring, customer support, implementation, inventory, and contractor spend often rise before cash is collected.

If collections slow at the same time, the company may fund more of its growth from its own cash.

It also matters when payment terms shift.

Moving from upfront payment to net 30, net 60, or payment after acceptance changes the business.

The revenue amount may be the same.

The cash reality is not.

It matters even more outside pure software.

Companies that buy inventory, purchase components, manufacture products, or pay suppliers before customer cash arrives can feel AR stretching more sharply.

Cash leaves early.

Cash returns late.

That gap can become the business model’s real funding need.

It also matters when cash buffer is thin.

A company with a large cash balance may absorb a few weeks of delay.

A company with a short runway, high fixed costs, or heavy supplier commitments may not have that room.

The same AR delay can be manageable for one company and dangerous for another.

Do not overreact to every AR increase

AR stretching should not create panic every time receivables increase.

A higher AR balance can be normal.

A large invoice may have gone out near month-end.

A seasonal billing cycle may temporarily increase receivables.

A large customer may still be within agreed terms.

A normal growth month may create more AR without any collection weakness.

The danger is not AR growth itself.

The danger is misreading the reason.

Temporary AR movement is different from structural deterioration.

A one-time billing spike is different from worsening DSO.

A customer still within terms is different from a customer repeatedly overdue.

A large current receivable is different from old AR that keeps rolling forward.

A planned terms change is different from uncontrolled collection delay.

The founder’s job is not to fear AR.

The founder’s job is to read AR.

That means separating timing, growth, process, customer behavior, credit quality, and forecast impact.

What investors and teams need to hear

AR stretching should be explained in a way that does not overstate or understate the issue.

The simplest framing is this:

Revenue is still growing, but the time from revenue to cash is lengthening.

Then explain why.

That second part is essential.

If the company says only “AR is stretching,” the message may feel vague.

If the company explains the cause, the discussion becomes useful.

For example:

Revenue growth remains strong, but AR has started to stretch because enterprise customers are moving through longer approval and payment cycles.

Or:

Revenue is growing, but DSO has increased and the overdue list is concentrated in two customers, so we are updating cash timing and reviewing terms.

Or:

AR increased this month because of a large invoice issued near month-end. The balance is still within terms, so we do not see this as a structural collection issue yet.

This is the right tone.

It does not deny growth.

It does not panic.

It connects the revenue story to cash reality.

For internal teams, the message can be even simpler:

This revenue is good news.

But it is not cash yet.

We need to know when it becomes cash, why any delay is happening, and whether our spending plan still makes sense.

That is the conversation founders should create.

How to review AR stretching each month

AR stretching should be part of the monthly cash review.

It should not be handled only as an accounting cleanup item.

A practical monthly review can follow this order.

Start with revenue versus AR growth.

Did AR grow in line with revenue, or faster than revenue?

Then review DSO.

What is DSO this month?

What was it last month?

What is the three-month moving average?

How does it compare with the same period last year?

Then review AR aging.

How much is current?

How much is 30 days overdue?

How much is 60 days overdue?

How much is 90 days or more overdue?

Then review the overdue list.

Which customers are overdue?

How much is overdue?

Why is it overdue?

Who owns the follow-up?

What is the updated expected receipt date?

Then compare expected receipts with actual receipts.

What cash was expected this month?

What actually arrived?

Which receipts slipped?

Are slipped receipts moving again from one forecast to the next?

Then connect the answer to decisions.

Does the runway forecast change?

Does spending direction need to change?

Do customer terms need review?

Should the company require prepayment, shorter terms, or tighter credit for certain customers?

Does any AR need to be treated as risky or excluded from usable cash planning?

This is how AR becomes useful.

Not as a static balance.

As a cash signal.

What the number is really telling you

When AR starts stretching, it may be telling you several things at once.

It may be telling you that revenue is growing.

It may be telling you that customers are larger.

It may be telling you that payment terms are changing.

It may be telling you that billing operations are not keeping up.

It may be telling you that a few customers are quietly becoming cash risks.

It may be telling you that growth is consuming more working capital than expected.

It may be telling you that runway confidence is too high.

The balance itself does not choose the interpretation.

The company has to read it.

That is why founders should not stop at “AR increased.”

They should ask:

Is this AR young or old?

Is it concentrated or diversified?

Is it within terms or overdue?

Is it one-time or repeated?

Is it collectible but slow?

Is it technically collectible but not usable?

Is it tied to specific spending decisions?

Is it already reflected in the cash forecast?

Those questions turn AR from an accounting line into a management signal.

How RunwayDigest fits

RunwayDigest helps founders and finance leads read runway, burn, and cash direction from their inputs.

The point is not to replace judgment.

It is to make the current cash read clearer, faster, and easier to act on.

AR stretching matters because a runway number can look acceptable while cash is taking longer to arrive.

Revenue may be growing.

Receivables may be rising.

The forecast may still assume expected collections.

But if DSO is worsening, overdue AR is increasing, or expected receipts keep slipping, cash safety may be weaker than the headline runway suggests.

A better cash read asks:

Which expected receipts support this runway number?

How reliable are they?

What happens if they move by 30 days?

Which spending decisions depend on them?

If you want a simpler way to read your current runway, burn, and cash direction, RunwayDigest can turn your inputs into a structured report by email.

Start free.

About the author

RunwayDigest Editorial Team

RunwayDigest Editorial Team writes about runway, burn, cash direction, and the operating habits that help founders and finance leads make calmer cash decisions.

Want a structured runway report by email?

RunwayDigest turns your inputs into a structured runway, burn, and cash direction report and sends it by email. Start with the free version.

Start free

← Back to Insights