Track one document that satisfies several request items

Map purposes without multiplying files

Link the evidence to each requirement so one accepted file can unblock the right work without creating confusion.

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 from the requirements rather than the upload count. A combined statement might cover two accounts, or an agreement might support several periods. Those are reasons to create explicit links, not reasons to declare every related item complete. Keep the original document in its authorized location and avoid separate working copies that can diverge.

Use a small mapping table

Create columns for source reference, requirement reference, relevant pages or sections, reason for the link, reviewer and acceptance state. Each row expresses one relationship. If the same source supports three requirements, there are three mapping rows but still only one source artifact.

TaxDome: Link documents describes linking documents to job cards. Microsoft: Excel tables supports tabular worksheet records. Use whichever existing tool can preserve the relationships clearly. Do not assume that a software link means the evidence has been reviewed: the link makes the source findable, while your acceptance field records the decision about its suitability.

Review a combined statement

Synthetic example: a client supplies U101, a six-page combined bank statement. Pages one to three concern operating account O1; pages four to six concern reserve account R2.

The file has arrived once, but only the O1 requirement is accepted. R2 remains a specific missing-page problem. The ownership question stays separate until its reviewer decides what the cover page establishes. Asking the client to upload U101 again would not resolve either issue unless a corrected copy is needed.

Handle revisions across every relationship

If U101 is replaced, identify all requirements that rely on it before changing the working reference. Check whether the replacement alters only R2's missing page or also changes other content. Reassess affected links and tell the relevant owners. A source replacement should not silently inherit all earlier approvals.

Where only an extract is shared with a colleague, record its relationship to the full source and the pages included. An extract may be convenient, but it should not create the impression that the source consists only of those pages. Keep access permissions consistent with the actual recipients and work.

Reconcile both sides of the map

Check for requirements linked to no source, sources linked to no requirement, and accepted requirements whose cited pages do not contain the needed evidence. Also check that the same source is not being counted as several independently supplied documents in operational reports.

Try the map with one document supporting two requirements, one of which remains unresolved. A colleague should locate both decisions without duplicating the file. the related workflow guide shows how those outcomes return to the collection register. Use the workflow audit checklist if tracing shared evidence repeatedly consumes staff time, recording actual handling rather than assumed savings.