On this page Jump to section
Reconcile the customer view
Preserve the original invoice, void reason, replacement reference, and any payment or credit application in one trace. If line items or dates change, state why. The support record highlights duplicate-risk evidence; the authorized reviewer decides whether to void, credit, or reissue.
Start with a correction request, not a replacement invoice
Capture who requested the change, when the request arrived, and the original invoice reference. Ask which detail is disputed or incorrect and what evidence supports the proposed replacement. A customer asking for a purchase order number to be added is a different request from a dispute about the services billed.
Keep the original document and communication in the approved workspace. Do not replace the saved original with an edited copy. The reviewer needs to see what the customer received and how the new request differs from it.
Prepare the comparison for review
- Document identity
- CaptureOriginal invoice number, customer, project reference and issue date.
- CompareThe proposed replacement reference and any requested identity changes.
- Changed details
- CaptureThe specific line, description, date, quantity or other field named in the request.
- CompareThe requested value and source evidence, with unchanged fields left clearly identified.
- Existing activity
- CaptureKnown payment, credit, reminder and customer-delivery references.
- CompareWhich linked records need review before any correction proceeds?
- Decision
- CaptureThe authorized reviewer's response, date and exact permitted action.
- CompareDoes the prepared action match the approval, including any limits?
- Customer communication
- CaptureThe approved explanation, recipient and delivery record.
- CompareCan the customer identify the correct document without treating both as payable?
Keep payment and credit questions visible
Before preparing a handoff, inspect the records your access allows and note the time of the check. A payment reference, a customer statement or an existing credit may affect what the reviewer needs to decide. If a linked item is unclear, include it in the question packet rather than omitting it from the comparison.
The assistant should not detach a payment, apply a credit, remove an invoice or change a closed period to make a requested replacement easier. Those actions require the organization's accounting instructions and appropriate authorization. This log helps prepare the decision; it does not determine the accounting treatment.
An illustrative purchase-order correction
A customer requests a corrected purchase order reference on an invoice they already received. The assistant preserves the original invoice and the customer's message, checks for known payment activity, and prepares a field-by-field comparison showing the requested reference change.
The authorized reviewer decides how to handle the correction in the accounting records and what document should be sent. The assistant records that decision, links the resulting document and prepares the approved customer explanation. If a payment arrives while the request is open, the assistant adds that information to the review instead of continuing from the earlier snapshot.
Verify implementation against the decision
After an authorized correction is completed, record the resulting document reference and the person responsible for the action. Compare the changed fields with the approved request. Check that the original and resulting records can be followed through the log and that any remaining linked-record questions have named owners.
If the result differs from the approval, leave the item open and return it for review. “New invoice created” is not a sufficient closing note when the customer-facing explanation or payment linkage is still unresolved.
Close the communication loop
Record whether the approved document was sent, through which channel, and whether delivery failed. Keep a resend as a separate event so a later reviewer can distinguish a correction from a duplicate transmission. Use approved wording and recipients; do not improvise promises about payment terms, tax treatment or dispute resolution.
A complete handoff contains the original record, correction request, comparison, decision, resulting record and delivery evidence. For recurring accounts receivable administration, define who owns each approval and which communications an assistant may send. The same trace should remain usable when another team member takes over the account.
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.


