Custom reports are the ScotiaConnect answer to "standard formats almost work, but not quite". A saved view combines a filter set, a column layout, an optional pivot and a delivery schedule. Built once, it runs on demand or arrives automatically on a cadence. This reference covers how to structure custom reports so they stay maintainable, how to scope them to a user, team or company, and how template governance keeps shared definitions from drifting.
Users coming from spreadsheet workflows sometimes expect a saved view to be a snapshot. It is not. A ScotiaConnect custom report is a definition, not a captured result. That distinction matters because the data behind a custom report is always current when the report runs. The trade-off is that saved views cannot be backdated by editing the view itself; to replicate a past run, the date filter must be changed to the historical window.
A well-built custom report typically has three to six filters, a column layout that fits inside the receiving team's reporting habit, and either zero or one pivot axis. Pivots on two axes are supported but tend to produce wider files that spreadsheet consumers find harder to work with. See transaction history for the interactive filter surface that most custom reports evolve from.
ScotiaConnect custom reports live in three scopes: private to the creating user, shared with a named team, or company-wide. The scope determines who can run the report, who receives scheduled deliveries, and who can edit the underlying definition.
Pivoted summaries are the most common reason teams move from transaction-history exports into custom reports. A monthly cash-movement summary by counterparty, a weekly FX trade summary by currency pair, or a daily outgoing-wire summary by originator are all natural fits for the pivot feature. ScotiaConnect runs the pivot server-side, so large underlying result sets still produce compact output files.
Scheduled delivery turns a custom report into an operational flow. A cadence is chosen, a subscriber list is selected, and the portal produces the file and notifies the list when the run completes. Most teams deliver to CSV for spreadsheet analysis; teams integrating with downstream systems typically pair scheduled delivery with data exports over sFTP for automated pickup.
Template sprawl is the usual failure mode. A team builds a custom report, a neighbouring team copies it, each team edits the copy, and within a quarter the two versions produce different numbers for the same question. The ScotiaConnect defence is scope discipline: mark reports that serve the whole company as company-wide, give team-specific reports a team scope, and keep private views for one-off investigations. The Canadian prudential supervisor's OSFI guidance on operational-risk documentation supports the same logic in the regulated-entity context.
| Template scope | Editable by | Delivery options | Retention |
|---|---|---|---|
| Private | Template owner | On-demand, scheduled to owner | Until deleted by owner |
| Team | Named team members | On-demand, scheduled to team list | Until deleted by administrator |
| Company-wide | Company administrator | On-demand, scheduled, sFTP push | Retained with company profile |
| Read-only shared | Original author only | On-demand, scheduled to subscribers | Until deleted by author |
| Archived | Administrator to restore | Not runnable while archived | Retained for audit history |
“We collapsed eleven overlapping spreadsheet reconciliations into four ScotiaConnect custom reports. The company-wide scope keeps every team on the same definition, and the scheduled delivery means the file lands before anyone asks for it.”
— Halldora J. KristjansdottirController, Harperton Aviation Services
A custom report on ScotiaConnect is a saved view that combines a filter set, a column layout, an optional pivot and a delivery schedule. Users build the report once and run it on demand or have the portal deliver it automatically.
Saved views store a definition, not a data snapshot. Each run pulls current data from the posting ledger.
Yes. ScotiaConnect supports private, team and company-wide template scopes. Editing rights on shared templates are governed by the company administrator, which prevents drift when multiple users rely on the same definition.
Scope choice should match the audience: private for one-off investigations, team for departmental flows, company-wide for enterprise reconciliation.
Scheduled custom reports on ScotiaConnect are delivered as CSV or Excel to the reporting queue, and optionally pushed over sFTP to a client landing directory. Email notifications can be sent to the subscriber list when a scheduled run completes.
Pair scheduled delivery with data exports when the downstream consumer is an automated treasury workstation rather than a human reviewer.
Editing rights on a shared ScotiaConnect custom report follow the scope assigned at creation. Company-wide templates are editable only by administrators. Team templates are editable by named users on the team. Private templates are editable by the owner.
Every definition change is logged to the audit trail with the acting user and timestamp, which supports post-incident investigation when a report output unexpectedly shifts.