On this page Jump to section
Separate dispute age from balance age
Age the unresolved question from the last substantive response, while retaining the invoice or bill age for reporting context. This distinguishes a new disagreement on an old invoice from a dispute that has received no response. Route write-off, credit, payment, and collection decisions to the authorized reviewer.
Build a dispute register that links back to the transaction
Keep the dispute register separate from the accounting record. Its purpose is to show the question, supporting correspondence, and next action without changing an invoice, bill, payment, or customer balance.
| Register field | What to capture |
|---|---|
| Transaction reference | Customer or vendor name, invoice or bill number, and a link to the existing record |
| Report context | Date of the aging report and the transaction date shown on that report |
| Dispute opened | Date the issue was first raised and the source of the request |
| Last substantive response | Date and link to correspondence that answered a question or supplied evidence |
| Reason | A short description, such as missing delivery evidence, quantity mismatch, or an unrecognized charge |
| Outstanding request | The exact document or clarification still needed |
| Next owner and date | The person responsible for the response and the agreed follow-up date |
| Decision reference | The authorized reviewer's instruction, recorded separately from the assistant's preparation notes |
A reminder sent by the assistant is not a response from the other party. Log reminders as activity without replacing the last substantive response date. This keeps repeated follow-ups from making an unattended dispute appear current.
Keep payable and receivable questions distinct
For a vendor bill, gather the bill, relevant purchase order, receiving confirmation, and the internal requester's explanation. Identify who can confirm whether the goods or services were received. The assistant can organize those documents and request missing evidence; a payment hold or release stays with the authorized approver.
For a customer invoice, gather the invoice, delivery or service-completion evidence, agreed scope, and the customer's description of the disputed item. Preserve the correspondence in date order. Keep any requested credit or adjustment marked as a request until the authorized reviewer records a decision.
A practical weekly review
- Export or open the agreed aging report and record its date and reporting scope.
- Match each open dispute to its transaction reference. Flag unmatched items instead of guessing which invoice or bill they belong to.
- Check whether new correspondence resolves an evidence request or introduces a different question.
- Identify items whose agreed follow-up date has passed, along with items that have no assigned owner.
- Send the reviewer a concise queue: transaction, unresolved question, evidence already available, missing item, and requested next action.
- Record the reviewer's instructions and the next checkpoint. Keep the original correspondence attached or linked.
Use the team's agreed escalation rules. Do not turn the register's age alone into an instruction to pay, withhold payment, write off a balance, or contact a customer with a collections demand.
Example: an old invoice with a new question
This is an illustrative workflow, not a customer result. An invoice has appeared on several aging reports, but the customer raised a delivery question only this week. The register keeps the original invoice date and separately records the new dispute date. The assistant links the customer's message, asks the internal delivery owner for the missing confirmation, and assigns a follow-up date.
If the same customer sends a useful clarification later, that message becomes the latest substantive response. If the assistant merely sends another reminder, the existing response date stays unchanged. The reviewer can then distinguish transaction age from the time spent waiting for evidence.
Close the question with an auditable record
Record who resolved the dispute, when the instruction was given, and where the supporting decision is stored. If an authorized person updates the accounting record, link the resulting record rather than treating a note in the dispute register as proof that the update happened. A closed question should retain its original evidence and correspondence.
For a recurring review queue, see the payables and receivables support role. Confirm the exact task boundary and approval owner before delegating access.
Related resources
Compare the service fit on the QuickBooks VA services page, then use the free consultation form to map the first handoff. For platform context, review QuickBooks Online.


