In one sentence
A deduction occurs when a customer pays less than an invoice and identifies, explicitly or implicitly, a program claim, pricing issue, return, shortage, or other reason for the difference.
What it is
A deduction occurs when a customer pays less than an invoice and identifies, explicitly or implicitly, a program claim, pricing issue, return, shortage, or other reason for the difference.
Who uses it
Accounts receivable, deductions analysts, credit teams, sales, program owners, and finance.
How the calculation works
The deduction is compared with eligible open claims or obligations. Matching identifies support for resolution; it does not by itself change the obligation balance until settlement is posted.
Financial execution
Analysts match, validate, dispute, approve, partially approve, or write off the deduction. Resolution applies a credit or creates a receivable adjustment with a full audit trail.
Accounting impact
Deductions reduce cash received and create an open receivable difference until resolved against a credit, allowance liability, write-off, or recovery.
Example
A customer short-pays $9,800 and references a rebate. An $8,500 approved obligation is applied; the remaining $1,300 stays disputed and collectible.
Required inputs
- Remittance and short-paid invoice
- Deduction amount and reason
- Customer documents
- Related claim, contract, accrual, or obligation
Common rules
- Customer and invoice matching
- Reason classification
- Tolerance and auto-match limits
- Valid obligation and available-balance checks
- Approval and write-off policies
Common exceptions
- Unidentified remittance
- Duplicate deduction
- No supporting obligation
- Amount mismatch
- Mixed reasons
- Customer dispute
How LicenseIQ supports it
- Ingests and classifies deduction evidence
- Matches deductions to claims and obligations
- Separates matching from financial resolution
- Tracks recovery, write-off, settlement, and accounting impact
Related concepts