Home › Reverse audit
Reverse audit
Take a filed return apart and check it
A new client hands you the return filed for them last year. Before you sign anything for the year after, it is worth knowing whether that one was computed correctly. Upload the JSON and find out.
How it works
The filed CBDT JSON is read back into its schedule-level inputs, those inputs are run through our computation engine, and the result is compared against the values that were actually filed. What comes back is a table, one row per field:
- the schedule the field belongs to,
- the value in the filed return,
- the value our engine computes,
- the variance between them, and
- a severity — a rounding difference is not a mistake, and is not reported as one.
Above the table is the count of matches, the count of mismatches and the pass rate for the return.
Supported forms
ITR-1, ITR-2 and ITR-4, for AY 2025-26 and AY 2026-27.
What it is not
It is not an opinion and it is not a certificate. It is an independent second computation of the same return, which is the thing a single piece of software can honestly offer. What you do with a variance is professional judgement.
Three times a CA reaches for this.
- Taking on a client whose earlier returns you did not prepare.
- A notice that disputes a figure, where you need to know your own position before replying.
- A second pair of eyes on a return prepared by a junior, without re-keying it.
Questions
What does the reverse audit compare?
Which forms does it support?
Is it useful on a return we filed ourselves?
Does a variance mean the filed return was wrong?
Check a return you did not prepare
Upload a filed ITR JSON and see the variance report. 30-day trial, nothing held back.