When to Write Off, When to Place: A Decision Framework for Aging International Debt
Every credit controller eventually has to walk into a finance meeting and defend a number. Not the invoice amount — that part's easy to explain. The harder number is the one on the write-off line, and the question that follows it every single time is some version of "why didn't we place this sooner?" or, just as often, "why didn't we just write it off six months ago instead of paying an agency to chase it?" Both are fair questions. Both deserve an answer that isn't a shrug.
This is the framework for giving that answer before the meeting happens — a decision tree that turns "it felt like the right call" into something you can point to on a page.
The Four Inputs That Actually Matter
Most write-off-versus-pursue decisions get made on gut feeling, which is fine until someone asks you to defend the gut feeling in a meeting where the word "materiality" gets used unironically. A defensible decision runs on four inputs, evaluated together rather than one at a time: the age of the debt (collectability drops fastest in the first 90-120 days and flattens out from there — the same curve covered in our escalation matrix piece), the size of the exposure relative to what it would cost to pursue, the jurisdiction's cost-to-collect (a debtor in a slow, expensive-to-litigate market changes the math even when everything else looks identical), and the debtor's solvency signal — is this a cash-flow hiccup or a company quietly circling the drain. Any one of these in isolation gives you a hunch. All four together give you a decision.
The Decision Matrix
Here's how those four inputs typically resolve into an actual call. This isn't exhaustive — every book of receivables has edge cases — but it covers the large majority of accounts a credit controller sees in a given quarter.
Jurisdiction cost-to-collect shifts every row of this table — a debtor in a fast, low-cost-to-enforce market can justify legal escalation at a smaller balance than one in a slow, expensive jurisdiction.
The Workflow: Flag, Assess, Decide, Document
The matrix above is the logic. This is the process that gets you there on a schedule, rather than whenever someone happens to notice the account again.
A Word on Provisioning: Why Your Finance Team Cares About the Timing
Part of why this decision needs a paper trail isn't just internal hygiene — it connects directly to how the receivable is provisioned for on the balance sheet. Under the IFRS 9 expected credit loss model, a receivable isn't written down only at the moment it's formally written off; it's provisioned against earlier, based on the expected credit loss over its life, informed by exactly the kind of ageing and solvency signals this matrix already tracks. That's not a full accounting treatment — the mechanics of ECL modelling are their own subject, covered properly elsewhere on this site — but it's worth knowing the vocabulary, because "we're tracking this account under our ECL policy" lands very differently in a finance meeting than "we're keeping an eye on it."
The CFO's Raised Eyebrow
There's a specific look a CFO gives when someone proposes writing off a receivable and the answering question — "what did we do to try to collect it?" — gets a vague gesture instead of a timeline. Every credit controller has seen that look at least once, usually in a meeting they didn't fully prepare for. The fix isn't a better poker face. It's having the four inputs and the workflow already on paper before the meeting starts, so the answer to "what did we do" is a sentence instead of a scramble.
Why Writing Off Too Early Is Nearly as Costly as Writing Off Too Late
Most of the attention in credit control goes to the failure mode everyone recognises — letting a receivable age past the point of realistic recovery because nobody wanted to make the hard call. The quieter failure mode gets far less attention: writing off, or simply not pursuing, a receivable that was actually recoverable, because pursuing it felt like more trouble than the balance seemed worth. Both mistakes show up on the same line of the same report, and both cost the business real money — one through effort wasted chasing what was never coming back, the other through recovery abandoned that would have come back with a bit more effort. A framework that only guards against one of those failure modes is only half a framework. The matrix above is built to catch both directions, which is the actual point of having one at all.
Keeping the Matrix Honest Over Time
A decision matrix built once and never revisited slowly drifts out of sync with reality — jurisdiction cost-to-collect changes as court backlogs shift, agency fee structures change, and what counted as a "material balance" two years ago may not be material today. A quarterly review of the thresholds themselves, not just the accounts being run through them, keeps the framework doing its job rather than becoming a document people quietly stop trusting because it hasn't kept pace with the business. This review doesn't need to be elaborate — a short comparison of actual outcomes against matrix recommendations from the previous quarter is usually enough to spot when a threshold needs adjusting.
It's also worth tracking how often the matrix gets overridden, and why. A low override rate suggests the thresholds are well calibrated to how the team actually thinks about risk. A high one is a signal worth investigating — either the matrix needs recalibrating, or overrides are becoming the default way of avoiding an uncomfortable write-off conversation, which is exactly the failure mode a documented framework exists to prevent in the first place.
Frequently Asked Questions
When should a business write off bad debt instead of pursuing collection?
Write-off is generally the right call when the balance is small relative to the cost of further pursuit, the debt has aged past the point where internal or agency collection is likely to succeed, and no recoverable assets or solvency signal justify legal escalation. The decision should be documented with the reasoning, not made silently.
What factors go into a bad debt write-off decision?
Four inputs matter most: the age of the debt, the size of the exposure relative to cost-to-collect, the jurisdiction's cost and speed of enforcement, and the debtor's solvency signal. Evaluated together, they produce a defensible recommendation rather than a guess.
How does IFRS 9 expected credit loss relate to the write-off decision?
Under IFRS 9, receivables are provisioned for expected credit loss before formal write-off, based on ageing and risk signals similar to those used in a write-off-versus-pursue decision. Documenting the collection decision process supports and aligns with that provisioning.
Is it better to write off a bad debt early or keep trying to collect it?
Neither extreme is correct as a default. Writing off too early abandons genuinely recoverable balances; pursuing too long past the point of realistic recovery wastes cost on collection that was never coming back. A four-input decision matrix, applied consistently, is designed to avoid both.
When should an aging receivable be escalated to legal action instead of an agency?
Legal escalation is usually justified when the balance is large enough to absorb litigation cost, the debtor shows clear solvency distress, and recoverable assets have been identified. Without identifiable assets, legal action often costs more than it recovers.
Why does a write-off decision need to be documented?
A documented decision creates the audit trail finance and leadership expect — showing what was assessed, what action was taken, and why — and supports the expected credit loss provisioning process rather than leaving write-offs looking arbitrary after the fact.
The account doesn't care whether the decision took five minutes or five months — it only cares whether the decision got made and written down. Contact Cosmopolite for a free case assessment. No recovery, no fee.
