A practical receipt-to-account process for cash, bank and wallet payments, with partial payments, unmatched references and device decisions kept separate.
A customer says the qist is paid, but the shop’s register still shows it as due. The first task is to trace and allocate the money. It is not to make a device decision from a screenshot. This guide describes an operating process for Pakistan mobile installment businesses; confirm how your chosen software supports each step.
Separate five states
Payment initiated is an attempted payment. Payment received is a receipt confirmed by the receiving business. Payment reconciled is a receipt allocated to the correct agreement. Account status updated means the reconciled balance and unresolved issues are reflected in the account record. An authorized device action is a separate decision by the responsible account owner. Staff should be able to explain which state applies without using one ambiguous “paid” label.
Keep the evidence appropriate to the channel
| Channel | Receiving check | Allocation check |
|---|---|---|
| Cash | Numbered receipt and responsible staff member | Customer and agreement reference on the receipt |
| Bank transfer | Entry in the receiving account record | Reference, amount and intended installment |
| Mobile wallet | Receiving transaction record | Correct customer agreement, including a third-party payer |
| Raast merchant payment | Merchant receiving confirmation | Agreement allocation independent of payment method |
SBP’s Raast P2M programme provides merchant-payment context in Pakistan. It does not establish that a merchant uses Raast, that RecTym processes those payments, or that the device-management system posts them automatically. Treat any proposed connector as a separate implementation question.
Primary source for the merchant-payment context, not evidence of a RecTym integration.SBP: Raast person-to-merchant paymentsarrow_forwardWork through a partial payment
Illustration only: one agreement has PKR 7,500 due and the customer transfers PKR 5,000. Once receipt is confirmed and the full PKR 5,000 is allocated to that installment, PKR 2,500 remains against it. Do not mark the whole installment paid or record the same receipt a second time when the remaining amount arrives. These are example ledger amounts, not financing terms.
If the same customer has two phones, ask which agreement the money covers. If a relative sent the transfer, record the relationship needed to trace it without copying unnecessary personal data. Keep a shared payment reference when a transfer is split across agreements, with allocations that add up to the received amount.
Give unmatched receipts an owner
An unmatched payment should remain visible as an exception. Record the reference, amount, receiving time, likely agreement and person investigating. Ask the customer only for the evidence needed to resolve the mismatch. Avoid asking them to pay again simply because the first receipt has not yet been allocated.
For a wrong allocation, preserve the original entry and a traceable correction. If the receiving record later changes or a payment is reversed, follow the business’s review process and communicate the revised account position. Do not silently edit a balance that another shift has already discussed with the customer.
Close the daily reconciliation
Compare received amounts, allocated amounts and unallocated receipts. Hand unresolved items to a named colleague with the next action. Before reminders or device instructions, check whether a reported overdue account has an open receiving or allocation query. Record approval and device-state confirmation separately from the financial record.
Use this routine alongside counter records, staff handovers and account completion.Pakistan retailer workflowarrow_forwardFor centrally received payments, agree how a verified account decision reaches the retail partner.Lender and retailer responsibilitiesarrow_forward
