TD provides statements for personal and business checking, chequing, trust and Visa card accounts in the United States (TD Bank, USD) and in Canada (TD Canada Trust, CAD). The two layouts differ, but the converter settings are the same, so one page covers both. The reviewed statements include Business Premier, Business Simple and Convenience Checking, Business Chequing and Lawyer Trust Account, two of them scans, and Aeroplan Visa Infinite and Business Travel Visa statements.
Full name: Toronto-Dominion Bank (TD Canada Trust, TD Bank N.A.)
Countries: Canada, United States
Supported statement formats: PDF
Supported destinations: QuickBooks Desktop, QuickBooks Online, Quicken, Xero, CSV/Excel
QuickBooks Online can read a PDF statement itself: Banking, Upload transactions, choose the PDF. Try it first. Use ProperConvert when QuickBooks flags the statement for review, stops before the last page, or the account is not in QuickBooks Online.
For a short statement, type the date, memo, and amount into the destination. Reconcile the result to the closing balance.
Open the PDF statement, review the extracted transactions, choose QuickBooks Online, and save the converted file on your computer.
Choose the posted transaction date, supply a missing year from the statement period, and check statements that cross January.
Remove currency symbols from numeric cells, preserve the decimal separator, and verify debit and credit signs against the running balance.
Keep the payee or customer reference that helps identify the transaction, while avoiding repeated headers and unrelated reference numbers.
The following details were checked against TD statements from 2021 to 2026 from both the United States and Canada: TD Bank personal and business checking statements, TD Canada Trust business chequing and lawyer trust account statements, and TD Visa card statements (Aeroplan Visa Infinite, Business Travel Visa). One page covers both countries because the converter settings are the same: dates without a year, unsigned amounts, and short coded descriptions. Where the US and the Canadian layout differ, the section says which one it describes. Two of the Canadian chequing statements were scans, so the page also covers what OCR does to a TD page.
MM/DD with no year, and the year comes from "Statement Period: Jan 01 2021-Jan 31 2021" in the header. TD Canada Trust rows carry MAR11 with no space and no year, and the year comes from "FEB 27/26 - MAR 31/26" in the header. TD Visa rows carry two dates, transaction and posting, as DEC 4 and DEC 10, and the year comes from "STATEMENT PERIOD: December 06, 2024 to January 06, 2025". All three cross the year in December or January, so the converter has to assign the year from the period and not from the statement date alone.-$3,330.08.0206 and 0206-5245609 under "Branch No." and "Account No.". TD Visa prints a masked number, 4520 71XX XXXX 3243, with only the last four digits visible.TD is one brand, but the US and the Canadian statements come from two different banking systems and share almost nothing in layout. A US TD Bank statement starts with "STATEMENT OF ACCOUNT" and an "ACCOUNT SUMMARY", then lists "DAILY ACCOUNT ACTIVITY" in sections by transaction type, each with a "Subtotal:" line, and it prints no running balance next to the rows. A Canadian TD Canada Trust statement starts with "Statement of Account" and "Branch No. / Account No.", then prints one ledger with five columns, DESCRIPTION, CHEQUE/DEBIT, DEPOSIT/CREDIT, DATE, BALANCE, opened by "BALANCE FORWARD" and closed by a "Credits / Debits" count box. Even the date on the row is different: 01/27 in the US and MAR11 in Canada. A converter that keys on the bank name and applies one TD template gets nothing from the other country's file. It has to detect the layout from the page, for example from "Primary Account #:" against "Branch No.", and then parse each one with its own rules. The sections below say which layout they describe.
A US TD Bank statement under "DAILY ACCOUNT ACTIVITY" is split into sections: Deposits, Electronic Deposits, Other Credits, Checks Paid, Electronic Payments, Other Withdrawals, Service Charges. Each section has its own "POSTING DATE / DESCRIPTION / AMOUNT" header and closes with a "Subtotal:" line. Every amount is positive. A converter that reads amounts without tracking which section it is in makes every payment a deposit. Sections continue across pages with headings like "Other Withdrawals (continued)", so the section state has to survive a page break. The "ACCOUNT SUMMARY" on the first page repeats each section total, which is the check for the parse. A Canadian TD statement has no sections. It prints CHEQUE/DEBIT and DEPOSIT/CREDIT as two columns and the column decides the sign, so a converter needs the column positions from the header row and must not guess them from the first transaction.
A debit card purchase takes three lines. The first line is the type and authorization, DEBIT CARD PURCHASE, AUT 010121 VISA DDA PUR, where 010121 is the authorization date in MMDDYY. The second line is the merchant with city and state, SHOPRITE 227 * PARSIPPANY * NJ. The third line is the full 16-digit card number. A converter that keeps only the first line gives every purchase the same payee. One that joins all three lines puts a card number into the memo of every row, which is a privacy problem in the exported file. The useful payee is the second line.
Business statements add another trap. An "RTP RCVD" or "CCD DEPOSIT" row can wrap into a second line that contains a number that looks like an amount, CREDIT ACCEPTANCE CORPORATION-29 853.00, while the real amount sits in the AMOUNT column on the first line. A converter that picks the last number in the text block takes the wrong value.
"Checks Paid" prints "No. Checks: 23" and then lists checks two per row: DATE, SERIAL NO., AMOUNT, then the same three columns again to the right. A * after a serial number marks a gap in the check sequence and is not part of the number.
The "How to Balance your Account" page repeats the ending balance, 28,667.72, in a worksheet with numbered steps and empty rows for the customer to fill in. A converter that treats every line with a number as a transaction picks up the worksheet. Reconciling to the Ending Balance in the summary catches this.
Disputes and overdrafts show up as ordinary rows and must be kept. A disputed charge appears as CREDIT, Temporary Credit under Other Credits, and when the bank closes the dispute against the customer it appears as DEBIT, Reverse Temporary Credit under Other Withdrawals. Overdraft fees appear as OVERDRAFT PD and OVERDRAFT RET rows under Other Withdrawals, several on the same day. A converter that drops rows it does not understand, or merges same-day rows with the same description, loses these and the balance no longer reconciles.
A TD Canada Trust statement has five columns: DESCRIPTION, CHEQUE/DEBIT, DEPOSIT/CREDIT, DATE, BALANCE. When several transactions post on the same day, the BALANCE column is filled only on the last row of that day. A converter that expects a balance on every row either drops the rows without one or shifts the balance up to the wrong transaction. The running balance is still a good check: the balance after the last row of a day must equal the previous balance plus credits minus debits for that day.
In the text layer of a TD Canada Trust PDF, an amount in the DEPOSIT/CREDIT column and the date next to it often come through as one element, 12,710.00 MAR13, while a debit amount and its date stay separate. A converter that splits columns by position finds the credit column empty and a strange token in the date column. The element has to be split on the space before the date.
The descriptions are short and coded: HH271 TFR-TO 6649512, SEND E-TFR ***aqf, MONTHLY PLAN FEE, ACCT BAL REBATE, AMDP29617180013 MSP. The transfer reference number and the e-transfer suffix change on every row, so the payee has to be normalized to TFR-TO or SEND E-TFR before rules can match it.
Business plans print MONTHLY PLAN FEE 125.00 as a debit and ACCT BAL REBATE 125.00 as a credit on the same day. Both are real transactions that net to zero. A converter that skips one of them because the balance did not change ends up with a running balance that no longer matches the statement.
Two reviewed chequing statements were photographed or scanned, and their text came from OCR. What OCR does to this layout is predictable: FEB10 becomes FEBIO and FEB11 becomes FEBII, the period JAN 30/26 - FEB 27/26 becomes 27126, an amount like 1,463.15 splits into 1,463 and 15 with the decimal point lost, and 14,859.71 becomes 14,859, and 71 as two elements. Stray characters like '70 or 2',530: appear between rows where a taller amount was read twice. A converter that treats an OCR file the same as a text file gets amounts a hundred times too large and dates that do not parse. It has to rejoin split numbers, fix the month names against the statement period, and reconcile the running balance row by row.
The first page of a TD Visa statement prints the transaction table on the left and a side panel on the right with "CONTACT INFORMATION", "TD REWARDS POINTS", "PAYMENT INFORMATION" and "CALCULATING YOUR BALANCE". The side panel lines sit at the same height as the transaction rows, so a converter that groups text by line sees SHELL C02357 SCARBOROUGH DEC 4 DEC 6 $80.00 and Annual Interest Rate: Purchases 19.99% as one row. The table has to be cut by column position before rows are grouped.
Merchant names wrap onto a second line when the city does not fit, JACK ASTOR'S SCARBOROUGH then SCARBOROUGH again on the next line, and the second line has no date or amount. Foreign purchases add two lines below the row, FOREIGN CURRENCY 97.55 USD and @ EXCHANGE RATE 1.31963. These lines carry numbers that are not amounts in CAD. The CAD amount is the one on the row with the dates.
The bottom of the first page is a payment stub with "NEW BALANCE", "MINIMUM PAYMENT" and "PAYMENT DUE DATE" and the numbers again, and the last line is a long numeric string that holds the card number and the amounts without separators, 4520710032423243 0006500 0323442 6. A converter that scans the page for numbers picks up the balance twice and the stub line as a transaction. The stub is below the "Continued" line and has no transaction dates, which is how to leave it out.
Compare the converted transaction count and totals with the statement, then confirm that the calculated final balance equals the printed closing balance.
Yes. If the PDF statement is readable, its age does not prevent conversion. Confirm the year when transaction rows omit it.
No. Convert posted transactions that contribute to the statement balance. Pending or future-dated items should not be mixed into that reconciliation.
Use the destination-specific settings below, then review the file before import. The destination may require particular columns, dates, account identifiers, or sign rules.
A bank PDF can contain searchable text, scanned page images, or a mixture of both. Searchable text still needs layout analysis because transaction descriptions wrap, columns move, and headers or balances repeat at page breaks. A scanned statement adds OCR uncertainty.
A transaction may begin at the bottom of one page and continue on the next. Continuation pages can omit column headings, repeat an opening balance, or insert footer text and legal pages between transaction pages. A conversion should join split rows and exclude repeated page furniture before it writes the output.
On scanned pages, OCR can turn 0 into O, 1 into l, or 5 into S. It can also lose a minus sign or decimal mark, read two columns in the wrong order, or struggle with skewed and faint pages. The running balance is the best check: a damaged amount or missing row breaks the balance sequence.
Yes. Review the OCR result and reconcile every balance movement. Scans with faint printing, rotation, or handwritten marks need more checking than searchable PDFs.
PDF text stores page positions rather than a spreadsheet table. Wrapped descriptions, repeated headers, and visually aligned columns can paste in the wrong order or into the wrong cells.
Try selecting a transaction description in a PDF reader. If individual words can be selected, the page probably contains text. If the whole page behaves like one picture, it requires OCR.
QuickBooks Online imports bank transactions from a file through Banking, Upload transactions. It accepts QBO, QFX and OFX files, which share the OFX structure, and CSV files. Uploaded rows land in the For Review list, where QuickBooks matches them to existing entries and the user adds or excludes them.
Since 2026 the same upload screen also takes a PDF or an image of a statement (JPG, PNG, HEIC). Intuit's AI reads the pages, and a statement it cannot read with confidence is held for a manual review by Intuit staff. If the account is in QuickBooks Online and the statement is a clean PDF, try that first; it costs nothing. A converted file is the better route when the upload flags the statement or stops before the last page, when there are many statements to catch up, when the bookkeeper wants to see and fix every row before it enters the books, or when a client's statement should not be uploaded to a third party.
Settings that matter:
MM/DD/YYYY or DD/MM/YYYY depending on the company settings, digits only, four-digit years.Use OFX, QFX or QBO when the file can be made in that format. It carries the payee, the memo and the check number and gives QuickBooks a transaction ID for duplicate checks. Use CSV when a spreadsheet is the only source and a single description is enough.
The usual causes are a date column QuickBooks cannot read, an amount with a currency symbol or thousands separator, more columns than the three- or four-column layout, or a file over the size limit. Save the file with dates as digits, amounts as plain numbers, and only the needed columns.
The account was chosen during upload. QuickBooks Online does not read the account name from the file. Exclude the rows, delete them from Excluded, and upload again with the right account selected.
In For Review, select the rows, choose Batch actions, Exclude Selected. Open Excluded, select them again, Batch actions, Delete. The rows are gone and the file can be uploaded again.
QuickBooks Online skips rows whose transaction ID it has already seen and, for CSV, rows it reads as duplicates by date, amount and description. Two genuine identical rows on the same day can be dropped from a CSV. Use an OFX-type file with unique IDs for those.
Yes. The 90-day limit applies to a live bank connection, not to a file upload. Any date range can be uploaded from a file.
For one clean statement of an account that is already in QuickBooks Online, the built-in upload is the shortest path, and this page says so. A converter earns its place when the upload flags the statement for review, when a scanned or multi-year statement does not go through, when the account is in QuickBooks Desktop, Quicken, Xero or Sage instead, or when the statement must stay on your computer. The converted file goes through the same Upload transactions screen as a QBO file, with a transaction ID per row, so re-uploading a period does not double it.