Across hundreds of African companies, expense management runs through WhatsApp
An employee buys something for work — fuel, a client lunch, a piece of equipment — takes a photo of the receipt, and forwards it to their manager or finance contact. The finance person says "noted" and saves the image somewhere. This works fine when there's one or two of these a week. The moment it's ten or twenty, things start to fall apart. The problems compound quietly. Images get lost in chat history. Context disappears — what was this purchase for? Which project does it belong to? Was it approved beforehand or is this a retroactive request? When month-end comes around, the finance team is piecing together a puzzle from dozens of conversations across different chats. The information technically exists, but it's not usable. Receipts without context aren't records — they're just images.
And the problem scales faster than most finance teams expect. A company with 20 employees submitting 3 expenses each per month is managing 60 receipt images across WhatsApp threads, with no consistent format, no audit trail, and no way to query what was actually spent on what. At 50 employees, that's 150 images a month. At 100, it's unmanageable — and yet most companies at that size are still running exactly this system.
What a receipt actually needs to be
A receipt isn't just an image. It's a record — and a record only has value when it carries the right context with it. A properly captured expense links a receipt image to:
- A specific amount, confirmed at the point of submission
- A reason for the purchase
- An approval from a named person, with a timestamp
- A project or department code
- The currency it was incurred in — locked at submission, not converted later
That chain of context is what makes the expense auditable, reportable, and useful to the business. A WhatsApp message with a photo attached has none of that structure. The information might exist somewhere across the thread, but extracting it and turning it into something a finance team can work with requires manual reconstruction — every single month.
The most common workaround is the shared spreadsheet. A finance manager spends hours each month transferring information from WhatsApp images into a Google Sheet — typing amounts, guessing categories, chasing employees for missing details. It feels like progress. It isn't. The data is only as accurate as the person doing the typing, and there's no guarantee that what's in the sheet matches what was actually spent.
Why this matters more as you scale
The WhatsApp system doesn't break immediately. It degrades gradually, and usually at the worst possible moment — when the company is growing, headcount is increasing, and the finance team is already stretched. Audit risk increases. If your business is ever audited — by the Federal Inland Revenue Service (FIRS) in Nigeria, the Kenya Revenue Authority (KRA), or a donor conducting a financial review — a folder of WhatsApp screenshots is not an acceptable expense record. FIRS audit requirements specify that expense documentation must include the nature of the transaction, the amount, the vendor, and evidence of approval. A WhatsApp photo of a POS receipt with "noted" as the approval trail fails every one of those criteria.
The lack of a structured approval chain is a compliance problem, not just an inconvenience. Reporting becomes impossible. You can't run a report on WhatsApp. How much did the team spend on travel last quarter? Which department is consistently over budget? Which project is burning through its allocation? These questions have no answer when the data lives in chat threads.
Finance managers at growing African companies regularly describe the same scenario: they can tell you the company is spending money, but they can't tell you exactly where, by whom, or whether it was within policy. Finance capacity gets consumed by reconciliation. Every hour a finance manager spends chasing receipts and reconstructing context is an hour not spent on analysis, forecasting, or the work that actually moves the business forward. In a 50-person Lagos company, a finance manager spending 3 hours per week on manual expense reconciliation is losing more than 150 hours a year — nearly a full month of working time — to a process that proper tooling eliminates entirely.
The fraud surface is wider than most companies realise. When receipts are submitted as WhatsApp photos, there's no systematic way to catch duplicate submissions — the same receipt submitted twice in different threads, weeks apart. There's no way to flag inflated amounts on cash transactions where the employee has filled in a blank receipt. And there's no audit trail that would surface either problem during a review. The informal system doesn't just create inefficiency. It creates financial exposure.
A better process doesn't have to be complicated
The improvement isn't about adding bureaucracy. It's about capturing the right information at the right time, in the right place. When an employee submits an expense — with the receipt attached, the amount confirmed, the reason stated, and the relevant project or department selected — that's everything finance needs. A good tool makes that submission take less than a minute from a phone the employee already owns.
Farthingly's Penny AI does the heavy lifting at the point of capture. An employee snaps a receipt, and the system reads the amount, date, merchant name, and currency automatically. The employee confirms and submits. The expense enters an approval queue with full context attached — no manual data entry, no chasing for details. The result is a clean, queryable record that doesn't require anyone to dig through old chats. Approvals happen in the tool, with a timestamp and a named approver. Month-end becomes a review process, not a reconstruction exercise.
What to look for in a replacement
If your team is ready to move off WhatsApp, the bar for a replacement isn't high — but a few things matter specifically for African teams:
- Mobile-first submission that works on mid-range Android. Most of your team isn't using the latest iPhone on fast Wi-Fi. The tool needs to work on a mid-range Android device over 3G, because that's the reality for field teams across Nigeria, Kenya, and Ghana. Receipt scanning that fails on low-resolution POS receipts or informal vendor formats isn't useful.
- Simple approval workflows that match how your organisation actually works. Most African companies don't have the flat org structure that Western expense tools assume. Field offices, matrix management, and multi-entity setups require approval routing that can be configured to match how decisions actually get made — not forced into a hierarchy that doesn't fit.
- Multi-currency support for African currencies. NGN, KES, GHS, ZAR — treated as first-class currencies, with rates locked at submission time. If your tool converts everything to USD at reporting time, you lose the actual transaction amounts every time the naira moves.
- Reimbursement through local payment rails. Bank transfer and mobile money — M-Pesa, MTN Mobile Money, Airtel Money, Paystack — need to be first-class reimbursement options, not workarounds. An employee in Nairobi shouldn't need a USD account to get reimbursed for a business expense.
- A proper audit trail. Every submission timestamped, every approval named, every amount locked at entry. Not because you expect to be audited — but because clean records are what give a finance team actual visibility into where money is going.
Farthingly was built specifically for this transition — from informal WhatsApp-based expense tracking to a structured process that gives finance teams clean records and employees a submission experience that takes less time than sending a chat message. If your team is still running expenses through WhatsApp groups, the problem isn't your people. It's the system. And the system is fixable. Start your free trial at farthingly.com →