logo
W-2 fraud

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

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
35 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.

How it looks

One REST call, one deterministic verdict

Upload the PDF. The API returns INTACT, MODIFIED, or INCONCLUSIVE with named markers — in about three seconds.

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 verifies 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 verify 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 verify 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
How it works

Five forensic layers, one deterministic verdict

Every PDF we receive passes through the same structural pipeline — no model training, no thresholds to tune.

01

Metadata analysis

Creation and modification timestamps, producer and creator fields, XMP metadata — the first layer exposes basic tampering.

02

File structure

Xref tables, trailer chain, incremental updates. Any edit after export leaves a structural fingerprint here.

03

Digital signatures

Signature chain integrity and post-signature modifications produce deterministic markers. Certainty-level signal.

04

Content integrity

Fonts, objects, embedded content, page assembly. Multi-session edits and inserted objects are visible at this layer.

05

Verdict with markers

Deterministic output: INTACT / MODIFIED / INCONCLUSIVE, with named markers for every finding — suitable for audit trail.

Document types

W-2 and adjacent US income-proof PDFs we check

Every type listed below is analyzed at the structural file layer — not the rendered image.

W-2 PDF (Wage and Tax Statement)1099 PDF (NEC, MISC, INT, DIV, K, R)Pay stub PDFTax return 1040 PDFAsset letter PDFBank statement PDF (salary credits)Employment verification letter PDF
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 verification

The relationship between Box 1, Box 2 (Federal income tax withheld), Box 3 (Social Security wages), Box 5 (Medicare wages), and state wages is verified 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.

Integrate in minutes

Two HTTP calls to verify any W-2

Buyers can skip this section — developers, the integration is two HTTP calls.

Step 1 — submit the PDF

curl -X POST https://api.htpbe.tech/v1/analyze \
  -H "Authorization: Bearer $HTPBE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://your-storage/borrower-w2-2024.pdf"}'

Step 2 — read the verdict

{
  "id": "w1u2s3a4-5w6t-7w8o-9p0d-f1g2h3i4j5k6",
  "status": "modified",
  "modification_confidence": "high",
  "modification_markers": [
    "Spreadsheet producer detected (Microsoft Excel)",
    "Two cross-reference tables — incremental update",
    "Modification date 7 months after creation date"
  ],
  "producer": "Microsoft Excel",
  "creator": "ADP Workforce Now (original)",
  "creation_date": 1706659200,
  "modification_date": 1726272000,
  "has_digital_signature": false,
  "xref_count": 2,
  "has_incremental_updates": true
}

Original came from ADP Workforce Now in late January (the IRS deadline). Then seven months later it was opened in Microsoft Excel and re-saved — adding a second xref table. Verdict: modified at high confidence. The borrower edited a real W-2 after employer issuance.

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 verified 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

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.
No. D1C and AIM verify 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.
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.
IRS Get Transcript is a separate consent-based path — most lenders cannot use it for borrower verification at scale. htpbe? inspects the W-2 PDF the borrower uploaded directly, no IRS access required.
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 verification 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.