Home/Documents/Investment Statement

Supported document type

Detect tampered and deepfake Investment Statement

An investment statement shows what someone holds, what it is worth, and how it got there, which is why banks ask for one when they need source of wealth or collateral. Altered statements inflate a portfolio value or conjure holdings. Each position is a quantity times a price, the positions sum to the account total, and the period's movements reconcile the opening and closing values, so an edited figure has to be carried through several places.

API slug: investment_statement

What a genuine investment statement contains

A statement identifies the account holder and account number, the custodian or broker, and the period. It shows opening and closing account value, a holdings table with each security, quantity, price, and market value, and a list of transactions, dividends, interest, and fees. Some add asset allocation summaries and realised and unrealised gain figures.

The values interlock. Quantity times price gives each position's value, the positions sum to the portfolio total, and opening value plus contributions plus gains less withdrawals and fees equals closing value. Prices should fall within the range at which the security traded on the statement date. The account number and broker branding should be identical from the first page to the last.

How investment statement forgeries are made

  • Portfolio value inflation

    The headline total is raised, or a large holding is added. The holdings stop summing to the total and the reconciliation from opening value breaks.

  • Invented positions

    A security row is inserted to show assets never held. Its row spacing, font metrics, and place in the sort order differ from the genuine rows.

  • Transaction history editing

    Withdrawals are deleted or contributions added to make the source of funds look plausible. The value roll-forward no longer closes.

  • Borrowed statements

    Another investor's statement is relabelled with a new name and account number. Those replaced fields do not share rendering with the rest of the page.

What TamperCheck checks on an investment statement

TamperCheck runs 200+ forensic checks across three layers and returns a risk score from 0 to 100 with plain-English findings tied to specific regions of the document. These three carry the most weight on this document class.

  • Arithmetic reconciliation

    Stated totals are recomputed from their components, and running or cumulative figures are checked for continuity across periods. A single edited value breaks the chain even when the page still looks right.

  • Table structure integrity

    Inserted and deleted rows leave structural artifacts behind: inconsistent spacing, misaligned columns, and formatting the visible table no longer accounts for.

  • Letterhead, logo, and issuer plausibility

    Issuer branding is checked for resolution and compression consistency against the body text it sits on. A logo lifted from a website carries the signature of its source, not of the document.

  • And many more checks

    The three above are the layers that carry the most weight on an investment statement. Every upload runs the full suite of 200+ checks regardless of document class, spanning file structure and metadata, pixel-level forensics, font and text rendering, optical and print characteristics, provenance signals, AI-generation signatures, and many more checks.

Who verifies an investment statement, and why

Banks, wealth managers, lenders, and compliance teams. In each case the document is being used to unlock money, access, or a legal status, which is exactly what makes it worth forging.

How to verify an investment statement in 4 steps

  1. Check the fields against each other

    Read portfolio value, holdings and quantities, and account number together rather than one at a time. Forgers typically change one value and leave the rest of the document describing the original.

  2. Inspect the file metadata

    Open the document properties and look at the producer, creation date, and modification date. A document produced by a consumer PDF editor, or created long after the date printed on its face, is worth a closer look.

  3. Ask for a second document

    Request a corroborating document from the same issuer or an adjacent period. Forgery effort concentrates on one file, so inconsistencies surface as soon as there are two to compare.

  4. Run a forensic check

    Manual review catches obvious edits but not field-level pixel manipulation or synthetic generation. TamperCheck runs 200+ forensic checks on an investment statement and returns a risk score from 0 to 100 in about a minute, at $0.50 per document.

Frequently asked questions

How do banks verify a brokerage statement?

They check that holdings times prices sum to the total, that the value roll-forward closes, and that the account number and branding are consistent. For material cases they ask the broker to confirm directly. Forensic review of the PDF adds a test for edited figures.

Can an investment statement be edited?

Yes, as any PDF can. The difficulty is keeping the positions, totals, and roll-forward consistent, and reproducing the broker's exact font metrics and compression for every changed number.

What is an investment statement used for?

Banks and compliance teams use it to establish source of wealth and available assets, lenders to assess collateral, and immigration and property files to show financial capacity. In each case the portfolio value is the figure being relied on.

Is a demat statement an investment statement?

Yes, in the sense used here. A demat or depository statement lists securities held in electronic form, and a brokerage or portfolio statement does the same with valuations. All are checked with the same arithmetic on quantities, prices, and totals.

TamperCheck analyses investment statement uploads with a hybrid forensic and AI pipeline tuned for this document class. Upload endpoints accept PDF and common image formats; class is inferred automatically. See the API documentation for authentication, async jobs, and webhooks.

Related document types

All supported document types