Banking · Guide 29 of 53
Importing a bank CSV and confirming drafts
CSV import puts every bank line into a draft state; confirming each one decides what kind of journal it produces, and money already in the books is matched rather than counted twice.
Most of your bank activity will arrive via CSV import. The import landed safely is half the work; the other half is the confirm step, which is where you decide what each draft is and the engine posts the corresponding journal.
Where to start
From any bank account’s cashbook, click CSV import. The workspace handles file upload, column mapping, deduplication, and review.
Uploading a file
Drop the CSV your bank gave you onto the upload area. You don’t need to tidy it first. IQ Books:
- finds the real header row itself, so account details or a statement period printed above it are skipped;
- works out whether the file uses commas, semicolons or tabs;
- matches columns by what is in them, using the header names to break ties: the date, the description, the amount (one signed column or a Money in / Money out pair), a CR/DR marker column and the running balance. Sort codes, account numbers and IDs are left alone, so a wide statement with thirty columns is fine;
- reads dates written as 28/09/2026, 28.09.26, 2026-09-28 or 28 Sep 2026, and amounts written as 1,234.56, 12.50 DR, 500.00 CR, (45.00), 45.00- or 1.234,56.
The panel shows how many rows are ready. Any row that can’t be read says exactly why, for example Line 9, Amount: “abc” isn’t an amount we can read, so you can fix the file or the setup rather than guess. When the file has a Balance column, IQ Books also checks that it adds up line by line and tells you the line where it stops, which catches a wrong amount column or money in and out the wrong way round.
Advanced setup
For anything unusual, click Advanced setup. It shows the file exactly as it is, as a grid, with a box above every column where you say what the column holds: Date, Description, Reference, Amount, Money in, Money out, In / out marker, Balance, or Ignore. Click a line number to make that line the header; everything above it is skipped. Along the top you can change the separator, whether dates are day-first or month-first (with a live example), the decimal style, and flip money in and out. The ready count, any problem lines and the balance check update as you go.
The setup is remembered for that bank account: the next file from the same bank, with the same columns, reads the same way with no intervention. It is saved when you tick Remember for this bank account and whenever an import succeeds.
The import check
Before a single row is written, IQ Books compares the file against what is already on that bank account and shows you an Import check panel if anything needs a decision. Nothing is imported until you answer it, so re-importing an overlapping date range is safe.
A statement line is matched on date, direction and amount on the same bank account, as a running count rather than a one-off lookup — so if the books already hold one £4.50 coffee on 3 March and your file has two, one is treated as already there and the other as new. The description is deliberately not part of the match, because banks reformat it between downloads; the description already on the books is shown beside each line instead, so a wrong match is easy to spot.
The panel splits the file into three counts and two lists:
- Already in your books — these are left out unless you tick them. Each row shows the date, the description in your file, the amount, and the description of the transaction it matched. If that last column makes it obvious the two are different payments, tick the line to bring it in.
- Repeated inside this file — these are brought in unless you untick them. A statement listing the same amount twice on the same day is usually genuine: two card payments, a standing order that ran twice, a payout split into two settlements. They are shown only so the repeat does not look like the import having doubled something. Untick any that really are one payment listed twice.
- Genuinely new — everything else, imported without being listed.
The button counts what you have chosen and updates as you tick. “Import all anyway” overrides both lists and brings in every row in the file.
What lands
Every imported row creates a row in iq_books.bank_transactions with status Draft. Drafts are not yet on the ledger — they have no journal entry behind them. They show in the cashbook with the “Draft” status badge and a hatched balance line.
Until you confirm a draft, your trial balance is unchanged. This is the point: the import is non-destructive; the confirm decisions are where the ledger updates.
How a draft is confirmed
Banking → Bank account → Review drafts is the workspace where you confirm. A draft posts one of three ways, and Review asks first when it may be money already recorded or an invoice being paid:
1. Confirm as category (the default)
You pick a chart-of-accounts category (e.g. Office supplies, Software subscriptions, Sales) and a VAT code. IQ Books posts: debit/credit Bank against credit/debit the chosen category, with VAT split if non-zero. source_reference = bank_transaction:N.
This is the path for ordinary expenses and miscellaneous income that don’t correspond to outstanding documents.
2. Confirm as transfer
If the draft is money moving between two of your own bank accounts — same amount, opposite direction, on roughly the same date in two different banks — pick the matching draft on the other side. IQ Books pairs them, posts a single transfer journal that touches both bank accounts, and confirms both drafts at once. source_reference = transfer:A-B where A and B are the bank account IDs.
The Drafts workspace highlights potential transfer pairs automatically; you confirm with one click.
3. Confirm as invoice payment / bill payment
If a money-in draft matches an outstanding sales invoice (same customer, same amount, near date), or a money-out draft matches an outstanding bill, the suggestion appears as a one-click confirm. IQ Books creates the customer receipt or supplier payment, allocates it against the matched document, and posts the corresponding journal. source_reference = customer_receipt:N or supplier_payment:N.
4. Match it to money already in the books
Sometimes the money is already recorded before its bank line arrives: a receipt you entered with Record receipt, a payment from a payment run, a refund, expenses paid back to someone. Posting the bank line as well would count the money twice, so Review shows it under Already recorded, naming the record, with two answers:
- Match: the line takes that record’s journal. Nothing new posts. If several records fit, you choose which.
- It is separate money: the line posts as its own entry, and that pairing is not offered again.
A record fits when it is on the same bank account, the same way round and the same amount, dated up to 10 days before the line or 3 days after. Bank feeds and imports match on their own only when exactly one record fits.
Undo a match and the line goes back to Review; the record stays. Delete or reverse the record and the line comes back to Review with the coding it had. While a line holds a record, the line cannot be recoded, and the record’s amount and bank account cannot change. Undo the match first.
5. When it is exactly what an invoice still owes
A money-in line coded to an income account for exactly what an open invoice still owes is almost always that invoice being paid. Review marks it Invoice owed and offers Record payment, which settles the invoice, or It is new income, which posts it as income and leaves the invoice open.
Bulk confirm
The Drafts workspace supports tick-multiple-rows-and-confirm-as-the-same-category. Common patterns:
- 15 Stripe payouts in a row, all going to a Stripe Sales account — tick all, confirm as that category.
- 30 small recurring expenses to a single supplier — tick all, confirm as bill payments (assuming all 30 have matching open bills).
Bulk confirm, and Confirm all N coded, confirm each line in its own transaction, so a line that fails does not stop the rest. They are more careful than confirming one line yourself: anything that needs a decision waits for you rather than posting. Lines CodeIQ paired as a transfer are booked once, as one transfer between the two banks; lines it matched to an invoice or bill are recorded as that invoice’s receipt or bill’s payment (a part payment part-pays it), never as income or spending again. A match CodeIQ is less than 75% sure of, money that looks already recorded, a line that looks like an invoice being paid, a transfer whose other side was coded differently or is waiting, a line the bank feed is holding, and a payment for an invoice already paid all wait in Review for you, and the summary says how many. A split line posts as split. Confirming a single line yourself, by contrast, records a match even when CodeIQ was unsure: that is your decision.
Ignoring a draft
If a row is genuinely not relevant to your books (a personal expense paid through a business card with the intent of repaying personally, say), mark it Ignore rather than categorising it. Ignored drafts:
- Don’t post a journal.
- Stay in the cashbook with an “Ignored” status badge so you have a record of having seen them.
- Can be un-ignored later (which puts them back in Draft for review).
Bank rules and CodeIQ enrichment
Both bank rules and CodeIQ are workflows that pre-populate the confirm decision for you. They produce a suggested category and VAT code on each draft; you accept or override. Covered in their own guides.
Related guides
Adding A Bank Line By Hand
Not every transaction arrives in a CSV. Cash takings, a cheque you wrote, a bank charge the export missed, or the very first line of a brand-new cashbook all need entering by hand. The manual route sits alongside CSV import and lands in exactly the same draft state, so it flows through the confirm paths you already know.
- Open the bank account. In Banking, click the account card so you are looking at its cashbook.
- Add a transaction. Set the date, a description, the direction (money in or money out) and the amount. Enter the amount as a plain positive figure — you never type a minus sign; the money-in / money-out choice carries the direction.
- Categorise now or later. You can pick a category account and a VAT code straight away, or leave both blank and treat the line like any other draft to confirm later.
- Save. The line is created as a draft. Nothing reaches your accounts until you confirm it, so a half-finished entry can sit safely until you are ready.
Two rules keep manual lines honest: the amount must be greater than zero, and any VAT you record has to be smaller than the gross amount. You’ll need owner, admin or bookkeeper rights to add and confirm lines.
Getting VAT Right When You Confirm A Bank Line
When you confirm a draft, the VAT code you choose decides how much of the gross figure is treated as tax. IQ Books works the VAT out from the gross — you enter what actually left or entered the bank, and the code splits it for you.
- Standard (ST), 20%. The VAT is the gross divided by six. A £120 gross expense becomes £100 net plus £20 VAT.
- Reduced rate (RR), 5%. Used for things like domestic fuel and power; the VAT is the gross divided by twenty-one.
- Zero-rated (ZR) and Exempt (EX). No VAT is taken either way, but the two are not the same on the return — zero-rated supplies still count as taxable at 0%, exempt ones sit outside taxable supplies entirely.
- No VAT (NV). For anything outside the VAT system, such as wages, transfers between your own accounts, drawings and loan repayments.
- Reverse-charge codes. For overseas services, imported goods under postponed accounting, and CIS work, the line carries the net only. No VAT sits on the transaction itself — IQ Books self-accounts for both sides so it still lands in the right VAT-return boxes.
One thing that surprises people: if you categorise a bank line to a balance-sheet or control account — a loan, a director’s account, PAYE, or the VAT account itself — any VAT code you pick is quietly changed to No VAT. VAT only belongs on income, expense and asset lines, so IQ Books strips it rather than let you claim tax that is already accounted for elsewhere.
Correcting Or Removing A Line After You’ve Confirmed It
Ignoring or deleting works only while a line is still a draft. Once you confirm, the line has posted to your accounts, and IQ Books never quietly rewrites a posted entry. Instead it reverses the original and posts a fresh one, leaving both on the record as an honest trail. You don’t have to do anything special — you just recategorise or delete, and the reversal happens behind the scenes.
- Recategorise a posted line. Open the confirmed transaction, change the category, VAT code, date or description, and save. The old entry is reversed and a corrected one posts in its place.
- Fix several at once. Select up to 200 posted lines and apply one shared change, such as the same category or VAT code. Each is reversed and reposted on its own, so if one line can’t be changed the rest still go through; you get back a list of what succeeded and what didn’t.
- Remove a posted line. Deleting a confirmed transaction posts a reversing entry that cancels it out. If the line was one leg of a transfer between two of your own accounts, its partner leg is carried with it automatically so the two never fall out of step.
Corrections respect your locked periods. If a transaction’s date — the old one or the new one — falls on or before a period-lock or year-end-close date, the change is blocked; lift the lock first or date the correction after it.
Common Questions And Troubleshooting
- “I imported the same file twice.” No harm done. IQ Books recognises rows it has already seen and refuses the duplicates rather than doubling up your bank, so re-importing a statement to pick up a few new lines is safe.
- “The whole import failed because of one bad row.” An import is all-or-nothing — a single unreadable row rolls the entire batch back so you are never left with half a statement. Fix the offending row (usually a stray date or a blank amount) and import again.
- “I’ve got more than 10,000 lines.” That is the ceiling for one import. Split a long history into separate files by month or quarter and import them in turn; the duplicate check still protects any overlap.
- “Confirm is greyed out.” A line needs a category before it can post — that is the one field confirming can’t do without. Pick a category account, or if you genuinely don’t know yet, park it in Suspense (999) and recode it later.
- “It won’t confirm — it tells me to wait until the transaction date.” The line is dated in the future. Confirming only works once the date has actually arrived.
- “I clicked confirm twice.” Only the first click posts. A second confirm on the same line simply hands back the entry that already posted — it never doubles it.
- “It’s a transfer between my own accounts.” Import or enter both sides, let CodeIQ link the pair, then use the transfer confirm on either leg — a single journal moves the money and both legs are marked done together. If the two haven’t been linked, confirm each side the ordinary way by picking a category instead.
- “CodeIQ charged me but the coding failed.” In-app CodeIQ coding costs four credits a line and is charged when the job starts. Unlike a receipt scan, it isn’t refunded automatically if the run fails, so start a fresh run rather than waiting for the credits to come back on their own.
- “Does importing change my figures?” No. Imported and hand-entered lines are inert drafts — they don’t touch a single report or balance until you confirm them.