On this page Jump to section
Recover from evidence, not memory
A vendor record may need attention after an incorrect contact change, a duplicate entry, or a mismatch between a supplier document and the account used by the team. Begin by describing the observed problem. Do not assume that the newest email or attachment contains the correct replacement details.
The assistant's job is to collect a reliable comparison, identify affected work and prepare a recovery request. The authorized owner decides which information is valid and what changes may be made. Payment instructions require the organization's established independent verification procedure; a convincing email is not a substitute for that check.
Preserve the current state
Record the entity, vendor identifier, current name and the specific fields in question. Retain a dated view of the record using approved storage. Include the request or event that exposed the discrepancy, the person who reported it and any known affected invoices. Avoid exporting unrelated supplier information into an unrestricted spreadsheet.
Ask the owner whether related administrative work should pause while the discrepancy is reviewed. State exactly which records or tasks are on hold and which can continue. An assistant should not independently cancel payments, merge vendor profiles or alter historical transactions as a recovery shortcut.
Build a focused recovery packet
- Observed discrepancy
- KeepThe field, current value and source that conflicts with it.
- ClarifyIs the problem confirmed, or does the source itself need verification?
- Earlier evidence
- KeepThe prior approved record or instruction, with its date and owner.
- ClarifyDoes that evidence still apply to this entity and supplier?
- Affected work
- KeepRelevant open tasks, invoice references and upcoming handoffs.
- ClarifyWhich items need an owner-approved hold or additional review?
- Recovery instruction
- KeepThe authorized decision, exact scope and permitted operator.
- ClarifyAre there separate permissions or verification steps before execution?
- Result check
- KeepCompletion evidence and the reviewer's comparison against the instruction.
- ClarifyWhich dependencies remain unresolved after the record is corrected?
Example: two supplier profiles with similar names
A bill arrives for a supplier whose name appears twice in the system. One profile contains older invoices and the other contains a recent contact update. The assistant records both identifiers, links the bill and describes the conflicting information. Neither profile should be assumed correct solely because it is newer or has more transactions.
The owner determines whether these are distinct suppliers, a duplicate record, or a naming issue. The recovery packet separates the identity question from the treatment of existing invoices. If further verification is required, the handoff states who will obtain it and which task is waiting.
Check the result and preserve history
After an authorized correction, compare the relevant fields with the approved instruction. Check the listed dependent tasks and ask their owners whether they can resume. A corrected contact field does not automatically resolve an invoice dispute or validate bank details.
Keep the original discrepancy, decision and result together. If a second issue appears, add a new linked entry rather than rewriting the first account of events. This allows the next reviewer to distinguish the initial problem from the recovery work.
For regular supplier-document preparation, see accounts payable and receivable support. Define access and approval boundaries before handing over vendor-record tasks.
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.
