Chase is one of the most commonly submitted banks in United States rental, lending, and employment screening files, so reviewers see a lot of Chase statements—and a Chase statement that has been altered in a PDF editor often looks completely normal at arm's length. The goal of this guide is not to teach you a single “tell.” It is to give you a repeatable sequence of checks that use the statement's own structure against sloppy edits: the summary must reconcile, the running balance must chain, and the file's internal metadata must be consistent with how the applicant says they obtained it.
Two cautions before you start. First, a clean file is not proof of authenticity: a careful forgery can pass every visual and arithmetic check, which is why high-stakes decisions should escalate to source verification. Second, a messy file is not proof of fraud: legitimate statements get printed, rescanned, merged, annotated, and passed through third-party aggregators, and each of those steps changes metadata. Treat every signal below as a reason to ask a better question, never as a verdict.
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 Chase bank statement typically contains
Formats change over time and vary by account product, so treat these as commonly observed traits of genuine, portal-downloaded Chase consumer statements rather than guarantees. What matters for verification is less any single visual detail than the internal consistency of the whole document:
- The issuer is typically identified as JPMorgan Chase Bank, N.A., with customer-service contact details in a box near the top of the first page.
- A statement period is stated as an explicit date range (for example, “July 09, 2026 through August 06, 2026”). Chase cycles do not always align to calendar months, so a period that starts mid-month can be perfectly normal.
- Checking statements typically open with a summary section (beginning balance, deposits and additions, categorized withdrawals, ending balance) followed by a transaction detail table listing date, description, amount, and a running balance.
- Transaction descriptions tend to be terse and uppercase-heavy, with recognizable prefixes for payroll direct deposits, card purchases, ATM activity, and electronic transfers.
- The account number is shown for the statement's account; where masking appears, it is applied consistently everywhere the number occurs, not on some pages only.
- Typography is uniform: one font family, consistent sizing within tables, right-aligned numeric columns, and page footers with page numbers in a consistent position across pages.
- A digitally downloaded statement is a text-layer PDF: you can select and copy the transaction text. A statement that is one large image per page is a scan or a reconstruction and deserves the stronger-source request below.
Field-level checks anyone can run
1. Ask for the portal-downloaded original
A PDF downloaded directly from chase.com or the Chase app preserves far more verifiable structure than a screenshot, photo, or print-and-rescan. If your policy allows, ask the applicant to download the statement themselves and send that exact file. Never ask for banking credentials.
2. Fingerprint the exact file you reviewed
Record a SHA-256 hash of the file the moment you receive it, so the document you checked is provably the document you decided on. Ocolta's free scanner computes this locally.
3. Reconcile the summary math
Beginning balance + deposits and additions − total withdrawals must equal the ending balance. An edit that inflates one deposit frequently forgets to update the summary. Document the exact formula and any discrepancy rather than eyeballing it.
4. Recompute the running balance
Chase transaction detail typically carries a running balance column. Spot-check it line by line for at least one page: each balance should equal the previous balance plus or minus that line's amount. A single broken link in the chain localizes exactly where a number was changed.
5. Check the statement period and day ordering
Every transaction date should fall inside the stated period, and dates should progress monotonically. Compare the period against adjacent months if you have them: the prior ending balance should match the next beginning balance.
6. Compare payroll deposits against the claimed income
Direct deposits should match the applicant's stated employer, pay cadence (weekly, biweekly, semimonthly), and net—not gross—pay from any paystubs in the file. A “payroll” deposit that arrives on an irregular cadence, or that exactly equals gross pay, deserves a question.
7. Inspect creator and producer metadata
A PDF records the software that created it. General-purpose design or editing tools appearing as the creator of a bank statement is worth an explanation; so is a modification timestamp long after the creation timestamp on a file presented as an untouched download.
8. Look for incremental revisions and appended objects
PDFs can be saved incrementally, leaving earlier versions of the document inside the file. Multiple revision pointers in a statement presented as a fresh download are a strong reason to request the original from source.
9. Check typography and alignment under zoom
Zoom to 400% on the figures that matter. Edited numbers often sit subtly off the baseline, use a near-match font, or break the column's right alignment. Compare the suspect figure with the same digit elsewhere on the page.
10. Verify account-number and name consistency
The account holder's name, the account number (or its masked form), and the address block should be identical on every page and should match the application. Mixed masking styles across pages suggest pages from different sources.
11. Sanity-check round numbers and duplicates
Real spending is noisy. A month of suspiciously round deposits, copy-pasted transaction rows with identical cents, or a balance that never dips before rent day are patterns worth comparing against a second month's statement.
12. Confirm the file behaves like text, not a picture
Try selecting the transaction text. If a supposedly portal-downloaded statement is actually a flat image, ask why. Images are not disqualifying—scans are common—but they remove most of the checks above, which raises the value of source verification.
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 is triage, not proof. If the decision is material—a lease, a loan, an employment offer—and questions remain after these checks, move to an authorized verification method: a consumer-permissioned account-data connection, a request for an issuer-downloaded original delivered under your written policy, or a documented verification call using contact information you looked up independently (never a number printed on the suspect document). Apply the same escalation criteria to every applicant, and get legal review before using document findings in an adverse decision.
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 Chase statement is fake?
No tool can. Ocolta's free scan checks the file's structure, metadata, revision history, and statement math locally in your browser and reports supported observations, including an explicit unable-to-determine outcome. It never claims a document is authentic or fraudulent, and it does not contact Chase.
Does Chase verify statements for landlords or lenders?
Do not rely on a phone number or email printed on the submitted document—if the document is forged, its contact details can be too. Use an authorized verification channel or contact information you obtained independently, and follow your own written screening policy.
Is unusual metadata proof that a Chase statement was forged?
No. Printing, rescanning, merging pages, mobile-app exports, and third-party financial software all alter metadata legitimately. Metadata anomalies justify requesting a portal-downloaded original; they do not justify an accusation.
What is the fastest single check to run first?
Reconcile the summary: beginning balance plus deposits minus withdrawals must equal the ending balance, and the running balance must chain line to line. It takes two minutes, it is objective, and sloppy edits fail it more often than any other check.
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.