Transaction history is where the ScotiaConnect user answers the day-to-day question "did that post?" and the investigation-mode question "where did that reference come from?" The history screen layers filters, free-text search and export paths over the same posting ledger that feeds scheduled account reporting, so answers reconcile across tools. This reference covers the filters, retention windows and audit-trail fields a treasury or payables team reaches for in the portal.
Every ScotiaConnect transaction history search starts with a date range. The default is the last thirty days, and the interactive window can be extended up to seven years on most commercial profiles. Beyond the interactive window, history is still retrievable through the scheduled statement files produced by account reporting. Filters on the history screen stack in the order they are applied, and the active filter set is shown in a breadcrumb above the results, which makes it straightforward to add, remove or narrow the filter chain mid-search.
Posting status is a frequently overlooked filter. ScotiaConnect distinguishes items that are provisionally posted from items that have cleared settlement, and the history screen exposes that distinction as a status column. Teams building end-of-day reconciliation scripts should pin the filter to cleared status, while teams investigating an overnight anomaly usually want the full provisional-plus-cleared view.
ScotiaConnect transaction history is built for audit-friendly retrieval. Every filter combination produces a deterministic result set, the export preserves filter metadata in the file header, and the underlying record carries the approver trail for payments originated inside the portal.
Filter performance is effectively instant for most commercial accounts when the date range is under thirty days. Longer windows slow proportionally, and very long windows combined with a broad amount filter are served from the reporting queue instead of the interactive grid. ScotiaConnect surfaces this transition automatically: when the query is heavy enough to warrant queue processing, the portal produces the result as a CSV download notification rather than as an on-screen grid, so the user can keep working in parallel.
Free-text search is the filter most users under-use. A transaction reference or narrative often carries an invoice number, a vendor code or an internal batch identifier, and text search against that field usually answers investigative questions faster than rebuilding a filter chain. Canadian anti-money-laundering reporting expectations managed through FINTRAC reinforce the value of good reference-field hygiene on the originating side.
The internal audit trail is the reason external auditors are comfortable relying on ScotiaConnect history for field-work evidence. The preparer-and-approver chain is non-editable once the item is released, and the history screen exposes it read-only alongside the transaction detail. When a payment is rejected or recalled, the history record captures the state transitions and the acting user, again without allowing retrospective edits. Clients that run downstream reconciliation scripts should persist the approver chain alongside the posting record, because that combination becomes the on-paper evidence for most operational audits.
| Filter field | Supported operators | Retention window | Max interactive results |
|---|---|---|---|
| Date range | Between, single day, rolling window | 7 years | 10,000 rows |
| Amount range | Equals, greater than, less than, between | 7 years | 10,000 rows |
| Transaction type | Equals, in-list | 7 years | 10,000 rows |
| Reference or narrative | Contains, starts-with, exact match | 7 years | 5,000 rows |
| Counterparty | Contains, in-list | 7 years | 5,000 rows |
| Posting status | Equals (cleared, provisional, returned) | 7 years | 10,000 rows |
“When our auditor asks for the approval chain on a specific vendor payment, the ScotiaConnect history screen answers it in under a minute. The preparer, reviewers, approvers and the rail reference are all attached to the record.”
— Sanna E. VoutilainenAccounts Payable Lead, Dunfield Textile Mill
Transaction history on ScotiaConnect supports an interactive look-back of up to seven years on most commercial profiles. The interactive window may be shorter depending on subscription tier; full retention is always available via archived statements and reporting exports.
Beyond the interactive window, account reporting files cover the same data through statement retrieval.
ScotiaConnect supports filters by date range, amount range, transaction type, originating account, reference or narrative text, counterparty and posting status. Filters stack, and the combined result set can be exported to CSV or Excel.
Free-text search against the reference or narrative field is the fastest way to locate a single item when the vendor code or invoice number is known.
Yes. ScotiaConnect exports filtered transaction history to CSV and Excel with a preserved column order that matches the on-screen view. Larger result sets are produced as a CSV download from the reporting queue rather than as an interactive export.
The export file header carries the active filter summary, which supports audit reproducibility.
Yes. For payments originated inside ScotiaConnect, transaction history includes the user who prepared the item, reviewers, approvers, timestamps and the rail confirmation reference. External debits and credits include rail-side references but not internal approver metadata.
The preparer-to-approver chain is non-editable once released, which is the characteristic that makes the record suitable as audit evidence.
Transaction history retention on ScotiaConnect is seven years on standard commercial profiles. Clients are expected to archive statement files to their own environment as well, so that independent retrieval remains possible outside the portal.
Independent archiving supports audit and legal scenarios where the file must be produced without relying on the banking system of record.