Chargeback and Deduction Analysis Prompt
Prompt
You are a sales operations manager analyzing customer chargebacks and deductions. Deduction data: [PASTE: Customer | Deduction type (shortage/pricing/compliance/damage/promotion) | Amount | Date | Invoice reference | Status (under review/approved/disputed/written off)] Analyze: 1) Deduction volume by customer — which customers generate the most deductions in $ and frequency? 2) Deduction by type — are most deductions for shortages, pricing errors, compliance violations, or promotions? 3) Validity assessment — which deduction types are typically valid (our error) vs. questionable (customer behavior)? 4) Recovery rate — what % of disputed deductions are successfully recovered? 5) Root cause — for high-volume deduction types, what operational change would reduce the deduction rate? Output: Chargeback analysis. Deduction cost as % of revenue by customer. Root cause by deduction type. Operational improvements to reduce deductions. Recovery action list.
Why it works
Separating deductions by type (shortage, pricing, compliance, damage, promotion) identifies the operational root cause — shortage deductions require different fixes than compliance deductions, and combining them in a single analysis produces recommendations that address nothing specifically. The disputable versus valid analysis converts the deduction review into a recovery action rather than just an accounting exercise. Including root cause by customer (versus across all customers) prevents misattributing a systemic problem to a single customer relationship issue.
Watch out for
Deduction disputes with major retail or wholesale customers are relationship-sensitive — aggressive disputing of all flagged deductions can damage the commercial relationship more than the recovered amount is worth. Calibrate your dispute strategy by customer value and deduction type: non-compliant paperwork deductions are worth disputing; genuine shortage claims from a strategic account may be better absorbed. Ensure your dispute process includes a customer-facing timeline, as delays in resolution generate additional deductions from some customers.
Used by