Mobile Money: Transforming Payments and Expectations
Mobile money didn't just change how people pay. It changed what people expect payments to feel like. Before M-Pesa, before MTN MoMo, before Airtel Money, sending money to someone in a different town meant a bank transfer that took two to three business days — if both parties had bank accounts, which millions of people didn't. Mobile money made the transfer instant, cheap, and available to anyone with a basic phone. That shift in what a payment could be didn't stay in the consumer space. It moved into how businesses think about paying people, moving money between locations, and settling expenses with employees in the field. But the business tooling hasn't kept pace with the rails. The infrastructure for moving money in African markets is genuinely world-class. The layer above it — the software that connects a payment to an expense record, an approval, a report — is still catching up. That gap is where the most interesting work in African business finance is happening right now.
What Mobile Money Actually Solved
The core problem mobile money solved was access. Sub-Saharan Africa has some of the lowest traditional banking penetration rates in the world — in many markets, more than half the adult population doesn't have a formal bank account. The reasons are structural: branch networks concentrated in urban centres, account minimums that exclude low-income earners, documentation requirements that many people can't meet. Mobile money bypassed all of that. A SIM card was the only requirement. The agent network brought access to rural areas that formal banking never reached. And the smartphone wasn't even necessary — the original M-Pesa interface ran on basic feature phones via USSD.
The scale of adoption reflects how significant the access problem was. M-Pesa alone processes more than $300 billion in transactions annually and has over 50 million active users across Africa. MTN MoMo operates across 16 markets on the continent. Airtel Money is present in 14. These aren't emerging payment methods hedging against the growth of traditional banking — they are the primary payment infrastructure for a significant proportion of the continent's population and businesses.
The speed dimension matters too. Mobile money transactions settle in seconds. That's not just a convenience feature — it changes the fundamental expectation of what a payment is. For employees waiting on expense reimbursements, the difference between "your transfer will arrive in two to three business days" and "your M-Pesa notification just came through" is the difference between a process that feels broken and one that feels like it works.
The Gap on the Business Side
For consumer use cases — sending money to family, paying a merchant, splitting a bill — mobile money infrastructure is complete. The rails work, the interfaces are mature, and the user experience has been refined over fifteen years of iteration. For businesses, particularly those managing employees across multiple locations or running field operations, mobile money created a new set of questions that the consumer infrastructure wasn't designed to answer.
When a finance team reimburses an employee via M-Pesa, how do they record it in their expense system?
How do they attach the payment to the specific expense it's covering?
How do they verify that the amount transferred matched the approved amount, not the submitted amount?
How does that reimbursement appear in their month-end reporting alongside expenses reimbursed through bank transfer or corporate card?
In most companies today, the answer to all of those questions is: manually. The M-Pesa transfer happens outside the expense system. Someone screenshots the confirmation. The finance team logs it in a spreadsheet. At month-end, someone reconciles the spreadsheet against the expense records and the bank statement and hopes the numbers agree. This is the gap. The payment rails exist and they're excellent. The business tooling that should sit above them — connecting payments to records, approvals, and reports — largely hasn't been built for the African context.
Why Western Expense Tools Don't Solve This
The major expense management platforms — Expensify, SAP Concur, Ramp, and their peers — were built for markets where corporate cards are the dominant reimbursement mechanism and bank transfers handle everything else. Mobile money isn't part of their model, and it isn't an easy feature to add after the fact. The issue isn't just integration. It's that the entire workflow in these tools assumes a particular reimbursement infrastructure. Approval triggers a bank transfer. The bank transfer references the expense record. The expense record closes. That chain works cleanly when your payment rails are Western banking infrastructure. It doesn't work when your primary reimbursement method is M-Pesa, because M-Pesa isn't connected to any of it.
African businesses using these tools end up running two parallel systems — the expense tool for submissions and approvals, and a separate manual process for the actual reimbursement. The result is the same reconciliation problem they had before the tool, just with an extra step in the middle.
The Infrastructure is Already There
What makes this moment interesting is that the hard problem — building reliable, scalable payment infrastructure — has already been solved in many African markets. Paystack and Flutterwave collectively process billions of dollars in transactions annually across the continent. Their APIs are mature, well-documented, and used by hundreds of thousands of businesses for everything from e-commerce payments to payroll. The reliability and coverage of these platforms rivals payment infrastructure in developed markets. M-Pesa's API has been available to developers since 2013. MTN MoMo's open API programme has been actively expanding.
The technical foundations for connecting expense management workflows to mobile money reimbursements are in place. The opportunity isn't to rebuild payments from scratch. It's to build the layer above the existing infrastructure — the software that takes an approved expense, triggers a reimbursement through the appropriate rail, records the payment against the expense record, and closes the loop in a way that makes month-end reconciliation straightforward rather than a multi-day reconstruction exercise.
What First-Class Mobile Money Support Actually Looks Like
There's a difference between an expense tool that technically supports mobile money and one that treats it as a first-class reimbursement method. The distinction matters in practice. Technically supporting mobile money might mean: the tool allows you to log that a reimbursement was made via M-Pesa. That's marginally better than nothing. It doesn't close the reconciliation gap, it doesn't verify the payment, and it doesn't connect the reimbursement to the approval that preceded it in any automated way.
First-class mobile money support looks different:
The reimbursement is triggered from within the expense tool — when a finance manager approves a reimbursement, the M-Pesa or MTN MoMo transfer initiates directly, without requiring a separate action in a separate system.
The payment is recorded automatically against the expense record — the transfer confirmation closes the expense in the system, creating a complete audit trail from submission through approval to payment.
The amount is verified — the system confirms that the amount transferred matches the approved amount, flagging any discrepancy before it becomes a reconciliation problem.
It appears in reporting alongside other payment methods — mobile money reimbursements, bank transfers, and card payments all show up in the same expense reports, in the same format, without requiring manual consolidation.
That's the workflow that makes mobile money genuinely useful for business expense management rather than just a payment option that exists somewhere outside the system.
Where Things Are Heading
Business finance tooling in Africa is catching up, and the pace is accelerating. The teams building in this space are increasingly starting from what African businesses actually need rather than adapting products designed for Western contexts. That means mobile money as a default reimbursement method, not an edge case. It means expense tools designed for Android-first, variable-connectivity environments. It means multi-currency support that treats NGN and KES as first-class currencies rather than unsupported edge cases. It means approval workflows built for the org structures common in growing African companies — field teams, matrix management, multi-entity setups — rather than the flat startup hierarchy most Western tools assume.
The convergence of mature payment infrastructure, growing smartphone penetration, and a generation of founders building specifically for African business contexts means the gap between the payment rails and the business tooling above them is closing. The companies that build the right layer — the one that connects M-Pesa to an expense record to an approval to a report — are positioned to serve a market that the incumbents have never seriously competed for.
That's what we're building at Farthingly. If you want to see what expense management looks like when it starts from Africa rather than adapting to it, start with a free trial.