Honest Take — Module 7: Tax Architecture & the One-Person Company — If You Operate Independently in India #
Of all the modules in this curriculum, this is the one I'm most uncertain about writing, and you should know why. Indian taxation is a moving target: CBDT issues clarifications, tribunal decisions modify practical interpretation, surcharge thresholds change with every Finance Bill. The structure of everything in this module — the bare acts I point you to, the strategic questions, the mock-filing checkpoint — is durable. The specific numerical answers are not, and if you're filing on the basis of a number, that number must come from your CA or the ITD portal, not from here. With that caveat: if I could re-architect the curriculum for pure ROI, this is the module I'd insist the independent operator do first. The savings-rate work helps you over decades; the tax work helps you next April. You'll spend 28-38 hours; the return, if it surfaces even one optimization your CA hasn't suggested, is probably 50-200x your hourly rate. Not because the module is brilliant — because the literacy gap in self-employed taxation is so wide that modest competence creates large arbitrage.
Let me say the direct thing about CAs, because the curriculum's stance matters. Most Indian CAs are competent professionals operating under a brutal economic constraint: compensation per filing is low, case loads are enormous, and the ten-hour analysis of whether your structure is optimal is not what they're paid for. They are paid to file. So when you ask "is my structure optimal?", you may get a polite shrug and a return to the form-filling. This is not malpractice; it is the structure of the market. The fix is not to switch CAs. The fix is to do the strategic analysis yourself and bring the answer for verification — at which point the CA spends two hours verifying instead of ten analyzing, and you get a useful conversation. That is the entire design of this module: it makes you the client who brings the spreadsheet and asks the strategic question.
The strategic question, stated baldly: is the one-person company the right vehicle for your income profile, or would you be better off as a sole proprietor under presumptive taxation? Under Section 44ADA, 50% of gross receipts are deemed expenses and the rest is taxed at slab, with an eligibility cap of ₹75 lakh of gross receipts — at typical contractor income the effective rates are meaningfully lower than the corporate route. Under the OPC: corporate tax under Section 115BAA at 22% plus surcharge and cess, roughly 25.17% effective on retained earnings (an opt-in that renounces certain deductions — compare before electing, because some elections don't reverse); salary you draw is deductible for the company and slab-rate income for you; dividends are paid from post-tax profit and taxed again at your slab, since the DDT was abolished by the Finance Act 2020 and dividend tax moved into the recipient's hands. Double-taxed money unless structured deliberately. For a senior contractor the gap between routes can compound to 10-20 percentage points of effective tax across years. The OPC has real non-tax advantages — limited liability (thinner in India than people assume: courts pierce the veil for fraud and statutory dues, and every personal guarantee you sign re-merges the liability you incorporated to separate), contracting standing, the retained-earnings shelter for reinvestment. The question is never "which is better in general" but "which is better at your numbers" — and asking it will be uncomfortable, because the entity is something you built, and rethinking the structure feels like admitting an earlier decision was wrong. It wasn't wrong then; the question is whether it's right now. Ask it without sentiment about the past. If you keep the company, the salary-vs-dividend-vs-retention split is real money: for an OPC at ₹50L revenue, the difference between naive and optimized splits runs ₹3-7L per year, and ₹3-15L across scales — over a compounding decade, ₹40L to a crore of additional deployed capital. One deflationary note carried from an earlier draft: the alphabet soup of incentives (35(2AB) R&D claims, SEZ benefits, 80-IAC startup exemptions) mostly does not apply to a one-person software operation — the right CA conversation confirms the absence rather than building optimization fantasies on the presence.
Two operational disciplines, and one piece of reassurance. The two-pool model — business cash and personal cash, separate accounts, separate books, separate decisions, with no "I'll classify it later" category — is the floor below which everything else gets corrupted. The violations are individually small: the business expense on the personal card "just this once," the ad hoc remuneration drawn when personal cash is short. The accumulation creates audit complications, muddies the corporate veil exactly when you need it intact, and makes the books illegible to your own future self. You'd never run a personal query against your production database; don't run personal expenses through the entity's books. Second, the compliance calendar: AOC-4, MGT-7A, DIR-3 KYC, DPT-3, GSTR-1/3B monthly, GSTR-9, quarterly advance tax, annual LUT renewal for zero-rated exports — each calendared with two reminders, because every missed filing is a fee plus a scramble. The reassurance: the bare acts are more readable than you expect. Section 44ADA fits on two pages. The legal drafting is opaque but the structure is logical, and after the third bare act you'll have the rhythm of how the language works. You will resent the time this module takes — it is slow, dense, bureaucratic, and there is no fun version of it. The resentment is the curriculum working: your time is worth a lot, and this module is reclaiming a lot. Resent your way through it.
One interaction worth naming because the modules feed each other: quarterly advance tax is the largest lumpy outflow in the independent operator's year, and it is the line most often missing from the gut-feel version of "how am I doing." The M8 runway model needs the advance-tax rows explicit and correctly timed, or it will overstate the trough months precisely when you're using it to decide something. Build the compliance calendar here; wire its cash consequences into the runway model there. The two artifacts are one system seen from two sides.
If you're not in India: the universal question this module instantiates is the corporate-form question every independent engineer eventually faces — does the entity's limited liability, contracting standing, and retained-earnings shelter justify its compliance cost and double-taxation drag at your specific income level — plus the adjacent one: is my accountant filing for me, or thinking for me? US readers have the LLC/S-corp election; UK readers the limited-company dividend-vs-salary split. The spreadsheet you'd build is the same shape. Build it.
Conclusion #
The most boring high-leverage module you will ever do. The boredom is structural — the topic is bureaucratic. The leverage is also structural — the literacy gap is wide and small applied effort yields large returns. Build the structure-comparison spreadsheet at three revenue scenarios, take it to your CA, and ask the strategic question. Mock-file your last completed year and diff it against what was actually filed. Keep the two pools separate. Don't outsource the thinking to the professional who isn't paid to think for you; bring the thinking and pay for the verification.
Predictions #
-
You'll find at least one optimization your CA hasn't suggested. Most likely candidates: a 44ADA opportunity unused, an LUT mishandling, a Schedule FA error, or advance-tax mistiming. One of the four will surface.
-
The entity-vs-44ADA question will be uncomfortable to ask, and the answer at your current revenue may favor the simpler structure. Decide deliberately either way; "we incorporated five years ago" is not a reason, it's an absence of one.
-
The salary-vs-dividend spreadsheet will produce an optimal salary lower than your default draw. The discipline is to retain or distribute the residual deliberately rather than over-drawing because over-drawing is psychologically simpler.
-
The mock filing will differ from what your CA actually filed in at least one line you don't initially understand. Chasing down that line is the module's payoff.
-
The two-pool audit will reveal one or two intermingled expenses you didn't notice. Fix forward; don't retroactively re-categorize closed years unless the amounts are material.
-
You'll be tempted to switch CAs after this module. Don't, on the first impulse — the literacy gap was on your side, and closing it changes the conversation. Switch only if the explicit checklist fails: never raised the structure question, doesn't know LUT, never asked about Schedule FA.
-
You'll resent the hours this module takes until you compute the implied hourly return on what surfaced. Then your CA's fee — and the module's time — will both feel like bargains.