Wire transfers on ScotiaConnect cover three main surfaces: domestic Canadian-dollar wires routed over Lynx, US-dollar wires routed over Fedwire through a correspondent bank, and cross-border instructions sent over SWIFT in MT103 or ISO 20022 equivalents. This page collects the value-date rules, cut-off times, beneficiary-field requirements, charge-code choices and recall-process notes that treasury teams reach for in the first weeks on the ScotiaConnect portal.
Same-day release on a ScotiaConnect wire depends on three clocks running in sequence: internal approval, portal cut-off, and the rail operator's own closing window. Miss any one and the wire books value for the next operating day.
Value date on a ScotiaConnect wire is the day funds are expected to settle at the beneficiary bank. For a domestic Lynx wire, value is same-day when the approved instruction reaches the ScotiaConnect queue before the published client cut-off, typically 17:30 ET. For a Fedwire USD wire the client cut-off is tighter, usually 16:30 ET, because Fedwire closes earlier and the correspondent path adds a handoff. SWIFT wires settle at the beneficiary bank on their local value date, which can run one to three business days behind the sending date depending on currency and correspondent chain.
Cut-off discipline is the single biggest driver of wire reliability. A batch that clears internal approval at 17:28 ET will make Lynx. A batch approved at 17:33 ET will not. ScotiaConnect surfaces the countdown on every in-flight wire so the approver can see how much time is left before the queue rolls to next-day. For treasury calendars, the Bank of Canada publishes the Lynx operating schedule, and the Bank of Canada site is the authoritative reference for holiday closures that affect same-day release.
Two practical notes apply inside ScotiaConnect. The portal's internal approval clock runs independently from the rail clock, so a four-eyes policy that requires a second approver in another office adds real minutes to every wire. Clients with tight cut-off behaviour should review the access guide to confirm that approver coverage is available during the last hour of the release window. See also the foreign exchange page for FX-linked wires where the currency leg has its own cut-off.
The beneficiary data block on a ScotiaConnect wire form is strict. Name must match the account holder on record at the beneficiary bank. Address is required for cross-border wires because sanctions screening uses the full line. Account number format depends on destination: IBAN for SEPA and most European destinations, BBAN or local clearing for North America and APAC, and free-format account for some exotic currencies. The portal validates basic structure at entry, which prevents a meaningful share of downstream rejections.
Charge-code choice is a business decision, not a technical one. OUR is the default for vendor payments where the contract specifies the gross amount must arrive at the supplier. SHA is common for inter-company transfers where both sides are comfortable absorbing their own charges. BEN is rarer and usually appears on reimbursement flows. Treasury should confirm the contract language before release, because a wrong charge code is not grounds for an automatic rework.
Cross-border screening touches anti-money-laundering rules set by Canadian regulators. The FINTRAC regime requires electronic funds transfer reporting on cross-border flows at or above published thresholds, and the ScotiaConnect portal captures the data elements needed for those reports directly on the wire form. See the international payments page for correspondent banking details and the security standards page for dual-control enforcement.
A ScotiaConnect wire can be recalled or amended, but success depends on how far the instruction has travelled. Before rail transmission, ScotiaConnect holds the wire in queue and allows clean cancellation. After transmission, recall is a request to the beneficiary bank, not a rollback.
Amendment covers small changes to a wire that has not yet cleared approval. Typical amendments are corrections to the reference field, a revised remittance note, or a fix to the beneficiary address block. Once the wire clears final approval and is released to Lynx, Fedwire or SWIFT, the portal no longer exposes an amend option, because the instruction has left ScotiaConnect.
Recall is a bank-to-bank process. When the originator requests recall inside ScotiaConnect, the operations desk sends a MT192 or equivalent camt.056 to the beneficiary bank asking for return of funds. The beneficiary bank contacts its customer and, subject to regulations and customer consent, returns the funds through the same rail. Recall success rates are highest in the first few hours after transmission and drop sharply once the beneficiary has booked and spent the credit.
Rejection handling on ScotiaConnect is surfaced as queue items with a short reason code and a link to the full error. The most common patterns are beneficiary-name mismatch, missing intermediary bank for USD wires outside the correspondent network, and sanctions holds requiring manual review. Rejected wires remain visible in the audit trail and can be cloned into a corrected draft without re-keying every field.
| Rail | Client cut-off (ET) | Typical settlement | Same-day possible? |
|---|---|---|---|
| Lynx (CA domestic) | 17:30 | Same business day | Yes, before cut-off |
| Fedwire (US domestic) | 16:30 | Same business day | Yes, before cut-off |
| SWIFT MT103 (cross-border) | 15:00 | 1-3 business days | Destination-dependent |
| RTR (Real-Time Rail, CA) | 24/7 window | Seconds | Yes |
| SEPA Credit Transfer (EUR) | 11:00 | Next business day | No |
| CHIPS (US high-value) | 16:15 | Same business day | Yes, before cut-off |
ScotiaConnect publishes a client cut-off of 17:30 ET for same-day Lynx wires, with internal approvals required before that clock. Items released into the approval queue after cut-off are held and transmitted on the next Lynx operating day.
Treasury teams with tight release windows should verify approver coverage in the last hour of the day and keep at least one backup approver configured in ScotiaConnect to avoid single-point-of-failure delays.
OUR means the sender pays all correspondent charges, so the beneficiary receives the full amount. SHA splits charges between sender and beneficiary. BEN means the beneficiary absorbs the correspondent deductions.
ScotiaConnect exposes the choice directly on the international wire form, and the selection flows into the outbound MT103 field 71A. Contract language normally dictates the choice, so confirm with payables before release.
A recall request can be placed inside ScotiaConnect, but the beneficiary bank must agree to return funds. Lynx and Fedwire are credit-push rails, so reversal is not automatic.
Recalls placed within hours of release, and before the beneficiary has booked the credit, have a meaningfully higher return rate than those placed a day or more later.
The top rejection causes are mismatched beneficiary name and account, missing intermediary bank for USD wires booked through correspondent chains, truncated address fields that fail sanctions screening, and duplicate references that collide with a prior open instruction.
Cloning the rejected wire into a corrected draft preserves the audit trail and avoids re-keying every field.
ScotiaConnect provides RTR access inside the domestic wire surface as the Real-Time Rail rolls out. Limits and eligibility vary by entity profile.
Treasury teams should confirm their per-transaction ceiling with the commercial service desk before migrating high-value flows away from Lynx.
“We moved all our USD supplier wires to ScotiaConnect Fedwire after two years of bouncing between a correspondent portal and a spreadsheet. Same-day release before the 16:30 cut-off is now routine, and the audit trail saved us during a year-end review.”
— Nikolai P. ChernyakovDirector of Treasury, Kincardine Tooling Co.