Handle a client who submits a folder with no index

Inventory the bundle before trying to finish it

Build a small inventory once, then use it to identify real gaps instead of reopening the same files during every status check.

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.

Keep the original bundle available in its approved location. Give each file a stable intake reference and preserve its supplied name. Renaming every file before you understand the contents can remove useful context and make it harder to explain which upload you are asking the client about.

Capture observations rather than guesses

Record file reference, supplied name, apparent document type, visible entity, visible period, page count where useful and proposed requirement. Add an uncertainty column for missing or conflicting clues. Use “not yet inspected” distinctly from “inspected, cannot identify”; they call for different next actions.

TaxDome: Document organization describes organizing documents in folders. Microsoft: Sorting data supports ordering worksheet records by multiple columns. Use those mechanics to group an inventory by apparent entity and period, but retain the source reference in every row. Sorting is a viewing aid; it should not change the evidence on which a match depends.

Work through a small bundle

Synthetic example: Juniper Studio uploads a folder containing four files with inconsistent names. The invented inventory below is enough to plan the next pass.

This inventory does not claim the package is four items complete. B1 is only ready for its acceptance check. B2 may be a duplicate, B3 is unusable for its apparent purpose, and B4 needs an identity decision.

Turn uncertainty into a short question list

After the first pass, group questions by the information needed to resolve them. Ask about B4's entity once, rather than sending separate speculative requests for every possible client. Refer to the supplied filename and intake reference so the contact can identify the document. Keep a record of the answer and its source.

Do not open unsupported or unexpected files through unapproved applications simply to complete the inventory. Follow the firm's existing file-handling process and record the blocked inspection. A password or access issue should remain visible as such, not become a guessed document classification.

Reconcile the inventory with the request register

Each file should end with an accepted requirement link, a duplicate/reference-only disposition, or a specific unresolved action. Each expected requirement should separately show whether sufficient evidence has been accepted. That two-way check catches both orphan uploads and missing requirements that a large folder can conceal.

For a trial, ask another handler to locate one accepted item and one unresolved item using only the inventory. Record repeated file openings and unclear matches in the workflow audit checklist. the related workflow guide supplies the wider collection flow; the inventory is useful only if its findings update that authoritative request record rather than becoming another abandoned spreadsheet.