Browse the knowledge base

Why this matched — and how to undo it

Every match carries an explanation: a plain-language headline, four score bars (invoice number 40 · amount 25 · date 20 · counterparty 15 — a total of 90+ auto-confirms silently), and caveat warnings when something deserves a second look. On mobile, the Matched segment lists every matched transaction; one tap unlinks an auto-match, and an Undo toast brings it back if that was a mistake.

What this article is about

Nothing in matching is a black box. Every automatic link, every flagged match, and every suggestion carries an explanation you can open: what the decision was based on, how strong each piece of evidence was, and what — if anything — looked off. And every match, including the fully silent ones, is visible and reversible. This article shows you where to find the explanation and how to undo a match on web and mobile.

The headline

Each match leads with a one-line, plain-language summary of the strongest evidence. These are fixed phrases, so you learn to read them at a glance:

  • "Invoice number and amount match"
  • "Invoice number matches"
  • "IBAN and exact amount match (no invoice number)"
  • "Several invoices from this vendor add up to this payment"
  • "Amount and vendor match"
  • "Only the amount matches"
  • "Weak match"

The further down this list a headline sits, the more it deserves your attention before you approve.

The four score bars

Behind the headline is the actual score: four signals, each with a fixed maximum weight.

Signal Max points
Invoice number 40
Amount 25
Date 20
Counterparty 15

The bars show how much each signal contributed. The total decides the behaviour: 90 or more auto-confirms silently, 70–89 is auto-matched but flagged for review, 50–69 appears as a suggestion for you to approve, and weaker candidates stay hidden behind the "Show all" toggle. For the full tier model, see how the matching pipeline works.

Caveat warnings

When something about a match warrants a second look, an amber caveat note is attached. There are three, and again the wording is fixed:

  • "Two invoices from this vendor have the same amount — confirm which one this payment belongs to."
  • "These invoices sum to the payment, but their dates are far from it — double-check this bundle."
  • "Matched on IBAN and amount, but the payment date is far from the invoice date — double-check this is the right invoice."

The date-related caveats appear when the payment sits more than 30 days from the invoice. A caveat doesn't block anything — it tells you where to spend your review attention.

Where you see it

  • Web matching inbox (/matching): every suggestion shows the score breakdown — the four signal bars, the tier label, and the total.
  • Advisor review panel (web): the transaction review panel shows the headline, caveats, and an expandable score breakdown; transaction rows with a caveat carry an amber marker so they stand out in the list.
  • Mobile: the review sheet shows caveats as amber notes and a "Why this match?" disclosure that opens the four score bars. The payment card on an invoice shows caveat warnings too.

The explanation only contains labels, numbers, and these fixed phrases — it never exposes anything beyond what you already see on the transaction and invoice themselves.

Undoing a match

Silent auto-matches are silent, not hidden. Every one of them is listed and can be reversed:

  • Mobile — the Matching screen has three segments: All, Probable, and Matched. The Matched segment lists every matched transaction; system matches carry an "Auto" badge. One tap unlinks the match, and an Undo toast appears so you can re-link instantly if the unlink itself was the mistake.
  • Web — use the Unmatch button on the transaction row on the Banking page, or unlink from the payment card on the invoice.

Unmatching reverts the invoice to unpaid and returns the transaction to the open pool, ready to be matched correctly. If the match was a bundle (one payment covering several invoices), unmatching reverts the whole bundle.

Every automatic match is also written to the audit trail with its score, tier, and signal breakdown — so even months later you can reconstruct why the system did what it did.

Related

Didn't answer your question? Write to [email protected] · the AI chat in the bottom-right corner answers most common questions.