Eko Recon vs Lerian Matcher
Eko Recon
github.comLerian Matcher
matcher.lerian.studioSide by side
| Figure | Eko Recon | Lerian Matcher |
|---|---|---|
| Price from | — | — |
| Free plan | — | — |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| Windows | Yes | — |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 0 |
| Spec score · Account Reconciliation Software | 7.7 (#11) | 7.6 (#12) |
| API | The architecture exposes a JSON API and documents it through Swagger and ReDoc. | The product site describes Matcher as API-first and multi-tenant, and the documentation links to an API for reconciliation contexts, sources, and matching rules. |
| Deployment | It runs locally or in Docker as one container, uses SQLite by default and can switch to MySQL or PostgreSQL for production. | Lerian says its platform is offered as SaaS operated by Lerian, with BYOC available depending on the solution; Matcher documentation says it is available to licensed customers. |
| Headquarters | India | São Paulo, Brazil |
| Matching | Its priority-ordered rule engine matches transactions using TID, tracking number, UTR and amount rules, with amount-tolerance mismatch flags. | Matching supports exact, tolerance, and date-window rules, multi-currency handling, split and aggregate relationships, and confidence scores from 0 to 100. |
| Purpose | Eko Recon is a full-stack bank reconciliation platform for fintech operations. | Matcher automates transaction reconciliation across internal systems, banks, payment processors, and payment gateways. |
Plans
In their own words
Eko Recon
Eko Recon is an open-source bank reconciliation platform for fintech operations, released under the MIT license. It accepts CSV, XLSX/XLS, PDF and tab-separated text files, recognizing headers and formats automatically. Its priority-ordered rules match transactions using TID, tracking number, UTR and amount, with flags for amount-tolerance mismatches. Teams can review Open Items, match manually, record overrides with mandatory remarks, use maker-checker approvals and add ad hoc tags. Modules cover DMT, AePS settlement, PG net settlement, QR settlement and chargebacks, E-Value wallet loads, BBPS refunds and SBI Kiosk P01–P04. Reports include summaries, ageing, SRC analysis, matched-pair exports, EOD digest emails, scheduled subscriptions and monthly reconciliation certificate PDFs. Controls include append-only audit logs, JWT and API-key authentication, IP allowlists, per-module permissions, product data scoping and session logging. It runs locally or in Docker as one container, with SQLite by default and MySQL or PostgreSQL options for production. A JSON API is documented through Swagger and ReDoc. Optional AI providers receive de-identified fields and return advisory output requiring human approval.
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.