Proof of payment in South Africa is one of those documents that every business deals with daily but rarely thinks about until something goes wrong. A supplier holds your stock because they haven't seen a POP. A landlord disputes your rent payment. A university blocks registration because the fees office can't match your transfer.
This guide covers what proof of payment actually is, how to get one from each major SA bank, what a valid POP must contain, and why businesses that process payments at scale are moving away from POPs entirely.
What is proof of payment?
Proof of payment (POP) is a document or screenshot confirming that a payment was initiated or completed. In South Africa, it is almost always a PDF or screenshot generated from internet banking or a mobile banking app after an EFT (electronic funds transfer) has been submitted.
The key word is initiated. A proof of payment confirms that you told your bank to send money. It does not, on its own, confirm that the money arrived in the recipient's account. This distinction matters more than most people realise — we will come back to it.
A POP typically takes one of three forms:
- A PDF downloaded from internet banking — the most reliable form. Generated by the bank, usually includes a transaction reference and a digital verification mark.
- A screenshot from a banking app — common for quick WhatsApp or email confirmations, but easy to edit and impossible to verify independently.
- A printed slip from an ATM or branch — less common now, but still used for cash deposits and over-the-counter payments.
When you need proof of payment in South Africa
POPs are requested constantly in South African business. The most common situations:
Supplier payments — a supplier dispatches goods only after receiving a POP, especially for first-time orders or large amounts. This is standard practice in SA wholesale and manufacturing.
Rent payments — landlords and managing agents request monthly POPs, particularly where the tenant pays via EFT rather than debit order.
University and school fees — institutions require proof of payment before registration or to release results. Late-semester payments almost always require a POP and a cover email.
SARS payments — when paying a tax liability via EFT (rather than eFiling's built-in payment), SARS may request a POP as part of a dispute or audit.
Vehicle purchases — dealers require a POP before releasing a vehicle, especially for private sales or cash deals.
Visa and immigration applications — some visa categories require proof that application fees were paid or that the applicant has sufficient funds moving through their account. A POP supplements the stamped bank statement that most embassies require.
Settling invoices — any B2B transaction where the buyer needs to prove payment was made before the seller's bank statement reflects the credit.
How to get proof of payment from each major bank
Every major South African bank lets you generate a proof of payment digitally. The exact steps differ, but the pattern is the same: find the completed transaction, and download or share the confirmation.
| Bank | App route | Internet banking route |
|---|---|---|
| FNB | FNB App → Accounts → select account → find transaction → Share/Download confirmation | FNB Online → Accounts → Transaction history → click transaction → Download PDF |
| Standard Bank | Standard Bank App → Transact → History → select transaction → Share | Standard Bank Online → Transaction history → select transaction → Print/Download |
| ABSA | Absa App → Accounts → select transaction → Proof of payment | Absa Online → Payments → Payment history → select transaction → Download |
| Nedbank | Money App → Accounts → Transaction history → select transaction → Share receipt | Nedbank Online → Payments → Transaction history → Download receipt |
| Capitec | Capitec App → Activity → select transaction → Share transaction details | Capitec internet banking → Statements & transactions → select transaction → Download |
A few practical notes:
- Timing matters. If you try to download a POP immediately after making the payment, the transaction may still show as "pending" or "processing". Some recipients reject pending POPs — wait for the status to change to "completed" if possible.
- Scheduled payments. If the EFT was scheduled for a future date, the POP will reflect the scheduled date, not the date you set it up. The payment has not actually left your account yet.
- Business accounts. The same process works, but only users with the right profile permissions can view transaction history and generate POPs.
- Older transactions. Banks typically show 90 days of transaction history in-app. For older payments, you may need to download a full statement and locate the line item — or request the POP through the bank's call centre.
What a valid proof of payment must include
Not every document labelled "proof of payment" is actually useful. A valid POP should contain the following fields, and recipients are within their rights to reject one that is missing key details.
| Field | Why it matters |
|---|---|
| Date and time | Confirms when the payment was made |
| Amount | Must match the invoice or expected payment |
| Beneficiary name | The person or company the payment was sent to |
| Beneficiary account number | Confirms the payment went to the right account — see bank details in South Africa for what this includes |
| Beneficiary bank and branch code | Identifies which bank received the payment |
| Your (payer) name or account | Identifies who made the payment |
| Payment reference | The reference you entered — this is how the recipient matches the payment to an invoice |
| Transaction status | "Completed" or "Successful" — not "Pending" or "Scheduled" |
| Bank stamp or digital verification | An embedded digital signature, QR code, or verification URL that confirms the document was generated by the bank |
The last point is critical. A PDF downloaded directly from the bank's system will have embedded verification — a QR code, a verification URL, or a digital signature. A screenshot or re-typed document has none of these. If you are receiving a POP from someone else, the presence or absence of verification features is the fastest way to judge whether it is genuine.
Proof of payment vs proof of receipt
This is the most misunderstood aspect of POPs in South Africa, and it causes real problems.
Proof of payment proves you sent the money. It does not prove the money arrived.
When you make an EFT, your bank debits your account and queues the payment for processing. The POP confirms that your bank accepted the instruction. But the funds still need to clear through the national payment system and be credited to the beneficiary's account. This typically takes 1-2 business days for standard EFTs, though same-day clearing is increasingly common.
If something goes wrong — a wrong account number, a closed account, a bank system issue — the payment can bounce back to you. Your POP still shows "completed" because your bank did complete its part of the process.
Proof of receipt is the opposite: it proves the money landed. The only reliable proof of receipt is the beneficiary's own bank statement showing the credit. The sender cannot produce this document — only the recipient can.
This distinction matters most in disputes. If a supplier says "I didn't receive your payment" and you send a POP, you have proved you initiated the transfer. But if the payment bounced or went to the wrong account, the POP is not evidence that the supplier was paid. You would need to contact your bank to trace the payment and confirm whether it was successfully credited.
The problem with proof of payment at scale
For an individual paying rent or settling an invoice, a POP is a minor admin task — download, attach, send. The system works well enough.
For a business receiving dozens or hundreds of payments daily, POPs become an operational bottleneck.
Consider a wholesaler receiving 50 payments a day from different customers. Each customer pays via EFT and sends a POP — some via email, some via WhatsApp, some by uploading to a portal. The accounts team must then:
- Open each POP — which arrives in different formats (PDF, screenshot, photo of a screen, forwarded banking notification).
- Extract the details — amount, reference, date.
- Match it to an invoice — using the payment reference, which customers frequently enter incorrectly or leave blank.
- Verify it looks legitimate — is it from a real bank? Is the amount right? Does the date make sense? Is the status "completed" or just "pending"?
- Record the match — update the accounting system to mark the invoice as paid.
This is bank reconciliation done manually, one POP at a time. It is slow, error-prone, and does not scale.
The common failure modes:
- Screenshots instead of PDFs — no verification, easy to edit, sometimes cropped so key fields are missing.
- Wrong reference — the customer typed "INV-2024-089" instead of "INV-2026-089" and now the POP cannot be matched to any open invoice.
- Pending status — the customer sent the POP immediately after initiating the payment. It shows "pending". The payment might still fail.
- Duplicate POPs — the customer sends the same POP twice, or sends it to two different people in your organisation. Without a system, it gets processed twice.
- Delayed POPs — the customer paid on Monday but only sends the POP on Thursday. In the meantime, the account shows overdue.
When your reconciliation process depends on someone else sending you a document, you are always waiting. And you are always trusting that the document is genuine, complete, and accurate.
Automating payment confirmation
There is a fundamentally different approach: instead of asking every customer to send you proof that they paid, monitor your own bank account for incoming credits.
If you can see your own transaction feed in real time — or on a scheduled basis — you already know who paid you and when. You do not need to wait for a WhatsApp message. You do not need to open a blurry screenshot. You do not need to trust that a forwarded PDF is genuine.
The matching works the other way around: you see a credit of R12,500 with reference "INV-2026-089" land in your account. You match it to the open invoice. Done. The source of truth is your own bank statement, not a document sent by the payer.
This is what BankLink transaction feeds enable. You link your business bank account once, set up a scheduled sync — a Pulse, in BankLink terminology — and transactions flow in automatically. Each incoming credit includes the amount, date, and reference, which is everything you need to verify the payment and match it to your records.
The benefits for businesses processing payments at volume:
- No more chasing POPs — you see the payment as soon as it clears, without waiting for the sender.
- No forgery risk — the data comes from your own bank account, not from a document someone else produced.
- Automated matching — payment references can be matched programmatically against open invoices.
- Faster reconciliation — what took hours of manual POP processing can happen automatically. See how to automate bank statement collection for the full workflow.
- Audit trail — every transaction is stored with its original bank data, not as a screenshot in someone's inbox.
This does not eliminate proof of payment entirely. Your customers may still need to send POPs for their own records, and there will always be ad hoc situations where a POP is the quickest way to confirm a single payment. But as a core reconciliation process, monitoring your own account is more reliable, faster, and far less dependent on the other party's admin discipline.
When you still need a traditional POP
Automated transaction monitoring handles the "did the money arrive?" question. But there are cases where a traditional proof of payment is still the right document:
- Visa applications — the embassy wants to see your banking activity, including outgoing payments. A POP from your bank is the expected format.
- Tax disputes — SARS may request proof that a specific payment was made from your account. Your bank's PDF is the appropriate evidence.
- Legal proceedings — courts and attorneys expect bank-generated documents, not third-party transaction feeds.
- Once-off payments — paying a deposit on a vehicle, settling a once-off invoice, or making a large personal transfer. The overhead of setting up automated monitoring is not justified for a single payment.
For these, the process described earlier — download the PDF from your bank, verify it includes all required fields, send it — remains the correct approach.
Summary
Proof of payment is a simple concept that creates disproportionate admin overhead at scale. For individual payments, downloading a POP from your banking app takes thirty seconds. For businesses processing hundreds of incoming payments, collecting and matching POPs manually is a reconciliation bottleneck that can be eliminated entirely by monitoring your own bank account for incoming credits.
The shift is straightforward: instead of asking "did you pay me?", you check "did the money arrive?" — and you check it from your own data, on your own schedule.