This release introduces Matcher, Lerian’s automated transaction reconciliation platform. Matcher reconciles transactions across any data sources—internal systems, banks, payment processors, ERPs, or payment gateways—using configurable rules, confidence scoring, and complete audit trails.
Matcher is a reconciliation engine designed to automate transaction matching across multiple data sources. You configure matching rules once. Matcher handles the repetitive work—matching transactions, flagging discrepancies, and maintaining audit trails for compliance.
This release includes comprehensive documentation to help you get started:
To get started, follow the Quick Start guide to set up your environment and run your first reconciliation.For details about design decisions and supported use cases, see the What is Matcher page.
What is Matcher?
Matcher is a reconciliation engine designed to automate transaction matching across multiple data sources. You configure matching rules once. Matcher handles the repetitive work—matching transactions, flagging discrepancies, and maintaining audit trails for compliance.
Key capabilities
- Automated matching — Exact or tolerance-based rules with confidence scoring (0–100)
- Multiple data sources — Reconcile banks, ERPs, payment processors, and ledgers simultaneously
- Exception management — Route unmatched items to JIRA, ServiceNow, or your own tools
- Compliance-ready — Immutable logs and SOX-ready reports for audits
- Split and aggregate — Handle 1:N, N:1, and N:M transaction relationships
- Multi-currency — Reconcile across currencies with FX rate handling
Documentation
This release includes comprehensive documentation to help you get started:
Getting started
- What is Matcher — Overview of Matcher’s capabilities and design principles
- Core Concepts — Understand contexts, sources, rules, matches, and exceptions
- Architecture — Explore Matcher’s architecture and data flow
- Prerequisites — Requirements before installation
- Installation — Set up Matcher in your environment
- Quick Start — Run your first reconciliation
Configuration
- Contexts and Sources — Define what you’re reconciling and where data comes from
- Match Rules — Configure exact, tolerance, and date-based matching rules
- Field Mapping — Map fields from heterogeneous data sources
- Exception Routing — Route exceptions to JIRA, ServiceNow, or webhooks
Daily reconciliation
- Uploading Files — Import data in CSV, JSON, or XML formats
- Reviewing Matches — Review and approve matched transactions
- Resolving Exceptions — Handle unmatched items and discrepancies
- Generating Reports — Export reconciliation reports for audits
Integrations
- Midaz Integration — Connect to Midaz Ledger for native transaction access
- External Sources — Integrate with banks, ERPs, and payment processors
- Webhooks and Callbacks — Receive real-time notifications and resolution callbacks
Reference
- Confidence Scoring — How Matcher calculates match reliability scores
- Multi-Currency — Handle FX rates and cross-currency reconciliation
- Split and Aggregate — Configure 1:N, N:1, and N:M matching scenarios
- Security — Authentication, authorization, and data protection
API Reference
- Contexts API — Create and manage reconciliation contexts
- Sources API — Configure data sources for reconciliation
- Match Rules API — Define matching logic and priorities
- Field Mapping API — Map source fields to Matcher’s schema
- Ingestion API — Upload and process transaction files
- Match Run API — Execute matching jobs and retrieve results
- Exceptions API — Query and resolve unmatched transactions
- Reports API — Generate reconciliation reports
- Audit API — Query immutable audit trail
- Disputes API — Manage transaction disputes
Getting started
To get started, follow the Quick Start guide to set up your environment and run your first reconciliation.For details about design decisions and supported use cases, see the What is Matcher page.