Why matching is hard
Systems rarely share a clean key. Customer names differ between the CRM and the ledger, amounts differ by tax or currency, and invoices are raised late, in parts, or combined.
The three layers Auditor Alpha uses
- Layer 1, Direct ID matching: invoice numbers, transaction IDs and PO references matched one to one across CRM and ledger.
- Layer 2, Semantic matching: when no shared ID exists, records are linked by meaning: amounts, dates, counterparties and descriptions.
- Layer 3, Heuristic rules: configurable business rules for timing lags, partial payments, tax mismatches and duplicates.
A record is flagged only once every strategy has been exhausted.
Confidence scores and human review
Each match is scored. Low-confidence matches and all flagged gaps are shown with their evidence: what was compared, what matched and what did not. Findings are suggestions, not automatic changes, and the platform is read-only.
What good matching looks like
- It explains why something matched.
- It handles tolerance.
- It avoids false alarms from tax and timing.
- It never writes to your ledger.
- It leaves an audit trail.
How Auditor Alpha helps
- Works without requiring you to change how you reference invoices, although consistent references improve results.
- Shows a detection trail for every flag, which supports internal audit and external review.
- Lets you configure rules to suit your billing model.
Read the full approach in our methodology.
Limits to be aware of
Accuracy depends on data quality. Messy or inconsistent records produce more low-confidence matches, and rules may need tuning to your billing model.
Illustrative example
Deal: a logistics client, £127,900, closed on 9 June. Invoice: the same client's registered name, £127,900, dated 11 June, with no shared reference. Layer 1 finds no ID match. Layer 2 pairs them by amount, date and counterparty with high confidence. The deal is marked as matched and needs no action.
All names and figures in this example are illustrative, not real customer data.
Frequently asked questions
Do I need to change how I name or reference invoices?
It helps, but it is not required.
What happens to low-confidence matches?
They are surfaced for human review.
Does Auditor Alpha create or edit invoices?
No. It is read-only.