Skip to main content
Matcher automates transaction reconciliation between any data sources—internal systems, banks, payment processors, ERPs, or payment gateways. You configure matching rules once. Matcher handles the repetitive work—matching transactions, flagging discrepancies, and maintaining audit trails for compliance.

​
Why use Matcher

Manual reconciliation doesn’t scale. Spreadsheets break, matching takes hours, and you lose visibility into what’s reconciled versus what’s stuck. 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
  • Route exceptions: Send unmatched items to JIRA, ServiceNow, or your own tools via webhooks
  • Stay compliant: Every match and resolution is logged immutably for audits

​
What Matcher does

  • Match automatically: Apply exact or tolerance-based 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, routed to your team, and tracked until resolved
  • Audit everything: Immutable logs and SOX-ready reports for compliance

​
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

​
Data ingestion

  • Import data in CSV, JSON, or XML formats
  • Automatic validation and duplicate detection
  • Flexible field mapping for heterogeneous data sources
  • Optional: Native access to Midaz Ledger transactions

​
Workflow integration

  • Route exceptions to JIRA or ServiceNow
  • Emit events through webhooks for custom integrations
  • Receive resolution callbacks from external systems
  • Track SLAs and automatically escalate breaches

​
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

High-confidence matches (>90%) get auto-approved. Lower scores and unmatched items go to your review queue.
5

Resolve

Handle exceptions: force a match, create an adjustment, split transactions, or route to JIRA/ServiceNow.
6

Report

Export reconciliation reports. Every action is logged immutably for audits.

​
Integrations with the lerian ecosystem

Matcher is a stand-alone product that can optionally integrate with other components of the Lerian ecosystem.
ProductIntegration
MidazOptional: Direct access to Ledger transactions for reconciliation
ReporterOptional: Reconciliation reports and audit summaries
FlowkerOptional: Event-driven reconciliation workflows
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.

​
Next steps

Core concepts

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

Quick start

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

Architecture

Explore Matcher’s architecture and data flow.

Match rules

Learn how to configure exact, tolerance, and date-based matching rules.