Is a high DSO always a sign of a collections problem?

Not necessarily. A rising DSO can reflect looser credit terms, a changing customer mix, disputes, or genuine payment risk. It should be broken down by cause before deciding on a response.

How can a CFO tell if write-offs reflect real credit losses or process gaps?

Reviewing whether written-off accounts followed a consistent escalation and documentation process before being abandoned is a useful way to separate genuine credit losses from accounts that were simply never pursued.

How often should escalation policy be reviewed?

Many finance teams review the underlying policy annually, while the aging report itself should be reviewed on at least a monthly cadence.

What CFOs Should Know About Aging B2B Receivables

For a CFO, aging receivables are not just an operational AR problem — they are a cash flow and balance sheet issue that deserves periodic direct attention rather than delegation without oversight. The most useful CFO-level view combines aggregate metrics like DSO with a structural understanding of where and why the escalation process breaks down.

9 min read

Definition

For CFOs, managing aging B2B receivables means overseeing not just the size of the delinquent balance, but the process discipline — timely escalation, consistent documentation, and clear write-off criteria — that determines how much of that balance is ultimately recoverable.

DSO tells you there's a problem, not what to do about it

Days Sales Outstanding is a useful trend indicator, but a rising DSO can result from very different underlying causes: looser credit terms extended to win business, a slower-paying customer mix, internal AR process breakdowns, or genuine deterioration in customer financial health. A CFO reviewing DSO in isolation risks addressing the wrong problem — for example, tightening credit policy broadly when the real issue is that a handful of large accounts are not being escalated on time.

A more diagnostic approach breaks aging receivables down by cause: disputed invoices, slow-but-solvent customers, and genuinely at-risk accounts. Each requires a different response, and lumping them together in a single DSO number obscures where action is actually needed.

The hidden cost of inconsistent escalation policy

Many companies do not have a written, consistently applied policy for when an account moves from internal AR follow-up to a more structured collections process. In practice, this means escalation decisions are made informally — often influenced by relationship history or whoever happens to be managing the account — which produces inconsistent recovery outcomes and makes it difficult to benchmark performance over time.

A written policy tying escalation triggers to days-past-due, contact-attempt counts, and balance thresholds gives a CFO a defensible, auditable process and removes the guesswork that otherwise causes accounts to age past the point of realistic recovery.

Write-offs can mask a process problem

A rising bad debt write-off line is sometimes treated as simply a cost of doing business, but a closer look often reveals that a meaningful share of written-off accounts were never properly escalated or investigated before being abandoned. Distinguishing 'genuinely uncollectible' write-offs from 'never seriously pursued' write-offs is a useful exercise for identifying whether the loss is a customer credit-risk issue or an internal process gap.

Building a periodic review cadence

A monthly review of the aging report segmented by cause (dispute, slow-pay, at-risk) rather than age bucket alone
A quarterly review of write-off accounts to identify whether escalation policy was actually followed before write-off
An annual review of credit policy and escalation thresholds against actual recovery outcomes
A standing process for periodically reviewing whether previously written-off or dormant accounts still warrant monitoring, particularly larger balances

Frequently asked questions

Is a high DSO always a sign of a collections problem?: Not necessarily. A rising DSO can reflect looser credit terms, a changing customer mix, disputes, or genuine payment risk. It should be broken down by cause before deciding on a response.
How can a CFO tell if write-offs reflect real credit losses or process gaps?: Reviewing whether written-off accounts followed a consistent escalation and documentation process before being abandoned is a useful way to separate genuine credit losses from accounts that were simply never pursued.
How often should escalation policy be reviewed?: Many finance teams review the underlying policy annually, while the aging report itself should be reviewed on at least a monthly cadence.