Choosing the return form is treated as a quick question at the start of the job and it is the decision most likely to cost an hour in December.
The department publishes the rules. They are numbered, they are quoted verbatim in the validation document for each assessment year, and they sort into two groups that behave completely differently.
One group refuses the upload. The other lets the return through, and the return is then treated as defective under section 139(9). The second group is the expensive one, because nothing goes wrong on the day you file.
Category A and category B
Every validation rule the department publishes carries a category, and the category is the whole story.
Category A stops the file. The upload is rejected, you see it immediately, and you fix it the same afternoon. Annoying, and harmless.
Category B does not stop anything. The return is accepted, the acknowledgement arrives, the client is told it is filed, and the return is treated as defective under section 139(9). The notice follows later, the client has moved on, and the fifteen days to respond start running from a date nobody was watching for.
A tool that only checks the things that would have been refused is checking the half that was never going to hurt you.
Important
A successful upload is not a valid return. Category B rules are satisfied by the portal and breached by the return, which is exactly why they surface as a notice weeks later rather than as an error at the portal.
The fifty lakh line, and what it excludes
The best known rule is also the one most often applied slightly wrong.
For ITR-1, the department's rule 117 reads: "Total income excluding LTCG C3 (a)(iii) should not be greater than Rs 50 lakhs." For ITR-4, rule 267 says the same thing in its own words: "Total income excluding LTCG u/s112A shall not be more than Rs. 50 Lakhs."
Both are category A, so a return over the line is simply refused.
The detail worth holding on to is the word excluding. The long-term capital gain under section 112A is taken out before the comparison. A client at forty eight lakh of other income with four lakh of listed long-term gains is not automatically out of ITR-1 on this test, and treating fifty lakh as a gross ceiling moves people onto ITR-2 who did not need to go.
There is a separate ceiling on how much 112A gain the form itself can carry, and that one is not in the rules document at all. It is in the form's own schema, as a maximum on the field. A form that has no room for a figure cannot carry it, whatever the eligibility rules say.
The TDS section codes that quietly rule you out
This is the test almost nobody applies by hand, and it is entirely mechanical.
The department reads the TDS schedule of your own return and rules the form out based on the section code under which tax was deducted. Two separate rules do it:
Both are category B. The return uploads. The defect notice comes later.
The useful part is that you do not need to interpret anything. The section codes are sitting in the client's own 26AS, which you have already downloaded. A client with a single 194C entry for a small contract payment has a business receipt by the department's reading, whatever the books call it.
- Income at a special rate: codes for 194B, 194BB, 194BA, 194IA, 194IC, 194LA and 194S rule out both ITR-1 and ITR-4.
- Business income by implication: codes for 194Q, 194C and 194R rule out ITR-1.
Pro tip
Read the section codes off 26AS before you pick the form, not after the computation. It takes a minute and it is the single most common reason a filed ITR-1 turns out to be the wrong form.
What the form has room for
A second class of limit never appears in the validation rules, because it does not need to: it is built into the form.
The number of house properties an ITR-1 can carry is a maximum number of items on an array in the schema. The most 112A gain it can hold is a maximum on a field. ITR-1 has no schedule for business income at all, so the question of whether a client with a business may use it does not need a rule. There is nowhere to put the figure.
This matters for how you check. A limit read off the form is true for that assessment year by construction and cannot drift. A limit typed into a tool from last year's circular is true until the department changes it and nobody notices. Every year is its own set of schemas, and a new year is a new set of files rather than an edit to the old ones.
The four questions no file can answer
Four things rule out ITR-1 and ITR-4 and cannot be derived from any document you hold:
None of these is in the bank statement, the Form 16, the 26AS or the AIS. A tool that suggests a form without asking them is guessing, and a tool that assumes the answer is no is guessing in the direction that produces a defective return.
The honest behaviour is to make the suggestion anyway, with the unanswered questions listed as things to settle before the file can be saved. A CA can answer all four in under a minute. What they cannot do is remember to ask them on the four hundredth return of the season.
Reading 26AS and the AIS covers where the rest of the inputs come from, the prefilled JSON covers what it may and may not fill, and a broker statement covers the one head it will not help you with.
- Is the client a director in a company?
- Did they hold unlisted equity shares at any time in the year?
- Do they have assets or income outside India?
- Is there exempt income beyond what the working already shows?
Why the suggestion should be arguable
A form chooser that says "ITR-2" and nothing else is not much use. The CA has to be able to disagree with it, and to disagree they need the reason.
So every reason should be the department's own: the rule number and its text, quoted, or the place in the form where there is no room for the figure. Not a paraphrase, and not the tool's own opinion about eligibility.
That has a second effect worth having. When the rules change for a new assessment year, a chooser built out of quoted rules shows you exactly which quoted rule moved. One built out of paraphrases shows you nothing, and the paraphrase quietly goes stale.
And the CA keeps the last word. A suggestion is a suggestion; the builder refuses only a form the rules say the client cannot use, and it refuses it with the same sentence it would have shown as the reason.
Conclusion
Form choice is not a judgement call most of the time. It is a set of published, numbered tests, half of which are mechanical reads off documents already on your desk.
What makes it feel like a judgement call is that the expensive half never announces itself. Category A rules argue with you at the portal. Category B rules agree with you at the portal and argue nine weeks later.
Where the year is already closed and the form was wrong, an updated return under 139(8A) is the route back, and the rebate under section 156 is the figure most often disputed on the way.
Greenote suggests the form from the department's own rules for that assessment year, quotes the rule behind every reason, and asks the four questions no document can answer rather than assuming them. It builds the file on your PC and files nothing. See what the return workspace covers.
Turn bank statements into Tally vouchers on your own PC
Greenote reads 100+ Indian banks and posts clean vouchers straight into Tally, from your own PC. The statement is not uploaded, and nothing is typed by hand.
Free trial: 2 days or 10 statements, no card. Works with Tally Prime & ERP 9.
