Record that an expected document does not exist

Distinguish absence from nonresponse

Without a recorded reason, the same request keeps resurfacing. Turn the answer into a reviewable decision so the team can stop chasing and move the work forward.

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.

The handler's job is to capture the explanation and obtain the appropriate review. It is not to decide that an absent document is unnecessary, to invent a substitute or to make a tax conclusion. The accepted alternative, if any, depends on the work and the authorized reviewer.

Capture a narrow absence record

Record the requirement reference, period, client's exact substantive explanation, date, source message, decision owner and next action. Avoid a broad statement such as “client has no records” when the answer concerned only one item. If the client describes a reason, preserve it separately from the firm's conclusion about what happens next.

TaxDome: Organizer answers supports reviewing individual organizer answers. TaxDome: Document statuses gives client approval a specific meaning. These features illustrate why an answered question or client-approved file should not automatically stand for the firm's acceptance of missing evidence. Use a separate reviewer decision in your chosen record, with whatever labels your existing process supports.

Work through three different answers

Synthetic example: Maple Repairs is asked for three items. Each answer needs a different operational response.

The second row may lead to a different requirement rather than an automatic closure. The third row may remain unresolved after the absence is documented. The table deliberately avoids turning a client's explanation into an accounting conclusion.

Keep the question open at the right level

Acknowledge the answer and ask only for what would resolve the next decision. For example: “Thank you for confirming there is no lease. We have passed that information to the reviewer, who will confirm whether another purchase document is required.” This avoids repeatedly asking for the same nonexistent item while leaving the underlying work visible.

If the explanation changes later, retain both statements with dates. A document subsequently found should reopen the relevant review, not erase the earlier unavailable state. Do not carry a period-specific absence decision into future months without checking whether its basis still applies.

Verify the closure evidence

Close the original requirement only when a reviewer accepts the explanation, approves an alternative or replaces the requirement. If the reviewer leaves the work blocked, retain an open blocker with a named owner. Record which outcome occurred. A blank evidence field should not be the only indication that the item was waived.

Try the method on a small set of unresolved requests. Check whether reminders became more accurate and whether reviewers can locate the actual absence explanation. the related workflow guide places this decision in the wider collection workflow. Use the workflow audit checklist to distinguish time spent gathering an answer from time spent deciding what the answer means.