Capture the payment exactly as received
Record the amount, date, reference, and remittance exactly as the bank or portal shows them. Do not adjust the receipt to match the invoice before the difference is understood. The short payment is the evidence, and changing it early destroys the trail. Apply the amount received and leave the remainder visible as an open item.
Attach the customer's remittance and any message that explains the deduction. If the explanation arrived in a separate email, link it to the payment record. A note that says customer short paid is not enough. The next reviewer needs to see the customer's stated reason and the amount withheld.
Identify what the customer withheld
Compare the payment to the invoice line by line. The difference may be a freight charge, a tax amount, a disputed unit price, or a credit the customer believes is owed. Write the specific line and amount in the dispute record. A total difference of two hundred dollars can represent four different issues that need different owners.
If the remittance does not identify the line, ask the customer for the detail in writing. Do not guess from the size of the difference. A guess can send the case to the wrong department and delay the real answer. The request should name the invoice, the amount received, and the specific information needed.
Ask for the missing explanation in writing
Use a short message that asks for the customer's calculation, supporting document, and desired resolution. Keep the tone neutral and make it easy to respond. Include a deadline that gives the customer a reasonable chance to gather records. The message should not promise a credit or a write-off before the claim is reviewed.
Record the date the request was sent and the date the response arrived. If the customer calls instead, write a summary of the call and send a confirmation email. The written record protects both sides and gives the reviewer something to test. A verbal explanation that is never documented will be reconstructed differently later.
Explore the related specialist service to define scope, ownership, and evidence.
Keep the invoice open in a controlled state
Do not close the invoice or mark it paid while a deduction is unresolved. Use a status that shows the amount received, the amount disputed, and the amount still collectible. The status should be visible in the aging report so the account is not treated as a clean payer. A hidden dispute distorts both the aging and the forecast.
Set a review date for the open balance. If the customer has not provided evidence by that date, the next step should be written down. The step might be a reminder, an escalation, or a decision to accept the deduction with approval. The important control is that the item cannot sit indefinitely without a named owner.
Set a decision date for the deduction
A deduction needs a decision date because open disputes tend to age into write-offs without anyone choosing them. Name the person who can approve the resolution and the evidence they need. For a small, well-documented deduction, the decision may be routine. For a large or repeated claim, the decision should include a review of the underlying cause.
Record the decision and the reasoning in the dispute file. If the deduction is accepted, show the approval and the accounting treatment. If it is rejected, show the evidence sent to the customer and the next collection step. A decision that exists only in a meeting is not a control.
Consumer Financial Protection Bureau provides public guidance that can inform a documented review.
Close only with a named approval
The dispute can close when the payment, credit, or adjustment is recorded and the approver is named. Check that the invoice balance, the customer account, and the general ledger agree. A closure that fixes one record but leaves another open creates a reconciliation problem later. The reviewer should verify all three before signing off.
Keep the closed file available for the next audit or customer question. Include the original receipt, the remittance, the correspondence, the decision, and the approval. A closed dispute with a complete file is easier to defend than one that relies on the memory of the person who handled it. A file that can be produced on request is the strongest evidence that the closure was controlled.
Feed the result back into billing
Review short payments for patterns by customer, invoice type, and reason. A recurring freight deduction may point to a delivery term that is not reflected in the invoice. A recurring tax difference may point to a master-data error. The dispute process should produce a fix, not just a series of closures.
Share the pattern with the billing and customer teams in a short monthly note. Name the most frequent cause and the change being made. If the cause is outside finance, assign the follow-up to the owner who can change it. The goal is fewer short payments next month, not faster paperwork this month.
Continue with a related workflow guide.
Common questions answered
Should a short payment be applied to the invoice?
Apply the amount received and keep the remainder open with the customer's stated reason and evidence attached.
What if the customer does not explain the deduction?
Request the calculation and supporting document in writing, then set a dated next step for the open balance.
Who should close a disputed deduction?
A named approver who confirms the customer account, invoice, and ledger all agree.
Define one reviewable receivables workflow.
Bring the queue, owner, source records, and exceptions you need to make visible.
Book a free consultation