Route a document marked final when a later version arrives

Treat final as a label, not a decision

Make the version decision visible so the preparer does not spend time working from a document the client has already replaced.

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.

The intake problem is precedence: several candidates appear authoritative, but their relationship is unclear. Resolve that relationship before staff continue using whichever copy they happen to open first. This procedure is useful for client schedules and working documents as well as externally issued forms.

Compare identity and purpose

Record the two artifact references, received times, sender explanation, apparent subject and period. Compare document content enough to identify the nature of the difference, without an intake assistant deciding the professional consequences. A changed cover page, extra supporting sheet and changed figures need different follow-up questions.

TaxDome: Document actions describes document names and descriptions. TaxDome: Link documents explains that documents can be linked to jobs. Those features can make candidate versions findable, but the business decision still needs a named reviewer. Keep the selected working reference distinct from labels such as final, revised or latest supplied by the sender.

Use a precedence decision record

The following fictional example shows why arrival order is insufficient. A staff member receives a schedule named final on Monday and another file on Wednesday.

After clarification, the practitioner selects the working source and identifies any preparation that must be revisited. The intake record retains the previous selection and the reason for the change. If the sender instead confirms the Wednesday file was an accidental older copy, no precedence change should occur.

Stop conflicting versions from circulating

Update the manifest's working-source field and the affected task links after the decision. Tell staff already using the old reference what changed and what remains to be reviewed. Do not rely on a renamed folder to communicate a change to someone who downloaded a copy earlier.

• Confirm the files concern the same subject and period.
• Record whether the later file replaces or supplements.
• Identify work already using the earlier version.
• Keep a clear selected-source field.
• Retain the reviewer and decision date.

If the two files conflict and nobody can explain why, leave the precedence decision unresolved. A convenient tie-breaker such as newest upload wins can conceal substantive differences. Likewise, removing the word final from a filename does not resolve which source the preparer should use.

Rehearse the next late arrival

Test the method with an invented third version. Ask a colleague where it would be recorded, who would decide its relationship and how the current preparer would be notified. The workflow should accommodate another arrival without overwriting the history of the first two decisions.

Use the related workflow guide for the broader package handoff and the workflow audit checklist to identify where version uncertainty creates repeated review. The practical improvement to seek is a traceable choice of working source, with supporting files and unresolved decisions still visible to the person doing the work.