Handle partial client document submissions clearly

Treat a partial reply as progress with several next actions

Mark the package complete and work stalls later; keep asking for everything and the client loses patience. Track each outstanding requirement so the next request is useful.

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.

Record the arrival and keep a link to the original message or upload. For each requirement, decide which next action applies: review an arrival, explain a mismatch, wait until a promised date, request a missing item, or ask a reviewer about something unavailable. Do not mark the whole package complete because an email has been answered.

This is a recommended collection process. Your engagement owner decides which records are required and acceptable.

Work through the reply item by item

Synthetic example: Harbor Repairs is an invented business. A client replies to a September collection request with four files and a message saying the card statement will be available on October 8. The team uses the following table to decide what belongs in the next message.

Copy this format for your triage. Explain the two gaps, date the promised follow-up and keep the possible duplicate in staff review rather than requesting it again.

Send an acknowledgment the client can act on

Use neutral descriptions of the remaining gap. “Please resend the correct documents” gives the client no reliable way to succeed. A useful request identifies the document, entity, covered period and observable problem. When one page is missing, ask for that page or the complete original through the agreed channel; do not automatically demand every document again.

Copyable synthetic wording:

Thanks—we received the four files. The September fuel receipt is accepted, and we're checking the supplier invoice already on file. Two items need a further upload: the merchant payout report covering September 21–30, and page 2 of the equipment lease document. Please use the existing September request in the portal. We've recorded October 8 for the card statement, so you do not need to send it today. If either requested item is unavailable, reply against that item and explain what is available.

Say “received for review” if acceptance has not been confirmed. Do not promise a completed bookkeeping handoff until the person responsible has assessed the remaining work.

Check where completion and replies reach your team

Vendor completion signals and your review decision may represent different events. Karbon's Client Requests documentation says a client's completed task updates the work item and notifies staff in Triage. Use that event to check the response; do not assume the client has verified the file against your requirement.

Response location matters too. Canopy documents that a direct reply to the notification email goes to the request sender, while a comment inside the request notifies the assigned team member. Its guide also describes editing an existing request's name and description. These details support checking both routes and updating the current request rather than creating a competing one.

Those are documented product behaviors, not ParseMill integrations. Test the relevant path in your actual account with synthetic files: send two items, supply one, reply outside the portal and check which staff member sees what. Confirm which reminders remain scheduled before relying on the resulting state.

Keep the next review and next reminder separate

Assign an internal review date to received material. Assign a client follow-up date only to an unresolved client action. If a generic reminder would repeat an obsolete list, pause or revise it using the controls available in your system and record who will check the remaining items. A pause without an owner can simply hide unfinished work.

If the client says a document does not exist, preserve that answer and ask the engagement reviewer to decide the next step. If the sender used the wrong entity or period, keep the original association evidence and explain the correction. Avoid silently closing a requirement or changing the underlying accounting record.

At handoff, report accepted items, outstanding client actions and outstanding staff decisions separately. Another person should be able to continue the work without rereading the entire email chain.

Check whether the revised process reduces confusion

For one collection cycle, count partial replies, repeated requests for already-received material, unclear-request questions and cases returned by the reviewer. Record the specific cause of each repeat interaction. Separate active staff minutes from waiting days; a later promised delivery is not additional handling time.

Use the workflow audit checklist to log a small baseline. If most repeat work comes from locating responses rather than checking documents, investigate the shared inbox handoff. If the same gaps recur because the original request is vague, improve that request before adding more reminders.

Questions about this workflow