Distinguish tax year from document issue date at intake

Read the period from the document

Getting that wrong at intake sends the preparer down the wrong path. Capture the stated tax year separately so the package is organized around the work being done.

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.

An intake register needs to preserve what the document says even when the practitioner later decides how it belongs in a return. Printed document periods and the reporting treatment are different questions. The procedure below concerns organizing evidence; the responsible practitioner decides how periods affect the tax work.

Give each date its own field

Use fields for printed period, issue date if shown, received date, intended package and assignment status. A filename can be a useful search aid but should be recorded as a label, not promoted into the source of truth. Preserve a page reference showing where the printed period was found.

TaxDome: Document actions documents file names and descriptions. Microsoft: Data validation explains how a worksheet can restrict permitted values. A proposed intake register can use an unresolved option alongside confirmed package years, preventing an empty year from being treated as current by default. Do not invent a date when the document provides only a year.

Compare three different clocks

This synthetic example illustrates why the fields matter. A client submits three files in the same upload session. Their arrival date is identical, but that fact does not make them one period's evidence.

Do not convert Statement B into a calendar-year document simply to fit a dropdown. Retain its actual range. For File C, ask for the complete document or confirmation of the period, and keep the original filename available so staff can identify what the client supplied.

Avoid silent routing mistakes

Check more than the cover page if the document contains multiple forms or statements. A bundle can include several years, and a cover letter date can be unrelated to the evidence inside. If splitting or indexing the bundle, preserve the original and record page references for each apparent period.

• Compare the printed period with the intended package.
• Flag conflicts between the document and its filename.
• Keep issue and receipt dates out of the period field.
• Ask a reviewer about fiscal or overlapping periods.
• Record who confirmed a disputed assignment.

A staff member may discover that a file already used in preparation was routed incorrectly. Treat that as an affected-work question for the preparer, not merely a filing correction. Moving the document without telling the person using it leaves the underlying risk unresolved.

Verify the register before handoff

Filter for missing, inferred and conflicting periods. Every unresolved item should have a question owner and a next action. Check that the package manifest distinguishes received evidence from evidence confirmed for that package, especially when the same file is also retained for historical reference.

Use the related workflow guide to connect this check to the full intake handoff. the workflow audit checklist can help identify whether wrong-period routing is causing repeated requests or rework. Start with a few ambiguous documents and test whether another staff member can reconstruct the assignment from the recorded evidence.