Contact Us

CorporateConnect International Payments: SWIFT, ISO 20022 and Cross-Border ACH

CorporateConnect moves money across borders over three rails: SWIFT MT103 for legacy customer credit transfers, ISO 20022 MX pacs.008 for the migrated cross-border rail, and cross-border ACH (NACHA IAT) for Canada, Mexico and participating EU corridors. Twenty-six beneficiary currencies are quoted with live FX pricing from the U.S. Bank FX desk; rate locking is available for payments above configurable thresholds.

Operating compliance is first-class, not an afterthought. Every cross-border payment is OFAC-screened at initiation and at release, BIC codes validate against the SWIFT directory, IBANs validate against ISO 13616 checksums and beneficiary whitelisting adds a final layer over dual authorization. For domestic wires, see wire transfers. For batch ACH, see ACH payments. For the FX pricing engine itself, see foreign exchange.

Sign In to Send a Cross-Border Payment Talk to the FX Desk

SWIFT, ISO 20022 and Cross-Border ACH on One Portal

One origination queue covers every cross-border rail. Controls, approval workflow and reporting are identical regardless of the underlying network.

International Payments Overview

  • Countries: 130+ via SWIFT, 3 active corridors via IAT cross-border ACH.
  • Currencies: 26 beneficiary currencies quoted live by U.S. Bank FX.
  • Message formats: SWIFT MT103, ISO 20022 MX pacs.008, NACHA IAT.
  • Compliance: OFAC SDN + sectoral + country screening, BIC/IBAN validation, beneficiary whitelist.
  • FX: live rate lock inside the payment, forward contracts for hedged payables.

Corridor Matrix: Method, Settlement and FX Options

A selection of the most-used commercial corridors with the rail, settlement days and available FX option shown.

CorridorMethodSettlement DaysFX Option
USA → Eurozone (EUR)SWIFT MT103 / pacs.0081Live FX or forward
USA → United Kingdom (GBP)SWIFT MT103 / pacs.0081Live FX or forward
USA → Canada (CAD)SWIFT or IAT cross-border ACH1 (SWIFT) / 2 (IAT)Live FX or rate lock
USA → Mexico (MXN)SWIFT or IAT cross-border ACH1 (SWIFT) / 3 (IAT)Live FX or forward
USA → Japan (JPY)SWIFT MT1031–2Live FX or forward
USA → China (CNY onshore)SWIFT MT103 with SAFE docs2–3Live FX (limits apply)
USA → India (INR)SWIFT MT103 with purpose code1–2Live FX
USA → Australia (AUD)SWIFT MT103 / pacs.0081Live FX or forward
USA → Brazil (BRL)SWIFT MT103 with BCB docs2Live FX
USA → Singapore (SGD)SWIFT MT103 / pacs.0081Live FX or forward

Correspondent Banking, Compliance and FX Execution

Three pillars behind every international payment: the correspondent chain that moves the money, the compliance engine that screens it, and the FX engine that prices it.

Correspondent Banking and Routing

U.S. Bank maintains a correspondent banking network spanning Europe, Asia, Latin America and Africa. For major currency corridors U.S. Bank typically holds a direct nostro with the correspondent, cutting the chain length to two banks (U.S. Bank and beneficiary bank) or three banks (U.S. Bank, correspondent, beneficiary bank). Shorter chains mean faster settlement and lower intermediary deductions.

Routing choice is made inside the FX desk workflow: the system selects the correspondent with the best dealer quote and cleanest sanctions risk for the corridor. You see the quoted all-in FX rate and any correspondent fee disclosed up-front rather than discovered after settlement.

OFAC Screening and Sanctions

Every international payment is screened against the OFAC SDN list, sectoral sanctions and country-based sanctions programs at initiation and again at release. Beneficiary name, address, intermediary banks, beneficiary bank and free-text fields are all screened. Fuzzy matching catches common spelling variants. Matches route to Treasury Operations for manual review; false positives are resolved within one business day on average.

Payments to fully sanctioned jurisdictions (Cuba, Iran, North Korea, Syria, the Russian-annexed regions of Ukraine) are rejected at the origination screen with a specific error. Sectoral sanctions (for example, the Russian energy sector under Directive 4) are enforced by entity and by prohibited activity. The beneficiary whitelisting feature adds a third layer on top of OFAC screening for companies with SOX or audit-committee mandates.

BIC, IBAN and Local Clearing Codes

BIC codes validate against the SWIFT BIC directory in real time. Invalid BICs block the wire at initiation with a specific "not in SWIFT directory" error rather than returning as a delayed failure. IBAN validates against ISO 13616 (checksum, country-specific length). For countries that do not use IBAN (U.S., Canada, Australia, China, Japan) the platform requires the local clearing code: ABA for the U.S., sort code + account for the U.K. when IBAN is not provided, BSB for Australia, transit + institution for Canada.

Purpose-of-payment codes are required for corridors that mandate them: China (SAFE codes), India (RBI purpose codes), Brazil (BCB nature codes). The platform surfaces the required code at the wire creation screen based on corridor rather than forcing the operator to remember which codes apply where.

FX Pricing, Rate Lock and Forwards

FX pricing uses the U.S. Bank FX desk. Live rate quotes populate in the wire creation screen with a 30-second hold window. For larger trades the rate lock extends to 15 minutes or 1 hour on request. Forward contracts and window forwards hedge payable exposure out to 12 months; forward points are disclosed alongside the spot rate.

FX execution uses institutional spreads negotiated against the U.S. Bank treasury book, not the retail markup a regional bank bakes into its branch channel. For companies with recurring FX exposure, the FX desk can build a rolling hedge program directly inside CorporateConnect with custom reporting on realized vs. hedged rate and average all-in cost.

International Footprint

One portal, three rails, every major corridor.

130+SWIFT Countries
26Currencies
3Cross-Border Rails
<1 dayOFAC False-Positive SLA

Cross-Border ACH for Canada, Mexico and EU

IAT is the cheaper alternative to SWIFT for recurring lower-value payments in three well-served corridors.

When to Use IAT vs SWIFT

Cross-border ACH (IAT) fits recurring payments under USD 25,000 to Canada, Mexico and participating EU corridors. Settlement takes 2–4 business days depending on corridor. Use cases: monthly commission payments, cross-border payroll, recurring B2B invoices. For urgent or high-value payments use SWIFT instead — next-day settlement and richer compliance data.

NACHA IAT Requirements

IAT entries require structured OFAC-mandated data fields: originator name and address, beneficiary name and address, originating and receiving depository financial institutions with country codes and identifiers, purpose of payment. CorporateConnect enforces the required fields at batch creation with country-specific validations. See NACHA IAT operating rules for full requirements.

ISO 20022 MX Migration

The Federal Reserve ISO 20022 migration and the SWIFT cross-border migration are shifting cross-border payments from MT to MX (pacs.008). CorporateConnect handles both in parallel with automatic translation for corridors in the migration overlap window. Structured remittance, structured addresses and LEI-enriched party data travel with pacs.008 payments where the full corridor supports them.

Beneficiary Whitelisting

The user management module supports a beneficiary whitelist for international payments. When enabled, only pre-approved beneficiaries can receive wires above configured thresholds. Whitelist edits require dual authorization and carry a cooldown before first live payment. This control is commonly required for companies with heavy OFAC exposure or SOX mandates on segregation of duties in cross-border payments.

International Payments FAQ

Which countries and currencies does CorporateConnect support?
SWIFT payments to more than 130 countries in 26 beneficiary currencies including USD, EUR, GBP, JPY, CAD, MXN, AUD, NZD, CHF, SEK, NOK, DKK, HKD, SGD, CNY, INR, BRL, ZAR, PLN, CZK, HUF, AED, SAR, ILS, THB and PHP. USD payments can settle to any country with a USD correspondent.
Is CorporateConnect adopting ISO 20022 MX?
Yes. The platform participates in the SWIFT cross-border migration to ISO 20022 MX (pacs.008 for customer credit transfer, pacs.004 for returns, camt messages for reporting). Both MT103 and pacs.008 are handled with automatic translation.
How does OFAC screening work on international payments?
Every international payment is screened against OFAC SDN, sectoral sanctions and country-based sanctions at initiation and again at release. Name, address and free-text fields are all screened. Matches route to Treasury Operations; false positives resolve within one business day on average.
How are BIC and IBAN validated?
BIC codes are validated against the SWIFT BIC directory with enrichment of branch details. IBAN is validated against the ISO 13616 checksum and country-specific length rules. Invalid BIC or IBAN data blocks the wire at initiation. For countries that do not use IBAN the platform requires the local clearing code.
What is cross-border ACH and when does it apply?
Cross-border ACH uses the NACHA IAT SEC code to send ACH-style payments to Canada, Mexico and participating EU countries via FedACH corridor bridges. Settlement takes 2–4 business days. IAT is suitable for lower-value recurring B2B and consumer payments; higher-value and time-sensitive payments still route over SWIFT.

Related Services

Wire TransfersDomestic Fedwire and international SWIFT wires. Foreign ExchangeLive FX pricing, rate lock and forward contracts. ACH PaymentsDomestic NACHA origination and IAT cross-border ACH. Vendor PaymentsInternational AP routing across SWIFT and IAT. Transaction ReportingCross-border payment status with correspondent chain. SecurityOFAC screening, beneficiary whitelist and MFA.