Altered Statements
Every statement tested for edits before it is underwritten, each finding marked on the page.
Why it matters
Edited PDFs and fabricated statements reach every funder’s queue; reviewing by eye misses balances that don’t add up and deposits copied from another month.
How the solution handles it
Agents test each statement four ways: the file itself (metadata, fonts, layers), the layout against the bank’s real template, the arithmetic of every running balance, and history against earlier submissions. Each finding is marked on the page in plain words. A fraud analyst clears, verifies with the bank or declines.
How a statement is tested
Five agents test every statement’s file, layout, arithmetic and history and mark each finding; a fraud analyst clears, verifies or declines.
What it reads, and what it hands back.
What goes in
- Bank statement PDFs and scans
- Bank layout library
- Bank-data feed or Account Aggregator pull
- Prior submissions for the merchant
What comes out
- Tamper report with marked pages
- Running-balance recompute
- Verify-with-bank request
- Fraud case for review
Who uses it
The difference, in numbers.
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
on every statement
“Target” = design goal, measured in the live solution · “Typical” = MoneyThumb and deBanked funder fraud survey, Sept 2025 · by-eye time estimated · a finding is a flag for a person, never an automatic decline
5 specialist agents. One person decides.
More in this division.
Every ISO submission read, screened and routed within minutes of arriving, while the merchant is still shopping.
Statement UnderwritingSix months of statements scrubbed to true revenue and daily balances in minutes, every number tied to its line.
Stacking DetectionEvery existing advance found before you fund, with its daily debit and the line that proves it.
Build this
for your team.
We’ll show Altered Statements running on your own documents.