What an international payment actually is — and is not
An international money transfer (IMT) is an instruction from your Australian account to a bank account in another country, in either Australian dollars or the destination currency. Unlike a domestic transfer, it does not travel through a single national system. It moves through a relay: your bank sends a secure message through the SWIFT network to the beneficiary's bank — sometimes directly, sometimes through one or more intermediary ("correspondent") banks that hold accounts with each other along the route. Each handoff is a place where processing happens, where compliance checks run, and, on some routes, where a fee can be deducted. That relay structure explains nearly everything that surprises first-time senders: why delivery is measured in business days rather than minutes, why the amount that lands can differ from the amount you pictured, and why a tiny error in the beneficiary details can strand a payment in a queue on the other side of the world.
One vocabulary point prevents a common misunderstanding: SWIFT is a messaging network, not a money pipe. When people say a payment "went by SWIFT", they mean the payment instructions travelled over SWIFT between the banks; the funds themselves settle through accounts the banks maintain with one another. This is also why "the payment has been sent" and "the payment has arrived" are separated by the relays' working hours, time zones and holidays in two or more countries. A payment to London authorised late on a Sydney Friday can legitimately arrive the following week without anything being wrong — it has spent the weekend waiting for Monday in two hemispheres. Plan supplier payments with that geography in mind, and read our general payments guide first if the create-and-authorise workflow itself is new to you.
SWIFT/BIC, IBAN and friends: the addresses of overseas money
Domestic payments need a BSB and account number. International payments need the destination country's equivalent addressing, and it comes in two main pieces. The SWIFT code — also called a BIC (the two names refer to the same identifier) addresses the bank and branch: eight characters identify the bank and country, and three optional extra characters narrow it to a branch. It is the overseas equivalent of a BSB, at global scale. The account identifier addresses the person's account at that bank. In much of Europe, the Middle East and beyond, that identifier is an IBAN — a long structured string that bundles the country, bank and account number together with built-in check digits, which is why a single wrong character usually makes an IBAN invalid rather than merely incorrect: the mathematics catches it. Other major destinations use their own formats — the United States uses a routing number (often called an ABA or Fedwire number) plus an account number; the United Kingdom uses a sort code plus account number, or an IBAN; New Zealand uses its own account format. The practical lesson is not to memorise the world's banking formats. It is to ask the beneficiary for their details in the exact format their bank gives for receiving international payments — every bank on earth produces this for its customers, often labelled "international payment details" or "wire instructions" — and to use those details verbatim.
Two smaller fields cause outsized trouble. The beneficiary name should be the full legal name on the overseas account — the account holder's name as their bank knows it — not a trading name, abbreviation or your contact's first name. Mismatches between the name you send and the name on the account are a leading cause of payments being held for review or returned. And the payment reference or remittance information — the invoice number, order number or account reference — is what lets the beneficiary's accounts team match your money to your debt. Omit it and your payment may arrive perfectly while your account is still chased as unpaid, because nobody at the other end can tell whose it was.
Exchange rates and fees: where the difference between sent and received goes
Two numbers govern what your beneficiary actually receives: the exchange rate applied and the fees taken along the way. Understanding both, before you authorise, removes nearly all unpleasant surprises in international payments.
The exchange rate you are offered is not the "rate" quoted in the news. The news rate is the wholesale, interbank rate at which banks trade with each other in enormous volumes. Your rate is a retail rate that includes a margin for the bank. The margin varies by currency — major pairs like AUD/USD are usually tighter than exotic ones — and by amount. The honest comparison is never "their rate versus Google's rate"; it is the total received amount for the total cost, which the platform shows you at confirmation. Read that screen properly: it is the one moment when every number that matters is in front of you at once. The fees come in layers. Your bank charges a sending fee for the transfer. Then, depending on the fee instruction attached to the payment, intermediary and beneficiary bank charges may also arise. Payments typically offer a choice in plain terms: charges borne by you (often labelled OUR), charges shared (SHA), or charges borne by the beneficiary (BEN). If a supplier must receive an exact invoice amount — common with overseas manufacturers — the shared/beneficiary options can leave them short by the amount of the deductions, and the shortfall conversation that follows costs more than the fee difference ever would. For exact-amount obligations, send in the beneficiary's currency, choose the option where you bear the charges, and consider adding a small buffer agreed with the supplier for routes known to deduct along the way.
Which currency should you send? If the invoice is in the supplier's currency, paying in that currency pushes the conversion to your end, where you can see the full AUD cost before authorising. Paying in AUD leaves the conversion to the beneficiary's bank at a rate you cannot see or control, and the supplier may receive less than the invoice after their bank's margin. There are exceptions — some suppliers prefer AUD accounts — but as a default, match the payment currency to the invoice currency and let the confirmation screen show you the true all-in cost.
The beneficiary details checklist: get these from the source, in writing
Nearly every rejected, delayed or misdirected international payment traces back to one of the items below being wrong, missing or transcribed from the wrong document. Collect them from the beneficiary's own bank-issued instructions — not from an email signature, not from an old payment, and (if the details have "changed") never from an unverified email. Then enter them exactly.
- Request the details as a document from the beneficiary's bank channels
Ask for their official international payment instructions — a PDF or letter from their bank, or a screenshot of the details from inside their own banking. A typed email with numbers in it is the weakest form of evidence and the fraudster's favourite format.
- Verify any change of details by voice
If a long-standing supplier announces new bank details, ring them on a number from your existing records — not from the email announcing the change — and read the new details back. This one habit defeats the most expensive scam in Australian business payments.
- Enter, then re-read against the source
Compare the SWIFT/BIC and account string character by character. IBANs reward this care: their check digits mean most entry slips fail loudly at entry rather than silently in transit.
- Choose currency and fee instruction deliberately
Match the invoice currency, and where the beneficiary must receive an exact amount, bear the charges at your end. Confirm the platform's displayed received-amount estimate matches the obligation.
- Authorise before the cut-off, early in the week
International payments have their own cut-offs, and time zones eat days. A payment authorised Monday morning in Sydney starts moving while the destination is waking up; the same payment authorised Friday afternoon may not be looked at overseas until their Monday — your Tuesday. For deadline-critical payments, send two business days earlier than feels necessary.
Why international payments get rejected, held or returned
A returned payment is annoying; an unexplained one is worse. These are the causes that account for the overwhelming majority, in roughly the order they occur.
Detail mismatches. The beneficiary name differs from the account name; the SWIFT/BIC points at the wrong branch or a bank that has merged and retired the code; the IBAN fails its check digits; an account number is missing a leading zero that a spreadsheet ate. Prevention is the checklist above; cure is corrected details from the beneficiary and a fresh payment, because a payment in flight generally cannot be edited. Compliance holds. Every bank in the relay screens payments against sanctions lists and anti-money-laundering rules, and some payments are paused for extra information — the purpose of the payment, the relationship between sender and receiver, supporting invoices. A hold is not an accusation; it is the system working. Respond to requests for information promptly and factually, and keep the supporting documents (invoice, contract) ready for significant payments as a matter of routine. Certain destinations, industries and payment purposes attract more scrutiny than others, and first payments to a new beneficiary are examined harder than the tenth payment on an established route. Destination requirements. Some countries require specific extra fields — a purpose code, a beneficiary address, a tax identifier, a local clearing code — and reject payments that arrive without them. If a payment to a particular country bounces, ask the beneficiary's bank what that country requires; the answer is usually a field you have never been asked for domestically. Account problems at the far end. Closed accounts, frozen accounts, and accounts that cannot accept the currency you sent all produce returns, sometimes weeks later, and usually minus the intermediary fees already incurred along the way. That deduction-on-return is standard practice in the relay system, not a penalty invented for you, and it is the financial reason the verification habits in this guide pay for themselves.
If a payment you sent has not arrived within the timeframe the platform indicated, do not simply resend it — a delayed original plus a duplicate is a much worse afternoon than a single late payment. Ask the bank to trace the original first. A trace follows the payment through the relay using its unique transaction reference, which is recorded with the payment in the platform; have that reference, the amount, the date and the beneficiary details ready when you call, in the same way our payments guide recommends for domestic traces.
A short word on receiving money from overseas
Many businesses meet international payments first as recipients. If customers or clients overseas need to pay you, give them the same quality of instructions you would want: your full legal account name, your bank's SWIFT/BIC, your BSB and account number in the format your bank specifies for international receipts, and a reference that lets you identify the payment. Expect the mirror image of the sending experience: intermediary deductions can arrive between what the sender sent and what lands in your account, conversion happens at the receiving bank's rate if the payment arrives in foreign currency for an AUD account, and arrival times stretch across weekends in two hemispheres. Quoting overseas customers with those mechanics in mind — stating the currency you invoice in, and that bank charges are for the sender's account where your terms allow — prevents the short-payment disputes that otherwise consume the margin on small export orders. When a received amount does not match an invoice, ask the sender for the payment confirmation details from their end before assuming anything; the record usually shows exactly where the difference arose.
One last habit ties the whole topic together: keep a short route diary for your regular overseas relationships. For each supplier or customer, note the details you verified, the currency and fee instruction you settled on, the typical transit time and the deductions you actually observed on the first few payments. International payments feel complicated because every route behaves slightly differently; the diary converts that variation into local knowledge your business owns. New staff inherit it, negotiations with suppliers can reference it, and the next time a payment behaves oddly you will know immediately whether it is odd for this route or merely normal for it — the difference between a problem to escalate and a pattern to relax about.
Cut-offs, time zones and value dates: why Tuesday's payment lands Thursday
International payments run on at least two calendars at once. Your bank applies a daily cut-off for each currency and destination — authorise after it and the payment effectively starts its journey the next Australian business day. The destination then applies its own business days, weekends and public holidays, which rarely align with Australia's: a payment can lose a day to a Sydney holiday, a day to a London holiday and a weekend to the simple fact that the earth is round. Add the date line and the arithmetic surprises everyone once: a payment sent from Australia on Friday may be processed in the United States on their Thursday or Friday, while a payment to New Zealand barely notices a time difference at all. The practical habits follow directly. Build supplier payment terms around value dates — the date the money is expected to be available at the destination — rather than the date you press authorise, and ask key suppliers what their bank typically does with incoming payments from Australia. Send deadline-critical payments at the start of your week, not the end: a Monday-morning authorisation gives the relay two full working days in both hemispheres before any weekend intervenes. And keep a simple per-supplier note after your first successful payment — sent date, landed date, deductions observed. Two or three entries turn that supplier's route from a mystery into a timetable you can promise against.
Purpose of payment and supporting documents: boring fields that prevent holds
Many destinations and payment types ask why the money is moving — goods, services, royalties, loan repayment, capital — sometimes as a structured purpose code, sometimes as free text. Treat the question as part of the payment, not bureaucratic decoration. The banks in the relay use it in their screening, and a vague or mismatched purpose ("services" attached to what is plainly a shipment of goods, with an invoice that says so) is a reliable way to earn a compliance hold and a request for documents while your supplier waits. Keep the supporting set ready for any significant payment: the supplier's invoice, the contract or purchase order behind it, and shipping or delivery documents for goods. Businesses that trade regularly should expect periodic requests for this material even on established routes — beneficiary banks refresh their files, sanctions lists change, thresholds get crossed — and the ones who produce documents in an hour rather than a week are the ones whose payments keep moving. File the set with the payment record each time; when the same questions arrive next quarter, you will answer them from the folder instead of from memory, and your audit trail for the tax office improves as a free side effect.
Frequently asked questions
How long does an international payment take?
It depends on the destination, the currency and whether the route needs correspondent banks. Major-currency payments to well-connected countries commonly land within one to three business days; routes involving intermediaries, compliance reviews or mismatched weekends and holidays can take longer. Authorise early in the Australian business day and early in the week to give the payment the cleanest run.
Are SWIFT and BIC the same thing?
Yes — in practice the terms are used interchangeably for the same bank identifier code. An eight-character code identifies the bank and country; an eleven-character version adds a branch identifier. Use the exact code from the beneficiary's bank-issued instructions.
Why did my supplier receive less than I sent?
Usually because of the fee instruction and the relay: intermediary or beneficiary bank charges were deducted along the way, or the amount was converted at a rate you did not see because you sent in AUD. If the supplier must receive an exact amount, send in their currency, choose the option where you bear the charges, and check the platform's estimated received amount before authorising.
What is an IBAN and does Australia use it?
An IBAN is a structured international account identifier used across Europe and many other regions; it embeds the country, bank and account number plus check digits that catch typing errors. Australia does not use IBANs — Australian accounts are identified by BSB and account number — but you will need a beneficiary's IBAN for payments to IBAN countries, exactly as their bank issues it.
My payment was rejected for a "name mismatch". What does that mean?
The beneficiary name on the payment did not match the name on the destination account closely enough for the receiving bank's checks. Obtain the full legal account name from the beneficiary — as printed on their bank statement or account documentation — and resend with it exactly. Trading names and abbreviations are the usual culprits.
Can I cancel an international payment after authorising it?
Once a payment has been sent into the relay, recall is a request, not a switch: the bank can ask for it back, but return depends on where the payment has reached and the beneficiary bank's cooperation, and fees already incurred are generally not refunded. Before processing begins there may be a window to stop it — which is why errors should be reported the moment they are spotted, with the payment's transaction reference ready.