---
title: "Sample report: an edited bank statement | Trustable"
url: "https://trustable.ai/sample-report"
description: "What Trustable finds in a bank statement with an edited balance: each finding, where it is, how it was changed and how strong it is. A synthetic example."
---

Sample report

# What a Trustable report looks like.

A synthetic bank statement with an edited balance, and the three findings a Trustable report shows: where each one is, how the file was changed, how strong the signal is.

[Download the PDF](https://trustable.ai/assets/sample-report.97419810fb5d.pdf) [Book a demo](https://cal.com/scamai/20min?utm_source=trustable.ai&utm_medium=website&utm_campaign=book_demo&utm_content=sample-report)

statement-sep-2026.pdf · PDF · 1 page · Needs review · 3 findings · Illustrative example · synthetic document

Example Bank Statement · Sep 1–30, 2026

J. Example · Checking ···· 4821

Transactions on the synthetic statement

| Date | Description | Amount | Balance |
| --- | --- | --- | --- |
| Sep 1 | Opening balance |  | 3,418.60 |
| Sep 5 | Payroll · Lakeside Logistics | +2,940.00 | 6,358.60 |
| Sep 8 | Rent · autopay | −1,850.00 | 4,508.60 |
| Sep 12 | Card purchases | −1,275.33 | 3,233.27 |
| Sep 19 | Payroll · Lakeside Logistics | +2,940.00 | 6,173.27 |
| Sep 30 | Closing balance |  | 14,173.27 |

- Closing balance re-rendered. Digits drawn over the original. The transactions add up to 6,173.27, not 14,173.27. Strength: Strong
- Deposit line overlaid. The Sep 19 text layer doesn’t match the rendered page. Font and spacing differ from the rest of the column. Strength: Moderate
- Metadata gap. Last saved by a PDF editor three days after the statement date. Not proof on its own. Strength: Moderate

Each finding says where it is, how the file was changed and how strong the signal is. Your team decides.

In every report

## Four things, every time. On every file you send.

### Result

One line, with the reason.

### Findings

Where, how it was changed, how strong.

### Marks on the page

Each finding drawn where it sits.

### File facts

Creator, dates and edits in the metadata.

Formats

## JSON from the API. A report in the app.

Send a file to the API and get JSON back: a one-line verdict with its reason, then each finding with where it is, how the file was changed and how strong it is. Or review the marked-up page in the Trustable web app.

FAQ

## About this sample.

### Is the sample a real customer file?

No. Example Bank, J. Example and Lakeside Logistics are invented, and the statement was made for this page. Only synthetic documents are ever shown in public. The findings are written the way Trustable reports them: where, how the file was changed, and how strong the signal is.

### What do Strong and Moderate mean?

Strength says how clearly a signal points to an edit. A strong finding usually deserves a request for the original document or a check with the source; a moderate one deserves a closer look alongside the rest of the file. Neither is proof of fraud on its own, and no AI is 100% accurate.

### How does a report reach my team?

As JSON from the API, which returns a one-line verdict with its reason and the findings, each with where it is, how the file was changed and how strong the signal is; or as the marked-up page in the Trustable web app at demo.trustable.ai. Routing results into a review queue is in development.

### Can I see it on my own file?

Yes. The demo itself runs on a sample file. Once data handling is agreed in writing, we run the same checks on a file of yours and walk through every finding with your team.

Your file next

## See it on your own file.

Book a 20-minute demo. We agree on data handling before you share anything.

[Book a demo](https://cal.com/scamai/20min?utm_source=trustable.ai&utm_medium=website&utm_campaign=book_demo&utm_content=sample-report)