Reconcile in minutes, not spreadsheets.
Rekfy matches your provider statements against your internal ledger and shows your team only the entries that don’t agree.
Built for finance and operations teams at payment companies and fintechs.
| Provider ref | Amount (NGN) | Result | Ledger ref | Amount (NGN) |
|---|---|---|---|---|
| PRV-48213 | 25,000.00 | Pending | TX-9921 | 25,000.00 |
| PRV-48214 | 8,400.00 | Pending | TX-9922 | 8,400.00 |
| PRV-48215 | 112,500.00 | Pending | TX-9923 | 112,000.00 |
| PRV-48216 | 3,000.00 | Pending | TX-9924 | 3,000.00 |
| PRV-48217 | 60,000.00 | Pending | – | – |
From raw statement to short exception list
Bring in your data
Upload provider files or push records through the API. Rekfy maps each provider’s columns to your format once and remembers it.
Rekfy matches
Exact matches first. Where it isn’t sure, it falls back to tolerance and fuzzy rules. Matching runs on a daily batch.
Your team clears breaks
Missing entries and amount differences land in a break queue, so people spend their time on exceptions, not on the 95% that agree.
What’s in it
Any match shape
One-to-one, one-to-many and many-to-many, with amount tolerance and fuzzy reference matching.
Files and API
Ingest CSV and Excel statements, or send entries as they arrive over a REST API.
Multi-tenant
Each customer’s accounts, sources and break queues are kept separate under one product.
Double-entry wallet ledger
The same ledger that powers matching can run customer wallets, so balances and reconciliation stay in one place.
Ask in plain languageIn development
A chat interface for reconciliation and wallet operations. Data is masked before it reaches any model.
Built in Go
A small, fast service with PostgreSQL underneath. Designed to start as a single API and split into services when volume needs it.
Still reconciling in Excel?
Rekfy is onboarding its first customers. Tell us how you reconcile today and we’ll set up a pilot on your own provider files.