These two terms get confused often, partly because both end with you submitting a corrected version of your return. But they’re triggered differently, governed by different sections, and have different deadlines \u2014 mixing them up is how people miss the window that actually applied to their situation.<\/p>\n
A defective return<\/strong> (Section 139(9)) is the department’s assessment of your return \u2014 they’ve reviewed it, found it incomplete or inconsistent against the form’s requirements, and are giving you a fixed, short window to correct it. You didn’t choose this process; it was triggered by a notice.<\/p>\n A revised return<\/strong> (Section 139(5)) is something you choose to do \u2014 voluntarily filing a corrected, complete version of your return because you’ve spotted an error or omission yourself, whether or not the department has said anything. It replaces your original return entirely.<\/p>\n A defective return notice always begins with a communication from the department, specifying which condition under Section 139(9) your return fails to meet, typically with an annexure explaining the exact defect. There’s no version of this where you initiate it yourself \u2014 by definition, it’s the department telling you something’s wrong.<\/p>\n A revised return can be filed for any reason at all \u2014 you forgot to declare a small interest income, you realise you claimed a deduction incorrectly, you want to switch ITR forms because you’ve belatedly realised the one you used doesn’t fit your income, or you simply want to correct a typo in a bank account number. It requires no notice and no external trigger.<\/p>\n This is the most practically important difference. A defective return notice gives you a fixed, short window \u2014 typically 15 days from the date of the notice, extendable at the AO’s discretion on request. Miss it, and your return risks being treated as never filed, with the consequences covered elsewhere in this series.<\/p>\n A revised return has a longer, standing window: you can file it any time up to three months before the end of the relevant assessment year, or before the assessment is completed, whichever comes first \u2014 in practice, this generally works out to around December 31 of the assessment year for most taxpayers, though it’s worth confirming the exact cutoff for a given year. There’s no daily countdown pressure the way there is with a defective return notice, but the deadline is still firm once it arrives.<\/p>\n A defective return correction is generally scoped to fixing the specific defect the notice identifies \u2014 the notice tells you what’s wrong, and your correction addresses that. In practice this often does require refiling the return more broadly (for instance, switching to the correct ITR form entirely), but the trigger and the department’s expectation are narrower than a full voluntary revision.<\/p>\n A revised return has no such constraint. You can change anything \u2014 add income you’d missed, correct a deduction, switch forms, update bank details, fix a computational error you noticed on your own. It’s a full, fresh filing that stands in place of the original for every purpose.<\/p>\n Yes. If you receive a defective return notice, the corrected return you file in response can also be thought of as functionally similar to a revision \u2014 you’re submitting a new, complete return in place of the old one. But procedurally, you’re responding to the 139(9) notice within its specific window and process, not independently invoking Section 139(5). And if you’d rather just refile more broadly on your own initiative before or instead of dealing with a defective notice’s narrow scope, filing a revised return under 139(5) (where the window still permits it) is generally the cleaner route, since it isn’t bound by the tighter timeline.<\/p>\n Conversely, if you catch a form error or omission yourself, before any notice arrives, you don’t need to wait for the department to flag it \u2014 file a revised return under 139(5) directly. There’s no requirement to wait for a defective return notice before correcting your own mistake.<\/p>\n If you have a notice in hand, the defective return process and its 15-day (or extended) deadline governs your situation \u2014 that’s the deadline that matters, regardless of how much time is technically still available for a revised return. If you don’t have a notice and you’ve simply noticed an error yourself, use the revised return route, and don’t wait for the department to catch it, since the earlier a genuine error is fixed voluntarily, the fewer downstream complications it tends to cause \u2014 a self-corrected return rarely draws additional scrutiny, while a department-flagged defect is one data point the system now has on your filing accuracy.<\/p>\n Defective return: department-initiated, narrow in stated scope, short and firm deadline, risk of invalidation if missed. Revised return: self-initiated, unrestricted in scope, longer deadline tied to the assessment year, no invalidation risk since it’s voluntary. Knowing which situation you’re in \u2014 whether a notice exists or not \u2014 tells you immediately which section, which deadline, and which process actually applies.<\/p>\n","protected":false},"excerpt":{"rendered":" These two terms get confused often, partly because both end with you submitting a corrected version of your return. But they’re triggered differently, governed by different sections, and have different deadlines \u2014 mixing them up is how people miss the window that actually applied to their situation. The core distinction A defective return (Section 139(9)) […]<\/p>\n","protected":false},"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_updated_date":"","_blog_featured_landing":false},"blog-category":[],"acf":{"alt_text":"","include_in_calculator_page":"","hash_tags":"","spotify-id":"","show_audio_player":false,"audio_title":"","audio_link":"","key_takeaway":"","article_sources":""},"yoast_head":"\nHow each one starts<\/h2>\n
Timelines<\/h2>\n
Scope of what you can fix<\/h2>\n
Can they overlap?<\/h2>\n
Which one should guide your decision<\/h2>\n
The practical summary<\/h2>\n