Every transaction
accounted for.
Tarakibu reads the settlement files you already download, puts them next to your own ledger, and tells you what doesn't line up — so revenue stops leaking quietly and you find out about a problem the morning it happens, not at month end.
Free through 31 October. No contract. Nothing to install.
- INV-40012KES 5,302.00
- INV-40013KES 1,455.00
- INV-40014KES 23,330.00NOT PAID
- INV-40015KES 850.00
- INV-40016KES 3,189.00
- TJ7G8KM42KES 5,302.00
- TJ6G6JM76KES 1,455.00
- TJ4C2LM18KES 850.00
- TJ9K1PM03KES 4,120.00NO INVOICE
- TJ2H5NM61KES 3,189.00
Everything accounted for
Every payment on every statement is either matched to your records or shown to you with a reason. Nothing is quietly dropped because it did not fit.
Revenue stops leaking
Fees charged above your contracted rate, settlements that never arrived, refunds taken twice. Small amounts, every day, that a monthly spreadsheet is not built to catch.
You find out early
A closing balance that does not foot, a paybill that stopped settling, a match rate drifting downwards. Visible the same morning, not at quarter end.
Files that should agree, and a spreadsheet in the middle.
An M-Pesa statement. A card gateway report. A bank breakdown. And an internal ledger that names its columns differently from all three. Somebody pastes them side by side, writes a VLOOKUP, and spends the morning finding the eleven payments that don't line up.
Money you were paid and never recorded
The provider notified your system, your system missed it. The payment is real, the ledger doesn't know, and your margin is overstated until someone finds it.
Money captured but never settled
The card gateway says it took KES 3,286. The bank never paid it across. Invisible in a two-file check, and it sits there for months.
Fees above the rate you agreed
Nobody checks 800 billing lines against a contract every month. A misapplied rate card compounds quietly, quarter after quarter.
Reconcile, then price, then prove.
Check your records against theirs
Equity, KCB, M-Pesa Paybill and Airtel Money come already configured — the column names, which rows count, which to set aside. You describe your own file and nothing else. Anything not on the list, you set up once and keep.
Every account in one pass
Drop in all your statements at once. Tarakibu works out which paybill or account each one belongs to, totals what you're holding across every one of them, and reconciles the lot as a single check.
Follow it through to the bank
Add your bank statement and it sorts settlements from refunds, chargebacks and charges by reading the narration. Where the bank pays in lump sums, each one is tied back to the breakdown that explains it.
Work out what each merchant is owed
Fees, reserves, settlement charges and net margin, per merchant, from your own pricing — with every fee compared against your contracted rate to catch what you were overcharged.
How much are we holding, right now?
If you collect across dozens of paybills or acquiring accounts, the first question of the day isn't reconciliation. It's how much is sitting where — for funding, for sweeps, for knowing whether anything has gone quiet.
Drop every statement in together. Tarakibu reads the paybill out of each file, gives you the closing balance on all of them and one consolidated figure, and tells you if a statement doesn't add up — which is how you find out a download was cut short before you build a number on it.
Then it reconciles all of them against your ledger in a single pass, and breaks the answer down per paybill. The whole thing exports to Excel: balances, reconciliation, every file, and the exceptions, on separate sheets.
| Paybill | Money in | Closing balance |
|---|---|---|
| 201001 | 1,035,601.69 | 7,235,601.69 |
| 247247 | 3,445,561.55 | 14,845,561.55 |
| 303030 DOESN'T FOOT | 5,135,589.28 | 14,035,589.28 |
| 412412 | 1,359,342.80 | 5,109,342.80 |
| 522522 | 2,165,251.16 | 9,265,251.16 |
| …and nine more | ||
| Consolidated | 21,271,190.97 | 80,626,945.41 |
Your files are read on your machine.
When you drop a settlement file into Tarakibu it is read in your browser. The file itself is never uploaded, on either plan — not to us, not to anyone.
- The statements and exports you upload
- Card numbers, phone numbers, customer names inside them
- Anything you do not explicitly save
- Your checks: which columns mean what, and your matching rules
- Notes and decisions your team writes on unresolved payments
- The reconciled result, so you can search it months later
We are deliberate about the difference. Keeping the reconciled result is what lets somebody find a payment from July in November — the single most requested thing by people who do this daily. Keeping the raw files would buy nothing and cost you a procurement review.
Nobody at Ops Edge can read your checks, your notes or your figures unless you switch support access on yourself. It lasts a few hours, it closes on its own, and everything done while it is open is listed for you to read afterwards.
Payment providers, and the teams who carry the numbers.
If you collect on behalf of merchants across mobile money and card rails, settle to them on a cycle, and hold a reserve against refunds — this was built from the inside of your job.
Settlement & finance operations
The morning check. What came in, what matched, what has to be chased before anyone notices.
Treasury
What is sitting across every paybill and account this morning, and what is free to move.
Revenue assurance & control
What each merchant should have been paid, what the processor should have charged, and numbers you can stand behind.
Built for the rails you actually use.
Anywhere else, you set your provider up once in about a minute and it's saved for next time — and if you send us the column headings, we turn it into a ready-made setup everyone gets.
From your files to an answer.
Pick who you're checking against
Choose your bank or mobile money provider. Their side is already described — you never have to explain an M-Pesa statement to us.
Add your files — one, or all of them
Drop in the export your system produces, and every provider statement you've downloaded. They're read in the browser, so nothing is uploaded and nothing is stored.
Point at the reference
Whether it sits in its own column, is buried inside a line of description text, or exists only in a separate lookup file — all three are handled.
Run it, and run it again tomorrow
Matched, needs a look, and not matched — broken down per account, exportable to Excel or CSV. Anything you can't resolve today, mark it and leave a note; it's still there next time that payment comes up.
Reconciliation is where it starts, not what it is.
The same proved data answers harder questions. These are being built in the order pilot users ask for them.
Checking & settlement
WORKINGMatch against any bank or mobile money provider, and follow the money through to your account.
Balances across every account
WORKINGClosing balance per paybill or account, one consolidated figure, and a check that each statement adds up.
Merchant pricing & margin
WORKINGPer-merchant payouts, reserves, net margin, and fees charged above your contracted rate.
Journal entries
NEXTReconciled figures posted to NetSuite or Oracle — merchant payables, fee revenue, reserve, tax.
Shared exception queue
NEXTUnresolved items assigned to named people, with ages and deadlines, visible across a team.
Chargeback recovery
NEXTProof that disputes you won were actually credited back, and that the ones you lost were recovered.
Anomaly & fraud signals
AFTER THATTold on the morning it happens, rather than at month end, when today stops looking like a normal day.
Collection by API and SFTP
AFTER THATFiles pulled on a schedule by API or SFTP, so the morning check is waiting when you sit down.
Three ways in. One set of rules.
You describe a provider's file once — which column is the reference, which is the amount, how to read the narration. After that it does not matter how the file reaches us. The rules, the matching and the reports are identical.
Upload
Somebody drops this morning's files in. Sixty paybill statements at once if that is what you have. The fastest way to start, and the only one that needs nothing from your IT team.
Send by API
Your system posts transactions to us as they settle, with a key you can revoke. Repeats are ignored rather than double-counted, and a batch is taken whole or not at all — half a batch reconciles cleanly and is wrong.
Collect by SFTP
We fetch the file from your server, or your bank's, on a schedule. For the providers who drop a file at 6am and expect you to go and get it.
A connection can change how it collects without being set up again. Start by uploading this week, move to API when your engineers have a spare sprint, and nothing about your checks changes.
Free until you need more than yourself.
The reconciliation engine is the same on both. Every check, every report, the Excel export. What changes is how much you can put through it, what you can connect to it, and whether your colleagues can reach the work.
For one person, checking by hand, with the files they already download.
- The full reconciliation engine — two-way, three-way, bank leg, balances
- CSV uploads
- Up to 10,000 rows per run
- Excel export, five sheets
- Records kept and searchable for 30 days
- Your files read on your own machine, never uploaded
For an operations team carrying the numbers between them, at volume.
- Everything in Free
- Every file format — CSV, Excel, fixed-width, JSON, XML
- No row limit
- Records kept and searchable for a year
- Several people, one shared workspace
- Hand an unresolved payment to a named colleague, with notes
- Shared checks and provider setups — nobody redescribes an M-Pesa statement twice
- Send transactions by API as they happen
- Collect settlement files by SFTP on a schedule
What this version can't do.
Better you read it here than discover it on day three.
- Chargeback recovery is not built. Tarakibu will show you a chargeback on a statement; it will not work the dispute for you.
- No journal entries out to NetSuite or Oracle. You get an Excel export and post it yourself.
- Files are added by hand. Sending transactions by API and collecting them by SFTP are being built, and are not there yet.
- Comfortable to about 10,000 rows per file, workable to 50,000.
- Everything on the roadmap above marked NEXT or AFTER THAT is genuinely not built.
Built out of a decade doing this job.
Tarakibu comes out of more than ten years inside banking and fintech operations in this region — credit risk, finance operations, settlement workflows, chargeback management.
Different institutions, the same conversation every time: we know the numbers are slightly wrong, we just don't have time to prove where.
It knows that a card gateway lists the same payment three times, and that an M-Pesa statement sometimes hides your reference inside a sentence, because those were our mornings.
It is early, and we are building it alongside the people using it. If you try it and it does not fit your files, we would rather hear that than not — it is the fastest way this gets better.
Bring one real file.
The pilot is free, has no contract, and runs to 31 October. We're taking a small number of teams so that everyone gets attention — and because what we want back is honest criticism, not signups.
FREE TO START · NOTHING TO INSTALL · YOUR FILES STAY ON YOUR MACHINE