ScotiaConnect Reference is an independent editorial project that documents how the ScotiaConnect commercial banking portal behaves in day-to-day treasury work. Pages here describe the workflows, timing rules, file formats and user roles that commercial clients encounter after implementation. This site is not affiliated with the issuing bank and does not publish binding policy, pricing or contractual terms.
Short version. ScotiaConnect Reference is an independent editorial library about the ScotiaConnect commercial portal, written for treasurers, controllers and payables teams who want plain-language notes on how the portal behaves in practice.
What this ScotiaConnect reference is
Portal scope
ScotiaConnect Reference exists to shorten the time a new commercial user spends guessing how the portal behaves. The site is a plain-language companion to the authenticated ScotiaConnect workspace, not a replacement for it.
ScotiaConnect Reference was built because mid-market and enterprise treasury teams kept asking the same first-six-months questions: which cut-off applies on a bank holiday, what a second-approver flag means on a wire template, where the BAI2 file lands on the sFTP drop, how the token enrolment sequence works when a user replaces a phone. Answers exist inside the ScotiaConnect portal and its onboarding packs, but they are scattered and often buried behind the login. This reference pulls the recurring answers into a single, navigable library.
The editorial model is simple. Each silo (payments, banking, reporting, platform) gets a lead page that explains the surface, followed by a set of topic pages that cover a single workflow in detail. Every topic page carries a short lead-callout for scanning, a data table for reference values, and a short FAQ for the questions that tend to arrive by email after onboarding. The knowledge base lists every page in the library.
ScotiaConnect Reference is written for treasurers, controllers, payables and payroll leads, and the operations analysts who do the daily portal work. If you manage commercial banking relationships on behalf of a client or an internal business unit, the material will feel familiar. For account opening, pricing or legal terms, the contact desk points at the right bank-side contact instead of duplicating answers we cannot authoritatively provide.
Short version. Core payment pages are reviewed every quarter, platform and security pages every six months, and breaking operational changes are patched within seven business days of confirmation.
Pages are not static. ScotiaConnect evolves with rail changes, cut-off adjustments and new reporting formats, and the reference has to stay close to the current behaviour or it loses its value. Each page carries a last-reviewed marker, and each silo has an editorial owner responsible for holding the review cadence. Changes to Lynx settlement, RTR roll-out schedules, CAMT format adoption and NACHA same-day windows are monitored through the primary regulators and the payment-rail operators.
The editorial group deliberately chose a conservative update model. When the Bank of Canada, the central bank, publishes a change to Lynx operating hours, the reference waits for confirmation from at least one independent practitioner before updating ScotiaConnect cut-off guidance. This reduces the chance of documenting a rumoured change that later gets postponed or scoped down.
Readers can also see the freshness of each ScotiaConnect topic at a glance on the knowledge base, which lists the last-reviewed quarter for every page. If a page looks stale, readers are encouraged to email the service desk so the editorial group can either confirm no change or schedule a refresh.
What this reference covers (and does not)
Decision points
ScotiaConnect Reference sticks to workflow-level content. It does not republish binding policy, pricing, contractual terms or any material that belongs inside the authenticated portal.
The line between editorial and binding content is kept strict on purpose. Anything that constitutes the bank's contractual relationship with a commercial client lives in the onboarding packs, the master agreements and the ScotiaConnect portal itself. This reference will describe, in plain language, how a feature behaves, but will never quote or reproduce proprietary policy text.
ScotiaConnect reference scope — covered vs. not covered
Topic area
Covered here
Not covered here
Wires, ACH, international payments
Workflow, timing, file layout, approval model
Exact fee schedule, negotiated FX spreads
Account structures
Entity-to-account relationships, signer model
Legal master agreement wording
Reporting and exports
BAI2, CAMT.053, MT940 fields and scheduling
Confidential account numbers or client file dumps
Security
2FA options, session timeouts, device binding
Internal penetration-test findings
Onboarding
Typical four-to-eight-week cadence, checklist
Individual client-specific contractual terms
Regulatory context
Pointers to OSFI, FINTRAC, CDIC, Bank of Canada
Original regulatory filings or enforcement letters
How the editorial group works
Short version. A small group of former treasury practitioners drafts and reviews each ScotiaConnect topic, with a single editorial lead holding the final publish decision and maintaining the correction queue.
The contributor model is deliberately small. A draft starts as a working document owned by one contributor with practitioner experience in the silo — a former treasurer for payments, a former controller for reporting, a former implementation lead for platform topics. The draft is read by a second contributor before it enters the editorial queue, which is managed by the treasury reference lead.
Corrections are triaged on the same queue. Readers who email the desk with a specific paragraph that needs revision get a response within two business days. Material errors — wrong cut-off time, wrong file-layout field, wrong approval threshold — are patched first and annotated with the correction date. Stylistic changes are batched into the next scheduled review.
The editorial group takes guidance from public regulatory sources where appropriate. Anti-money-laundering and cross-border reporting context, for example, draws on material published by FINTRAC, the Canadian financial-intelligence unit. Prudential context is referenced from OSFI publications. Readers are always directed to the primary regulator for binding interpretations.
Frequently asked questions
Short version. Five questions cover what most readers ask on a first visit: who writes the ScotiaConnect reference, how often it updates, whether it is the official bank site, how to report errors, and how topic suggestions are handled.
Who writes the ScotiaConnect reference?
A small editorial group with prior commercial-banking, treasury and controllership experience writes and reviews each page. The lead editor is named on the treasury reference lead page. Contributors are not current employees of the issuing bank, and the site does not republish proprietary policy content.
Each silo has an editorial owner: payments, banking, reporting and platform. The owner holds the review cadence and the correction queue for their silo, and reports to the lead editor for publish decisions.
How often is the ScotiaConnect reference updated?
Core silo pages covering wires, ACH, foreign exchange and reporting receive a quarterly review. Access, security and platform pages receive a semi-annual review. Breaking changes that affect cut-off times, file layouts or approval thresholds are patched inside seven business days of confirmation by at least one independent practitioner.
The knowledge-base index shows the last-reviewed quarter for every ScotiaConnect page so readers can see freshness at a glance.
Is this the official ScotiaConnect bank website?
No. ScotiaConnect Reference is an independent editorial site. Binding policy, pricing and contractual terms are published by the issuing bank through onboarding documents and the authenticated portal. This reference is informational only and should not be used as the basis for a contractual claim or a compliance filing.
For authoritative answers on account terms, pricing, legal agreements or regulatory matters, readers should contact the bank directly through the relationship-manager channel provided at onboarding.
What if I find an error on a ScotiaConnect page?
Send the page URL and the paragraph that needs revision to service-desk@sconnect.gr.com. Corrections are reviewed within two business days. Material errors that affect operational behaviour — cut-off times, file layouts, approval thresholds — are prioritized over stylistic revisions.
Reader-submitted corrections are welcomed. They are the fastest way to catch a drifting cut-off time or a changed reporting format, because practitioners see the change sooner than the editorial group does.
Can readers submit new ScotiaConnect topic suggestions?
Yes. The editorial queue accepts reader suggestions. Topics backed by practitioner evidence and broad treasury applicability move to the top of the drafting list. Topics that would require republishing proprietary policy text or client-specific contractual language cannot be accepted.
Send topic suggestions to the same service-desk address used for corrections. The editorial group confirms receipt within two business days and includes a rough drafting estimate when the topic enters the queue.
One reader perspective
Short version. An implementation-lead reader described how the ScotiaConnect reference filled the gap between onboarding packs and the team's daily questions in the first month after go-live.
“The onboarding pack was thick, the portal help was thin, and our treasury team had a week of go-live questions that nobody wanted to escalate to the relationship manager. The ScotiaConnect reference filled that gap — cut-off times, file layout, approval routing, all in plain language.”
— Elsa R. LjunggrenImplementation Lead, Crestwater Industrial Holdings