Client document collection for accounting firms, step by step

Start each client's month from this list and remove what doesn't apply. Save the trimmed version as that client's standard list so you don't rebuild it every month.

One row per expected item, per client, per period.

Set up two views. One shows everything still Requested or Partly received across all clients, oldest first, so you can see who to chase. The other shows Received but not Checked, so files don't sit unopened.

Files arrive by email, WhatsApp, upload or phone photo. A few rules keep them in the right place:

1. Name every file the same way: {ClientCode}_{YYYY-MM}_{DocType}_{AccountLast4}.pdf, e.g. ACME_2026-10_BankStatement_4521.pdf.
2. Match the client by sender email or upload link first. If one person sends for more than one client, for example an owner with two companies, don't guess. Send it to the review queue.
3. Take the period from the dates printed on the document, not the day it arrived. A September statement sent in late October belongs to September.
4. If a file covers two periods, file it under both or split it. Note it in both rows.
5. If you can't tell the client, the period or the account, it goes to the review queue with a one-line note. A person decides.

The review queue can be a folder, a label in your inbox or a status in the tracker. Clear it every day during busy weeks.

A partial file can easily get marked done by mistake. To stop that, the tracker records what the document covers, then compares it with what you expected.

Give each account its own row, so one statement arriving can't close the request for all three. An item only moves to Received when the "Covers" range matches the expected period.

Subject: {Client}: 2 items still needed for October

Hi {first name},

Thanks for the documents so far. For October we still need:
- Bank statement for the account ending 4521, covering 16 to 31 October
- Your card terminal sales report for October

You can reply to this email with them or upload them here: {link}.

Could you send them by {date}?

{Your name}

Stop rule: reminders for an item stop as soon as it's marked Received or the client replies. A person reads every reply before the next reminder is due. The whole request closes only when every row is Checked or Not applicable with a reason.

The first month with a new client needs a one-off list on top of the monthly one. Use the same tracker with a "Why we need it" column added.

Once the new client's list is complete, turn the bank and card list into their monthly checklist rows.

1. Write down every client and the items you expect from each one every month. That's your standard list.
2. Build the tracker in whatever you already use: a spreadsheet, your practice management tool or a Notion database.
3. Agree the file naming rule and the review queue with your team.
4. At the start of each period, copy each client's standard rows forward with the new period.
5. Send one request per client that lists every item.
6. Send reminders a few working days apart that name only what's missing. Stop when it arrives.
7. Check files as they come in and clear the review queue daily in busy weeks.

Runnrr scopes document collection around the software an accounting firm already uses, with agreed checks for stopping reminders when the right file arrives. If you'd like to talk through one collection workflow, see how Runnrr sets up a workflow.