Payment operations guide

Guided pilot: How to Reconcile Mobile Money Payments for ISP Billing

Guided pilot scope. A practical reconciliation workflow for provider references, invoice allocations, receipts, unmatched payments, and settlement exceptions.

Mobile-money scope
Workflow checklist

Qualify before rollout

Scope
Map
Test
Lab
Review
Pass
PlanConfirm the workflowRequired
TestCapture failure evidenceRequired
ReviewAgree recovery stepsRequired
Operating requirements, not live product results. Product readiness is stated below.
Page type
Guides
Primary search
reconcile mobile money payments ISP billing
Updated
2026-10-16

Reconciliation connects payment evidence to the right invoice

A subscriber's payment message, a provider transaction, an invoice allocation, and a bank settlement are different records. Reconciliation checks that they agree. It should answer who paid, which obligation the payment covers, whether the event is authentic, and whether the provider subsequently settled or reversed it.

Design the workflow around durable references. A phone number can help a reviewer investigate, but it is a weak sole matching key: someone may pay for a relative, change their number, or use a shared wallet. A screenshot is supporting evidence, not confirmation from the payment provider.

Architecture: preserve evidence before allocating money

Verified provider event / controlled statement import
                         |
         Normalize reference, amount, currency, status
                         |
             Deduplicate within provider account
                         |
                Match customer + invoice
                 /                    \
          Unique match             Unmatched queue
                 |                    |
          Allocation record     Finance review + reason
                 \                    /
                 Recorded payment + receipt
                         |
            Separate access-policy evaluation

Provider settlement statement --> Compare gross, fees, net
                                      |
                           Finance exception review

Retain the original provider reference alongside the internal payment and invoice identifiers. Scope lookups to the correct ISP tenant and receiving provider account. A reference collision across accounts must not move money between customers.

Verify callbacks using the chosen provider's documented authentication mechanism. Validate amount, currency, receiving account, and final transaction status before allocation. Do not assume a webhook format, signature method, or success code is shared across providers.

Roadmap requirements: M-Pesa paybill/till, MTN MoMo, and Orange Money

Use a separate mapping contract for each provider account and country. These are integration requirements to validate, not available ISPAgents clients.

Collection pathMatching evidence and operator decision
M-Pesa PaybillPreserve the business account, provider transaction ID, and customer-entered bill reference. Validate the reference against the intended invoice rather than trusting its spelling.
M-Pesa Buy Goods tillDo not assume a Paybill-style invoice reference is present. If the transaction cannot be linked uniquely, use the unmatched queue and verified provider evidence.
MTN MoMoPreserve the request reference and provider transaction identity separately. A request being accepted is not proof of completed payment; resolve its final status before allocation.
Orange MoneyConfirm the local merchant offer and integration contract. Keep the merchant/order reference alongside the provider payment record; rehearse missing and conflicting references.

Safaricom's Daraja C2B documentation distinguishes Paybill account references from Buy Goods transactions. MTN documents asynchronous payment status; Orange describes its merchant Web Payment offer. Confirm the actual product contract and supported market before implementation. Never invent a shared signature format or infer success from a subscriber's SMS.

Workflow example: clean, missing, partial, and duplicate payments

Use these illustrative records to rehearse a reconciliation process with mock data:

EvidenceExpected review outcome
Transaction LAB-TXN-A, reference LAB-INV-A, 1,500 units in the invoice currencyAllocate once if the receiving account, invoice, amount, and confirmed status agree.
A repeated event for LAB-TXN-APreserve delivery evidence without creating a second payment or receipt.
Transaction LAB-TXN-B, 1,500 units, blank invoice referenceHold in the unmatched queue; do not guess based on amount alone.
Transaction LAB-TXN-C, 600 units against separate invoice LAB-INV-C for 1,500 unitsAllocate 600 once, leave 900 due, and keep the service in its existing state unless the explicit eligibility policy says otherwise.
Transaction LAB-TXN-D, another 900 units for LAB-INV-CAllocate once; the combined 1,500 now meets this example's full-payment rule. Recheck holds before requesting restoration.
  1. Import or receive the records into a reviewable evidence store. Normalize provider timestamps without discarding their original timezone or value.
  2. Match LAB-TXN-A using the invoice reference and receiving account. Confirm that the invoice belongs to the intended customer and service.
  3. Record the allocation and create a receipt reference that links back to the payment. If receipt delivery fails, retry delivery without creating another financial entry.
  4. Put LAB-TXN-B in an unmatched queue with a reason, assigned reviewer, age, provider reference, and candidate invoices. Limit personal data to what the reviewer needs.
  5. Finance verifies the provider record and customer evidence, records the matching reason, and obtains a second approval when the operator's risk rules require it. Leave ambiguous cases unresolved.
  6. Compare the provider settlement statement with the accepted transactions. Check gross payments, separately recorded fees, net settlement, and any timing differences. Do not reduce a customer's invoice credit merely because the provider deducted a fee.

Decide separately when an allocated payment makes a service eligible for restoration. Settlement timing and service eligibility may follow different operator rules. Neither an unmatched event nor a payment screenshot should trigger an access change.

Operational risks

  • Duplicate delivery: deduplicate using the provider account and transaction identity, while retaining each delivery attempt for investigation.
  • Partial or excess payment: allocate the approved amount and keep the remaining balance or unapplied credit explicit; never silently write off a difference.
  • Late or reversed transactions: retain the original evidence and route adjustments through a reviewed reversal process. Recompute access eligibility separately.
  • Statement cutoffs: compare the same currency and accounting window; distinguish delayed settlement from missing money.
  • Manual matching errors: record who matched the payment, why, and which invoice was selected. Make corrections traceable.
  • Receipt confusion: distinguish the provider's transaction confirmation from the ISP's receipt for the recorded allocation.

These are controls to implement and validate, not claims that ISPAgents already supplies a complete finance recovery workflow.

Implementation checklist

  • Define a customer-facing invoice reference and a fallback review process.
  • Document the provider's callback authentication, statuses, retry rules, and statement format.
  • Test duplicate events, invalid authentication, wrong currency, and wrong receiving account with mocks.
  • Rehearse split payments, missing references, overpayments, and payments made by someone else.
  • Give the unmatched queue a named owner and escalation interval.
  • Link receipts and allocation history to provider evidence without exposing credentials.
  • Reconcile gross, fees, net, and settlement timing before closing a batch.
  • Validate the separate access-policy and reversal procedures before enabling any restoration automation.

Where ISPAgents fits

ISPAgents has guided-pilot foundations for invoices, payments, allocations, provider evidence, reconciliation, and settlement. Payment-provider presets, generic JSON webhook mapping, signature verification, and settlement-import parsers are also guided-pilot foundations.

Live M-Pesa Daraja clients are not shipped. M-Pesa, MTN, Orange, Airtel, and Wave settlement is not verified. Stripe Checkout, PayPal Orders, and Paystack initialize HTTP clients are implemented but not qualified; code-completeness and provider calls were not established in the review. Guided pilot: generic/Morocco mobile-money initiation remains static reference/URL preparation. Confirm the exact provider and evidence format during a guided pilot.

AR aging works and a USD statement read is verified; journal CSV export is implemented but its contents were not exercised. Tax/multicurrency posting, refund/reversal/receipt flows, credits/deposits/write-offs, settlement cycles, accounting sync, and production recovery remain unqualified. Accounting-grade customer billing is guided pilot scope. Automatic payment-to-access restoration is not a shipped promise.

Related solutions and guides

Review mobile-money ISP billing and ISP payment collection for pilot boundaries. Use the prepaid monthly billing guide , unpaid-invoice suspension guide, and guided-pilot automatic suspension scope to plan what should happen after a verified allocation changes a service's balance.

Frequently asked questions

Roadmap: does ISPAgents ship M-Pesa Daraja reconciliation?

No. Live M-Pesa Daraja clients are not shipped. MTN MoMo and Orange Money settlement is not verified. Payment mapping, reconciliation, and settlement foundations are available only for a guided pilot.

Pilot scope: should a partial mobile-money payment restore service?

Only if the verified allocation satisfies the documented service eligibility rule and no independent hold remains. A payment message or unmatched reference is not enough.

Next step

Discuss the scope for your network.