On this page Jump to section
Track receipt quality
Record request scope, received date, source location, coverage, and any mismatch. A file can be received but incomplete. Keep superseded versions and send sufficiency or interpretation questions with the underlying records to the authorized tax preparer.
Turn each request into a clear record
Use the tax preparer's actual request list as the starting point. Record the requesting person, entity, period, document description, requested delivery date and approved upload location. Keep the wording of any unusual request available through a source link so the assistant does not substitute a different document based on a similar filename.
Assign one follow-up owner per request. If several departments hold parts of the answer, create linked subtasks without losing the original request. Questions about whether an alternative document is sufficient should go back to the preparer.
Distinguish arrival from acceptance
A file arriving does not mean the request is satisfied. Use statuses that show where work remains.
- Requested
- Record Request source, recipient, scope and due date.
- Next check Confirm that the recipient knows what is needed and where to deliver it.
- Received for checking
- Record Arrival date, source link and document version.
- Next check Check readability, requested period and whether all expected pages are present.
- Incomplete or mismatched
- Record Missing pages, wrong period or unclear entity reference.
- Next check Send a precise follow-up and retain the partial document.
- Delivered for review
- Record Approved destination, delivery date and the exact version sent.
- Next check Track any response without assuming that delivery establishes sufficiency.
- Accepted or returned
- Record Preparer's response and any new requirement.
- Next check Close the request only under the agreed acceptance process, or reopen it with a named owner.
Follow up without creating competing copies
Use controlled links to restricted originals whenever the approved workflow permits. Avoid circulating sensitive documents in general task-board comments. Record a replacement as a new version, identify what it supersedes and notify the preparer if an earlier version was already delivered.
Before chasing a missing item, check whether it arrived through another approved channel. Link that arrival to the request instead of creating a second supposedly outstanding task. Keep reminders concise: identify the request, the precise missing material and the agreed next date.
Example: a statement is missing its final page
A twelve-page statement arrives as an eleven-page file. Mark it received but incomplete, record the missing page and request a complete replacement. Do not silently label the request complete because the first page shows the expected account and period.
When the complete file arrives, retain the earlier version and mark the new one as current. If the preparer already received the partial file, send a version-specific update through the approved channel. The preparer decides whether the supplied material meets their needs.
Hand over the exceptions with the documents
Send the tracker with a short summary of outstanding requests, mismatches, replacements and items awaiting acceptance. Include the packet's cutoff time. A late arrival should have its own dated update so it cannot be confused with the original delivery.
For help maintaining document indexes and follow-up queues, see reporting and tax preparation support. The assistant organizes the requested evidence; the tax preparer interprets it and makes filing decisions.
Related resources
Compare the service fit on the QuickBooks VA services page, then use the free consultation form to map the first handoff. For platform context, review QuickBooks Online.
