← products

Matcher

transactional services · POST /v1/reconciliations

The reconciliation engine: it matches transactions across banks, processors, ERPs and your ledger, with confidence scores, exception handling and an audit trail.

POST /v1/reconciliations

{ "sources": ["bank.statement", "ledger.midaz"] }

reconciled 1.284 score ≥ 98

exceptions 3 routed

200 ok · run complete

what it is

Matcher is Lerian's reconciliation engine. It automates transaction matching across any data sources — internal systems, banks, payment processors, ERPs or gateways. You configure the rules once and Matcher reconciles, flags discrepancies and keeps audit trails for compliance.

Manual reconciliation does not scale: spreadsheets break, matching takes hours and you lose sight of what is reconciled. Matcher applies exact or tolerance-based rules, assigns confidence scores from 0 to 100 and routes exceptions into your own tools.

capabilities

  • 01Exact, tolerance-based and date-range matching, with a confidence score from 0 to 100.
  • 02Connects to and ingests from several sources at once: banks, ERPs, processors, gateways and ledgers.
  • 03Split and aggregate matching: 1:N, N:1 and N:M relationships.
  • 04Ingestion in CSV, JSON or XML, with validation and duplicate detection.
  • 05Exception management routed to JIRA or ServiceNow through webhooks.
  • 06Full audit: immutable logs and SOX-ready reports.

when to use it

  • Bank reconciliation: internal records against daily statements.
  • Processors and acquiring: settlements from Stripe, Adyen or the card networks, with tolerance for fees and timing.
  • ERP synchronization: SAP, Oracle or NetSuite before the monthly close.

On the platform.

Reconciles transactions from the Midaz ledger against external sources: it connects to and ingests from the banks, ERPs, processors and gateways you already use, and issues reconciliation reports through Reporter. Reconciliation workflows can be orchestrated by Flowker.

Midaz

everything settles here · double entry · immutable trail

Build with Matcher.

Talk to the people who build it — or go straight to the documentation.