An invoice can remain unpaid because a customer lacks funds, but it can also remain open because nobody has resolved a pricing discrepancy or posted an approved credit. Repeated collection reminders do little to fix those problems.
A useful dispute process connects the collector who hears the issue with the employee who can resolve it. It also keeps the financial outcome visible until the ledger and customer understanding agree.
Distinguish a dispute from an unexplained deduction
A dispute is a stated disagreement about an invoice or obligation. A deduction is a short payment that may relate to an agreed allowance, an error, a customer claim, or another cause.
Do not assume every deduction is valid or every dispute is an excuse. Record the reason and gather evidence. A customer may have legitimate supporting documents that have not reached your team.
Separate the amount questioned from the amount still expected to be paid. This helps collectors discuss the undisputed balance without ignoring the unresolved issue.
Capture enough information at intake
Record the account, invoice, disputed amount and currency, customer explanation, date raised, and supporting documents. Useful evidence may include purchase orders, pricing agreements, delivery records, returns, and correspondence.
Use categories that lead to action: pricing, quantity, delivery, tax, documentation, or credit pending. Avoid a catch-all label that leaves the next owner guessing.
Check for an existing case before creating another. Duplicate records can produce conflicting responses and misleading workload figures.
Assign resolution ownership
| Issue | Potential owner | Evidence needed |
|---|---|---|
| Price mismatch | Sales or pricing | Approved price and order details |
| Short delivery | Operations or customer service | Shipment and receipt records |
| Missing purchase order | Order administration | Customer purchasing requirements |
| Approved credit not posted | Accounting | Authorization and posting reference |
| Unexplained short payment | Collections initially | Remittance detail and customer clarification |
These are example responsibilities. Your structure may differ, but each case needs one accountable owner, a next action, and a target date.
Follow the case through to the financial result
A hypothetical customer deducts $3,000 from a $20,000 invoice, claiming a pricing error. The collector confirms the $17,000 receipt and records the remaining balance as disputed.
Pricing reviews the agreement and determines that $2,000 of the claim is supported. An authorized credit is issued and posted. The customer is informed that $1,000 remains due, with the explanation and supporting calculation.
The case is complete only when the accounting records, communication, and next collection action reflect that result. Marking it resolved before the credit posts can leave a collector pursuing an amount the company has already agreed to remove.
Keep communication coordinated
Tell the customer who is investigating and when an update is expected. Avoid promising an adjustment before it is authorized.
Give the collector visibility into progress so routine reminders do not contradict the investigation. Continue appropriate follow-up on undisputed amounts and confirm any agreed payment timing.
Escalate cases that stall across departments. The escalation should identify the missing decision or evidence rather than simply increase the number of copied recipients.
Measure delay and recurring causes
Track open disputed value, case age, time to resolution, and cases waiting for posting. Define the starting and ending events consistently.
Review the amounts accepted, rejected, or partially accepted, with enough context to understand the cause. A high rejection rate does not prove an efficient process if customers repeatedly raise the same preventable issue.
Look for recurring sources such as outdated price files, missing delivery documentation, or incorrect invoice instructions. Preventing the next dispute is often more useful than accelerating the same correction repeatedly.
Use a practical control checklist
- Separate disputed and undisputed amounts.
- Record evidence and a meaningful reason.
- Assign one resolution owner.
- Define authority for adjustments.
- Confirm posting and customer communication.
- Resume collection of any valid remaining balance.
Dispute recommendations here describe operational practices, not a claim that CMS provides a dedicated dispute-management module. Confirm the configuration and integrations needed for your process.
CMS Credit Suite supports collection workflows, account information, recorded outcomes, and reporting. Contact Credit & Management Systems, Inc. to discuss how unresolved invoice issues fit into your wider B2B collections workflow.