Who this suits
Businesses matching confirmed M-Pesa receipts to orders or invoices.
When a simpler option is a better fit
A daily reviewed statement import may be enough for low volume where live fulfilment does not depend on payment confirmation.
Proposed workflow
Capture confirmed payment records from an approved source
Match stable references and check amounts
Post only under the agreed finance rule and queue exceptions
Illustrative operating rules
Order-reference matching, duplicate receipts, partial payment, and exception review
Illustrative design example. Adapt these rules with the responsible team before implementation.
| Record or decision | Illustrative rule | Accountable owner |
|---|---|---|
| Duplicate receipt | Retain one allocation per verified receipt identifier | Finance operator |
| Partial payment | Allocate the received amount and leave the balance open | Accounts receivable |
| Missing reference | Hold the receipt for investigation rather than guessing | Finance reviewer |
Required inputs
- Approved payment access and records
- Order or invoice references
- Allocation policy and reconciliation owner
Limits and exceptions
Illustrative case: a KES 3,000 receipt against a KES 5,000 invoice leaves KES 2,000 outstanding. A repeated receipt event must not reduce the balance twice. A submitted payment request is not settlement evidence.
Scope and operating costs
Budget payment access, mapping, finance controls and monitoring. Production Daraja permissions and exact callback contracts require account-specific verification.
Acceptance and measurement
Reconcile receipt totals, allocated amounts and outstanding exceptions against approved statements. Test overpayments and late confirmations.
Questions before starting
What inputs does this workflow need?
Approved payment access and records; Order or invoice references; Allocation policy and reconciliation owner.
Product documentation
Documentation checked 11 October 2026. Access and costs must be confirmed for your account and intended workflow.
Discuss the scope and availability
Tell CraftDuka about the task, your current systems and the people who will use it. Our team is based in Nairobi and serves Kenya and East Africa. We will assess the fit and availability before agreeing a project.