Matcher
Automatic reconciliation across any data sources.
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
- Exact, tolerance-based and date-range matching, with a confidence score from 0 to 100.
- Connects to and ingests from several sources at once: banks, ERPs, processors, gateways and ledgers.
- Split and aggregate matching: 1:N, N:1 and N:M relationships.
- Ingestion in CSV, JSON or XML, with validation and duplicate detection.
- Exception management routed to JIRA or ServiceNow through webhooks.
- Full 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.
Build with Matcher.
Talk to the people who build it — or go straight to the documentation.