Automate document chasing for accounting firms

Do not let the next bottleneck start when the client replies

Make each follow-up specific enough to move the work forward. Your existing request system can own the reminders; ParseMill can take over the invoice-to-Excel step once the requested supplier PDFs arrive.

Inspect the interactive invoice sample, then try your own invoices. Eligible new workspaces get 10 pages for 7 days after email verification, with no card or automatic subscription.

The queue is the missing item, not the email

A reminder email is an action. The thing being worked is a missing bank statement, unclear receipt or unanswered question. Track that item from the first request until it is accepted, withdrawn or escalated. Retain the owner, due date, last response and next action.

A client may reply with two of five documents, say a statement will arrive next week, or explain that a file is unavailable. Those are different states. A useful process acknowledges the response and updates the remaining request before sending another reminder.

Start with the collection register. Without an accurate list, an automated cadence simply repeats inaccurate requests faster.

Write stop and escalation rules first

Stop when the request is resolved, the engagement ends, the recipient is wrong or a person takes over. Failed delivery needs attention rather than endless retries. A client should not receive reminders from both a practice system and a separate workflow for the same item.

Make the next action specific

Illustrative client-service reminder: “We are preparing your May bookkeeping and still need the May statement for the business card ending 1234. Please use your usual secure upload link by Friday. If it is not available yet, reply with the expected date so we can update the request.”

Adapt the wording and timing to your firm. Keep sensitive financial details in the approved portal, confirm the intended recipient and include only the context they need. Use this example within the client engagement and your firm’s communication policy.

If the client uploads the wrong month, close the old reminder action and create a clear clarification. Do not mark the required May statement complete merely because a file arrived.

A worked example: the cost of repeated follow-up

Hypothetical assumptions: 240 clients × 35% needing a chase × 3 follow-ups per month × 6 staff minutes per follow-up ÷ 60 = 25.2 hours per month. At $45/hour, the modeled capacity cost is $1,134.

If a future pilot reduced handling time from 6 to 2 minutes for those same 252 follow-ups, the gross difference would be 16.8 hours. Additional exception review, configuration and monitoring must be deducted to estimate net capacity. Use your own handling times to adjust this scenario.

For a useful baseline, time the complete follow-up action: find the request, check what arrived, write the message and update the record. Do not add those component times again elsewhere.

Use native reminders before adding a new workflow

Karbon Client Requests already supports scheduled reminders. Canopy Client Requests supports reminder intervals and client snoozing. Check your current configuration, ownership and response handling first. For a practical test of partial completion and staff review, use the Karbon client requests and document reminders guide.

Record one month of follow-ups by unresolved reason: no response, partial response, wrong document, promised later or unavailable. The distribution tells you whether the bottleneck is cadence, request quality, matching or a decision that needs staff judgment.

Request a missing-document chasing audit to estimate the time spent following up and identify a practical improvement.

Questions about this workflow