TD Bank's retail footprint runs down the East Coast, so screening files from that corridor regularly include its statements—and a statement adjusted in a PDF editor rarely looks adjusted. The reviewer's advantage is that a genuine TD Bank statement is a self-checking document: summary totals must match the transaction detail, daily balance figures must follow from the listed activity, dates must respect the statement period, and the PDF's internals must be compatible with how the applicant says the file was obtained. This guide arranges those tests from cheapest to most involved, so a few minutes of arithmetic does the heaviest lifting before you touch metadata at all.
Two constraints govern everything below. A file that passes every check is not thereby genuine—a patient forgery can reconcile perfectly, which is why decisions with real consequences should escalate to source verification rather than ending at the PDF. And a file that fails checks is not thereby fake: honest documents are printed, rescanned, merged into packets, marked up by brokers, and exported through aggregators, each step legitimately disturbing structure and metadata. Treat every anomaly as material for a better question—most usefully, a request for a freshly downloaded original—never as a finding in itself.
A polished bank statement is not proof of authenticity. Unusual metadata is not proof of fraud. Every signal here is a reason to ask a better question—never a verdict.
What a genuine TD Bank bank statement typically contains
TD Bank's formats differ by product and change over time, so the traits below describe commonly observed features of genuine, portal-downloaded consumer statements, not requirements. The reviewer's real test is coherence: whether the summary, the activity, the balances, and the file's metadata all describe the same account over the same period without contradiction:
- The issuer is typically identified as TD Bank, N.A., with Member FDIC language and customer-service contact details on the first page.
- The statement period is stated as an explicit date range; cycles recur on a regular rhythm for a given account and may not track calendar months.
- A summary commonly opens the statement—beginning balance, total deposits and credits, total withdrawals and payments, fees, and ending balance.
- Transaction detail typically lists date, description, and amount, and a daily balance summary commonly accompanies checking activity rather than a balance printed on every row.
- Descriptions are compact and code-styled, with recognizable conventions for direct deposits, debit-card purchases, checks, and electronic transfers.
- Masked account numbers follow one masking convention throughout—identical treatment on every page and in every summary block.
- A statement downloaded from TD online or mobile banking carries a selectable text layer; a file rendered as a single image per page is a scan or a rebuild and merits the stronger-source request below.
Field-level checks anyone can run
1. Obtain the portal original where possible
Ask the applicant, within your policy, to download the statement from TD Bank online or mobile banking and provide that exact PDF. Screenshots, photographs, and print-and-rescan copies discard the internal structure that most of these checks examine. Never request banking credentials from anyone.
2. Take the file's SHA-256 fingerprint
Hash the document at intake so your review is bound to one identifiable version. If a revised file appears later, its different hash surfaces the substitution instantly. Ocolta's free scanner runs the computation locally in the browser; nothing is uploaded.
3. Balance the summary against itself
The beginning balance plus deposits and credits, minus withdrawals, payments, and fees, has to equal the ending balance exactly. A line-level edit frequently strands the summary at its old value. Do the arithmetic in writing and preserve any discrepancy in your notes.
4. Reproduce the daily balance summary
Where the TD Bank statement includes daily balances, rebuild a sample of days from the transaction detail: prior day's figure plus that day's net activity should equal the printed balance. A day you cannot reproduce is the precise place to direct your next question.
5. Confirm dates, period, and continuity
All activity should fall within the stated period in chronological order. When you hold multiple months, verify the hand-off: each ending balance should appear as the following statement's beginning balance, with no absent month and no overlapping period.
6. Reconcile payroll deposits with claimed earnings
Payroll credits should identify an employer consistent with the application, arrive on the declared schedule, and match net pay from any pay stubs supplied. Deposits that mirror gross pay, or wages arriving as informal transfers, are gaps between story and statement worth closing.
7. Evaluate creator and producer metadata
The PDF names the software that produced it. A statement crediting a general-purpose editor or design tool needs an explanation, and a modification timestamp trailing well behind creation contradicts a claim that the file is a straight, untouched download.
8. Look inside for incremental revisions
PDFs can be saved incrementally, retaining prior versions within the same file. A TD Bank statement offered as a single fresh download that turns out to contain multiple internal revisions is strong cause to require a replacement pulled directly from the source.
9. Put decisive figures under 400% zoom
Enlarge the deposits and balances your decision hinges on. Edited digits tend to give themselves away—slight baseline drift, a nearly-right typeface, alignment that breaks the numeric column. Compare against identical digits printed elsewhere on the same page.
10. Verify holder details page by page
The name, masked account number, and address should be identical on every page and consistent with the application file. Masking that changes style midway through the document points to pages drawn from different sources and calls for the stronger-source request.
11. Stress-test convenient-looking activity
Genuine months are messy—odd cents, uneven gaps, small recurring charges. A statement built from round deposits, cloned rows, or a balance that never once approaches your screening threshold deserves comparison against an adjacent month before it carries any weight.
What Ocolta’s free scan checks automatically
Several of the checks above are mechanical, and mechanical work belongs to software. Ocolta’s free bank statement checker runs entirely in your browser—the file never leaves your device—and reports the supported signals it can actually observe: whether the declared file type matches its binary signature, which software the PDF says created and produced it, creation and modification timestamps, incremental revision pointers, embedded scripts or attachments, and a SHA-256 fingerprint of the exact file you reviewed. For statements it also reconciles the summary arithmetic—opening balance plus credits minus debits against the closing balance—and explains benign causes to consider for each observation. The PDF tamper checker runs the structural subset on any PDF. Every result keeps “unable to determine” on the table; the scan never claims a bank statement is authentic or fraudulent.
When to escalate beyond file review
File review narrows the problem; it never closes it. If material doubt remains after these checks, escalate through an authorized channel: a consumer-permissioned account-data connection, a newly downloaded original requested under your written policy, or a documented verification call using TD Bank contact information you looked up independently—never a number printed on the document under review. Hold every applicant to the same escalation standard, and involve legal counsel before document findings contribute to an adverse decision of any kind.
When the file itself deserves a deeper look before you escalate externally, Ocolta’s AI Deep Review ($5 per document, no subscription) asks a model to organize fraud-risk and AI-generation indicators—evidence locations, confidence, benign explanations, limitations, and next checks. It reports observations, not verdicts, and it can return “unable to determine.” See pricing for 5-review and 25-review packs.
Frequently asked questions
Can Ocolta tell me whether a TD Bank statement is fake?
No tool can make that judgment. Ocolta's free scan reviews structure, metadata, revision history, and statement arithmetic locally in your browser and reports supported observations, including an explicit unable-to-determine result. It does not certify documents, accuse anyone, or contact TD Bank.
What is the fastest first check for a TD Bank statement?
Reconcile the summary: beginning balance plus deposits and credits, minus withdrawals and fees, must equal the ending balance—then confirm the daily balances follow from the activity. It takes minutes, needs no software, and trips careless edits more reliably than visual review.
Is unexpected metadata proof a TD Bank statement is forged?
No. Printing and rescanning, merging PDFs, exporting from mobile apps, and aggregator processing all rewrite metadata in ordinary, honest workflows. An anomaly warrants a request for the portal-downloaded original and an account of the file's history—nothing stronger.
Will TD Bank confirm a statement for my screening file?
Do not trust contact information printed on the document you are questioning; forged statements can carry forged phone numbers. Use an authorized verification channel or independently sourced contact details, document the attempt, and apply your written policy identically to every applicant.
Do not tell an applicant that a document is “fake” based on file review alone. State the observation, request the same follow-up your written policy requires in comparable cases, apply consistent criteria to every applicant, and preserve an unable-to-determine outcome. Obtain legal review before using document findings in an adverse decision.