Skip to the guide
IQ Booksby ReconcileIQ

Banking · Guide 30 of 53

Bank rules: auto-categorising recurring transactions

Match a bank line by its description or exact amount, set the category and VAT code once, and every matching draft arrives coded. Rules are free, and the lines wait in Review for your Confirm unless you tick Post matching lines without review.

Half of your bank activity is the same handful of transactions repeating monthly: the same software subscriptions, the same utilities, the same fee on every card payout. A bank rule codes that repetition for you, free, every time a matching line arrives.

Where to find them

Banking → Bank rules lists every rule on the organisation, with its match, bank, direction, category and priority. A rule applies across all your bank accounts unless you tie it to one.

Making a rule

Click New rule and fill in the form:

  • Rule name. Something you will recognise in the list, such as “Stripe payouts”.
  • Strategy. How the line is matched: Description contains, Description regex or Amount equals.
  • Direction. Either, Money in only or Money out only.
  • Match value. The text to look for, the pattern, or the amount.
  • Bank. Any bank, or one bank account so the rule never touches the others.
  • Target category. The account matching lines are coded to.
  • VAT code. Optional. Leave it unset, or pick a code such as ST, RR, ZR, EX or NV. The VAT amount is worked out from the gross.
  • Priority. A number, 100 unless you change it. See below.
  • Post matching lines without review. Off unless you tick it. See below.

Click Add rule to save it.

The three strategies

  • Description contains. The line’s description contains your match value, ignoring capitals. The one most rules use. Keep the value short and distinctive, so a changing reference number does not stop it matching.
  • Description regex. The description matches a regular expression, ignoring capitals. A pattern that is not valid is refused when you save.
  • Amount equals. The line is exactly this amount, entered in pounds (14.99, not 1499). Useful when a supplier’s name varies in your bank narrative but the amount never does.

Direction and Bank narrow any strategy. A line has to pass all three to match.

Priority: which rule wins

Rules are tried from the highest priority number down, and the first one that matches codes the line. Two rules with the same number are tried oldest first.

Give a specific rule a higher number than a broad one. “Amount equals 120.00, money out” for business rates at priority 200 beats “Description contains COUNCIL” at 100.

When a rule fires

A rule only ever fills a draft that has no category yet. It runs:

  • when a bank feed line lands;
  • when a CSV import adds its lines;
  • when you add a draft by hand;
  • when you click Apply to all drafts on the rules page, which runs every rule over the drafts still without a category and tells you how many it coded.

A rule-coded line still waits in Review drafts. It usually sits in Ready, with the reason Your bank rule and the rule’s name, and posts when you confirm it. The exceptions: a line that looks already recorded, matches an open invoice exactly or is held waits in Needs you, and a line that looks paid in advance waits in Worth a glance, each with that reason instead. Unless you tick Post matching lines without review, a rule never posts a line on its own.

Post matching lines without review

Off by default. Tick it on a rule you trust and, while Post automatically when confident is on for the feed (Settings → Bank feeds), a new feed line the rule coded posts by itself. It skips the check that the merchant has posted to that account 3 times before. Every other check still applies: transfers, invoice matches, splits, VAT that needs a person (reverse charge, import VAT), a filed VAT period, a future date, a CIS subcontractor, a line that looks paid in advance and money already recorded all wait for you. CSV imports and lines added by hand never post by themselves.

A rule with it ticked shows Posts on its own in the list. Untick it to stop at once: the next feed pass reads the rule again. A line it already posted is an ordinary confirmed line, so send it back to Review the usual way if it is wrong.

Making a rule from Review drafts

The quickest way to make one. When a group of repeated lines in the review queue has a category, its … menu offers Always code <merchant> to <category> (a free bank rule). Confirming it creates a Description contains rule for that merchant, in that direction, on every bank, with the group’s category and VAT code, at priority 100. The lines still wait in Review for you.

Bank rules and CodeIQ

Both put a category on a draft. The order:

  1. Bank rule. Fires as the line lands, so a matching line arrives already coded. Rules are your explicit instruction, and they cost nothing.
  2. CodeIQ. Codes the drafts no rule caught, at 4 credits a line. It only codes drafts without a category, so it never replaces a rule’s choice.
  3. You. Anything left in Needs you waits for your pick.

Editing, switching off and archiving

Each rule in the list has three controls:

  • Edit (the pencil) opens the same fields, including Post matching lines without review. Saving changes what the rule does from now on. Lines it already coded keep their category.
  • Off / On switches the rule without losing it. A switched-off rule shows an Off pill and does not fire.
  • Archive removes it from the list. Lines it already coded stay as they are.

What rules don’t do

  • Rules never change a confirmed transaction, and never overwrite a category already on a draft.
  • Rules code to a category. A payment that settles a supplier bill or a customer invoice is better matched to that document in Review drafts, so the bill or invoice is marked paid and nothing is counted twice.

Related guides

Before A Rule Can Fire: Getting Lines Into Banking

A rule can only act on a bank line that is already sitting in your drafts, so there has to be something for it to catch. A draft gets there one of three ways: a bank feed brings it in, you import a statement, or you type a line in by hand. None of them touches your books until you confirm it, so all three are safe places for a rule to do its work first.

To import a statement:

  1. Open the bank account. Click Banking in the sidebar and open the card for the account the statement belongs to (add one first if you haven’t).
  2. Go to the CSV import tab. Drop in the CSV your bank gave you, or choose it from your computer.
  3. Check the columns. IQ Books finds the header row itself and works out which columns are the date, the description and the amount — one signed column, a Money In and Money Out pair, or an amount with a CR/DR marker — by what is in them. If anything is read wrongly, open Advanced setup and say what each column holds; the setup is remembered for that bank.
  4. Check the sanity totals. The preview shows total money in, total money out, the net movement, the period covered and how many rows were skipped. Compare those against your paper statement before you commit.
  5. Add the rows. They land in the review list as drafts, ready for a rule (or CodeIQ) to categorise.

A few things worth knowing about imports:

  • You can bring in up to 10,000 rows in one go.
  • Re-importing the same statement is safe: IQ Books recognises lines it has already seen and refuses the duplicates rather than doubling them up.
  • Any row it can’t read is left out and named, with the line, the column and the reason, so you know exactly what was left behind and why.

To add a single line by hand — a cash payment, a bank charge you spotted, anything not on a CSV — open the bank account, choose to add a transaction, and set the date, a description, the direction (money in or money out) and the amount. Enter the amount as a plain positive figure; it’s the direction that tells IQ Books whether it went in or out, so you never type a minus sign. You can pick a category and VAT there and then, or leave them blank for a rule to fill in. If you do add VAT, it has to be smaller than the gross amount. The line saves as a draft and stays out of your books until you confirm it.

A Worked Example: A Rule For Your Monthly Broadband

Say your business broadband leaves the current account as a £48 direct debit around the 3rd of every month, always described something like ‘BT GROUP PLC’. Here is the whole rule, start to finish:

  1. Open Bank Rules. Open Banking, then Bank rules, and click New rule.
  2. Name it plainly. Something like ‘Broadband — BT’ so you recognise it later in the list.
  3. Set the match. Choose ‘description contains’ and enter BT GROUP. Keep it short and distinctive — enough to catch the payment, not so much that a changing reference number stops it matching.
  4. Narrow it if you like. Set the direction to money out so it can never fire on a refund.
  5. Choose the category and VAT. Point it at your telephone & internet expense account and set the VAT code to standard-rated. IQ Books will work the £8 of VAT out of the £48 for you when you confirm.
  6. Scope it to the right bank. If only your current account pays this, tie the rule to that account so it never touches drafts on your savings or card.
  7. Give it a priority and save. Higher-priority rules are tried first, so a specific rule like this should sit above any broad catch-all.
  8. Apply it. Click Apply to all drafts to sweep your existing uncategorised drafts. From then on, every fresh import with a matching line is pre-coded the moment it lands.

Reviewing And Confirming After The Rules Run

Running Apply to all drafts fills in the category (and VAT) on every matching draft, but it deliberately stops there: the lines are still drafts and nothing has reached your accounts yet. That last step — confirming — is what actually posts each transaction. Keeping it separate gives you a chance to eyeball what the rules did before it becomes part of your ledger.

  1. Open your drafts. Go to the review list for the bank account. Lines a rule has touched now show a category and, where set, a VAT code; lines nothing matched are still blank.
  2. Scan the pre-coded lines. Check the category looks right. If a rule guessed wrong, just change the category on that one line — you’re overriding the rule for this transaction, not editing the rule itself.
  3. Fill in the leftovers. Any draft no rule caught still needs a category before it can be confirmed. Pick one, and set a VAT code if it isn’t Non-VATable.
  4. Confirm. Confirm the lines you’re happy with. Each one turns into a posted entry that moves the money between the bank account and the category, splitting any VAT out to the VAT control account for you.

Confirming has a few guard rails that are useful to understand when something won’t go through:

  • A category is compulsory. You can’t confirm a line that has no category — which is the whole reason to run rules first.
  • Future dates wait. A line dated in the future won’t confirm until its date has arrived.
  • Closed periods are protected. If the line falls on or before a locked date (for example a finalised VAT quarter or a closed year), the confirm is blocked so your filed figures can’t shift underneath you.
  • VAT is worked out for you. If a code carries a rate but you didn’t type an amount, IQ Books backs the VAT out of the gross — a standard-rated £60 payment splits into £50 net and £10 VAT.
  • Clicking twice is harmless. Confirming a line that is already confirmed simply returns the entry that’s already there; it never posts it a second time.

When To Match A Bill Instead Of Ruling It

A rule codes a bank payment straight to a category — it treats the money as a plain expense (or a plain receipt). That is exactly what you want for a broadband direct debit or a bank charge. It is not what you want when the payment settles a supplier bill or a customer invoice you have already entered.

If you let a rule code a supplier payment to, say, Materials, you will have recorded the cost twice — once on the bill and again on the bank line — and the original bill will still look unpaid. For those, skip the rule and use match to invoice on the draft instead: pick the outstanding bill, and confirming records the payment against it so the bill is marked paid and nothing is double-counted. A good habit is to point your rules at the recurring costs that never arrive as bills, and leave anything that settles a document to be matched by hand or by CodeIQ.

Common Questions And Troubleshooting

  • My rule didn’t fill anything in. The usual causes: the line already had a category (a rule never overwrites one that is already set), the description didn’t actually contain your match text, or the rule’s direction or bank excluded it. Rules also only look at drafts — a line you have already confirmed is off-limits.
  • I re-ran the import and expected the rule to redo everything. Rules only reach drafts that have no category yet, so already-coded lines are left exactly as they are. Change those by hand if you need to.
  • My VAT code turned into Non-VATable. You pointed the rule at a balance-sheet account (something like a loan, drawings or a control account). VAT only sticks to income, expense and asset categories; on anything else it is cleared to Non-VATable on purpose.
  • My regular-expression pattern was refused when I saved. A regex match value is checked the moment you save the rule; if the pattern isn’t valid, the rule won’t save until you fix it. If you don’t need pattern matching, use the simpler ‘description contains’ option.
  • Two of my rules could match the same line. The one with the higher priority wins, and only that first match is applied — so give the more specific rule the higher priority to beat a broad catch-all.
  • I archived a rule by mistake. Archiving a rule never unpicks transactions the rule has already coded, and those postings stay exactly as they were.
  • I clicked Apply to all drafts but nothing posted. That’s intended — applying rules only categorises the drafts. You still confirm them to post, which is your final check before anything reaches your books.

IQ Books by ReconcileIQ

Your books, kept by themselves.

IQ Books is the AI-native UK ledger that does the bookkeeping for you. Bank transactions arrive coded, receipts and bills file themselves from a photo or an email, and the books are reconciled to the statement. RiQ does it, you sign it off. The ledger is free.