# Client Folder Structure for Bookkeepers

- Author: AutoBankConvert (https://www.autobankconvert.com)
- Published: 2026-07-05
- Updated: 2026-07-05
- Category: Client work
- Canonical: https://www.autobankconvert.com/blog/client-folder-structure-for-bookkeepers

> A client folder structure for bookkeepers: one tree per client for statements, exports, workpapers and letters, with a template you can copy for each client.
A good client folder structure for bookkeepers gives every client the same tree with five branches: admin, statements, exports, workpapers and correspondence. Statements sit under year and month folders, exports mirror them, and letters stay apart from working files. Copy the empty template for each new client so anyone on the team can find anything.

## What belongs in a client folder structure for bookkeepers?

A client folder structure for bookkeepers needs one top-level folder per client and the same five branches inside each: admin for the engagement, statements for source documents, exports for files sent to the books, workpapers for your own working, and correspondence for what passed between you and the client. Keep the names and order identical for every client.

Each branch has one job, and the job decides what goes in it:

| Branch | What goes in it | What stays out |
| --- | --- | --- |
| 01 Admin | Engagement letter, fee changes, access list, client notes page | Monthly statements, working files |
| 02 Statements | Bank, card and loan statements as received | Spreadsheets you built from them |
| 03 Exports | Converted files imported into the books, by period | Original PDFs |
| 04 Workpapers | Reconciliations, schedules, review notes, year-end package | Client emails |
| 05 Correspondence | Saved client emails, letters, signed confirmations | Drafts of your own working |

The numbers at the start of each name keep the branches in the same order in every file browser. That sounds minor until you are covering for a colleague and want to open the same place in each client's tree without thinking.

The one-tree-per-client rule matters more than the branch names. A shared "Statements 2026" folder holding every client's PDFs makes it easy to drop a file into the wrong client's work, and hard to remove a client cleanly when the engagement ends.

## A copyable client folder template

A copyable client folder template is an empty tree you keep in one place and duplicate for each new client, then rename the top folder. Starting from a copy rather than building folders by hand keeps every client identical, including the ones set up by someone else on a busy day.

Here is an example template for a fictional client:

```
Ortega Landscaping LLC/
  01 Admin/
    Engagement/
    Access and contacts/
    Client notes.docx
  02 Statements/
    2026/
      2026-01/
      2026-02/
      ...
    Prior years/
  03 Exports/
    2026/
      2026-01/
      2026-02/
  04 Workpapers/
    2026/
      Reconciliations/
      Year end/
      Review notes/
  05 Correspondence/
    2026/
```

Name the top folder with the client's legal name as it appears on their bank statements, followed by a short code if you use one. Inside the month folders, give each statement a name that says the client, bank, account and period, so a file still makes sense if it is ever moved out of the tree. The post on [bank statement file naming conventions](/blog/bank-statement-file-naming-convention) sets out a pattern for that.

Keep a "Client notes" document in Admin. It holds the facts that are not files: which accounts exist, how statements arrive, quirks of the client's vendors, and who to call. When someone covers a client for the first time, this is the page they open.

### Keeping the template current

The template will change as the practice changes. You might add a payroll branch when you start offering payroll, or split Workpapers once year-end packages grow. When that happens, change the master template first, then decide whether existing clients need the same change. Adding a new empty folder to every active client takes minutes and keeps the trees identical. Restructuring old years rarely pays, so leave closed years as they were and apply the new layout from the next year folder onward. Record the date of each template change in a short note beside the master copy, so a colleague who finds two slightly different trees knows which one is current.

## Year and month folders inside the statements branch

Year and month folders inside the statements branch should go two levels deep and no further: one folder per year, one folder per month inside it, with months named as numbers so they sort in order. Deeper trees, such as a folder per bank inside each month, add clicks without making files easier to find.

Use the format 2026-01 rather than "January" for month folders. Named months sort alphabetically, so April comes before January. Numbered months sort correctly everywhere, and they match the period in each statement's file name.

### Edge cases in the date folders

- **Statement periods that cross months.** A card statement running from January 15 to February 14 belongs in the folder of its closing date, 2026-02, because that is the period it reconciles.
- **Quarterly statements.** File them in the month the period ends, and note in the client page which accounts arrive quarterly so nobody chases a "missing" January statement.
- **Catch-up work.** When you take on a client with a year or more of history, file the backlog into the same year and month folders. The [catch-up project status updates](/blog/catch-up-project-status-updates) post covers how to report progress through that backlog to the client.
- **Prior years.** Older years you received but do not work on go in a "Prior years" folder, so the active years stay short.

## Where do workpapers and client letters sit in the folder tree?

Workpapers and client letters sit in their own branches, apart from statements and exports. Workpapers are your working, such as reconciliations and review notes. Letters and emails are the record of what you and the client agreed. Mixing either one into the statement folders makes month folders harder to scan.

Workpapers group by year and then by purpose: reconciliations, year-end items, and review notes. A reconciliation report saved each month gives you proof that the account tied, and it is what a reviewer or the client's CPA will ask for. Review notes record the corrections made and why, which helps when the same issue appears again.

Correspondence groups by year only. Save the emails that carry a decision or an instruction, such as "please code all Home Depot purchases to job materials", and name the saved file with the date and the subject. You do not need every message, just the ones you might need to show later.

The engagement letter and fee changes stay in Admin, not Correspondence, because they define the whole relationship rather than one month. If a client relationship ever has to end, those Admin documents are the first ones you will open, and [when to fire a bookkeeping client](/blog/when-to-fire-a-bookkeeping-client) covers the rest of that decision.

## Client folder permissions for staff and cover

Client folder permissions should follow the work. The preparer and reviewer for a client need the whole tree. A colleague covering a vacation needs it only for the cover period. Nobody outside the practice should see Workpapers, and the client, if they have access at all, should see only a shared upload folder.

Set permissions at the top client folder, not on each branch, so the same rule covers everything. Then grant cover access before the absence starts. The guide to [bookkeeper vacation coverage without missed closes](/blog/bookkeeper-vacation-coverage) explains how to plan the handover, and the folder tree is a big part of it: if every client looks the same, the person covering can work without a tour.

If clients upload their own statements, give them a separate shared folder per client rather than access to 02 Statements. Move files from the upload folder into the right month folder when you process them. This keeps your working files private and keeps the client from deleting or renaming something you depend on.

As the client list grows, folder permissions become a real admin job. Review them each quarter, and when someone leaves the practice, remove their access the same day. [How many clients a bookkeeper can handle](/blog/how-many-clients-can-a-bookkeeper-handle) is a useful read on how fast that list can grow.

## Closing a client folder when the engagement ends

Closing a client folder means moving the whole tree out of the active area once the engagement ends and the final handover is done. Rename it with the end date, remove staff access except for the owner, and keep it for as long as your retention policy says before deleting it.

A close-out sequence, as an example:

1. Confirm the final month is closed and the last exports are in the books.
2. Save the handover letter and any final confirmations in Correspondence.
3. Send the client, or their new bookkeeper, the files the engagement letter says they are owed.
4. Rename the top folder, for example "Ortega Landscaping LLC (ended 2026-09)".
5. Move it to an archive area and limit access.
6. Note the deletion date in your client list.

Because the tree holds only one client, closing it is a single move. A practice with shared folders across clients has to hunt for every file instead, and usually misses some.

## Folder trees that copy the bank instead of the client

The most common folder mistake is building the tree around banks or file types instead of clients: a "Chase" folder, a "Wells Fargo" folder, or one folder of every client's PDFs for the month. These trees feel natural when you download statements from each bank in turn, but they put several clients' records side by side.

The problem shows up later. A statement saved into the wrong client's work leads to wrong books. A client who leaves has files scattered across every bank folder. A colleague covering a client has to search several places to see one month.

Keep the client at the top, always, and let the bank show up in the file name instead. The same rule applies to the tools you work in. AutoBankConvert keeps a separate workspace for each client, with their own accounts, rules and history, so a folder tree built around clients matches how the statements are processed. You can [see how a batch moves from statements to export files](/) on the homepage.