When a document arrives with no reporting period

Treat the period as an unanswered question

That guess can put the wrong evidence into this month's work. Resolve the period once and make the answer visible to the next person.

A complete client folder still leaves someone turning supplier invoices into spreadsheet rows. That is the step ParseMill handles: upload invoice PDFs, review extracted details and line items beside the source, then download Excel. Keep document requests and engagement tracking in your existing process.

Start with the existing requirement reference. If no requirement can be identified confidently, give the upload a temporary intake reference rather than attaching it to the nearest open task. This prevents one uncertain association from making the intended requirement appear complete.

Gather the evidence in a consistent order

Read the document heading, reporting dates, account or entity label, and any continuation pages. Check whether the period is a complete interval or only an issue date. Compare those observations with the request, recording the exact coverage text rather than paraphrasing it immediately. A statement covering 28 August to 27 September is not automatically a calendar-September statement.

Use a separate period-evidence note. TaxDome: Document actions documents editable descriptions; that is one possible place for the note if your existing system uses it. In a worksheet, Microsoft: Data validation supports restricted values. Use confirmed, conflicting and unknown as your own proposed decision labels. A dropdown standardizes recording; it does not establish the correct period.

Work through an ambiguous upload

Synthetic example: Brook Lane Studio sends three files against its September collection request. The dates and references below are invented. The intake owner checks the content before changing any requirement's state.

Only U32 has established September coverage. U31 is not corrected by renaming it, and U33 is not October evidence merely because of its issue date. Keep all three originals linked to their intake notes so another handler can reproduce the decision.

Ask a question the client can answer

A useful request identifies the supplied file and the unresolved distinction: “We received U33, issued October 2. Which dates does this settlement report cover? We are completing the September package.” This is easier to answer than “Please send the right document.” If the client confirms a period, retain that response with the source and record whether the designated reviewer accepts it.

Do not infer period coverage from a neighboring client's file, a recurring filename or last month's convention. If a document spans periods, preserve its actual interval and ask the reviewer how it supports the required work. Intake staff should not invent accounting allocation rules to make the register fit.

Close the ambiguity without losing the trail

Before accepting the association, check that the requirement, evidence interval and reviewer decision agree. Record who resolved the question and the date. If the source genuinely cannot establish a period, keep the item unresolved with a specific next step rather than repeating the same request indefinitely.

Trial this check on the next mixed upload and count how many period questions remain open after the first pass. Use the related workflow guide to place the check in the wider collection process. If repeated ambiguity creates significant rework, record that handling time in the workflow audit checklist before discussing any change to software or responsibilities.