Lerian Matcher automates reconciliation across financial transaction sources. It matches records using exact values, tolerances, date windows, multiple currencies, and split or aggregate combinations, then assigns each match a confidence score from 0 to 100. Scores of 90 or higher are confirmed automatically, except for fuzzy matches. Lower-scoring and unmatched items enter a review queue, where users can classify, assign, and track exceptions, force a match, create an adjustment, or open a dispute. An append-only audit log records configuration changes and exception resolutions. Matcher accepts CSV, JSON, XML, ISO 20022 camt.053, CNAB, OFX, and acquirer EDI files. It can reconcile data from banks, ERPs, payment processors, and other sources on its own, with optional connections to Lerian’s Midaz ledger, Reporter reports, and Flowker workflows. The product is API-first and supports multi-tenant operation with isolated databases, message broker namespaces, cache keys, and storage prefixes for each tenant. Documented deployment uses PostgreSQL, Redis, and RabbitMQ, with Docker or Kubernetes available. Matcher is offered to licensed customers, with pricing on request. Its documented default upload limit is 100 MB and 100,000 transactions per file; the size limit can be configured.
Who it is for
Matcher suits acquirers, PSPs, marketplaces, payment institutions, and financial institutions that reconcile transactions across multiple sources. It is designed for teams that need exception review, approval controls, and an audit trail alongside automated matching.
What is good
- Supports exact, tolerance, date-window, multi-currency, and split or aggregate matching.
- Routes lower-scoring and unmatched transactions into an exception review queue.
- Records configuration changes and exception resolutions in an append-only audit log.
- Accepts common data formats, including CSV, JSON, XML, and ISO 20022 camt.053.
- Can run independently or connect optionally to Lerian products.
What to know first
- No free plan is offered.
- Access is for licensed customers, with pricing on request.
- Documented default uploads are capped at 100 MB and 100,000 transactions per file.
- Documented deployment uses PostgreSQL, Redis, and RabbitMQ.
Verdict
Choose Lerian Matcher if your organization needs automated financial reconciliation with scored matches, controlled exception handling, and audit records. It supports a range of file formats and can operate independently or with optional Lerian integrations. Contact Lerian for licensed access and pricing; the documented default file limits may also matter for large reconciliation files.
Get started with Lerian Matcher
- Visit the Matcher website and contact Lerian to request licensed access.
- Ask about the offered file-based proof using a masked data file.
- Choose a deployment approach: Lerian-operated SaaS or, depending on the solution, BYOC.
- For documented containerized deployment, use Docker or Kubernetes with PostgreSQL, Redis, and RabbitMQ.
- Connect transaction sources using the API or provide supported CSV, JSON, XML, ISO 20022 camt.053, CNAB, OFX, or acquirer EDI files.
Limits to know first
The documented default maximum is 100 MB and 100,000 transactions per file; the file-size limit is configurable. Matcher has no free plan, and it is available to licensed customers.
Questions about Lerian Matcher
How much does Lerian Matcher cost?
Pricing is on request. Matcher is available to licensed customers.
Is there a free plan?
No. The listed pricing model is paid.
What platforms does Matcher support?
It is listed for API, self-hosted, and web use. Lerian offers its platform as SaaS and says BYOC is available depending on the solution.
Can Matcher be used without other Lerian products?
Yes. It can run independently and reconcile data from banks, ERPs, payment processors, and other sources. Connections to Midaz, Reporter, and Flowker are optional.
What file formats can Matcher accept?
It accepts CSV, JSON, XML, ISO 20022 camt.053, CNAB, OFX, and acquirer EDI files.
What are the documented file limits?
The default maximum is 100 MB and 100,000 transactions per file. The file-size limit can be configured.
Compared on account reconciliation software
- Free plan
- No
- Matching automation
- rules
- Exception workflows
- Yes
- Approval controls
- Yes
