Manufacturing ERP in India: BOM, Work Orders and GST Together

If you run a manufacturing unit in India, you already know the daily scramble. Your engineering team maintains the bill of materials in one spreadsheet. Your shop floor tracks production in a separate workbook. Your accountant fights to reconcile material consumption, labour and GST across three tools that were never built to talk to each other. When the GST return deadline arrives, someone stays late stitching numbers together by hand.

This is not a tooling problem. It is an architecture problem. And it is the single biggest reason manufacturers in India lose money to silent errors, missed input tax credit and audit stress. A manufacturing ERP that keeps your BOM, your work orders and your GST on one ledger fixes it at the root. This guide walks through what changes when those three live together, grounded in how the modules actually work.

The Problem: Three Sources of Truth That Never Agree

Most Indian small and mid-size manufacturers run a divided stack. A bill of materials (BOM) sits in a spreadsheet owned by engineering. Production is tracked on the shop floor in a whiteboard or a legacy desktop accounting file. GST is computed in a separate billing tool at the end of the month.

Three failures follow, and they compound.

First, your BOM drifts from reality. Engineering changes a raw material grade, but purchasing still orders against the old specification, and accounting costs the finished good at the old price. In a multi-level BOM, one small change on a sub-assembly propagates silently into every parent product. Nobody notices until margins collapse.

Second, your work orders arrive late to the cost conversation. A production order is closed on the floor on Friday, but the material consumption reaches the books the following Wednesday. By the time it lands in the ledger, the period is shut and the variance is a mystery nobody can explain.

Third, GST never ties back to the physical event. A raw steel issue, a scrapped batch of castings, and an output sale each become a manual journal line detached from the inventory movement that caused it. When a GST auditor asks for the trail behind an input tax credit claim, the answer is a stack of printouts and a lot of hope.

Each tool works. The connection between them does not. For a manufacturer, the connection is where the truth lives.

What Changes: BOM, Work Orders and Tax-Aware Accounting Together

A manufacturing ERP fixes this by making the BOM, the work order and the tax setting part of one connected ledger. When the shop floor consumes raw material against an approved BOM, the inventory movement and the accounting entry happen in the same transaction. GST flows through on the same record, mapped to the correct output and input accounts.

Let us look at what each piece actually does in a real manufacturing ERP, based on how the modules are implemented.

Bills of Materials as the Recipe

A bill of materials is the recipe that produces one base quantity of a finished product from a set of component lines. Each BOM carries a finished product, a base production quantity, a unit of measure, and an ordered list of component lines. Each component line references a raw material product, its own unit, and the quantity consumed per base lot.

This matters because every work order sources its material consumption from a BOM. When engineering updates a component, the change is versioned and every new work order picks it up automatically. The old spreadsheet drift disappears because there is one source of truth, not three.

Manufacturing Orders as the Work Order

A manufacturing order is the production instruction that turns raw materials into finished goods. Each order carries a finished product, a demand quantity to produce, a packaging unit, a planned start date, a source location for raw material issue, and a destination location for finished goods receipt.

The order moves through a clear lifecycle. It starts as a draft, is confirmed to reserve material, and is completed when production finishes. The completion step does real work. It deducts the raw materials from the source location, creates or validates an inventory lot for finished goods, and receives the finished quantity at the destination. Header and line statuses update together, so the books and the bins agree at every step.

Partial output is handled honestly. If production falls short of demand, the system can split the remaining quantity into a child order linked to the parent. You get a clean backorder instead of a fudged number, and the shortfall quantity is recorded explicitly.

Tax Settings as the GST Backbone

GST compliance lives in the tax settings, and this is where the honesty matters. The tax engine is a general configurable tax-rate system, not a manufacturing-specific GST module. Each tax setting defines a rate as a percentage from zero to one hundred, a sales tax account that must be a liability account for output GST, and a purchase tax account that must be an asset account for input GST. The account subtypes are validated at write time, so output tax can never accidentally land in an asset account.

What this means for a manufacturer is that GST is attached at the product and transaction level, not bolted on at month end. When you sell a finished good, output GST posts to the correct liability account. When you buy raw material, input GST posts to the correct asset account, ready for your input tax credit reconciliation. The BOM and the manufacturing order do their inventory work, and the tax setting does its accounting work, on records that reference each other.

That is the architecture shift. Three tools become one ledger.

A Real-World Scenario

Consider a mid-size precision components manufacturer in Pune. The unit employs 140 people, runs two shifts, and produces around 18,000 finished assemblies a month for automotive and industrial buyers. Annual revenue sits near 48 crore rupees.

Before a unified ERP, the engineering team maintained a 200-line multi-level BOM in a shared spreadsheet. The shop floor ran production on whiteboards. Accounting used a separate billing tool for GST. Three failures recurred every single month.

A sub-assembly BOM changed when a bearing supplier was swapped. Purchasing kept ordering the old part for three weeks. The cost team priced the assembly at the old rate for two full months. The silent error cost roughly 14 lakh rupees before anyone caught it.

Production shortfalls were absorbed silently. An order for 2,000 units would close at 1,860, and the remaining 140 would vanish into a verbal note. Input tax credit on the consumed raw material never reconciled cleanly with the declared output, because the consumption event and the GST entry lived in different systems.

After moving to a single manufacturing ERP, the BOM became the only recipe. Every manufacturing order referenced it. Raw material consumption posted to the source location and the ledger in one transaction. Output GST on the sale and input GST on the purchase each landed in their dedicated accounts, mapped by the tax setting. The monthly GST reconciliation that used to take three days now takes hours, and the audit trail behind every cost figure is a single click.

Why This Matters for India Businesses

India stacks the pressure on manufacturers. GST compliance, MSME scheme benefits, Make in India sourcing expectations, and a tightening audit environment all demand a clean, connected record. A divided stack fails all four.

GST wants every transaction tied to a tax rate and a pair of accounts, one for output and one for input. A unified manufacturing ERP delivers that by default because the tax setting is part of the same record as the inventory movement. Your input tax credit reconciliation stops being detective work and becomes a report.

The MSME scheme and Make in India both reward manufacturers who can prove domestic value addition and clean cost trails. When your BOM, your work orders and your tax settings live together, you can show exactly what went into a finished good, what it cost, and what GST was paid and collected, without rebuilding the story from scraps.

Auditors are the final test. The moment a GST officer asks for the trail behind a credit claim, a divided stack collapses. A unified ERP hands you the manufacturing order, the BOM it consumed, the inventory lots it created, and the tax accounts it posted to, all linked.

Is This Right for Your Business?

A manufacturing ERP with unified BOM, work orders and GST is the right move if any of these sound like your week.

You reconcile material consumption against GST returns by hand at month end. Your BOM lives in a spreadsheet that only one engineer fully understands. Production shortfalls are tracked on paper or not at all. Your input tax credit reconciliation takes more than a day. An auditor request for a cost trail sends the team into a printout panic.

If two or more of those are true, the divided stack is already costing you more than the migration would. The fix is not another point tool. It is one ledger that connects the recipe, the floor and the tax office.

Frequently Asked Questions

Does the GST engine handle manufacturing-specific GST rules?

The tax engine is a general configurable tax system, not a manufacturing-specific GST module. It lets you define any tax rate from zero to one hundred percent, map output GST to a liability account and input GST to an asset account, and apply those rates at the product and transaction level. For most manufacturers, this covers GST on raw material purchases and finished good sales cleanly. Specialised manufacturing-specific GST treatments would need to be configured through these settings rather than being a separate dedicated module.

Can I track partial production and shortfalls?

Yes. A manufacturing order records a demand quantity and a produced quantity. When production falls short, the system can split the remaining quantity into a child order linked to the parent, with the shortfall quantity recorded explicitly. You get a clean backorder and an honest number, never a fudged figure.

Can I change a tax rate or BOM without a developer?

Yes. Both tax settings and bills of materials are configurable master data. You can add a tax rate, re-point its accounts, update a component line, or change a base quantity through configuration. The BOM is versioned, so a change flows into new work orders automatically while keeping the history of what was produced under the old recipe.

💡 Key Takeaway: The divided stack of BOM, work orders and GST in separate tools is where manufacturers lose margin, miss input credit and invite audit risk. A manufacturing ERP that keeps the recipe, the floor and the tax office on one ledger fixes the architecture, not just the symptoms.

Stop Reconciling by Hand

Kikan System brings your BOM, your manufacturing orders and your tax-aware accounting together on one ledger, so GST posts to the right accounts the moment material moves. Start on the free plan, up to 2 users, no credit card required, at /#get-started.

Related reading: