Separate business entities in a shared client upload

Establish the entity before moving a file

Separate the entities before anyone builds a workbook or starts review, so a familiar supplier name does not send a document to the wrong client file.

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 ambiguous files in an authorized intake location while the question is resolved. This is a proposed handling method, not an automatic identity-matching feature. The goal is to avoid turning a weak guess into a confident downstream instruction.

Build an entity-to-evidence map

For each file, record its upload reference, observed entity wording, apparent document purpose, period, proposed destination and confidence reason. Separate text actually present on the document from information supplied later by a client. If the name differs from the approved entity list, record the difference instead of silently standardizing it away.

TaxDome: Document organization describes folder-based document organization. TaxDome: Folder permissions explains that moving documents can change inherited access. Therefore confirm both the intended entity and the destination's permitted audience before moving a file. A correctly named folder can still be the wrong place for a document if its sharing settings differ from the engagement's requirements.

Use a three-way routing example

Synthetic example: Alder Group's contact uploads a single bundle for two companies. These names and references are invented; the table demonstrates routing decisions only.

Do not spread U43 across both entities to ensure it is somewhere. Link the unresolved file once to an intake question and ask the authorized contact for the exact entity relationship. The two clearly labeled files may continue through their own checks while U43 stays visibly unresolved.

Make the confirmation narrow and reproducible

Ask about the specific document, not the entire client relationship: “Which entity is named as borrower for U43? The supplied heading says Alder Group, while our agreed work covers Workshop and Retail separately.” Preserve the answer and supporting source. If a document intentionally supports several entities, let the reviewer define separate purposes and references rather than creating uncontrolled copies.

Watch for trade names, old names, individual names on business-related records and pages containing several entities. A title page may not resolve every page in a bundle. Split the review scope by source section when needed, while retaining a link to the original combined document.

Check the routed package

A second handler should be able to follow the entity map without relying on a colleague's memory. Check that each accepted file has an entity basis, each uncertain file has a question owner, and each destination has appropriate access. Verify that moving a document did not leave an obsolete link that now appears broken or points to an earlier copy.

Use the related workflow guide for the broader request-to-acceptance flow. If multiple entities repeatedly cause rechecking, add the routing decision to the workflow audit checklist and measure actual touches per file. The useful improvement may be clearer client instructions or existing folder controls, rather than a new matching system.