Accounts Receivable Write-Off Approval Workflow

An overdue invoice is not automatically ready for a write-off. The customer may have paid into an unapplied-cash account, a billing dispute may still be open, or an old approval may name an amount that has since changed. Clearing the aging report without resolving those questions can hide a different problem.

An accounts receivable write-off approval workflow connects a specific invoice balance to collection evidence, delegated authority, accounting execution and a checked close. The process below is a recommended internal-control design for B2B finance teams, not a universal accounting rule. Your controller should determine accounting treatment under the applicable reporting framework; legal release of a debt and tax deductibility require separate decisions.

Separate a write-off from a correction or concession

A write-off removes an uncollectible receivable from the accounting records. Cornell’s receivables write-off guidance connects that decision to collection attempts, documented reasons and authorization. Its monetary limits are Cornell’s policy, not thresholds other businesses should adopt unchanged.

Before preparing a request, classify why the balance remains open:

• Cash exists but is unmatched: investigate the receipt and apply it to the correct customer and invoice through the cash application process. Do not call a matching problem bad debt.
• The invoice is wrong or a concession is approved: use the appropriate correction or customer credit memo workflow. Preserve the reason the billed amount changed.
• The customer disputes a short payment: resolve the claim through deduction management before assuming the residual is uncollectible.
• A valid debt appears uncollectible: prepare the evidence and write-off request under company policy. Small residual balances should use a separately defined policy route, not an informal shortcut.

Age is a review trigger, not proof of uncollectibility by itself. Keep allowance estimation, invoice correction and the disposition of a specific receivable distinct. Do not treat a write-off approval as permission to reduce revenue, forgive a contractual claim or stop every recovery action.

Build an invoice-level decision packet

The AR owner should assemble a dated packet before asking for authorization. Record the customer’s legal entity, internal account, invoice IDs, currency and proposed write-off amount. Include the policy version and authority route so a reviewer knows which decision they are making.

1. Prove the open balance. Attach the invoice and current subledger detail. Show original amount, applied receipts, posted credits, previous adjustments and the remaining balance, all at a stated timestamp.
2. Explain the collection position. Link dated contact attempts, broken promises, collection-agent updates or other relevant evidence. Identify unresolved disputes and the owner’s next recommendation. Do not invent a universal number of calls or days.
3. Check related records. Review unapplied receipts, pending credits, payment batches awaiting allocation and existing write-off cases for the same invoice. Explain any difference between the customer statement, collection record and ledger.
4. State the requested decision. Name exact invoices and amounts, reason, requested posting date, proposed accounting route for controller review, and whether recovery or legal follow-up remains active.
5. Assign execution and close. Identify an authorized approver, accounting poster and independent reviewer where practical. State what evidence will prove completion.

For a batch, retain invoice-level amounts and a batch total. Apply the company’s aggregation rules across related requests rather than splitting one exposure into smaller approvals. Separate currencies unless policy specifies the translation basis and authority calculation. Restricted legal or customer records should be accessible only to the people who need them.

Use a decision-and-close control matrix

Adapt the following matrix to your authority policy. Role names are suggested responsibilities, not legally mandated job titles. Each row has an exit condition; no one should infer that a request advanced merely because someone replied to an email.

Make approval narrow enough to remain valid

Define authority before the urgent case

Company policy should specify who can approve each reason and amount, how related requests aggregate, who substitutes for an absent approver, and which unusual cases need controller or legal review. Avoid self-approval by the requester; where a small team cannot fully separate duties, document a compensating review rather than pretending separation exists.

System limits and approval requirements are different controls. Oracle’s PeopleSoft write-off documentation distinguishes maximum permitted amounts from approval-needed limits and describes preventing posting while approval is pending. That is product-specific behavior, but the design question travels: does your process actually block an unapproved posting, or only record a request?

Specify what requires a fresh decision

Approve a named set of invoice balances, not “clear this customer.” Record conditions and a validity window appropriate to your operation. New cash, a credit, changed customer/entity, increased amount, revised classification or a different accounting period should trigger a comparison with the authorization. Obtain revised approval when the approved basis or scope changes; do not silently reuse an old signature.

An approval should also distinguish accounting disposition from recovery instructions. A ledger write-off is not itself evidence that an authorized person released the legal debt. Have the responsible legal or credit owner determine continuing collection, customer communication and any settlement terms.

Worked example: cash arrives before posting

Illustrative example, not a customer result or recommended threshold: an invoice originally totaled $12,000. A verified $3,000 receipt has been applied, leaving $9,000. AR proposes writing off that $9,000 after documenting the company-policy collection review. The designated approver authorizes those invoice details and that exact amount.

Before accounting posts, another $2,000 arrives and is verified and applied to the same invoice. The current open balance is now $12,000 − $3,000 − $2,000 = $7,000. Posting the old $9,000 request would not match the receivable that remains.

1. Keep the case at the pre-posting gate. Link the new receipt and refreshed $7,000 invoice detail to the original request.
2. Mark the $9,000 authorization superseded; retain it as evidence rather than overwriting the decision history.
3. Ask the proper approver to decide on the revised $7,000, including whether the new payment changes the collectibility assessment.
4. If approved, accounting posts only the revised amount using the controller-approved treatment and captures the transaction/application references.
5. The reviewer confirms the invoice is zero after $5,000 of applied cash and the $7,000 write-off, with no duplicated adjustment or unexplained customer credit.

If the $2,000 is only promised, do not label it applied cash. If it has arrived but is unmatched, investigate allocation and obtain the appropriate decision before posting. A changed amount is not the only risk: new evidence can change whether a write-off is justified at all.

Prove accounting execution before closing the request

The controller should specify the posting treatment, relevant allowance or expense accounts, and period handling under the applicable accounting policy. This workflow does not prescribe a universal journal entry. Ask the operator to link the posted transaction to the specific customer and invoices, not merely show that a journal balances.

Close review should compare the authorized amount with the posted amount, inspect invoice-level AR after application, and reconcile the relevant ledger movement. A batch total can agree while one invoice is missed and another adjusted twice. Keep the row-level check.

• Posting failed: capture the error, owner and corrective action. A changed date, account or amount may require renewed approval.
• Posting outcome uncertain: search the accounting record using the case and transaction references before resubmitting. Do not create a second adjustment to escape an unknown result.
• Invoice remains open: investigate application and posting differences; do not close the workflow on a successful journal message alone.
• Period is closed: obtain controller direction through the approved period process. Do not backdate simply to match the request.

Handle subsequent receipts without losing the history

Keep a searchable link between the written-off invoice, original decision and any continuing recovery record. If money arrives later, route it to accounting to identify the customer, invoice and required recovery treatment. Do not automatically apply it as ordinary cash against a receivable that no longer exists or erase the original write-off.

The University System of New Hampshire’s uncollectible-receivables procedure includes reporting of payments on certain written-off accounts and reversal when appropriate. Its particular reporting and accounting rules belong to that institution; the general operating lesson is to assign a recovery path before closing the original case.

On a regular policy-defined cadence, review requested, rejected, posted, unreconciled and recovered amounts separately. Investigate repeat requests on the same invoices, batches split around approval limits and cases closed without posting references. Report operational exceptions without inventing a savings target or treating a lower write-off total as proof of better decisions.

Where Workhint fits

Workhint’s Workflow Engine describes approval routing to defined roles and requiring details, files or notes before work advances. Those capabilities are relevant to collecting a write-off request packet and routing a documented decision.

The Workflow Automation Software solution describes structured forms, assigned review stages and tracking of approvals, owners and next actions. A finance team can evaluate those configurable components for the request-to-review and exception handoffs described here.

These pages do not establish a native AR write-off module, automatic ERP posting, accounting-policy calculation or legal debt release. Keep accounting execution and reconciliation in the authorized record system, and validate any integration separately. A workflow status should identify the evidence of posting, not substitute for it.

Frequently asked questions

Can finance write off every invoice over a fixed age?

Age can select cases for review, but it does not resolve unmatched cash, disputes or policy requirements. Validate the balance and evidence before seeking approval. Use the company’s documented criteria rather than copying another organization’s timing.

Is a write-off the same as a customer credit memo?

No. Billing corrections and commercial concessions explain why the billed amount changed. A write-off addresses an uncollectible receivable. Classify the underlying reason and let accounting determine the correct transaction rather than using whichever button clears the aging.

Does approval mean the workflow is finished?

No. Approval authorizes the specified action. Completion also requires checked posting, invoice-level application, reconciliation and an owner for remaining recovery or exceptions.

What if payment arrives after approval?

Refresh the receipt and invoice records before posting. If the balance or decision basis changed, preserve the old approval and obtain the revised authorization required by policy. After posting, route later receipts through the defined recovery process.