There is nothing in it for you to file late. The statement is compiled by the department from other people's reports, so it has no due date of its own and no penalty attaches to it in your name. Two real deadlines sit either side of it. Payers have periods within which they must report what they deducted, and lateness there is their exposure. You have your own return deadline, and lateness there is yours. The statement is what connects the two, and the damage a delay does is to your credit and your refund rather than to a penalty account.
What is the late filing penalty for Form 26AS?
- 15+Years of the founder's cross-border experience
- 18,000+Clients served across our offices in India, the USA, Canada and the UAE
- 5.0Google rating
- 4Global offices — India, USA, Canada & UAE
The consolidated statement of tax deducted, collected and paid against a taxpayer's Indian identifier. The exposure on this kind of filing is charged by reference to the form and the delay rather than to the tax, which is why an unfiled year with no tax can still be expensive.
What a late filing costs
The consolidated statement of tax deducted, collected and paid against a taxpayer's Indian identifier.

When the rule breaks
Credit is given for what appears here, not for what the certificate says. Reconciling the statement before filing is how a mismatched deduction is found while it can still be fixed by the deductor.
Where to go from here
The full treatment — who it binds, the deadline, the penalty and the fixed fee — is on Form 26AS — tax credit statement in India. If a letter prompted this, bring the letter — it usually contains the answer to half the questions.
Read and approved for the 2025 and 2026 filing seasons by Udit Gupta, International Tax, Cross-Border Tax & Transfer Pricing Expert, Legal Quotient Consultants. Written as general guidance, not as a recommendation for your situation. Talk it through with us before acting on it.
Cross-border situations we are engaged for
Return filed days before the deductor's report went through
The return went in on the last available day, and the final quarter's deduction was reported by the bank shortly afterwards. Processing allowed only the credit the statement then held and raised a balance for the rest. We put together the certificate, the bank's own acknowledgement of when it filed, and the statement as it later stood, then answered the assessment on that footing. The engagement produced the full credit restored for the year, a documented sequence explaining the difference, and a revised filing calendar so the following year did not repeat it.
Read how this one runsRefund held for months behind a payer's unfiled quarterly report
A refund claim sat unpaid because one payer had deducted and never reported it. The account holder had been writing to the department, which was the wrong address for the problem. We identified the payer and the period from the deposit records, produced its own certificate back to it, and pursued the correction until the entry appeared. The engagement produced the missing entry against the right identifier, the refund released on the strength of it, and a short written record of the correspondence in case the same payer repeats the pattern.
Read how this one runsUnfiled Indian years rebuilt from the statements themselves
A non-resident who had not filed in India for a long period wanted the position regularised before selling a property. We pulled the statement for each unfiled year, treated it as the inventory of what had been reported, then established what income had no deduction against it and so appeared nowhere. The engagement produced a year-by-year reconciliation, a set of returns filed in sequence for those years, and a clear statement of the credits claimed against what the department itself held for each of them.
Read how this one runsDemand raised because claimed credit exceeded the statement at processing
The return had claimed credit from every certificate received. By the time it was processed, a payer's report had been rejected for a data error and no longer appeared, so the claim exceeded what the statement showed and a demand followed. We traced the rejection back to the payer, had the corrected report filed, and replied to the demand with the entry and the dates. The engagement produced a withdrawn demand, the credit allowed in full, and a note to the payer's accounts staff about the field that had caused the rejection.
Read how this one runsBuyer deducted at closing and reported it a quarter late
An Indian property sale closed with the buyer holding tax back from the consideration, as required. The buyer's reporting was filed a full period late, so for months the seller's statement showed a sale with no tax against it while the seller was abroad and unable to press the point in person. We set out the buyer's reporting obligation in writing, followed it through to completion, and matched the entry when it arrived against the deed. The engagement produced the deduction visible against the seller and a return that recovered the excess held back.
Read how this one runsEmployer's late and mis-keyed report corrected for a whole payroll
A small Indian employer had filed a quarterly report late and against transposed identifiers, so a number of employees saw nothing in their statements while their payslips showed deduction every month. We reconstructed the payroll against the report as filed, identified every entry that had gone to the wrong identifier or nowhere, and had the corrections filed. The engagement produced accurate entries for each employee for that period, a payroll process that checks identifiers before the report goes out, and written guidance for the staff who file it.
Read how this one runsCatching Up From Inside the United States
The domestic route suits a filer who was resident in the US through the missed years, and it differs from the offshore one in what it asks for and what it costs. Choosing between them before anything is filed is the whole engagement.
Read how this one runsA Penalty Argued on the Facts Rather Than the Form
Reasonable cause is a documented story with dates, not an assertion of good intent. The engagement assembles what the client actually knew and when, and puts the sequence in writing alongside the filings it explains.
Read how this one runsAll case studies — every published engagement in one place.
Core International & Cross-Border Tax Services
Strategy and compliance for income, assets and families spread across borders.
Industries & Client Types We Serve Worldwide
- Foreign VAT / GST / sales tax registrations
- Marketplace withholding reviews
- Inventory nexus & PE analysis
- Multi-currency books reconciled
Software revenue crosses borders by default — sourcing rules, withholding on licence-like payments and IP location decide the effective rate.
Software revenue is rarely taxed where the team sits. Licence, subscription and service income are characterised differently by each side, and the answer decides withholding at source, treaty relief and whether a foreign customer creates a taxable presence at all — questions that are cheap to settle before the contract and expensive afterwards.
- Cross-border revenue sourcing & withholding
- IP structuring with real substance
- Equity for cross-border teams
- U.S. expansion: entity & PE setup
- Reg 105 / 102 waivers
- Permanent establishment risk
- Partner mobility planning
- Cross-border withholding recovery
- Section 216 rental returns
- FIRPTA withholding recovery
- Section 116 clearance
- Treaty credit optimization
- Transfer pricing documentation (s.247)
- Customs value vs transfer price
- Foreign affiliate reporting (T1134)
- Country-by-country reporting
- Reg 105 & U.S. CWA agreements
- Multi-state & country calendars
- Touring income allocation
- Royalty & image-rights withholding
- Residency analysis before moving
- Employer payroll exposure
- Totalization & social security
- Foreign tax credits
- Treaty access & PPT reviews
- FAPI & surplus computations
- Withholding-efficient routing
- Governance & substance
Form 26AS: further questions
The return is processed against what the statement held at the time, so a credit that was not yet visible is likely to be disallowed and a balance raised. That is a correctable position rather than a final one. Once the payer's report has gone through and the entry appears, the return can be revised, or the demand answered by pointing at the entry that now exists. Keep the certificate, the payer's acknowledgement of its own late report, and the dates. What decides how much work this takes is whether you can show the sequence, not whose fault it was.
You can, and sometimes you must, but do it with your eyes open. Filing ahead of the last reporting period means filing against an incomplete picture, and any deduction not yet reported is a credit you are claiming that the processing cannot see. If the deadline allows, wait until the final period's reporting has gone through and check the statement once more. If it does not allow, file on your own correct figures rather than on the statement's shorter version, and keep the evidence of the missing deductions where you can reach it quickly.
The obligation to report belongs to the payer, so the consequence of reporting late sits with the payer. What sits with you is the practical cost: a credit that is not visible when your return is processed, a refund that waits, and correspondence to fix something you did not cause. That is worth knowing before you chase the wrong party. A branch or a tenant who has deducted and not yet reported is the only one who can make the entry appear, and asking the department to accept your certificate in place of the entry does not work.
Usually it does, because a refund is the difference between what you owed and the credit the processing can actually see. If part of that credit is not in the statement, the computed refund shrinks or disappears, and the correspondence to restore it takes longer than the filing did. The order of work that avoids this is unglamorous: confirm every deduction is visible, then file. Where a payer is late and the deadline will not wait, file correctly and treat the refund as something that follows the payer's correction rather than your submission.
In our experience the older years are still retrievable, and they are the most useful thing you have. When someone returns to Indian filing after a long gap, the statement for each year is the closest thing to an objective record of what was reported about them: which banks deducted, which buyer deducted on a sale, what was paid directly. Start there, year by year, then look for income that carried no deduction and so left no trace. Reconstructing from memory and a shoebox is the alternative, and it produces a return you cannot defend.
A social security agreement that stops you contributing to two systems for the same work, and lets periods in both count towards benefit eligibility in either. Which system you stay in depends on the agreement's rules for your situation — a seconded employee usually remains in the home system for a set period, a locally hired one usually joins the host system. You evidence it with a certificate of coverage obtained before or shortly after the assignment starts. See certificates of coverage.
Usually the country you are physically in, because employment income is generally sourced where the work is done, with your residence country taxing it as well if you are resident there and giving credit. Three things follow: your employer may acquire withholding and social security obligations where you sit, a treaty tie-breaker may be needed if both countries call you resident, and a short trip that becomes a long stay can cross a residence threshold nobody was watching. See remote workers and digital nomads.



