Xero Auto-Reconciliation: Notes From Our Testing

By Andrew Erkins · 31 March 2026

Xero's auto-reconciliation feature - powered by JAX (Just Ask Xero) - has been in beta since late 2025. It's the most significant piece of Xero's AI to ship so far. Our team at Digit turned it on across a cross-section of client files from January 2026 and ran it for up to ten weeks. The short version: it works well on simple, repeating-transaction clients and saves real time there, but it falls over on complex files, creates a specific timing problem with Dext, and doesn't always stay consistent even on transactions it previously got right

The test setup

We asked each team member to activate Xero's automatic bank reconciliation on at least one client. We deliberately mixed the portfolio - low volume dental practices through to high-transaction retail, flower catering, and recruitment files. Some clients use Dext for receipt capture, some don't. Some have clean bank rules already built, others rely mostly on memory matching. We even tested it on Digit's own books

Eighteen responses came back covering everything from a day spa doing 150 transactions a month to a web developer doing 35-50. We didn't cherry-pick easy clients. We wanted to see where the edges were

What auto-reconciliation gets right

On simple, repeating transaction clients, Xero's auto-reconciliation is genuinely good. It picks up bank transfers between linked accounts, matches sales invoices to deposits (where amounts are unique), and correctly applies historical coding to recurring charges like subscriptions and insurance

Princess Espinosa tested it on a day spa client and tracked the numbers closely. "69 out of 116 transactions were auto reconciled for the past 30 days," she reported. "It effectively recorded and reconciled the repeating transactions such as daily sales, afterpay fees, wages and super payments, internet payments, insurance premium funding, bank transfers and some office, travel, and subscription expenses that are normally cash-coded." That's a 60% hit rate with no errors flagged

Laarnie Reyes saw similar numbers on a web developer client that's mostly monthly subscriptions. "It auto-reconciles most of the transactions, including received items - 26 out of 39 in the last 30 days." That's 67%. On clients like this, where bank rules are already set up and sales invoices are minimal, she found "less time working on the account - more time is spent on viewing all reconciled than reconciling."

Michael Villafania had a clean run on a low-volume digital marketing client. "It perfectly reconciles the transaction as per memory and leaves those transactions that normally has mixed GST," he said. "It saves time when you open View All Reconciled - it shows the details of the transaction and whether it is matched to an invoice or reconciled via memory, so it is easier to check." View All Reconciled is Xero's new review screen that shows every transaction JAX has processed automatically, with the matching logic visible alongside each entry

Dan Banting, working on a trades client, put it simply. "Auto reconciliation is one of the best features made by Xero as it saved me a lot of time on doing the bank rec for this client."

Where it falls over

Problems showed up on more complex files, and they were consistent across different team members testing different clients

Intercompany and variable transactions. Monica Atizado tested it on a high-transaction audio-visual business and got the worst result in the group. "The process is not suitable if there are transactions that vary, like intercompany transactions that are coded differently from time to time," she said. "I thought that Xero would not reconcile it since it would not be sure, but it would reconcile based on the previous transaction which would make it incorrect." The kicker: "It says it will reconcile transactions that are sure - it coded transactions to multiple suspense accounts." She had to remove and redo transactions every week

Part payments and batch deposits. Cindy Escueta found that auto-reconciliation "doesn't work well with batch payments from customers - so you will still need to do a batch deposit or match manually during bank rec." Dan Banting hit the same wall from the other side. "Xero is not able to reconcile part payments made by customer even though the invoice number and customer name is already in the description."

Bank transfers between related entities. This was the single most common failure across the whole test. Mark Salvacion was blunt. "Its main challenge is the bank transfers. It's not reliable in this regard and I usually end up having to remove and redo it." Dan had the same issue with transfers between sister companies where Xero couldn't determine which entity the money belonged to. Michael Villafania hit it again on a second client - a flower catering business with heavy interbank activity. "Some funds were transferred to the wrong account," he said. "It is quite a pain to check all the accounts and reverse the reconciliation."

GST edge cases. Earvin Uy found a repeating subscription that's GST-free being auto-reconciled with GST on expenses. Small error, but the kind that compounds across a BAS period if you're not checking

Inconsistent coding between runs. Michelle Nivera tested it on Digit's own books and found something the others didn't: JAX getting a transaction right the first time, then wrong the second. "Subscriptions are not coded correctly even though it was correct by JAX the first time - the second recon is incorrect," she reported. Even when it gets something right once, that doesn't mean it will next time. She scored it a 3 out of 5, the joint-lowest rating in the group

The Dext timing problem

This one deserves its own section because multiple team members hit it independently, and it's the most operationally significant finding from the whole test

The issue: if a bank statement line comes through before the bill has been published from Dext, Xero's auto-reconciliation will code it as spend money based on historical memory. Then when the bill arrives from Dext, you have to remove the auto-reconciled transaction and redo it to match the bill properly

Aaron Trinidad described the pattern clearly. "If there are memory records for a supplier and the client usually sends bills through Dext, Xero auto-reconciles before I can match the bill. I have to undo it and match manually." Cindy Escueta confirmed the same. "Items already reconciled as spend money in Xero don't show as a paperwork match when the bill comes through from Dext later."

There's a flip side worth noting. Laarnie Reyes found that on her client, "items that have an invoice attached to the previous transactions remain unreconciled in Xero." In that case, JAX was smart enough to leave Dext-attached items alone rather than reconciling over the top. The behaviour seems inconsistent across files, which makes it hard to predict

Some team members tried delaying Dext processing to see if it would resolve naturally. Mark Salvacion tested this approach. "I've tried to delay the dext processing to see if it matches automatically - sometimes it works, sometimes it doesn't. I still prefer doing Dext and leaving the recon to Xero."

In practice, this is partly a workflow sequencing question. On clients where Dext is used to create bills (rather than simply attaching receipts to existing transactions), the timing conflict is more likely to surface. Adjusting the process so that routine purchases are captured as attachments rather than bills can reduce the friction. On clients that don't use Dext at all, the problem doesn't exist

How it changes the bank reconciliation workflow

Every team member reported the same shift: less time reconciling individual transactions, more time in View All Reconciled reviewing what Xero's automation did. Whether that's a net time saving depends on the client

Princess put it well. "It reduced the time I spend on repetitive transactions. Now it's just a quick scan to check what the auto-reconciliation did." But Mackie Silvero flagged a practical friction. "For transactions with mixed GST, I have to search them individually on Bank Statements because you can't open transactions from View All Reconciled."

Cindy was honest about her experience on a higher-volume file. "Spent more time checking the auto-recs." When the hit rate is high and accuracy is strong, the review is fast. When there are false matches to catch, review time can eat into the savings

Which clients suit Xero auto-reconciliation

Auto-reconciliation works well when the client has mostly repeating transactions, low to moderate volume, limited intercompany activity, and clean historical coding. It's particularly strong on files where sales invoices have unique amounts and customers pay single invoices at a time

Michael Villafania landed on the most practical recommendation after testing it on two very different clients. On the simple digital marketing file, it was a clear win. On the flower catering business with heavy interbank transfers, he took a different approach: "I will turn it on for the credit card account, but not for the other bank accounts used for transfers." That selective activation - turning it on per account based on what flows through that account - is probably the smartest way to use it right now

It's not ready for complex files - high transaction volume with variable coding, batch payments, intercompany transfers, or heavy reliance on Dext for bill capture timing. On those files, the review burden and remove-and-redo cycles can negate the time saved

We're keeping it turned on for the simpler clients and the credit card accounts where it tested well. For the rest, we're watching Xero's updates and will test again as the feature matures. Xero's roadmap for JAX suggests the matching will get smarter over time - the question is how quickly it learns to handle the edge cases that tripped up our team

One thing everyone agreed on: even on the clients where auto-reconciliation performed well, you still need to review what it did. Michelle Nivera's finding on Digit's own books says it best - a transaction coded correctly the first time got it wrong the next. The "set and forget" pitch doesn't hold up in practice. Not yet

Testing conducted January - March 2026 across client files by Digit's bookkeeping and technical team. Auto-reconciliation is available on Xero Growing plan and above

Do you want to learn Xero?

We are Xero experts, in the top 1% of Xero partners in the world. Learn from a team that use Xero daily to support businesses

Get Started

Andrew Erkins

Andrew co-founded Digit to help businesses make sense of their numbers. He thinks in systems, builds from scratch, and is quietly obsessed with how things work

Meet Andrew

Common questions

Timing creates a conflict. If a bank statement line arrives before the bill is published from Dext, JAX codes it as spend money from memory and you need to remove and redo the transaction once the bill comes through. On some files JAX leaves Dext-attached items alone; on others it doesn't. The behaviour is inconsistent across client files.

Low to moderate volume clients with mostly repeating transactions, limited intercompany activity, and clean historical coding. In practitioner testing, auto-reconciliation correctly handled 60-67% of transactions on suitable files with no errors. It works best where sales invoices have unique amounts and customers pay single invoices at a time.

Manual review is still necessary. JAX can code a subscription correctly the first time then incorrectly the second time on the same transaction type. False matches, GST errors, and incorrect entity coding all occurred across different client files during ten weeks of testing.

Auto-reconciliation activates per bank account in Xero. Turning it on for credit card accounts (mostly repeating, one-directional spend) while leaving it off on operating accounts with interbank transfers produced the best results in practitioner testing.

Bank transfers between related entities were the most common failure - JAX coded funds to the wrong account across three separate client files. It also struggles with batch customer payments, part payments against invoices, intercompany transactions with variable coding, and can apply incorrect GST treatment to repeating subscriptions. JAX may also code the same transaction type correctly once then incorrectly the next time.

Insights