Doocat

How African MFIs Can Reduce Fraud in Cash Loan Collections

Content authorBy DoocatPublished onReading time10 min read
A business manager discusses loan strategies in a bright office, holding a tablet displaying a banking dashboard, with employees working nearby.

Cash collection fraud shrinks when every repayment carries a unique, device-generated receipt reference tied to one borrower and one loan, and when the officer who collects cash never posts or reconciles it. Add daily handover matching and an independent borrower complaint channel, and most leakage becomes visible within 24 hours instead of months.

Where can collection fraud occur?

Collection fraud lives in the gaps between handoffs. A repayment passes from the borrower's hand to the officer's pocket and finally to a bank deposit. Each transfer is a point where value and record can separate: missing receipts and plain cash shortages at the end of the day.

Asset misappropriation, the category that covers skimming and cash larceny, appeared in roughly 90% of occupational fraud cases in the ACFE's 2026 study of 2,402 investigations across 143 countries. Which means the boring ones are your problem. If you map your collection chain and count how many handoffs produce no independent record, that count is a proxy for your exposure, and it's higher than operations managers expect.

What can fail at collection?

The borrower pays, and nothing provable happens. That's the core failure at the point of collection. An officer accepts cash without issuing an acknowledgment or writes down 3,000 when 5,000 changed hands. None of it is visible from head office until the borrower complains or an auditor visits.

The 1998 CGAP handbook on external audits of microfinance institutions describes this directly: loan officers collect and then steal clients' payments simply by failing to report what they received, and considerable time passes before a supervisor checks with the client. Twenty-eight years later, the mechanism hasn't changed, only the device in the officer's hand. So the control that matters is whether the borrower leaves the encounter holding evidence the institution can later match.

What can fail during posting?

Posting failures distort balances without anyone stealing anything. A tablet holds a batch of receipts for six hours before synchronization, so the portfolio report at 4 p.m. is wrong. An officer taps submit twice and creates a duplicate entry. A payment lands on the borrower's old loan rather than the current one. A back-office user corrects a figure without leaving a reason.

Musoni Kenya moved its loan officers from paper forms to a tablet application in 2013 and cut loan application forms from 11 to two pages, according to the Alliance for Financial Inclusion. Digitizing the capture step removes transcription errors, but it introduces timing errors in their place. That trade matters for investigations, because a balance that looks wrong at noon and right at 6 p.m. is a synchronization artifact, while one that stays wrong after full sync is something else entirely.

What can fail during handover?

Handover fails when the officer's counted cash and the bank deposit slip don't match. A shortfall anywhere in that chain means either a counting error or theft, and the chain itself rarely tells you which.

Ghana's central bank recorded suppression of cash and deposits losses of GH¢4.2 million in 2021 across banks and specialised deposit-taking institutions, up from GH¢2.3 million the year before. Suppression is the handover failure in its purest form: cash received, record withheld. The practical read for an MFI is that deposit timing deserves the same scrutiny as deposit amount, because an officer who banks Tuesday's collection on Friday has effectively taken a three-day interest-free loan, and that pattern almost always precedes a shortfall that doesn't get repaid.

Ready to digitise your financial institution?

Talk to our team about your roadmap and discover scalable digital banking solutions tailored to banks, fintechs and microfinance institutions.

Request a Demo →

How should one collection round work?

A loan officer records payments at a community center, surrounded by clean charts and a soft blue-white gradient background.

A clean round produces a matching trail at six points, and you reconstruct it from records alone. Here's an illustrative round for a field officer with 14 scheduled repayments. The borrower pays and receives a printed or SMS acknowledgment showing amount and a reference the device generated. That reference is unique across the whole institution. The payment allocates to one named loan, and the officer's running cash balance on the device increases by the same figure.

At day's end the officer's device total and counted cash show the same number. The next morning someone who collected nothing reconciles the deposit against the system. At the Association for Social Advancement in Bangladesh, loan officers write the day's expected collection on a blackboard every morning before leaving. Publishing the target before the round makes under-reporting a visible gap rather than a private decision, and that's the cheapest control in this entire article.

Which controls prevent common losses?

Each recurring loss type should have one preventive control and one evidence requirement. Documenting these responsibilities clearly eliminates ambiguity about who checks what and ensures accountability. According to the ACFE’s 2026 data, surprise audits were associated with 50% lower median losses and 50% faster detection, placing them among the four most effective anti-fraud controls measured.

The following framework outlines the warning signs, preventive measures, responsible reviewers, and evidence required for investigation:

  • Missing or skipped receipt numbers: Use device-issued sequential references as a preventive measure. The branch supervisor is responsible for reviewing them. Investigation evidence should include a full sequence export and borrower confirmation.

  • Posting more than 24 hours late: Implement a sync-age alert on every device. The operations manager is responsible for reviewing delays. Investigation evidence should include connectivity logs and device timestamps.

  • Duplicate records: Use server-side rejection of repeated references. The core system owner is responsible for reviewing duplicates. Investigation evidence should include both entries and their submission times.

  • Reversals: Require documented approval before posting. The head of credit is responsible for reviewing reversals. Investigation evidence should include the approval record, reason for reversal, and approver identity.

  • Allocation errors: Require loan selection exclusively from the borrower's profile. Internal audit is responsible for reviewing allocation errors. Investigation evidence should include the original receipt, corrected entry, and edit history.

  • Deposit shortfalls: Require same-day banking and independent reconciliation. Finance is responsible for reviewing discrepancies. Investigation evidence should include the deposit slip, handover sheet, and counted cash record.

Audit the audit schedule itself. A surprise visit that always falls on a Monday stops being a surprise by the second quarter.

How should offline collections be controlled?

Offline mode must behave as a queue with evidence. The device generates the unique reference locally and still produces borrower proof. Only then is working without signal acceptable. The coverage question is real: around 9% of Africa's population lives outside mobile broadband coverage, according to GSMA's Mobile Economy Africa 2026 report, and rural lending concentrates in exactly those areas.

On synchronization, the server should check five things:

  • Duplicate references already applied, returning the original result rather than creating a second entry

  • Gaps in the device's reference sequence

  • Timestamps that run backwards or sit outside the officer's working hours

  • Conflicting edits to the same record

  • Any batch held longer than your stated threshold

Treat an unexplained sync delay as an exception requiring a written reason, because the officer who controls when data arrives controls when discrepancies surface.

Ready to digitise your financial institution?

Talk to our team about your roadmap and discover scalable digital banking solutions tailored to banks, fintechs and microfinance institutions.

Request a Demo →

Is it fraud, error, or delay?

Separate the three before you accuse anyone. Use evidence rather than instinct. The ACFE's 2026 study found a lack of internal controls was the primary contributing weakness in 33% of fraud cases, with override of existing controls at 19% and absent management review at 18%. Weak controls produce errors and fraud in the same records, which is precisely why triage needs a fixed method.

Work through these in order:

  1. Did the officer report the discrepancy before anyone asked? Prompt self-reporting is the strongest single indicator of error.

  2. Does the connectivity log support the timing explanation?

  3. Has the same pattern recurred with the same person or location?

  4. Did anyone benefit personally, even temporarily?

  5. What does the correction history show about who edited what, and when?

One unreported discrepancy with a matching connectivity gap is a delay. The same discrepancy appearing monthly, always unreported, is a scheme you haven't named yet.

Which duties must remain separate?

No person should collect cash and reconcile it. Split those two at minimum, and separate the approval of reversals from the investigation of exceptions. The MFI Internal Audit and Controls Toolkit documents the opposite arrangement in a diagnosed institution where loan officers handled collection and bank deposits with no supervisory monitoring. The evaluator's conclusion was blunt about the control system being weak.

Reversals need documented approval from someone who didn't collect the payment, with the reason stored alongside the entry. And access rights must follow the person: when an officer transfers branches or leaves, revoke the old permissions the same day. I'd go further and audit dormant accounts quarterly, because a transferred officer who still holds posting rights at a former branch has every tool required and none of the oversight.

How can borrowers expose discrepancies?

Borrowers catch what your systems miss, provided the channel to reach you doesn't run through the officer in question. Publish a short code or phone number on every receipt and in every group meeting. Acknowledge each complaint within a stated window and verify the claim by matching the borrower's receipt reference against the posted balance.

Customers supplied 21% of all fraud tips in the ACFE's 2026 study, with vendors contributing a further 11%. For an MFI with thousands of weekly cash touchpoints and a handful of auditors, your borrowers are a larger detection network than your internal audit department will ever be, and they cost nothing to deploy.

Protect complainants from retaliation and say so publicly. Then track allegations by officer and by branch over rolling quarters, since one dispute is noise and five against the same officer is a case file.

What should managers check daily?

Eleven checks, every working day, before the next round starts. The ACFE's 2026 figures put the median time to detection at 12 months across 2,402 cases, unchanged from the 2024 and 2022 editions despite better technology. Daily review is how an MFI beats that benchmark, because a scheme that depends on records nobody reads dies the week someone starts reading them.

Check that the receipt sequence is complete with no gaps. Confirm a sample of borrowers by phone. Match the officer's cash balance to counted cash. Verify every collection has posted. Review offline exceptions and sync delays with written reasons attached. Confirm handover signatures exist for each officer. Match the bank deposit to the day's total. Review every correction for prior approval. Check open complaints against the officers named in them. Confirm no departed or transferred staff retain access. Finally, confirm the reconciliation was done by someone who collected nothing that day.

Can Doocat support these controls?

Yes, with verification through a configured pilot rather than a feature list. Doocat is a microfinance core banking platform built by Energize Global Services, a company founded in 2007 with delivery operations across Europe and Africa, and deployments in Zimbabwe and Ethiopia. Its agency banking module covers supervisor sign-off and a lightweight Android app designed for intermittent connectivity. The core platform carries tamper-evident audit logging across services.

Map your own collection chain against those capabilities, handoff by handoff, as you consult the controls table above. Then test the specific behaviors that decide whether fraud surfaces in a day or a year. Check what the device does with a duplicate reference on sync and who can approve a reversal. Check which alerts fire on a delayed batch and how fast access dies when an officer leaves. Request a pilot and run those four tests with your own data.

Ready to digitise your financial institution?

Talk to our team about your roadmap and discover scalable digital banking solutions tailored to banks, fintechs and microfinance institutions.

Request a Demo →

Track receipt-sequence completion, same-day posting, sync delays, cash-to-deposit differences, approved reversals, and borrower complaints. Compare these measures by officer and branch each week, then investigate repeated exceptions rather than isolated errors. A falling exception rate matters only when review records show that staff resolved discrepancies promptly.

Record the shortage before changing any transaction, preserve the receipt sequence, device timestamps, handover sheet, counted cash record, and deposit slip. Ask the officer for a written explanation, then compare it with connectivity and edit logs. Keep collection, reconciliation, and investigation duties separate while the discrepancy remains open.

Yes. Staff can verify the claim by checking the borrower’s loan, payment date, amount, officer assignment, and posted transaction history. The complaint channel should accept the borrower’s phone number or another identifier when the reference is unavailable. Record the outcome and look for repeated claims linked to the same officer.

The officer’s permissions for the former branch should be revoked on the transfer date, while new access should match the assigned branch and duties. Managers should review pending offline batches, unsettled handovers, and dormant accounts before closing the old access. Keep the transfer record so later edits can be traced to the right branch.

Test the controls with realistic borrower and repayment records before full deployment. Confirm that offline receipts remain unique, duplicate references are rejected, delayed batches trigger alerts, reversals require approval, and a departing officer loses access promptly. Have finance and operations review the results together, then document failures and retest after corrections.

Schedule a Meeting

Book a time that works best for you

You Might Also Like

Discover more insights and articles

Two diverse professionals engaged in a friendly discussion over a tablet in a bright, modern office with large windows and blurred coworkers.

Murabaha Financing: Contracts and Examples for African Banks

This article walks through how murabaha financing becomes a working bank product: the transaction sequence and the controls your core system has to enforce. It is written for the teams who have to build the thing and then defend it in an audit.

A mid-aged manager reviews documents at a warm wood desk in a sunlit office, with a monitor displaying analytics in the background.

SACCO Management System: A Buyer’s Guide for Kenyan SACCOs

This article walks through how a Kenyan savings and credit cooperative can define what it actually needs from new software and check vendor claims against evidence before it plans a migration that doesn't break member balances. It ends with a checklist you can score vendors against before any price talk begins.

Close-up of hands holding a smartphone displaying a banking app, set in a cozy home office with blurred background elements.

Mobile Money Interoperability in Ghana: How GhIPSS MMI Works

This article maps the four transfer flows supported by Ghana's national mobile money interoperability platform and shows who owns each step of them. It covers transaction direction and the questions to settle before a new connected channel goes live.

A business-casual office worker demonstrates a payment process on a smartphone to a customer in a bright, modern office setting.

Ijara Financing: Asset Leasing Workflows for African Banks

This article walks through how an asset-based lease moves from supplier quotation to contract closure inside a bank, and what each step leaves behind in documents and system records. It is written for the teams that have to build or review that workflow together.