An admin or subscriber switches auto-reconcile on for each bank account, on a plan that includes it, such as Growing and above on Xero's USD price list. To check it, open Review reconciled, filter by method (Rule, Match, Memory or Prediction), look at why each line matched, and edit or remove and redo anything wrong.
Xero says JAX reconciles a line only when it is highly confident, and it works on new statement lines after you switch it on. The catch is that a confident match can still be wrong, and a Xero staff reply on its community forum says there is no way yet to mark transactions as reviewed. So the control has to be yours: a short weekly routine and a log. Xero's Help Centre covers where the buttons are. What follows is what to look at on each line, and how often.
Before you switch it on: plan, role and three things to tidy
Availability depends on plan and region. On the USD price list I read, automatic bank reconciliation is included on Growing ($59 a month list) and Established ($97), and Early ($27) lists it as an optional add-on at $5.00 a month. Other regions use different plan names. The regional product pages I read say it is available from the Grow plan upwards and describe an optional add-on called AI Automate for the lower plans, so match the pattern to your own plan comparison rather than assuming the USD names. Xero's August 2026 product update still called the feature beta; its November product page does not use the word, so look at how your own organisation labels it.
An admin or subscriber can switch it on, and it applies to new lines. That makes the order of work matter. Tidy these first:
- Bank rules. A Rule match is applied "when a bank rule applies", so every stale or over-broad rule becomes a confident wrong answer. Read the list, delete rules for suppliers you no longer use, and tighten any rule that matches on a short word.
- Open bills and invoices. Match works from existing Xero records. Duplicate bills and invoices that were paid some other way give it wrong candidates, and community posts report matches offered on the amount alone. Clear them first.
- The backlog. Reconcile or park what is already waiting, and write down the date you switch the feature on. Anything before that date was your work; anything after it needs the review routine.
Pick one account to start, ideally the one with the most repetitive lines, such as the card or the main current account. Xero's own update post talks about enabling it on one of your own bank accounts, and starting with a single account is sensible for the same reason.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowSwitching on one account and recording the starting point
Xero keeps the click-by-click path in its Help Centre article on using automatic bank reconciliation, and a Xero staff reply on its community forum points to the Auto-reconcile settings button on the main Bank Reconciliation screen as the place to manage it. Follow Xero's current article for the exact menu names, because they change. Before you press anything, record four things in a one-line log: the account, today's date, the number of unreconciled lines, and the date of your last clean reconciliation.
After the switch, new statement lines are reviewed by JAX as they arrive. It reconciles the ones it is confident about; for the rest it suggests a match and learns from your corrections. Give it a normal week before you judge anything, then start the routine below on the first Friday.
What each label means for the way you check it
Xero's page lists four ways JAX reconciles a line, and you can see which one was used. Each deserves a different kind of suspicion. The sampling rates are my rules of thumb, not Xero's.
| Label | Xero's wording | How it goes wrong | What to check | Sample |
|---|---|---|---|---|
| Rule | When a bank rule applies | A stale or broad rule codes a different supplier with full confidence | The rule's name and the last three lines it touched; fix the rule, not each line | 25% for the first four weeks, then 10% |
| Match | When the transaction matches an existing Xero record | Right amount, wrong customer or bill; a duplicate; a partial payment | Payee, reference and date against the document it picked | 25%, plus every line over $1,000 |
| Memory | Based on how you have reconciled similar transactions | Repeats your own earlier mistakes; users report it can override a rule | Account code and tax rate against what the payment was for; every new payee | 25% |
| Prediction | Based on how other Xero users reconciled similar transactions | Generic coding that fits their accounts, not yours | Every line for four weeks, then a fifth of them | 100%, then 20% |
On 28 October 2026 Xero's community manager wrote that Review reconciled is now the main review step, and that you can filter it by reconciliation method and see why each transaction was reconciled. Xero's product page adds that every reconciled line carries a label (Rule, Match, Memory, Prediction, or Manual for lines a person reconciled), and hovering over it shows the reasoning. If the filter has not reached your organisation yet, sort or scan by the label column instead.
The weekly 20-minute review, in order
- Open and scope (2 minutes). On Review reconciled for the account, set the date range to the last seven days. Note the number of auto-reconciled lines in your log.
- Count by method (3 minutes). Filter by Rule, Match, Memory and Prediction in turn and record the counts. A sudden jump in Memory lines is worth a look, because it means JAX is leaning on your past coding.
- Check the sample (10 minutes). Take the sample from the table above and ask the six questions below of each line.
- Fix and log (3 minutes). Edit or remove and redo, and write one line per correction: the line, the label, what was wrong, what you changed.
- Decide (2 minutes). Work out the week's error rate. If more than one sampled line in ten was wrong, extend the check to every Memory and Prediction line that week, and if it happens twice in a row, pause the account.
| Question | What to look at | Typical failure |
|---|---|---|
| Is the amount right? | Bank line against the document or the usual amount for this payee | An electricity charge at more than double the usual figure that matched a catch-up bill |
| Is the date plausible? | Bank date against the invoice or bill date | A payment matched to an invoice raised after the money arrived |
| Is it the right payee or customer? | Name and reference on the line against the record | Two customers with similar names and the same amount |
| Is the account code right? | What the payment was for, not what it was last time | A personal course coded to staff training |
| Is the tax rate right? | The rate on the coding against the document | A zero-rated item picking up a standard rate from memory |
| Is it a duplicate? | Open bills and invoices for the same payee and amount | An insurance payment reconciled while the insurer's bill is still open |
A filled-in week: eight sampled lines at a yoga studio
Here is an illustrative second week for a yoga studio's main current account. JAX reconciled 31 lines: 9 by Rule, 6 by Match, 15 by Memory and 1 by Prediction. Using the sample rates above (25% of Rule and Match lines in the first four weeks, 25% of Memory, all Prediction), the owner's bookkeeper sampled eight.
| Day | Bank line | Amount | Method | Coded to | Verdict |
|---|---|---|---|---|---|
| Mon | LANDLORD RENT | -$2,400.00 | Rule | Rent | Correct |
| Mon | CLEANING CO | -$180.00 | Memory | Cleaning | Correct |
| Tue | MAT SUPPLIER | -$642.50 | Match | Bill SUP-2291 | Correct |
| Tue | WORKSHOP DEPOSIT REF 1190 | +$150.00 | Match | Invoice INV-1187 | Wrong invoice: same amount, but the reference points to INV-1190 |
| Wed | ONLINE ADS | -$95.00 | Memory | Advertising | Correct |
| Wed | ACADEMY FEES | -$320.00 | Prediction | Staff training | Wrong: the owner's personal course, so owner's drawings |
| Thu | ELECTRICITY | -$212.40 | Rule | Utilities | Query: the usual bill is about $92 |
| Fri | INSURANCE | -$118.00 | Memory | Insurance | Query: the insurer's $118.00 bill is still open |
Two of eight lines were wrong, a 25% error rate against the one-in-ten trigger, so the bookkeeper extended the check to the other 12 Memory lines and found one more, a zero-rated purchase carrying a standard rate. The two queries were resolved by phone and by looking at open bills: the electricity bill included a catch-up for a missed meter reading, and the insurance payment had been reconciled while the insurer's bill stayed open, which would have left the same cost counted twice. The log for the week read: four issues, three corrections plus one duplicate bill removed, no rule changes. It was the first of the two bad weeks needed to pause, and the next week came back at one wrong line in eight.
Fixing a wrong match: edit, or remove and redo
Xero's page gives two routes: edit the account code, or use remove and redo, and JAX learns from your correction. Its August 2026 update added a third convenience, editing directly on the Reconciled page without first removing the reconciliation. The practical split:
- Edit in place when the line matched the right record or payee but is coded wrongly: the account code, or the tax rate where your region allows it (Xero's post said tax-rate editing was not available in at least one region).
- Remove and redo when the line matched the wrong record altogether, as with the workshop deposit, or when the transaction it created should not exist. The bank line goes back to the queue, and you reconcile it properly.
- Change the rule when three or more corrections in a month trace to the same rule. Fixing each line leaves the cause in place.
Because JAX learns from corrections, a hurried wrong fix teaches it the wrong thing. Take ten seconds before saving. Xero's community team has said it is looking at a settings panel with more control over what drives auto-reconciliation, and some users want a rules-only mode, but treat both as work in progress until you see them in your own organisation. Since there is no mark-as-reviewed flag, the log is also your evidence of what you checked and when. Keep it as a shared spreadsheet with a row per correction.
Situations JAX still leaves to you, or needs watching
Xero's August 2026 update lists the scenarios it added: late-arriving documents, bank transfers, recurring transactions, bank rules and clearer transaction descriptions. It also says more complex cases are still being worked on, such as one payment that covers several invoices. Plan your checking around that boundary.
| Situation | What to expect | What to do |
|---|---|---|
| One payment covering several invoices | Xero says this is still in progress, so expect the line to stay in the queue | Reconcile it by hand and note the invoice numbers in the reference |
| Card processor payouts, which arrive net of fees | The Xero pages I read do not list these among the handled scenarios | Treat any auto-match on a payout as suspect and compare it with the processor's own report |
| Transfers between your own accounts | Listed as a handled scenario | Check that both sides were reconciled and neither was coded to an expense |
| A bill that arrives after the payment | Listed as a handled scenario | When the bill is entered, confirm it was matched to the payment and not left open or counted twice |
| Recurring payments with a changed amount | Memory may code the new amount confidently | Check the amount against the supplier's notice of the change |
Bank rules audited: three before and after
Rules are the cheapest thing to fix and the most confident thing JAX does, so audit them as a set once a quarter. For each rule ask three questions: what is the narrowest text that identifies this payee, which account is right every time, and would I be happy for this to post without my looking? Illustrative audit of a yoga studio's rules:
| Rule as found | Problem | Rule after the audit |
|---|---|---|
| Payee contains "AMAZON" goes to Office supplies | It also catches a cloud hosting subscription that belongs in software | Contains "AMAZON MKTP" goes to Office supplies; a separate rule for the hosting payee goes to Software |
| Payee contains "SHELL" goes to Fuel | A studio that rents a unit called Shell Lane Units would code its rent to fuel | Contains "SHELL FORECOURT" goes to Fuel; the rent has its own rule |
| Any line under $20 goes to General expenses | Hides subscriptions and bank fees that should be tracked | Deleted; small lines go through Memory and the sample like everything else |
Rules apply first and show the Rule label, so a good rule list also lowers the number of Memory lines you have to sample.
The first six weeks, as a calendar
- Week one: switch it on for one account and only watch. Count lines by method; do not fix yet unless a line is plainly wrong.
- Weeks two to four: run the full routine at the high sample rates. Write every correction in the log.
- Week five: read the log as a whole. If three or more corrections point to one rule or payee, fix the rule. Drop the Rule sample to 10% if that label has been clean for four weeks.
- Week six: decide per account: keep, keep with a tighter sample, or pause. Only then switch it on for a second account.
Using an assistant to pick the lines worth a second look
The sample catches errors you can see in a label. An assistant can widen the net by reading the whole week's export for patterns a person skims past. Export the week's reconciled lines from a Xero report to a spreadsheet, delete bank account numbers and personal names, and paste the rest into an assistant on a business plan. The prompt asks for flags, never for corrections.
Below is a week of reconciled bank lines as CSV: date, payee, amount, method, account, tax rate.
Flag lines worth a human second look, in these categories only:
1. Same payee and similar amount appearing twice in the week
2. Amount more than double that payee's other amounts in the data
3. Same payee coded to two different accounts
4. First appearance of a payee in the data, coded by Memory or Prediction
5. Tax rate that differs from the rest of that account's lines
For each flag give the row, the category and one sentence of reasoning. Do not suggest corrections and do not calculate totals.An illustrative reply on the yoga studio's week would list the electricity line (category 2, more than double the earlier payments), the insurance line (category 1, as the same payee appeared in an earlier row with a similar amount), the academy fees line (category 4, a first-time payee coded by Prediction) and the zero-rated purchase (category 5). That is three of the four problems already found by hand, plus the tax-rate slip the sample missed, which is the point of running both.
It also over-flags. In the first run it flagged the rent under category 4 as a first-time payee, because a single week's export holds only one rent line. The rent was right, and the fix was to paste the previous month's export underneath as reference data, with the line "use the reference rows only to judge categories 2 to 4". Treat every flag as a prompt to look, and do the arithmetic yourself in the spreadsheet, as the explainer on why AI gets quotes and invoices wrong shows. For the wider method of checking AI-assisted reconciliations on any software, the general guide to automating reconciliation and checking the matches sets out the principles this routine applies to Xero.
Month-end: prove the books still agree with the bank
The weekly review checks individual lines; month-end checks the total. Run Xero's Bank Reconciliation Summary for the account, compare the statement balance with the balance in Xero, and look at any outstanding items. If the two agree and the log shows no open corrections, lock the period. If they differ, start with the lines your log flagged as queries, because that is where the difference usually sits. Keep the month's log with the reconciliation papers.
What the routine saves, and what it costs
The routine is only worth running if the saving beats the review. Illustrative assumptions: 25 seconds to reconcile a line by hand, 65% of lines reconciled by JAX, and a fixed weekly review of 12 minutes (20 minutes for the busiest account). Net saving per month is the hand-time avoided minus the review time.
| Lines a month | Hand-time avoided | Weekly review, over four weeks | Net saving | Worth at $30 an hour |
|---|---|---|---|---|
| 200 | 54 minutes | 48 minutes | 6 minutes | $3 |
| 400 | 108 minutes | 48 minutes | 60 minutes | $30 |
| 900 | 244 minutes | 80 minutes | 164 minutes | $82 |
Set that against the price. The $5.00 optional add-on on Early is worth about ten minutes of time at $30 an hour, so it pays from around 215 lines a month on these assumptions. If you would move from Early to Growing only for this feature, the extra is $32 a month, about 64 minutes at $30 an hour, which needs around 415 lines a month. On these figures a studio with 200 lines should skip it and a firm with 900 should not. If you are weighing the upgrade for other reasons too, the tutorial on Xero's price increase and whether auto-reconcile is worth it sets out the plan comparison, and the guide to JAX for invoices and cash-flow questions covers the other things it does.
Xero auto-reconciliation questions bookkeepers ask
Does Xero auto-reconcile my old transactions when I turn it on?
No. Xero's product page says that once it is enabled for a bank account, matching applies to new statement lines. Anything already waiting stays for you to reconcile as before, so clear the backlog first or keep a separate note of the date you switched it on.
Can I switch auto-reconciliation off for one bank account?
Yes. Xero says an admin or subscriber can switch it on or off for each bank account. A Xero staff reply on its community forum adds that it can be turned off at any time from the Auto-reconcile settings button on the main Bank Reconciliation screen.
How do I correct a wrong match?
Edit the account code or use remove and redo, and Xero says JAX learns from your correction. Its August 2026 product update added editing directly on the Reconciled page. Use edit when the match is right but the coding is wrong, and remove and redo when the line matched the wrong record.
Is Xero's automatic bank reconciliation still in beta?
Xero's August 2026 product update still called it beta, while the product page I read in November does not use the word. Labels change, so check how your own organisation shows it before you describe it to a client. If a screen described here is missing, compare it with Xero's current Help Centre article.
Which Xero plan includes JAX auto-reconciliation?
On the USD price list it is included on Growing and Established, with an optional $5.00 a month add-on on Early. Other regions use different plan names and describe an add-on called AI Automate for lower plans. Check your own region's plan comparison, because availability and names differ.
Further reads
- Xero vs QuickBooks AI: Which Saves More Bookkeeping Time? — See how the two accounting suites compare on AI bookkeeping time.
- Best AI Accounting Agents: QuickBooks, Xero JAX and Sage Copilot — Where JAX sits among the accounting assistants from the main suites.
- Is Xero Smart Document Capture Enough Without Dext? — The bill and receipt capture that feeds matches in Xero.
- Claude for Excel for Accountants: Reconciliations a Manager Can Sign Off — A review-ready reconciliation layout a manager can sign off.
- ChatGPT for Accounting With Excel: Seven Tasks, Each With Its Check — Seven accounting tasks, each with its own check.
- AI Accounting for Ecommerce: Reconciling Payouts and Fees — Payout and fee matching, where lumped bank lines cause trouble.
- Claude vs ChatGPT for Bookkeeping: A Test You Can Run on Bank Data — A 26-line bank export with a known answer key, planted duplicates and a refund trap, plus a scoring card to compare Claude and ChatGPT yourself.
- AI Accounting Workflow: Client Upload to Reviewed Books, Step by Step — Five stages from client upload to partner review, each with an owner, tool and check, shown through one worked month for a small contractor client.
- AI Accounting in New Zealand: GST Returns, IRD and Xero Fit — Use AI to check a GST return before filing: IRD dates and thresholds, supplier document checks, a box-by-box worked review and what each Xero plan includes.
- AI Bookkeeping Agents: What They Do Alone and What You Must Review — A task-by-task review checklist for AI bookkeeping agents: what each may post alone, what must queue for a person, and how big a sample to check.
- AI Bookkeeping in Canada: GST/HST Coding and Remittance Checks — A bookkeeper's review routine for GST/HST coding and payroll remittances: formulas for the maths, AI for the judgement calls, CRA pages for the dates.
- Ten AI Use Cases in a Small Accounting Practice, Ranked by Set-Up Effort — Ten AI jobs for a small accounting practice, ranked by how much set-up and risk each carries, with an example and a first step for every one.
- QuickBooks or Xero for a Sole Trader: Which Plan Includes AI? — Plan-by-plan prices for Xero and QuickBooks for a self-employed sole trader, what AI each tier includes, and which fits common volumes.
- AI Accounting for Startups: Monthly Close, Burn and Runway — A founder's monthly close routine that connects checked books to cash burn, runway and accountant review.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Xero's product page for automatic bank reconciliation and its price list; the Xero product-update post of 14 August 2026; official Xero Community Manager replies on the Xero product ideas forum, including the 28 October 2026 filter update; Xero's regional plan pages, read in early November 2026.