Plinth holds your money on a real double-entry ledger. Every balance shows its work: what you hold, what you can actually spend today, and the entry behind every last pesewa.
GHS and mobile money first. No card details, no commitment. We open accounts in batches so we can set each one up properly.
The gateway dashboard, the bank statement and a spreadsheet someone updates on Fridays. When they disagree, nobody can say which one is wrong, and that is usually the week you find out.
The request times out. Did it send? Sending again could pay twice; waiting could mean a supplier is unpaid for a week.
Some of it is still settling, some is a reserve you cannot touch. One number cannot answer "can I pay this invoice today?"
Your accountant asks for a trial balance. You send exports, they send questions, and the answers live in four browser tabs.
Signature and all, even when we reject it as a duplicate.
A correction is a new entry that says what it reverses, and why.
Ordered by effective date, so two people reading it see the same thing.
What did not match is listed by reference and age, never netted off quietly.
The big figure is what you can send right now. The smaller one is everything recorded, including money still on its way from the gateway. In the console that difference is itemised line by line: what is still settling, what is already promised to a payout, what is ring-fenced in a reserve.
Open as many wallets as you need: operating, payroll, a chargeback reserve, each with its own account number and its own rules about who may take money out.
Keep operating money, payroll and a chargeback reserve apart. Each wallet decides whether it may pay out, go negative, or hold a floor, enforced when the entry is posted, not flagged in a report afterwards.
Pay suppliers and staff from a balance you can see. Changing account details creates a new beneficiary rather than editing one. The oldest trick in fraud stops being possible.
Tag every entry with branch, channel or product, then slice a P&L by any of them. Per-customer and per-supplier balances roll up to their control account and are checked against it.
Trial balance, balance sheet, P&L, account statements, settlement and payout history. Close a month with four checks and a lock, and see the difference before you commit to it.
Settlement batches are matched line by line. When something does not tie, you get the reference, the amount, the age and the account, not a red badge.
Separate books, separate keys, and an interface that changes colour entirely, so nobody confuses a rehearsal with a real payment.
Mobile money is not an afterthought bolted onto a card processor. Settlement takes a day, references collide, and the same payment can arrive twice. Plinth is designed around that, starting with Ghana and GHS.
Multi-currency is on the roadmap and the ledger already stores a currency on every account. We would rather do one country properly first.
Nothing is edited or deleted. A wrong entry is reversed by another entry that points at it and says why.
Who did what, when, from where. API keys are included, so an automated action is as accountable as a person.
Set an amount above which someone else must approve a payout. New beneficiaries cool off before they can be paid.
A key can read, or record, or move money. No pick-and-mix scopes to grant transfer rights by accident.
Every write takes an idempotency key. Retry a request after a timeout and Plinth returns the entry it already made instead of making a second one, and the developer log shows you the replay, so you can see the call that correctly changed nothing.
Retail, food, pharmacy, e-commerce: several branches or channels, and a need to know which one earned what.
Suppliers, riders, contractors, payroll. Approvals, caps and beneficiaries that cannot be quietly edited.
If your first task each month is rebuilding last month, this is for you. Bring your chart of accounts.
Funds sit with our payment partners and are recorded on your books here. Plinth is not a bank, and the console always shows what is held, what is still settling, and what you can actually send.
We are opening accounts in small batches so each one is set up with a chart of accounts that fits the business. Tell us where to write.
Or write to us directly: plinthtechnologiesconsult@gmail.com