Home/Documents/Pension Statement

Supported document type

Detect tampered and deepfake Pension Statement

A pension statement is the retired applicant's payslip, and it does the same job with a different author: a scheme or provider rather than an employer. Consulates and lenders use it to test whether a fixed monthly income clears a means threshold, so the figure that gets inflated is the periodic payment. Unlike a payslip, the payments are meant to be identical month after month, which makes an inserted or uplifted row conspicuous. TamperCheck checks each row for $0.50 per document, no minimum.

API slug: pension_statement

What a genuine pension statement contains

A pension statement identifies the pensioner by name, address, and a pension reference or member number rather than a payroll number. It states the scheme name and the paying office, the statement period, and the pension in payment: gross periodic amount, tax deducted, net paid, and the account it was credited to, usually masked. It will also carry the annual entitlement, the date the pension commenced, any commuted lump sum already taken, cost-of-living increases applied during the period, survivor entitlements, and the seal or signature of the paying authority.

A pension in payment is meant to be monotonous, and that is its verification value. The periodic amounts repeat unchanged between increases, so the rows in the payment table should be identical until an indexation date, where they step once and then hold. Gross less tax equals net on every row, twelve monthly payments reconcile to the annual entitlement, and each payment date should appear as a matching credit in the pensioner's bank statement. An irregular amount or an out-of-cycle date stands out in a way it never would on a payslip.

How pension statement forgeries are made

  • Periodic amount inflation

    The monthly pension is raised so a fixed income clears a consular means threshold or a lender's affordability floor. Because the same figure repeats down the table, editing it convincingly means rewriting every row, and rows rewritten one at a time seldom match each other pixel for pixel.

  • Beneficiary substitution

    A genuine statement belonging to a relative or acquaintance has the pensioner's name and reference replaced, so one real pension supports several applications. The identity block is a small region in an otherwise untouched document, and the payment account will not belong to the applicant presenting it.

  • Statement period extension

    The period covered is stretched forward so a historic statement reads as current, sometimes with extra payment rows appended beyond the last real one. The appended rows have to be invented, and their dates often fall on a cycle the scheme does not actually pay on.

  • Scheme letterhead fabrication

    A statement is produced for a fund with a plausible name, or a real scheme's branding is rebuilt from its public documents. Provider letterheads and seals tend to be reproduced more crudely than bank or government ones, because they are seen less often and therefore checked less closely.

  • Entitlement and lump sum inflation

    The annual entitlement or a commuted lump sum is raised to show capital that was never received. This contradicts the periodic payments printed alongside it, since twelve months of the pension shown no longer add up to the annual figure being claimed.

  • Statements built for means-test files

    Complete statements are produced to satisfy financial-means requirements, with payment tables that reconcile from the first row. Their weakness is corroboration: the payments they describe do not appear as credits in the applicant's bank statement, and the scheme's own formatting is approximated rather than reproduced.

What TamperCheck checks on a pension 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.

  • Signature forgery analysis

    Signature regions are assessed for ink consistency and for how the stroke sits on the page, which distinguishes a genuine pen stroke from a pasted image of one.

  • And many more checks

    The three above are the layers that carry the most weight on a pension 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 a pension statement, and why

Consulates and lenders assessing financial means for retired applicants. 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 a pension statement in 4 steps

  1. Check the fields against each other

    Read monthly payment amount, beneficiary name, and statement period 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 a pension statement and returns a risk score from 0 to 100 in about a minute, at $0.50 per document.

Frequently asked questions

How do consulates verify pension statements?

Consulates match the statement against the applicant's bank statement, expecting each pension payment to appear as a credit of the same amount on the same date from the named scheme. They check that the periodic amounts reconcile to the annual entitlement, that the pension reference follows the scheme's format, and they may ask the paying office to confirm the pension directly.

Can a pension statement be faked for a visa?

Yes, and it is a common submission in financial-means files for retirement and long-stay visas, because a pension is often the applicant's entire income and the threshold is a fixed monthly figure. The forgeries are usually inflated periodic amounts on a genuine statement, or a relative's statement with the name changed. Both fail when the payments are compared against bank credits.

What should a genuine pension statement show?

It should show the scheme or provider name, a pension reference or member number, the statement period, and a table of payments giving the gross amount, tax deducted, net paid, and the credited account for each one. The amounts should repeat unchanged between indexation dates, and the total should reconcile with the annual entitlement printed on the same statement.

How is a pension statement checked against a bank statement?

Take each payment date and amount from the pension table and find the matching credit in the bank statement for the same period. A genuine pension arrives on a predictable cycle, in the net amount shown, with the scheme named in the credit narrative. Missing credits, different amounts, or a payment account that is not the applicant's are the discrepancies that matter.

TamperCheck analyses pension 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