How to spot warning signs in a bank statement
Check the source file, statement continuity, running math, and the limits of visual review.
Read the guideOcolta field guides
Review documents with a method, not a hunch.
Source-aware checklists for income documents and AI-generation indicators—written around what a file can expose, what remains uncertain, and what still needs verification.
A defensible paystub verification checklist
Reconcile gross pay, deductions, net pay, dates, year-to-date totals, and employer-source evidence.
Read the guideHow to review AI-generated document signals
Check provenance, internal coherence, metadata, detector limits, and source evidence without claiming reliable origin detection.
Read the guideA document failed review. Now what?
Confirm the finding, consider the ordinary explanations, ask one specific question, document the file, and handle the decision without creating a second problem.
Read the guideHow to verify an employment verification letter
The income document with the least internal structure, and the one that has to be confirmed at the source. A checklist for doing that carefully.
Read the guideSpot fake bank statements, bank by bank
Verification checklists for Chase, Bank of America, Wells Fargo, Chime, and eight more: genuine-format traits, reconciliation math, and escalation steps.
Browse the bank librarySpot fake pay stubs, provider by provider
Checklists for ADP, Gusto, Workday, QuickBooks Payroll, and more: YTD math, withholding plausibility, and pay-cadence consistency.
Browse the paystub libraryCheck a PDF for tampering signals
Inspect metadata, revision pointers, embedded scripts, attachments, and a SHA-256 fingerprint locally.
Open the toolWhy Ocolta reports review priority—not authenticity
Understand the difference between a file observation, an inference, and an issuer-verified fact.
Explore the evidence modelStart with evidence
Know what deserves a closer look.
Run a private, browser-based integrity scan. Your file never leaves your device.
Scan a document