India Audit Lens
Export, hand off, and record an ITR filing
AuditLens does not transmit an ITR to the Income Tax portal in the verified baseline. It creates an engine-schema hand-off bundle, after which the authorised user completes the return in approved tax software/ITD…
By India Audit Lens product team · Updated 2026-07-17
Confirm the pre-file gate
Open File for the correct client and AY. Review Pre-file gate. Confirm Computation clean, 26AS credits reconciled, and All checks green — hand-off is safe. If any item fails, return to its source tab, correct it, recompute/review, and reopen File.
The interface may allow an acknowledgement to be recorded despite open errors. Do not do this unless an independently filed portal return genuinely exists and the discrepancy is being handled under an approved exception process. Recording an acknowledgement changes the internal status; it does not validate the return.
Build and inspect the hand-off bundle
Under Hand-off — export & portal filing, click Build hand-off bundle (JSON). Download the new ENGINE JSON artifact. Open it only in an approved secure environment. Review assessment year, resolved form, regime, sources, engine request/response, summary, contract flags, and validation findings. Treat the file as a preparation/evidence bundle. It is explicitly not the ITD portal upload schema and must not be uploaded blindly to the portal.
If the gate was not clean, the bundle embeds open findings. Building the artifact does not approve or clear them.
Complete the portal hand-off
Use the approved tax software or Income Tax portal to complete every required form-specific schedule and validation absent from AuditLens. Reconcile portal totals back to the reviewed computation and source evidence. Have the authorised signatory/filer review the final portal return. Submit and complete the applicable DSC/EVC/e-verification step outside AuditLens. Obtain the official acknowledgement/receipt and verify PAN, AY, form, filing section/type, submission time, and verification state.
Record the acknowledgement
Return to File → Acknowledgement. Enter the exact Acknowledgement number from the portal receipt. Select e-Verify mode: Aadhaar OTP, Net banking EVC, DSC, ITR-V by post, or Not yet verified. Click Record filing once. Verify the stable Filed — ack … status, recorded time, and verification mode.
If verification is still pending, choose the pending state and track completion externally. Do not describe a pending ITR-V/e-verification as fully e-verified.
Review artifacts and history
The current File tab lists stored hand-off and acknowledgement artifacts with creation times. It does not provide a complete, separate event/provider-call history screen.
Review the artifact type, name, created time, and download availability. Preserve the reviewed engine bundle, final portal JSON/PDF, computation, approval evidence, portal acknowledgement, and e-verification evidence under firm policy. Reconcile the internal Filed status to the portal on subsequent work or before revision. For a revised/updated return, create/use the appropriate workpaper and preserve lineage to the original acknowledgement; do not overwrite the evidence trail.
Expected result
The externally completed and verified return has a matching official acknowledgement recorded in AuditLens, with the engine hand-off artifact and independent portal evidence retained. No part of this process should imply direct AuditLens transmission.