What Is Beneficiary and Bank Account Verification?

Account verification answers a simple but critical question before money moves: does this bank account exist, and does it belong to the person or business I think it does? In South Africa this is done through Account Verification Services — commonly referred to as AVS, with AVS-R being the real-time version — which query the account-holding bank and return a set of yes/no results in near real time.

Verification matters because banks generally do not check that a beneficiary name matches the account number when a payment is made. If you pay the wrong account — through a typo or a fraudster's swapped banking details — the money goes where the number points, and instant payments cannot be recalled.

What does an AVS check confirm?

An AVS request submits the account details you hold, together with the customer's identity information, to the account-holding bank. The response typically confirms whether:

• The account number exists at the bank and branch specified.
• The account is open, and how long it has been open.
• The account accepts debits.
• The account accepts credits.
• The ID number or company registration number matches the account holder.
• The initials and surname, or business name, match the account holder.
• The cellphone number or email on record matches, where supported.

The result is a series of match/no-match flags, not the account holder's actual details — verification confirms what you were given without exposing anyone's banking information.

What is the difference between AVS and CDV?

These two checks are often confused:

• CDV (check digit verification) is a mathematical test that an account number is validly formatted for a given branch code. It runs offline and instantly, but it cannot tell you whether the account actually exists or who owns it. See account validation and CDV.
• AVS queries the actual bank and confirms the account's existence, status and ownership in near real time.

CDV is a cheap first filter; AVS is the real assurance. Sensible systems run CDV at capture and AVS before the first payment or debit.

When should you verify an account?

Verification is worth the small cost and delay whenever the risk of paying or debiting the wrong account is material:

• Before payouts: verify supplier, employee and customer withdrawal accounts before the first payment — see payouts and bulk payments.
• Before debit orders: verify that the account exists, accepts debits and belongs to the mandate signer before the first collection — this reduces unpaids and disputes.
• When details change: treat any request to change banking details as high-risk and re-verify. Invoice redirection fraud relies on businesses skipping this step.
• During onboarding: confirming that an account belongs to the customer supports FICA and fraud controls.

What are the limits of account verification?

AVS is powerful but not a complete defence:

• A match confirms the account belongs to the named person — it does not confirm that person is trustworthy or that the invoice is genuine.
• Results reflect the account's status at the time of the check; accounts can close afterwards.
• Coverage and response times vary by bank, and some account types cannot be fully verified.

Pair verification with process controls: independent confirmation of banking-detail changes, dual authorisation on payouts, and healthy suspicion of urgency. And remember that verification protects the sending side — receiving businesses still need cleared funds, not a proof of payment document, before releasing goods.

Tips

• Verify every new beneficiary before the first payment, not after.
• Re-verify whenever banking details change, and confirm the change with the beneficiary on a known contact number.
• Log verification results as part of your audit trail.
• Combine CDV at capture with AVS before payment for the best cost/assurance balance.

Back to the Bank Transfers, Payouts and PayShap hub.