How to Export Interac e-Transfer History to CSV or Excel

To export Interac e-Transfer history into CSV or Excel, download the relevant account activity and any dedicated e-Transfer history available through your financial institution, then add useful details from the original notification emails. Keep one row per actual transfer, preserve its status and reference number, and reconcile the finished file to the bank account before using it for bookkeeping or tax records.

There is no single export workflow that applies to every Canadian bank or credit union. Interac e-Transfer is accessed through participating financial institutions, so available dates, fields, formats, and history screens vary. A bank CSV may confirm the money movement but omit the payer, recipient, reference, or invoice context you need.

What Should You Export From the Bank and the Inbox?

Treat the bank record and notification record as two connected sources:

• Bank account activity: supports whether money entered or left the account, the posting date, amount, and balance impact.
• Dedicated e-Transfer history: may show the recipient or sender, status, contact, and transaction reference, depending on the financial institution.
• Notification email: may preserve the displayed person, amount, direction, lifecycle status, message, and Interac reference.
• Invoice, receipt, lease, or contract: explains why the payment happened and how it should be classified.

Interac says email and text carry transaction notifications while financial institutions use payment networks to move the money. It also says each e-Transfer receives a unique reference number for identification and tracking. That reference can help connect records, but it does not replace the bank entry or source document.

Which Columns Belong in an e-Transfer CSV?

Use stable columns that can be filtered without changing the original facts. A practical business export includes:

• Bank posting or completion date
• Notification date
• Sent or received direction
• Amount and currency
• Displayed sender or recipient
• Known customer, supplier, tenant, or employee
• Email address or mobile number, when legitimately available and needed
• Status, such as completed, pending, cancelled, declined, or expired
• Interac or bank reference number
• Invoice, bill, property, unit, project, or claim identifier
• Category and business purpose
• Connected inbox and bank-account label
• Notes explaining an allocation, correction, or unresolved item

Keep dates in an unambiguous format such as 2026-09-03, keep amounts as numeric values, and use separate direction or debit-and-credit fields instead of adding words to the amount cell. Do not store security answers, passwords, complete bank-account numbers, or unrelated personal information in the spreadsheet.

How Do You Build a Reliable e-Transfer Export?

1. Define the exact scope

Choose the business or property, bank accounts, inboxes, date range, and payment direction before downloading anything. Record whether the range uses bank posting dates, notification dates, or both.

A calendar-year tax file, monthly rent register, and accounts-receivable review can include different transactions. Mixing scopes makes totals difficult to explain and increases the chance of including personal transfers.

2. Download the bank activity first

Use the financial institution's known app or website. Download the applicable transaction range in CSV, Excel, OFX, QFX, QBO, or another format your bookkeeping workflow accepts. Also save the statement or other readable bank record for the period.

If the account offers a separate Interac e-Transfer history, export or preserve that view too. Do not assume a general bank CSV contains the same detail. If older activity is unavailable online, contact the bank or credit union and ask what records can still be supplied.

The bank export is the settlement layer. Preserve it unchanged, then work from a copy so sorting or adding columns does not alter the source file.

3. Gather the matching notification records

Search every inbox that received or sent notifications during the period. Include Autodeposit notices and status changes, not just messages whose subject says a transfer was sent.

If the history spans old accounts or deleted messages, follow the old e-Transfer record recovery workflow. Record any period or inbox you could not retrieve instead of quietly treating the export as complete.

4. Collapse lifecycle messages without erasing them

One transfer can generate a sent notice, reminder, deposit confirmation, cancellation, decline, or expiry notice. Do not turn each message into a new payment row.

Group messages using the reference number, amount, people, direction, and timing. Keep the final status in the main row and retain the underlying messages or a linked status log. Never merge two transfers solely because their amounts match.

Use the pending, cancelled, declined, and expired e-Transfer workflow when the lifecycle is unclear.

5. Add the business context

Match each completed transfer to the invoice, receipt, contract, customer account, rent period, expense claim, or other source document. Keep the displayed banking name and the known business name separately when they differ.

Do not label every incoming transfer as income or every outgoing transfer as an expense. Owner contributions, shareholder loans, refunds, reimbursements, customer deposits, and movements between the business's own accounts need different treatment.

If a payer remains unclear, leave the row unmatched and use the unknown-sender verification checklist before classifying or returning money.

6. Reconcile the file to the bank

Compare every completed row with the corresponding bank deposit or withdrawal. Investigate:

• A notification with no bank movement
• A bank line with no notification record
• A duplicate row created from two emails
• A different amount, date, direction, or account
• A cancelled attempt included in the completed total
• A refund or replacement transfer missing from the sequence

The reconciled total should agree with the scoped bank activity after documented non-business items, fees, refunds, and transfers between accounts are handled separately.

7. Validate and preserve the export

Check the row count, filters, date range, formulas, blank identifiers, duplicate references, and totals. Open the final CSV in a second program or import a copy into a blank spreadsheet to confirm that dates, accents, commas, and amounts remain readable.

Save the reconciled CSV with a clear filename, keep a readable PDF or statement where useful, and preserve the original emails and source documents. The Canada Revenue Agency says electronic records must remain accessible and usable, and that an audit trail should connect source documents to summarized accounts. Converting records must not destroy or alter relevant information.

Is a CSV Export Enough for the CRA or an Accountant?

No. A CSV is a useful transaction index, not a complete evidence package.

The CRA says business-income records should show the date, amount, and source and be supported by original documents. Depending on the transaction, that may include invoices, receipts, contracts, bank statements, deposit records, and relevant emails. Give an accountant the reconciled export plus the documents that explain each amount and any unresolved exceptions.

Use the e-Transfer bookkeeper handoff checklist to package the register, bank evidence, source documents, and open questions for a monthly or year-end close.

For a formal request, follow the CRA e-Transfer audit preparation workflow and the exact scope and delivery instructions in the CRA letter.

Which Export Problems Need Extra Care?

The bank CSV does not show the sender

Use the amount, date, reference, notification, expected payments, and source records together. Do not identify a customer from amount alone.

Several inboxes or accounts were used

Keep an inbox and bank-account label on every row. Reconcile each account independently before combining a reporting view.

The history contains personal and business transfers

Preserve the original account total, identify exclusions, and document why they are outside the business scope. A mixed account does not make personal movements deductible or business receipts non-taxable.

The spreadsheet will be imported into accounting software

Confirm the software's required bank-statement format and remove overlapping dates before importing. A notification export is not automatically a bank-statement file. Importing both can duplicate the same cash movement.

For Wave users, the safer default is to use the notification export as a matching register beside the bank transactions already in Wave. The Wave e-Transfer reconciliation guide explains when to categorize an imported bank line, merge a true duplicate, and reconcile the period.

The same separation matters in desktop accounting software. The Sage 50 e-Transfer reconciliation guide explains how to use notification details beside bank feeds or imported statements without creating a second cash movement.

How TransferLog Helps Export Notification History

TransferLog organizes details found in supported incoming and outgoing Interac e-Transfer notification emails from connected Gmail, Outlook, or iCloud inboxes, starting from January 1, 2024. You can search and filter by fields such as date, person, amount, direction, status, reference, category, and connected inbox. CSV and PDF export are available on the Pro plan.

Use the TransferLog export as the notification layer, then reconcile it with the financial institution's records and the invoices, receipts, agreements, or ledgers that explain each payment. TransferLog does not access bank accounts, retrieve deleted email, guarantee that every notification format is supported, create source documents, or decide tax treatment.

Official Sources

• Interac e-Transfer Help Topics
• Interac e-Transfer FAQ
• CRA: Business records
• CRA: Your responsibilities for business records
• CRA: Electronic Record Keeping

Organize supported e-Transfer notifications before your next export. Start free; export on Pro, then reconcile the file with your bank and source documents.