Skip to main content
Matcher is Lerian’s engine that automates transaction reconciliation between any data sources: internal systems, banks, payment processors, , or payment gateways. Matcher is available to licensed customers. Lerian maintains its repository internally. You configure matching rules once. Matcher handles the repetitive work: matching transactions, flagging discrepancies, and maintaining audit trails for compliance.

​
Why use Matcher

Every financial institution reconciles transactions, comparing internal records against bank statements, payment processors, and ERPs. Most do it manually in spreadsheets. This does not scale: matching takes hours, errors go unnoticed, and month-end close becomes stressful. Matcher solves this:
  • Automate matching: Configure rules once, let the system handle routine matches
  • Know what’s reliable: Confidence scores tell you which matches are solid and which need review
  • Stay compliant: An append-only audit log records configuration changes and exception resolutions

​
What Matcher does

  • Match automatically: Apply your match rules. Get confidence scores (0-100) for every match
  • Handle multiple sources: Reconcile between banks, ERPs, payment processors, ledgers, all at once if needed
  • Manage exceptions: Unmatched items get classified, assigned, and tracked until resolved
  • Audit changes: An append-only records configuration changes and exception resolutions

​
Matching features

  • Exact matching: Match transactions by ID, amount, date, and custom attributes
  • Tolerance matching: Allow controlled variance in amounts, defined as absolute values or percentages
  • Date range matching: Handle timing differences using configurable date windows
  • Multi-currency support: Reconcile transactions across currencies with FX rate handling
  • Split and aggregate matching: Support 1:N, N:1, and N:M transaction relationships
  • Confidence scoring: Assign a 0–100 score indicating match reliability
  • Dry run mode: Preview matching results before committing changes
  • Adjustments: Record a balancing entry, such as a bank fee or an FX difference, on a match group or a transaction

​
Data ingestion

  • Import data in CSV, JSON, XML, or ISO 20022 camt.053 format, plus a catalog of regional layouts (CNAB, OFX, acquirer EDI files). See Formats and templates
  • Automatic validation and duplicate detection
  • Flexible field mapping for heterogeneous data sources
  • Pull transactions through database and REST API connections
  • Optional: reconcile Midaz Ledger exports that you import as a LEDGER source

​
Workflow integration

  • Receive resolution callbacks from external systems

​
Common use cases

Match your internal records against daily bank statements. Upload CSVs, map fields, run matching. Review exceptions where the bank and your systems don’t align.
Reconcile Stripe or Adyen settlements against your ledger or ERP. Handle splits (one payment, many invoices) and aggregates (many payments, one deposit) automatically.
Match Visa, Mastercard, or Elo settlement files against your transaction records. Tolerance rules handle fee variances and timing differences between authorization and settlement.
Reconcile acquiring transactions with complex rate structures. Handle MCC-based rates, transaction type variations, and Interchange Plus models where rates vary by card type, merchant segment, and transaction method.
Verify SAP, Oracle, or NetSuite transactions against your other systems. Catch discrepancies before month-end close or audits.

​
How Matcher works

1

Configure

Define what you’re reconciling (contexts), where data comes from (sources), and how to match (rules).
2

Ingest

Upload files or pull data automatically. Matcher validates, normalizes, and deduplicates everything.
3

Match

Run a matching job. Matcher applies your rules and assigns confidence scores to each proposed match.
4

Review

Matcher confirms EXACT and TOLERANCE matches with a score of 90 or above automatically. Matcher never confirms a FUZZY or DATE_LAG match automatically: it sends the match to review, whatever its score. Lower scores and unmatched items go to your review queue.
5

Resolve

Handle exceptions: force a match, create an adjustment, or open a dispute.
6

Report

Export reconciliation reports. The audit log records configuration changes and exception resolutions.

​
Integrations with the lerian ecosystem

Matcher is a stand-alone product that can optionally integrate with other components of the Lerian ecosystem.
Matcher works independently or as part of the Lerian Studio ecosystem. Use it alone or connect it to Midaz and other financial components as needed.
Matcher reads an idempotency key only from the X-Idempotency header, and only when you send one. Matcher does not use a key that you send in X-Idempotency-Key or Idempotency-Key.

​
Next steps

Core concepts

Understand the key concepts: contexts, sources, rules, matches, and exceptions.

Architecture

Explore Matcher’s architecture and data flow.

Quick start

Run your first reconciliation, then review matches and exceptions with confidence.

Match rules

Learn how to configure exact, tolerance, and date-based matching rules.
Explore the Matcher API. Browse endpoints for reconciliation contexts, sources, and matching rules.