VisionONE ERP · Finance & control · Kenya
M-Pesa Integration
VisionONE scopes M-Pesa integration around your merchant account, bringing payment references into sales and receivables so collections can be matched and reviewed.
What your team can manage
Bring collections into focus.
Define the route, reference fields and reconciliation rules before going live, so the integration serves finance as well as the customer payment experience.
Safaricom connection
Agree the PayBill, Till or other eligible route and permissions for your merchant account. Identify the account owner, the payment flow customers use and the connection proposed for VisionONE. Confirm which approvals and onboarding steps are required before implementation; access to a merchant account does not establish that every available payment product is included.
Reference capture
Bring transaction IDs, amounts and payer references into the agreed ERP hand-off. Review a representative payment record and identify the information finance needs to trace it. Agree the handling of missing or inconsistent references, and confirm which source record will be used when the payment information and the sales record differ.
Receipt matching
Use the agreed reference details to identify the customer or invoice and flag payments that need review. Include a partial payment, an overpayment and an unclear reference in the demonstration. Confirm the matching criteria and the authorised review process before allowing a receipt to be treated as settlement of an invoice.
Collection review
Compare recorded receipts with payment activity and investigate missing, partial or duplicate entries. Agree the reconciliation period, source statement and person responsible for resolving each difference. Check how a corrected match reaches receivables and the ledger, so finance can explain both the recorded collection and any outstanding exception.
The day-to-day picture
A payment alert is only the beginning.
A confirmation on a phone does not tell finance which invoice was settled. A well-scoped M-Pesa connection gives each receipt a traceable reference in VisionONE, while unmatched activity stays visible for follow-up.
A practical workflow
From customer payment to reconciliation.
Your chosen Safaricom product determines how payment information reaches VisionONE. Set the posting and review rules around your real PayBill, Till, order and invoice process. Use the data migration checklist to plan opening customer balances and references. Decide how collections received around cutover will be checked against the old and new records, with a named owner for reconciliation.
- 01Confirm the authorised PayBill, Till or other route
- 02Connect and test the agreed payment data
- 03Match the reference to an invoice or customer
- 04Review exceptions and reconcile collections
Know which payments are accounted for.
With the right route and rules in place, finance can review matched collections and the exceptions that need investigation. Agree what evidence will show that a payment has been received, recorded and allocated to the correct account. Include the users who resolve customer queries in acceptance testing, and document the route for investigating a delayed or uncertain payment status.
Before you choose
Questions about M-Pesa integration.
Answers to the questions teams bring to a first conversation.
Can VisionONE work with our PayBill or Till?
M-Pesa is among VisionONE’s integration options. The supported flow depends on your Safaricom product, merchant permissions and the connection agreed with VisionONE. Bring the details of your current collection route to the evaluation and confirm the supported account type, reference handling, onboarding responsibilities and work included in the proposal before proceeding.
Does this include STK Push or C2B?
Safaricom offers different Daraja payment products. Confirm whether STK Push, C2B or another flow is included in your particular VisionONE project, together with the required merchant permissions. Ask the demonstration team to distinguish the proposed customer payment experience from the finance receipt and reconciliation steps; support for one flow does not establish support for every flow.
Will payments automatically settle invoices?
The matching rule, reference quality and treatment of partial or unmatched receipts are agreed during implementation. Ask to see your payment-to-invoice process, including an exception that requires review. Confirm who approves a correction and how the remaining balance is represented. A phone confirmation alone should not be treated as evidence that the correct invoice has been settled.
A more useful demo
See your payment-to-invoice workflow.
Bring an anonymised payment reference, customer invoice and reconciliation example. Use the ERP selection checklist to prepare questions about integration scope, exception handling, responsibilities and support. The walkthrough should show the proposed handoffs and identify anything that needs separate confirmation before your organisation accepts the connection.
Talk to VisionONE