Fee Regulation Acts Across Indian States: Building Billing That Adapts

The billing rule starts with jurisdiction, not the fee amount

A school group cannot safely copy last year's fee table from one campus to another and change the rupee values. The two campuses may sit under different Acts, rules, notifications, court directions, affiliation conditions and approval processes. Even within one state, coverage can change with school type, recognition, aid, minority status, board, fee threshold or land-allotment condition.

The first billing question is therefore not “How much is tuition?” It is:

Which legal and regulatory rule set applies to this school, this student, this fee, and this academic year?

Only then can the system decide whether the head is permitted, optional or refundable; who approves it; how long the approval remains effective; what must be disclosed; and whether an increase can be billed.

This is an implementation guide, not legal advice or an exhaustive statement of every Indian jurisdiction. Fee law changes through amendments, rules, government orders, committee decisions and judgments. A school should have its current position confirmed by qualified counsel and the competent education authority before configuring production billing.

The national floor does not create a national fee code

The central Right of Children to Free and Compulsory Education Act, 2009 prohibits capitation fee and screening procedure for admission under section 13. That is an important national control, but it does not standardise ordinary private-school fee fixation across India.

States and union territories have adopted different mechanisms. Some centre on a school-level committee with parent representation. Some use a district, divisional or state fee committee. Some prescribe categories and disclosure. Some create increase thresholds or multi-year blocks. Others rely on an older education Act, rules, government directions and institution-specific conditions.

The billing system must handle both layers:

• national controls, such as the prohibition relevant to capitation fee; and
• jurisdiction-specific controls, including coverage, heads, approvals, timing and remedies.

Do not encode “CBSE school” as the legal answer. Affiliation identifies an academic board; the state or territory's fee regime may still apply, subject to its scope and any valid exceptions.

Seven examples, seven different control patterns

The table below is deliberately architectural. It identifies differences the ERP must represent; it is not a substitute for reading the current Act, rules and orders for a particular school.

Jurisdiction	Primary framework reviewed	Control pattern the system must support
Maharashtra	Educational Institutions (Regulation of Fee) Act, 2011	PTA and executive-committee process, proposed fee, escalation to divisional regulation and revision, approved fee and record controls
Rajasthan	Schools (Regulation of Fee) Act, 2016	Parent-teacher and school-level fee committee participation, management proposal, multi-year decision structure, divisional dispute and revision mechanisms
Uttar Pradesh	Self-Financed Independent Schools (Fee Regulation) Act, 2018, as amended	Coverage tests, classified fee components, optional services separated from recurring fee, disclosure, accounts and regulatory appeal
Bihar	Private Schools (Fee Regulation) Act, 2019	Public disclosure of previous and current fees, statutory increase threshold and regulatory review beyond it
Gujarat	Self-financed Schools (Regulation of Fees) Act, 2017	Fee Regulatory Committees, proposal/determination workflow, prohibited excess collection and appeal structure
Tamil Nadu	Schools (Regulation of Collection of Fee) Act and Rules, 2009	Fee determination by the statutory committee, school submissions and control against collecting beyond the determined fee
Delhi	School Education (Transparency in Fixation and Regulation of Fees) Act and Rules, 2025	School-level fee regulation committee, parent and teacher participation, multi-year proposal/approval, prescribed heads and head-wise disclosure

Maharashtra: committee lineage matters

The Maharashtra Act provides for Parent-Teachers Associations, an executive committee, regulation of fees in private unaided and permanently unaided schools, a Divisional Fee Regulatory Committee and a Revision Committee. It also covers accounts, records, offences and penalties.

For billing, the important object is not simply “approved annual fee”. Preserve:

• the management proposal and academic years covered;
• executive-committee constitution and decision;
• meeting, quorum, vote or consent evidence required by the applicable process;
• any dispute, divisional decision or revision;
• the final effective schedule by class and head;
• publication and parent-notice evidence;
• the source document and version authorising each change.

If an appeal or revision changes the result, do not overwrite the original fee plan. Create a superseding version and calculate the required prospective adjustment, credit or refund from its effective date.

Rajasthan: fee approval is a dated governance process

The Rajasthan Act regulates collection by schools, provides for Parent-Teachers Associations and school-level fee committees, gives management the ability to propose the fee in private schools, and establishes Divisional Fee Regulatory and Revision Committees. Section 8 lists fee-determination factors including location, infrastructure and facilities, educational standard, administration and maintenance expenditure, staff and salary components, expenditure on students, and reasonable surplus for development and expansion.

The ERP should not attempt to calculate legal fee merely from those factors. It should support the evidence pack and approval workflow, then enforce the amount actually approved for the relevant period. Store proposal, supporting cost schedules, committee decision, regulator outcome and effective academic years as separate records.

Uttar Pradesh: fee type is part of compliance

The Uttar Pradesh framework applies according to statutory coverage conditions. The Act's structure distinguishes possible fee components, optional fee components and a refundable charge. The available text identifies transport, boarding, mess or dining, excursions and similar activities as optional components, while security or caution money is refundable subject to the statutory terms.

That distinction should survive into invoices and the ledger. Transport is not merely another tuition instalment. It needs service enrolment, dates, route or plan, opt-in or applicability, proration rule and cessation. Refundable security belongs in a liability balance rather than fee income, with refund status and settlement at leaving.

Do not collapse every recurring charge into a locally invented head if the applicable law requires a composite or classified presentation. The billing catalogue must be jurisdiction aware.

Bihar: thresholds need a calculation record

The Bihar Private Schools (Fee Regulation) Act, 2019 requires disclosure of fee details and provides a statutory mechanism around fee increases. The published Act text allows an increase up to a stated limit over the previous year and places review beyond the limit with the Fee Regulatory Committee, subject to the current law and any operative directions.

A compliant system should retain:

• which prior-year amount forms the comparison base;
• whether the comparison is by fee head, total regulated fee or another prescribed basis;
• the calculated percentage with an unrounded audit value;
• exclusions or optional services, if the operative rule treats them differently;
• regulatory submission and approval where the proposal exceeds the permitted route;
• the public disclosure of previous and current fees.

Never embed a number such as seven per cent permanently in billing code. Store it as a cited, effective-dated rule subject to legal validation. A later amendment or order should change policy configuration, not require a software release.

Gujarat and Tamil Nadu: determination is not a spreadsheet note

Gujarat's 2017 Act creates a statutory framework for fixation of fees in self-financed schools, including Fee Regulatory Committees. Tamil Nadu's 2009 Act and Rules use a committee-based determination process and prescribed submissions.

For both patterns, the system needs a proposal-to-determination workflow:

1. proposed fee version;
2. supporting return and documents;
3. submission acknowledgement;
4. questions, hearings or requested corrections;
5. determination or approved schedule;
6. appeal or revision where applicable;
7. final billable version and effective period.

“Submitted” is not “approved”. A school should not activate a proposal merely because it has been uploaded to a portal, unless the current law provides a deemed or interim treatment that counsel has configured explicitly.

Delhi: the rule set can change materially

Delhi is the clearest warning against static configuration. The Directorate of Education now publishes the Delhi School Education (Transparency in Fixation and Regulation of Fees) Act, 2025 and Rules, 2025, alongside the Delhi School Education Act and Rules, 1973. Official directions state that the 2025 framework came into force in December 2025.

The new framework includes school-level fee regulation committees with management, principal, teacher, parent and Directorate representation, proposals for blocks of academic years, approved fee controls and disclosure. The 2025 Rules define “Fee Head-wise Disclosure”, “Regulated Fee Structure” and “Unjustified Fee Demand” and set permissible categories and limits.

The product lesson is not to reproduce those limits in a blog. It is to model them:

• a legal rule version with commencement and end date;
• a scoped institution population;
• permitted head catalogue and cap type;
• committee constitution and deadline;
• proposal block and approval state;
• disclosure template;
• transitional handling for an academic year already in progress;
• credits or refunds when a demand is not sustained.

Delhi changed from one operational framework to another without the concept of “school fee” changing. A rigid fee master would see the same field. A compliant system sees a new rule lineage.

The applicability matrix comes before the fee master

Build one record for each legal operating unit or campus:

Applicability field	Why it matters
State or union territory	Selects the primary jurisdiction profile
Campus and recognition number	Connects billing to the regulated institution
School category and levels	Pre-primary, elementary, secondary and senior secondary may be treated differently
Aided, unaided or self-financed status	Many Acts distinguish coverage and control
Minority status	May affect coverage or procedure; requires legal confirmation, not a checkbox assumption
Board or affiliation	Some Acts expressly enumerate recognised or affiliated boards
Land or grant conditions	Prior-approval obligations may arise outside the general fee Act
Annual fee or other threshold	Some frameworks use a coverage threshold
Academic-year calendar	Determines proposal, notice, billing and approval periods
Governing Act, rules and orders	Cited legal basis with version and effective dates
Competent authority	Committee, education officer, directorate or regulator for the school

Require legal or compliance approval before a profile becomes active. If one school group operates campuses in Delhi, Noida, Gurugram and Jaipur, “North India policy” is not an acceptable jurisdiction profile.

Separate five objects that most ERPs combine

1. Fee head definition

What the charge means: tuition, admission, examination, transport, boarding, refundable security or another permitted category. Store its regulatory class, income or liability treatment, recurrence, optionality, tax review status, refundability and allowed basis.

2. Fee schedule

The amount by campus, class, programme, student category or service for a defined academic period. This is a proposal until approved under the configured process.

3. Approval

The committee or authority decision: approved, modified, rejected, interim or under appeal. Store meeting or order reference, date, covered years, conditions, document and approvers.

4. Student assessment

The amount actually charged to one student after scholarship, concession, optional service, start date, withdrawal, sibling policy or lawful adjustment. Preserve the calculation inputs.

5. Ledger transaction

Invoice, credit note, receipt, allocation, refund, write-off or deposit movement. Once posted, a change to the fee schedule should create adjusting transactions, not rewrite history.

Combining these into one editable “fee amount” field makes it impossible to prove why a parent was charged, which approval applied or how a later order was implemented.

Model fee heads as regulated products

Each fee head should carry rules rather than only a name and price:

• jurisdiction category and statutory citation;
• mandatory, conditional or optional status;
• one-time or recurring frequency;
• permitted collection point;
• amount type: fixed, capped, approved, formula-based or actual cost;
• class or service applicability;
• approval required and approving body;
• disclosure label and invoice presentation;
• proration and withdrawal treatment;
• refundable status and liability account;
• concession eligibility;
• permitted late treatment;
• effective dates and version.

Prevent vague heads such as “miscellaneous”, “other” or “annual charges” unless the applicable approved structure explicitly supports them. A locally convenient label can become an unapproved demand.

Optional services need an entitlement object. If transport stops on 15 September, the system should know the approved cessation and proration policy rather than leaving finance to edit an invoice line. If an excursion is optional, refusal should not be processed as overdue tuition.

Version the rule, approval and amount separately

There are at least three timelines:

1. Legal rule timeline: when an Act, rule, notification or order applies.
2. Approval timeline: when a fee proposal is decided and for which academic years.
3. Billing timeline: when a charge becomes due for a student.

Do not force them into one “valid from” date.

A new Rule may commence during an academic year but contain a transitional arrangement. An approval may cover three academic years while instalments fall monthly or quarterly. A student may join mid-year under the same approved schedule with a different assessment.

Use immutable versions:

• JurisdictionPolicy v3, effective from a cited date;
• CampusFeePlan 2026–29, revision 2;
• Approval Order 47, covering specified years;
• Student Assessment, calculated on a timestamp against those versions.

When policy changes, simulate affected students before activation. Show proposed invoices, credits, deposits and revenue impact, then require dual approval.

Increases need a reproducible basis

Where a law or approval process controls increases, store the full comparison rather than the final percentage.

The calculation record should identify:

• prior approved fee and version;
• proposed fee and version;
• included and excluded heads;
• grade, class or campus scope;
• rounding method;
• threshold or approval rule and citation;
• result before rounding;
• exception pathway;
• supporting documents and decision.

Be careful with class progression. Comparing what a Grade 6 student paid last year with Grade 7 this year may mix a cohort increase with a grade-level price difference. The applicable framework may define the required comparison differently. Configure the legally approved basis; do not let analysts choose the denominator each year.

Billing cannot start before governance ends

Use controlled states:

1. Draft
2. Management approved
3. Committee proposed or reviewed
4. Submitted to authority, where required
5. Approved or determined
6. Published and notified
7. Active for billing
8. Superseded, stayed or withdrawn

The allowed path varies by jurisdiction. Make the workflow configurable, but do not allow users to skip a required gate.

Activation should check:

• correct campus and academic year;
• approval covers the fee head, amount and student class;
• required notice or disclosure completed;
• effective date reached;
• no stay, revision or later order supersedes it;
• invoice wording matches the disclosed head;
• optional consent or service assignment exists;
• refundable amounts post to the correct liability treatment.

An invoice run should produce an exceptions report before posting. “Blocked: no effective approval” is a feature, not a system error.

Disclosure and receipts are data outputs

Several frameworks require fee information to be displayed, filed or disclosed. Generate disclosure from the same approved fee-plan version that generates invoices. Manually typing a website table creates a second source of truth.

Keep evidence of:

• what was displayed or communicated;
• language and format;
• website or notice-board publication date;
• parent notice date and delivery status;
• prior and current amounts where required;
• committee composition or decision where disclosure is required;
• authority filing and acknowledgement.

Every receipt should identify the payer, student or account, fee head, period, amount, payment mode, allocation, transaction reference and issuing institution. Maharashtra's capitation-fee framework expressly requires an official receipt for fees, deposits or other amounts collected. In any jurisdiction, a generic receipt for “school fees” weakens both parent transparency and audit.

Refunds, deposits and reversals need their own controls

Refundable security is not a negative invoice waiting to happen. Track it as a student-specific liability:

• amount received and receipt;
• allowed deductions and evidence;
• interest treatment where required;
• leaving or refund trigger;
• bank and approval workflow;
• refund amount, date and reference;
• unclaimed or disputed status.

When an approved fee is reduced or a demand is held invalid, calculate adjustments at student level. Preserve original invoice, credit note, refund or reallocation, interest if legally required, and parent communication. Never edit the original invoice amount to make the ledger appear as though the overcharge never occurred.

Bulk refunds need the same control as bulk billing: affected population, rule, dry run, approval, payment reconciliation and exceptions.

Collections must respect fee type and current directions

The system should distinguish:

• invoiced but not due;
• due and unpaid;
• disputed;
• stayed or under regulatory review;
• covered by an approved payment plan;
• awaiting scholarship or concession evidence;
• optional service ceased;
• refundable balance;
• written off under authority.

Do not apply one automatic penalty or service restriction to every balance. The applicable law, court orders, education-authority directions and school policy may restrict coercive action, student exclusion, result withholding or late charges. Configure collection actions only after legal approval, with effective dates and protected categories.

Parent communications should show the calculation and route to dispute. A collection message must not represent a disputed or stayed amount as finally payable.

Evidence for a fee dispute

For any invoice line, the school should be able to produce:

1. the school's applicability profile;
2. the governing rule version and citation;
3. the approved fee plan and authority or committee evidence;
4. required disclosure and notice;
5. the student's class, service and effective dates;
6. concession, scholarship or optional-service decision;
7. the invoice calculation;
8. receipt, allocation, credit and refund history;
9. all later amendments or orders affecting the charge;
10. a complete audit log of who changed what and why.

This is why scanned approvals in a shared folder are insufficient. The document must be linked to the fee-plan version it authorises.

A safe configuration process for a new state

1. Obtain a current legal memorandum. Identify Act, rules, amendments, orders, judgments and regulator practice.
2. Define coverage. Map school type, level, board, aid, minority and threshold conditions.
3. Build the permitted fee taxonomy. Heads, optional services, deposits, caps and prohibited patterns.
4. Configure governance. Committees, membership, quorum, deadlines, proposal, approval, appeal and disclosure.
5. Define calculations. Increase basis, rounding, proration, refunds and transitional rules.
6. Create evidence templates. Proposal pack, minutes, filing, notice, disclosure, invoice and receipt.
7. Test edge cases. Mid-year admission, withdrawal, class progression, transport change, sibling concession, disputed increase and retrospective reduction.
8. Run a parallel simulation. Compare every assessment with the legally approved manual calculation.
9. Approve and lock. Legal, finance and school leadership sign the version.
10. Monitor change. Assign an owner to review official sources and trigger impact assessment.

Do not call the profile “India”. Call it by jurisdiction, scope and version.

Common failure modes

• One national fee template. State-specific heads and approvals are ignored.
• Board affiliation is treated as jurisdiction. CBSE or ICSE replaces the state-law analysis.
• The current amount overwrites history. Prior invoices can no longer be reproduced.
• Approval is a PDF with no scope. The system cannot tell which heads, classes or years it covers.
• An increase cap is hard-coded. An amendment, order or exception requires a software release.
• Optional charges are bundled into tuition. Consent, cessation and refund rules disappear.
• Deposits post as income. Refund liabilities cannot be reconciled.
• A proposal activates on submission. “Filed” is confused with “approved”.
• Website disclosure is typed manually. The public fee and invoice fee diverge.
• Bulk corrections edit invoices. Evidence of the original demand and remedy is destroyed.
• Collection rules ignore disputes. Stayed or contested amounts trigger automated pressure.
• Legal changes are tracked in email. No one knows which campuses and academic years are affected.

FAQ

Is there one maximum annual fee increase for private schools across India? No. The governing mechanism varies by state or territory and may depend on school coverage and approval. Do not apply a percentage from one state to another.

Does CBSE affiliation determine the fee rule? Not by itself. State or territory law and other institution-specific conditions may apply to a CBSE-affiliated school. Confirm scope for the particular campus.

Can transport be included in the main school fee? That depends on the applicable framework and approved fee structure. Some laws expressly classify transport as optional. The system should keep service entitlement and billing separable even where invoices are consolidated.

Should a fee change update existing invoices? No. Post a controlled credit, debit or refund from the legally effective date. Preserve the original transaction and the authority for the adjustment.

How often should the legal configuration be reviewed? Before each fee proposal and academic-year billing cycle, and whenever an Act, rule, order, judgment or authority direction changes. Delhi's 2025 transition shows why annual review alone may not be enough.

Where a system helps

An adaptable school ERP separates law, approval, fee plan, student assessment and ledger transaction. It can apply the correct jurisdiction version to each campus, stop unapproved heads before invoices post, generate disclosure from the approved source, preserve deposits and refunds, and reproduce the evidence behind any parent charge. The objective is not to automate legal judgment; it is to ensure that the judgment the school has approved is executed consistently and audibly. See SchoolOS for school ERP.

Related reading: What Is a Student Information System? (KB-033) and Why School ERP Migrations Fail Mid-Year (KB-488).

Sources

• India Code, Right of Children to Free and Compulsory Education Act, 2009
• India Code, Maharashtra Educational Institutions (Regulation of Fee) Act, 2011
• India Code, Rajasthan Schools (Regulation of Fee) Act, 2016
• India Code, Uttar Pradesh Self-Financed Independent Schools (Fee Regulation) Act, 2018
• India Code, Bihar Private Schools (Fee Regulation) Act, 2019
• India Code, Gujarat Self-financed Schools (Regulation of Fees) Act, 2017
• India Code, Tamil Nadu Schools (Regulation of Collection of Fee) Rules, 2009
• Delhi Directorate of Education, Fee Regulation Act and Rules 2025