Rules: fill in or import transactions your way

Tell Endute once how a kind of transaction should be handled, and it handles it that way every time one arrives.

What a rule does

A rule looks at each new transaction from your bank or a file. When a transaction matches the rule's conditions, the rule fills it in the way you chose: it can set the payee and the category, add tags and set the description. It can also import the transaction straight into your ledger, or make sure it always waits for you in review. Each rule reads as a plain sentence:

  • When bank text contains "applecare": set category Streaming & Media
  • When bank text contains "netflix": set category Subscriptions, import automatically
  • When payee is Tesco and amount is over 100: add tag Big shop

You build and manage rules on the web. They run on our side, so they work whichever device you review on: the app shows the payee and category a rule set, and the rule's description and tags are applied when you process an ordinary money-in or money-out transaction there, though the app does not show them first.

The Rules page

Open Rules from the sidebar, just below Payees & Categories (it is marked New for now). Your rules are listed in the order they run, top to bottom, each with its number. New rule opens the editor, and the search box finds a rule by its name or its summary.

When your rules imported transactions automatically in the last 30 days, a line under the title counts them. Review them lists those transactions, each with an undo button that moves it back to review, where you can check it yourself.

Each rule shows its name (or its summary, if you gave it no name) and badges for how it behaves: Imports automatically, Always review, Stops later rules and Off. A line underneath counts its work, such as Used 12 times · last on 3 Oct 2026, and adds how many it imported automatically. A rule counts as used when its work reaches your ledger; filling in a transaction that is still waiting in review does not count until you process it.

  • The switch turns a rule off without deleting it, and back on.
  • The grip on the left moves a rule up or down. The keyboard works too: focus the grip, press space to pick the rule up, the arrow keys to move it and space to drop it. While you are searching, the order cannot change: clear the search first.
  • The menu holds Edit, Duplicate and Delete. Clicking a rule's name opens it too. A duplicate is named after the original with (copy) and goes to the end of the list.
  • History lists each time the rule was applied to past transactions, with what it changed and an Undo button.

When you delete a payee or an account, we take it out of every rule condition that names it. A rule whose condition still names others keeps running. A rule whose condition named only what you deleted is switched off: it shows Not running and Off, with the reason underneath. Open it, choose another payee or account in that condition (or remove the condition), save, then switch it back on.

Deleting a rule

Transactions already in your ledger stay as they are, and new ones are no longer matched by the rule. Once it is deleted, its runs can no longer be undone, so undo any run you want to undo before you delete the rule.

Building a rule

New rule opens the editor. A name is optional; without one the rule is shown by its summary. The line This rule: shows the rule as a sentence and updates as you build it.

Conditions

Choose Match all of these (every condition must hold) or Match any of these (one is enough). Each condition picks what to check, how to compare and a value. Add a condition adds another, up to 20, and ticking Not on a condition matches the opposite, so contains becomes does not contain. The list of fields says what each one checks, and the information button beside the chosen field explains it again: hover over it, or tap it on a touch screen.

  • Bank text: contains, is, starts with, ends with, or contains one of (type several values, separated by commas). It looks at everything the bank sent at once: the description, the names of who paid and who was paid, and the merchant name we recognised. It is the simplest way to catch a transaction. Under More fields you can narrow it to just the Description (the bank's own wording, even if you changed it in Endute), Counterparty (the names of who paid and who was paid) or Merchant (the merchant name we recognised, for example Amazon from "AMZN MKTP UK").
  • Amount: is, is under, is over, is between, or is about (within a margin you set, 10% to start with). Type a plain number: the box has no currency symbol.
  • Money in or out: Money out or Money in.
  • Account: is one of the accounts you pick.
  • Payee: is one of the payees you pick. As the editor says, Checks the payee a transaction is already linked to. To catch new ones, use Bank text. So it acts only on transactions Endute has already linked to that payee. With Not ticked, it also matches transactions not yet linked to any payee.

How text and amounts are compared

Text matches whole words, and capital letters, apostrophes and punctuation make no difference. So contains "apple" matches APPLE.COM/BILL but not applecare, and is compares the whole text, word for word. A very short value made of several pieces, such as M&S, must appear as written (capitals aside). An amount is the size of the transaction whichever way the money moved (use money in or out for the direction), in the transaction's own currency, without conversion. is under and is over leave the amount itself out; is between includes both ends.

What the rule does

Under Then, choose any of a Payee, a Category, tags under Add tags (type a new name to create one) and a Description. Each starts as, for example, Leave the payee as it is, and a box left that way changes nothing on the transaction.

The category list offers only categories without subcategories. When the rule matches all of its conditions and one of them is money out, only expense categories are offered; with money in, only income categories.

Book as: transfers and loan repayments

Above Then, Book as says what kind of transaction the rule makes. Spending or income is the usual kind, with a payee and a category. The other two take no category:

  • Transfer: money moving between two of your accounts. Choose the Other account: money out goes to it, money in comes from it. Both sides are booked, so the other account's balance moves too. When that account has its own bank connection, its bank's copy of the transfer is matched to the side we booked, not added twice. When the two accounts use different currencies, the amount on the other account is worked out at the day's rate: check it against your statement.
  • Loan repayment: a payment towards one of your loans, money out only. Choose the Loan and the Interest category the interest is budgeted under, and give it a payee (usually the lender). The interest is worked out from the loan's rate and balance, and any payment extras come from the loan's own settings; the rest pays down the loan.

A Make a rule from a transaction you have set up as a transfer or a loan repayment starts as that kind.

Handling

  • Fill in for review, the default: the transaction waits in review, filled in, for you to check.
  • Import automatically (skip review): the transaction goes straight into your ledger.
  • Always send to review: never imported automatically, even when another rule says so.

Tick Stop later rules and, when this rule matches, the rules below it are not checked.

The order rules run in

Rules run top to bottom, and every rule that matches applies, not just the first one:

  • When two rules set the payee, the category or the description, the lower one wins.
  • Tags add up: the transaction gets the tags of every rule that matched.
  • Always send to review beats Import automatically, wherever the two rules sit, unless a rule above it with Stop later rules has already ended the run.
  • Stop later rules ends the run at that rule.

Your rules come first: what a rule sets wins over what Endute learned from your past choices and over our automatic merchant suggestions. A useful pattern is general rules higher up and specific ones below them, so the specific rule has the last word. Or put the specific rule first and tick Stop later rules.

When a transaction stays in review anyway

Import automatically only books what it can book safely. A matching transaction still waits in review, filled in, when:

  • it looks like a transfer between your own accounts;
  • it has no payee, because no rule sets one and Endute has none to suggest;
  • it has no category that fits it (an expense category for money out, an income category for money in), whether from the rule, from Endute's suggestion or from the payee's default category (the category review fills in from your last three transactions with the payee is not used here);
  • it matches a scheduled transaction or one you entered by hand (shown as Matched), so you can match it to that instead;
  • its amount is zero;
  • another matching rule says Always send to review.

A rule that books as a transfer or a loan repayment needs no category, and a transaction that looks like a transfer is exactly what a transfer rule expects. It still waits in review, filled in, when:

  • the other account or the loan has been closed or deleted (the rule shows Not running);
  • Endute has already paired it with the other side of a transfer, or it is a move to or from a savings pot;
  • for a transfer, the other side is already booked on the other account (its own bank or imported-file transaction: accept it and Endute pairs the two), the other account is an investment account your broker keeps in sync, or there is no exchange rate for the day;
  • for a loan repayment, the loan is in another currency, the loan has its own bank connection, a scheduled repayment of that loan enters itself automatically, there is no payee, or the loan has no interest rate (or a balance we cannot work the interest out from);
  • a repayment of that loan with interest is already booked for the same month, so an overpayment always waits for you. An interest-only loan's repayments always wait for you, filled in with the interest, since nothing tells an overpayment from the interest due.

Only the transfer or loan repayment rule's own Import automatically books it that way: another matching rule's never does.

Rules also fill in older history you import in one tap, after connecting a bank or with Import all for a file: the payee, category, description and tags only. That import brings the rows in anyway, so the handling choices make no difference there, and transfers are left as they are. Rules that book as a transfer or a loan repayment sit that import out.

See what it matches before you save

Under the form, What this rule matches checks the rule against what you already have as you build it, for example Matches 3 waiting in review and 40 in your ledger. 12 in your ledger would change. Two lists, Waiting in review and In your ledger, would change, show the transactions, each ledger one with its before and after, such as Category: None → Food > Groceries. A transaction whose category the rule cannot use says so and keeps its category. Each list shows the first 200; the counts cover every match.

Apply a rule to past transactions

Saving a rule changes nothing you already have: it works on transactions as they arrive. To bring the past into line, tick Also apply to the N transactions this would change or fill in under the preview. It starts unticked. Once ticked, every match is included and each row in the preview gets a tick box: untick any you want to leave out. The button then reads Save and apply to N and shows its progress while it works.

In your ledger, applying changes the payee, category and description of the matching transactions and adds the rule's tags (it never removes tags). Waiting in review, it fills in the matching transactions, or imports them where your rules say so. Waiting transactions are checked against all your rules, so one that another rule imports automatically can be imported. A message then sums it up, such as 12 changed in your ledger, 3 imported and 5 filled in for review. If it stops before the end, the message says how far it got and offers Continue, which carries on from there and keeps the rows you left out.

What applying never changes

  • transfers, loan repayments, split transactions, refunds and category credits;
  • estimates a scheduled transaction entered, still waiting for the bank to confirm them;
  • transactions on investment accounts.

Nor does it import a waiting transaction that a transfer, a scheduled transaction or one you entered by hand already covers: it is filled in but stays in review, so you can match it.

A rule that is switched off cannot be applied: switch it on first.

A rule that books as a transfer or a loan repayment applies to transactions waiting in review and to new ones only: the transactions already in your ledger stay as they are.

Undo

The message after an apply has an Undo button, and every run stays in the rule's History with its own. Undo puts back what the run changed. Anything you have changed since stays as you left it, and the message says how many were left that way. A transaction the run imported goes back to review, filled in, unless you have changed it or attached something to it since. For a transfer or a loan repayment that means every part of it: both sides of the transfer, or the repayment with its interest and the loan side. What a run filled in on transactions still waiting in review stays filled in: change it there if you need to.

Rules in the review queue

A transaction a rule filled in says so on its row: Rule: <name>, or N rules when several matched; hover over it to see which. Its description and tags come from the rule, and you can change or remove them before you process it.

A transaction a transfer or loan repayment rule filled in starts as that kind, with the other account or the loan chosen and, for a loan repayment, the interest worked out. If you book it as spending or income instead, the rule's description and tags are left off. In the app, which does not show the rule's choice yet, you book it as you choose; with Import automatically, the rule books it on our side whichever device you use.

Every row also has a Make a rule button (the wand icon). It opens the editor already set up from that transaction: a bank text condition taken from it, whether the money went in or out, and the payee, category (when it fits) and tags the row has now, so you only adjust what you need. The rule can be saved only while it matches the transaction you started from; otherwise the editor says This rule would not match the transaction you started from.

Rules in the payee and transaction dialogs

  • When you edit a payee that your rules mention, its dialog shows Rules that mention this payee: N · Manage rules. Manage rules closes the dialog without saving and opens the Rules page showing just those rules, with a Payee: <name> chip. Remove the chip to see every rule again and to change their order.
  • When you edit a transaction a rule touched, its dialog says so under the description: Filled in by rule <name> on <date>, Imported by rule <name> on <date> or Changed by rule <name> on <date>.

Your per-payee auto-import

The Auto-import switch in the payee dialog, the amber lightning icon on the Payees tab (under Payees & Categories), and the Automate offer and Auto button in review all keep working. Each per-payee auto-import appears on the Rules page as a rule named after its payee, set to import automatically, and you can edit it there. Change only its category and the payee's switch stays in step; give it another payee, condition or action and it becomes an ordinary rule, managed on the Rules page only. In the app, the Auto-Import Rules screen (under More) can switch these on or off or delete them; new ones are made on the web.

What next

Rules work best on top of good payees: the payees guide covers default categories and matching texts, and reviewing imported transactions covers everything a rule leaves for you to check.