Bad Debt Write-Off

A customer with a $78,000 AR balance went silent six months ago. Every attempt at contact failed. Finance has kept the balance on the books as a receivable, even though the chance of collecting it is close to zero. The CFO asked why it hadn't been written off. The answer: nobody wanted to start the write-off process, and there was no policy for when that decision gets made. So the balance sat there, overstating AR and assets and skewing the bad debt reserve calculation. A bad debt write-off is the accounting action of removing an uncollectible receivable from the balance sheet. When a company concludes that a specific customer balance can't be collected (after exhausting collections efforts, after a customer bankruptcy, or after documented failure to locate the debtor), it removes the receivable from AR and records the loss as an expense. Writing off a balance doesn't mean the company stops trying to collect. It means the balance sheet stops pretending collection is likely. The accounting question of when and how to write off is governed by GAAP, which requires companies to recognize credit losses when they are probable and estimable, not only when they are certain. That requirement is why the bad debt reserve (the allowance for doubtful accounts) is the standard mechanism: it lets companies estimate probable losses on current receivables before individual balances are confirmed uncollectible, instead of waiting for certainty.

How bad debt write-offs work

Under GAAP, companies must use the allowance method for bad debt, also called the allowance for doubtful accounts or bad debt reserve. Each reporting period, the company estimates how much of its outstanding AR is unlikely to be collected, based on aging analysis, customer-specific risk, and historical collection rates. That estimate is recorded as an increase to the allowance for doubtful accounts (a credit on the balance sheet that offsets gross AR to show net realizable AR) and an increase to bad debt expense (a debit on the income statement). The reserve entry doesn't remove any specific receivable. It reduces net AR and recognizes the estimated loss in the period the risk becomes apparent, not when the collection failure is confirmed. When a specific customer balance is later judged definitively uncollectible, the actual write-off happens: the invoice amount is removed from gross AR (a credit) and the allowance is reduced by the same amount (a debit). If the allowance was sized properly, the income statement isn't affected at write-off, because the expense was recognized when the reserve was set up. The write-off only hits the income statement directly under the direct write-off method, which expenses a receivable only once it is confirmed uncollectible and keeps no reserve. The direct write-off method is not GAAP-compliant for companies with significant credit sales because it mismatches revenue recognition (earlier period) with expense recognition (the later period when the write-off happens). It is only allowed where bad debt amounts are immaterial.

When the allowance method requires judgment

Setting the bad debt reserve takes judgment, and that judgment is tested most visibly when the reserve turns out to be too small. The standard approach is aging-based estimation: work out historical collection rates by aging bucket and apply them to the current AR aging. If 5% of balances in the 61 to 90 day bucket and 20% of balances in the 90+ day bucket have historically gone uncollected, set the reserve accordingly. Customer-specific information supplements the statistics. A customer known to be in financial distress, in bankruptcy proceedings, or with a history of disputes may need a specific reserve against the full balance regardless of aging bucket. The timing of write-offs, when a specific balance moves from reserved to written off, should follow a documented policy. Common triggers: all reasonable collection efforts have been exhausted and documented, the customer has filed for bankruptcy and the receivable is listed as a claim, the customer is unreachable and a defined time threshold has passed, or continued collection would cost more than the expected recovery. Without a policy, write-off decisions are made inconsistently or not at all, and AR carries balances that serve no economic purpose. When a written-off receivable is later collected (a customer recovers financially and pays, or a bankruptcy estate distributes a partial payment), the accounting reverses the write-off and records the collection. The recovery is recorded as an increase to the allowance (reversing the original write-off) and then as a cash receipt against AR. The recovery appears as a credit to bad debt expense (or a separate recovery account) in the period it is received.

How platforms handle it

The accounting difference between a bad debt write-off and a credit memo determines how each should be handled in the system. A credit memo reduces AR and reduces revenue (or records a returns-and-allowances expense). It acknowledges a legitimate adjustment to what the customer owed. A bad debt write-off reduces AR and reduces the allowance for doubtful accounts. It acknowledges that the full amount was legitimately owed but won't be collected. The GL entries differ, the income statement impact differs (credit memos reduce revenue; write-offs draw down a reserve with no direct income statement impact if the reserve was set correctly), and so does the purpose. AR platforms that blur the two, or route write-offs through the credit memo workflow, create errors that distort both revenue and the bad debt reserve. What to check in a platform evaluation: is there a dedicated write-off workflow with the correct GL posting (debit allowance, credit AR), separate from the credit memo workflow? Does a write-off require approval, documented collection efforts, and a policy trigger, or can anyone start one without controls? Does the platform track write-offs at the invoice level so a recovery can be matched to the specific written-off balance? Does the system stop dunning and other collections outreach once a balance has been written off and removed from AR?

Questions to ask

• Is the bad debt reserve calculated using aging-based historical collection rates, or a flat percentage of total AR?
• Is there a documented write-off policy with defined triggers, such as aging thresholds, documented collection attempts, or a bankruptcy filing?
• Who has approval authority for write-offs, and is there a system-enforced approval workflow?
• Is the write-off GL entry posting to the allowance account (not expensing directly), and is this separate from the credit memo workflow?
• How is the bad debt reserve reviewed and adjusted at each period-end relative to the actual aging composition?
• Is there a process for recognizing recoveries on previously written-off balances, and does the platform support the reversal accounting?

Common mistakes

The most common bad debt accounting mistake is delaying write-offs past the point where the reserve can absorb them cleanly. When a balance that should have been reserved against in Q2 is written off in Q4 without an adequate reserve, the write-off hits the income statement directly as a current-period expense instead of drawing down an existing reserve. The result is a large, unexpected expense in the write-off period that proper reserve accounting would have spread across earlier periods. The second mistake is treating write-offs as admissions of failure instead of routine accounting hygiene. When the organization is reluctant to write off balances, whether from concern about the signal it sends or simple unwillingness to start the process, AR fills up with stale balances that overstate assets and distort the aging used to estimate the reserve. A write-off policy with clear triggers, regular review, and a simple approval process turns what feels like an exceptional decision into a routine, predictable procedure.

Comparing AR automation

AR tools separate on remittance handling, because a payment with no readable remittance advice becomes manual work no matching engine removes. Once bad debt write-off is settled as a requirement, read the AR Automation Software category guide for how the market splits, then weigh the HighRadius profile against the Versapay profile on that requirement rather than on the feature list. Our HighRadius pricing breakdown records what the vendor publishes and what is quote-based. The HighRadius against Versapay comparison sets two of them side by side on the same criteria. Before you book demos, put your own numbers through the AR automation cash flow calculator so the business case is written down before a vendor writes it for you.

Bad Debt Write-Off questions

Related terms

Accounts Receivable, AR Aging Report, and Cash Application come up in the same workflow as bad debt write-off, and the rest of the AR automation cluster is indexed in the finance operations glossary.