Lerian Matcher vs OpenRecon
Lerian Matcher
matcher.lerian.studioOpenRecon
naresh-paturi-community.github.ioSide by side
| Figure | Lerian Matcher | OpenRecon |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | — |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 0 | 1 |
| Spec score · Account Reconciliation Software | 7.6 (#12) | 7.6 (#13) |
| Intended users | The product site names acquirers, PSPs, marketplaces, and payment institutions as users, while the documentation describes financial institutions reconciling transactions. | The maker describes use by payments, finance and accounting, engineering and operations, marketplaces, audit teams, and teams embedding reconciliation in internal tools. |
| Matching | Matching supports exact, tolerance, and date-window rules, multi-currency handling, split and aggregate relationships, and confidence scores from 0 to 100. | It first matches shared IDs or references, then matches remaining rows by amount, currency, and date window. |
| Purpose | Matcher automates transaction reconciliation across internal systems, banks, payment processors, and payment gateways. | OpenRecon matches transactions across payment processors, gateways, and an internal ledger, and reports mismatches and missing transactions. |
Plans
In their own words
Lerian Matcher
Lerian Matcher automates reconciliation between financial transaction sources. It evaluates exact, tolerance, date-window, multi-currency, split, and aggregate matches, assigning confidence scores from 0 to 100. Scores of 90 or higher are confirmed automatically except for fuzzy matches; lower-scoring and unmatched records enter a review queue. Users can classify, assign, and track exceptions, then 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 operate independently with banks, ERPs, payment processors, and other sources, or connect with Lerian Midaz, Reporter, and Flowker products. The API covers reconciliation contexts, sources, and matching rules. Documented deployment uses PostgreSQL, Redis, and RabbitMQ, with Docker or Kubernetes options. Multi-tenant deployments isolate databases, broker namespaces, cache keys, and storage prefixes. The default upload limit is 100 MB and 100,000 transactions per file. Pricing is on request.
OpenRecon
OpenRecon reconciles transactions from payment processors and gateways against an internal ledger, then reports mismatches and missing transactions. It first pairs records with shared IDs or references; remaining rows are matched by amount, currency, and a date window. Amounts use Python Decimal rather than floating-point arithmetic. Presets cover Stripe, Adyen, PayPal, Razorpay, Braintree, and Square, with column auto-detection or explicit field mapping. The listed input is two CSV files. OpenRecon provides a command-line interface and Python library, with console summaries and optional JSON or CSV reports. Its command line returns a non-zero status when discrepancies exist, supporting scheduled and CI workflows. The maker says it runs locally without network calls, leaving ledger and processor files on the user's computer. Requirements are Python 3.9 or later and no dependencies beyond the standard library. Many-to-one matching, multi-currency settlement, refund and chargeback handling, and HTML reports are listed as planned improvements. The project is free, has no paid tier or account requirement, and uses the MIT license.