Banking · Guide 32 of 53
Coding your bank with CodeIQ
One click runs every uncoded draft through CodeIQ’s eight-phase pipeline. The review queue then sorts the lines into Ready, Worth a glance and Needs you, each with the reason it was coded that way.
CodeIQ is ReconcileIQ’s coding engine. Inside IQ Books it codes your bank drafts: a feed codes new lines as they land, and the Code with CodeIQ button codes the drafts from a statement. Every line then shows in the review queue with its category, its confidence and one plain sentence on why.
When to use it
Bank rules are best for predictable recurring transactions. CodeIQ handles the rest: the long tail of one-off purchases, ad-hoc payments, transfers and miscellaneous income that don’t justify a rule.
Typical use: import a month’s CSV, let your rules catch the repeats, run CodeIQ once over what is left, then work down the review queue.
What it does
Each draft goes through CodeIQ’s eight-phase pipeline, which asks:
- Is it a transfer? Equal and opposite lines between your own accounts are paired first, and not charged.
- Does it settle an invoice or bill? The amount and timing are matched against your outstanding sales invoices and supplier bills.
- What category should it go to? From how your own books have coded this merchant before, the universal pattern database, the card merchant category, and the meaning of the description.
- What VAT code applies? Standard, reduced, zero, exempt or none.
How to run it
- Open
Banking → Bank account → Review drafts. The button Code with CodeIQ (N) sits in the panel header, where N is the drafts with no category and no suggestion yet. It is hidden when there is nothing left to code. - Click it. A dialog shows the drafts to code and the rate, 4 credits per transaction, with transfers paired first and not charged. Click Code N drafts.
- The button reads Coding… while the pipeline runs, typically 10 to 30 seconds for a month of drafts.
- When it finishes, the queue sorts every line by how much you are needed.
Reading the review queue
Three sections, in this order, with a count for each at the top:
- Ready. Coded at 90% confidence or more, or chosen by you or a bank rule (unless it looks already recorded, matches an open invoice or looks paid in advance), or Proven by your books (this merchant has gone to this account at least 3 times this year). Repeated lines are grouped by merchant, so twelve card takings are one row.
- Worth a glance. Coded at 75% to 89%: probably right, read it before it posts. Invoice and bill matches, and transfers paired across your banks or against a line already posted, always land here or lower, never in Ready.
- Needs you. Below 75%, no category, something odd, or money that looks already recorded. The small label in front of the reason says which: Not coded, Low confidence, Check, Already recorded, Invoice owed or Choose document.
Lines a feed is still settling (the other half of a transfer, a payout) sit in the Waiting panel below.
Each line’s reason says where its category came from, for example Coded the way your books have coded this before, A known merchant, coded the way most businesses code it, Matched on meaning, not a known merchant, Coded from the merchant’s card category or Your bank rule.
Confirming
Each line has one main button, named for what it does:
- Confirm posts a line coded to a category.
- Confirm transfer books both halves as one transfer.
- Pay bill (or Pay bills) settles a matched supplier bill; Apply settles a matched sales invoice. Part payments that clear one document together read Pay all N or Apply all N.
- Record payment appears when the line is exactly what an open invoice still owes, so it is recorded as that invoice’s payment.
- Match (or Match… when there are several candidates) links money already recorded in your books instead of counting it twice.
To clear many at once, use Confirm all N ready on the Ready section, Confirm these N on Worth a glance, or Confirm all N coded in the panel header, which takes every draft with an account chosen, whichever section it is in (hover it to see how they split). A confirm can be undone from the Undo bar for a few seconds after.
When CodeIQ is not sure
When CodeIQ has a guess it is not sure enough to fill in, or now suggests something different from the category on the line, the line shows a suggestion chip reading Account · NN% Use. Click it to take that category, then confirm. Or pick a different category from the dropdown.
What CodeIQ learns from
- Your own books. Each run reads how this organisation has coded each merchant, and the latest treatment wins. Confirm a line and drafts from the same merchant can pick up that coding straight away, with the reason Coded the way you just confirmed and the merchant’s name.
- The universal pattern database. Anonymised merchant-to-category patterns contributed with consent by CodeIQ users.
- Built-in VAT classification for the standard cases.
- Transfer detection and invoice matching, which read your other banks and your outstanding documents live.
Bank rules and CodeIQ
A bank rule fires as the line lands, so it codes first. CodeIQ only codes drafts with no category, so it never replaces a rule’s choice. The reason on the line always says which one coded it.
Privacy and data handling
CodeIQ runs server-side. Your transaction descriptions are sent to the pipeline for classification, but:
- Your amounts and your customer and supplier names are never published to the universal pattern database.
- Only abstracted merchant patterns (e.g. “NETFLIX” → “Software subscriptions”) are shared, after personal details are stripped.
- Contributing patterns is optional and needs your consent; you can switch it off again at any time in CodeIQ’s settings. The privacy policy sets out how contributed patterns are handled.
When CodeIQ is wrong
Change the category before you confirm. Once the line is posted it is part of your books, and the next run reads your books, so the same merchant follows your correction from then on.
If a class of transactions keeps needing the same correction, make a bank rule for it instead. A rule fires the same way every time and costs nothing. The queue offers one on any coded group: Always code <merchant> to <category> (a free bank rule).
Related guides
In-App Coding Or The Full CodeIQ Workspace
CodeIQ reaches your bank drafts two different ways, and it helps to know which one you are using.
- In-app coding. The Code with CodeIQ button on a bank account’s Review drafts tab. It writes a suggested category, VAT code and contact straight onto each draft and leaves them sitting there for you to review. Nothing posts — you stay inside IQ Books the whole time.
- The full CodeIQ workspace. The Or let CodeIQ bookkeep this account band on the CSV import page, or Let CodeIQ do the bookkeeping on Bank accounts. This opens the dedicated CodeIQ workspace in a separate view, codes the whole statement there in one pass, posts the finished results back to your ledger, and returns you to Review drafts.
Use in-app coding when you want to keep a hand on every line before it posts. Use the full workspace when you are clearing a large statement and are happy for CodeIQ to do the heavier lifting end to end. Either way the drafts are the same drafts — you can start with in-app coding and move to the workspace later.
Working Through The Suggestions
After an in-app run, every draft on the Review drafts tab carries what CodeIQ found, each with a confidence level. Two counts on the buttons tell you where you stand:
- Coded drafts. Rows one click can actually post — they already have a category, or a matched transfer or invoice. The Confirm N coded drafts button posts exactly these.
- Low-confidence rows. Rows where CodeIQ has a guess but isn’t sure enough to hand you a category. They are counted separately because they still need a human to pick.
- Deal with the sure things first. Click Confirm N coded drafts to post every row CodeIQ is confident about in one go.
- Accept a low-confidence guess. On a low-confidence row, click the suggestion chip (it shows the account, the confidence and Use) to accept it.
- Fix the rest by hand. Anything left over gets a category the normal way — pick the account, set a VAT code if needed, and confirm.
- Work in bulk when it’s faster. Tick several rows to bring up the bulk bar, then confirm them, apply one category across them, or delete them together.
The drafts list shows 100 rows to a page, so on a long statement clear one page before moving to the next. Confirming is safe to repeat: click it twice on the same row and nothing double-posts — the second click simply returns the entry that already exists.
More Than A Category: Transfers And Invoice Matches
CodeIQ doesn’t only pick an expense or income account. When it recognises what a line really is, it suggests the right treatment instead:
- A transfer between your own accounts. When money leaving one of your bank accounts matches money arriving in another, CodeIQ links the two sides. Confirming the transfer posts a single movement between the two banks rather than treating each side as separate income and expense, so nothing is double-counted.
- A payment against an outstanding invoice or bill. When a receipt matches a sales invoice you raised, or a payment matches a supplier bill, CodeIQ offers to settle it. Confirming records the receipt or payment against that document and marks it paid — it does not post a fresh category journal, so the invoice or bill is properly cleared instead of counted twice.
Direction has to agree for a match to stick: money coming in can only settle a sales invoice, and money going out can only settle a supplier bill. If the amounts differ, a same-currency shortfall is treated as a part payment and the rest stays outstanding.
How CodeIQ Fills In The VAT
CodeIQ suggests a VAT code alongside the category, but it usually leaves the actual VAT figure blank and lets IQ Books work it out when you confirm. That is normal — the code is the important part.
- Standard 20% (ST). The VAT is taken as one-sixth of the gross. A £120 card payment coded to an expense at 20% posts £100 to the expense and £20 to VAT.
- Reduced 5% (RR). The VAT is gross × 5 ÷ 105. A £105 gross line posts £100 net and £5 VAT.
- Zero-rated, exempt or no VAT (ZR / EX / NV). No VAT is added — the whole amount is net.
One safeguard runs on its own: if the category you choose is a balance-sheet or control account (a liability, equity or suspense account), any VAT code is dropped to Non-VATable, because VAT only belongs on expense, income and asset lines. This stops stray pennies of VAT landing where they shouldn’t.
Give reverse-charge situations a second look. Codes such as the CIS domestic reverse charge (DRC and DRR), overseas services and imported-goods postponed VAT record the net only and account for the VAT on both sides for you — there is no VAT amount sitting on the transaction. CodeIQ tends to reach for standard 20% by default, so if a line should be reverse-charge, set that code yourself before confirming.
Credits, Failures And Common Questions
Coding with CodeIQ costs 4 credits per draft, and the charge is taken up front — before the run starts — based on how many drafts you are coding. A few things are worth knowing.
- A failed run is not refunded. Unlike receipt scanning, which returns your credits automatically if it fails, bank coding does not. If a run doesn’t finish you have still paid for it, so it pays to get the drafts right first.
- Coding is not posting. An in-app run only writes suggestions. Nothing reaches your ledger, your reports or your VAT return until you confirm the drafts. If your balances haven’t moved after coding, that is why — you still need to confirm.
- Only uncoded drafts are charged. The button counts the drafts that don’t already carry a suggestion, so re-running after a partial pass doesn’t pay twice for lines already coded.
To keep the bill down, import your statement and check the totals band first so you are coding clean data, and let your bank rules clear the obvious repeats before you spend credits on the rest.
A confirm won’t go through. Two rules block a confirm no matter how good the suggestion is: a line dated in the future won’t post until its date arrives, and a line dated on or before a locked period-end is blocked so you can’t disturb a closed period. Change the date, lift the lock, or leave the line as a draft.