W-2 fraud

Two digits on a W-2 survive every downstream check most lenders run today

Built for fraud ops at lending, insurance & compliance teams

Mortgage processors, auto-loan underwriters, and tenant-screening agents trust the W-2 the applicant brings as primary income proof. The IRS rarely sees the PDF; the lender does. When the applicant edits Box 1 (Wages, tips, other compensation) before uploading, the wrong figure is the figure the file is built on.

~3 sec
per document
59 checks
forensic layers
From $15
per month
1,500+
docs / month on Growth
Scope

HTPBE? analyzes the structural layer of the PDF file — the layer that records every edit, even invisible ones. We don’t inspect holograms, phone photos, or ID biometrics. If your fraud problem is a digitally altered or fabricated W-2, we’re the most specific tool for it.

When HTPBE? returns INCONCLUSIVE on a W-2, that’s itself a fraud signal in this context — real W-2 exports always come from a US payroll system, never from a desktop tool.

The problem

Modern document fraud is invisible to visual review

A growing class of document fraud opens a genuine PDF, edits a balance, a date, or a beneficiary, and re-saves it. Visually nothing changes — the document passes pixel-level review, layout review, and KYC.

Structural PDF analysis reads the layers rendering engines never expose: revision history, object structure, signature coverage maps. That is where edits leave fingerprints they cannot wipe.

Common tampering patterns

  • Modified balances or totals after export
  • Swapped IBAN or beneficiary on invoices
  • Post-signature edits on contracts
  • Backdated issue and modification dates
  • Fabricated documents from consumer PDF tools

What this looks like

How fake and tampered W-2 PDFs actually look

Three real fraud mechanics we catch at the structural PDF layer.

01

Real W-2 edited after employer issuance

Authentic W-2 comes from a US payroll system (ADP, Paychex, Gusto, QuickBooks Payroll, Workday, Rippling, BambooHR Payroll, Square Payroll, Justworks). The applicant downloads it, opens it in any PDF editor or spreadsheet, edits Box 1 (Wages) or Box 5 (Medicare wages), exports as PDF. The producer field changes from the payroll engine to whichever editor was used.

02

W-2 fabricated in Word from a template

A W-2-shaped PDF authored in Word using the IRS form layout copied from screenshots, populated with a desired employer and Box 1, exported. The producer is Microsoft Word; the structured payroll-system metadata authentic W-2s carry is missing entirely.

03

Box arithmetic broken after edit

When Box 1 (Wages) gets edited up, the dependent boxes — Federal income tax withheld, Social Security wages, Medicare wages, state wages — usually do not get touched. The arithmetic relationship breaks. Combined with structural edit markers, the verdict is unambiguous.

The scale

$11B+
in annual mortgage application fraud exposure (US)
~3 sec
per W-2 via API
No IRS
no IRS Get Transcript call needed — works on the file

Why your existing checks miss this

Day 1 Certainty checks the data with the source. It does not cover every borrower or every doc.

Both layers matter. The PDF the borrower uploaded is what your underwriter opens.

Fannie Mae Day 1 Certainty and Freddie Mac AIM check income data with payroll providers when the borrower’s employer participates and the borrower consents. Coverage is partial — many employers and borrowers fall outside. VOE services call the employer directly, but that step is downstream and slow. Equifax and credit bureaus check identity and credit, not document integrity. HTPBE? catches the W-2 PDF the borrower uploaded at the moment of intake — standalone, no IRS API, no payroll-provider integration required.

Results in under 3 seconds30 to 1,500+ documents/monthFrom $15/mo

What HTPBE? checks

Detection capabilities

Deterministic structural signals. No probabilistic scores, no model training.

Producer signature mismatch

Authentic W-2s carry the producer signature of US payroll software. When the producer is Microsoft Excel, Microsoft Word, LibreOffice, Chrome Headless, or a generic PDF library, the document was edited or fabricated on a desktop — it did not come fresh from the payroll engine.

Incremental update trail

A clean payroll export has one cross-reference table. Re-saves through any editor append a second xref — visible structural evidence of post-issuance editing.

Box arithmetic fraud detection

The relationship between Box 1, Box 2 (Federal income tax withheld), Box 3 (Social Security wages), Box 5 (Medicare wages), and state wages is checked row by row. Edited boxes break the chain unless every dependent field is also adjusted.

Modification timestamp gap

A real W-2 issued by January 31 has CreationDate ≈ ModDate. A months-later modification on a "freshly issued" W-2 is a high-confidence flag for post-export editing.

Font subset divergence across pages

Multi-session edits leave font subset prefix shifts. Single-session legitimate exports have consistent subsets across all pages.

Image-stream artefacts in fabricated W-2s

Fabricated W-2s often paste the IRS form layout from screenshots. Pasted image streams carry different compression characteristics than authentic embedded forms — a structural fingerprint of fabrication.

Share with engineering

Wire this into your intake pipeline in under a day

Two API calls — one POST to submit the PDF, one GET to retrieve the verdict. Forward this page to your engineering team; the full API reference, quotas, and copy-paste examples in cURL, JavaScript, Python, PHP, Go, and Ruby are one click away.

Pricing

Self-serve plans, no sales call

All plans include the same forensic checks. Pick the quota that matches your monthly document volume.

manual

Starter

$15/mo

30 checks/mo

Manual spot-checks and integration testing

most common

Growth

$149/mo

350 checks/mo

Active document processing pipelines

high volume

Pro

$499/mo

1,500 checks/mo

High-volume automation and API integrations

Enterprise (unlimited, on-premise available) see full pricing

API key on signup. Free test environment on every plan. No card required.

Customer Stories

Teams that stopped document fraud

Compliance, finance, and risk teams use HTPBE? to catch manipulated PDFs before they become costly mistakes.

Caught an invoice where the total had been changed by less than a thousand dollars. Without this I would have approved it without a second look.

Sarah M.

AP Manager

United States

We had three applicants in the same week with bank statements that looked completely fine. Two of them were flagged as modified. You simply cannot see this by reading the document — it is in the file structure.

Lars V.

Risk Analyst, Online Lending

Netherlands

Salary slips were coming with altered figures. We identified two problematic files before the placement was finalised.

Priya K.

HR Operations Lead

India

Since we started checking documents this way, we stopped two applications early in the process that would have been very difficult to reverse later.

Julien R.

Fraud Analyst, Fintech

France

Some applicants were sending PDFs that looked authentic but had been edited in ways not visible to the eye. We now ask for checked originals when something is flagged. Already saved us from a few bad decisions.

Marta S.

Compliance Coordinator

Spain

One invoice was caught because there was a mismatch between the document dates and structure. That particular case would have cost us significantly.

Tariq A.

Finance Manager

United Arab Emirates

FAQ

Frequently asked questions

Does HTPBE? work with W-2s from any US payroll provider?

Yes. The analysis is producer-agnostic — it inspects whichever PDF the borrower or applicant submits. Authentic W-2s from ADP, Paychex, Gusto, QuickBooks Payroll, Workday, Rippling, BambooHR Payroll, Square Payroll, Justworks, or smaller in-house systems all carry recognisable producer signatures. Re-saves change those signatures, which HTPBE? flags.

Does this replace Fannie Mae Day 1 Certainty or Freddie Mac AIM?

No. D1C and AIM check income data with the source payroll provider when available. HTPBE? inspects the W-2 PDF the borrower uploaded — covering cases where D1C/AIM is not available, the employer is not in coverage, or the borrower will not consent. Use both: D1C/AIM for the data when available, HTPBE? for the file always.

Can it catch W-2s fabricated entirely from scratch in Word?

Yes. Fabricated W-2s lack the payroll-system producer signature and the structured metadata genuine W-2s carry. The verdict is typically modified or inconclusive with producer-mismatch and missing-metadata flags.

What about W-2s from IRS Get Transcript?

IRS Get Transcript is a separate consent-based path — most lenders cannot use it for borrower fraud detection at scale. HTPBE? inspects the W-2 PDF the borrower uploaded directly, no IRS access required.

What does an INCONCLUSIVE verdict mean for a W-2?

HTPBE? returns INCONCLUSIVE when a W-2 PDF lacks the institutional metadata that genuine US payroll-system exports carry — typically because the file was authored on a desktop with consumer software (Word, Excel, LibreOffice) rather than exported from a payroll engine such as ADP, Paychex, Gusto, Workday, or QuickBooks Payroll. In the W-2 context, INCONCLUSIVE is itself a high-confidence fraud signal: a real W-2 always comes from a payroll system — it would never originate from a desktop tool. Treat INCONCLUSIVE on a W-2 as fraud-positive and route the case to VOE or Fannie Mae Day 1 Certainty fraud detection before underwriting.

Secure your workflow

Create your account — API key on signup, free test environment on every plan.
From $15/mo. No sales call. Cancel any time.