Client document chase emails at day 0, 3, 7 and 14, with portal links only and a preparer escalation

The problem

Waiting on documents stalls the return and the books, and the chasing itself is unpaid time. The figures below come from a vendor survey, so treat them as indications.

• Financial Cents' 2025 survey of 816 firm owners and admins: getting documents from clients was the biggest workflow issue, ahead of manual admin tasks. One respondent: 'Client reminder emails were manual and exhausting. Most of my time was spent chasing, not working.' Vendor survey. Source: Financial Cents, 2025 State of Accounting Workflow and Automation Report (816 firm owners and admins, mostly North America) (Vendor survey by a practice-management software company)
• Karbon (Business plan and above) and TaxDome already send automatic reminders on client requests. If you use them, try those first; this recipe is for firms on email and a sheet, or who want one ladder and one escalation rule across clients. Source: Karbon pricing and plan comparison (automatic client reminders on Business and Enterprise) (Vendor pricing page)
• IRS Publication 4557 tells preparers to 'Encrypt all sensitive files/emails, especially those with the taxpayer's personally identifiable information.' That's why the emails link to your portal and never ask for attachments. Source: IRS Publication 4557, Safeguarding Taxpayer Data (Rev. 6-2024) (US regulator guidance (IRS))

Background reading: Client document reminder emails: a ladder that stops when files arrive · A WISP for small tax and bookkeeping firms that use automations: what the Safeguards Rule asks of your tools

Who it's for

US solo and small CPA, EA, tax and bookkeeping firms (1-15 staff) who chase documents by hand from email and a spreadsheet, or who use TaxDome or Karbon but want one weekly-style ladder across all clients.

Tools and monthly cost

Example month: Illustrative arithmetic. Assume 80 clients in tax season, 60 with something missing: about 60 first emails, 45 at day 3, 30 at day 7 and 15 at day 14, so about 150 emails plus a few internal notes, inside Resend's free tier (3,000 a month, 100 a day). About $0 a month plus your n8n server. Karbon and TaxDome are optional and only if you already use them.

Setup

1. Read the 'Safeguards Rule, WISP, 7216 and Circular 230' section on the accounting hub first.
2. Choose the source. Sheet (default, CHASE_SOURCE=sheet): one row per item in ac-doc-requests (request_id, client_id, client, first name, email, item, asked date, preparer email, optional Karbon work item key) and one row per received item in ac-doc-received; ac-chase-paused lists clients not to chase. TaxDome (CHASE_SOURCE=taxdome): turn on API & MCP in TaxDome settings and set TAXDOME_API_KEY and MSS_TAXDOME_API to https://<your-subdomain>.taxdome.com/api/v4; the workflow only reads.
3. Set CPA_PORTAL_URL to your client portal's upload page and CHASE_DAYS if you want a different ladder (default 0,3,7,14).
4. Karbon (optional): in Settings > Connected Apps > API Applications (Business or Enterprise plan), copy the application ID and access key into KARBON_APP_ID and KARBON_ACCESS_KEY. By default the API only sees Public clients; Private or Hidden clients need an admin request to Karbon. Karbon requires both headers on every call; the workflow refuses to send them to any other host. KARBON_REQUEST_INTERVAL_MS paces calls and 429 replies wait for Retry-After. KARBON_NOTE_AUTHOR is the user the day-14 note is posted as.
5. Set CPA_FIRM_NAME, CPA_FIRM_SHORT, CPA_PHONE, CPA_ADDRESS, CPA_FROM_EMAIL, CPA_REPLY_TO, CPA_TZ and PARTNER_EMAIL from .env.example. Every client email is signed with your firm name, phone and address. Run n8n behind HTTPS with multi-factor authentication on the n8n login and on every connected account, keep execution logs short (Settings > n8n data pruning), and add n8n and its host to your WISP's list of service providers.
6. Swap the mock sheet URL (MSS_SHEET_URL) for n8n's Google Sheets node, and run it on a test client with your own email first. The workflow also has a manual 'run now' webhook used by our tests. Delete it, or put it behind n8n's header authentication, before you go live.

Download

Download accounting-document-chase-ladder.zip

Contains the n8n workflow, the mock data, the test runner with its last results, and the mock server we tested against. All keys in .env.example are fake.

Test result

Every workflow was imported into n8n 2.45.4 and run end to end on our test machine. Karbon (API v3), TaxDome (public API v4, read-only), QuickBooks Online (Accounting API with OAuth 2.0), Google Sheets and the email sender (Resend) were replaced by a local mock server built from their official API docs: it checks the same request shapes, authentication headers and query syntax, pages results (Karbon @odata.nextLink, TaxDome cursors, QuickBooks STARTPOSITION), returns HTTP 429 with Retry-After, and expires the QuickBooks access token so n8n's real OAuth2 refresh runs. These recipes use no AI model; every decision is a written rule. Clients, firms and transactions are invented. Verified with mocks; no real client data was used, and nothing was sent to a real person or account.

Actual output from the test run

Scenario C1: the day-0 email to a client (invented client and firm; account number masked). Names and numbers are invented.

Subject: Documents we need from you (2)

Hi Ava,

To get started on your work, we need the following:

- 2025 W-2 from Northwind Health
- 1099-INT for account *7766

Please upload them through your secure client portal:
https://cedarledger.example/portal

For your security, please don't email tax documents or send them as attachments, and never put your Social Security number in an email. If something on the list doesn't apply to you this year, just reply and tell us - we'll take it off.

Thank you,

Cedar Ledger CPAs
(555) 555-0140
40 Example St, Suite 3, Hartford, CT 06103