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’s itself a fraud signal in this context — real Form 16 exports always come from TRACES (Part A) or a payroll engine (Part B), 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 Form 16 PDFs actually look
Three real fraud mechanics we catch at the structural PDF layer.
Part B salary breakdown edited after issuance
Authentic Form 16 Part B comes from the employer’s payroll system as a generated PDF. The applicant downloads it, opens it in any PDF editor or spreadsheet, edits Gross Salary or Perquisites, exports as PDF. The page looks identical; the producer field changes from the payroll system to whichever editor was used.
Fabricated Form 16 from a generator tool
Online "Form 16 generator" sites produce a Part A + Part B PDF for any employer name and salary the user types in. These tools miss the structured TRACES metadata authentic Part A carries and leave generator-tool producer fingerprints.
TDS figures inflated, but TAN/PAN math broken
When the gross is edited, the TDS deducted no longer reconciles with the slabs and surcharge. Row arithmetic across Part B (Gross → Standard Deduction → Net → TDS) breaks — a high-confidence flag even before structural analysis.
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-fraud-detection 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.
Producer signature on Form 16
Authentic Form 16 Part A is generated by TRACES (the income tax portal) — a unique, recognisable producer signature. Part B comes from the employer’s payroll engine. When the producer is Microsoft Excel, LibreOffice, Chrome Headless, or a generic PDF library, the document was edited or fabricated on a desktop.
TRACES metadata presence in Part A
Real Form 16 Part A embeds structured TRACES metadata — receipts, ack numbers, deductor TAN. Generator-tool fakes don’t reproduce this metadata correctly. Missing or malformed TRACES identifiers are a clean signal of fabrication.
Incremental update trail (xref tables)
Authentic Form 16 PDFs have a single cross-reference table from the issuing system. Re-saves in Excel or PDF editors append a second xref — a structural fingerprint of post-issuance editing.
Gross-to-TDS arithmetic
Line arithmetic across Part B (Gross Salary → exemptions → Standard Deduction → Net Taxable → TDS) is checked row by row. Edited gross figures break the chain — even when the visual layout is preserved.
Modification timestamp gap
A real Form 16 issued in May has CreationDate ≈ ModDate. A six-month gap — common when applicants edit the file later for a loan application — is a clear flag.
Font subset prefix divergence
Multi-session edits or page-by-page reassembly leave font subset fingerprints across pages. Authentic single-session payroll exports have consistent subsets; tampered files don’t.
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
$15/mo
30 checks/mo
Manual spot-checks and integration testing
most commonGrowth
$149/mo
350 checks/mo
Active document processing pipelines
high volumePro
$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
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 or inconclusive with producer-mismatch and missing-TRACES-metadata flags.What about scanned Form 16 PDFs? Some applicants send a scan of a printed copy.
inconclusive: the institutional metadata is gone (because the scanner authored a fresh PDF). 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?
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.