Record a name mismatch without inferring identity

Record the mismatch without resolving identity by guesswork

Record the difference without guessing identity so the preparer has the evidence needed to decide whether the file belongs in the package.

If supplier invoice PDFs need to become a business-expense workbook, test that step in ParseMill. It extracts invoice fields and line items for your review and Excel export. For tax forms, package completeness and preparer handoffs, bring one recurring bottleneck to a scoped workflow review.

This intake control helps prevent evidence being filed against the wrong person or entity. It does not replace identity verification or determine whether a name change is legally effective. Record only the information needed to resolve the routing question and keep sensitive identifiers out of broadly visible task titles.

Create a concise mismatch card

Record artifact reference, source page, name as printed, internal account reference, nature of the difference and confirmation owner. Avoid copying full identifying numbers into a general register. If the document is already in a shared location, have the authorized owner check access while the assignment is reviewed.

TaxDome: Folder permissions explains how folder placement can affect access. TaxDome: Request actions describes client-request actions. Use the approved communication and access arrangements for the engagement; a request tool does not establish who is authorized to confirm a disputed identity. The proposed card records the observation and next action without inventing a conclusion.

Distinguish three different conflicts

The following synthetic examples require different questions. None should be resolved merely by editing the filename to match the existing client record.

The confirmation may establish a valid relationship, identify a mistaken upload or show that more evidence is needed. Retain the source of the confirmation and the authorized decision. If the file concerns another account, follow the firm's handling process rather than forwarding it informally to someone who seems likely to know.

Prevent the assumption from spreading

Check whether the uncertain document has already been linked to preparation work or included in a package. Notify the responsible owner that its assignment is under review. Do not alter professional work yourself; identify the affected references so the practitioner can decide what requires reconsideration.

• Preserve the name exactly as observed on the source.
• State the specific conflict without speculative explanations.
• Use approved channels for confirmation.
• Record the reviewer and assignment decision.
• Check downstream references after a misroute is corrected.

A client's casual message may provide context but still require verification under the firm's process. Conversely, do not imply wrongdoing merely because names differ. The useful operational state is unresolved assignment with a clear next action, not an accusation or an unsupported identity match.

Verify the final routing record

Before closing the mismatch, confirm that the selected account, period and access location agree with the authorized decision. A colleague should be able to see why the document belongs in the package without relying on the original intake owner's memory. Retain any remaining limitation explicitly.

Use the related workflow guide for the broader intake workflow and the workflow audit checklist to examine ambiguous routing. Test the process with invented similar names so the team can practice stopping an assumption before it becomes a misleading package label.