Client Onboarding: Collecting Bank Statements for New Bookkeeping Clients

A new client just signed. They sent you 4 bank accounts across 3 banks. You need 12 months of statements by Monday, and the client has never downloaded a bank statement before.

New client onboarding is the most time-consuming part of the bookkeeper workflow. This page covers the 12-month collection process, the 4-bank client, the templated email, and how the recon cutoff tool’s batch upload handles 50 statements in one go.

New client onboarding takes 3-5 hours of statement collection alone. The 4-bank client with 12 months of statements means 48 statements. Most clients don’t know how to download statements from their bank portal, so the request takes 2-3 emails to clarify. The recon cutoff tool’s batch upload handles the conversion in 24 minutes (30 seconds per statement).

The 5-step onboarding process: send the request, follow up, receive the statements, convert, and verify. The 5 steps take 3-5 hours for a typical 4-bank client. The recon cutoff tool’s archive feature stores the original PDFs and converted files for the audit trail.

For the broader bookkeeper workflow, see the bank statement workflow for bookkeepers pillar. For month-end close, see the month-end close guide. For multi-entity, see the multi-entity guide.

The 5-Step Onboarding Process

The 5 steps run in order. Each step has a typical time budget. The total is 3-5 hours for a 4-bank client.

What most guides miss about this workflow is that the quality depends on the mechanism, not on the tool. Two tools that look different on the surface often run the same 4-step process underneath: read, find, parse, verify. The difference is in how well each step handles edge cases (merged cells, missing balances, non-standard date formats, scanned vs digital input).

Choosing between tools based on UI alone misses the actual quality lever.

Step 1: Send the Request

The request goes out the day the engagement letter is signed. The email is templated. The template lists each bank, each account, and the date range (12 months for new clients, 24 months for tax prep clients). The template includes the bank-specific download instructions for the 3 most common banks (Chase, BofA, Wells Fargo) and a generic instruction for other banks.

The email is short. The subject line is “Bank Statements Needed for [Client Name] Onboarding.” The body has 3 paragraphs: the date range, the format (PDF + OFX/QFX if available), and the deadline. The recon cutoff tool’s archive feature can generate the templated email automatically.

Step 2: Follow Up

The first follow-up is on day 3 if the client hasn’t responded. The follow-up is short: “Checking in on the bank statements. The download instructions are below. Let me know if you have any questions.” The second follow-up is on day 5 with a phone call offer. The third follow-up is on day 7 with a status update to the engagement partner.

Most clients respond by the second follow-up. The slow clients are usually small business owners who handle their own books and don’t have a system for statement downloads. The slow clients add 1-2 weeks to the onboarding timeline.

Step 3: Receive the Statements

The statements arrive as PDF attachments or as a link to a cloud folder. The recon cutoff tool’s archive feature tracks which statements have arrived and which are still pending. The 12-month × 4-account client has 48 statements. The average arrival rate is 50% on day 3, 80% on day 5, 95% on day 7.

Step 4: Convert

Conversion is the recon cutoff tool’s batch upload. The tool handles 50 statements in one go. The conversion takes 30 seconds per statement. The 48 statements for the typical 4-bank client take 24 minutes. The per-period split is automatic.

Step 5: Verify

Verification is checking that the converted file matches the source PDF. The recon cutoff tool’s reconciliation worksheet shows row count, ending balance, and date range. The verification takes 1-2 minutes per statement. For the 48 statements, that’s 1-2 hours.

The 4-Bank Client

The 4-bank client is the most common new client pattern: Chase business, Chase personal, Stripe, Mercury (or similar fintech). Each bank has a different download path. The download instructions are bank-specific.

Chase business. Log into Chase Business Banking → Documents → Statements → select date range → download as PDF. The download takes 2-3 minutes per statement. Chase has 24 months of statements available.

Chase personal. Same as Chase business but in the personal banking portal. Chase has 7 years of statements available for personal accounts.

Stripe. Log into Stripe Dashboard → Reports → Statements → select date range → download as CSV (Stripe doesn’t offer PDF). The recon cutoff tool handles CSV directly. Stripe has 12 months of statements available.

Mercury. Log into Mercury Dashboard → Accounts → Statements → select date range → download as PDF or CSV. Mercury has 24 months of statements available. For more banks, see the bank export guide.

The Templated Email

The templated email saves 1-2 hours per onboarding. The template has 5 placeholders: client name, bank list, account list, date range, and deadline. The email body is 3 paragraphs. The attachment is the bank-specific download instructions for the 3 most common banks.

Email Template

Subject: Bank Statements Needed for [Client Name] Onboarding

Hi [Client Name],

Welcome aboard. To get your books set up, I need 12 months of bank statements for the following accounts: [list]. Please download each statement as a PDF (and OFX or QFX if available) from your bank portal.

Download instructions for Chase, BofA, and Wells Fargo are attached. For other banks, log into your online banking, go to Documents or Statements, and download the PDF for each month in the date range.

Please send the statements by [deadline]. Let me know if you have any questions.

Thanks, [Bookkeeper Name]

What to Ask For

The format request is PDF plus, when available, OFX or QFX. The PDF is the official statement, used for the audit trail. The OFX or QFX is the raw data feed, used for the conversion.

The date range is 12 months for new clients, 24 months for tax prep clients. The recon cutoff tool’s archive feature stores the full date range.

What About Older Statements?

Most banks have 12-24 months of statements available. Some banks have 7 years. Older statements are usually not available through the online portal; the client needs to request them from the bank by mail or in person. For new client onboarding, 12 months is usually enough.

The Common Bottlenecks

3 bottlenecks that slow down onboarding.

Client doesn’t know how to download. The bank-specific instructions help, but some clients need a phone walkthrough. The walkthrough takes 15-30 minutes per bank. The recon cutoff tool’s archive feature can record the walkthrough as a Loom video for future reference.

Bank doesn’t have the full date range. Some banks only have 6-12 months available. The fix: ask the client to request older statements from the bank, or accept the gap and explain it to the engagement partner.

Statements arrive in different formats. Some clients send PDFs, others send CSVs, others send links to cloud folders. The recon cutoff tool handles all three formats. The conversion step is the same regardless of input format.

After the Conversion

Once the statements are converted, the next step is reconciliation. The recon cutoff tool’s reconciliation worksheet shows which transactions match the books and which don’t. For a new client, the books are usually empty, so the reconciliation is straightforward: every transaction is new.

The first month-end close for a new client is the most time-consuming. The bookkeeper sets up the chart of accounts, the bank feeds, and the categorization rules. The recon cutoff tool’s archive feature stores the setup so the second month-end close is faster.

A common failure mode bookkeepers report is treating this as a single operation rather than a chain of dependent steps. The temptation is to find a tool that ‘just works’ and stop investigating the mechanism.

The result is a wrong-fix cycle: the tool gives partial output, the bookkeeper spends 30+ minutes troubleshooting, the fix is for the wrong step, and the same error recurs on the next statement. The fix: identify which step failed and apply the right intervention to that step.

The Onboarding Checklist

5 items on the onboarding checklist.

Send the templated email on day 1. The earlier the better. The slow clients add 1-2 weeks to the timeline.

Follow up on day 3, day 5, and day 7. The follow-up cadence is non-negotiable. Most clients respond by the second follow-up.

Use the bank-specific download instructions. The instructions are attached to the templated email. For less common banks, the generic instructions work.

Batch convert with the recon cutoff tool. The batch upload handles 50 statements in one go. The conversion is 30 seconds per statement.

Verify and archive. The reconciliation worksheet catches errors. The archive stores everything for the audit trail.

For the broader bookkeeper workflow, see the bank statement workflow for bookkeepers pillar. For month-end close, see the month-end close guide . For multi-entity, see the multi-entity guide . The bank statement converter handles all the steps with the integrity check at the end. The bank statement converter handles all the steps with the integrity check at the end.

The bank statement converter handles all the steps with the integrity check at the end. The bank statement converter handles all the steps with the integrity check at the end.

Related:

This topic is part of the bookkeeper-resource cluster on this site. The consolidated hub, covering onboarding, monthly close, year-end, client deliverables, and multi-entity workflows, lives in the complete bookkeeper workflow guide.

For related reading on the broader clusters, the
covers credit-card-side mechanics, and the
covers bank-account-side mechanics. The expanded bank statement anatomy is a useful primer.

Decision framework for this topic

For the broader context on US bank-statement reading, see the consolidated hubs on merchant category codes, payment rails, and the statement anatomy. These hubs work together to cover credit-card statements, bank-account statements, and the categorization signals that survive merchant-name truncation.

Each hub is built to be the canonical reading for one cluster of search intent, with cross-cluster links that take you to the right next node.

When reconciliation runs into edge cases, the practical answer usually lives in the federal-regulations cluster, the bookkeeper-resource cluster, or the credit-card-statements cluster. Each offers a domain-specific take on the same underlying signal. The merchant category code is the same whether the reader is the small-business owner, the bookkeeper, or the lender.

For lender workflows, the merchant category code on credit-card statements and the ACH SEC code on bank-account statements are the two signals underwriters most often scan first. Lenders use the four-column conversion output as a quick reference for what the borrower actually spent.

Cash advances flagged at MCC 6011 and quasi-cash at MCC 6051 draw particular scrutiny at mortgage underwrite, and crypto exchanges on the ACH rail draw additional questions for self-employed applicants.

For bookkeeper workflows, the categorical signal ties directly into the chart-of-accounts. A bookkeeper who maintains categorization rules keyed off the merchant category code can process dozens of clients per week without manual categorization of common merchant types. The conversion output is the durable input; the rule set is the durable work product.

Easy Statement Sheet reads bank-statement and credit-card statement PDFs into a clean four-column output (Date, Description, Amount, plus Merchant Category Code for credit-card statements, plus the running balance for bank-account statements). Files are never stored. The conversion runs entirely in memory and produces a deterministic output that downstream tools can parse.

The first three statement conversions are free, no card required. Plans start at $15 per month. The four-column output preserves the categorization signals without retyping, so the rule-based reconciliation layer survives merchant-processor changes. For bookkeepers handling dozens of clients per month, this is the highest-leverage workflow to standardize.

Related reading and broader clusters

For the broader context on US bank-statement reading, see the consolidated hubs on merchant category codes, payment rails, and the statement anatomy. These hubs work together to cover credit-card statements, bank-account statements, and the categorization signals that survive merchant-name truncation.

Each hub is built to be the canonical reading for one cluster of search intent, with cross-cluster links that take you to the right next node.

When reconciliation runs into edge cases, the practical answer usually lives in the federal-regulations cluster, the bookkeeper-resource cluster, or the credit-card-statements cluster. Each offers a domain-specific take on the same underlying signal. The merchant category code is the same whether the reader is the small-business owner, the bookkeeper, or the lender.

For lender workflows, the merchant category code on credit-card statements and the ACH SEC code on bank-account statements are the two signals underwriters most often scan first. Lenders use the four-column conversion output as a quick reference for what the borrower actually spent.

Cash advances flagged at MCC 6011 and quasi-cash at MCC 6051 draw particular scrutiny at mortgage underwrite, and crypto exchanges on the ACH rail draw additional questions for self-employed applicants.

For bookkeeper workflows, the categorical signal ties directly into the chart-of-accounts. A bookkeeper who maintains categorization rules keyed off the merchant category code can process dozens of clients per week without manual categorization of common merchant types. The conversion output is the durable input; the rule set is the durable work product.

Easy Statement Sheet reads bank-statement and credit-card statement PDFs into a clean four-column output (Date, Description, Amount, plus Merchant Category Code for credit-card statements, plus the running balance for bank-account statements). Files are never stored. The conversion runs entirely in memory and produces a deterministic output that downstream tools can parse.

The first three statement conversions are free, no card required. Plans start at $15 per month. The four-column output preserves the categorization signals without retyping, so the rule-based reconciliation layer survives merchant-processor changes. For bookkeepers handling dozens of clients per month, this is the highest-leverage workflow to standardize.