India Audit Lens
Build, review, and hand off a TDS or TCS filing package
AuditLens can prepare, validate, build, and review a TDS/TCS package. Direct production transmission is not qualified for this manual: the production baseline contains conflicting gates and live-looking controls,…
By India Audit Lens product team · Updated 2026-07-17
Before you begin
Complete Data, Compute, and Validate for the exact TAN/FY/form/quarter. Resolve missing PAN, challan, deposit-date, rate, interest, default, and parity issues. Confirm that the preparer and approver are different eligible users. Obtain the current CSI/challan evidence through the firm's approved process. Never enter an OTP, TRACES password, or portal credential in an unapproved screen or support message.
Generate the return package
Open the required form and quarter and verify the scope in the page header. Open Build. Under Return TXT, click Generate TXT. Wait for the stored job to succeed. If it fails, download the validation report, correct every source/schema error, and rebuild. Download and preserve the generated TXT under the engagement's approved evidence policy. Obtain/verify the CSI file for the same TAN and period through the approved controlled route. Generate the FVU package only when the CSI source, provider operation and credit/consent requirements are qualified for the firm. Review the FVU validation…
TXT and FVU generation are package-building steps; neither proves that the return was filed.
Run the maker-checker review
Open File and locate Prepare for filing. Click Prepare & run gate. This creates/refreshes the filing record and checks single quarter, ready rows, single TAN, deductee PAN coverage, challan deposit dates, and positive tax where applicable. Review each Pre-file check and its PASS/WARN/BLOCK result. Click Re-check after correcting data. Re-preparation can invalidate an earlier approval. Click Submit for review. The eligible reviewer independently verifies the package, source tie-outs, interest/fees, challans, approval scope, and generated artifact version. Click Approve for filing or Send back.
The preparer cannot approve their own return in the intended maker-checker workflow. Approval is for a specific reviewed version; regenerate/re-prepare after changes and repeat review.
Hand off and record completion
Download the final approved artifacts required by the external filing process. File through the firm's currently approved TDS/TCS portal or provider process outside AuditLens. Obtain the definitive portal receipt/provisional receipt number and timestamp. Store the receipt and filed artifacts in the approved client/engagement evidence location. Update the filing history/status only through the supported acknowledgement or completion path. Cross-check the recorded receipt against the external portal before describing the return as filed.
Direct-transmission boundary
Do not use a Confirm & e-file control merely because it is visible. At the verified production revision:
one transmission-status path says live TDS transmission is NOTREADY pending test-environment validation and explicit opt-in; a separate UI/API path is labelled live but is not consistently bound to the documented filing approval check; and certificate/OLTAS operations also retain explicit production-readiness gates.
Until this conflict is resolved and re-tested end to end, this manual does not authorize or teach direct production e-filing. Escalate the screen to the platform owner and use the approved portal hand-off.
Expected result
You have a validated, reviewer-approved filing package plus independent external receipt evidence. Use Filed only after the receipt is verified; otherwise record the package as Prepared, Approved, or Handed off, as appropriate.