Tracking Scrap and Consumption in a GST-Ready ERP

Walk through any Indian manufacturing shop floor and you will find two numbers that rarely reach the books on time. One is the raw material lost to a damaged lot, a tooling error, or a failed quality check. The other is the stock pulled for internal use, samples, or rework. Together they are your scrap and consumption, and in most small factories they live on a clipboard, a WhatsApp message, or a month-end adjustment entry.

That gap costs you twice. First in inventory accuracy, because your system shows stock that no longer exists. Second in GST, because the moment scrap is sold, moved, or written off, a tax treatment applies and the auditors expect a clean reason code, a dated document, and a linked tax account. A GST-ready ERP closes that gap by treating every scrap and consumption event as a real, numbered, auditable transaction instead of an afterthought.

The Problem: Scrap That Disappears Before the Books Catch Up

The typical pattern is familiar. A machine operator sets aside 18 kg of off-spec aluminium extrusion. Nobody records it immediately because the shift is busy. By month end, the store manager remembers roughly how much was discarded, writes a single line in the stock adjustment register, and the accountant posts a journal entry with the label "inventory write-off".

Three things go wrong here. The quantity is approximate, so your perpetual inventory drifts from reality. The reason is missing, so when the GST auditor asks why output tax was reversed on written-off input stock, you have no documentation. And the tax linkage is manual, so the liability account for output tax and the asset account for input tax are updated by memory rather than by rule.

Research on Indian small and medium enterprises puts the cost of this kind of manual compliance sharply. A study of GST compliance burden found an average annual compliance cost of roughly ₹87,450 and about 372 administrative hours per SME each year, much of it spent reconstructing exactly these missing links. For a manufacturer, scrap is one of the leakiest links of all.

What Changes When Scrap Is a First-Class Transaction

A modern cloud ERP does not bury scrap inside a generic stock adjustment screen. It gives scrap and consumption their own document type, their own workflow, and their own connection to the tax engine. Kikan System implements this through a dedicated scrap and consumption module that removes stock from a location with a full audit trail.

Two Distinct Types, One Document

The module recognizes that not all stock removals are the same. A record carries an explicit type that distinguishes between two intents:

SCRAP for disposal. This is material you are discarding, selling to a recycler, or writing off because it can no longer be used. The system classifies the resulting stock movement as a scrap disposal.
CONSUMPTION for internal use. This is material pulled for a non-saleable purpose such as samples, internal consumption, or process use. The movement is classified as a consumption movement rather than a disposal.

Separating these two matters for both accounting and GST. Disposal often leads to a subsequent sale and an output tax event, while internal consumption may affect input tax credit treatment. By tagging the intent at the source, you avoid reinterpreting a vague adjustment entry months later.

A Numbered, Dated, Locked Document

Each scrap or consumption record is a real document, not a silent database mutation. It gets a human-readable, company-unique number such as SCRAP-2026-0001 generated automatically on creation. It carries a business movement date that is applied to the stock-out entries when the record is completed. And it moves through a defined workflow of DRAFT, COMPLETED, or CANCELLED.

The workflow matters because it stops accidental posting. A record stays in DRAFT while your team reviews it, and only when the operation is set to COMPLETE does the system apply the stock-out movements inside a single transaction. If something is wrong, you cancel instead of unwinding a messy reversal.

Lines With Product, Lot, Quantity, and Reason

The heart of the record is its line items. Each line specifies the product being removed, an optional inventory lot, the quantity expressed in the packaging unit, a unit conversion factor to the stocking unit, and a reason. The reason is required, not optional, because it is the field an auditor reads first.

For lot-managed products, the lot is required and the system respects FIFO and FEFO picking discipline. This is the same lot traceability discipline you would apply to finished goods and raw materials, now extended to the moment stock leaves the usable pool. When a quality team rejects a specific lot of incoming raw material, the scrap record points at that exact lot, preserving the chain of custody that a GST review or a product recall demands.

The unit conversion is handled on the backend. Your operator enters the quantity in the unit they actually count, such as a box of 12, and the system computes the stocking-unit delta before recording the movement. That removes a common source of error where a clerk converts units by hand and the stock ledger quietly diverges.

Signed Stock-Out Movements, Recorded Transactionally

When a record is completed, the module records a signed negative stock change for every line. The movement type is chosen automatically based on the record type, so a SCRAP record produces a scrap disposal movement and a CONSUMPTION record produces a consumption movement. Each movement carries the source, the reference, and the reason, so the inventory ledger tells a readable story rather than showing an anonymous minus.

Because the header, the lines, and the stock movements are written inside one transaction, you never get the partial state where the document says completed but the stock was not adjusted. Either the whole record lands, or none of it does.

Audit Trail and Locking

Every record carries who created it and who last updated it, with resolved user display information. Optimistic locking via a version counter means two people cannot silently overwrite each other while editing the same draft. Soft deletes preserve history for audit rather than physically erasing a record. Together these properties give you the evidence trail that an internal controls review or an ISMS assessment expects.

How This Connects to GST

Scrap does not exist in a tax vacuum. The same ERP carries a tax settings master that defines how tax is applied across your product, sales, and purchase lines. Each tax setting holds a human-readable name such as "GST 18%", a rate as a percentage from 0 to 100, and critically, two linked accounts from your chart of accounts: a sales tax liability account for output tax and a purchase tax asset account for input tax.

This is where the scrap and consumption module and the tax engine meet in practice. When you eventually sell accumulated scrap to a recycler, the sale invoice applies the configured tax rate and posts output tax to the liability account you already defined. When you consume or write off input stock on which you have claimed input tax credit, the linked purchase tax asset account is where the reversal story begins. The point is not that the scrap module performs tax reversal automatically, because tax treatment depends on facts that vary case by case. The point is that both sides, the physical stock event and the tax accounting structure, live in one connected system instead of two disconnected spreadsheets.

For Indian manufacturers this matters because the GST treatment of scrap has become stricter, not simpler. Most metal, plastic, and rubber scrap now attracts 18% GST, and metal scrap purchased from unregistered suppliers can fall under the Reverse Charge Mechanism. Registered buyers purchasing metal scrap above ₹2.5 lakh from dealers must deduct TDS at 2% under GST. When your scrap records carry dated reasons, lots, and quantities, you are prepared to answer the questions these rules generate, instead of reconstructing them from memory during a notice.

A Real-World Scenario

Consider a mid-sized precision components maker in Pune, running two CNC lines for automotive suppliers, with an annual turnover near ₹40 crore. In a typical month the shop floor generates around 120 kg of metal scrap from off-spec batches, broken tooling runs, and trimming waste, plus roughly 8 kg of internal consumption for test samples and fixture fabrication.

Before adopting a structured scrap process, the store team logged a single monthly adjustment. The quantity was an estimate, the lot was forgotten, and the reason column said "production loss". When the unit sold accumulated scrap to a recycler for around ₹2.8 lakh, the accountant applied 18% GST but had no documentation tying the sale back to the original input lots on which input tax credit had been claimed.

With a proper scrap and consumption workflow, the same unit now raises a numbered record the same shift the scrap is set aside. Each line names the product, the lot, the exact weight in kilograms, and a reason such as "tooling breakage" or "dimensional rejection". When the monthly scrap sale happens, the sales invoice applies the 18% rate from the tax settings master and the audit trail runs cleanly from shop floor to output tax ledger. The finance team stops spending the last week of every month reconstructing what happened on the floor three weeks earlier.

Why This Matters for India Businesses

Three pressures make structured scrap and consumption tracking especially relevant in India.

First, GST audit scrutiny. Inspectors look for consistency between physical stock movement, input tax credit claims, and output tax on scrap sales. A dated, numbered, reason-coded scrap record is exactly the artifact that turns a stressful question into a five-minute answer.

Second, MSME compliance maturity. As a small or medium enterprise grows toward the next turnover threshold, the informal practices that worked at ₹5 crore stop working at ₹40 crore. Lenders, large customers, and certification bodies increasingly expect inventory discipline that goes beyond a tally of finished goods.

Third, cost recovery. Scrap that is measured is scrap that can be sold, recycled, or reduced. Manufacturers who track scrap by reason quickly learn which machine, which shift, or which supplier is the largest contributor, and that visibility is where real margin improvement begins.

Is This Right for Your Business?

You will get outsized value from a dedicated scrap and consumption workflow if any of these is true. You manufacture or process physical goods and generate meaningful waste, off-spec output, or rework. You sell accumulated scrap to recyclers or brokers and need to apply GST correctly on those sales. You claim input tax credit on inputs that sometimes get consumed internally or written off. Or you are preparing for a GST audit, an internal controls review, or a certification that demands documented inventory discipline.

If your operation is purely trading with no transformation, or you carry minimal inventory, a lighter adjustment process may be enough. But for most manufacturers, scrap and consumption are too tightly linked to tax and margin to leave on a clipboard.

Frequently Asked Questions

Does the system track by-products separately from scrap?

No. The module handles two types: SCRAP for disposal and CONSUMPTION for internal use. It does not model a separate by-product output flow. If you produce a saleable by-product, you would typically receive it as finished goods through your manufacturing order and then sell it through the normal sales flow, while using the scrap and consumption module for true waste and internal drawdown.

How does scrap tracking connect to GST?

The scrap and consumption module records the physical stock-out with reasons, lots, and quantities. Separately, the tax settings master defines your tax rates and links each rate to an output tax liability account and an input tax asset account. When you sell accumulated scrap, the sales invoice applies the configured rate and posts to the defined liability account. The scrap module does not auto-calculate tax reversal, because that depends on case-specific facts, but it gives you the documented stock events your accountant needs to post GST correctly.

Can I record scrap against a specific lot for traceability?

Yes. For lot-managed products, each scrap or consumption line can reference a specific inventory lot, and the system respects FIFO and FEFO picking. This keeps your lot traceability chain intact from goods receipt through production all the way to disposal, which is essential for recalls, expiry management, and audit.

Key Takeaway

Scrap and consumption are not noise to be adjusted away at month end. They are physical and tax events that deserve the same numbered, dated, reason-coded treatment as any other inventory movement. When your ERP gives them a first-class document and connects that document to your tax accounts, you gain inventory accuracy, audit readiness, and a clear line of sight into where margin is leaking.

Stop Guessing at Scrap. Start Recording It.

Kikan System gives your manufacturing team a dedicated scrap and consumption workflow with numbered documents, lot-level traceability, required reasons, signed stock movements, and a tax settings master that links every rate to the right output and input accounts. If you are tired of reconstructing scrap from memory at month end, it is time for a core business system built for Indian manufacturers. Start on the free plan, which supports up to 2 users with no credit card required, at /#get-started.

Related reading