Capability · Match

Deterministic matching you can audit

Amount, counterparty, period and reference matching with tolerance rules you set. Pure code, no model: the same inputs always produce the same matches, and every match shows the rule that made it.

No model in the matching engine

A language model is the wrong tool for deciding whether 42,180.00 equals 42,180.00. Matching in TieOut Pilot is ordinary code with explicit rules, so an auditor can read the rule, re-run it and get the same answer.

Rule types

  1. Exact — same reference, same amount, opposite sign.
  2. Tolerance — amounts within an absolute or percentage band you set (default: 1.00 or 0.1 %, whichever is smaller). Differences inside the band are recorded as rounding, never silently absorbed.
  3. Many-to-one — several invoices summing to one payment (or one credit against several debits), limited to combinations of up to 6 items to keep results explainable.
  4. Reference-less — amount and date proximity when no reference exists; these are proposed with a confidence score and require a click to accept.

Order of operations

Exact → tolerance → many-to-one → reference-less. An item matched by an earlier rule is removed from later passes, so the result does not depend on file order.

What goes to the model

Only what remains unmatched after all four passes. That is typically 2–5 % of items, and it is exactly where a human would start reading invoices and emails — which is what the explanation step does.

Related

TieOut Pilot is in early access.

We are onboarding a small number of design partners with real documents and real deadlines. Tell us what you work on and we will set up a workspace with your material.