Home › Blog › Excel, CSV & Google Sheets › Google Sheets Bank Statement Workflow
Import a converted bank statement CSV into Google Sheets, protect the header, filter and sort safely, and total categories with simple formulas.
By StatementVerified Editorial · November 3, 2026 · 6 min read · Filed under Excel, CSV & Google Sheets
Google Sheets has quietly become the review desk for a lot of small bookkeeping practices. It opens anywhere, shares with a client in one link, and handles the sorting, filtering, and totaling that statement review actually requires, without the version chaos of emailed workbook copies. Used well, it is an excellent middle stage between converting a statement and importing it into accounting software. Used casually, it creates the classic shared-file problems: a client sorts one column without the others, a total quietly includes a header row, and nobody knows which tab is the real one.
This workflow sets Sheets up the way a careful bookkeeper would: a protected source tab that never changes, a working tab for review and categorization, formulas described plainly so anyone can audit them, and a clean export step that produces the import file. It suits monthly clients, year-end categorization passes, and any job where a client needs to answer questions inside the data itself.
Start a fresh spreadsheet for the client and period, and import the converted CSV into its own tab, choosing to replace or create a new sheet rather than appending to existing data. Name that tab plainly as the source, with the account and period in the name. Then protect it: Sheets lets you set a warning or a restriction on a range or a whole sheet, and the source tab deserves that protection because every later number traces back to it. Review and categorization happen on a copy, never on the source.
Before copying, verify the source tab against the statement: row count, credit and debit totals, and the walk from opening to closing balance. Doing this check on the imported tab rather than the raw file catches any reinterpretation Sheets applied on the way in, such as dates displayed in a new format or long references converted to numbers. If Sheets changed a value on import, fix the import settings or the source file now, while the comparison is still one screen wide.
Duplicate the source into a working tab and freeze the top row so the column headings stay visible while you scroll; on a long statement this one setting prevents most misreading. Turn on filters for the full data range so you can isolate a vendor, a month, or an amount range in seconds. Add your review columns to the right of the bank data: category, notes, and a question flag for the client. Keeping your columns separate from the bank columns matters later, because the export for import will take only the bank columns plus, where wanted, the category, in a known order.
Sorting deserves a warning you should give every client who will touch the file. Always sort the entire data range together, never a single column on its own. Sorting one column independently scrambles every transaction, detaching dates from amounts from descriptions, and the damage can look plausible at a glance. Sheets offers sort range tools that keep rows intact; use those, and say so in a note at the top of the working tab. Better still, do exploratory sorting on a second copy and keep the main working tab in statement order, which is the order reconciliation will expect.
The totals a reviewer needs are simple, and the formulas behind them should be explainable in a sentence each. A category total is a sum of the amount column for only the rows where the category column matches a chosen label: a sum-if calculation. A monthly total is the same idea keyed on the month of the date column. A grand total is a plain sum of the whole amount column, and its job is control: it must equal the statement movement for the period at every stage of the review, no matter how rows are categorized or flagged.
Put totals on a separate summary area or tab rather than in rows inside the data, because a total row inside the data range will eventually be sorted, filtered, or exported into an import file as a phantom transaction. On the summary tab, list each category with its total and a count of transactions, then a control line comparing the sum of all categories plus an uncategorized line against the statement totals. When the control line disagrees, stop and find the row that lost its category or its amount; do not adjust the total to make it agree.
Sheets earns its keep when the client joins the review. Share the working tab with comment access or edit access limited to the notes and answer columns, and ask the client to work down the flagged rows: what was this payment, is this transfer between your own accounts, is this purchase personal or business. Their answers land in the file next to the transactions, timestamped by the sharing history, instead of scattering across email threads you will have to reconstruct at year end.
Set a simple status convention: unflagged means categorized and agreed, flagged means waiting on the client, and a resolved marker means the answer has been applied. Review the file once a week during an active cleanup rather than letting questions age; a client answers a two-week-old question from memory and a two-month-old question from imagination. When every flag is resolved, lock the working tab by changing its protection, so the reviewed state that the import is built from cannot drift afterward.
Build the import file as its own clean tab: only the columns the importer expects, in the mapped order, one header row, dates in the agreed format, amounts in the agreed signed or split convention, and no totals rows, notes, or blank lines. Download that tab as a CSV and inspect it as raw text before importing, checking the first and last rows and one row whose description contains a comma. This export step is deliberate on purpose; downloading the working tab directly is how notes columns and summary rows end up inside ledgers.
Archive three things together in the client folder: the original converted CSV, a link or copy of the Sheets review file in its final state, and the exported import CSV. That trio tells the whole story of the data, from bank to books, and it makes the next month faster because the Sheets file becomes the template: same tabs, same columns, same formulas, new source data. Consistency across months is what turns a clever spreadsheet into a reliable system.
They can, with limits. Give clients access to the answer and notes columns on the working tab, keep the source tab protected, and keep your own review on a tab they do not restructure. The sharing history in Sheets gives you a record of who changed what.
A total that lives inside the data range can be moved, filtered out, or double counted when the range changes. Keep totals on a separate summary area that references the data, and keep a control total that must always match the statement movement for the period.
Some tools connect to Sheets, but the safer route is to export a dedicated clean tab as a CSV, inspect it as text, and import that file. The dedicated export prevents notes, totals rows, and extra columns from reaching the importer.
Excel, CSV & Google Sheets · November 3, 2026
Excel workbooks and plain CSV each win in different bookkeeping jobs. Learn the formatting risks of workbook round-trips and when to use each.
Excel, CSV & Google Sheets · November 2, 2026
Understand the two amount conventions in statement files, which importers expect each one, and how to convert between them without flipping signs.
Excel, CSV & Google Sheets · November 4, 2026
Remove header blocks, page-title rows, subtotals, blank rows, and stray characters from a converted bank CSV so it imports cleanly the first time.
Convert a statement now and watch the reconciliation check verify it against the statement itself.
Your first conversion is free — no card, no sign-up — and every result is reconciled against the statement itself before you download it.