Good payment records help a small business separate real income from pending transfers, refunds, fees and failed transactions. This guide provides a simple daily process for recording the date, customer, amount, payment channel, reference, sale purpose and confirmation status without storing a customer's PIN or unnecessary identity data. It explains how receipts, bank statements, POS reports and wallet histories support
There is no USSD code for record keeping. The practical task is to capture each payment reference and reconcile daily.
What to dial first
| Need | Code or route | Use it for |
|---|---|---|
| Transfer payments | Bank app/statement/USSD balance where supported | Confirm credit |
| POS payments | Terminal history/receipt | Match sale to settlement |
| Wallet payments | Wallet transaction history | Track app payments |
Step-by-step
- Create a daily payment log.
- Record amount, channel, customer note and reference.
- Mark payment as paid, pending or failed.
- Keep receipts and alerts.
- At closing, compare records with actual balances and settlement.
- List unresolved transactions for follow-up.
Expected result
You should end each day knowing what was paid, what failed and what needs follow-up.
Alternatives
Use notebook, spreadsheet, POS report, bank statement or wallet export.
Common errors and fixes
- Missing reference: use time/amount/customer note.
- Staff forgot entry: reconcile from alerts.
- Settlement mismatch: contact provider with records.
Good records are a business safety tool, not just accounting.
Simple record-keeping answer
A small business should record each payment date, amount, customer name or order note, payment channel, reference number, status and receipt. At the end of the day, compare cash, POS, transfer and wallet records with actual sales.
Why records matter for small shops
Many small businesses receive money through cash, transfer, POS and wallets. Without records, it becomes hard to know who paid, which transaction failed, and whether settlement entered the account.
Good records do not need expensive software. A notebook, spreadsheet or simple daily sheet can help if the business owner is consistent.
What every record should include
Capture the date, time, amount, customer or invoice note, channel, reference, status and staff member if more than one person handles payments. For POS, keep terminal receipts. For transfers, write the sender name and reference if available.
Separate personal money from business money where possible. Mixing them makes it harder to track profit, failed payments and customer disputes.
A daily record routine
This routine is simple enough for a kiosk, salon, POS stand or small retail shop.
- Open a daily sales page or spreadsheet.
- Record each payment as it happens.
- Mark pending or failed payments clearly.
- Keep POS slips and transfer confirmations together.
- At closing, compare cash, bank alerts, wallet history and POS settlement.
- Write unresolved issues for follow-up the next day.
The goal is not perfection. The goal is to make every payment traceable enough to answer customer and bank questions.
Useful payment record fields
| Field | Why it matters | Example | Mistake to avoid |
|---|---|---|---|
| Reference | Helps trace payment | FT123456 | Leaving it blank |
| Channel | Shows where money came from | POS, transfer, wallet | Mixing all payments |
| Status | Tracks unresolved issues | Paid, failed, pending | Marking failed as paid |
| Customer note | Connects payment to sale | Order 24 or Mr Ade | Using vague notes |
Three small-business examples
The following examples explain three small-business examples and show how the guidance applies in different situations.
1. Provision store transfer log
A store owner writes customer name, amount and bank alert time before releasing goods. This reduces fake-alert risk.
2. Salon daily reconciliation
A salon compares cash, POS and transfer totals at closing. Missing settlement is noticed early instead of weeks later.
3. POS agent failed transaction book
A POS agent keeps a separate failed transaction page with customer phone number, amount and receipt reference for follow-up.
Protect customer information
Records should be useful but not careless. Do not expose full account details, card information or customer private data where other customers can see it.
Keep records secure and use official support when disputes happen. Do not ask customers for their banking PIN, OTP or private passwords.
Payment record FAQs
The following examples explain payment record FAQs and show how the guidance applies in different situations.
Can I use a notebook?
Yes. A clear notebook is better than no record. A spreadsheet is useful if you can maintain it.
How long should I keep receipts?
Keep them long enough to resolve disputes, reconcile settlement and support business records.
What if staff forget to record payments?
Create a simple routine and check records daily. Assign responsibility clearly.
Should I record customer phone numbers?
Only when necessary for follow-up, and keep them private.
Small records prevent big arguments
A simple payment log can protect your business from fake alerts, failed settlement confusion and customer disputes.
Download the POS Agent Handbook and adapt the record fields to your business.
Records should match the payment channel
CBN’s electronic-payment channel overview distinguishes POS, transfers, USSD and mobile payments. Keep the channel, provider reference and settlement evidence together so a disputed entry can be traced accurately.
Verification record
- Last fact-check
- July 31, 2026
- Method
- Official provider or regulator sources reviewed where available; live menus control account-specific actions.
- Reviewed by
- Nigeria USSD Codes Editorial Team
Primary official sources:
Article note
Last reviewed: July 31, 2026. This independent guide is informational and does not replace instructions from your bank, telecom provider, regulator, or service provider. Verify sensitive actions through an official channel before sending money or sharing information.