Income Tax Portal Issues Form 144 Filing Manual for Non-Resident TDS Statements
The Income Tax Department’s e-Filing portal is carrying a detailed user manual for Form 144, the quarterly TDS statement for non-salary payments made to non-residents. The operational guidance is useful for companies, firms, government bodies, individuals and tax professionals handling cross-border payments because it sets out not only the filing route under the Income-tax Act, 2025 environment, but also the validation failures that can cause a submitted statement to be rejected.
The portal describes Form 144 as the quarterly statement required from a person who deducts tax at source on payments other than salary made to a non-resident. Examples identified in the official manual include interest, fees and other income. The Department’s help centre currently places the form under the paired label “Form27Q / Form 144”, while the filing workflow itself directs users to the “Forms as per Income Tax Act 2025” category.
Quarterly due dates remain central to the filing workflow
The official manual lists four filing deadlines. For the April-June quarter, Form 144 is due by July 31 of the financial year. The July-September quarter is due by October 31, the October-December quarter by January 31, and the January-March quarter by May 31 of the following financial year.
For compliance teams, the practical consequence is that the return-preparation process should begin before the quarter-end filing date. The Department specifically requires a valid TAN registered on the e-Filing portal, an updated Return Preparation Utility from Protean, a valid File Validation Utility output and a registered digital signature certificate where DSC-based upload is used.
Form 144 is prepared through Protean and uploaded on the e-Filing portal
The filing process is split between the Protean utility and the Income Tax e-Filing portal. The manual first directs the deductor to the Protean e-TDS/e-TCS downloads area, where the latest Return Preparation Utility for quarterly regular or correction statements is to be used. After the data is entered and validated, the FVU file is generated and converted into a ZIP file.
The deductor then logs in to the e-Filing portal using the TAN and navigates through e-File > Income Tax Forms > File Income Tax Forms. Under “Forms as per Income Tax Act 2025”, the user selects the deduction and collection at source category, chooses Form 144, the applicable Tax Year, the relevant quarter and whether the upload is a regular or correction statement.
The ZIP file containing the FVU output is then uploaded and the filing is taken through e-verification. The Department says the taxpayer should receive communication on the registered email address and mobile number after submission.
FVU version mismatch is a specific rejection risk
One of the most important controls in the new manual is the instruction to ensure that the FVU file being uploaded matches the FVU version shown on the e-Filing form screen. The portal separately displays the Protean and e-Filing versions and warns users to use the correct updated version.
This is more than a technical housekeeping point. The Department lists FVU-version mismatch among the possible reasons for rejection. Tax and payroll software teams should therefore verify the current utility version immediately before preparing a statement rather than relying on an older installed copy.
Accepted statements move to TRACES; rejected statements must be corrected
After submission, users can go to e-File > Income Tax Forms > View Filed Forms to see the filed Form 144 and its validation status. The manual says that a successfully validated statement will show as accepted and will be sent to TRACES for further processing. If validation fails, the form is rejected and the registered primary email receives a communication containing the rejection reason.
The Department identifies several common rejection scenarios: selection of the wrong Tax Year; multiple filing for the same quarter; mismatch between the FVU version prepared and the version expected by the portal; uploading a correction FVU while filing a regular statement or vice versa; a TAN in the FVU that does not match the logged-in TAN; and, for corrections, an RRR number in the FVU that does not match the number entered on the form landing screen.
The manual also makes clear that rejection is not the end of the process. The deductor should rectify the error, generate or use the correct FVU ZIP and file the form again. A submitted form may also temporarily remain under processing before an acceptance or rejection email is generated.
What CAs and tax teams should check before the next filing
- TAN readiness: confirm that the deductor’s valid TAN is registered on the e-Filing portal and matches the TAN embedded in the FVU.
- Utility version: download the current Protean RPU and ensure the generated FVU version matches the version displayed by the Income Tax portal.
- Statement type: distinguish regular and correction filings before generating and uploading the FVU.
- Quarter and Tax Year: validate the period selected on the portal against the data in the statement.
- Correction controls: where a correction is being filed, reconcile the RRR number before upload.
- Post-filing review: do not treat upload as completion; check the filed-form status until the statement is accepted and transmitted to TRACES.
Practical takeaway: the Form 144 manual turns the new non-resident TDS statement into a clear operating workflow. The most preventable failures are data-and-version mismatches, so firms and finance teams should build a pre-upload check around TAN, Tax Year, quarter, filing type, RRR details and the current FVU version.
Official source: View the official source document
Key takeaway
Current first-party filing guidance provides a highly practical workflow, quarterly due dates and rejection controls for a newly renumbered TDS reporting environment.
