# Customer Deductions and Short Pays: A Resolution Workflow

> Separate the cash from the claim on every short payment, gather evidence by deduction reason, and record each outcome correctly in NetSuite, SAP, and Sage.

- Canonical page: https://procindex.com/blog/customer-deductions-short-pays
- Author: ProcIndex Editorial Team
- Published: 2026-02-10
- Updated: 2026-11-10
- Topics: deductions, short-payments, accounts-receivable, collections

The bank shows $950 against a $1,000 invoice. The remittance says the $50 is for damaged goods. AR can apply the $950 in a minute. Nobody in AR can say whether the goods were actually damaged. If the $50 does not get an owner today, it will sit in aging until someone writes it off to close the month.

Unowned claims like this lose money without anyone ever deciding to give it away. This guide sets out a workflow that keeps the cash and the claim apart, gathers the right evidence for each kind of deduction, and records the outcome so you can tell recovery from write-off.

## Apply the cash, then open the claim

A short payment is two events. The receipt is a cash application task. The withheld amount is a claim against an identified invoice. Handle them separately.

1. Apply the amount the remittance supports to the invoice it names.
2. Open a claim record for the difference with the customer's reason, the invoice, the remittance, and the debit memo if there is one.
3. Assign an owner who can actually check the facts (shipping, pricing, sales operations) and a response date.
4. Keep the open balance visible in aging, tagged as disputed so collections does not chase it as ordinary late payment.

If you cannot identify which invoice the payment covers, that is a matching problem, not a deduction. Leave the receipt in the unapplied queue until someone confirms where it belongs. See the [unapplied cash guide](https://procindex.com/blog/unapplied-cash-remittances).

## Gather evidence by deduction reason

| Customer's reason | What to check | Who can confirm |
| --- | --- | --- |
| Short shipment | Order, packing list, shipment record, proof of delivery, customer's receiving count | Shipping or warehouse |
| Damaged goods | Delivery exception, inspection evidence, return authorization, credits already issued | Customer service or quality |
| Price difference | Billed unit price, order, approved quote, contract or price amendment and its effective date | Sales or pricing |
| Promotional allowance or rebate | Program terms, eligible products and dates, prior credits for the same sales | Sales operations or commercial finance |
| Freight charge | Invoice line, shipment reference, agreed freight terms | Logistics or the account owner |
| No reason given | Receipt, invoice, amount withheld | AR asks the customer for the claim detail |

Before approving anything, look for an existing credit. Customers sometimes cite an allowance you already credited, or send the same debit memo twice. Record the debit memo number and check whether another receipt or credit already references it. A second copy of a claim should lead the reviewer to the first record, not create a second credit.

Manufacturers face a wider set of claim types (warranty chargebacks, OTIF penalties, billbacks). Those are covered in the [manufacturing chargebacks guide](https://procindex.com/blog/manufacturing-chargebacks-claims).

## Record one of four outcomes

"Closed" is not an outcome. Every claim should end in one of these states, and your reporting should keep them apart.

| Outcome | What it means | Typical entry (illustrative) |
| --- | --- | --- |
| Recovered | Customer paid the withheld amount after the dispute | Debit cash, credit receivables |
| Credited | Claim approved on the evidence; you issue a credit | Debit a returns, allowances, or deductions account; credit receivables |
| Written off | Authorized decision to stop pursuing it | Debit a deduction write-off or bad debt account; credit receivables |
| Still open | Has an owner, evidence request, and next action date | No entry yet |

Which accounts you use is a chart-of-accounts and revenue policy question. Pricing and promotional credits often reduce revenue rather than hitting expense; confirm treatment with your controller or auditors.

Microsoft's Dynamics 365 deduction workbench documents matching a deduction to a credit, splitting it, denying it, and writing it off as separate actions, because each has different accounting and collection effects. [Microsoft's deduction workbench guide](https://learn.microsoft.com/en-us/dynamics365/supply-chain/rebate-management/deduction-workbench). Check how your own system distinguishes them before you report a closure rate.

### Worked example: a split claim (illustrative)

A retailer withholds $2,400 from a $20,000 payment and attaches a debit memo citing a promotional allowance and a shortage.

- Sales operations confirms the promotion: $1,500 is supported by the program terms and has not been credited before.
- Shipping finds proof of delivery for the full quantity on the line the retailer says was short: the $900 shortage is unsupported.
- Check: $1,500 + $900 = $2,400.

Issue a $1,500 credit and apply it to the invoice. Keep $900 open, and send the retailer the proof of delivery with a request for payment. The invoice should now show $900 due, tagged as a disputed balance with a response date. If the retailer later pays, record a $900 recovery; if your policy authorizes closing it, record a $900 write-off. Do not let the $900 disappear into the $1,500 credit.

## How this works in NetSuite, Sage Intacct, SAP, and Sage 100

| ERP | Behaviour the sources document | What to watch |
| --- | --- | --- |
| NetSuite | Open credit memos can be applied on the Customer Payment page alongside payments; Auto Apply can target the oldest amounts due. [Credit memos](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N1312521.html) · [Customer Payment](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N1288824.html) | A credit meant for a specific invoice landing on the oldest one instead |
| Sage Intacct | A debit memo adjustment increases the balance due; a credit memo adjustment decreases it. At the top level of a multi-entity, multi-currency company, an adjustment needs a base currency and location. [AR adjustments](https://www.intacct.com/ia/docs/en_US/help_action/Accounts_Receivable/Adjustments/ar-adjustments-overview.htm) | Adjustments created in the wrong entity or currency |
| SAP S/4HANA Cloud | A partial payment leaves the original invoice and payment open; a residual item clears both and creates a new open item linked to the invoice. Dispute cases are available for both when Dispute Management is installed. [SAP](https://help.sap.com/docs/SAP_S4HANA_CLOUD/918bca53037f408f91a2295d04ac16bc/279bad94d6414e05aab0cacf42eb3803.html?locale=en-US) | Collectors seeing different open items for the same $50 net balance |
| Sage 100 | In Cash Receipts Entry, Amount Posted reduces the invoice balance by the amount entered, and the default can be the full invoice balance when enough money remains on the receipt. [Field reference](https://help-sage100.na.sage.com/2019/Subsystems/AR/ARMainFields/Cash_Receipts_Entry_-_Fields.htm) | On a check covering several invoices, the default paying one in full and leaving the short pay on the wrong invoice |

In SAP, ask the controller which method (partial payment or residual item) applies to which scenario. In the $950 example, both leave a net $50, but a collector working from the residual item needs its link back to the original invoice, or a cleared invoice can make an unresolved deduction vanish from follow-up.

## Run a weekly review from the claims register

The register should hold the original deduction, customer, reason code, invoice, owner, due date, and amount still open. Each week:

- Group open claims by customer and reason. Repeated shortages go to shipping; recurring price claims go to sales; credits that were approved but never applied go to cash application.
- Pick the largest repeatable cause your team can act on, and check whether it recurs on the next batch of invoices. A string of freight deductions from one customer is worth checking against the freight terms on their customer record before you blame the customer.
- Review small deductions too. Policy may let AR clear amounts under a threshold without investigation, but a customer taking $40 on every invoice is a pattern worth a phone call.
- Compare outcomes, not just backlog. A shrinking backlog can hide rising write-offs.

Track time to apply the cash separately from time to decide the claim. A fast posting says nothing about how long the customer waited for an answer.

## What goes wrong

- **The default allocation hides the short pay.** The ERP pays the first invoice in full and leaves the shortfall on the wrong one.
- **Duplicate credits.** A claim is credited, then the customer deducts it again on the next payment.
- **Denied claims with no follow-up.** The decision is made but collections never gets the evidence to request payment.
- **Write-off as the default closure.** The month-end push clears old claims without anyone authorizing the decision.

## Test before you automate

In a sandbox, run a check paying several invoices with one short pay, a payment with no usable reference, a debit memo that arrives twice, and a split claim like the example above. Tie the deposit to the receipts batch, then open customer aging and confirm the disputed amount sits on the intended invoice. Those two checks catch different errors. If you use SAP, run one short payment as a partial payment and one as a residual item and compare what the customer sees on a statement.

## Deduction handling checklist

- [ ] Cash applied to the invoice the remittance names; difference opened as a claim the same day.
- [ ] Claim has reason, owner, evidence request, and response date.
- [ ] Existing credits and earlier copies of the debit memo checked first.
- [ ] Partial approvals split into credited and still-open amounts.
- [ ] Outcome recorded as recovered, credited, written off, or open.
- [ ] Write-offs approved by someone with authority, not cleared to close the batch.
- [ ] Weekly review by customer and reason, with one root cause assigned.

Related: the [collections aging review](https://procindex.com/blog/collections-aging-review) shows how disputed balances should appear on the call list, and the [cash application guide](https://procindex.com/blog/cash-application-automation) covers the matching side.

## Sources

- https://learn.microsoft.com/en-us/dynamics365/supply-chain/rebate-management/deduction-workbench
- https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N1312521.html
- https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_N1288824.html
- https://www.intacct.com/ia/docs/en_US/help_action/Accounts_Receivable/Adjustments/ar-adjustments-overview.htm
- https://help.sap.com/docs/SAP_S4HANA_CLOUD/918bca53037f408f91a2295d04ac16bc/279bad94d6414e05aab0cacf42eb3803.html?locale=en-US
- https://help-sage100.na.sage.com/2019/Subsystems/AR/ARMainFields/Cash_Receipts_Entry_-_Fields.htm

---

Published by ProcIndex, which builds AI accounting agents for construction and manufacturing finance teams. ProcIndex currently connects to NetSuite, Sage Intacct, and QuickBooks. Worked examples in this guide are illustrative, not customer results.