Supported document type
Detect tampered and deepfake Mortgage Document
Mortgage document fraud runs in two directions. An applicant alters a statement or an offer letter to change what an underwriter sees: a smaller outstanding balance, a rate that makes affordability work, a co-applicant added or removed. Elsewhere a fabricated charge document is used to show a lender's security that does not exist, or to hide one that does. Both are edits to paperwork that reaches the file as a PDF from the borrower rather than from the institution that issued it.
API slug: mortgage_document
Last updated:
What a genuine mortgage document contains
A mortgage file is a set of related documents rather than a single page. The sanction or offer letter states the amount sanctioned, the rate and whether it is fixed or floating, the tenure in months, the fees, and the conditions attached to drawdown. The agreement and the charge document name the borrower and any co-applicants with their identity references, describe the secured property, and record the lender's charge over it. Statements show the outstanding principal, the instalment, the interest applied, and the arrears position at a stated date.
The arithmetic of a loan is closed, which is what makes the file hard to edit convincingly. Principal, rate, and tenure determine the instalment exactly, so changing one without recomputing the others leaves a schedule that no amortisation produces. Each statement row carries the interest charged and the principal repaid, and the balance has to walk forward row by row. The sanction reference ties the agreement, the charge, and the statements to one loan account, so a mismatch anywhere in that chain is a document that does not belong to the file.
How mortgage document forgeries are made
Statement balance edits
The outstanding principal or the arrears line is rewritten so an existing loan looks smaller or cleaner than it is, improving the applicant's debt position. A statement is a running balance, so one altered figure has to hold across every row beneath it, and the edited digits carry a different rendering history from their column.
Rate and tenure changes
The interest rate or the term is changed so the monthly commitment fits an affordability calculation. Principal, rate, and tenure produce exactly one instalment figure, and an edit that leaves the instalment untouched describes a loan that could not have been written on those terms.
Borrower and co-applicant edits
Names and identity references are altered so a loan sits with a different party, or a co-applicant is added to bring income into the assessment. This edit crosses documents, so it is caught by comparing the same field across the offer letter, the agreement, and the statements rather than by reading any one of them.
Offer letter fabrication
A whole sanction letter is produced on a lender's letterhead, with a reference number in the right format and terms that suit the applicant. The branding is copied from a real letter and resampled to fit, which leaves it on a different compression footing from the text set around it.
Signature and stamp transplant
An authorised signatory's signature and the lender's stamp are lifted from a genuine document and placed on the fabricated one, often slightly rescaled. The transplanted region carries the tone and sharpness of the file it came from, and the stamp prints with an even ink coverage that a real impression never has.
Regenerated repayment schedules
Schedules are recalculated in a spreadsheet and re-rendered so every row ties out to the altered terms. Internal arithmetic then passes completely, and the discrepancy moves to the artefact: text layers that were never printed or scanned, and production metadata unlike anything a bank issues.
What TamperCheck checks on a mortgage document
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.
Stamp authenticity and placement
Stamps are assessed for whether the ink was impressed onto the page or printed as part of it, and for whether the impression was placed digitally after the fact.
Reference and document number checks
Document, account, and reference numbers are checked for issuer format conformance and against every other place the same value appears on the page.
And many more checks
The three above are the layers that carry the most weight on a mortgage document. 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 mortgage document, and why
Mortgage underwriters and conveyancers reviewing loan files. 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 mortgage document in 4 steps
Check the fields against each other
Read principal and interest rate, borrower details, and repayment schedule together rather than one at a time. Forgers typically change one value and leave the rest of the document describing the original.
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.
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.
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 mortgage document and returns a risk score from 0 to 100 within seconds, at $0.50 per document.
Frequently asked questions
How do lenders detect mortgage document fraud?
Lenders detect it by reconciling the file against itself before examining any single document. The sanction reference should appear on the agreement and the statements, the instalment should follow from the principal, rate, and tenure, and the borrower's name should be identical on every page. Forensic analysis then covers what reconciliation cannot: fields edited after issue, and letterheads pasted in from another file.
What documents are faked in mortgage applications?
Payslips, bank statements, and tax documents are faked most often, because income is what the decision turns on. On the property side of the file, the documents altered are statements from an existing lender, offer letters, and title or valuation evidence. Anything the applicant supplies as a PDF, rather than the lender obtaining it directly, is the part of the file worth checking forensically.
Can an edited mortgage statement be detected?
Yes. A statement is a closed sequence, so an edited balance either breaks the row-by-row arithmetic or forces every following row to be rewritten, and rewritten text does not share the compression and font rendering of the original page. TamperCheck runs 200+ forensic checks on the file, scores it from 0 to 100, and names the field that moved.
What is the fastest check on a mortgage offer letter?
Compare the instalment figure against the sanctioned amount, rate, and tenure printed on the same letter, because those four values cannot disagree on a genuine offer. Then check the reference format against other letters from that lender and confirm the letterhead is not a resampled image. Where the letter arrives as a PDF from the applicant, a forensic check settles it within seconds.
TamperCheck analyses mortgage document 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 & MCP documentation for authentication, async jobs, and webhooks.