Revenue and reconciliation
What Is a Chargeback or Customer Deduction?
Direct answer
A chargeback or customer deduction is an amount a payer, marketplace or retailer removes from money otherwise expected by a supplier. It may represent a card-payment dispute, return, pricing claim, shortage, promotion, service penalty or unsupported short payment. Finance teams reconcile it to the original transaction, validate the governing evidence, dispute or accept it, and record the final outcome without hiding open exposure.
Also known as: customer deduction, short payment claim, trade chargeback.
Key takeaways
- Cardholder chargebacks and retailer trade deductions are different processes even though both reduce expected cash.
- A deduction code is the payer's claim, not proof that the amount is contractually valid or correctly calculated.
- Evidence should connect the claim to the order, invoice, delivery, return, contract, communication and settlement line.
- Accepted claims, disputed claims and cash received must remain separate so one cannot mask another.
- The workflow below is operational practice; card rules, commercial contracts, GST and accounting policies govern specific outcomes.
Chargeback versus commercial deduction
Operational-practice note: businesses use “chargeback” in more than one way. In card payments, a cardholder dispute can move through an issuer, network, acquirer and merchant under applicable rules. In B2B and retail supply chains, a customer may call a shortage, price claim, compliance fee or service-level penalty a chargeback even when no card transaction exists. A marketplace can also net a claim from a seller payout.
RBI’s current Credit Card and Debit Card Directions regulate card issuers and include billing, protest and documentary-evidence requirements for the cardholder relationship. They do not prescribe the B2B deduction taxonomy or dispute workflow in this article. Those are operational controls derived from contracts, channel practices and accounting needs.
A deduction begins as an assertion by the payer. The supplier must decide whether it is valid, duplicated, misclassified, outside the contractual window, calculated on the wrong base or unsupported. “Accepted” means the review concluded that the supplier bears the amount; “disputed” means recovery remains sought. Neither label should be inferred from the payer's settlement code. A cash shortfall can also be unidentified rather than a claim, especially when remittance detail is missing.
Operational claim taxonomy
| Claim family | Typical assertion | Minimum review |
|---|---|---|
| Price and promotion | Invoice price exceeded the purchase order, or supplier-funded campaign support was not credited. | Effective price list, purchase order, promotion agreement, eligible units and prior credits. |
| Quantity, shortage or damage | Customer says fewer usable units were received than invoiced. | Dispatch quantity, carrier hand-off, proof of delivery, goods receipt, inspection, photos and return record. |
| Return and cancellation | Goods were returned, rejected or cancelled after billing. | Return authorisation, item identity, receipt condition, original invoice and refund or note already issued. |
| Freight and logistics | Freight was incorrectly billed or delivery conditions were missed. | Incoterm or delivery term, route, carrier invoice, promised date and actual delivery event. |
| Service-level or compliance | Fill rate, labelling, appointment, packaging or data requirement was missed. | Contract clause, measurement period, source events, threshold, cure process and cap. |
| Fee, commission or reserve | Marketplace or distributor netted a fee, reserve or adjustment. | Effective commercial schedule, calculation base, settlement event and release rule. |
| Payment or card dispute | Payer denies authorisation, receipt, quality or amount of a payment transaction. | Order and authentication data, fulfilment, customer communication, refund history and submission deadline. |
| Tax or document claim | Payer alleges invoice, GST, withholding or supporting-document deficiency. | Tax invoice, registration and return data, contract, note history and qualified tax review. |
This taxonomy is not an RBI, GST or accounting classification. It is a practical way to assign evidence and owners. Preserve the payer’s original reason code alongside the internal family; collapsing both into “deduction” makes recurrence analysis and recovery difficult.
Evidence checklist before acceptance or dispute
- Original customer claim, portal record or settlement line with claim ID, amount, date and stated reason.
- Contract, purchase order and amendments effective for the underlying event, including dispute windows and calculation caps.
- Invoice and every related debit note, credit note, cancellation, refund or prior deduction to prevent duplicate relief.
- Order, SKU, quantity, price, discount, tax and legal-entity details at source.
- Dispatch, carrier scan, proof of delivery, customer goods receipt and inspection or shortage evidence.
- Return authorisation, returned quantity, receipt date, condition and disposition for return-based claims.
- Promotion brief, funding split, eligible dates, participating items and order-level calculation for promotional claims.
- Service-level definition, source events, denominator, exclusions and approval for penalty claims.
- Payment authentication, fulfilment, customer messages and refund history where a card-related dispute is involved.
- Settlement or remittance report and bank entry showing how and when cash was reduced.
- Owner conclusion separating fact, contract interpretation, tax treatment, accounting entry and collection action.
- Submission receipt, counterparty response, deadline and final resolution reference.
Evidence must be contemporaneous and connected. A delivery screenshot without the order identifier, or a current contract attached to a historical claim, can look persuasive while proving nothing. Keep source files immutable and record translations or manual mappings separately.
Deduction dispute lifecycle
- Detect and preserve. Import the deduction from remittance, settlement or portal data and retain the original reason, documents and response deadline.
- Prevent duplicates. Match on claim ID, invoice, amount and event; check whether an earlier note, refund or deduction already resolved the same issue.
- Classify and route. Assign the operational claim family, financial owner and business owner. Quarantine an unidentified short payment until the payer explains it.
- Validate facts. Reconcile quantities, prices, dates, fulfilment, returns and payment evidence. Recalculate the claim from source events rather than copying the payer’s total.
- Read the governing term. Check effective contract language, notice periods, materiality, cure rights, limits and tax requirements. Escalate ambiguity to qualified advisers or contract owners.
- Decide. Accept fully, accept partly, dispute, request more evidence or identify a timing item. Document the amount and rationale for each component.
- Submit and track. Send the counterparty’s required file format before the deadline, preserve receipt and monitor every response, re-presentment or escalation.
- Resolve cash and documents. Recover through a later payment, receive a reversal, issue an appropriate note where justified, or post an approved settlement. GST adjustments require the applicable Section 34 facts and documents; a commercial acceptance does not automatically permit tax reduction.
- Close the ledger. Clear only the resolved amount, link the final evidence and preserve any residual dispute. Analyse recurrence by customer, reason, SKU, location and root cause.
Do not close a dispute merely because the portal status changed to “completed.” Confirm the financial result in settlement and bank data and the corresponding ledger entry. A won claim that has not been repaid remains an open receivable or other item subject to the applicable accounting assessment.
Worked B2B customer deduction
Fictional B2B example: A packaged-food supplier invoices a supermarket chain ₹5,00,000 for an accepted delivery. The customer remits ₹4,50,000 and reports ₹50,000 of deductions: ₹30,000 for a documented supplier-funded launch promotion and ₹20,000 for an alleged short delivery. The supplier confirms the promotion against eligible units but its signed proof of delivery shows the full shipment, so the shortage remains disputed.
| Reconciliation component | Amount | Status |
|---|---|---|
| Customer invoice | ₹5,00,000 | Original receivable |
| Accepted promotion deduction | ₹30,000 | Supported, subject to approved accounting and tax document |
| Disputed shortage deduction | ₹20,000 | Recovery claim remains open |
| Cash received | ₹4,50,000 | Matched to bank and remittance |
The invoice reconciles exactly: ₹5,00,000 = ₹30,000 accepted + ₹20,000 disputed + ₹4,50,000 cash. The company does not net the ₹20,000 dispute into the accepted trade-spend account merely to clear the customer balance. It links delivery evidence, submits the claim and keeps the financial exposure visible until the customer reverses it or an authorised settlement is reached.
If the ₹30,000 acceptance requires a supplier GST credit note, the supplier separately tests Section 34 conditions, document particulars, return timing and tax-incidence restriction. A customer-created portal deduction is not by itself the supplier’s statutory credit note.
Accounting and tax outcomes
| Outcome | Operational treatment | Control risk |
|---|---|---|
| Counterparty reverses claim | Match the later settlement or payment to the original dispute and clear the recoverable amount. | Recognising recovery before it appears, or counting both reversal and payment. |
| Supplier accepts valid claim | Post to the approved return, discount, logistics, trade-spend or other account; issue required documents. | Using one deduction expense for every root cause and losing tax treatment. |
| Partial settlement | Allocate accepted, recovered and residual amounts explicitly. | Closing the entire claim because one component moved. |
| Timing difference | Track expected clearing event and verify the later settlement. | Allowing “timing” to become a permanent unexplained balance. |
| Unsupported and unrecovered | Continue collection or apply the approved credit-loss or write-off policy with authority. | Writing off to improve ageing without exhausting or documenting recovery. |
The accounting classification depends on why the amount arose, not what the customer called it. A return, contractual discount, service failure, bad debt and payment-processing fee can affect different accounts and taxes. Material or ambiguous items require accounting and tax review.
Preventing recurring deductions
Recovery addresses the symptom; root-cause control reduces repetition. Price claims point to contract or master-data governance. Shortage claims may reveal dispatch, proof-of-delivery or customer receiving gaps. Promotion claims often need order-level accruals and funding approvals. Service penalties need shared event definitions. Duplicate returns require links between logistics, credit notes and settlement files.
Measure gross claims, valid claims, disputed exposure, recovered value, age, recurrence and reason-code concentration separately. A high win rate can coexist with poor prevention if the same invalid customer claim returns every month. Conversely, a low dispute rate is not necessarily healthy if teams accept unsupported deductions to clear receivables quickly.
Frequently asked questions
Is every customer deduction a chargeback?
No. A card chargeback follows a payment-dispute process, while B2B or retailer deductions often arise from commercial claims. Preserve the original process and reason.
Should a deduction immediately reduce revenue?
Not automatically. The accounting depends on the underlying cause, evidence, contract and applicable policy. Keep disputed and accepted amounts separate until an authorised conclusion is reached.
What makes a deduction dispute-ready?
A connected evidence pack should prove the contract term, original transaction, fulfilment or return facts, calculation, prior adjustments and timely submission.
Can a customer deduction replace a GST credit note?
No. A commercial deduction does not itself satisfy the supplier’s Section 34 conditions or prescribed document requirements. The supplier must perform the separate GST analysis.
How are partial deductions reconciled?
Split the invoice into cash, accepted claim, disputed claim and any timing amount. Each component needs its own owner, ledger treatment and closing evidence.
When should a disputed deduction be written off?
Only under the approved credit-loss or write-off policy after documented recovery analysis and authorisation. Age alone should not silently convert a dispute into acceptance.
Does RBI prescribe this B2B dispute lifecycle?
No. RBI regulates relevant payment and card contexts; the B2B taxonomy and workflow here are operational practice shaped by contracts, accounting and tax requirements.
Sources and further reading
- Reserve Bank of India: Credit Card and Debit Card – Issuance and Conduct Directions, 2022Verified Jul 25, 2026
- Reserve Bank of India: Payment and Settlement Systems Act, 2007 FAQsVerified Jul 25, 2026
- India Code: Central Goods and Services Tax Act, 2017, Section 34Verified Jul 25, 2026
Educational disclaimer: This material is general information, not legal, tax, or accounting advice. Check current official guidance and your facts with a qualified professional.
From definition to workflow
Apply this concept with connected finance operations
Finnoto connects source records, approvals, reconciliation evidence, and exception ownership so teams can move from knowing the rule to operating the control.
Explore settlement reconciliation