Supported document type
Detect tampered and deepfake Settlement Statement
A settlement statement, the HUD-1 or its ALTA successor, is the ledger of a property closing: what the buyer owes, what the seller receives, and where every dollar went. Lenders and agents treat it as the definitive record. Editing one means rebalancing two columns of charges, credits, and payoffs, so a change to any single line that is not carried through both sides leaves the statement out of balance.
API slug: settlement_statement
What a genuine settlement statement contains
The statement has a borrower or buyer column and a seller column. It lists the contract price and deposits, loan proceeds, payoffs of existing liens, commissions, title and settlement fees, recording and transfer taxes, prorations for taxes and utilities, and ends with cash due from the buyer and cash due to the seller. The settlement agent, file number, and date appear on the form, with signature lines for the parties.
The columns balance. Total charges less credits gives the cash figure for each party, and the seller's proceeds are the price less payoffs, fees, and prorations. Payoff lines should agree with the lenders' payoff letters, commissions with the listing agreement, and the loan amount with the closing disclosure. Signatures from the parties and the agent close the document and can be checked against those elsewhere.
How settlement statement forgeries are made
Cash-to-close changes
The cash the buyer brought is reduced, or the seller's proceeds inflated. The column no longer foots, and the changed digits usually differ from their neighbours in rendering.
Payoff line edits
An existing lien's payoff is lowered or removed so the sale appears to clear more equity. It disagrees with the payoff letter, and the remaining lines fail to sum.
Commission and fee shifts
Fees are moved between parties or disguised as credits to alter who paid what. The offset has to appear on both columns, and the edit is often carried through only one.
Signature page grafting
A signed last page from another closing is attached to an altered statement. The paging, file number, and agent details conflict with the pages in front of it.
What TamperCheck checks on a settlement 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 settlement 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 settlement statement, and why
Lenders, real-estate agents, closing attorneys, and title underwriters. 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 settlement statement in 4 steps
Check the fields against each other
Read cash to or from each party, payoff lines, and commissions and fees 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 settlement statement and returns a risk score from 0 to 100 in about a minute, at $0.50 per document.
Frequently asked questions
How do I know if a settlement statement was edited?
Check that the buyer and seller columns balance, that payoffs match the lenders' letters, and that the loan amount agrees with the closing disclosure. Then examine the PDF for figures inserted after generation. Any one of those tests can expose an edit.
What is faked on a HUD-1?
The cash the buyer brought, the seller's net proceeds, payoff amounts, and fee lines are the usual targets. They matter because lenders and tax authorities read the bottom lines to judge equity, source of funds, and the price actually paid.
Is a settlement statement the same as a closing disclosure?
Not exactly. The closing disclosure is the borrower's loan-focused form. The settlement statement, whether HUD-1 or ALTA, is the closing agent's full ledger covering both buyer and seller. They should agree on the loan amount and the buyer's costs.
Who prepares the settlement statement?
The settlement or escrow agent, which is usually a title company or closing attorney. Because it is prepared by a third party, the agent's name, file number, and licence should be consistent with the rest of the transaction file.
TamperCheck analyses settlement 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.