Inventory the contents before declaring the package received
Inventory what is inside before handoff so the preparer gets a clear package, not a fresh file-discovery job.
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.
Do not open unfamiliar executable content or move client material into an unapproved conversion service. If the archive cannot be handled through the approved process, ask for a supported delivery format. The aim is a reliable inventory for the preparer, not an improvised technical workaround.
Check the upload route before relying on folder structure
The TaxDome: Upload documents documentation describes ZIP handling in TaxDome's web application. TaxDome: Supported file types shows that supported formats differ across application routes. Verify the behavior of the route your team actually uses, including whether nested folders and unsupported contents are preserved. Do not assume an archive and the resulting document list are interchangeable records.
Create an inventory with archive reference, relative path, filename, apparent type, readability, apparent period and review state. Retain the source container where permitted by your approved storage process. If the system transforms the upload, record the relationship and reconcile its result against the inventory rather than assuming every contained item arrived.
Work through a small archive
This synthetic archive contains four files in three paths. The count of four received files does not mean four usable tax documents, and it does not establish the completeness of the engagement.
| Relative path | File | Intake result |
|---|---|---|
| income/ | statement.pdf | Readable; apparent period recorded |
| income/ | statement-old.pdf | Readable; prior-period reference |
| expenses/ | schedule.xlsx | Opens; review pending |
| notes/ | scan.pdf | Cannot read key text; replacement needed |
The cover sheet can report four files inventoried, three readable, none professionally reviewed, one replacement requested. Keep these counts separate. If the prior-period file is reference material, label its purpose so it does not satisfy a current-period expectation by accident.
Reconcile files before handing them on
Compare the source inventory with the destination list after upload or extraction. Investigate missing items, altered names and collapsed paths. Identical filenames in different folders require care: income/summary.pdf and expenses/summary.pdf may be distinct evidence. Assign artifact references that remain unambiguous even when a system displays only the basename.
- Record the original relative path for each file.
- Check supported types and readability separately.
- Flag nested archives for the approved handling process.
- Reconcile the number of inventoried and available files.
- Keep document review and package completeness separate.
If the contents are password-protected, use the firm's approved access process. Do not describe inaccessible items as reviewed. If the container includes unrelated material, ask the responsible owner how it should be handled without distributing it more widely simply to complete the inventory.
Deliver an index the preparer can use
Hand over the inventory, stable artifact links and unresolved handling questions. Ask a colleague to find two files with the same basename and identify the unreadable item from the index. That practical check catches ambiguity that a total file count misses.
Use the related workflow guide for the full intake workflow and the workflow audit checklist to examine time spent opening, classifying and requesting replacements. This is a manual control proposal; evaluate any automation against a known archive fixture before relying on it for package completeness.
Put it to work with ParseMill
Is invoice preparation the next bottleneck?
If supplier invoice PDFs still need to be keyed into Excel, test that step in ParseMill. Upload a representative invoice, check and correct the fields beside the source, then download the workbook. Compare the complete job with your manual method.
Eligible new workspaces: 10 pages for 7 days after email verification. No card or automatic subscription.
Invoice processing: $49 USD/month · 500 PDF pages · one user. Buy only after you have checked the fit on your own invoices.
If collection, ownership or handoffs are the bigger problem, discuss this workflow with us. We agree the scope and any fee before starting a review.
Sources and editorial notes
- TaxDome: Upload documentsChecked 2026-10-25
- TaxDome: Supported file typesChecked 2026-10-25
Written by ParseMill. Worked examples are illustrative process examples, not customer results. Software availability can vary by subscription and region; check the linked documentation for your account. Review decisions and approvals remain with your team.