The Treasurer's Phone Is the Treasury: Mobile Money Terms for US–Cameroon Partnerships
Photo by Photo by Zac Wolff on Unsplash on Unsplash
A US foundation signs a modest agreement with a community association in the Southwest Region. The term sheet is careful: budget lines, reporting dates, a named project lead. Then comes the practical question of how money actually reaches the group, and the answer is a phone number. The funds move by MTN MoMo or Orange Money, the treasurer reads out a code, and the project begins. Nothing about that sequence is unusual. What is unusual is how rarely the sequence appears in writing.
Mobile money is the working treasury of a great many Cameroonian associations, cooperatives, and church-linked committees. Treating it as a mere last mile—something handled after the agreement is signed—leaves the most frequent transaction in the partnership governed by habit rather than by terms. The remedy is not a longer contract. It is one focused clause, or a short schedule attached to the term sheet, that answers the questions a treasurer and a program officer will otherwise answer differently.
Why this rail warrants its own schedule
US partners are accustomed to describing payment mechanics precisely when the channel is a bank: routing numbers, authorized signatories, wire cutoffs, confirmation protocols. Mobile money deserves the same discipline, because it carries the same risks at higher frequency and lower value. A partnership that moves twenty small transfers a month has twenty opportunities for a misdirected payment, an unrecorded fee, or a disputed receipt. Frequency, not size, is what makes the rail worth codifying.
Naming the holder and the custodian of the SIM
The first clause should identify the registered mobile money account holder by full legal name and by the MSISDN registered with the operator. Where the registered holder is the association itself, the clause should say so and attach the registration evidence. Where the holder is an individual—common in practice—the agreement should state that fact plainly, describe the handover arrangement if that person leaves office, and confirm that the organization's governing body has authorized the arrangement.
Custody of the physical phone and SIM is a separate question from registration and should be addressed separately. A useful pattern assigns the handset to one officer and the approval authority to another, so that no single person can both initiate and release a payment. Recording the SIM serial number and the operator at signature is a small step that simplifies recovery if a handset is lost.
Limits, tiers, and the discipline of the large transfer
Operators impose balance ceilings and transaction ceilings that vary with the customer's verification tier. A clause that ignores this will eventually collide with a disbursement larger than the account can absorb. The agreement should require the Cameroonian partner to disclose its current tier in writing at the outset and to notify the US side before any change in status.
For tranches that exceed the ceiling, the schedule should name the fallback in advance: a sequence of transfers across several days, a merchant or business account with higher capacity, or a bank transfer for the largest installment. Splitting payments purely to evade a limit is a compliance problem, not a workaround, and the clause should say so. The point of planning is to keep every movement of funds inside the operator's rules.
Fees, float, and the meaning of the stated amount
A grant of a stated sum should arrive as that sum. Mobile money transactions carry transfer fees and cash-out charges, and the incidence of those charges varies with the operator, the amount, and the channel. The agreement should state explicitly whether fees are absorbed by the sender, deducted from the transfer, or charged to the recipient at withdrawal, and it should confirm that the project receives the full budgeted figure.
The clause should also note the currency. Amounts are denominated in CFA francs, and the US partner's internal records will show dollars; the conversion basis and the date of conversion belong in the reporting schedule, not in an email thread.
Receipts that survive an audit
A screenshot of a confirmation screen is a weak record. The clause should require, for every transfer, the operator-generated transaction identifier, the timestamp, the sender and recipient numbers, the gross amount, and the fee. These should be filed to a shared drive within a set interval—forty-eight hours is workable—rather than reconstructed at reporting time. Monthly statements exported from the operator's own interface give the US partner an independent check against the partner's ledger.
Reconciliation as a shared ritual
Reconciliation is where a payment rail becomes a governance system. The schedule should assign responsibility for a monthly comparison of transfers against budget lines, name who performs it on each side, set a variance threshold above which an explanation is required, and tie the exercise to the existing reporting calendar. Keeping the ritual monthly rather than annual keeps discrepancies small enough to resolve by conversation.
Fraud, impersonation, and the callback rule
Mobile money fraud in the region often relies on social engineering rather than technical breach: a message purporting to come from a director, a request to change a number, a plausible story about a lost phone. The clause should establish that payment details change only through a documented, dual-confirmed process, never by email or messaging application alone, and that any change is verified by a callback to a number already on file. An initial test transfer of small value, confirmed by both sides before larger sums move, costs little and settles doubts.
Elements of a workable clause
- Registered holder name, MSISDN, operator, and SIM serial, recorded at signature.
- Named custodian and named approver, with a two-person rule for releases.
- Disclosed verification tier and a pre-agreed fallback for large tranches.
- Stated incidence of fees and confirmation that the project receives the full amount.
- Required transaction identifiers and a filing deadline for each receipt.
- A monthly reconciliation step with a named owner and variance threshold.
- A callback rule for any change to payment details, and a test-transfer protocol.
The phone in a treasurer's hand is not a lesser account. It is the account. Writing its terms down is the same act of respect a partnership extends to any other instrument it relies on—and it is the cheapest insurance against the small misunderstandings that, left alone, become large ones.