Truist was formed from the merger of BB&T and SunTrust, and its statements are now common in screening files across the Southeast and Mid-Atlantic. The brand's relatively short history gives reviewers one extra, carefully hedged angle: documents dated well after the conversion to Truist branding would ordinarily carry Truist identity rather than legacy BB&T or SunTrust marks, so a mismatch between the document date and its branding is worth a polite question—though never a conclusion, since transition-era documents and archived statements complicate the picture. Beyond that, the discipline is the same as for any bank: make the arithmetic prove itself and make the metadata match the story.
Anchor the review with two principles. A file that clears every check remains unproven—patient forgeries reconcile perfectly, which is why leases, loans, and offers that matter should proceed to source verification instead of stopping at the PDF. A file that trips checks remains unaccused—printing, rescanning, merging, broker annotations, and aggregator exports all disturb structure and metadata in the ordinary course of honest life. Treat each signal below as the start of a better question, most often a request that the applicant download a fresh original and send that exact file.
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 Truist bank statement typically contains
Truist statement formats vary by product and continue to evolve, so the traits below are commonly observed features of genuine, portal-downloaded consumer statements rather than rules. Because the brand consolidated two predecessor banks, internal consistency—arithmetic, dates, branding, and metadata agreeing with one another—is an especially useful lens here:
- The issuer typically identifies itself as Truist Bank, with Member FDIC language and customer-service contact details on the first page.
- The statement period appears as an explicit date range; cycles recur predictably for a given account without necessarily matching calendar months.
- A summary section commonly presents the beginning balance, total deposits and credits, total withdrawals and debits, fees, and the ending balance.
- Transaction detail typically shows date, description, and amount, and balance information—per line or as daily balances—is commonly included with checking activity.
- Descriptions are compact and pattern-heavy, with recognizable forms for payroll credits, card purchases, ATM withdrawals, and transfers.
- Account-number masking follows one consistent convention across all pages and summary blocks of the document.
- A statement obtained from Truist online or mobile banking is a text-layer PDF with selectable text; a flat-image file indicates scanning or reconstruction and calls for the stronger-source request below.
Field-level checks anyone can run
1. Ask for the Truist online-banking original
The most reviewable artifact is the PDF the applicant downloads from Truist online or mobile banking and forwards untouched. Screenshots, photos, and rescans surrender the structure that powers most of these checks. Request the original where policy allows, and never ask for credentials.
2. Hash the exact file you received
Compute a SHA-256 fingerprint at intake so the reviewed document is pinned beyond argument. Later substitutions produce different hashes and become visible immediately. Ocolta's free scanner performs the computation locally; the file stays on your machine.
3. Force the summary to reconcile
Beginning balance plus deposits and credits, minus withdrawals, debits, and fees, must equal the ending balance to the cent. Transaction-level edits frequently leave summaries stale. Write out the equation and document any residual rather than approximating by eye.
4. Verify the balance progression
Where balance figures accompany the activity—per line or per day—recompute a meaningful sample: each figure should follow from the previous balance and the intervening transactions. The first irreproducible balance tells you precisely which row deserves scrutiny.
5. Test dates, period, and month-to-month continuity
Every transaction should fall inside the printed period with dates in order. Across consecutive statements, the ending balance must carry into the next beginning balance. A missing month between otherwise continuous Truist statements is itself worth a question.
6. Compare payroll activity with the stated income
Deposits labeled as payroll should match the claimed employer, cadence, and the net figures on any pay stubs submitted alongside. Income that appears only as transfers from another personal account, while claimed as employment wages, needs clarification before it supports a decision.
7. Weigh branding against the document date
Truist branding replaced BB&T and SunTrust identities after the merger. A statement dated recently but styled as a legacy brand—or mixing brand identities across pages—deserves an explanation. Hedge carefully: archives and transition-era documents exist, so this is a question, never a verdict.
8. Inspect creator and producer metadata
Check what software the PDF reports generated it. Editing and design applications appearing as the creator of a bank statement invite an explanation, as does a modification timestamp substantially later than creation on a file presented as a direct download.
9. Look for incremental save history
Incrementally saved PDFs can preserve earlier versions of themselves inside the file. Multiple internal revisions in a statement offered as a clean, single download are strong grounds to require a fresh original retrieved directly from the source.
10. Scrutinize amounts under magnification
At 400% zoom, altered digits show their seams: baseline drift, near-match fonts, disrupted right alignment in numeric columns. Compare any doubtful figure against the same numerals printed elsewhere on the page before drawing even a provisional conclusion.
11. Confirm holder details never vary
Name, masked account number, and address should be identical across every page and consistent with the application. Variation in masking style or name formatting between pages suggests assembly from multiple documents and justifies the stronger-source request.
12. Sense-check overly clean numbers
Genuine activity is untidy. All-round-dollar deposits, repeated rows with identical cents, or a balance that never approaches the threshold you screen against are patterns to test against an additional month of statements rather than accept at face value.
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
Everything above is triage. When a material decision still carries unresolved questions, escalate through an authorized route: a consumer-permissioned account-data connection, a newly downloaded original requested under your written screening policy, or a documented verification call using Truist contact information you found independently—never numbers printed on the document being examined. Keep the escalation bar identical for every applicant, and obtain legal review before document-based findings feed into any adverse action.
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 Truist statement is fake?
No tool can. Ocolta's free scan checks structure, metadata, revision history, and statement math locally in your browser, then reports supported observations—including an explicit unable-to-determine outcome when the file does not permit conclusions. It never asserts authenticity or fraud, and it does not contact Truist.
What single check should I run first on a Truist statement?
The summary reconciliation: beginning balance plus deposits minus withdrawals and fees must equal the ending balance, and any balance figures should chain from the transactions. It is quick, entirely objective, and the check that hurried alterations fail most often.
Is legacy BB&T or SunTrust branding proof of a fake?
No. Genuinely archived statements from before the Truist conversion exist, and transition-era documents varied. Branding that conflicts with the document's date is a fair question to ask the applicant—paired with a request for a current portal download—but it is not evidence of fraud by itself.
Does odd metadata mean a Truist statement was altered?
Not on its own. Printing, rescanning, PDF merging, app exports, and aggregator processing all rewrite metadata during entirely legitimate handling. Use anomalies to justify requesting the original from source and asking how the file was produced—not to level an accusation.
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.