School Fees Under Which Head in Tally in India: Checklist, Risks & Realistic Timelines (2026)

Q: ### Can we keep fee receipts in SAP and only push summary journals to Tally?

Yes. Many groups run a **hybrid model**: SAP stays the sub-ledger for student-level fee management (receipts, concessions, refunds, ageing), while a monthly summary journal (debit Student Receivables, credit Fee Incomes, credit GST Output) posts to Tally for consolidation. This avoids full voucher migration and keeps Tally light. The trade-off: drill-down from Tally to student detail requires SAP access.

Q: ### What if our school division is a separate legal entity (Section 8 / Trust)?

Create a **separate Tally company** for the trust. Map its COA independently. Inter-entity fee flows (e.g., management fees, shared services) become inter-company journals — eliminate on consolidation. Do *not* merge trust and manufacturing COAs in one Tally company; it breaks audit trails and GSTIN-wise reporting.

Q: ### How long does a typical SAP-to-Tally migration take for a mid-size group?

**Discovery: 2–3 weeks.** **Build & UAT: 4–6 weeks** (mapping, master data load, voucher config, parallel run). **Cutover & sign-off: 1

Quick Answer
In Tally, school fees received are booked under an Income (Direct/Indirect) ledger grouped under 'Income Accounts' — typically named 'Tuition Fee Income', 'Fee Collection', or 'Academic Receipts'. The corresponding receivable sits under 'Sundry Debtors' (or a dedicated 'Student Receivables' group). GST liability, if applicable, routes through a separate 'GST Output' ledger under 'Duties & Taxes'. Never route fees through a Liability or Capital head.

## Why the Ledger Head Matters for Compliance and MIS

Choosing the correct group for school fees in Tally is not a cosmetic labelling exercise. It determines how the income reflects in your Profit & Loss, how GST returns (GSTR-1/3B) auto-populate, and whether your TDS certificates (Form 16A) generate correctly for any tax deducted at source on specific receipts. For a manufacturing or trading group running a school division — or an educational trust consolidating into a group Tally instance — misclassification cascades into:

Incorrect revenue recognition in quarterly board packs
Mismatches between Tally's GST ledger and the portal (GSTR-2A/2B reconciliation failures)
TDS credit denial for parents/deductors because the income head doesn't map to the correct section (194C vs 194J)
Audit qualifications on revenue cutoff at year-end

If you are migrating from SAP, legacy Excel, or a standalone school ERP into Tally Prime, the chart-of-accounts (COA) remapping step is where this gets fixed — or broken.

## Standard Ledger Structure for School Fees in Tally Prime

Ledger Name	Group (Tally Default)	Purpose	GST/TDS Impact
Tuition Fee Income	Income Accounts → Direct Incomes	Core academic revenue	Taxable supply (if > ₹20L turnover); maps to GSTR-1 B2B/B2C
Transport Fee Income	Income Accounts → Direct Incomes	Bus/van charges	Taxable (composite supply) — same HSN as tuition
Hostel/Mess Fee Income	Income Accounts → Direct Incomes	Boarding revenue	Taxable (renting of residential dwelling — check HSN 9963/9972)
Admission/Registration Fee	Income Accounts → Direct Incomes	One-time charges	Taxable; often missed in GST returns
Late Fee / Fine Income	Income Accounts → Indirect Incomes	Penalty revenue	Taxable; treat as 'other income' for MIS clarity
Student Receivables	Current Assets → Sundry Debtors	Fee dues per student	Drives aging, collection follow-up, bad-debt provision
GST Output — School Fees	Current Liabilities → Duties & Taxes → GST	CGST/SGST/IGST collected	Auto-picks in GSTR-1 if tax ledger mapped in voucher type
TDS Receivable (on Fee Refunds)	Current Assets → Loans & Advances	Tax deducted by parents on refunds	Rare; only if refund > ₹30K and PAN available

Implementation note: Create separate ledgers per fee type (not per class or student). Use Cost Centres for branch/class/stream segmentation. That keeps the COA lean and MIS flexible.

## How Does a SAP-to-Tally Migration Handle Fee Ledgers?

When a manufacturing group moves its school division from SAP (FI/CO, Student Lifecycle Management) to Tally, the fee ledger mapping is part of a broader COA remapping workshop. The process:

Extract SAP GL balances (FS10N, FAGLL03) for all fee-related GL accounts — revenue, receivables, tax, advance/adjustment accounts.
Map each SAP GL to a Tally ledger group using a signed-off mapping sheet (Excel). Example:
SAP GL 400010 (Tuition Fees) → Tally 'Tuition Fee Income' (Direct Income)
SAP GL 140100 (Student Debtors) → Tally 'Student Receivables' (Sundry Debtors)
SAP GL 215100 (GST Output) → Tally 'GST Output — School Fees' (Duties & Taxes)
Validate opening balances at cutover date: run trial balance in SAP and Tally side-by-side; reconcile to ₹0 difference per ledger.
Migrate transaction history (optional): if you need 3–5 years of fee receipts in Tally for TDS/GST audit trails, use Tally's Import Masters & Vouchers (XML/Excel) or a UDIMagic/ODBC tool. Most groups carry only opening balances + current FY transactions to keep Tally light.
Configure voucher types (Receipt, Contra, Journal) with mandatory tax ledger selection so GST posts automatically on fee receipt.
Parallel run for 1–2 months: post fee collections in both SAP and Tally; reconcile daily.
Cutover & sign-off: finance controller and auditor sign the TB reconciliation certificate.

## Checklist: Fee Ledger Setup & Migration Readiness

Use this before you engage a migration partner or start the discovery phase.

[ ] COA mapping sheet finalised — every SAP fee GL mapped to a Tally ledger group
[ ] GST HSN/SAC codes assigned per fee type (9992/9963/9972) and validated against CBIC notifications
[ ] TDS sections identified per receipt type (194C for transport/hostel contractors, 194J for professional fees — not on tuition)
[ ] Opening balances extracted as of cutover date (TB, debtor ageing, GST credit ledger)
[ ] Student master data cleaned: unique ID, PAN (for TDS), GSTIN (for B2B receipts), branch/class tags
[ ] Voucher numbering series defined for Tally (manual/auto, prefix per branch)
[ ] User roles & approval matrix set in Tally (who posts, who authorises, who reconciles)
[ ] Parallel-run plan documented: duration, reconciliation frequency, tolerance thresholds (₹0 for TB, ≤0.1% for GST)
[ ] Sign-off authority named (CFO / Finance Controller + Statutory Auditor)
[ ] Rollback plan if cutover fails (SAP remains live, Tally frozen)

## What Usually Goes Wrong — Real Risks from Live Projects

Risk	Symptom	Root Cause	Mitigation
Unmapped ledgers	TB difference ₹X lakh at cutover	SAP GLs created ad-hoc, not in mapping sheet	Pre-migration GL inventory; lock SAP GL creation 30 days before cutover
Tax-code mismatches	GSTR-1 shows ₹0 tax on fee receipts	Tally voucher type not linked to GST ledger; HSN missing	Mandate tax ledger in voucher type; test with 50 sample vouchers
Rounding differences in TB	₹1–₹500 variance per ledger	SAP allows 3 decimals; Tally rounds to 2	Apply rounding adjustment journal at cutover; document in sign-off
Student debtor ageing broken	Collections not knocking off oldest invoices	Migration imported invoices without allocation logic	Import receipt with allocation (bill-wise) or run allocation script post-migration
GST history gap	Auditor asks for FY 2022-23 GSTR-1 vs Tally	Only current FY migrated; prior years in SAP only	Carry GST register (summary) as opening balance; keep SAP read-only for 7 years
Cost centre loss	Branch-wise P&L blank in Tally	Cost centres not activated / not mapped in vouchers	Enable 'Cost Centres' in F11; map every fee receipt to branch/class CC

## Cost Drivers for a Migration Like This

TACHY quotes SAP-to-Tally migration as a fixed-fee project after a paid discovery phase. The final fee moves on these levers — no per-student, per-ledger, or per-day rates:

Number of legal entities / companies in Tally (each = separate company, separate TB sign-off)
Active ledgers & cost centres in scope (a 500-ledger COA takes 3× the mapping effort of a 150-ledger one)
Years of transaction history carried (opening balances only vs. 3–5 years of vouchers)
Statutory history depth (GST registers, TDS returns, TCS, PF/ESIC — each adds validation effort)
Custom Z-reports / SAP scripts that must be rebuilt in Tally (TDL or Excel-based)
Inventory complexity (if school stores/uniforms/books are stocked in SAP MM and move to Tally)
Parallel-run duration (1 month vs. 3 months of dual posting support)
Travel / on-site days required for workshop, UAT, cutover handholding

A discovery workshop (typically 3–5 days on-site + remote) produces the Statement of Work, migration plan, and fixed fee. No surprises after sign-off.

## FAQ

### Can we keep fee receipts in SAP and only push summary journals to Tally?

Yes. Many groups run a hybrid model: SAP stays the sub-ledger for student-level fee management (receipts, concessions, refunds, ageing), while a monthly summary journal (debit Student Receivables, credit Fee Incomes, credit GST Output) posts to Tally for consolidation. This avoids full voucher migration and keeps Tally light. The trade-off: drill-down from Tally to student detail requires SAP access.

### What if our school division is a separate legal entity (Section 8 / Trust)?

Create a separate Tally company for the trust. Map its COA independently. Inter-entity fee flows (e.g., management fees, shared services) become inter-company journals — eliminate on consolidation. Do not merge trust and manufacturing COAs in one Tally company; it breaks audit trails and GSTIN-wise reporting.

### How long does a typical SAP-to-Tally migration take for a mid-size group?

Discovery: 2–3 weeks.
Build & UAT: 4–6 weeks (mapping, master data load, voucher config, parallel run).
**Cutover & sign-off: 1

See TACHY live for your India school
Free demo · free data migration · go-live in 3–7 days
📅 Book Free Demo 💬 WhatsApp