What is a chargeback?

A chargeback is a forced reversal of a payment you already received, triggered by the customer or their bank rather than agreed to by you. In a card setting, the buyer's bank pulls the funds back and asks you to prove the charge was legitimate. In B2B accounts receivable, the same idea shows up as a deduction: a customer pays less than the invoice and applies the difference against a claim they say you owe, such as a pricing error, a shortage, or a promotion.

Either way, cash you counted as collected leaves your account, and the burden is on you to show the charge was valid. That makes chargebacks both a cash-flow problem and a documentation problem. The ones you can disprove are recoverable revenue. The ones you cannot are write-offs waiting to happen.

How chargebacks work

A chargeback runs through a predictable sequence, whether it starts at a bank or a buyer's AP team.

1. A claim is raised. The customer disputes the charge or deducts from a payment, citing a reason like a return, a billing error, or goods not received.
2. The funds are reversed. In card networks the issuer debits your account immediately. In B2B the customer simply remits short, so the open balance reappears on your aging.
3. You investigate. You match the claim back to the original order, contract, and delivery record to see whether it holds up.
4. You respond with evidence. If the claim is invalid, you submit proof and bill the customer back for the difference. If it is valid, you clear it with a credit memo.
5. The case closes. The money stays reversed, comes back to you, or splits, depending on whose documentation wins.

The trap is step three. A deduction that nobody codes and investigates quietly ages into a permanent loss, because the window to dispute it closes and the buyer moves on.

Chargeback vs refund vs deduction

These three get mixed up, but they differ on who decides and how the money moves.

• Refund: You agree the customer is owed money and return it on purpose. You control the timing and the amount.
• Chargeback: The reversal is forced on you, usually by a bank in a card transaction, often before you can weigh in. You recover it only by disputing.
• Deduction: The B2B cousin of a chargeback. The customer pays the invoice short and applies the gap to a claim. No bank is involved, but the effect is the same: cash withheld until someone proves who is right.

For most B2B finance teams, the day-to-day version of a chargeback is the deduction, which is why disciplined deductions management decides how much of this revenue you keep.

Common chargeback reasons

Most chargebacks and deductions cluster into a handful of root causes:

• Pricing discrepancies. The customer was billed at a rate different from the one on the contract or purchase order.
• Shortages and damages. Fewer units arrived than ordered, or some arrived unusable.
• Trade promotions and allowances. The buyer deducts an agreed rebate, co-op, or discount, sometimes correctly, sometimes twice.
• Returns. Product was sent back and the customer takes the credit before you process it.
• Compliance and freight charges. Retailers in particular charge back for late shipments, wrong labeling, or routing errors.
• Duplicate or disputed billing. The customer believes they already paid or were billed for something they did not receive.

A pattern in the reasons tells you where to fix the upstream process. Repeated pricing chargebacks point to a contract sync problem, not a collections problem.

How to manage and dispute chargebacks

Recovering cash comes down to acting before the window closes and proving the charge was valid. A workable approach:

1. Code every claim by reason. You cannot prioritize or fix what you have not categorized. Tag each deduction with its root cause the moment it lands.
2. Validate against the source. Pull the contract, purchase order, proof of delivery, and pricing. The claim either matches the agreement or it does not.
3. Recover the invalid ones. Where the customer has no basis, bill them back promptly with the supporting documentation attached, before the deduction ages out.
4. Clear the valid ones cleanly. Issue a credit memo so the balance reconciles and stops cluttering the aging.
5. Watch the deadlines. Card networks and many trading agreements set hard windows to dispute. Miss them and a recoverable charge becomes a loss by default.
6. Feed the pattern upstream. Send recurring reasons back to billing, shipping, or sales so the same chargebacks stop recurring.

Done consistently, this turns a silent leak into recovered revenue. Done sporadically, the invalid claims pile up and get written off because nobody had time to chase them.

How Rex handles chargebacks and deductions

Chargebacks and deductions inflate the metric finance teams watch most here: the longer a claim sits uncoded and unworked, the higher days deductions outstanding climbs and the more cash stays trapped. The fix is consistency, not heroics, and that is where the work overwhelms a team doing it by hand across a full ledger.

Rex codes each deduction by reason as it arrives, validates it against the contract, purchase order, and delivery record, and drives the invalid ones back to the customer before the dispute window closes. It clears the valid ones with the right credit, keeps the aging clean, and escalates only the genuinely ambiguous cases to a person with the documentation already assembled. The team stops triaging a backlog and starts deciding the handful of claims that actually need judgment.

See how Rex works deductions across your whole ledger and recovers the cash others write off.