Fake 1099 Detection – Catch Tampered Self-Employment PDFs
A 1099 is the only income proof a self-employed borrower has – and the easiest one to inflate. Self-employed borrowers face stricter income-documentation standards than W-2 employees. Many lenders treat the 1099 PDF as the primary document of record. When the contractor edits the figure on Box 1 (NEC) or Box 7 (Nonemployee compensation, MISC) before uploading, the wrong number anchors the entire underwriting decision.
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 1099, we’re the most specific tool for it.
When HTPBE? returns INCONCLUSIVE on a 1099, that is a reason to escalate to manual review, not proof of fraud – it means HTPBE? cannot confirm the file as an untouched original.
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 1099 PDFs actually look
Three real fraud mechanics we catch at the structural PDF layer.
Real 1099 edited after issuance
The contractor downloads the real 1099 from the payer’s accounting software or platform, opens it in any PDF editor or spreadsheet, edits Box 1 (NEC) or Box 7 (MISC), exports as PDF. The edit typically leaves traces of the editor in the file.
1099 fabricated in Word from a template
A 1099-shaped PDF authored in Word using the IRS form layout copied from screenshots, populated with desired payer and amount, exported. However closely it copies the IRS form, the file does not come back INTACT: with nothing indicating later editing it returns INCONCLUSIVE and should go to manual review; with evidence of editing or fabrication, MODIFIED.
Multiple ‘monthly’ 1099s aggregated to claim higher annual
A contractor stitches together ‘1099s’ from several fake clients to claim higher aggregate income than reality. The dates the API returns for each file show that ‘five different payers’ all produced their PDFs in a single sitting.
The scale
Why your existing checks miss this
IRS Get Transcript checks via consent. Most lenders cannot use it at scale.
Both layers matter. The PDF the contractor uploaded is what your underwriter opens.
IRS Get Transcript can check 1099 figures with the IRS – but only with the borrower’s consent and one-by-one transcript pulls, which most lenders cannot run at scale. Bank-statement parsing platforms (Plaid, Finicity, MX) check deposit history when the contractor connects their bank account – contractors who edited the 1099 rarely do. HTPBE? catches the 1099 PDF the contractor uploaded at the moment of intake – standalone, no IRS API, no consent required.
What HTPBE? checks
Detection capabilities
Deterministic structural signals. No probabilistic scores, no model training.
Hand-built 1099s aren’t cleared
A 1099 saved as PDF from Word, Excel or LibreOffice does not come back INTACT, however closely it copies the IRS form or a payer’s layout. With no sign of later editing it returns INCONCLUSIVE for manual review; with evidence of editing or fabrication, MODIFIED.
Post-issuance edit detection
Editing a 1099 after issuance – in a PDF editor, or by rebuilding it in other software – leaves structural evidence behind. HTPBE? flags it as MODIFIED.
Batch-produced sets
When multiple 1099s arrive together claiming different payers, the API returns each file’s own dates. Real 1099 issuance from different payers happens at different times; a set produced in one sitting stands out.
Character overlay on the original
Changing a figure on an existing form leaves a structural trace. HTPBE? flags it without reading the boxes – it never looks at what the numbers say.
Dates that disagree
A ‘freshly issued’ 1099 whose own dates show it was changed months later is a high-confidence flag for post-issuance editing.
Reworked documents
HTPBE? detects documents reworked after their original creation and documents assembled from pages of different sources.
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.
manualStarter
30 credits/mo
Manual spot-checks and integration testing
most commonGrowth
350 credits/mo
Active document processing pipelines
high volumePro
1,500 credits/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 1099s from any platform issuer?
Can it catch a contractor stitching together multiple fake 1099s?
Does this replace IRS Get Transcript or income-data checks?
What about 1099s from self-published platforms (Substack, Patreon, Etsy)?
modified when the file carries evidence of the edit. One rebuilt in Word, Excel or LibreOffice and exported directly, with nothing indicating later editing, comes back inconclusive – not intact – and should go to manual review.What does an INCONCLUSIVE verdict mean for a 1099?
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.