International payments on ScotiaConnect cover cross-border flows routed over SWIFT, either in the legacy MT103 format or in the ISO 20022 pacs.008 successor. The ScotiaConnect cross-border surface captures the full beneficiary block, the correspondent-bank path, the charge-code selection, the FX conversion option and the sanctions-screening outcome. This reference collects the field requirements, regulatory touchpoints and corridor-specific notes commercial clients lean on when moving money internationally through the portal.
ScotiaConnect international payments sit inside a live standards transition. MT103 is the familiar legacy format; ISO 20022 pacs.008 is the richer structured successor. During the coexistence window, both flow out of the portal, and both are accepted by correspondent banks that have completed their migration.
MT103 has been the single-customer-credit-transfer workhorse of SWIFT for decades. It is a compact, tag-delimited format with defined fields for ordering customer, beneficiary, amount, value date, charges and remittance. ISO 20022 pacs.008 rebuilds the same content as structured XML, with much more granular party data, structured remittance and proper support for purpose-of-payment codes. The practical benefit to treasury is that pacs.008 flows carry fewer truncation errors and allow richer downstream reconciliation.
Inside ScotiaConnect, the migration is largely invisible to the payment originator. The portal captures the same business data on both formats and serialises the outbound message in whichever format the beneficiary correspondent accepts. Over the coexistence window, more and more corridors move to pacs.008 native, with MT103 retained as a fallback. Primary guidance on Canadian payment infrastructure is published by the Bank of Canada, which oversees the domestic rails that connect into the SWIFT ecosystem.
Correspondent banking is the other piece of the puzzle. ScotiaConnect routes most international payments through a small network of nostro banks, and the correspondent choice can affect settlement time, fee profile and sanctions-screening behaviour. For USD wires to a US beneficiary that is not a direct SWIFT member, the path typically runs through a US correspondent onto Fedwire, which the wire transfers page covers in detail.
Account identifier format matters. Europe and most MENA countries expect an IBAN, which is length-validated and checksum-validated at entry. UK beneficiaries use IBAN that encodes the sort code and account number. APAC, LATAM and North American beneficiaries use a local account number format combined with a routing identifier. The ScotiaConnect form adjusts its validation rules based on destination country, so a field that looks short or wrong-format will fail at entry rather than at the correspondent.
BIC is the ISO 9362 identifier for the receiving bank. It is an 8- or 11-character code and resolves to a specific branch or head office. Where the BIC does not match the account IBAN country, ScotiaConnect prompts the originator to confirm the routing before release. Intermediary banks appear when the originating bank has no direct correspondent relationship with the receiving bank; the intermediary carries the payment through one additional hop before it lands at the beneficiary.
Charge-code selection drives who absorbs correspondent fees. OUR is the default for vendor payments where the contract specifies a gross amount. SHA splits the charges and is common on inter-company flows. BEN means the beneficiary absorbs every deduction. Cross-border AML reporting is handled under the FINTRAC regime, which requires electronic funds transfer reporting at the published thresholds. See also the foreign exchange reference for FX rate mechanics at payment versus settlement.
Sanctions screening is mandatory on every outbound international payment on ScotiaConnect. A clean screen releases the payment to its correspondent path; a hit routes the item to compliance review before release is possible.
Screening runs against consolidated Canadian, US and international sanctions lists, supplemented by internal watchlists. A screening hit is not the same as a true sanctions violation. Name overlaps are common, and analysts on the compliance desk clear false positives with documented evidence before releasing the payment. True positives are rejected, logged and reported to the relevant authority. The Office of the Superintendent of Financial Institutions sets the prudential standards that frame how ScotiaConnect's parent institution operationalises these controls.
FX conversion choice sits next to sanctions as a practical decision the originator makes at release. Convert at payment uses a rate quoted when the payment is approved, producing a known debit in the source currency. Convert at settlement lets the correspondent settle the credit leg in destination currency and returns the source-currency debit once the final exchange is known. Treasury teams managing margin on high-value flows normally prefer convert-at-payment because it eliminates settlement-date rate risk.
Operational note: a payment held in sanctions review does not consume its cut-off window. ScotiaConnect preserves the original release timestamp, and if the compliance review clears inside the rail cut-off, the payment still makes same-day value. Reviews that take longer than the cut-off push the payment to the next value date, which the originator sees as a status change on the payment queue.
| Destination region | Typical currency | SWIFT path | Approx. transit days |
|---|---|---|---|
| European Union (EUR) | EUR | Direct or one correspondent | 1-2 business days |
| United Kingdom (GBP) | GBP | Direct to UK bank | 1-2 business days |
| Asia Pacific (major) | USD or local currency | USD correspondent then local | 1-3 business days |
| Latin America | USD or local currency | USD correspondent then local | 2-3 business days |
| MENA | USD or local currency | USD correspondent then local | 2-4 business days |
| United States (USD) | USD | Fedwire via correspondent | Same day if before cut-off |
MT103 is the legacy SWIFT single-customer-credit-transfer format. ISO 20022 pacs.008 is the structured XML replacement that carries richer beneficiary, originator and remittance data.
ScotiaConnect supports both during the coexistence window, with pacs.008 becoming the default as correspondent banks complete migration.
Mandatory fields include beneficiary name and full address, receiving bank BIC, account identifier in the format required by the destination country, payment currency, payment amount, charge code and purpose of payment.
Intermediary bank details are required on correspondent routes where the originating bank has no direct relationship with the receiving bank.
Every outbound international payment screens against consolidated sanctions lists before release. A hit routes the payment to a compliance review queue where an operations analyst inspects the match.
Screening references Canadian, US and international regimes, with FINTRAC reporting applied to qualifying cross-border flows.
Yes. ScotiaConnect supports both models. Convert at payment locks the FX rate when the payment is released, so the debit amount in the source currency is known.
Convert at settlement uses the rate observed when the correspondent settles the credit leg. Treasury teams usually prefer convert-at-payment for predictability on high-value flows.
Settlement times vary by corridor. USD to Europe typically clears in one to two business days. USD to Latin America and MENA runs two to three business days.
Cross-currency into exotic destinations can take longer where additional correspondents are involved. The ScotiaConnect payment form shows an estimated range before release.
“Our import supplier base sits across five currencies. ScotiaConnect's pacs.008 support plus convert-at-payment has let us lock FX at release and stop chasing settlement-day variances. The sanctions-review queue is visible, which keeps our compliance team calm.”
— Raphaela D. KlausmannHead of Global Treasury, Rushmore Hotel Partners