Start from the statement and the ledger
A vendor statement is the vendor's view of the account. Your ledger is your view. The dispute starts when the two views do not agree. Before contacting the vendor, capture both sources as of a specific date and identify the statement period, the closing balance, and the open items.
Do not edit the statement to match the ledger or the ledger to match the statement. Preserve both and build a reconciliation that explains each difference. The reconciliation is the evidence pack's backbone, and it should be reproducible by another person.
Identify the disputed population
List each disputed item with the invoice number, date, amount, payment reference, and the reason for the difference. Common reasons include a payment not applied, a credit not reflected, a duplicate invoice, a short payment, a return, or a pricing disagreement. Keep the list focused on items that are actually disputed.
Separate items that are merely open from items that are disputed. An invoice that is not yet due is not a dispute. A payment that is in transit is a timing question. Mixing categories makes the vendor response harder to interpret and can escalate a routine question.
Use the related specialist service role as a starting point for defining scope and evidence.
Attach proof of payment and credits
For each payment claimed, attach the remittance advice, bank confirmation, or payment portal record. Show the amount, date, method, and reference. If the payment was applied to a different invoice, explain the application and provide the vendor's acknowledgment if available.
For credits, attach the credit memo, return authorization, or approved adjustment. If the credit was applied in a later period, show the cross-period link. A claim without a source document is an assertion, not evidence, and it will usually prolong the dispute.
Write the dispute narrative
Keep the narrative short and factual. State the account, the statement date, the total difference, the items in dispute, and the resolution requested. Attach the reconciliation and the supporting documents. Avoid accusations and avoid presenting an unresolved question as a proven error.
If the vendor needs to take an action, say what it is: apply a payment, issue a credit, correct an invoice, or confirm a balance. Give a response date that reflects the payment terms and the close calendar. A clear request is easier to route than a general complaint.
GAO Standards for Internal Control in the Federal Government provides public guidance that can help your team test relevant workflow assumptions.
Track the response
Record the date sent, the recipient, the reference number, and the response. If the vendor asks for more information, add it to the same pack rather than starting a new thread. Keep the status visible in the payables queue so the item does not disappear while the team waits.
If the response is unsatisfactory, escalate with the facts and the remaining difference. Do not close the dispute just because a call or email occurred. Closure requires a resolution: a credit, a corrected statement, a payment confirmation, or an approved write-off.
Compare this approach with our guide to the next related workflow.
Close and learn
When the dispute is resolved, update the ledger and the vendor account, retain the final response, and note the cause. If the same cause appears across vendors, review the intake, matching, or payment application process. A dispute pack that resolves one item but leaves the cause untouched will be needed again next month.
Review the pack with the owner for completeness and tone. The goal is a record that a controller, auditor, or vendor can follow without a meeting. That standard reduces repeat questions and makes the outcome easier to defend.
Common questions answered
Who should send the dispute to the vendor?
Follow the approved communication boundary. A payables specialist may prepare and send routine reconciliations if authorized, while sensitive or high-value disputes may require an owner.
What if the vendor statement includes invoices we never received?
List them as missing records, request copies, and keep them separate from disputed items until the invoice and receipt are available.
How should a write-off be handled?
The authorized finance owner approves the write-off under policy. The evidence pack should retain the approval and the reason.
Ready to create a clearer support role?
Bring the workflow that consumes the most attention. We will help you shape the role, handoff, decision boundaries, and review points.
Book a free consultation