Every few years, a Kenyan county decides its revenue system is not working. The collections look low, reconciliation takes weeks, and nobody can say with confidence how much was collected through which channel. So the county does the only thing the market lets it do: it procures a new system.
That means new collection points, new integrations with banks and mobile money, new training for revenue officers, and a long overlap where two systems run side by side and the numbers in neither can be trusted. The county pays again for capability it already paid for once.
At Moffhub Solutions we think the problem is not any single vendor. The problem is that the county does not own the layer underneath them.
The rails, not the train
PayOrchestra is the payment backbone we built for county governments. It sits between the county and every channel that collects money on its behalf. Mobile money, banks, agency networks and existing revenue platforms connect to it as connectors.
Because every shilling passes through one layer the county controls, three things change:
- One view of collections. Treasury sees every channel in one place, reconciled daily rather than discovered at the end of a quarter.
- Vendors become replaceable. If a collection partner underdelivers, the county disconnects it and connects another. The rest of the system keeps running. Changing a vendor stops being a procurement crisis.
- The county keeps control. The county owns the platform and its source code.
EREV: the revenue system on top
For counties that want a full revenue system, EREV runs on the PayOrchestra engine. It is modular: a county picks the modules for the revenue streams it needs now and plugs in others later. The county owns it outright.
Counties that are happy with their current revenue system can take PayOrchestra on its own, as a reconciliation and diagnostics layer over what they already run.
Built on delivery experience
This design comes from systems we have already delivered. In 2023 our team delivered the build for a county revenue system, a platform built to handle upwards of 600,000 transactions a month. The lesson from that work was simple: the hardest part of county revenue is not collecting money, it is proving where every shilling went.
What we would ask a county treasury
• Can you see yesterday's collections, by channel, this morning?
• If your main revenue vendor left tomorrow, what would it cost you to replace them?
• Who owns the code your revenue runs on?
If any of those answers is uncomfortable, we would like to talk