An Income Tax Return PDF can be edited and re-saved with a higher gross — and still print clean
NBFCs use it as primary income proof. Embassies use it as supporting documentation. And every applicant who needed a higher loan or a stronger visa case knows that the original ITR-V from the Income Tax portal can be edited in five minutes. The page renders identically. 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 ITR, we’re the most specific tool for it.
When HTPBE? returns INCONCLUSIVE on an ITR, that’s itself a fraud signal in this context — real ITR-V exports always come from the Income Tax portal, 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 ITR PDFs actually look
Three real fraud mechanics we catch at the structural PDF layer.
Gross taxable income inflated in Excel
Authentic ITR-V comes from the Income Tax portal as a generated PDF with the IT Department’s producer signature. The applicant downloads it, opens it in any PDF editor or spreadsheet, edits the Gross Total Income, exports as PDF. The producer field changes from the IT portal to whichever editor was used. Visual layout preserved; file fingerprint flipped.
Acknowledgement number fabricated to match a fake ITR
The applicant builds a phony ITR PDF in Word using a screenshot of the layout, types in a plausible 15-digit acknowledgement number, exports. The structural metadata of the IT Department’s portal is missing entirely — and the producer field is Microsoft Word, not the portal’s engine.
Refund amount edited up to support claimed income
When the gross is increased, the refund or tax payable should change to match. Edited ITRs often leave the refund untouched, which the structural arithmetic check catches. Combined with the producer mismatch, the verdict is unambiguous.
The scale
Why your existing checks miss this
Document parsers extract numbers. They do not check the file.
OCR can read whatever the PDF shows — even if the PDF was edited after issuance.
NBFC document-parsing platforms (Perfios, ScoreMe, Karza) extract figures from ITRs via OCR and run rules — they don’t analyse the PDF’s file structure. If the applicant edits the gross after issuance and re-exports, the OCR happily reads the inflated number. The IT Department portal has its own fraud detection but requires the applicant’s consent for portal access — most teams cannot rely on it. HTPBE? fills the structural-PDF layer those workflows do not provide — standalone, no IT Department call, no candidate consent for portal access.
What HTPBE? checks
Detection capabilities
Deterministic structural signals. No probabilistic scores, no model training.
Producer signature on the ITR PDF
Authentic ITR-V comes from the Income Tax portal — a unique, recognisable producer signature. When the producer is Microsoft Excel, LibreOffice, Microsoft Word, Chrome Headless, or a generic PDF library, the document was edited or fabricated on a desktop.
IT portal metadata block presence
Real ITR-V embeds structured metadata from the Income Tax portal — acknowledgement digest, e-filing receipt identifiers, system-generated barcodes encoded as objects. Generator-tool fakes don’t reproduce this metadata. Missing or malformed identifiers are a clean signal of fabrication.
Incremental update trail
Authentic ITR PDFs have one cross-reference table. Re-saves through Excel or PDF editors append a second xref — visible structural evidence of post-issuance editing.
Income arithmetic
Line arithmetic across the computation (Gross → exemptions → deductions → Taxable → Tax → Refund) is checked row by row. Edited gross figures break the chain unless every dependent field is also adjusted — which fraudsters routinely miss.
Modification timestamp gap
A real ITR filed in July has CreationDate ≈ ModDate. A six-month gap on a "freshly filed" ITR is a high-confidence flag for post-export editing.
Font subset and barcode object integrity
The IT portal embeds barcodes as specific object streams; tampered files often break or omit these objects. Font subset prefix divergence across pages is another structural fingerprint of multi-session editing.
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
Do I need to call the Income Tax Department to check ITRs?
How is this different from NBFC document parsers like Perfios or Karza?
Can it catch ITRs fabricated entirely from scratch?
modified or inconclusive with producer-mismatch and missing-metadata flags.What about ITRs filed by a CA on the applicant’s behalf?
What does an INCONCLUSIVE verdict mean for an ITR?
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.