Assign an unreadable tax document to the right follow-up

Diagnose the obstacle before requesting another file

Identify whether the client, intake owner or preparer can resolve it so the package moves toward usable evidence.

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.

Receiving a file and accepting its evidence are separate events. Retain the arrival record while keeping the affected requirement unresolved. Do not ask the client to resend every document if only one page or one format is the problem, and do not infer obscured figures from nearby values.

Separate viewing difficulty from source quality

First confirm that the approved viewer or application supports the file type. TaxDome: Supported file types describes differing supported upload formats across TaxDome applications. TaxDome: PDF editing describes viewing and editing PDF documents. A viewer limitation does not necessarily mean the source is damaged; conversely, zooming cannot restore information absent from the original image.

Record what you tried within the approved process, the affected page or area and the observable result. Avoid changing the source to make it appear legible. If an enhancement or working copy is created, keep it clearly separate and have the reviewer confirm whether the evidence is sufficient.

Route three different problems

The fictional examples below illustrate distinct next actions. They should not all produce a generic resend everything message or the same internal technical task.

For a replacement request, identify the source label, page and defect. For example: the right side of page two is cut off; please provide the full page with all edges visible. Avoid including sensitive field values in an ordinary task title or unrelated message thread.

Keep the evidence requirement open

The requirement should show received but unusable, or another explicit state your team defines. Link the replacement request and set an owner. If the client cannot obtain a clearer source, route that explanation to the practitioner for a decision; an intake assistant should not decide that an unreadable field is unimportant.

• Confirm the intended client and period before requesting replacement.
• State the exact affected page or region.
• Distinguish unsupported viewing from damaged content.
• Retain the original arrival and replacement relationship.
• Check the new file against the stated defect.

A replacement can fix one problem while introducing another. A clearer photograph might omit the reverse side, or a converted file might drop pages. Repeat the focused quality check and verify the apparent document identity before selecting it as the working source.

Test whether the request was understandable

Give a colleague the proposed request without showing them your internal discussion. They should be able to describe what the client needs to provide and why. If the instruction remains vague, add the observable defect and acceptance condition rather than more urgency.

Use the related workflow guide for the wider intake sequence and the workflow audit checklist to identify recurring quality failures. Track whether replacements resolve the specific obstacle on the next attempt, which is more informative than counting how many reminder messages were sent.