A Form 16 is one of the easiest documents to edit and the hardest to question
NBFCs use it to set loan eligibility. Employers use it to check previous compensation. Embassies use it as supporting income proof. And every applicant who ran the original through Excel and bumped the gross knows the page renders identically – but the file structure 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 altered or fabricated Form 16, we’re the most specific tool for it.
When HTPBE? returns INCONCLUSIVE on a Form 16, 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 Form 16 PDFs actually look
Three real fraud mechanics we catch at the structural PDF layer.
Part B salary breakdown edited after issuance
The applicant downloads the real Part B generated by the employer’s payroll system, opens it in any PDF editor or spreadsheet, edits Gross Salary or Perquisites, exports as PDF. The page looks identical; the edit typically leaves traces of the editor in the file.
Fabricated Form 16 built from scratch
Online ‘Form 16 generator’ sites produce a Part A + Part B PDF for any employer name and salary the user types in. Whatever tool produced it, a Form 16 comes back MODIFIED when the file itself carries evidence of editing or fabrication. Treat an INCONCLUSIVE result as a prompt for a manual check with the employer, not as proof of fraud.
Edited figures, re-saved file
When the gross is edited, the TDS deducted no longer reconciles with the slabs and surcharge. HTPBE? does not read those figures – it reports the structural trace of the re-save that produced the mismatch.
The scale
Why your existing checks miss this
BGV checks the employment. It does not check the file.
Both layers matter. Most teams only run one.
Background-check platforms like AuthBridge, IDfy, and OnGrid confirm whether a candidate worked at the claimed employer – they cannot tell you whether the Form 16 PDF the candidate uploaded was edited after issuance. NBFC document-parsing platforms (Perfios, ScoreMe, Karza) extract figures via OCR and run rules – they don’t analyse the PDF’s file structure to detect the edit itself. Manual HR review catches obvious typos, but a clean re-save through any editor passes a visual check every time. HTPBE? fills the structural-PDF layer those workflows do not provide – and works standalone, with no Income Tax Department lookup required.
What HTPBE? checks
Detection capabilities
Deterministic structural signals. No probabilistic scores, no model training.
Unconfirmed files go to review
INCONCLUSIVE means HTPBE? cannot confirm the file as an untouched original – a reason for manual review, not proof of fraud.
Evidence in the file decides
Whatever tool produced it, a Form 16 comes back MODIFIED when the file itself carries evidence of editing or fabrication. How faithfully it copies the TRACES page plays no part in that – HTPBE? looks at the file, not the page.
Post-issuance edit detection
Editing a Form 16 after issuance – in a PDF editor, or by rebuilding it in other software – leaves structural evidence behind. HTPBE? flags it as MODIFIED.
Character overlay on the original
Changing a figure on an existing Form 16 leaves a structural trace. HTPBE? flags it without reading the page – it never looks at what the figures say.
Dates that disagree
A Form 16 whose own dates show it was changed months after it was issued – common when applicants edit the file later for a loan application – is a clear flag.
Reassembled documents
HTPBE? detects documents assembled from pages of different sources and documents reworked after their original creation.
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
How is this different from BGV services like AuthBridge or IDfy?
Do I need to call the Income Tax Department or TRACES to check?
Can it catch Form 16s made with online generator tools?
modified when the file itself carries evidence of editing or fabrication, whatever tool produced it. An inconclusive result means HTPBE? cannot confirm the file as an untouched original – a reason for manual review, not proof of fraud. Checking with the employer is a sensible next step.What about scanned Form 16 PDFs? Some applicants send a scan of a printed copy.
inconclusive: the scanner authored a fresh PDF, so HTPBE? cannot confirm it as the untouched original. Treat inconclusive on a Form 16 as a prompt for manual review or a request for the original PDF.What does an INCONCLUSIVE verdict mean for a Form 16?
Why would someone fake a Form 16 – and can it be caught?
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.