Skip to main content

Integrations / CraftDuka

ERPNext and M-Pesa receipt allocation

Prepare ERPNext payment records from confirmed receipts and reviewed allocations. Keep unmatched payments and overpayments visible until finance decides how to post them.

Who this suits

Finance teams matching M-Pesa receipts to ERPNext invoices.

When a simpler option is a better fit

A controlled import can be simpler for low-volume daily reconciliation.

Illustrative event and field map

Receipt-to-invoice matching, payment states, overpayments, and review of unmatched entries

Illustrative design example. Adapt these rules with the responsible team before implementation.

ERPNext and M-Pesa receipt allocation: decisions and ownership
Record or decisionIllustrative ruleAccountable owner
Invoice matchUse approved reference and account checksAccounts receivable
OverpaymentHold the excess under the agreed finance processFinance reviewer
Unmatched receiptKeep amount and source reference in the review queueReconciliation owner

Data flow and sync direction

  1. Capture verified receipts with stable identifiers

  2. Match the customer and invoice under finance-approved rules

  3. Create a reviewed payment entry or exception task

API and account prerequisites

  • ERPNext version and accounting permissions
  • Approved payment source
  • Invoice references and finance allocation policy

Limits and exceptions

Posting must respect the ERP's accounting state and permissions. A duplicate receipt cannot create another payment entry. Do not guess an invoice from a similar amount alone.

Implementation cost drivers

Estimate receipt volume, matching complexity, accounting configuration and reconciliation tests. Production payment access is a verified prerequisite.

Acceptance and measurement

Reconcile source receipts, ERP entries and exceptions by amount and identifier. Test partial payment, overpayment and a later reversal under the finance policy.

Questions before starting

Which prerequisites must be verified?

ERPNext version and accounting permissions; Approved payment source; Invoice references and finance allocation policy.

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.

Privacy policy