Table of contents

Manual · Page 29 · 19 min

Chapter 27 | Not All Delays Are the Same

Chapter 27 | Not All Delays Are the Same - online reading page from the From Sales to Cash handbook, dedicated to the Quote-to-Cash cycle and Credit Management.

An overdue invoice is not an explanation.

It is a signal.

When an invoice passes its due date, the aged balance shows that it is late. It makes it possible to see how long the invoice has been overdue, what amount is concerned, which customer is exposed and how outstanding balance is distributed by age.

It is an essential tool.

But it is only a starting point.

The aged balance says that an invoice is late. It does not always say why.

Yet two invoices overdue by 60 days can tell two completely different stories.

In the first case, the customer is facing financial difficulty. It no longer responds to reminders, does not keep its promises, pays partially, postpones its commitments and tries to gain time.

In the second case, the customer is solvent and ready to pay, but the invoice is blocked because it contains an internal error: wrong purchase order number, missing delivery note, invoice uploaded on the wrong portal, credit note not issued, validation of service performed not completed, payment already received but not matched.

These two invoices have the same age.

But they do not require the same action.

This is why Collections must not only classify delays by age. It must qualify them.

Understand before acting.

The Aged Balance: A Necessary Tool

The aged balance is one of the most commonly used tools in accounts receivable monitoring.

It classifies open invoices according to their age: not yet due, overdue by 0 to 30 days, 31 to 60 days, 61 to 90 days, more than 90 days, sometimes more depending on the company.

It makes it possible to quickly see overdue amounts.

It helps prioritize actions.

It gives an overview of apparent risk.

It makes it possible to monitor the evolution of DSO, delays, old receivables and portfolio quality.

It is useful for Collections teams, Credit Management, Finance, Treasury, Sales and management.

Without an aged balance, the company navigates blindly.

It does not clearly know who owes what, since when, and for what amount.

But the aged balance is not enough.

It measures the age of the delay. It does not always give its cause.

The Limit of the Aged Balance

The main limit of the aged balance is that it can create an illusion of understanding.

An invoice overdue by more than 90 days seems more serious than an invoice overdue by 10 days. This is often true. But not always.

An invoice of 100,000 euros overdue by 90 days may be blocked by a clearly identified technical dispute, with a credit note being issued. An invoice of 20,000 euros overdue by 15 days may be the first signal of a customer that no longer responds and whose situation is quickly deteriorating.

Age is important, but it does not tell the whole story.

A delay can age because the customer does not want to pay or cannot pay.

It can also age because the company has not corrected an error.

It can age because the dispute has no owner.

It can age because evidence is missing.

It can age because payment has been received but not allocated.

If the company looks only at age, it may take the wrong action.

Strongly chasing a customer that is waiting for a legitimate credit note can damage the relationship.

Blocking an order when the invoice has been paid but not matched can destroy value.

Treating as a simple dispute a customer that truly lacks cash can worsen the loss.

The aged balance must therefore be completed by qualification.

A Delay Is a Question, Not a Conclusion

When an invoice is overdue, the right question is not only: how long has it been overdue?

The right question is: why has this invoice not been paid?

This question changes the posture of Collections.

It forces the team to look for the real cause before choosing the action.

Has the customer received the invoice?

Is the invoice compliant?

Is the purchase order correct?

Is delivery recognized?

Has the service performed been validated?

Does the customer dispute the price, quantity, quality or scope?

Is a credit note expected?

Has a payment been received?

Is the payment unmatched?

Does the customer lack cash?

Is the customer using the delay as leverage?

Has the customer promised to pay?

Has it kept its previous promises?

These questions make it possible to move from an accounting delay to an operational understanding.

Effective Collections starts with diagnosis.

The Main Families of Delays

To qualify delays, it is useful to group them by families.

There are delays linked to the customer: financial difficulty, willingness to pay slowly, internal disorganization, payment policy, broken promise.

There are delays linked to the invoice: amount error, wrong purchase order number, wrong entity, incorrect VAT, invoice sent through the wrong channel, missing attachment.

There are delays linked to execution: disputed delivery, validation of service performed not completed, milestone not recognized, missing intervention report, missing proof of receipt.

There are delays linked to the contract: unclear terms, disagreement on scope, penalty, conditional discount, acceptance not formalized.

There are delays linked to cash application: payment received but not matched, partial payment, unidentified deduction, offset, credit note incorrectly applied.

Finally, there are delays linked to internal organization: absence of a dispute owner, poor information flow, Sales Administration not informed, Operations not mobilized, Sales not aligned.

Each family requires a different action.

This is why all delays must not be treated in the same way.

Financial Delay

Financial delay is the one that comes to mind most naturally.

The customer does not pay because it lacks cash, faces economic difficulty, suffers a drop in activity, loses financing, is waiting to be paid itself, or is approaching a more serious situation.

This type of delay must be taken very seriously.

The signs can be multiple: broken promises, partial payments, requests for a payment plan, silence, changes in contacts, requests for additional time, delays that lengthen, old invoices unpaid, deteriorated external information.

In this case, chasing is not always enough.

Exposure must be reduced, new orders must be blocked or conditioned, partial payment must be requested, a precise payment plan must be put in place, a guarantee must be obtained if possible, the limit must be reviewed and the case must be escalated if the stakes are significant.

Financial delay is a signal of customer risk.

It requires a protective action.

Voluntary or Strategic Delay

Some customers are solvent but deliberately pay slowly.

They use supplier credit as a source of financing. They wait for reminders. They pay according to their own cycles. They delay payments to optimize their cash.

They are not necessarily in difficulty.

But they consume cash.

This type of delay must be distinguished from financial default.

The customer will probably pay, but it will pay too late.

The action is not the same.

Preventive reminders must be strengthened, firm payment dates must be obtained, real payment terms must be discussed, shorter conditions must be negotiated, penalties must be applied if the policy allows it, the limit must be adjusted to the reality of behavior and Sales must be mobilized if the customer is important.

The risk is not necessarily final loss.

The risk is financing suffered by the supplier.

A solvent but slow customer must be managed firmly.

Administrative Delay on the Customer Side

A customer may not pay because its own administrative process is blocked.

The invoice has not yet been recorded.

The purchase order has not been matched.

Receipt has not been entered.

Validation of service performed is waiting for internal approval.

The approving manager is absent.

The portal shows a blocked status.

Payment is waiting for a monthly cycle.

In this case, the customer is not necessarily acting in bad faith.

But cash is still blocked.

Collections must then identify the blocking point in the customer process.

Who must approve?

Which document is missing?

Which status is displayed?

Which action allows the invoice to move to the next step?

What payment date is planned after validation?

This type of delay requires knowing how the customer works and working with the right contacts, not only sending generic reminders.

An invoice may be late simply because it has not yet passed through the customer’s internal workflow.

Delay Caused by an Incorrect Invoice

An incorrect invoice is one of the most frequent causes of delay.

Wrong price.

Wrong quantity.

Wrong discount.

Wrong purchase order number.

Wrong address.

Wrong entity.

Incorrect VAT.

Wrong currency.

Service period incorrectly indicated.

Missing attachment.

Non-compliant sending channel.

In this case, the delay comes from the company.

The customer may refuse to process the invoice until it is corrected.

Chasing without correcting is useless.

The right action is to understand the error, issue the credit note or corrective invoice if necessary, resend the compliant invoice, confirm its acceptance and follow the new due date.

The cause must also be recorded to prevent it from happening again.

An incorrect invoice delay is not a customer delay. It is a weakness in the billing process.

Treating it as an unpaid invoice would be a diagnostic error.

Delay Linked to the Purchase Order

In many organizations, the purchase order is mandatory.

If the invoice does not mention the right number, if the purchase order does not exist, if it does not cover the right amount or if it corresponds to another entity, the customer may block payment.

The supplier may have delivered correctly and invoiced at the right price. But if the customer’s system requires matching with a valid purchase order, the invoice will not be payable.

This type of delay is often avoidable.

It must be anticipated from the order stage.

In Collections, the problem must be handled quickly: obtain the right number, request a regularized purchase order, correct the invoice if necessary, upload it again on the portal, follow acceptance.

The company must also ask why the order was executed without a compliant purchase order if this was mandatory.

The cause of the delay sometimes started long before the due date.

Delay Linked to Execution or Evidence

A customer may block payment because it does not yet recognize the delivery or service.

Missing delivery note.

Receipt not validated.

Intervention report absent.

Acceptance report not signed.

Validation of service performed not confirmed.

Project milestone disputed.

Insufficient documentary evidence.

In this case, the delay is not necessarily a refusal to pay. It is an absence of recognition of execution.

Collections must then mobilize Operations, Sales Administration, the project manager, Logistics or the relevant department.

Evidence must be obtained, receipt status must be clarified, reservations must be handled and documents must be sent to the customer.

Chasing the customer’s Accounts Payable department without providing the expected evidence will not move payment forward.

Here, the delay reveals a problem between operational execution and invoicing.

It is a reminder that cash also depends on evidence.

Delay Linked to a Real Dispute

A real dispute exists when the customer disputes an element in a justified or serious way.

Non-compliant product.

Missing quantity.

Delivery delay with impact.

Price error.

Incomplete service.

Forgotten discount.

Service not validated.

Scope disputed.

In this case, Collections must avoid two mistakes.

The first would be to treat the dispute as a simple excuse and chase without resolving the substance.

The second would be to let the whole outstanding balance remain blocked without distinguishing the part that is really disputed.

The dispute must be qualified: amount concerned, cause, internal owner, expected action, resolution date, impact on payment.

If only part of the amount is disputed, Collections must request payment of the undisputed amount.

A real dispute must be treated quickly, otherwise it becomes involuntary financing granted to the customer.

Delay Linked to a Tactical Dispute

Not all disputes have the same nature.

Some customers use disputes to delay payment.

They dispute late, sometimes just after a reminder. They use vague reasons. They request documents already provided. They dispute a small part but withhold the whole payment. They change arguments. They provide no precise evidence.

This type of behavior must be identified.

A vague dispute must not be allowed to block a receivable indefinitely.

Collections must request a written, precise and documented dispute. It must isolate the amount actually disputed. It must require payment of the undisputed amount. It must escalate if the customer systematically uses this method.

The tactical dispute is a form of behavioral risk.

It is not treated like a simple operational problem.

It requires firmness, documentation and Sales or Legal involvement if necessary.

Delay Linked to an Expected Credit Note

A customer may withhold payment because it expects a credit note.

The credit note may be legitimate: price error, product return, validated discount, accepted penalty, invoice correction.

As long as the credit note has not been issued, the customer may block all or part of the payment.

The question is then simple: is the credit note justified and approved?

If yes, it must be issued quickly and payment of the balance must be chased.

If not, the customer must be told why the deduction is not accepted and full payment or payment of the undisputed amount must be requested.

Pending credit notes must be monitored closely.

An untreated credit note can tie up a lot of cash.

It can also blur the relationship: the customer thinks the company must correct, while the company thinks the customer is not paying.

Qualification helps avoid this confusion.

Delay Linked to Cash Application

Some invoices appear overdue even though they have already been paid.

The payment arrived, but it was not matched to the right invoice.

The customer paid several invoices in one transfer without details.

The payment has no reference.

A deduction or offset has not been understood.

The payment was allocated to the wrong entity.

The credit note was not matched.

In this case, the delay is fictitious or partly fictitious.

Chasing the customer is useless, sometimes even harmful.

The right action is internal: identify the payment, obtain the remittance advice, match correctly, treat differences, update the account.

This type of delay shows why Collections and cash application must be connected.

An aged balance that contains many unmatched payments does not correctly reflect customer risk.

It also reflects the quality of internal processing.

Delay Linked to a Siloed Organization

Sometimes, the delay continues because nobody truly owns the problem.

Collections knows that the customer disputes.

Operations knows that a reservation exists.

The salesperson knows that a discount was promised.

Sales Administration knows that a purchase order is missing.

Billing is waiting for approval.

But no function coordinates the resolution.

The invoice ages.

This type of delay is common in siloed organizations.

Everyone holds part of the information, but nobody turns this information into complete action.

Collections must then play a coordinator or alert role.

It must identify the owner, set a resolution date, monitor progress and escalate if necessary.

An unqualified delay can remain blocked for a long time simply because it has no clear owner.

Qualification must therefore include the question: who must act now?

Qualifying the Delay

Qualifying a delay means assigning it a clear and actionable cause.

It is not only writing “dispute” or “customer does not pay.”

It must be more precise.

Price dispute.

Missing purchase order.

Invoice rejected by portal.

Validation of service performed not completed.

Payment promised on the 15th.

Payment received but not matched.

Credit note to be issued.

Customer cash difficulty.

Unjustified deduction.

Missing delivery document.

This precision changes everything.

It makes it possible to assign the right action to the right person.

It also makes it possible to measure the real causes of delay in the company.

If 30% of delays come from rejected invoices, the problem is not only Collections. If 20% come from missing purchase orders, action is needed at order level. If many delays come from unmatched payments, cash application must be improved.

Qualifying delays makes it possible to move from symptom to cause.

Prioritizing by More Than Age

Age is important, but it must not be the only priority criterion.

The amount, customer risk, cause of delay, probability of resolution, impact on orders, concentration, margin and behavior must also be considered.

A very old invoice for a small amount, linked to a minor difference, does not have the same priority as a recent but significant invoice for a customer showing signs of fragility.

An invoice of 200,000 euros overdue by 10 days may deserve immediate action if the customer is sensitive.

An invoice of 5,000 euros overdue by 120 days may be treated differently if it corresponds to a credit note not posted or a small residual dispute.

Priority must combine age, amount and cause.

Effective Collections does not only follow a chronological queue.

It acts where cash impact and risk are highest.

Choosing the Action According to the Cause

Each cause of delay requires a different action.

Financial difficulty: secure, negotiate a payment plan, reduce exposure, block if necessary.

Voluntary delay: chase firmly, obtain a date, review conditions, mobilize Sales.

Incorrect invoice: correct, reissue, confirm acceptance.

Missing purchase order: obtain or regularize the purchase order, correct references.

Missing evidence: mobilize Operations or Logistics, provide the document.

Real dispute: qualify, resolve, obtain payment of the undisputed amount.

Tactical dispute: request written justification, isolate the disputed amount, escalate.

Expected credit note: approve, issue or challenge the request.

Unmatched payment: work with cash application.

Siloed organization: appoint an owner and follow resolution.

The quality of Collections depends on this fit.

The wrong action on the right cause does not produce cash.

Chasing Is Not Always the First Answer When an invoice is late, the natural reflex is to chase the customer.

This is often necessary, but not always sufficient.

If the invoice is rejected, it must be corrected.

If the delivery note is missing, it must be provided.

If payment has been received but not matched, it must be matched.

If a credit note is expected, it must be handled.

If validation of service performed is not completed, validation must be obtained.

If the dispute is real, it must be resolved.

Chasing without treating the cause can create frustration.

The customer receives payment requests even though it has already explained the blockage. Internal teams repeat the same exchanges. The invoice ages.

Chasing must be adapted to the diagnosis.

Collections is not only about asking for money. It is about removing what prevents money from arriving.

Qualification Improves the Customer Relationship

Qualifying delays also protects the customer relationship.

A good-faith customer may be irritated if it is treated as a bad payer while the invoice is incorrect.

A customer that has already paid may lose trust if it is chased wrongly.

A customer waiting for an approved credit note may feel poorly treated if the company demands full payment without handling the correction.

Conversely, a customer that deliberately delays must not benefit from excessive indulgence.

Qualification makes it possible to be fair.

It makes it possible to adapt tone, action and escalation level.

It avoids confusing internal error, legitimate dispute and poor customer behavior.

Fair Collections is often more effective than Collections that is only insistent.

Qualification Improves Credit Decisions

Credit Management uses delays to decide whether to maintain a limit, block an order, reduce exposure, request a down payment or review conditions.

If delays are not qualified, decisions can be wrong.

A customer may be blocked for overdue invoices even though these invoices are disputed because of internal errors.

Conversely, a customer may seem acceptable because delays are classified as “disputes,” while it systematically uses vague disputes to delay payments.

Qualification gives Credit Management a more precise reading.

It distinguishes customer risk from process risk.

It makes it possible to know whether the problem comes from solvency, behavior, invoice, execution, dispute or matching.

A credit decision based on poorly qualified delays can be unfair, ineffective or dangerous.

Qualification Improves Company Management

When a company properly qualifies its delays, it can understand the real causes of cash blockage.

It can measure amounts retained for price disputes, missing documents, portals, purchase orders, credit notes, unmatched payments, customer financial difficulty, broken promises.

This information is very powerful.

It makes it possible to act at the source.

If delays mainly come from poorly mastered portals, portal management must be improved.

If they come from missing purchase orders, order control must be strengthened.

If they come from execution evidence, the company must work with Operations.

If they come from slow but solvent customers, terms must be negotiated and preventive reminders reinforced.

If they come from customer financial difficulty, limits and conditions must be reviewed.

Collections then becomes a source of improvement for the Quote-to-Cash cycle.

It does not only treat symptoms.

It reveals causes.

Categories Must Remain Simple

To qualify delays, the company must not create a classification that is too complex.

If categories are too numerous, they will not be used correctly. If they are too vague, they will be useless.

A balance must be found.

A few large categories may be enough: customer financial risk, voluntary delay, commercial dispute, operational dispute, billing error, missing document, purchase order, expected credit note, payment received but not matched, portal or customer process, internal action pending.

Each category must be clear.

It must indicate the expected action.

It must have a possible owner.

It must be reviewed regularly.

Qualification must help teams, not become an additional administrative burden.

A good category is a category that makes action possible.

Collections Comments

The quality of Collections comments is important.

A useful comment does not only say “customer chased.”

It says what happened and what must happen next.

For example: “Customer confirms invoice accepted, payment planned on 15/04.”

Or: “Invoice rejected by portal, purchase order number missing, Sales Administration must correct before Friday.”

Or: “Quality dispute on 12,000 euros, Operations must provide report, undisputed balance of 48,000 euros to be claimed.”

Or: “Payment received on 10/04, awaiting cash application matching.”

These comments create continuity.

They allow another person to take over the file. They facilitate escalations. They avoid asking the customer the same questions again.

Good Collections follow-up turns information into action.

Example: Two Invoices Overdue by 60 Days

Take two invoices overdue by 60 days.

The first concerns a customer whose payments have been deteriorating for several months. It no longer responds quickly, has missed two payment promises, requests a new major delivery and refuses to provide a firm date.

The invoice is overdue by 60 days because the customer seems to be in difficulty or is using the delay to preserve its cash.

The action must be strong: escalation, block or release under conditions, partial payment, limit review, possible formalized payment plan.

The second invoice concerns a reliable customer. Payment is blocked because the invoice was issued without the required purchase order number. The customer has confirmed that it will pay after correction and upload in the portal.

The invoice is overdue by 60 days because the company issued an unusable invoice.

The action must be internal: correct the invoice, upload it correctly, confirm its acceptance, then follow payment.

Same age. Same apparent delay. Two opposite realities.

Example: Old Delay but Low Risk

An invoice of 8,000 euros is overdue by 120 days.

At first sight, it seems concerning. But the analysis shows that it corresponds to a recognized price difference, with an approved credit note not yet issued. The customer has paid all other invoices on due date. The account is healthy.

The priority is not to block the customer.

The priority is to issue the credit note and clean the account.

Customer risk is low. The delay is old, but its cause is internal and identified.

This example shows why age must be interpreted.

An old invoice does not always mean a bad customer.

Example: Recent Delay but High Risk

A significant invoice of 250,000 euros is overdue by only 12 days.

The customer operates in a sector in crisis. Its credit insurance coverage has just been reduced. It requests a new order of 180,000 euros. It does not respond clearly to reminders and orally asks for additional time.

Even if the delay is recent, the risk is high.

Action must be taken quickly: escalation, suspension of new deliveries, request for partial payment, limit review, discussion with the salesperson, request for information from the customer.

This example shows that priority does not depend only on age.

A recent delay can be more dangerous than an old delay that is well explained.

Collections as Diagnosis

Collections is sometimes reduced to a reminder function.

This chapter invites us to see it differently.

Collections is a diagnosis function.

It looks for why cash is not arriving.

It identifies causes.

It directs actions.

It alerts the teams responsible.

It distinguishes the customer that cannot pay, the customer that does not want to pay on time, the invoice that cannot be processed, the dispute that must be resolved, the payment that must be matched.

This diagnostic ability is essential.

It makes Collections more intelligent, fairer and more effective.

In a Quote-to-Cash logic, Collections does not only start after due date. It extends the whole chain and reveals what worked well or badly before it.

Key Takeaways

Not all delays are the same.

The aged balance is a necessary tool because it shows open invoices, amounts, due dates and the age of delays. But it is not enough.

Two invoices overdue by 60 days can tell opposite stories: a customer in financial difficulty or an invoice blocked because of an internal error.

Delays must therefore be qualified instead of being treated only by age.

A delay may come from customer financial risk, slow payment behavior, a customer administrative process, a billing error, a missing purchase order, absent execution evidence, a real dispute, a tactical dispute, an expected credit note, an unmatched payment or a siloed organization.

Each cause requires a different action.

Chasing, correcting, providing evidence, matching, issuing a credit note, resolving a dispute, requesting partial payment, blocking an order or escalating are not interchangeable answers.

Good Collections starts with a simple question: why has this invoice not been paid?

Understanding before acting protects cash, the customer relationship and the quality of credit decisions.