Treasury management inside ScotiaConnect is the layer that turns a set of operating and savings accounts into an orchestrated liquidity picture. Cash concentration, zero-balance accounts, physical and notional pooling, sweep rules, liquidity reporting and treasury-workstation file exchange all sit together under one portal surface. This reference explains the shapes clients most commonly stand up in the first year of ScotiaConnect use, the practical differences between physical and notional pooling, how same-currency and multi-currency pools operate, and the Canadian intra-company lending context that sits behind cross-entity concentration structures.
Concentration and ZBA structures collapse many operating balances into one working position each night. The sweep direction, the settlement frequency and the target balance on each leg are set during the treasury-management onboarding and adjusted as entity volumes evolve.
Cash concentration moves working-capital balances from many subsidiary accounts into a single master account, so the treasury team has one number to manage instead of dozens. A zero-balance account takes the concept to its limit: the subsidiary account clears to zero at end-of-day by sweeping every remaining dollar into the master. Intraday activity still posts against the ZBA - payables, receivables, card settlements - but overnight the master account holds the consolidated position, and the next morning the master funds each ZBA back to its operational minimum if one is set.
A typical implementation at a mid-market client will use three or four ZBAs feeding a single master concentration account per currency. Tomas V. Kalvelis at Beaconridge Public Infrastructure, for example, runs four CAD ZBAs (project-level payables accounts) and one CAD master concentration account; each project account clears to zero overnight and is funded back to a per-project minimum before the morning payables run. The same structure exists in USD for the cross-border project portfolio, with its own master and its own set of ZBAs.
Concentration structures that move cash across legal-entity lines require intra-company lending documentation. Canadian income-tax rules on intra-company loans, transfer pricing and interest allocation - administered broadly through Canada Revenue Agency guidance and framed at the prudential level by the Office of the Superintendent of Financial Institutions via OSFI - mean the treasury team keeps a written intra-company lending agreement on file for every cross-entity sweep. ScotiaConnect does not produce the agreement; it consumes it as a pre-condition of setting up the cross-entity structure, and the relationship manager verifies that the agreement is in place before enabling the sweep.
Physical pooling is the structure most widely used in Canada. Sub-account balances sweep into a master account overnight, the master account earns interest on the concentrated balance, and sub-account balances reset in the morning. Physical movement means the cash actually moves between accounts, and that movement creates an intra-company loan when the source account and the destination account belong to different legal entities. The tax and legal overhead of physical pooling is significant for cross-border or multi-entity structures but is well-understood, which is why it remains the default in commercial treasury practice.
Notional pooling does not move cash. Instead, the bank calculates interest on the aggregate position across all accounts in the pool, leaving each account balance physically in place. For clients that do not want intra-company loans created every night, notional pooling is attractive because the legal fiction is that each entity holds its own cash at all times. Notional pooling is available on ScotiaConnect but carries regulatory constraints: cross-border notional pooling is tightly restricted in several jurisdictions, and cross-entity notional pooling requires the bank's right of set-off to be documented between all pool participants. Investment-industry context for cross-border interactions with dealer-desk activity is shaped in Canada by IIROC and in the United States by SEC-registered counterparties on the credit-card and FX side.
In practice, clients choose physical pooling when intra-company lending is already part of the tax file and the operational benefit of one consolidated working balance justifies the documentation. They choose notional pooling when keeping the accounts legally separate matters more than achieving a single physical balance - common with holding structures where each subsidiary must maintain clear and auditable cash ownership.
Liquidity reporting is the output layer of the treasury-management module. The screen shows each currency, each entity in the pool, the current position, the intraday change and the projected end-of-day number. ScotiaConnect exposes the same view in PDF for archival, CSV for ad-hoc work, and in BAI2, CAMT.053 and CAMT.052 for treasury-workstation consumption. The feeds are scheduled to a sFTP landing directory and consumed by workstations such as Kyriba, GTreasury, FIS Quantum or internally built liquidity platforms. The MT940 format remains available for legacy integrations.
Same-currency pools aggregate balances within one currency; multi-currency pools support cash concentration across CAD, USD, EUR and GBP, with notional interest calculated per currency leg rather than through forced conversion. The multi-currency pool screen shows each currency leg, the leg balance, the aggregate notional interest at the pool level, and the per-entity allocation. This avoids the sharp corner where multi-currency pooling quietly creates unintended FX exposure on leg sweep.
The Bank of Canada's oversight of core payment infrastructure, referenced at Bank of Canada, sits behind the Canadian settlement rails that liquidity feeds report on. Same-day settlement frequency on Lynx drives the intraday BAI2 cadence that most clients pull. Multi-currency reporting for cross-border pool legs picks up the target settlement frequency for each leg's home payment system.
| Structure | Pool type | Settlement frequency | Entity visibility |
|---|---|---|---|
| Single ZBA feeding master | Physical (same entity) | End-of-day | Single-entity |
| Multi-ZBA feeding master | Physical (same entity) | End-of-day | Single-entity |
| Cross-entity concentration, CAD | Physical (cross-entity) | End-of-day | Multi-entity, per agreement |
| Same-currency notional pool | Notional (same currency) | Interest-calculated daily | Multi-entity, per set-off |
| Multi-currency notional pool | Notional (per-leg) | Interest-calculated daily, per leg | Multi-entity, per set-off |
| Hybrid (physical sweep + notional on residual) | Physical + notional | End-of-day + daily calc | Multi-entity, layered |
“We run a physical sweep within each legal entity and a notional overlay across the group. That gives us one working number every morning and keeps each subsidiary's balance sheet legally intact overnight. The ScotiaConnect liquidity screen is the single view the treasury team opens first.”
— Tomas V. KalvelisTreasury Director, Beaconridge Public Infrastructure
A zero-balance account is a subsidiary operating account that clears to zero at end-of-day by sweeping its balance into a master concentration account. Intraday activity posts against the ZBA; overnight the master account holds the consolidated position.
Most ZBA implementations also set a morning minimum on the subsidiary, so that the master funds each ZBA back to an operational balance before the payables run. The minimum is a configuration option inside the treasury-management setup.
Physical pooling moves cash between accounts through actual sweep transactions, consolidating balances into one account. Notional pooling leaves balances in place and calculates interest on the aggregate position, without moving funds between entities.
Physical pooling creates intra-company loans whenever the source and destination accounts sit in different legal entities, which carries tax and transfer-pricing implications. Notional pooling avoids the loan creation but requires documented right of set-off between pool participants.
Yes. Same-currency pools aggregate balances within one currency. Multi-currency pools support cash concentration across CAD, USD, EUR and GBP, with notional interest calculated per currency leg rather than through forced conversion.
Multi-currency pool screens show each currency leg, the leg balance, the aggregate notional interest at the pool level and the per-entity allocation. This avoids the sharp corner where multi-currency pooling quietly creates unintended FX exposure on leg sweep.
Entity visibility is controlled by permission rather than by balance blending. A user with cross-entity view rights sees a stacked liquidity grid with each entity's position shown separately. True balance consolidation is achieved only through a concentration or pooling structure, documented in the treasury-management setup file.
This separation between view permissions and actual cash movement is deliberate. It keeps the audit trail clean: any movement between entities is a logged sweep against an underlying agreement, not a side effect of how a user happens to view the portal.
ScotiaConnect delivers prior-day BAI2, intraday BAI2, CAMT.053 and CAMT.052, and MT940 feeds to treasury workstations, typically over scheduled sFTP to a client-defined landing directory. Common workstations include Kyriba, GTreasury and FIS Quantum, alongside internally built liquidity platforms.
Feed cadence is set on the reporting configuration screen. Most clients run a prior-day BAI2 feed at the overnight cut-off, an intraday BAI2 refresh every two hours during the business day, and a CAMT.053 or MT940 feed for cross-border-aware workstations.