How to Reconcile TD Bank Statements

Drag & drop statement PDFs hereor tap to choose files — multiple PDFs for batch mode

Privacy: uploaded files and generated exports are stored only briefly to complete your download and are automatically deleted within 15 minutes. Files are never used for any other purpose.

What you are checking against

TD statements typically run in a single chronological history with the balance shown per transaction.

Think of the statement as self-auditing. It opens at one balance, lists everything that moved, and closes at another — and if the list is complete and correctly read, the numbers cannot help but agree. Reconciliation is checking that they do, before the data is trusted downstream. Done at conversion time, the check has a practical shape: the file either reproduces the statement's balances or it is flagged with the exact rows where the walk breaks. The methodology page documents the method.

The TD Bank month-end reconciliation workflow

Begin where the proof ran out. Find the most recent month that was fully reconciled and treat everything after it as unproven, however tidy it looks. Balances that happen to agree can hide two cancelling errors.
Convert the next month only. One statement, one conversion, one result. Working singly keeps every flag attached to the month that caused it.
Interrogate a flag by size. Compare the difference to the transactions: an exact match suggests a missing or doubled row, double an amount suggests a flipped sign, a few cents suggests a misread digit. The difference itself is the best clue you own.
Close the month in the software. Reconcile the account to the statement's closing balance, listing outstanding items explicitly rather than forcing agreement.
Repeat without skipping. The workflow's power is its monotony: the same five moves, every month, no exceptions for quiet months — quiet months are where skipped steps hide.

These are the general steps most banks follow for statement downloads; exact menu labels vary by bank and change over time.

Reading one TD Bank statement closely

A TD Bank statement repays thirty seconds of orientation before any numbers move. Locate the balance pair the month is anchored to — opening and closing on deposit accounts, Previous and New on cards — and scan the transaction list for the period's biggest items, since a reconciliation difference is most often one of them. Note any section subtotals the layout prints; each one is a free checkpoint the converter's running-balance walk also uses. Pull the PDF from Statements & Notices in TD Online Banking and the TD Bank app so you are always working from the issued document, not a re-export.

When a TD Bank statement does not tie out

A transfer between two of the customer's own accounts was imported on one side only. Each account reconciles against its own statement; the pair of differences, equal and opposite, is the fingerprint.
The statement period straddles a bank holiday weekend and the bank grouped several days of card activity under one posting date — the rows are all present, but their order differs from the software's expectation.
A page-header or section-total line was read as a transaction — the converter guards against this, and any survivor shows up as a row whose own balance breaks the walk.
The statement's opening balance belongs to a different period — usually a gap month in the set. Check that consecutive statements chain: each closing balance should equal the next opening balance.

Reconciliation as a fraud and error net

Monthly reconciliation is usually sold as tidiness, but its sharper value is detection. A transaction nobody recognizes, a fee that quietly changed size, a duplicate payment to the same vendor — all of them surface fastest when someone compares the books to the bank's record every single month, while amounts and memories are fresh. A year of unreconciled statements is where small problems go to become large ones; the monthly habit is the cheapest control a small organization owns.

Questions and answers

What should I keep as evidence a month was reconciled?

The statement PDF, the converted file, and the reconciliation result for that month, filed together. That trio lets anyone re-perform the month later without asking you anything.

The difference is a few cents. Is that worth chasing?

Yes. Small differences are usually misread digits or rounding on a split transaction, and they compound silently if waved through. A reconciliation that tolerates cents teaches the whole file to drift.

Can I reconcile a quarter at once instead of monthly?

You can import in batches, but prove the months individually and in order. Three months reconciled as one blob hides which month owns a difference; the chain check needs each month's closing balance separately.

My software balance and the statement agree, but I never reconciled. Am I fine?

Not necessarily — two errors can cancel. Agreement of balances is a hint, not a proof; the proof is the transaction-level comparison a reconciliation performs. Convert and check the statements to be sure.

Who should reconcile — the person who enters transactions?

In larger setups, separation is a genuine control: the person reconciling is not the person who entered. In a one-person practice the monthly habit plus the filed evidence trio is the practical substitute.