Keep a document request separate from an accounting question

Name the thing you are waiting for

Combining those two gaps makes reminders vague and progress misleading. Separate the evidence request from the decision that still needs an owner.

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.

Use the smallest useful distinction. You do not need separate tasks for every sentence in a conversation. Split the work when the evidence can be received independently of the explanation, or when different people must decide whether each outcome is satisfactory.

Use two completion tests

For evidence, define what source is needed and which period or transaction it should concern. For an explanation, state the precise question and who will assess the answer. Link both records to the same case so the client does not receive unrelated-looking messages.

Intuit: Transaction requests supports requests for explanations and receipts. TaxDome: Request list distinguishes response progress. These are useful native capabilities, but your review still needs to establish whether the supplied response resolves the actual question. Use your existing request system where possible rather than introducing a second list with competing states.

See why one attachment is not always enough

Synthetic example: Oak Lane Catering has a card transaction for 180. The handler asks for the receipt and which event the purchase supported. All details are invented.

The receipt can pass its source checks while the event question remains open. The client should receive one focused follow-up about the unanswered event, not another generic request for the receipt. The reviewer, not the worksheet, decides the accounting treatment.

Ask without implying the answer

Phrase the explanation question neutrally: “What activity does this purchase relate to?” Avoid prefilled assumptions such as “Confirm this was for the September event” unless that is already supported information needing a narrow check. If the client does not know, record that answer and route the uncertainty rather than changing it into a confident category.

Keep a received attachment connected to its message context. A file may concern another transaction or contain several purchases. Where the relationship is unclear, leave the evidence association pending even if the client has answered the narrative question fully.

Finish the right record

Close the evidence request only after its acceptance check. Close the question when the designated reviewer accepts the answer or records another explicit disposition. The parent case remains open until all required outcomes have a valid resolution. If one outcome is no longer needed, record the scope decision rather than pretending it was supplied.

Check a handful of recently completed cases for attachments with unanswered questions. the related workflow guide explains the broader collection method. Use the workflow audit checklist to measure whether separating these outcomes reduces duplicate requests and review returns, keeping those observations distinct from any claimed time saving.