A confidence score of 100 percent is the point at which a matched remittance line is safe to post into Xero with nobody looking at it, and by default it's the only score that qualifies. Anything lower means the system has found a candidate it isn't sure about. Where you set that threshold, whether you review everything, auto-post only at 100 percent, or open the band wider, is the most important configuration decision your team will make. A wrong match costs you a finance manager's trust, and a queue full of matches that were right all along costs you their attention, so the setting has to sit between the two.
Most Xero remittance tools put a confidence score against each matched line, which is the system's own estimate of how sure it is that this remittance line maps to this open Xero invoice. The score is useful, and what matters is what you do with it. Teams land in one of three places: reviewing everything, auto-posting only at 100 percent confidence and reviewing the rest, or auto-posting a wider band and accepting the occasional correction. Each of those carries its own trade-offs in audit exposure, exception load, and team trust.
What an auto-match confidence score measures
Behind the percentage, most matching engines are combining three separate signals: invoice number match (exact, partial, or fuzzy), amount match (exact or within a tolerance), and customer or supplier identity match, meaning whether the remittance says it's from the customer whose invoices you're reconciling against. A 100 percent score usually means all three line up cleanly, so the remittance reference matches a single open invoice number exactly, the amounts agree to the penny, and the payer identity is unambiguous.
A sub-100 score is the system flagging a candidate it can't fully stand behind. The most common reasons are a remittance reference that's a customer-side PO number rather than your invoice number, an amount short by a deduction or VAT discrepancy, a payer paying through a parent account that doesn't match the entity on your invoice, or a remittance line that could plausibly map to two open invoices of similar value. Each of those needs a different response from a person, which is why the ambiguous cases keep a review layer at all.
Three thresholds, three different operating models
Review everything (zero auto-match)
This is where most teams start. Every remittance is parsed, every line is matched, and a person approves the batch before it posts to Xero. It's the safest setting and the right one for the first two weeks of any rollout, because reviewing everything gives the team a chance to check that the system is reading their formats correctly, that customer name normalisation is doing what they expect, and that the audit trail looks the way they want it to. After about ten to twenty live remittances, most teams have seen enough to know whether they trust the high-confidence matches without checking them.
Auto-match at 100 percent confidence, review the rest
This is the setting that most high-volume teams end up running. Lines that score 100 percent post straight to Xero with no manual step. Anything below 100 sits in a review queue where someone in the finance team confirms the suggested match, adjusts it, or rejects it. On most B2B remittance flows that means the bulk of the work runs untouched and the finance team's time goes on the small minority of lines that need a judgement call. High-volume customers describe the change the same way after onboarding, and one running 400 remittances a month across eight Xero entities put it like this: "a game changer, just take the manual element out of the process."
Why RemitClear does not open the band wider than 100 percent
The tempting next step is to push the threshold down, on the reasoning that if the system is 95 percent sure then the review usually confirms what it already thought, so the time spent confirming feels wasted. RemitClear auto-posts on 100 percent confidence matches and nothing else, and the threshold is fixed there. Ninety-five percent confidence isn't certainty, and the matches that go wrong in that band tend to go wrong without anyone noticing, which is the failure that costs a finance manager's trust in the whole system. Everything below 100 queues for review, so the only lines that reach Xero unattended are the ones where the invoice number, the amount, and the payer all line up exactly.
The decision in front of you is where the human review layer sits. Put it too high and you spend your time on work the system has already done correctly, and put it too low and you spend that same time unwinding posted entries that should never have gone in.
How to choose the right threshold for your team
How stable are your customer remittance formats
If you process remittances from a small number of large customers who use consistent layouts (think a labour hire firm invoicing four big civil contractors, or a wholesale supplier shipping to a handful of grocery chains), the system learns those formats quickly and high-confidence matches become reliable inside a few cycles. If your remittance flow includes dozens of one-off customer formats, RemitClear reads them all the same way and routes the less clear-cut lines to review, and a tighter threshold is the setting that suits that mix. Stability of inputs predicts more about whether an aggressive auto-match setting will work than anything else does.
How much audit exposure do you carry
NDIS providers, healthcare operators, public-sector contractors, and any business with grant funding sit in a different audit posture than a typical B2B wholesaler. For those teams, the cost of a single wrong match (and the resulting need to reverse and repost a batch payment in Xero) is meaningfully higher because it leaves a visible trail in the ledger. Tighter thresholds, and a clear note on the review log of who approved each batch, matter more. In practice the review layer at 100 percent auto-match is already small for these teams, because most NDIA remittances score cleanly once the formats are learned, and the exceptions are usually the same handful of plan-manager edge cases each week.
What your team's capacity looks like
Capacity is rarely said out loud in this conversation. A finance manager who's comfortable with the review queue and has the time to work through it will set thresholds tighter than a finance manager who is the only person reconciling several hundred remittances a month and needs the system to take most of the work off the table. The threshold should reflect your operating reality, and there's no prize for setting one stricter than your team can sustain.
What does the customer mix tell you
If 80 percent of your remittances come from five customers, you can almost certainly auto-match those five formats at 100 percent confidence after the learning period, and keep tighter manual review on the long tail of one-off payers. Most matching engines let you set thresholds per customer or per format, which is the version of this decision most teams should be making, because a single global threshold is the easy answer and a per-customer threshold matches how the work arrives.
What a healthy review queue looks like
If you've set your threshold correctly, the review queue shouldn't be a bottleneck. At 100 percent auto-match, a healthy queue runs anywhere from a couple of percent of total remittance lines on clean books to 20 percent where payers send messy documents. The reviewer isn't re-confirming matches the system already made, because those have posted. What reaches the queue is the ambiguous work: a deduction that needs allocating to a separate GL account, a short payment that should be left unallocated pending a credit note, a remittance line that maps to two plausible invoices of identical value, or a payer identity the system hasn't seen before.
A queue that sits consistently above 30 percent of total lines after the first month probably means the threshold is set too aggressively for your data, or that your customer name and invoice number normalisation needs tuning. A very small queue isn't a warning sign in itself, and on clean data it's what you're aiming for, though it's worth spot-checking a sample of auto-posted lines in the first month to confirm the confident posts really were right. What you want is a queue where the reviewer's time goes only on the cases their judgement adds value to.
A note on the bookkeeper-as-reviewer question
Bookkeeping practices have a slightly different version of this conversation. Part of what they sell clients is judgement, knowing which deductions to post where, which short payments to chase, and which credit notes are about to land. Auto-matching the routine 80 percent of lines doesn't hollow the job out, it moves the bookkeeper's billable time onto the cases that need judgement, and for a practice owner pricing client work that improves the margin. The fear that automation replaces the bookkeeper hasn't borne out, and the part it removes is the part of the day that was never billable in the first place.
A simple rollout pattern that tends to work
For most teams, the cleanest path is to start at zero auto-match for the first two weeks, move to 100 percent auto-match once the formats have settled, and only consider a wider band after at least three months of clean operation at the 100 percent threshold. Trust builds in that order, because the team sees the matches before they post, then sees them post correctly on their own, and any loosening comes after the operating history justifies it. Teams who let the first fortnight do its work are the ones who stay on auto-match, since by then the confidence is earned on their own formats.
Summary
You stop worrying about the threshold once your own operating history has answered it. Start at zero, move to 100 percent auto-match after a fortnight of clean runs, and only widen the band on stable, high-trust customer formats where a wrong match is cheap to unwind. By then the queue has shrunk to the handful of lines where a person's judgement changes the outcome, and nobody is thinking about the dial any more. RemitClear's Xero remittance matching is built around that review-then-auto-post workflow. For the cost framing of the same decision, see our post on offshore AR teams versus Xero remittance automation, and for what happens when a single customer pays you across hundreds of invoices at once, see the Xero 200-invoice batch payment limit.
