Do Your Books From Bank Statements With Claude

You've got a folder of bank statements and no bookkeeping software. Claude can turn that into a first draft of your books. Not finished books. A first pass you read and fix, the same way you'd check a new hire's work.

Can Claude do your books straight from bank statements?

Yes, for a first pass. Point Claude at a folder of PDF bank statements, including scanned or image ones. It reads every page, categorizes each transaction against a standard chart of accounts like the QuickBooks default, and builds pattern rules as it goes. It flags anything it's unsure about. You get back three files: a categorized transaction spreadsheet, a balance sheet, and a P&L. This is a fast first-pass draft, not finished books. You review it before you trust it, starting with the flagged items.

Key Takeaways

• One folder in, three files out: drop your PDF statements in, and Claude returns a categorized transaction spreadsheet, a balance sheet, and a P&L.
• It sorts against a standard chart of accounts: the QuickBooks default works out of the box, or hand it your own.
• Pattern rules build on the fly: it sees 3 coffee charges from one vendor tagged as meals, and tags the 4th and 5th the same way.
• The flagged pile is the point: transfers, credit-card payments, and opening balances get flagged instead of guessed.
• The bank balance is your check: the cash on the built balance sheet should match your last statement's ending balance. If it doesn't, a line is missing or double-counted.
• It's a first pass, not a filing: read every category and clear every flag before you call the books done.
• Good for your own books, not a 30-client roster: one folder at a time, with no memory that carries your fixes forward.

What doing your books from bank statements means

Most books start from two things. Bank statements and card statements. Every dollar in and out is on them. So if you want Claude to do your books, statements are the natural place to start.

Claude reads the statements directly. You don't need a live accounting connection for a first draft. Just the files. That matters if you're behind on the year and staring at twelve PDFs from online banking.

Here's the honest frame. This is a draft. A good one, usually. But a draft. You read it and fix it, the same way you'd check anyone's first attempt.

Want the wider setup first? The full Claude Cowork for bookkeeping walkthrough covers the whole workflow. This guide zooms in on one job. Books from statements. For the plain-language version of what the tool does day to day, the overview of using Claude for bookkeeping is a good primer.

Why statements are a good starting point

Statements are the raw record. Nothing's been categorized yet, so nothing's been miscategorized yet either. You're starting from the source, not from someone else's guesses.

Think about what a bank statement already is. A dated list of every dollar in and out, with a running balance and a stated ending figure. That's most of a set of books, minus the labels. The work Claude does is put a label on each line and add the two summary statements. The raw truth is already sitting in the file.

Claude reads scanned and image-based PDFs too. Old paper statements you scanned last spring still work. So do fresh exports from online banking. You bring what you have, in whatever shape it's in.

Set up a folder for the job

The setup is small. You point Claude at a working folder. That folder is the whole job. Your statements go in. Your finished files come out.

Pick your target chart of accounts before you start. The QuickBooks default is a safe, common choice. It's familiar, and most accountants read it without asking questions. You can hand Claude your own chart instead if you have one.

One thing worth saying plainly. You don't need the QuickBooks connector for this. Claude reads the statement files directly, so a first pass works without connecting anything. If you do want live data later, the step to connect QuickBooks to Claude covers it.

Your chart of accounts is the target

A chart of accounts is just the list of buckets. Rent, software, meals, income, and so on. Claude sorts every transaction into one of them. Give it a standard chart, and the output reads like real books, not a pile of guesses.

Why does a standard chart matter so much? Because the labels are what turn a bank feed into accounting. A row that says "$1,200, Rent" is bookkeeping. A row that says "$1,200, out" is just a bank line. The chart is the set of labels you're sorting into. Pick a messy one and the output is messy. Pick a clean, standard one and the output looks like books an accountant would recognize.

The six buckets a standard chart uses

The QuickBooks default chart groups everything into six kinds of account. Knowing the six helps you read the output and catch a bad sort fast.

• Income. Money you earn. Sales, service fees, anything a customer pays you.
• Cost of goods sold, or COGS. The direct cost of what you sell. Materials, inventory, the labor that goes straight into the product.
• Expenses. The running costs of the business. Rent, software, meals, utilities, insurance. Everything it takes to keep the doors open.
• Assets. What the business owns. Bank accounts, equipment, money customers still owe you.
• Liabilities. What the business owes. Credit-card balances, loans, unpaid bills.
• Equity. The owner's stake. Money you put in, money you draw out, profit left in the business.

Two math rules fall out of those six. Income minus COGS minus expenses gives you profit. That's the P&L. Assets equal liabilities plus equity. That's the balance sheet. Claude builds both from the same sorted transactions, so a clean sort feeds two clean statements.

You don't have to memorize this. But when you read the draft, a quick gut check helps. Is a loan payment sitting in expenses when it should touch a liability? Is an owner deposit tagged as income when it's really equity? Those are the sorts worth a second look. If you want the wider frame beyond the books themselves, the Claude for accounting overview covers the reports that sit on top.

What to drop in the folder

Now the easy part. Drop your statements in.

• PDF bank statements, one account or several.
• Card statements too.
• Scanned or image-based PDFs. Claude reads those.

No cleanup first. You don't have to rename files or sort by month. A year of raw exports is fine. Messy is expected.

Scanned statements, and where they break

Claude reads scanned statements and image-based PDFs, not just clean digital exports. So the stack of paper statements you scanned last spring works the same as a fresh download. You don't convert anything first.

The honest limit is scan quality. A crisp scan reads fine. A crooked phone photo of a crumpled page reads worse. A fax-quality copy where the numbers blur is where it starts to struggle. Handwriting is the hardest case of all. If you scribbled a note in the margin, don't count on Claude reading it right.

When a scan is bad, the fix is a better scan, not a better prompt. Lay the page flat, good light, straight angle, and re-scan. A clean image reads clean. This is worth knowing up front so you don't blame the sort when the real problem is a fuzzy input.

The prompt that categorizes everything

Here's the prompt. Copy it, point Claude at your folder, and send it.

Prompt: Categorize every transaction in these bank statements against the QuickBooks default chart of accounts. Build a balance sheet and a P&L. Flag any transaction you weren't sure how to classify.

What happens next. Claude reads every statement, page by page. It sorts each transaction into an account. Then it builds the two financial statements from what it sorted. You watch it work, and you can stop it any time to redirect.

That's the core of getting Claude to do your books. One prompt, one folder, real output.

How Claude builds pattern rules on the fly

This is the part that saves you time. Claude doesn't treat every line as a stranger.

Say it sees three charges from the same coffee shop, all tagged as meals. It notices the pattern. So it tags the fourth and fifth charges the same way, without asking you again. Recurring vendors get sorted automatically once the pattern is clear.

That's pattern learning. Not a black box. Just Claude spotting a repeat and applying it.

And when it isn't sure? It doesn't guess and hide it. It flags the transaction for a second look. A silent wrong guess is the one you can't catch later. A flag is one you can.

What you get back

Three files. That's the output.

• A categorized transaction spreadsheet: every line, with the account Claude picked.
• A balance sheet: built from the categorized data.
• A P&L: built from the same data.

The spreadsheet is where you'll spend your review time. It's the working document. The balance sheet and P&L follow from it, so fix the spreadsheet and the statements update.

Running several accounts and a full year at once

Real books rarely live in one account. You've got checking. Maybe a savings. One or two cards. And a year isn't one statement. It's twelve. The good news is you can drop the whole pile in one folder and let Claude read across it.

Order doesn't matter. Files named by month, files dumped at random, both work. The date on each transaction tells Claude where the line belongs. It reads the full set together, not one file at a time.

The thing to watch with several accounts is transfers between them. Move $2,000 from checking to savings and it shows up twice, once as a debit on checking and once as a matching credit on savings. Claude matches the two sides by amount and date and flags the pair. You'll clear that kind of flag in the worked examples below.

For a full year, the risk is a missing month. If March is gone, the running balance won't line up. Claude can't invent a statement it doesn't have. It'll flag the jump instead of papering over it. So gather the full run before you start. A quick check catches gaps early: each month's ending balance should match the next month's opening balance. If they don't, a statement is missing.

Review the flags first

Now the real work. And it's less than you think.

Start with the flagged pile. These are the transactions Claude wasn't sure about. Three reasons show up again and again: transfers between your own accounts, credit-card payments, and opening balances with no statement behind them. Each one is easy to misread, so Claude holds it for your call instead of guessing. The worked examples below show how you clear each.

Here's a prompt to walk the pile with you.

Prompt: Walk me through every transaction you flagged, grouped by reason. For each one, show me the category you'd suggest and why. Wait for my answer before you change anything.

Three worked examples from the flagged pile

The flagged pile sounds abstract until you see it. Here are the three that show up most, and how you clear each one.

The $2,000 transfer that isn't an expense. You moved $2,000 from checking into savings. On the checking statement, that's a $2,000 debit. If Claude counted it as spending, your P&L would show $2,000 of expense that never happened. When both accounts are in the folder, there's a second half to catch too. The matching $2,000 credit lands in savings, and on its own that looks like income. Claude sees the amounts match on the same date across two of your accounts, so it flags the pair. You tell it: same money, my own accounts. It codes both to a transfer, and neither one touches the P&L.

The credit-card payment that isn't spending. You paid your card $1,500. Money left checking, so it looks like an expense. But the spending already happened, on the card, when you bought things. If Claude counted the payment as an expense too, every purchase would be counted twice. Once as the card charge. Once as the payment. Claude flags the payment. You confirm it's a card payment. It codes it against the credit-card liability, which is you paying down what you owe, not a new cost.

The opening balance with nothing behind it. Your first statement starts with money already in the account. There's no deposit line showing where it came from, because it landed before this statement period began. Claude can't source what it can't see, so it flags the gap. You give it the opening figure and, if you know it, the reason. An owner contribution. A carryover from last year. It records that as opening equity, so the balance sheet starts from a true number instead of a hole.

Clear those three and you've handled most of what Claude will ever flag.

Then spot-check the confident pile

The flags are only half the review. The other half is the transactions Claude was sure about.

Here's the trap. A flag is Claude telling you it wasn't sure. But a wrong sort it was sure about won't carry a flag. It filed a charge with confidence, and it filed it the way most businesses would, which happens to be wrong for yours. No flag, because there was no doubt on Claude's end. Only on yours.

So read the confident pile too. Not every line. Spot-check. Scan the big-dollar transactions first, since a wrong sort there moves the statements the most. Then skim the vendor names you recognize and make sure each one landed where you'd put it. A software charge you treat as COGS, an owner meal you keep personal, a client refund that isn't really income. Those are the ones a general sort gets wrong and never flags.

The COGS-versus-expense split is the classic one. Say you buy $400 of raw material that goes straight into a product you sell. That's COGS. Say you buy $400 of office software the whole business runs on. That's an expense. Both are money out, and a general sort can swap them without a second thought. The split matters because it changes your gross margin, so it's worth a look when the dollar amount is real.

Treat the whole thing like a new hire's first categorization pass. Useful. Mostly right. Worth a real read before you sign off. If you'll do this every month, the Chat and Projects way to use Claude for bookkeeping shows how to keep context between runs.

Reconcile the balance sheet back to your bank

Here's the one check that tells you the draft holds together. Compare the cash on the built balance sheet to the ending balance on your last statement. They should match.

Say your checking statement ends at $8,412.55. If the balance sheet shows checking at $8,412.55, every transaction is accounted for. Nothing dropped, nothing doubled. That's a strong sign the sort is complete, even before you read a single category.

If the two numbers differ, the gap is the size of the error. A $2,000 difference points you straight at a transfer counted once instead of twice, or twice instead of once. A smaller odd figure often means a missing page or a misread line from a bad scan. An opening balance that's off throws the whole run by the same amount from day one.

Ask Claude to hunt the difference for you.

Prompt: Compare the checking balance on the balance sheet to the ending balance on my last checking statement. If they don't match, list the transactions that could explain the difference.

Run this for each bank and card account. When every account's built balance matches its statement, the books tie out. That's the moment a draft stops feeling like a guess and starts feeling like books. It's also the check a real bookkeeper runs, so building the habit now pays off whether you stay with Claude or move to a purpose-built tool.

Where a bank-statement first pass stops

Be honest about the ceiling. A statement pass with Claude is genuinely useful. For your own books. For a couple of simple clients. It gets you from a folder of PDFs to a reviewable draft in one sitting.

Here's where it stops. There's no per-client memory that carries your fixes forward across a roster. Fix the same vendor for one client this month, and next month, for the next client, you start over. And there's no built-in audit trail of who approved what across ten, twenty, thirty client books. Once you're running books for others, that gap gets expensive. The multi-client AI bookkeeping breakdown walks through why a roster needs more than a single folder.

That's the line where Growthy begins. Growthy connects to QuickBooks Online. It pattern-learns per client, so the same correction carries forward instead of getting re-taught. It reviews every transaction with you before it posts. And it runs 10 to 30-plus client books with an audit trail behind every change.

Same idea as this guide, built for volume. Growthy is that reviewable first pass at scale, with memory. Growthy is 85% accurate on first import. You review the rest. And if your work runs into tax season, our sister product TracePrep handles tax workpaper automation. That's the difference between a first pass for your own books and a system that runs a full roster of them.

Get started with Growthy. Get started and see what it catches on your first import.

Frequently asked questions

These are the questions that come up once you've tried a first pass from statements.

Can Claude really do my books from just bank statements?

Yes, as a first pass. It reads your PDF statements, categorizes every transaction, and builds a balance sheet and P&L. You review the draft before you rely on it. Think of it as a strong starting point, not a finished set of books.

Does Claude read scanned or image-based PDF statements?

Yes. Scanned statements and image-based PDFs both work. So do exports straight from online banking. You don't have to convert them first. The one limit is scan quality. A blurry or crooked scan reads worse, and handwriting is the hardest case, so re-scan a bad page rather than fight the sort.

What chart of accounts does it use?

Whatever you point it at. The QuickBooks default is a common, safe target, and most accountants read it easily. Have your own chart? Give Claude that instead, and it sorts against yours.

What are the main account types in a standard chart?

Six. Income, cost of goods sold, expenses, assets, liabilities, and equity. Income minus COGS minus expenses is your profit, and that's the P&L. Assets equal liabilities plus equity, and that's the balance sheet. Claude builds both from the same sorted transactions.

Do I need a QuickBooks subscription or the connector?

No, not for a first pass. Claude reads the statement files directly, so you can build a draft with no connection at all. If you want live QuickBooks data later, that's a separate setup step.

What does Claude flag, and why?

The transactions it isn't sure about. The usual three: transfers between your own accounts, credit-card payments, and opening balances with no statement behind them. Each one is easy to misread, so Claude flags it instead of guessing.

How does it handle a transfer between my own accounts?

It treats it as money moving, not money earned or spent. When both accounts are in the folder, it matches the debit and the credit by amount and date, then flags the pair so the same dollars don't count twice. You confirm it's your own transfer, and it codes both sides out of the P&L.

Is the output ready to file taxes from?

No. It's a first-pass draft, not a filing. Read every category and clear every flag first. Treat it like a new hire's first attempt. Useful, but it needs your sign-off before anything official.

Does it build a balance sheet and P&L, or just categorize?

Both. You get the categorized transaction spreadsheet plus a balance sheet and a P&L built from it. Fix the spreadsheet, and the two statements follow.

How do I know the books are complete?

Reconcile. Compare the cash on the built balance sheet to your last statement's ending balance. If they match, every transaction is accounted for. If they don't, the gap is the size of the error, and it usually points at a transfer, a missing page, or an off opening balance.

Can it handle several bank and card accounts at once?

Yes. Drop them all in one folder. Claude reads across every statement together and still flags transfers between your own accounts so they don't count twice.

Is it safe to hand Claude my bank statements?

Statements hold sensitive numbers, so it's a fair question to ask of any tool. Read up on how data is handled before you upload, and keep files where you control them. The AI bookkeeping data security overview covers what to check.

What if my account mixes business and personal spending?

Common when a sole proprietor runs everything through one account. Claude sorts every line into the business chart by default, so a personal grocery run can land in expenses. Tell it up front to flag anything that looks personal. On review, mark those as owner draws instead. They aren't business costs. They pull money out of the owner's equity. A quick pass to pull personal charges out keeps the P&L honest.

What if I'm running books for a lot of clients?

That's where a single-folder pass stops being enough. There's no memory that carries your fixes across clients, and no audit trail across a roster. A purpose-built tool covers that gap.

Where to start

Start small. Your own books, one folder, the prompt above. Read the flagged pile first, then spot-check the rest, then reconcile the cash back to your last statement. Once you trust the pattern, the same habit scales to a client or two. Past that, you'll want a tool that remembers.

Growthy is bookkeeping software, not a CPA firm. This content is educational, not professional advice.