Form 16 fraud

A Form 16 is one of the easiest documents to edit and the hardest to question

Q: Do I need to call the Income Tax Department or TRACES to check?

No. HTPBE performs standalone forensic analysis on the PDF itself – no third-party API call, no IT Department lookup, no candidate consent for portal access. The signals are inside the file structure.

Q: What does an INCONCLUSIVE verdict mean for a Form 16?

HTPBE returns INCONCLUSIVE when a Form 16 PDF lacks the institutional metadata that genuine TRACES-generated or employer-payroll-issued certificates carry – typically because the file was authored on a desktop with consumer software (Word, Excel, LibreOffice) rather than exported from TRACES or a payroll engine. In the Form 16 context, INCONCLUSIVE is a review trigger, not a verdict: authentic Form 16 Part A always comes from TRACES, and Part B from a payroll system – neither would originate on a desktop. INCONCLUSIVE is not evidence of fraud – it means the file carries no institutional baseline to check it against. Route the case to a manual employer or TRACES check before any underwriting or hiring decision.

Built for fraud ops at lending, insurance & compliance teams

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.

~3 sec

per document

63 checks

forensic layers

1,500+

docs / month on Growth

Plans

subscriptions or one-off packs — see pricing

Scope

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 – 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. HTPBE? does not read those figures – it reports the structural trace of the re-save that produced the mismatch.

The scale

~$3.1B

fraudulent loan applications use altered income docs annually

~3 sec

per Form 16 via API

No DB

no Income Tax Department lookup needed – works on the file

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.

Results in under 3 seconds·30 to 1,500+ documents/month

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.

Character overlay on the original

Changing a figure is usually done by stamping replacement characters over the original rather than rebuilding the document. The overlay leaves a structural trace of its own. HTPBE? flags it without reading the page – it never looks at what the figures say.

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.

Full API reference for engineering

Pricing

Self-serve plans, no sales call

All plans include the same forensic checks. Pick the quota that matches your monthly document volume.

manual

Starter

30 credits/mo

Manual spot-checks and integration testing

most common

Growth

350 credits/mo

Active document processing pipelines

high volume

Pro

1,500 credits/mo

High-volume automation and API integrations

Enterprise (unlimited, on-premise available) — see full pricing

Secure your workflow View API docs

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?

BGV services check employment history with the previous employer or check a registry – they confirm the candidate worked there. HTPBE? checks whether the specific Form 16 PDF the candidate uploaded was edited after issuance. Use both: BGV for the fact, HTPBE? for the file.

Do I need to call the Income Tax Department or TRACES to check?

No. HTPBE? performs standalone forensic analysis on the PDF itself – no third-party API call, no IT Department lookup, no candidate consent for portal access. The signals are inside the file structure.

Can it catch Form 16s made with online generator tools?

Yes. Generator tools leave producer fingerprints (often Chrome Headless or a specific PDF library) and miss the TRACES metadata block authentic Part A carries. The verdict on a generator-produced Form 16 is typically 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.

A scan-to-PDF made from a real printed Form 16 typically returns 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?

HTPBE? returns INCONCLUSIVE when a Form 16 PDF lacks the institutional metadata that genuine TRACES-generated or employer-payroll-issued certificates carry – typically because the file was authored on a desktop with consumer software (Word, Excel, LibreOffice) rather than exported from TRACES or a payroll engine. In the Form 16 context, INCONCLUSIVE is a review trigger, not a verdict: authentic Form 16 Part A always comes from TRACES, and Part B from a payroll system – neither would originate on a desktop. INCONCLUSIVE is not evidence of fraud – it means the file carries no institutional baseline to check it against. Route the case to a manual employer or TRACES check before any underwriting or hiring decision.

Why would someone fake a Form 16 – and can it be caught?

A Form 16 is the single most-requested income proof in India: NBFCs read it to set loan eligibility, credit-card issuers use it to justify a higher limit, and embassies accept it as supporting income evidence for a visa. That makes it the document applicants most often bump – inflating the gross in Excel to clear a loan threshold or strengthen a visa case. Because the edited page renders identically, a visual review never catches it. HTPBE? checks the PDF’s structure instead, so you can spot a Form 16 that was edited or fabricated after issuance. Drop a suspect file into the free check to see the verdict in seconds.

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.

Start Free – Close the Structural Fraud Gap See Pricing

Read API Docs →