# Shoebox Client Bank Statements: From Paper to Batch

- Author: AutoBankConvert (https://www.autobankconvert.com)
- Published: 2026-04-12
- Updated: 2026-04-12
- Category: Batch conversion
- Canonical: https://www.autobankconvert.com/blog/shoebox-client-bank-statements

> Shoebox client bank statements arrive as loose paper by the box. Sort them by account and month, scan them in sets and run one batch with a gap check.
Shoebox client bank statements are the loose paper a client hands over in a box, often months of it, out of order and mixed with other mail. To turn them into usable books, sort the pages by account and month, check for gaps, scan each statement as its own file, then convert the whole set in one batch.

## What arrives in a shoebox client's box of statements?

A shoebox client's box holds far more than statements, and the statements it does hold are rarely complete or in order. Expect a mix of bank paper, other financial mail and personal papers, folded, stapled and sometimes annotated. The first job is not scanning. It is finding out what you have.

A typical box contains, in no fixed order:

- **Monthly bank statements** for one or more checking and savings accounts, sometimes with pages separated.
- **Card statements**, often from more than one card, some business and some personal.
- **Check images or returned checks**, if the bank still sends them.
- **Deposit slips and ATM receipts**, which are useful later but are not statements.
- **Notices**, such as rate changes, overdraft letters and privacy policies, which look official and say nothing about transactions.
- **Loan and mortgage statements**, which belong in the books but follow different rules.
- **Personal mail**, which you should hand back rather than file.

Before anything else, ask the client one question: which accounts did the business use during the period you are catching up? Write the list down. It becomes the rows of the sorting grid later, and it tells you when a statement in the box belongs to an account nobody mentioned.

## Sorting shoebox statements by account and month

Sorting shoebox statements means building one stack per account, then ordering each stack by statement period. Work on a large table and sort in two passes. The first pass splits paper by account. The second puts each account's pages in date order and puts the pages of each statement back together.

### Pass one: by account

Read the account ending on each page header and drop the page on that account's stack. Banks usually print the account ending, or a masked account number, on every page, not just the first. Pages with no account number, such as a back page with only a disclosure, go on a separate stack for now. Most will match a statement once the pages of that statement are side by side.

Set aside anything that is not a bank or card statement in a labelled pile. Deposit slips and receipts can go in an envelope for the client file. Notices can usually be discarded after a glance, but check for one kind first: a letter announcing a new account number or a changed statement cycle explains a gap or a short statement you will meet later.

### Pass two: by period

For each account stack, order the statements by their printed period. Then check each statement's page numbering, such as "Page 2 of 4", and make sure every page is present. A statement missing its last page is the most common problem in a shoebox, because the last page is often the one with the closing balance or the fee summary.

Staple or clip each complete statement as one set. If a page is missing, mark the statement with a sticky note before you move on. It will show up in the gap check as a statement you have but cannot fully trust.

## Scanning shoebox statements in sets

Scanning shoebox statements in sets means scanning each statement as a separate file, with all its pages and nothing else. One statement per file keeps every later step simple: the batch sees one period per file, the balance check runs on a whole statement, and file names map one-to-one to the grid.

Use a document scanner with a sheet feeder if you have one. The guide to [bulk scanning paper bank statements](/blog/bulk-scanning-paper-bank-statements) covers scanner settings in detail. For shoebox work, these steps keep the output clean:

1. **Remove staples and unfold pages.** Folded paper feeds at an angle, and the fold line can hide a row.
2. **Scan one statement at a time.** Load the pages of one statement, scan, save, then load the next.
3. **Scan at a resolution meant for text.** Very low settings blur digits, and very high ones only make files bigger.
4. **Scan both sides only if the statement is printed on both sides.** Blank backs add pages to count and nothing else.
5. **Name the file as you save it**, with client, account ending and statement month, so the name matches the grid.
6. **Check the first file of each account on screen** before scanning the rest of that stack, to catch a setting problem early.

If you end up with a long scan that holds several statements, because the feeder took a whole stack at once, you can still separate it. The guide on how to [split a bank statement PDF by month](/blog/split-bank-statement-pdf-by-month) shows where to cut without losing summary pages. Scanning in sets from the start avoids that step.

## How many months of shoebox statements are missing?

You find missing months by filling a sorting grid: one row per account, one column per month, and a mark for each statement you hold. Empty cells are gaps. Do this before you convert anything, because a missing statement found now is a request to the client, while one found after posting is a reconciliation problem.

Here is an example grid for a made-up client catching up on the first half of a year. "Y" means a complete statement is in hand, "P" means a statement with a missing page, and a blank means nothing was found.

| Account | Jan | Feb | Mar | Apr | May | Jun |
| --- | --- | --- | --- | --- | --- | --- |
| Checking ending 2208 | Y | Y | P | Y | | Y |
| Savings ending 7731 | Y | | | Y | | |
| Card ending 0456 | Y | Y | Y | Y | Y | Y |
| Card ending 9012 | | | Y | Y | Y | Y |

Read it row by row:

- **Checking 2208** is missing May and has an incomplete March. Both need a replacement before the books for those months can be trusted.
- **Savings 7731** shows statements only in January and April. That can mean missing statements, or it can mean the bank issues quarterly statements for a low-activity savings account. Check the period printed on the April statement: if it runs from February 1, nothing is missing.
- **Card 0456** is complete.
- **Card 9012** starts in March. Either the card was opened in March, or the first two statements are gone. The first statement's opening balance answers it: a zero or near-zero opening balance points to a new card.

The balance chain confirms the grid. Each statement's opening balance should equal the closing balance of the one before. Where the chain breaks, a statement is missing even if the grid looks full, which can happen when two statements with the same month name come from different years. The [pre-batch checklist for bank statements](/blog/pre-batch-checklist-for-bank-statements) includes this chain check as one of its steps.

## Running the shoebox batch and reading its flags

Running the shoebox batch is the easy part once the grid is done: upload the folder of named scans as one batch. The useful work is in reading what comes back, because scanned paper produces more flagged statements than downloaded PDFs, and each flag points to a specific fix.

AutoBankConvert reads scanned PDFs as well as digital ones, matches each file to its client, and holds back any statement whose opening balance plus transactions does not equal its closing balance. On a shoebox batch, expect the flagged list to cluster around the same few causes:

- **A missing page.** The statements you marked "P" will usually fail, because the transactions on the absent page are not there to add up. This is the check working as intended.
- **A misread digit** on a faint or creased page. Compare the flagged statement's lines against the paper and correct the value.
- **A page out of order** inside a file, which can make lines appear in the wrong sequence. Rescan that statement with pages in order.
- **A handwritten note** over a transaction row. Clients often write on statements. If the note covers an amount, read the amount from the paper.

Statements that pass still deserve a short look, since paper adds risk to dates and descriptions that a balance check does not test. Read the dates on one page per statement against the printed period, and skim the descriptions for characters that do not belong. Lines the categorization rules are unsure about go to the review queue with a suggested category, so the first month of a shoebox client is usually the heaviest for review.

Update the grid as you go. When a flagged statement is fixed and passes, change its cell to "Y". When a replacement arrives from the client or the bank, scan it, add it to a follow-up batch and fill its cell. The grid stays the single view of what is done.

## Scoping and pricing shoebox statement work

Scoping shoebox statement work means pricing the sorting and scanning as their own step, separate from the bookkeeping. A box of paper takes hours of handling before a single transaction is coded, and that time does not appear in a normal monthly fee. Clients who bring a shoebox once tend to bring one again unless the arrangement changes.

Agree three things in writing before you start:

1. **The period covered.** "Everything in the box" is not a scope. Name the months.
2. **How missing statements are handled.** Say who requests replacements from the bank, and whether any fee the bank charges is passed on.
3. **What happens next month.** The best outcome is moving the client to downloaded statements, or to statements forwarded by email, so the box does not come back.

Shoebox clients often run their own payroll by hand too, with the same paper trail. If they ask you to take it on, price it as its own service. The guide to [pricing payroll services as a bookkeeper](/blog/pricing-payroll-services-as-a-bookkeeper) covers how to set that fee without folding it into the cleanup.

## When should a shoebox client order copies from the bank instead?

A shoebox client should order copies from the bank when the paper costs more to repair than to replace. If most months are missing, pages are damaged, or the statements are so marked up that you would be reading every line by hand, a fresh set of digital statements is faster and more reliable than the box.

Signs the box is not worth processing:

- **More than a third of the grid is empty or marked "P"** for an account. You will be requesting most of it anyway.
- **Pages are water-damaged, faded or torn** through the transaction area.
- **The client has online banking access** and simply never downloaded statements. Downloading takes them minutes, and the result is digital, not scanned.
- **The catch-up covers more than a year.** Paper becomes harder to find the further back it goes, while banks can usually provide older statements through online banking or on request.

Even then, keep the box. Sort it far enough to fill the grid, because the grid tells the client exactly which statements to download or request, and it gives you something to check the replacements against when they arrive. When the replacements are in, [AutoBankConvert](/) can take them as one folder alongside any paper you already scanned.