You've shipped the order, raised the invoice, and now your overseas customer says the payment is on its way. Your bank asks for beneficiary details, the supplier wants to know why the funds haven't arrived, and the amount received doesn't quite match the invoice. For a South African finance team, cross border payments through SWIFT can feel less like sending money and more like handing a parcel to several couriers without a single consolidated receipt.
That uncertainty matters for exporters, importers, BPO companies, and businesses paying international contractors. The right choice depends on the corridor, currency, urgency, compliance requirements, and the amount the beneficiary must finally receive. Before comparing newer payment rails, it helps to understand what SWIFT does, where the money travels, and which charges appear beyond the headline bank fee.
Why SWIFT Still Powers Most Cross Border Payments
A Cape Town software company may need to pay a United States supplier in USD. A Durban exporter may receive EUR from a European customer. A Johannesburg BPO may pay contractors in several countries. In each case, the finance team wants the same outcome: the correct amount should leave the business, reach the intended account, pass compliance checks, and arrive with enough information for reconciliation.
SWIFT remains important because it connects banks across international corridors and supports payment instructions in many currencies. It isn't the money itself, but it gives participating financial institutions a structured way to communicate payment instructions. That reach makes it especially useful when a regional instant-payment system doesn't connect the South African bank to the beneficiary's bank.
South Africa's role is particularly relevant. The South African Reserve Bank explains that, until 2024, transfers between Common Monetary Area countries, South Africa, Namibia, Lesotho, and Eswatini, were processed on domestic payment systems. These flows were classified as cross-border only from 2024 onward, so older comparisons can understate the region's cross-border activity. The same South African Reserve Bank analysis of payment performance says Southern Africa's share of intra-African payments rose from 40% in 2021 to 55% in 2025, highlighting the region's growing importance in connected payment corridors.
For a seller, international fulfilment is also part of the payment decision. Planning shipping abroad for SA sellers helps clarify delivery obligations, customer locations, and the timing between dispatch and settlement. Those operational details influence whether a payment can wait for a traditional bank process or needs a faster corridor-specific option.
This guide is for finance managers who need more than a definition of a SWIFT code. You'll learn how correspondent banks handle the transfer, why costs vary, what SWIFT gpi changes, and how to decide whether SWIFT, a regional instant rail, or a specialist provider fits the particular payment.
How SWIFT Actually Moves Money Across Borders
The easiest way to understand SWIFT is to separate messaging from settlement. SWIFT sends authenticated financial messages between institutions. The actual balances move through accounts that banks maintain with one another, often through correspondent banking relationships.
Think of a tracked postal network. Your bank writes a secure instruction telling another bank what to do. The postal network carries the instruction, but it doesn't own the parcel or settle the recipient's account. Banks use their account relationships to complete the financial part.
The five parties and actions
The sender's bank initiates the instruction. You submit the beneficiary's name, account or IBAN where applicable, bank identifier, currency, amount, purpose, and supporting information. The bank checks the instruction and creates a message for the receiving institutions.
The SWIFT network relays the message. The network transmits the payment instruction securely. It doesn't debit your account, hold the funds, or credit the beneficiary.
A correspondent bank may provide the currency account. Your South African bank may not hold a direct account with the beneficiary's bank in the required currency. A correspondent can hold the relevant account relationship and pass the settlement value onward.
Additional correspondent banks can participate. Some corridors need more than one intermediary. Each institution may receive, screen, route, or repair the instruction before the beneficiary bank can act.
The beneficiary's bank applies the funds. After receiving the instruction and settlement value, the bank performs its own checks and credits the recipient, subject to local requirements and account details.
Why the chain affects the result
The payment message and the funds don't always travel through identical operational steps. A correspondent may need to investigate an incomplete address, clarify the purpose of payment, or request information before releasing the funds. That creates a delay even when the original instruction was sent promptly.
The terms nostro and vostro describe the same account relationship from different banks' perspectives. A bank's nostro account is an account it holds with another bank. The other bank can describe that same account as a vostro account. You don't need to memorise the terminology, but you should know that these accounts are the infrastructure behind many international settlements.
Practical rule: Treat the SWIFT message as the instruction receipt, not proof that the beneficiary has been paid.
That distinction explains why a payment can show as sent by the South African bank while the recipient still sees nothing. It also explains why a query may involve several institutions, and why a fee can arise after the original transfer instruction has left your bank.
What Determines Cost and Timing in a SWIFT Transfer
The amount that leaves your account and the amount the beneficiary receives can differ because a SWIFT payment has several layers. A useful forecast starts with the full landed-cost stack, not the first fee shown on the bank's payment screen.
The cost stack
| Component | Who charges | Impact on cost or timing |
|---|---|---|
| Outgoing transfer fee | Sending bank | Adds a fixed charge before the payment enters the correspondent chain. |
| Foreign-exchange spread | Bank or payment provider | Changes the conversion rate and therefore the amount exchanged. |
| Correspondent deduction | Intermediary bank | May reduce the value delivered before the beneficiary bank receives the payment. |
| Fee allocation | Sender, beneficiary, or both | OUR, SHA, and BEN determine who is intended to carry the available charges. |
| SWIFT query or amendment | Sending or intermediary bank | Adds an exception cost and can hold the payment while details are checked. |
| Statement or message documentation | Bank | Creates an operational cost for confirmations, statements, and reconciliation records. |
| Compliance review | Banks in the chain | Can pause release while parties, purpose, sanctions, or supporting documents are assessed. |
| Cut-off and time-zone effects | Sending and receiving banks | An instruction submitted after a cut-off may wait for the next processing window. |
| Return or cancellation | Banks handling the transfer | Can create further charges and delay the recovery of funds. |
South African pricing illustrates why the headline fee isn't the whole answer. Capitec lists outgoing international payments at R250 for SHA or BEN and R500 for OUR, with a SWIFT query fee of R138, according to its business foreign-exchange fee schedule. Standard Bank's 2026 business guide lists a R293 cross-border payment fee and R21 per SWIFT MT900/MT910 or MT940/MT942 statement page, showing that documentation and exception handling can sit beside the transfer fee.
OUR, SHA, and BEN in plain language
OUR means the sender elects to bear the payment charges, usually to give the beneficiary a clearer expectation of the amount to receive. It doesn't guarantee that every cost in every corridor will be predictable, because intermediary practices and exceptional handling can still affect the final result.
SHA generally splits charges between the sender and beneficiary. BEN allows charges to be deducted from the payment amount, so the recipient receives less than the invoice value. The important question isn't which label sounds cheapest. Ask which party must receive the full commercial amount and whether the bank can provide an all-in estimate.
Public pricing information also shows outward SWIFT fees ranging from R250 to R550 at major South African banks, with possible query, amendment, cancellation, and foreign-bank deductions. The Access Bank South Africa pricing guide is a useful reminder that unpredictable cost can come from fee allocation, bank investigations, return-of-funds charges, and exchange-rate spreads, not only from the initial transfer charge.
Why timing varies
Timing depends on the number of institutions involved, the currency, the receiving bank's operating schedule, cut-off times, weekends, public holidays, compliance screening, and the quality of the payment data. A complete beneficiary address and correct bank identifier can prevent manual repair. An incomplete purpose description can create the opposite result.
To forecast properly, record the instruction time, the bank's cut-off, the expected currency route, and the person responsible for following up. Finance teams should also ask whether the bank can provide a tracking reference and confirmation of credit, rather than relying on a generic “processed” status.
Common Pain Points for South African Businesses Using SWIFT
SWIFT problems rarely come from one dramatic failure. They usually appear as small uncertainties that become expensive at month-end: an invoice arrives short, a supplier asks for proof of payment, or a transfer remains unconfirmed while staff email the bank.
The first pain point is unpredictability. A finance manager may know when the instruction was submitted but not which intermediary currently holds it. Cut-off times, screening, manual repairs, and different bank operating schedules can all affect arrival.
The second is slow settlement. Every extra bank in the chain creates another hand-off. If one institution asks for clarification, the payment waits while the parties exchange information. This is why a transfer can be technically released by the sender without being available to the beneficiary.
The reconciliation problem
Poor visibility creates a third problem. Once the message enters a multi-bank corridor, the sender may have limited practical information about the next action, the intermediary deduction, or the expected credit time. Without a usable tracking reference, staff often escalate through the bank rather than trace a specific payment event.
Reconciliation headaches follow. The accounting team matches the outgoing bank entry to an invoice, but the supplier's receipt may show a different net amount. The difference can reflect the chosen fee model, correspondent deductions, FX conversion, or an investigation charge. If those fields aren't captured in the payment record, the team spends time explaining variances that the original approval didn't make visible.
The invoice amount, the amount debited, and the amount received are three separate control points.
South Africa's currency position adds context. The South African Reserve Bank paper citing Swift data identifies the rand as one of the most widely used currencies in sub-Saharan African cross-border transactions, accounting for 12.4% of customer-related Swift cross-border payments in the region. The same paper records South African pay-in activity of USD 1,022,468,162 over 12 months, representing 78.16% of the total value in its sample, with 124.96% average year-on-year growth and 56.31% recent growth momentum. These figures come from the specific sample described in the South African Reserve Bank paper on global cross-border payments, not from every South African business.
At scale, even a modest spread or recurring deduction can affect margins. The solution starts with identifying the exact failure: missing data, an unsuitable fee model, no tracking, or a corridor that should use a different rail.
How SWIFT gpi Improves Speed and Transparency
SWIFT gpi improves the experience around a SWIFT payment without replacing the underlying network. The practical change is better information about what happens after the sender submits the instruction.
A UETR, or Unique End-to-end Transaction Reference, gives the payment a tracking identity that can follow it through the chain. Instead of asking only whether the bank “sent” the payment, the finance team can ask where the transaction is, whether it was credited, or whether an institution rejected or returned it.
gpi can also improve confirmation and fee information where the relevant banks support the service. That helps the sender compare the expected amount with the reported deductions and identify exceptions sooner. Pre-validation can reduce avoidable errors by checking payment details before the instruction travels through the corridor.
The limits matter. gpi doesn't remove the foreign-exchange spread, correspondent banking relationships, or every possible charge. It also depends on participation and implementation across the banks involved. A gpi-enabled sending bank can't create end-to-end visibility where another part of the route doesn't provide the necessary status information.
Use gpi as a control improvement, not as a promise that every payment will be instant. Ask your bank three practical questions:
- Tracking: Can the bank provide the UETR for each eligible payment?
- Status: Can the team see intermediary progress and final credit confirmation?
- Charges: Can the bank show reported deductions and explain differences from the instructed amount?
That information can shorten investigations and improve reconciliation, even when the payment still uses traditional correspondent settlement.
Smarter Ways to Reduce Costs and Speed Up Settlement
The best rail isn't the same for every payment. A supplier in a country connected to a regional instant system may not need the same route as a once-off payment to a bank outside those networks.
South African businesses should assess four questions before selecting the rail:
| Decision factor | Use it to ask |
|---|---|
| Corridor | Does a supported route exist between the sender and recipient countries? |
| Currency | Can the rail settle the required currency, or will another conversion be needed? |
| Value and limits | Does the payment fit the provider's permitted value range and operating rules? |
| Urgency | Is same-day or near-real-time settlement necessary, or can the payment follow a bank timetable? |
Regional options already exist for selected Southern African routes. Regional reporting cited in South African payment-industry coverage describes a South Africa to Zambia route with settlement reported at 60 seconds, as well as low-value cross-border coverage across South Africa, Eswatini, Lesotho, and Namibia by late 2024. The South African Reserve Bank's 2026 cross-border regulation release also shows that payment-facilitator rules are being tightened in 2026. Availability, limits, compliance steps, and operating conditions still need to be checked for the specific corridor.
A practical payment policy
- Use SWIFT for reach. It remains the practical option when the beneficiary's bank sits outside a compatible regional network, when the currency isn't supported by the alternative, or when the transaction needs a bank-to-bank route with established correspondent coverage.
- Use regional instant rails for eligible corridors. Check currency, value caps, settlement windows, and whether both institutions participate. Don't assume that geographic proximity means automatic access.
- Consolidate where appropriate. Grouping approved supplier payments can reduce repeated administration, but only where it fits contractual deadlines and doesn't create unnecessary exposure or reconciliation complexity.
- Choose charges deliberately. Use OUR when the beneficiary must receive a defined amount, SHA when the commercial arrangement accepts shared costs, and BEN only when the recipient understands that deductions reduce the payment.
- Compare specialist platforms. Zaro offers South African businesses ZAR and USD business accounts funded by bank transfer, real exchange rates with zero spread, and a workflow advertised without SWIFT fees. Businesses should still complete their own KYB, corridor, currency, and compliance assessment before relying on any provider.
A multi-user approval process also matters. Separate the person who creates a payment from the person who approves it, set permissions by role, and retain the payment reference with the invoice. Those controls reduce operational mistakes regardless of the chosen rail.
Putting It All Together for Predictable Cross Border Payments
Predictability comes from matching the payment to the corridor rather than treating SWIFT as the automatic answer for every international transfer. Start with the beneficiary's country and bank, then confirm the currency, permitted value, operating window, compliance documents, and expected settlement route.
Before approving the next invoice, run this short control list:
- Confirm the beneficiary data. Check the account identifier, bank identifier, legal name, address, and payment purpose.
- Map the route. Ask whether a supported regional instant rail exists and where its limits or operating conditions apply.
- Calculate the landed cost. Include the bank fee, FX rate, fee allocation, possible intermediary deductions, and exception charges.
- Set the receiving expectation. Tell the supplier whether charges are OUR, SHA, or BEN and what evidence you'll provide.
- Capture tracking. Request a UETR or equivalent payment reference and record it against the invoice.
- Review the result. Compare the amount debited, the amount received, and all deductions before closing the reconciliation item.
South African businesses also need to monitor regulatory changes affecting payment facilitators and corridor access. The region is developing faster routes, but those routes don't eliminate the need for corridor-by-corridor checks. SWIFT remains necessary for some destinations and currencies, while other payments may suit a regional rail or a specialist provider with clearer FX and fee handling.
Zaro gives South African businesses ZAR and USD business accounts, real exchange rates with zero spread, and cross-border payment workflows designed to avoid SWIFT fees after KYB onboarding. Review how it could fit your supplier, contractor, or export-receipts process by visiting Zaro.