RBC CHEQUING · INTERAC AND BILL PAYMENTS
rbc bank statement example
An RBC statement is a Canadian-dollar record in which Interac e-Transfer activity, pre-authorised debits and bill payments each describe themselves differently. Capturing those descriptions completely is what makes a later review possible. The rbc bank statement example below is an invented Day to Day chequing month where an Interac e-Transfer wraps onto a second line and a bill payment carries a long account reference that must survive the import.
Download an authentic RBC statement
From Accounts Summary, select Statements/Documents, choose Account Documents, then filter and download the document.
RBC official statement instructions ↗
View a bank-hosted sample PDF ↗ — RBC-hosted personal chequing specimen from 2004; use it as a historical layout reference, not a current statement.
Interac e-Transfer descriptions wrap, and the tail matters
Incoming and outgoing e-Transfer entries typically carry a counterparty name, and often a reference or message, in a description column that is narrower than the text. The result is a line that continues onto a second printed row. The complete string is what you need: an e-Transfer identified only by the first fifteen characters cannot be matched against the email confirmation that accompanied it.
When you extract, treat a wrapped pair as one transaction rather than two. A row count taken from printed lines will overstate the activity on any account that uses e-Transfer regularly.
Pre-authorised debits repeat and should be mapped once
Insurance premiums, utility payments, subscriptions and loan instalments commonly arrive as pre-authorised debits on a schedule. Identify the set once, with the payee as RBC prints it, and you have a checklist you can run against every subsequent statement in seconds. A missing one is a cancelled arrangement; a duplicated one is worth a phone call.
Because the amount of a pre-authorised debit can change between collections, match them on payee and approximate date rather than on amount.
Bill payments carry an account reference
A bill payment to a utility, telecom or government payee usually includes the payee name and a reference identifying your account with them. That reference is numeric, often long, and exactly the kind of string a spreadsheet will convert into a number and ruin. Set the column to text before importing.
Keeping the reference intact is what lets you prove, months later, which of two accounts with the same provider a payment was applied to.
Money in and money out in the order printed
Read the activity in the order RBC printed it rather than resorting it first. The printed sequence, together with any running balance, is what lets you follow the account's behaviour through the period. Sorting before reconciling destroys the one sequence that was guaranteed to be internally consistent.
Once the balance chain closes you can sort, group and pivot freely. Before that, the original order is a diagnostic tool.
The reconciliation itself
Everything credited and debited between the two printed balances has to account for the difference. A difference equal to one transaction usually means a wrapped e-Transfer description was read as two rows; a difference equal to a page of activity means a page was missed.
Check the transaction count alongside the totals, because two errors in opposite directions can leave a total looking correct.
Getting RBC statements from online banking
Each RBC product issues its own document; request them individually. Keep the account label with the file; an RBC customer with chequing, savings and a card will generate three documents for the same month.
The PDF is the record. A spreadsheet built from it is a working copy for analysis.
Descriptions at the heart of this rbc bank statement example
The description column does most of the work on an RBC statement, which is why three of these rows concern it.
| Field | Why it matters here |
|---|---|
| Account and currency | Canadian dollars unless the product states otherwise |
| Statement period | Oct 15 – Nov 14 on the specimen |
| Opening balance | Starting figure |
| Interac e-Transfer entries | Capture the full wrapped description |
| Pre-authorised debits | Recurring commitments; map once, verify monthly |
| Bill payment references | Long numeric strings; keep as text |
| Closing balance | C$2,034.92 on the specimen |
An RBC extraction is dependable when:
- Wrapped e-Transfer descriptions produced one row each, not two
- Bill payment references survived import with their digits intact
- Activity was reconciled in the printed order before any sorting
Interac in Canada, Zelle and ACH south of the border
US statements describe transfers quite differently, which makes the Canadian conventions stand out. Canada's payment systems are operated and documented by Payments Canada, operator of the national payment systems.
From the issued PDF, the Excel converter or the CSV converter builds the table; the extraction guide explains the checks.
RBC bank statement example: e-Transfers and references
Why is my e-Transfer description cut in half?
The column is narrower than the text, so it wrapped onto a second printed line. The two lines are one transaction.
How should I track pre-authorised debits?
Map the set once by payee, then check each later statement against that list. Match on payee and date rather than amount, which can vary.
Why did my bill payment reference change after import?
The column was read as numeric. Set it to text before importing; converting afterwards does not restore the digits.
Should I sort the transactions before reconciling?
No. The printed order with the running balance is a diagnostic. Sort only after the balance chain closes.
Why does an Interac e-Transfer show a name but no account number?
e-Transfers are addressed by email or mobile number, so the statement names the sender or recipient. Keep the whole description, including any wrapped second line, to identify the payment later.