Eko Recon vs OpenRecon
Eko Recon
github.comOpenRecon
naresh-paturi-community.github.ioSide by side
| Figure | Eko Recon | OpenRecon |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | — |
| Windows | Yes | — |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Account Reconciliation Software | 7.7 (#11) | 7.6 (#13) |
| Automation | Watch-folder uploads, cron schedules, automatic reconciliation after ingest and startup self-healing migrations are supported. | The CLI exits with a non-zero status when discrepancies exist, supporting scheduled and CI workflows. |
| Matching | Its priority-ordered rule engine matches transactions using TID, tracking number, UTR and amount rules, with amount-tolerance mismatch flags. | It first matches shared IDs or references, then matches remaining rows by amount, currency, and date window. |
| Purpose | Eko Recon is a full-stack bank reconciliation platform for fintech operations. | OpenRecon matches transactions across payment processors, gateways, and an internal ledger, and reports mismatches and missing transactions. |
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.
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.