You need to sign in or sign up before continuing.
Course · 10 lessons ~33 hr Intermediate

Tax Architecture & the One-Person Company — If You Operate Independently in India

Independently file the presumptive-taxation return for a software-export practice (ITR-4 under Section 44ADA) — or know precisely why your structure requires otherwise. Understand the LUT route for zero-rated software exports. Ask and answer the big strategic question: is a one-person company the right vehicle for your income profile, or would you be better off as a sole proprietor under 44ADA? If you run the company: optimize director-remuneration vs dividend vs retained earnings, run the compliance calendar, separate the two capital pools, and evaluate your CA against an explicit checklist. The tax structure is a state machine with explicit transition costs; optimization is path-finding across entity and individual states, and the global minimum is non-obvious without modeling — the same shape as cost-optimizing data flow through priced services. The 115BAA election is a configuration choice with downstream costs: pick once, model the consequences, revisit on regime change. The corporate-form question is the form-vs-function audit you'd run on any legacy architecture: "we incorporated five years ago" is not a reason, it's an absence of one. And the CA is a vendor: scope, SLA, escalation path, value-vs-fee. Most engineers evaluate their cloud contracts more rigorously than the professional who touches every rupee of their business. The two-pool model, finally, is dev-prod separation — you'd never run laptop code against production; don't run personal expenses through the entity's books.

reading · we frame, you read MIT or the canonical taught · we author, no canonical fits ↺ spirals back to earlier lessons
Course locked

Complete Cross-Border Income Mechanics — If You Earn Cross-Border Income in India first.

This course unlocks once you've finished its prerequisite. Open prerequisite →

10 lessons. Read in order; spiral back when you need to. By the end you'll have used the core ideas twice — once on the abstract, once on something you'll meet at work next week.