Case Study: A Make-in-India Greenfield Plant on a Cloud ERP and GST

The Situation

Picture a precision-components manufacturer headquartered in Pune that just secured board approval to stand up a brand-new greenfield plant outside Ahmedabad. The flagship site in Pune runs on a mix of legacy desktop accounting and spreadsheets that have accreted over a decade. The new Ahmedabad plant is a blank slate: no software installed, no master data, no chart of accounts, no BOM library, no filing history. The COO has one mandate. The plant must go live producing saleable goods inside a single fiscal quarter, and it must be GST-clean from the first invoice.

This is not a brownfield migration where the first job is to untangle old data. This is a greenfield Make in India plant with roughly 90 staff on day one, a single product line of machined and assembled components, and two legal entities to register. The parent company in Pune holds the brand and the customer contracts. A new operating entity in Gujarat runs the plant and ships to customers across states. Everything has to be set up fresh, but it has to behave like a mature operation from week one. The COO chose to stand the plant up on a cloud ERP rather than copy the Pune legacy stack, because a greenfield site is the rare moment you can fix foundations without a migration hangover.

The Challenge

A greenfield plant that must be GST-clean on day one faces four pressures that each compound the others.

First, the legal-entity and tax setup has to exist before the first procurement order. The Ahmedabad operating entity needs its own GST registration, its own tax-rate configuration, and its own invoice sequence. The Pune parent needs to stay separate so inter-state stock transfers and inter-company billing do not bleed into each other.

Second, the production model has to be encoded before the first raw-material issue. Machined-and-assembled components mean a real bill of materials, real work orders, real consumption of raw stock from a raw store, and real receipt of finished goods into a finished store. If the BOM is wrong, the first production run eats the wrong raw quantities. If the work order does not consume and receive stock correctly, inventory drifts from hour one.

Third, GST has to be threaded through every commercial motion. Purchase bills carry input tax credit. Sales invoices carry output GST. Inter-state movement carries different treatment than intra-state. Reconciliation at month-end has to match purchase registers to what suppliers declared, or the input tax credit claim fails and cash flow suffers.

Fourth, the whole thing has to be live in weeks, not the 12 to 18 months that traditional on-premise ERP rollouts consume in Indian manufacturing. The COO did not have 12 months. The board wanted saleable goods inside a quarter.

The Implementation

The implementation sequence on the cloud ERP mirrored the order in which a plant actually comes alive: set up the organization, encode production, wire tax, then run orders. Every step below maps to a real capability in the ERP, not a roadmap promise.

Setting up the two entities on one account

The ERP is built for many organizations at once, and each organization's data stays fully isolated from every other. Within the plant's account, the team created two company profiles, one for the Pune parent and one for the Ahmedabad operating entity. Each company carries its own legal name, representative, address, tax numbers, locale defaults, rounding rules, and default tax setting. The legal-entity attributes live in the company master record and feed printed invoices and tax documents directly.

The critical discipline here was isolation. The Ahmedabad entity's invoices, purchase bills, and inventory never cross into the Pune entity's books by accident. Each company keeps its own chart of accounts, its own tax configuration, and its own invoice numbering. For a Make in India plant that sells across states, that separation is what keeps inter-state GST clean and audit-ready.

Encoding production with bills of materials

Before a single work order was cut, the engineering team loaded the BOM library. In this ERP, a bill of materials is a recipe that produces one base quantity of a finished product from a set of component lines. Each BOM carries a unique, auto-generated BOM number, the finished product, the base production quantity, an optional unit of measure, and an optional external reference such as a drawing or spec number. Each component line carries the component product, the decimal quantity required per base quantity, an optional unit, a sort sequence, and a remark.

For the Ahmedabad plant, the team built one BOM per finished component. Each BOM listed the raw steel and consumables consumed per finished unit, with quantities carried to three decimal places. The external-reference field held the drawing number so shop-floor and engineering always pointed at the same revision. Because the BOM defines the base lot size and component proportions, scaling a run up or down later did not require rewriting the recipe.

Running production with manufacturing orders

With the BOM library in place, the team cut the first manufacturing orders. In this ERP, a manufacturing order is a production instruction that consumes raw materials from a source location and receives finished goods at a destination location. It carries a unique, auto-generated order number, the finished product, the demand quantity to be produced, the packaging unit, the BOM used to source raw materials, the source location, the destination location, planned start and end dates, and a status that moves through a defined lifecycle: DRAFT, then CONFIRMED, then COMPLETED, or CANCELLED.

The lifecycle is driven by an operation field on each write. Saving persists a DRAFT. Confirming reserves raw stock at the source location. Producing consumes the raw materials per the BOM and receives the finished goods at the destination location, with the produced quantity recorded on the order and a lot created for lot-managed finished products. Deletion is blocked once an order reaches COMPLETED, and confirming it releases the reservations cleanly.

The feature that saved the plant during ramp-up was shortfall handling. When actual production came in below the planned demand quantity, the completion flow flagged a shortfall, returned the unproduced amount, and let the planner choose how to proceed. One option auto-creates a remaining child manufacturing order for the shortfall, with component lines scaled proportionally to the BOM. The parent and child orders stay linked. The team did not have to manually rebuild a second order every time a run came up short. During the first six weeks, when yields were still being tuned, that alone prevented dozens of spreadsheet-only workarounds.

Threading GST through tax-aware accounting

The accounting module carries a configurable tax engine and a true double-entry ledger. Each company stores its own tax settings, including separate output and input tax accounts. Sales invoices, purchase bills, and expense reimbursements generate journal entries automatically, so the ledger reflects commercial reality without a clerk retyping each transaction.

For the Ahmedabad entity, the finance lead configured the GST rates on the relevant products and tax accounts, set the output GST accounts for sales, and the input tax credit accounts for purchases. Because every commercial document flows through the same tax engine, the purchase register and sales register that feed GST reconciliation are consistent with the ledger from day one. Inter-state sales carry their rate. Intra-state sales carry theirs. The team still reconciles purchase-side input tax credit against what suppliers declared on the portal, because GST matching ultimately depends on supplier-side filing, but the internal register is no longer the bottleneck.

A boundary the team accepted honestly

It is worth stating plainly, because any case study that claims total automation is not telling the truth. Scrap and material consumption in production do not auto-post to the ledger. Scrap is recorded as an inventory operation through a dedicated scrap-and-consumption flow, and its accounting impact is booked through a manual journal entry. Labor and overhead costing for production also still require a human step. Only invoices, purchase bills, and expense reimbursements generate journal entries automatically. The plant accepted this boundary deliberately, because it keeps the ledger reviewable instead of cluttered with operational micro-transactions. If a vendor promised you that every gram of scrap auto-posts to the profit-and-loss on day one, ask to see the actual ledger entries. If they cannot show them, they do not have them.

The Outcome

The Ahmedabad greenfield plant cut its first saleable production run inside seven weeks of starting the ERP setup, and its first GST-compliant sales invoice in the same week. Three outcomes stood out for the COO.

Setup time collapsed. Standing up two entities, a BOM library of roughly 40 finished components, the manufacturing-order lifecycle, and a GST-aware chart of accounts took the core project team about five working weeks. The traditional on-premise alternative the COO had been quoted was a 12 to 18 month implementation. The cloud ERP's per-company, per-feature configuration model is what made the difference. There was no server procurement, no database tuning project, no separate reporting build.

Month-one GST close was clean enough to file without a firefight. The first GST reconciliation cycle exposed three supplier-side mismatches, all caught before the claim was submitted, because the internal purchase register already matched the ledger. The finance lead estimated that recovering even one wrongly claimed or missed input tax credit line on a plant of this size covers a meaningful slice of the monthly compliance cost. Multiply that across a year of filings, and the cash-flow protection is real.

Yield discipline improved faster. Because every manufacturing order recorded produced quantity against planned demand and auto-split shortfalls into child orders, the team had a clean weekly view of where yields were short. Within eight weeks, average yields on the three highest-volume components moved from roughly 88 percent to 95 percent. The shortfall-split flow did not cause the improvement. It made the improvement visible, fast, without a parallel spreadsheet.

Lessons for India Manufacturers

Three lessons generalize beyond this one plant.

GST-first beats feature-first for greenfield. A plant that cannot file GST cleanly in month one has a working-capital problem before it has a growth problem. Configure the tax engine, the output and input accounts, and the invoice sequences before you tune the production model. The tax configuration is the foundation, not a finish-line task.

Treat the BOM as a contract. The BOM library is where engineering, procurement, and production either agree or quietly diverge. Carry quantities to real decimal precision. Attach drawing numbers in the reference field. Make the BOM the single source of component truth, and enforce it through manufacturing orders. Plants that let the BOM drift into the shop floor's headcount lose yield control within a quarter.

Use MSME-friendly entry, then scale. The plant started on the free plan, which covers up to 2 users at no cost and requires no credit card. The COO and two leads validated the two-entity setup and the first BOMs before any spend. Once production ramped, they moved to a paid plan that raised the user limit and unlocked more storage and features. This staged path is well suited to MSMEs that need to prove the model before committing budget, and it removes the excuse of a heavy upfront license that kills so many greenfield ERP conversations.

Is This Right for Your Business?

This approach fits a specific shape of business. You are planning or operating a greenfield Make in India plant, typically in the 50 to 300 staff range, with one or more legal entities, real bills of materials, and a GST exposure that starts on day one. You want a cloud ERP that your team can configure in weeks, not an on-premise rollout that consumes a year.

It fits less well if you need a full manufacturing execution system with shop-floor machine integration and finite capacity scheduling, because those are not part of the built system today. It also fits less well if your accounting depends on automated multi-currency translation, because the ledger records each company in its own single currency and foreign-currency translation is handled manually through journal entries. If your plant is export-heavy with heavy forex exposure, plan for that manual step.

The honest test is this. If your biggest pain is that GST reconciliation is slow, BOMs live in three places, and you have no clean view of production shortfalls, then a greenfield rollout on a cloud ERP is a strong fit. If your biggest pain is factory-floor machine telemetry, look elsewhere first and revisit the ERP layer once the MES question is settled.

Frequently Asked Questions

How long does a greenfield ERP setup take for a new domestic manufacturing plant?

For a plant of this size, roughly five working weeks to stand up two entities, a BOM library of around 40 components, the manufacturing-order lifecycle, and a GST-aware chart of accounts, with the first saleable run inside seven weeks. This assumes the cloud ERP isolates each organization and is per-company configurable, and that your team treats the BOM library as a priority rather than an afterthought.

Does the ERP handle GST input tax credit and output GST automatically?

The ERP carries a configurable tax engine with separate output and input tax accounts per company, and invoices, purchase bills, and expense reimbursements generate journal entries automatically. This keeps your purchase and sales registers consistent with the ledger. Final input tax credit reconciliation against supplier-side filing on the GST portal still requires a human check, because it depends on what your suppliers declared.

Can we start on a free plan before committing budget?

Yes. The free plan covers up to 2 users at no cost and requires no credit card. Run your entity setup and first BOMs there, validate the workflow with two or three leads, and move to a paid plan once production ramps and you need more users, storage, or features.

Key Takeaway

A greenfield Make in India plant is the rare chance to fix foundations without a migration. Stand up each legal entity with its own isolated data, encode production as proper BOMs and manufacturing orders with real shortfall handling, thread GST through a configurable tax engine, and accept honestly that scrap and labor costing still need a human step. Do that, and your plant can ship saleable, GST-clean goods in weeks instead of the year a legacy rollout demands.

Start Your Plant on the Right ERP

If you are planning a greenfield plant or replacing a legacy stack before the next compliance squeeze, Kikan System gives you a cloud ERP built for many organizations, with per-company data isolation, bills of materials, manufacturing orders with shortfall splitting, and a configurable tax engine for GST-aware accounting. Begin on the free plan, up to 2 users, no credit card. Start at /#get-started, or compare plans at /#pricing.