Convert TD Bank Statements to Excel

Upload the statement PDF and the transaction activity is extracted into structured rows — dates, descriptions, amounts, and balances where printed.

Dates deserve a second look on any statement whose format you have not converted before. A date written numerically can be read two ways depending on the convention the document follows, and a statement that omits the year on continuation lines relies on its period header for context. StackExtract reads the document’s own format; confirming that reading is a review step worth spending thirty seconds on, because a transposed date does not change any total and so no arithmetic check will catch it.

That is the general shape of what review is for: the checks catch what changes a total, and a person catches what does not. A date, a description and an account attribution all fall in the second category.

Every extracted cell is editable before anything is exported, and rows a check flagged are marked so the review is directed rather than a re-read of the whole statement. Where the statement prints opening and closing balances, the reconciliation check runs against them: the transactions should move the opening figure to the closing one.

Where the statement does not supply those figures, the check is reported as one that could not run — never as a pass. And nothing is silently corrected: where figures disagree, both are shown as printed and the row is flagged, because a tool that adjusted a number to make its own arithmetic work would be removing the evidence you needed.

Historical reconstruction is the usual reason — the period needed predates the connection, or the account is closed, or a client’s archive is the only copy.

Cross-border work adds its own version of the same problem, where statements from different jurisdictions follow different conventions and need to end up in one consistent spreadsheet.

StackExtract is an independent tool and has no affiliation with any bank.

Statements from different periods or jurisdictions can be uploaded together and are each read on their own terms, then exported into one consistent shape. The consistency comes from the export rather than from an assumption that the sources agreed.

XLSX is the usual choice when a person is going to read the file: it opens in Excel with the columns intact and the accented characters preserved. CSV is the choice when something else will consume the rows.

For bank statements there is also a QuickBooks-ready CSV, shaped for that import workflow. It is a file you download and import yourself — not a QBO file, not Web Connect, and not a connection to your accounting software or to the bank. Every import decision stays in your environment.

One PDF is one document whatever its page count, and the free preview shows the whole result before you decide to export.