Bad debt describes a customer receivable the business does not expect to recover. An allowance for doubtful receivables recognizes expected loss while the underlying open item can still exist. A write-off addresses an amount considered uncollectible through an authorized accounting process. In SAP FI, the posting and clearing mechanics depend on the solution edition, company accounting policy, tax rules and configured accounts.
Three decisions that should not be confused
First, the collections team decides how to pursue a late payer. Second, Finance estimates whether the receivable is impaired or doubtful at a reporting date. Third, once collection is no longer realistically expected and the relevant policy criteria are met, authorized users may write off the balance. These decisions use related evidence but are not interchangeable: a late invoice is not automatically irrecoverable, and a provision is not proof that an invoice has been legally extinguished.
How a write-off differs from clearing by payment
Ordinary customer clearing is supported by settlement evidence such as received funds or an agreed credit. Writing off an uncollectible amount recognizes that the receivable will not be realized; it should not be presented as the customer having paid. Depending on configuration, the write-off may clear the item and post to a defined expense or adjustment account. Teams must verify the actual posting design and document type in their SAP environment instead of assuming a single universal transaction.
A practical customer example
A distributor holds an invoice for ₹80,000. After repeated documented collections efforts, the customer disputes ₹10,000 and enters insolvency proceedings. The company may assess an allowance for the unrecoverable estimate while investigation continues. If the approved final decision is to write off a specific amount, the team should link the authorization to the affected open items, the accounting treatment, applicable tax handling, and any later recovery process.
The control handoffs
Collections gathers payment promises and dispute history. Customer service resolves commercial claims. The credit function monitors exposure and limits, but does not independently dictate the financial posting. The financial controller confirms materiality, accounting classification and authorization, while tax and audit stakeholders examine any recovery, impairment or indirect-tax implications.
An approved write-off needs a stated reason, evidence of attempted recovery where policy requires it, correct company code and customer, segregation of duties, posting traceability and a plan for later recoveries. Authorizations and thresholds should be designed against the company's own risk policy.
Five checks before posting
Confirm the open amount and any unapplied receipts; check whether a valid credit memo or dispute correction is actually required; separate allowance accounting from the final write-off; establish the correct tax treatment for the jurisdiction; and confirm the posting account, approver and audit trail. A write-off should not be used to hide a data-quality, billing or cash-application defect.
Questions a consultant should ask
Which business events trigger an allowance assessment? Which role authorizes an individual versus a mass write-off? How do reason codes, account determination, dunning blocks and customer correspondence interact? What evidence appears in reporting after a write-off and what process handles a later receipt? Test the designed behavior with realistic customer items and reversals rather than relying only on a successful accounting document.
Related concepts
Read about disputes and deductions, customer account clearing, credit management and receivables, and the SAP FI / FICO hub for the surrounding process.
Official SAP References
SAP Help — Writing Off Doubtful Receivables