An ERP for a CNC machine shop has to follow your customer's material from the inward challan, through your machines, to the return challan, scrap balance, inspection report and GST invoice. Accounts, stock and payroll come after that. If a system can't tell you which lots of which customer are on your floor today, how old they are and how much scrap you owe back, it won't run a job shop, however long its feature list.
This guide is written for job-shop owners in India, where GST job-work rules decide what the software must record. It draws on the GST rules as summarised in the ICAI's Handbook on Job Work under GST (June 2026 edition), the ERPNext documentation, and the feature list of Klevershop, the workshop software we build. It is not tax advice: confirm filings with your CA.
Signs your shop has outgrown registers, Excel and Tally
Whatever you run today, ask it these questions. If answering takes a phone call, a register and someone's memory, the shop has outgrown its system.
- For one customer, which of their lots are on your floor right now, and on which inward challan did each arrive?
- Which lots are getting close to the one-year limit explained below?
- On a lot you sent back in three part-dispatches, what was each return challan number?
- How much scrap or turning chips from that customer's material is still with you, and is it yours to sell or theirs?
- Which dispatched lots went without a PDI report?
- Can your accountant raise the job-work invoice without re-typing quantities from the dispatch book?
Most of these come straight from GST rules, which is why they matter more than any dashboard.
What a CNC job-shop ERP must handle in India
When a customer sends you their material to machine, you are the job worker under GST. The law defines job work as any treatment or process on goods belonging to another registered person. The customer who sends the bar stock, forgings or castings is the principal. You may also use your own material alongside theirs; the rules allow it. Either way, the software needs two kinds of stock: yours and theirs.
| Event on the shop floor | What the GST rules say | What your software must record |
|---|---|---|
| Customer material arrives | The principal sends it on a delivery challan with Rule 55 details (HSN, quantity, taxable value and so on), made in triplicate | Inward entry against the customer's challan number and date, kept apart from your own stock |
| Material sits in your shop | Inputs must return within one year, capital goods within three. After that the customer is treated as having supplied them on the day they were sent, and owes tax with interest. The Commissioner can extend this by one and two years | The age of every open lot, with a warning well before the deadline |
| You return finished parts | You send back a copy of the customer's challan and invoice your job-work charges | Dispatch linked to the original challan, plus a service invoice |
| You return in part-lots | The original challan can't be endorsed; you must issue a fresh challan | Your own return-challan series, each one tied to the original |
| Parts move between States | An e-way bill is compulsory whatever the value | An e-way bill prompt on inter-State challans |
| Customer files ITC-04 | Table 5 asks for your challan number and date, the original challan, the nature of job work, and losses and wastes | A report per customer that gives them all of this without anyone re-typing it |
ITC-04 timing is worth knowing because your customers will chase you around it. Since 1 October 2021, a principal with aggregate turnover above ₹5 crore in the previous year files every six months; everyone else files once a year, by the 25th of the month after the period. Older guides that say "quarterly" are out of date.
Customer-owned dies, jigs, fixtures and tools are the exception: no return deadline applies to them. Log them by customer anyway.
Scrap: whose it is and who can sell it
Scrap causes arguments because ownership isn't obvious. Under Section 143, the principal is responsible for keeping accounts of inputs, capital goods and waste or scrap lying with the job worker, and should keep records of scrap cleared from the job worker's premises.
Who sells it depends on your registration. A registered job worker may sell scrap from job work directly, on payment of tax. If you are not registered, the scrap goes back to the customer with the goods, or the customer sells it from your premises under their own invoice.
So the software needs a running scrap balance per customer: how much was generated on each lot, what went back, and what is still owed. Watch for systems that work scrap out from a fixed ratio. ERPNext's standard subcontracting flow, for example, takes scrap items and quantities from the bill of materials. Your customer wants the real figure, because it lands in their ITC-04 as losses and wastes.
Generic ERP vs shop-specific software vs a custom build
| Option | Fits when | Where it tends to break | What to check |
|---|---|---|---|
| Generic ERP with standard subcontracting | You mostly send work out to other shops | ERPNext's documented subcontracting flow runs from the sender's side: BOM, subcontracted purchase order, subcontracting order, "Send to Subcontractor" stock entry, subcontracting receipt, purchase receipt. The page doesn't mention challans or ITC-04 | Whether inward job work is set up at all, and who will configure it |
| Generic ERP with inward job-work features | You have someone in-house who can configure and maintain it | ERPNext version 16 added Subcontracted Sales Order and Subcontracting Inward Order documents for customer-supplied material, built around sales orders and work orders. Part-lot challans, scrap owed back and PDI still need checking | Which version the vendor installs, and whether part-lot returns produce fresh challans |
| Compliance add-on | You already run ERPNext on the principal side | The India Compliance app fills ITC-04 Tables 4 and 5 from subcontracting entries and supports e-way bills. It covers the filing, not your shop-floor routine | Whether your data entry habits match what the add-on expects |
| Shop-specific software | Job work for customers is most of your revenue | Fit depends on how close its screens are to your actual paperwork | Run the demo test below |
| Custom build | Your process is truly unusual, or you need deep links to other systems | Time and cost. A custom web application or ERP typically takes 8–16 weeks to build | Who owns the code, and who fixes it in year two |
A custom build is the wrong choice if an existing product already matches nearly all of your paperwork. Build only for the part that is genuinely yours.
Machine data: what an ERP can and can't tell you
An ERP knows what was planned and booked: lot received, job card opened, parts dispatched. It doesn't know what the spindle actually did between those entries. Nobody keys in idle time.
That needs machine monitoring, read straight from the control. Our FactoryOS reads Fanuc controls read-only over Ethernet (FOCAS) and runs in daily production on 2 VMCs at a CNC job shop. It shows run, idle and alarm time, cycle and part counts, and "Hidden Time" as a rupee cost at each machine's hourly rate. There is more detail in our CNC machine monitoring software post.
Buy the ERP first if the arguments are about material, challans and scrap. Add monitoring when the open question is where machine hours go.
How to test a vendor's demo: one real job, start to finish
Don't accept the vendor's sample data. Bring the paperwork for one finished job that was messy, and make them run it live:
- Inward. Enter the customer's actual challan: their number, date, HSN, quantity and value. Check that it lands in customer stock, not yours.
- Mixed material. If you added your own material, check that the system keeps the two apart.
- Production. Book the operations and any rework. Note how many screens it takes.
- Part-dispatch. Send back part of the lot. The system should issue a fresh challan tied to the original.
- Second dispatch. Send the rest. The original challan should now show as closed.
- Scrap. Record actual chips or offcuts, return some, and show what is still owed.
- PDI. If your customers want an inspection report with each lot, print it against the dispatch.
- Invoice. Raise the job-work invoice from the dispatch without re-typing quantities.
- Customer report. Produce what the customer needs for ITC-04 Table 5: your challans, the original challans, the nature of job work, and losses and wastes.
- Ageing. Show every open lot across all customers, oldest first, with the date each one hits the one-year limit.
If the demo stalls at step 4 or step 6, you have your answer. Also ask who owns your data if you leave, and in what format you get it back.
What Klevershop covers
Klevershop is our workshop management software for workshop owners and job-work units. Its shop module covers:
- material inward/outward and job-work entries, with PDFs
- sub-contracting, with stock tracking of material you send out
- scrap receipts and returns, with the balance owed back
- Pre-Dispatch Inspection (PDI) reports as PDFs
- parties, transporters, products, raw materials and job-work rate tables
- an invoice generator, plus staff, attendance and payroll
- sales, purchase, stock, scrap and outsourced-stock reports, with per-user roles
Accounting runs in Klevershop Books, which is ERPNext under our brand, with single sign-on to the shop module. It covers ledgers, payments, bank reconciliation, P&L, balance sheet, GST invoicing and stock accounting.
Put Klevershop through the same ten-step test as any other vendor. If your work is mostly sending jobs out rather than taking them in, a generic ERP with a compliance add-on may suit you better. For broader factory systems, see our manufacturing software work and our guide to inventory management software for manufacturers.
If your shop is outside India
The challan and ITC-04 rules are Indian, but the core need is the same anywhere a shop machines customer-owned material. You need a separate ledger for that material, return documents tied to what came in, a scrap balance per customer, and inspection records per dispatch. Swap in your country's paperwork and the demo test still works.