IndiaAuditLens
Build, validate, review, and file a TDS or TCS statement
IndiaAuditLens owns the return calculation, reviewed source revision, statutory TXT, official Protean FVU result and artifact lineage. The workspace prepares the approved FVU package; you upload it on the official…
By IndiaAuditLens product team · Updated 2026-10-28
Before you begin
Confirm the TAN, financial year, form and quarter in the workspace header. Complete the return's earlier steps (Data, Challans, Review or Check) and source approval for that exact scope. Resolve missing PAN, challan, deposit-date, rate, interest, fee, default and tie-out issues. Confirm that the preparer and approver are different eligible users. Obtain the current CSI through the supported OTP route or the approved CSI-file intake shown by the workspace. Enter credentials and one-time codes only in the dedicated controlled fields. Do not put them in notes, uploaded files, AuditIQ or…
Build or import the statutory TXT
Open the Build the TXT and run FVU stage for the required statement. Confirm that the current source revision is approved. Select Build IndiaAuditLens TXT when the owned builder is available. To continue from a TXT prepared in another approved utility, open Import a TXT from another utility. This intake is supported for regular 24Q, 26Q, 27Q and 27EQ statements in Q1–Q4 when the workspace displays it as available. For an imported TXT, select the exact .txt, verify its SHA-256, add the workpaper or utility reference, confirm its scope and import it. Wait for the stored TXT job to succeed…
An imported TXT must match the workspace TAN, financial year, form and quarter. Import creates a reviewable input artifact; it does not establish that the TXT is valid, approved or filed.
Obtain the CSI and run official FVU
Open the Challan status file (CSI) stage. Upload the approved same-scope CSI file through the route displayed by the workspace (the connected TAN-and-OTP route is switched off). Confirm the CSI coverage and that the saved CSI belongs to the same TAN and filing period. Return to Build the TXT and run FVU and select Generate FVU. IndiaAuditLens runs the official Protean FVU for the statement year when that FVU version is set up on the server (Platform admin › Settings › Returns). Wait for the stored job to finish. If FVU fails, review the displayed error code, field/path, record, line,…
The FVU stage is not disabled merely because the connected service is unavailable. The official local validator and portal package route remain separate from it.
Approve the exact FVU
Open the Partner approves the exact FVU stage. Confirm the form, quarter and year. Compare the displayed TXT and FVU SHA-256 values with the artifacts you reviewed. Review the successful official validation result. A reviewer who is different from the preparer selects the confirmation and clicks Approve exact FVU.
Approval is bound to one source revision and one FVU hash. Rebuilding or replacing an upstream artifact requires a fresh review and approval.
Upload on the official e-Filing portal
Open the Upload on the e-Filing portal stage. Select Prepare official upload ZIP. The action is available only for the current successful and approved FVU. Download the official upload ZIP and keep its displayed SHA-256 with the workpaper. This upload ZIP contains only the exact approved .fvu file required by the portal. The separate filing evidence archive contains the source, validation and supporting reports; do not upload that evidence archive. Open the official e-Filing portal from the workspace and upload the official upload ZIP under the firm's authorised process. Do not mark the…
The status remains Portal package ready until a real portal receipt is recorded.
Expected result
The current approved source is linked to its exact TXT, CSI, official validation result and FVU. The statement then has an independently recorded official-portal receipt. The UI distinguishes preparation, package-ready and filed states.