RBC Royal Bank is one of the larger statement formats we parse, and also one of the most varied. Within a single bank you get a personal chequing layout, a business chequing layout, a Visa layout, a Mastercard layout, and a French-language version of each of those for clients who have set their statement language to French. This guide walks through how to convert any RBC statement PDF into a clean Excel file and what to verify after the conversion, with notes on the format-specific quirks.
What RBC statement formats are supported
The converter auto-detects all of the following without you needing to pick anything manually:
- RBC Personal Chequing (English and French) — the standard chequing/savings statement with the Date | Description | Withdrawals | Deposits | Balance layout.
- RBC Business Chequing (English and French) — same column structure as personal but with the business-account header block and longer descriptions for cheque and EFT lines.
- RBC Visa (English and French) — credit-card statement with Transaction Date | Posting Date | Description | Amount.
- RBC Mastercard (French primarily; the English Mastercard layout shares the Visa parser) — same column structure as Visa.
If your statement does not auto-detect (rare, but it happens with very old layouts or with statements re-saved through a PDF editor), expand the Wrong format detected? Pick your bank manually disclosure under the upload zone and select the right RBC variant from the dropdown.
Step 1: Download your statement from RBC Online Banking
Sign in to RBC Online Banking, go to My Accounts → Statements, pick the account, and download the PDF version. RBC statements are not password-protected by default, so you can upload the file directly. If you set up statement passwords yourself, remove the password first via File → Print → Save as PDF from your PDF viewer — the converter does not accept password-protected uploads.
If your statement is in French because you set Préférences linguistiques to French, the converter will still detect and parse it correctly. You do not need to switch your account to English to use the tool.
Step 2: Upload to the converter
Drop the PDF onto the upload zone on the home page. Auto-detection identifies the RBC variant (personal vs business vs Visa vs Mastercard, English vs French) and routes it to the matching parser. You can tick Download as CSV instead of Excel if your downstream tool prefers CSV — see our CSV vs Excel guide for which to pick.
If you have several months of RBC statements and want them combined, use Merge Statements mode and drop all the PDFs together. The merged Excel file gets one sheet per source plus an All Transactions sheet sorted by date, with a Source File column so you can filter by statement.
Step 3: Verify the conversion (automatic for RBC)
RBC is one of the formats where the converter runs an automatic reconciliation check against the printed summary of account block on the statement. After conversion, if the sum of withdrawals or deposits does not match the printed totals, a yellow warning banner appears on the result page. This covers personal and business chequing in both languages, plus Visa and Mastercard in French.
Even with the automatic check, two manual sanity checks are worth doing for an extra 30 seconds:
- Compare the last row’s balance in the Excel file to the closing balance printed on the statement.
- Open the All Transactions sheet (if you merged multiple statements) and confirm the date column sorts in chronological order across the full date range.
How RBC’s opening-balance row is handled
RBC statements have a special opening-balance row at the top (and a closing-balance row at the bottom) that look like transactions but are actually summary lines. The parser strips these so they do not count as transactions in your Excel file — the row count you see should match the transaction count printed in the statement’s summary block, not the printed line count.
This matters most for Tally Prime imports: if the opening-balance row leaks into the voucher sheet, Tally will post it as a duplicate of an entry you already have, and you will spend the next hour figuring out why the bank ledger is out of balance.
French statements: what changes
The French RBC layout uses the same underlying column structure as English, but with French column headers (Date | Description | Retraits | Dépôts | Solde) and French day/month abbreviations in the date column (e.g. 1 avr. for 1 April). The parser handles both languages of date abbreviation, so amounts and dates land in the Excel file with the same data types as the English version — numbers as numbers, dates as text in DD/MM/YYYY format.
One thing to know: the French Visa and Mastercard statements have slightly different transaction-description wrapping than the English Visa. The parser stitches wrapped lines back together so each transaction is one row in the output regardless of the language.
Multi-page statements and statement-period boundaries
RBC business chequing statements routinely run 6–15 pages and have continuation lines that wrap from page to page. The parser tracks the column geometry across page breaks, so a transaction whose description wraps from page 3 to page 4 still produces a single row in Excel with the full description.
If you have a statement period that spans multiple statements (for example, you want all 2025 transactions and they live across 12 monthly PDFs), use Merge Statements mode rather than running 12 separate conversions. The output is identical in content but the All Transactions sheet gives you a single sorted view of the year.
What the Excel output looks like
For chequing/savings statements, the Excel file has one sheet called Transactions with columns Date, Description, Withdrawals, Deposits, Balance. For Visa and Mastercard statements, the columns are Transaction Date, Posting Date, Description, Amount (with debits as positive and credits as negative, matching the credit-card statement convention).
Amounts are stored as numbers with two decimal places, so =SUM() on the Withdrawals or Deposits column works immediately. Dates are stored as text in DD/MM/YYYY so they re-parse cleanly into whichever locale your downstream tool uses.
Privacy and what happens to your file
The PDF is processed in memory during the conversion request. A usage log row is written with the bank format, page count, transaction count and file size for rate-limiting and analytics — not the transaction data itself. Full details are on the privacy page; please read it before uploading sensitive statements.