Handle a prior-year document supplied for reference

Label historical evidence by its intended use

Label its purpose clearly so the preparer can use the reference without treating it as a newly supplied current-year document.

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.

Reference material can help explain structure, terminology or an earlier treatment. That usefulness does not establish current completeness. Keep the question being answered by the historical file separate from the current evidence requirement so staff can see what the upload did and did not resolve.

Make the distinction visible in the manifest

Add fields for source period, intended use, linked current question and current requirement status. Use wording such as prior-year reference supplied by client, with the practitioner decision recorded separately. If a file supports several discussions, link it to those questions without changing its period or copying it under a misleading new name.

TaxDome: Organizer answers describes comparing organizers based on the same template. TaxDome: Link documents describes linking documents to work. Both can make historical context accessible. The operating rule proposed here is to preserve the original period and keep the current requirement open until its own acceptance condition has been met or formally changed.

Work through a misleading arrival

In this synthetic example, the firm asks for a current schedule. The client uploads last year's schedule to show how the information was previously arranged. A simple uploaded checkbox would hide the missing current input.

H14 resolves the question of which layout the client means, but it does not complete R52. The response can explain the required current information without requesting the same historical file again. If the practitioner decides the requirement should change, record that decision against R52 explicitly.

Prevent reference material from becoming current evidence

Check filenames, folder placement and package summaries. A prior-year file copied into a current folder can be mistaken for current evidence even when its internal year is correct. Include the source period in the visible label and the manifest, especially when someone will review an exported or downloaded package.

• Keep the printed period unchanged in metadata.
• State why the historical file was supplied.
• Link the current question it helps answer.
• Retain the current requirement's separate state.
• Ask the practitioner to resolve disputed relevance.

Do not assume all prior-year material is irrelevant. The aim is accurate use, not automatic exclusion. Conversely, do not accept a prior-year document as a substitute based on intake convenience. The practitioner should decide whether an alternative source or explanation is appropriate for the work.

Verify the package without relying on folder names

Ask a colleague to identify which files are current evidence and which are reference material using the manifest alone. Then compare a sample to the printed periods. If the distinction disappears when files are downloaded, add a cover sheet or explicit index that travels with the package.

Use the related workflow guide for the full tax intake process and the workflow audit checklist to assess whether reference uploads cause false completion or repeated requests. A useful workflow makes historical context available while keeping the remaining current-period work visible.