PDF security blog

PDF Fraud in Real Estate: Which Documents to Check in a Property Deal

HTPBE Team··12 min read
PDF Fraud in Real Estate: Which Documents to Check in a Property Deal

This article is a snapshot – content was accurate as of November 2025 (code examples tested against the API as of October 2026). The product evolves actively; specific counts, examples, and detection rules may have changed since publication – see the changelog for the current state.

A property deal is a chain of PDFs. A buyer sends proof of funds to the agent. The lender collects payslips and bank statements. The title company circulates closing documents. Near the end, wire instructions arrive by email. Each file is read by someone who has to decide something – make an offer, approve a loan, release money – and almost none of them is ever opened to see how it was built.

That is the gap this article is about. It is written for the agent, escrow officer or lender who owns one stage of a deal and needs to know what the other stages do. It is a map of the deal, not a deep dive on one fraud: which documents carry weight, where each one enters your process, what a structural file check can tell you about it, and what it cannot. Where a document has its own full treatment, we link to it.

Which PDFs Matter, and Who Relies on Them

DocumentWho relies on itWhat it is used to decide
Proof of funds, brokerage or bank statementListing agent, seller, escrowWhether to take an offer seriously
Payslips, W-2s, tax documentsLender, underwriterIncome for the loan
Bank statements, gift letters, asset lettersLender, underwriterDown payment and reserves
Rental application documentsProperty manager, landlordWhether to approve a tenant
Purchase agreement, addenda, payoff lettersAgents, title, escrowWhat was agreed and what is owed
Wire instructionsBuyer, escrow, titleWhere the money goes

Two things separate these files. The first group is supplied by the applicant – the person has every reason to improve it and can open it in an editor before sending. The second group is issued by a third party and passed along by email – the risk there is someone in the middle changing it in transit. The same file check applies to both, but the sensible response differs, and so does what the check can promise.

The Deal Timeline: Who Checks What, and When

The same transaction touches different people on different days. This is an illustrative timeline for a financed purchase; the dates are relative and your own contract dates will differ.

StageDocument that arrivesWho relies on itCheck to runDecision it protects
OfferProof of funds or a brokerage statementListing agent, sellerFile check, then a request for a statement direct from the institution if it is a cash offerWhether to treat the offer as a cash offer
Contract to underwritingPayslips, W-2s, bank statements, gift lettersLender, underwriterFile check at intake, then the lender’s own income and asset verificationWhether the file goes to underwriting
UnderwritingUpdated statements, explanation lettersUnderwriterA new check for every replaced documentThe loan decision
Clear to closePayoff letters, signed addendaTitle, escrowFile check, and confirmation of the payoff amount with the payee’s known contactThe amount disbursed
Closing weekWire instructionsBuyer, escrowFile check, then a callback on a number already in the fileWhere the funds go
After closingRecorded documentsTitleCompare with the recorded instrumentWho holds title

The rule that holds across the table: every document that replaces an earlier one gets its own check. A substitution late in the process is exactly where a document is least likely to be looked at again.

A scenario: the payoff letter two days before closing

An illustrative case. Two days before closing, the escrow officer receives an updated payoff letter by email. The amount differs by a few hundred dollars from the first, and the wiring details have changed. The officer runs the file check, which returns modified, and does not wire. A call to the lender’s payoff department, on the number printed in the original loan documents, finds that no updated letter was issued. The closing is delayed by a day and the genuine letter arrives. The file check pointed at the document; the callback settled it. Had the check returned intact, the callback would still have been made, because the account details changed.

A closing-week checklist for the escrow officer

  • Every instruction that changes where money goes is confirmed by phone, on a number from the engagement letter or an earlier verified document.
  • Every replaced document has its own check ID on the file.
  • Anything modified pauses the step and goes to a named person.
  • Anything inconclusive that claims an institutional origin is requested again from the issuer.
  • The buyer is told in advance that instructions will not change by email, and how a real change would reach them.

Applicant-Supplied Documents: Proof of Funds, Income and Assets

This is where edited files most often enter a deal. A cash buyer shows a brokerage statement with a bigger balance. A borrower adds a deposit to a bank statement so it covers reserves. A tenant lifts the income on a payslip. The edit is small, done in a desktop editor or a spreadsheet, and the result looks like any other statement.

Reviewers do what they can: they check that the arithmetic holds, that large deposits are sourced, that the employer exists. Those are good controls and they test whether the figures are plausible. They do not test whether the file is the one the bank or payroll provider produced. The detail is covered in the pieces below:

If you work in one of these lanes, the use-case pages show the same check as a workflow: mortgage, lending and tenant screening.

Third-Party Documents Passed Along by Email

Purchase agreements, addenda, payoff letters, closing documents and wire instructions are produced by a counterparty and travel through several inboxes. If one of those mailboxes is compromised, an attacker can take a genuine document, change a field, and forward it on. The recipient sees the right letterhead, the right file number and the right names.

Fabricated documents are a different thing. A letter built from scratch on a look-alike domain was never edited, so there is no edit to find. We come back to that in the limits section, because it decides how far you can lean on a file check.

Deed and title fraud follows the same pattern: a property description, an owner name or a notarial block changed in a copy that is then circulated or filed. A file check can show that a circulated copy was edited after it was made, which a visual read cannot. It does not replace the recorded instrument, the title search or owner notification, which stay the authority on who holds title. The MOST Policy overview of title fraud is a useful background read.

Wire Instructions: A File Check Plus a Callback

Wire instructions are the highest-value file in the deal, because one swapped account number sends the closing funds somewhere else, and wires are hard to pull back. The FBI tracks this under business email compromise: in 2022 its Internet Crime Complaint Center recorded 21,832 BEC complaints with adjusted losses above $2.7 billion. That figure covers all BEC, not closings alone, so read it as the scale of the surrounding problem rather than a count of forged PDFs. State regulators publish the same warning in plain terms, for example the California DRE.

Two controls belong together, and neither replaces the other:

  1. A file check on the instruction PDF. If a genuine instruction was edited after the title company issued it, the file can show that. This catches the intercepted-and-altered case before anyone dials a number.
  2. A callback to a number you already had. Confirm the bank, the account and the amount by phone, using a number from the engagement letter or an earlier document, never from the email. Read the account digits back.

A file check cannot verify an account number. An unmodified instruction PDF does not tell you the account belongs to the title company; it only tells you the file shows no sign of being changed since it was made. If an attacker sent a freshly built document, the file can show nothing and the account still be wrong. That is why the callback stays, and why a passing file check never shortens it. For the full closing-table treatment, including how callbacks themselves get defeated, see wire fraud in real estate closings.

Where the Check Fits in Agent, Escrow and Lender Workflows

Run the check at the point where a document enters your process from outside, before anyone acts on it.

  • Listing agents and brokerages: proof of funds, before an offer is treated as a cash offer. One check per file at intake.
  • Lenders and underwriters: payslips, bank statements, tax documents and gift or asset letters at file intake, ahead of the asset and income review.
  • Title and escrow: inbound wire instructions and payoff letters, and any document that supports a change to disbursement details. Returned signing packages before disbursement.
  • Property managers: application documents at intake, before approval.

HTPBE? is a two-step API call: post the PDF’s URL to /v1/analyze, then read /v1/result/{id}. The result carries a status, the named modification_markers that drove it, and a modification_confidence of certain, high or none. There is no numeric risk score. Store the check id and the full response against the file number, so there is a record of what was checked and when. The request and response reference is on the API page, and a test key returns deterministic synthetic results so you can build the integration before a live document touches it. Volume plans for agencies, lenders and closing platforms are on the pricing page.

What to Do With Each Verdict

The usage_caution block in the response names the action to take, so you can route on it instead of on the status alone.

intact – no structural sign of modification. Proceed with your normal process. It is not an endorsement of the content: the figures still need your usual review, and a wire instruction still needs the callback.

modified – the file was changed after it was created. Pause the step that depended on it and send the case to a person. In a wire scenario that means do not send money; reach the issuer on a known number and ask for a fresh copy. In underwriting it means a human reviewer looks at the file and, where needed, asks the applicant for the document directly from the institution.

inconclusive – the file does not carry enough history to confirm integrity either way. Files made in everyday desktop or consumer software can be produced by anyone, so there is no original to compare against, and a scan or print-to-PDF cannot be cleared structurally. When a document claims to come from a bank or an employer but carries that kind of origin, it is a reason to go back to the issuer, not a finding against the sender. Request a fresh copy from the issuer where one exists; where it does not, confirm by other means, such as the signing agent or the originals. It is not proof of anything against the person who sent it.

In every branch, a structural result describes the file, not the sender. A compromised mailbox means the person who forwarded the document is frequently a victim as well. The API says so in the payload: do not use a verdict as the sole basis for an automatic adverse decision against a buyer, seller, borrower or tenant.

Honest Limits

A file check is one layer, and it is narrow on purpose.

  • It checks the file, not the content. It does not read the figures and decide whether a balance is true, an employer is real or a signature belongs to the signer.
  • It is not designed to prove a newly built document genuine. A document fabricated from scratch has no edit to find; do not read a lack of findings as clearance.
  • It does not verify identity or accounts. It cannot tell you who sent a file or that a routing and account number belong to the named company.
  • It does not cover every document equally. Scans, photos and print-to-PDF files often return inconclusive rather than intact.
  • It does not replace the human controls. Callbacks, identity checks, sourcing of large deposits and title insurance all stay.

What it removes is one specific failure: an edited document passing as untouched because nobody could see inside it.

Where to Start

Pick the document that moves the most money in your process, usually proof of funds at offer stage, income and asset files at underwriting, or wire instructions at closing. Run it through the check at intake, route modified and inconclusive to a named person, and keep the callback exactly as it is. If you process these documents at volume, the same check runs through the PDF tamper detection API.

Share this article

Found this article helpful? Share it with others to spread knowledge about PDF security and fraud detection.

https://htpbe.tech/blog/pdf-fraud-real-estate-protecting-transactions

Secure your workflow

Create your account – check PDFs on the web or with an API key, both ready on signup.
No sales call. Cancel any time.