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 verify 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.
One REST call, one deterministic verdict
Upload the PDF. The API returns INTACT, MODIFIED, or INCONCLUSIVE with named markers — in about three seconds.
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 verifies the employment. It does not verify the file.
Both layers matter. Most teams only run one.
Background-verification 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.
Five forensic layers, one deterministic verdict
Every PDF we receive passes through the same structural pipeline — no model training, no thresholds to tune.
Metadata analysis
Creation and modification timestamps, producer and creator fields, XMP metadata — the first layer exposes basic tampering.
File structure
Xref tables, trailer chain, incremental updates. Any edit after export leaves a structural fingerprint here.
Digital signatures
Signature chain integrity and post-signature modifications produce deterministic markers. Certainty-level signal.
Content integrity
Fonts, objects, embedded content, page assembly. Multi-session edits and inserted objects are visible at this layer.
Verdict with markers
Deterministic output: INTACT / MODIFIED / INCONCLUSIVE, with named markers for every finding — suitable for audit trail.
Form 16 and adjacent income-proof PDFs we check
Every type listed below is analyzed at the structural file layer — not the rendered image.
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 verified 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.
Two HTTP calls to verify any Form 16 PDF
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/applicant-form16-fy2024.pdf"}'Step 2 — read the verdict (GET /v1/result/{id})
{
"id": "f1g2h3i4-5j6k-7l8m-9n0p-q1r2s3t4u5v6",
"status": "modified",
"modification_confidence": "high",
"modification_markers": [
"Spreadsheet producer detected (Microsoft Excel)",
"Incremental update detected after original creation",
"TRACES metadata block missing on Part A"
],
"producer": "Microsoft Excel",
"creator": "TRACES (original)",
"creation_date": 1684012800,
"modification_date": 1707432000,
"has_digital_signature": false,
"xref_count": 2,
"has_incremental_updates": true
}The mismatch between creator: "TRACES (original)" and producer: "Microsoft Excel" tells the story: the original came from the income-tax portal, then was opened in Excel and re-saved nine months later. Combined with has_incremental_updates: true, the verdict is modified at high confidence.
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
Frequently asked questions
modified or inconclusive with producer-mismatch and missing-TRACES-metadata flags.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.Related solutions and guides
Alternative Lending
Form 16 + bank statement forensics for NBFC and alt-lender underwriting pipelines.
HR & Hiring
Pre-employment income document fraud detection for talent ops and BGV operators.
Fake Salary Slip Detection
Sister page — same structural forensics applied to monthly salary slips.
Fake ITR Detection
Income Tax Return forensics — submitted alongside Form 16 in lending and visa workflows.
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.