Keep a third-party document request visible in tax intake

Track the dependency separately from client responsiveness

Keep the request and its owner visible so everyone knows what is pending and who can move it forward.

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.

Record the client's explanation as reported, including any expected availability date and its source. Treat that date as an estimate unless the responsible reviewer has confirmed otherwise. A third-party dependency does not itself determine whether preparation can proceed; route that question to the practitioner.

Create a dependency row

Useful fields are requirement reference, expected source organization or contact category, person responsible for obtaining it, date requested, last update, expected availability, next check and affected work. Use only the contact information needed under the engagement's approved communication process. Do not contact another organization merely because its name appears in the file.

Karbon: Client Requests describes requests with due dates. TaxDome: Request actions describes actions on client requests. These tools can hold or support follow-up, but the proposed dependency record explains why the date exists. Distinguish your next internal check from the client's expected document arrival and from any practitioner-owned filing deadline.

Work through a delayed issuer document

In this fictional case, a client reports that an issuer will make a document available later. The intake owner changes the follow-up plan while leaving the evidence and readiness decisions unresolved.

The next message can ask whether the issuer's estimate still stands, instead of repeating the original upload instruction. If the date passes without evidence, update the dependency and seek a revised plan. Do not move the expected date forward silently just to remove an overdue flag.

Escalate the obstacle rather than the message count

Escalation should explain the missing item, known dependency, last confirmed information and decision needed. The practitioner may choose to wait, request alternative evidence or adjust work sequencing. Intake staff should record that decision and its scope without inventing a professional conclusion.

• Confirm who is obtaining the document.
• Keep reported dates separate from verified deadlines.
• Record the latest source of the availability estimate.
• Assign the next check to one staff member.
• Notify the preparer when the dependency changes materially.

If the third party sends the document directly, reconcile it to the existing requirement and tell the client-facing owner so reminders stop appropriately. If the client forwards an incomplete copy, retain the dependency until the acceptance condition is satisfied or the practitioner changes it.

Review dependencies as a group

At the package review, inspect all external dependencies by next check date and affected work. This helps distinguish a missing owner from a known wait. A row with no current estimate can still be controlled if it has an owner, next check and explicit practitioner decision about the work.

Use the related workflow guide for the full intake workflow and the workflow audit checklist to examine where waiting time originates. A useful system should show the reason for the wait and the next responsible action, rather than treating every outstanding document as identical client delay.