Supported document type
Detect tampered and deepfake Tax Return
A tax return is how a self-employed applicant proves income when there is no employer to corroborate it, which makes it the most heavily leaned-on document in a lending or visa file. It is also the longest: schedules feed subtotals, subtotals feed gross total income, deductions come off, and the tax computed follows from what remains. An inflated figure on the summary page rarely propagates back through the schedules. TamperCheck ties its findings to specific regions of the filing.
API slug: tax_return
Last updated:
What a genuine tax return contains
A return is a stack rather than a page. It opens with the taxpayer's name, tax identification number, address, filing status, and the assessment year, then works through schedules: business or professional receipts and expenses, depreciation, capital gains, property income, interest and dividends, and foreign income where declared. Those feed a gross total income line. Deductions and reliefs come off to give taxable income, tax is computed on it, and credits for tax already paid are set against the result, with a verification block and an acknowledgement number closing the submission.
The document is one long calculation, so most of its fields are outputs rather than inputs. Each schedule's total appears again in the summary, subtotals roll into gross total income, and the tax computed follows from taxable income at published rates. Carry-forward lines have to match the prior year's return. Tax already paid should reconcile with withholding certificates and the authority's own credit statement. The acknowledgement number and filing date are generated by the filing system rather than the taxpayer, so they encode how and when the return was submitted.
How tax return forgeries are made
Summary-page income inflation
Gross total income or the taxable income line is raised while the schedules that produce it keep their original figures. Anyone reading only the summary sees a larger business. Anyone adding the schedules up sees two different returns bound into the same submission.
Acknowledgement number fabrication
The acknowledgement number and filing date are invented, or copied from another filing, so a return that was never submitted reads as filed. These identifiers are issued by the filing portal in a defined format that encodes the submission, and a fabricated one usually fails the format or contradicts the date beside it.
Draft presented as filed
A return prepared in tax software but never submitted is exported and passed off as a filing, sometimes with an acknowledgement page appended from a genuine earlier year. Nothing in the computation is wrong. What is missing is any evidence that the authority ever received it.
Prior-year return re-dated
A genuine older return has its assessment year and dates changed so it passes as current. Return layouts and schedule numbering change between years, so the form's own structure often contradicts the year now printed across the top of it.
Tax paid line inflation
Credits for withholding and advance instalments are raised, both to imply a larger underlying income and to manufacture a refund. This line is the one a lender can most easily test, because it should reconcile with the tax authority's credit statement for the same taxpayer.
Acknowledgement page transplant
The acknowledgement or computation page from one genuine filing is merged with the body of another. A legitimately assembled submission also mixes separately issued pages, so the signal here is inconsistent identity and figures across the pages, not the fact that pages were merged at all.
What TamperCheck checks on a tax return
TamperCheck runs 200+ forensic checks across three layers and returns a risk score from 0 to 100 with plain-English findings tied to specific regions of the document. These three carry the most weight on this document class.
Arithmetic reconciliation
Stated totals are recomputed from their components, and running or cumulative figures are checked for continuity across periods. A single edited value breaks the chain even when the page still looks right.
Table structure integrity
Inserted and deleted rows leave structural artifacts behind: inconsistent spacing, misaligned columns, and formatting the visible table no longer accounts for.
Field-level forensics
Every text region is analysed in its own right rather than as part of one whole-page image. This catches the smoothed and feathered edits that whole-image Error Level Analysis misses entirely.
And many more checks
The three above are the layers that carry the most weight on a tax return. Every upload runs the full suite of 200+ checks regardless of document class, spanning file structure and metadata, pixel-level forensics, font and text rendering, optical and print characteristics, provenance signals, AI-generation signatures, and many more checks.
Who verifies a tax return, and why
Lenders and consulates assessing self-employed income and financial standing. In each case the document is being used to unlock money, access, or a legal status, which is exactly what makes it worth forging.
How to verify a tax return in 4 steps
Add the schedules up yourself
Total each income schedule and check the result against the gross total income line, then follow the deductions through to taxable income and the tax computed. A return that was edited at the summary is a return whose own schedules no longer support it.
Verify the acknowledgement against the filing system
The acknowledgement number and filing date come from the tax authority's portal. Ask the applicant to produce the return from the portal directly, or to supply the authority's own document, such as a tax transcript, an SA302, or a portal-generated acknowledgement, rather than a PDF they exported themselves.
Reconcile the tax paid against the credit statement
Credits for withholding and advance payments appear on the authority's own statement for that taxpayer. Where the return claims tax paid that the credit statement does not show, the return was either altered or never filed.
Run a forensic check on the file
TamperCheck analyses every page of a return for edited figures, rebuilt tables, and pages rendered differently from the rest, and returns findings tied to specific regions of the document at $0.50 per document.
Frequently asked questions
How do lenders verify a tax return?
Lenders ask for the return to come from the tax authority rather than from the applicant, as a transcript, an SA302, or a portal-generated acknowledgement. Failing that, they re-add the schedules to confirm they support the summary, reconcile the tax paid against the authority's credit statement, and compare declared income against business bank statements for the same period.
How do self-employed applicants fake income documents?
The usual route is to inflate the summary figures on a return that was prepared but never filed, then append an acknowledgement page so the submission appears complete. Others re-date a genuine older return, raise the tax-paid line to imply a larger business, or supply an accountant's income certificate built entirely from figures the applicant provided.
What is a tax transcript or SA302, and why do lenders ask for one?
It is a summary of the return as the tax authority actually holds it, issued by the authority rather than by the taxpayer. Lenders ask for it because it takes the document out of the applicant's hands: a transcript obtained from the portal cannot have been edited on the way, which a PDF exported from tax software certainly can.
Can an edited tax return PDF be detected?
Yes. Altering a figure in a filed return leaves the changed region with different rendering and compression characteristics from the table around it, and an edited summary stops agreeing with the schedules that feed it. TamperCheck checks both, reading the arithmetic across pages and flagging the regions that were rewritten.
TamperCheck analyses tax return uploads with a hybrid forensic and AI pipeline tuned for this document class. Upload endpoints accept PDF and common image formats; class is inferred automatically. See the API & MCP documentation for authentication, async jobs, and webhooks.