Liked our Blogs?
Please share your details to Subscribe to our Newsletter
Oops! Something went wrong while submitting the form.
How to set up an accounting system in India in 2026 — chart of accounts, tooling, compliance, reporting. A blueprint for startups and foreign companies.
Most accounting systems in Indian startups and foreign-owned subsidiaries are not designed. They accumulate. Someone opened Tally on a laptop in month two. Someone else added Razorpay in month four. Payroll moved to Excel. Then the company hit ₹5 Cr revenue, the statutory audit started, asking questions the spreadsheets couldn't answer, and three months later the founder was paying ₹4 lakh to redo the books retrospectively.
This is preventable. An accounting system, well-designed, has four layers that build on each other. Get the layers right at the start — even if some of them stay light for the first 12 months — and you avoid the expensive rebuild later. This guide is the blueprint.
It's written for two audiences: an Indian founder setting up books in the first six months of operations, and a foreign-owned subsidiary entering India that needs to install a finance function from Day 1 alongside the broader compliance stack. The principles are the same; the tooling and timeline differ slightly.
A working accounting system has these layers, each serving a different purpose, each built once and refined continuously.
Layer 1 — The Foundation. This is the data model. Chart of accounts. Master data (customers, vendors, employees, products). Accounting policies. Currency and rounding conventions. Document numbering schemes. The foundation is invisible to anyone who isn't a CA or a CFO, but everything else built on top of it inherits its decisions. A bad chart of accounts at month one produces a painful audit at month thirty-six.
Layer 2 — The Operations Layer. This is where transactions happen. Invoice generation. Bill recording. Payments. Receipts. Payroll. Expense reimbursements. Bank reconciliation. The operations layer is what most founders mean when they say 'accounting" — and it is the most labour-intensive layer to run but the least strategic.
Layer 3 — The Reporting Layer. This is where data turns into information. Monthly close. P&L, balance sheet, cash flow. MIS pack for management. Board pack. Parent-company group reporting (US GAAP / IFRS mapping for foreign-owned subsidiaries). FP&A model that consumes the GL feed. Variance analysis. The reporting layer is what investors, boards, and the parent's CFO actually look at.
Layer 4 — The Compliance & Audit Layer. This is where the system meets the regulators. GST filings linked to the operations layer. TDS deductions and quarterly returns. Statutory audit. Tax audit. Transfer pricing documentation. FEMA filings if there are foreign shareholders. ROC filings. The compliance layer is the most under-designed in most startups — usually layered on top by a separate vendor with predictable seams.
The key insight: you can't skip a layer. You can run each one lightly in the early months, but you can't pretend it doesn't exist. The systems where founders get into trouble are the ones where the operations layer ballooned without the reporting layer growing alongside it.
Before any software is chosen, the foundation has to be designed. This is a 4–6 hour CFO exercise, ideally done before the first invoice is issued.
The chart of accounts (CoA) is the spine of everything. A well-designed CoA in Indian GAAP / Ind AS for a small- to mid-sized business has somewhere between 80 and 250 active accounts, organised in a hierarchy. Fewer than 80 and your reporting is too coarse. More than 250 and your bookkeeping team is making classification decisions every day instead of running operations.
The standard hierarchy:
For foreign-owned subsidiaries, the CoA should map cleanly to the parent's group chart at Tier 2. Decide this on Day 1 — retroactively mapping 18 months of transactions to a new chart costs ₹2–5 lakh in reclassification work.
A short written document — typically two pages — capturing your starting policies:
This document gets reviewed by your statutory auditor in year one. Having it ready is the difference between a 6-week audit and a 12-week audit.
The single most-skipped piece. Build master tables for:
Clean master data is the foundation of clean GST filings, clean TDS deductions, and clean MIS reporting. Dirty master data is the foundation of every "why doesn't this reconcile?" conversation that happens at month-end.
This is the layer most founders evaluate first. It shouldn't be, Layer 1 should be — but it is. Here's how to choose the operations stack.
Five tools cover roughly 90% of the Indian accounting market for startups and SMEs:
For most Indian startups in 2026 with ₹0–25 Cr revenue, Zoho Books or TallyPrime is the right answer. Foreign-owned subsidiaries with parent reporting in US GAAP / IFRS often start with Zoho or Xero for native multi-currency. Above ₹50 Cr revenue, the conversation shifts to NetSuite or similar.
Six processes that have to work cleanly:
Each of these has a process owner, an SLA, and an exception trigger. Without ownership and SLA, the operations layer drifts within 3 months.
The discipline that makes this work is captured well in our monthly bookkeeping checklist for MSMEs — the standard rhythm that should be in place regardless of who runs the books.
Reporting is where most accounting systems quietly fail. Operations are happening, transactions are going in, but the numbers that come out at month-end don't tell anyone anything they can act on. The reporting layer turns the GL into a decision-making instrument.
Best practice in 2026:
A 10-day close is the bar for a modern finance function. 15 days is acceptable. 20+ days means the system isn't designed — it's accumulating.
A CFO-grade monthly MIS includes the following:
The MIS doesn't run itself. A finance manager + senior CFO oversight builds it monthly. (Our guide on building finance SOPs that scale with your business walks through the operating rhythm that makes this consistent.)
The single most underused report in Indian startups. A 13-week rolling cash forecast, updated weekly, is the most leverage a finance function can produce in any given week. It catches receivable stretches, tax timing surprises, and working capital pressure before they become problems.
For a deeper view on cash-flow operating discipline, our Cash Flow Management: A Practical Guide for Indian Businesses is the right companion read.
This is the layer that most distinguishes a real accounting system from a bookkeeping function. Compliance has to be designed in — not bolted on after.
A typical foreign-owned Indian Pvt Ltd files 40+ formal compliance submissions per year. The accounting system needs to be designed so that compliance filings draw their data directly from the GL — not from parallel spreadsheets that drift out of sync.
The most common compliance failure is not a missed filing — it's a filing whose numbers don't match the books. Output GST in GSTR-3B that's ₹3 lakh different from output GST in the GL. TDS deposited that doesn't tie to Form 26AS. Payroll filed with different numbers than the GL salary expense.
These mismatches are caught in an audit and trigger weeks of reconciliation. The fix is design-level: every compliance number must trace, in one click, back to the GL entry it came from. If your system can't do that, it's not a finance system — it's two parallel systems that occasionally agree.
Open the entity. Set up DSCs and DINs. Apply for PAN, TAN, and GST. Open the bank account. Design the chart of accounts. Choose the accounting tool. Document the accounting policies (2 pages).
Configure the tool with the CoA. Build master tables (customers, vendors, employees, products). Configure tax (GST rates, TDS sections), payroll, document numbering. Set up bank feeds. Train the bookkeeper.
The operations layer goes live. First GST filing, first TDS deposit, first payroll. Run the first monthly close — even if rough — and document where it broke. Iterate.
The reporting layer goes live. Build the MIS template. Start the 13-week cash forecast. Set the 10-day close target. Bring the founder into the monthly close review.
The compliance layer matures. First statutory audit done with clean books. First Tax Audit (Form 3CD). FEMA filings (if applicable) on schedule. Transfer pricing documentation is contemporaneous.
Refine, automate, scale. As revenue crosses ₹25–50 cr, consider an FP&A layer on top (Cube, Mosaic, Causal, or NetSuite-native). Above ₹100 Cr, the conversation shifts from "accounting system" to "ERP".
A practical question every founder asks: should the accounting system be built in-house or outsourced?
The honest answer for most Indian startups and foreign-owned subsidiaries under ₹50 Cr revenue: outsource Layers 2 (Operations) and 4 (Compliance) to a CFO-grade partner; build Layer 1 (Foundation) and Layer 3 (Reporting) with that partner's senior CFO. This typically delivers the following:
The trigger to move accounting in-house is usually one of three: revenue crossing ₹50 Cr, opening operations in 3+ states, or preparing for a Series B / C fundraise where in-house finance leadership becomes a stated investor expectation.
A few additions for the foreign-entrant case:
For the broader foreign-subsidiary picture, the architectural choices walk hand-in-hand with the entry decisions covered in the foreign company India guides.
Patterns we see often:
If you'd rather not design the foundation, build the tooling, and run the monthly close yourself, Jordensky's Mumbai-based bookkeeping and CFO team installs all four layers — foundation, operations, reporting, and compliance — for 100+ Indian startups and foreign-owned subsidiaries. One partner, one SLA, audit-ready from Day 90. Talk to a CFO →. 30 minutes, no commitment.
How do I set up an accounting system for a new company in India?
Start with Layer 1: design the chart of accounts, document accounting policies, and build master data. Then choose a tool (Tally Prime, Zoho Books, or Xero for most cases) and configure it. The operations layer goes live in month 2. Reporting and compliance layers mature over months 3–6.
What accounting software is best for Indian startups in 2026?
Tally Prime for manufacturing and trading; Zoho Books for SaaS, services, and D2C; Xero for foreign-owned subsidiaries with the parent already on Xero. Above ₹50 Cr revenue, evaluate NetSuite. Above ₹500 Cr, you're in ERP territory.
Do I need different accounting for a foreign-owned subsidiary?
The Indian books are the same — Indian GAAP / Ind AS — but the chart of accounts should map cleanly to the parent's group chart at Tier 2. Multi-currency setup, parent-group reporting overlay, and FEMA filings (FC-GPR, FLA, 15CA/15CB) are additions for the foreign-owned case.
What is a chart of accounts and why does it matter?
The chart of accounts is the structured list of every account where transactions get recorded. A well-designed CoA in Indian GAAP for a small to mid-sized business has 80–250 active accounts in a four-tier hierarchy. It's the spine of every report, every filing, every audit. Get it right at month one.
How long does it take to set up an accounting system?
Foundation work: 4–6 hours of CFO time. Tool configuration: 2–4 weeks. Operations layer live: month 2. Reporting layer at the 10-day-close standard: month 4–6. Full compliance layer including audit-readiness: months 6–12.
Should I outsource my accounting in India?
For most ₹0–50 Cr revenue startups and foreign-owned subsidiaries, yes — outsource the operations and compliance layers to a CFO-grade partner that handles accounting, GST, TDS, payroll, FEMA, and audit under one engagement. It's typically 35–50% of in-house cost and faster to onboard.
What's the difference between bookkeeping and an accounting system?
Bookkeeping is the operations layer — entering transactions, reconciling banks, and processing payroll. An accounting system is the whole architecture: foundation, operations, reporting, and compliance. Bookkeeping is necessary but not sufficient.
Does GST need to be integrated into the accounting system?
Yes. Every transaction with GST implications must record the tax in the GL at the time of entry. The monthly GSTR-1 and GSTR-3B should be filed from the system's GL — not from a parallel spreadsheet. Without integration, mismatches surface in audits, and weeks of reconciliation follow.
What is a monthly close, and how fast should it be?
The monthly close is the process of finalising all transactions, reconciliations, accruals, and provisions for the previous month so that the books accurately reflect the period. Modern finance functions target a 10-day close. 15 days is acceptable. Beyond 20 days, the system isn't designed.
Can I use Excel as my accounting system?
For the first 3–6 months of a pre-revenue company, yes. After that, no — GST filings require structured data, audits require traceability, and any reporting beyond a single founder's review needs a real accounting tool. Migrate to Tally or Zoho early.
The reason most Indian accounting systems break is not bad bookkeepers or bad tools. It's that no one ever designed the system. Transactions accumulated, tools were added, and the result was an operations layer with no foundation under it and no reporting on top of it.
The fix is to build it as four layers — foundation, operations, reporting, and compliance — and to build them in that order. Spend an afternoon on the foundation. Two weeks on the operations setup. The reporting layer matures over the next quarter. The compliance layer matures over the next year.
Do that, and you'll never have to rebuild it. Don't, and the rebuild will arrive somewhere between your first audit and your first fundraise.
