Customer deductions and adjustments: how the process runs, step by step

A deduction starts when a customer pays less than the invoice says. Cash application spots the gap and opens a case. An analyst researches it, internal owners weigh in, and the customer is engaged. A credit, a chargeback or a write off follows. Accounting then posts the entries and reconciles them.

The steps in order

1. Set the rules. The credit manager and the controller agree on which deduction types the business will accept, what proof each one needs and who can approve a credit or a write off. These rules sit in a written procedure and a reason code list. Sales and supply chain should sign off, because they generate most of the valid claims.

1. Catch the short payment. When a remittance arrives, the cash application clerk matches it to open invoices. Any unexplained difference is split off from the invoice and logged as a deduction case with a reason code taken from the customer's remittance advice. The original invoice is then closed against the cash actually received.

1. Research the claim. A deduction analyst pulls the supporting evidence. Typical sources include proof of delivery, the pricing agreement, promotion contracts, return authorizations and carrier claims. The analyst decides whether the claim looks valid, invalid or unclear.

1. Bring in the internal owners. Few deductions can be settled by finance alone. Sales confirms whether a promotion was actually agreed. Logistics checks shortage and damage claims against shipping records. Customer service may know about a pricing promise that never reached the contract file. The analyst records each answer on the case.

1. Engage the customer. For unclear or invalid items, the analyst or a collector writes to the customer's accounts payable team or uses the customer's dispute portal. They ask for backup, explain why a claim is being rejected and negotiate a settlement where both sides have a point. Larger retailers often have strict windows for disputes, so this step cannot wait.

1. Get a decision approved. Once the facts are in, the case goes to whoever holds authority under the policy. That is usually the credit manager for routine items and the controller for anything unusual. Approval results in a credit memo, a rejection or a write off.

1. Rebill what is owed. If a claim is rejected and the customer agrees to pay, or if policy calls for it, an accounts receivable specialist raises a chargeback invoice. It references the original invoice and the deduction case so the customer's payables team can trace it.

1. Post the entries. The revenue accountant books the outcome. Valid trade claims hit the trade spend or sales allowance accounts. Shortages and damages may go to freight recovery or cost of sales. Write offs clear against the bad debt or deduction reserve. Any manual journal is prepared, routed for approval and posted to the general ledger.

1. Reconcile at close. At each period end the revenue accountant ties the open deduction subledger to the ledger balance. The reserve for unresolved deductions is reviewed and adjusted. Supporting files are kept for auditors, who often sample closed cases.

1. Feed back the causes. The credit manager reviews which reason codes keep recurring and takes the patterns to sales, pricing and logistics. Policy and reason codes get updated when the business changes how it sells or ships.

Where the handoffs tend to fail

The gap between step 2 and step 3 is the most common weak point. Cash application is measured on clearing cash quickly, so cases can be opened with vague reason codes and little context. The analyst then spends time reconstructing what the customer meant.

Step 4 depends on people outside finance answering promptly. When sales owns promotion approvals but has no stake in deduction recovery, cases sit waiting.

The link between step 6 and step 8 also breaks quietly. Approvals sometimes happen by email while the credit memo is raised later by someone else, and the ledger coding drifts from what was approved.

Questions to ask the people who run it

What gets documented and what people actually do often differ. These questions surface the difference.

• When a remittance shows a deduction with no reason, what does the cash application clerk actually do with it?
• Which deduction types are approved without research, and who decided that?
• How does the analyst find out a promotion was agreed? Is there a system record, or does it depend on asking a sales rep?
• Who decides to stop disputing a claim, and is that decision written down anywhere?
• Are chargeback invoices ever raised and then quietly credited later? Why?
• Do customers dispute through portals, email or both? Who monitors each channel?
• Which accounts do small write offs really land in, and does that match the policy?
• At close, does the subledger tie to the ledger without manual plugs? If not, who makes the plug and how is it explained?
• When a reason code is missing from the list, what code do people pick instead?
• What workarounds would break if the process changed tomorrow?

Who owns what

The credit manager owns the policy and the decisions on routine cases. Cash application owns identification. Deduction analysts own research and customer contact. Sales, logistics and customer service own the facts about their part of the transaction. The revenue accountant owns the entries and the reconciliation, and the controller owns exceptions and the reserve.

APQC's Process Classification Framework® (PCF) is an open standard developed by APQC, a nonprofit that promotes benchmarking and best practices worldwide. To download the full PCF or to view definitions and measures, please visit www.apqc.org/pcf.