Fake Employment Letter Detection – Catch Forged Letters
An employment letter is the cheapest piece of paper a borrower or tenant can fabricate – and the one your underwriting team trusts. Mortgage and personal-loan underwriters, leasing agents, immigration officers, and HR onboarding teams all accept employment letters as proof. Fraud rings know it. They author letters in Microsoft Word using a real employer’s template, sign an HR Manager’s name, export to PDF. Visual review passes; structural analysis does not.
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 fabricated or tampered employment letter, we’re the most specific tool for it.
Employment letters are mixed-origin: large employers issue them through HRMS, voluntary-VOE platforms (The Work Number), or DocuSign workflows; small employers and HR managers legitimately export from Word. When HTPBE? returns INCONCLUSIVE on an employment letter, 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 employment letters actually look
Three real fraud mechanics we catch at the structural PDF layer.
Letter authored in Microsoft Word from scratch
No employer involved. The applicant downloads the company logo from LinkedIn, drops it into Word, types the letter with an inflated salary or invented role, signs an HR Manager’s name they invented, exports to PDF. However closely it copies the employer’s letterhead, 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.
Real letter with edited salary, dates, or role
Applicant has a genuine letter but the salary or tenure doesn’t support the loan, lease, or visa they want. They open the PDF in any editor, change the figure or date, re-export. HTPBE? flags the edit even when the visual layout looks pixel-perfect.
Letter signed by a non-existent or impersonated HR Manager
A ‘Director of Human Resources’ name nobody at the named company has heard of, with a signature that doesn’t match anything else from that employer. A letter like this built in Word, Excel or LibreOffice and exported directly, with nothing indicating later editing, comes back INCONCLUSIVE – not INTACT – however convincing the letterhead, and goes to manual review.
The scale
Why your existing checks miss this
VOE platforms check the fact when they have the employer. Underwriters often don’t.
And visual review of an employment letter PDF rarely catches a Word fabrication.
VOE platforms (The Work Number, Truework, Argyle) cover roughly two-thirds of large US employers – they confirm employment instantly when the named employer is in network. Outside that network (small employers, international, gig, recent hires), underwriters fall back to the PDF letter the applicant uploaded. HTPBE? catches the file the applicant uploaded – works regardless of VOE coverage. Use VOE where you have it; use HTPBE? everywhere else.
What HTPBE? checks
Detection capabilities
Deterministic structural signals. No probabilistic scores, no model training.
No free pass for a copied letterhead
An employment letter typed up in Word, Excel or LibreOffice and exported directly does not come back INTACT, however closely it copies a large employer’s letterhead. With no sign of later editing it returns INCONCLUSIVE for manual review; with evidence of editing or fabrication, MODIFIED.
Digital signature presence and chain
Most large-employer letters are e-signed via DocuSign, Adobe Sign, or HelloSign. Editing a signed letter after signing, or stripping its signature, is among the things HTPBE? looks for in the file.
Post-issuance edit detection
Editing an employment letter after issuance – in a PDF editor, or by rebuilding it in other software – leaves structural evidence behind. HTPBE? flags it as MODIFIED.
Pasted-element detection
HTPBE? detects logos, letterheads and signatures lifted from another document and pasted in.
Dates that disagree
A ‘freshly issued’ letter whose own dates show it was changed weeks or months later is a high-confidence flag for post-issuance editing.
Reused-template detection
HTPBE? detects documents built from a reused template – the pattern behind one fabricator turning out many ‘different’ employer letters.
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 this work for letters from any size employer?
inconclusive – not intact – whether a small employer wrote it or someone copying a large employer’s layout did. Treat it as a prompt for manual review, not proof of fraud. The verdict is modified when the file itself carries evidence of editing or fabrication.How is this different from VOE platforms?
Can it catch a salary or tenure edit on an otherwise real letter?
modified, with named markers, even when the visual layout looks clean.What does an INCONCLUSIVE verdict mean for an employment letter?
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.