How to Set Up Books from Bank Statements (No Receipts)

Sometimes the books were never set up in the first place. The business ran, money moved, and the year ended with nothing recorded and no shoebox of receipts to show for it. If that is where you are, the bank statement is what you have left — and it is enough to reconstruct a usable set of books from scratch.

This is a different job from starting clean. A general beginner's guide to bookkeeping from bank statements assumes you are setting up going forward, with receipts arriving as you spend. Here you are working backward through a year (or more) that already happened, reconstructing what you can from the statements alone. The method is similar, but the constraints and the honesty required are different.

Step 1: Gather every statement first

Before you categorize anything, collect a complete set of statements for the whole period you are reconstructing. A missing month leaves a hole that is hard to spot later, and partial books are worse than none because they look finished.

Pull statements for every account the business touched — checking, savings, credit cards, and any line of credit. If business and personal money mixed in one account, you still need all of it; you will separate the two later. Download each statement as a PDF and confirm the date ranges run end to end with no gaps. Note any account you can no longer access, because that is a documented gap rather than a forgotten one.

Step 2: Convert the statements to rows

You cannot reconstruct books from a stack of PDFs. The work happens in a spreadsheet with one transaction per row and columns for date, description, and amount. Typing a full year by hand is slow and introduces errors of its own, which is the last thing you want when the data is already incomplete.

Export each statement to structured rows instead. Many banks offer a CSV download for recent periods; for older statements or PDFs, run them through the bank statement converter to turn each one into clean rows. Stack every statement into a single sheet, sorted by date, so the whole period reads as one continuous ledger. Add a column for the source account so you can tell later which statement a row came from.

Step 3: Categorize from the descriptions

With everything in rows, work down the list and label each line. Without receipts, the description is your only clue to what each transaction was. A merchant name often tells you enough — a fuel station is travel, a software vendor is software, a recurring identical amount is likely a subscription or a loan payment.

Keep the category list short and consistent so you can total each bucket at the end. Income lines — deposits, client payments, transfers in — get labeled too, and they often need more care than expenses, because a deposit can be revenue, a refund, a loan, or an owner contribution, and only one of those is taxable income. When the description is a bare card-network code or a generic transfer, do not guess. The step that follows exists for exactly those lines.

Step 4: Flag what needs documentation

This is the step that separates honest reconstruction from invented numbers. Add a "Needs docs" column and mark every row you could not fully identify or that would need backup if questioned:

• Large or round-number payments with vague descriptions.
• Deposits you cannot confidently classify as income versus a loan or transfer.
• Anything that might be part business, part personal.
• Charges where the deductibility depends on what was bought, not just that money left the account.

These flags become your follow-up list. Some you can resolve from memory, a calendar, or an email trail; for others you can request a duplicate invoice from the vendor. Whatever you cannot back up stays flagged, so you and your tax preparer know which figures rest on a statement line alone.

Step 5: Separate business from personal

If one account carried both, mark each row business or personal. Personal spending is not a business expense and should be filtered out of your totals; treating it as a deduction is the kind of error reconstruction is prone to. A simple "Business?" column lets you filter to business rows and read the real totals, even though the underlying account was mixed.

What statements cannot tell you

Reconstructing from statements alone has hard limits, and naming them keeps the books honest:

• Statements show payments, not purchases. A line proves $300 left the account on a date. It does not show what was bought or whether it was deductible — that is what a receipt or invoice records. The statement is evidence the money moved, not evidence of the business purpose.
• Cash is invisible. Money taken in or spent as cash never appears. If the business handled cash, the statements alone will understate both income and expenses, and you will need a separate reckoning for it.
• Keep whatever receipts you can still find. Reconstruction is a recovery step, not a permanent method. Any receipt, invoice, or app report you can locate strengthens the corresponding row; attach or reference it and clear the flag.

The IRS expects businesses to keep records that support the income, deductions, and credits on a return — see the official guidance on recordkeeping. A reconstructed set of books built from statements is a reasonable starting point, but the flagged items are where you are still short of that standard, and they are worth closing where you can.

Putting it together

The reconstruction routine is: gather every statement for the full period, convert them into one dated ledger, categorize each line from its description, flag anything that needs backup, and split business from personal. What you end with is not a substitute for having kept records all along — it is the most defensible picture the available data allows, with its weak spots labeled rather than hidden.

Start with clean data. Run your statements through the bank statement converter to get categorizable rows, then work down the list. Once the structure is in place, keeping the books current going forward is far easier than rebuilding them was.