Account alerts convert passive portal data into active operational signals. A threshold breach, a payment-status change, a login from a new geography or a positive-pay exception lands in the treasury team's inbox, SMS, portal or mobile push within seconds of the trigger. This reference covers the alert categories, the delivery channels, the quiet-hours model and the escalation rules that prevent an unacknowledged alert from quietly dying in a user's inbox.
Balance-threshold alerts are the most common on ScotiaConnect. A configured upper or lower bound on a daily closing balance produces a notification when the actual balance crosses the bound. Treasury teams use this for early warning on funding positions; controllers use it for cash-concentration sweeps. Payment-status alerts track origination events: submitted, approved, released, returned, rejected. These are the alerts that tell a payables analyst when a batch has cleared the last approval gate and is now in the clearing rail.
Login alerts surface sign-in events from new devices, new geographies or at unusual hours. Security alerts cover broader posture changes: a failed second-factor attempt, a policy override, a privileged-user action. Positive-pay alerts raise exceptions against check-issuance files so the authorized reviewer can decide within the required window. Canadian prudential-supervisor expectations managed through OSFI underline how important the security and login categories are for federally regulated clients.
ScotiaConnect delivers alerts through email, SMS, the in-portal inbox and mobile push. Each category can use one or more channels simultaneously, and channel choice is driven by how quickly a human needs to see the alert and whether the recipient is expected to be at a desktop.
Email is the default channel for most alert categories because it is the channel that every user already monitors. SMS is reserved for time-sensitive categories where a reviewer needs to respond inside a short window, most commonly positive-pay exceptions and certain payment-status transitions. The in-portal inbox is the system-of-record channel: every alert lands there regardless of whether email or SMS was also chosen, which means an audit reviewer can reconstruct the alert history from the portal alone. Mobile push layers a low-friction notification on top of the in-portal inbox for users who carry the mobile banking app.
Combined channels are common for positive-pay and high-severity security alerts. A single triggering event can raise a mobile push, an SMS, an email and an in-portal inbox message, each with the same correlation identifier so the recipient knows they are looking at one event rather than four.
Quiet-hours are configured per user, within company policy bounds. A treasurer who does not want SMS between 22:00 and 06:00 can suppress that channel overnight while leaving email and in-portal delivery untouched. The quiet-hours model is category-aware, so security alerts continue to reach the user during the quiet window. Escalation is a separate rule engine: an unacknowledged alert is promoted after a configured interval. Promotion can move the alert to a second recipient, a different channel, or both. This pattern is most useful for positive-pay exceptions where a response window directly affects the downstream workflow.
| Alert type | Default channel | Configurable threshold | Default state |
|---|---|---|---|
| Balance threshold | Email, portal inbox | Upper and lower bound per account | Off, configured per account |
| Payment status | Email, portal inbox | Status transition list per template | On for release events |
| Login | Portal inbox, push | New device, new geography, off-hours | On for new-device events |
| Security | Email, SMS, push | Severity level | On for medium and above |
| Positive-pay exception | Email, SMS, push, portal inbox | Exception type, amount band | On for all exception types |
| Alert digest | Daily or weekly cadence | Off, user opt-in |
“We set ScotiaConnect balance-threshold alerts on every operating account, with SMS escalation on the lower bound. It caught a late vendor posting before our end-of-day sweep and saved an unplanned overnight borrow.”
— Tejaswi A. RanganathanCash Management Lead, Maplecrest Distillery Holdings
ScotiaConnect supports balance-threshold, payment-status, login, security and positive-pay alert categories. Each category has its own channel preferences and its own escalation rules, configurable per user or per company policy.
An optional alert-digest category bundles lower-severity items into a daily or weekly email for users who prefer a single consolidated view.
Alerts can be delivered by email, SMS, in-portal inbox and mobile push. Each category can use one or more channels simultaneously, so a positive-pay exception can raise a portal message and a mobile push while a login event emails a security contact.
The in-portal inbox is the system-of-record channel, which makes post-incident reconstruction straightforward.
Yes. ScotiaConnect supports user-level quiet-hours on non-urgent alert categories. Security-category alerts continue to reach the user during quiet-hours, because the category is reserved for conditions that warrant immediate attention.
Quiet-hours are suppressed only on channels the user selects, so an overnight email can still be delivered while SMS is paused.
Escalation rules on ScotiaConnect account alerts can promote an unacknowledged alert to a second recipient or a different channel after a configured interval. Escalation is typically used for payment-status and positive-pay exceptions where a response window matters to the downstream workflow.
Each escalation event writes to the audit trail, so post-incident review can reconstruct the sequence of notifications and acknowledgements.