Job Work Management for Indian MSME Manufacturers: Getting Off the Register

Ask the owner of a fabrication unit in Rajkot, a garment unit in Tiruppur or an auto-component shop in Pune where their job work records live, and the answer is often a register. A long-format notebook, one line per challan, filled in by the stores in-charge. Sometimes a duplicate book of challans, sometimes an Excel sheet that a junior maintains until that person leaves.

That register works right up until the moment it does not. Someone asks how much of the 4,200 kg of MS sheet sent to the powder coater in April has come back. Nobody knows without flipping pages. The coater's bill arrives with a rate applied to pieces, while the challan was written in kilograms. A challan issued eleven months ago has quietly crossed the point where the tax position changes. And the year-end reconciliation between what you sent, what came back, what was scrapped as process loss and what the subcontractor claims to have processed turns into a three-day argument.

Job work is not a side workflow. For units built around outsourced processing, it is the core of production. Yet it sits in the gap between the accounting software (which tracks money, not your material lying in someone else's shed) and the production floor (which tracks output, not custody). This post is about what actually breaks in that gap, and what software should be doing about it.

What job work actually is, operationally

Job work is any process you get done on your goods by someone else — cutting, machining, galvanising, powder coating, embroidery, dyeing, stitching, printing, heat treatment, assembly, packing. You send material out. It stays yours. It comes back changed, and usually lighter.

Three things make it structurally harder to manage than a normal purchase:

• Custody is separated from ownership. The material is on your books but not on your premises. Nothing about a standard stock ledger is designed for "in stock, at someone else's address, in a different form".
• Quantity does not survive the round trip. You send 1,000 kg of raw bar and receive 940 kg of turned components plus scrap. Whether that 60 kg is legitimate process loss, retained scrap or shortage is a commercial and a compliance question at the same time.
• The unit of measure changes mid-process. Sent in kilograms, returned in pieces, billed per piece or per square foot or per running metre. Every conversion is a place where the register and the bill disagree.

The compliance layer most registers ignore

Under GST, moving goods to a job worker is not a supply, so no tax invoice is raised — the movement happens on a delivery challan that carries the prescribed particulars: challan number and date, the GSTIN of each registered party, description of goods, HSN, quantity, taxable value and place of supply. An e-way bill is required where the consignment value crosses the applicable threshold, and inter-state job work movements have their own treatment.

The part registers handle worst is the clock. Under Section 143 of the CGST Act, inputs sent for job work must return within the prescribed period, and capital goods have a longer window. Miss it, and the movement is deemed a supply from the date the goods went out — which means tax with interest, not a warning letter. A register does not raise its hand at month ten. Nobody sits down on a Tuesday to page through last year's challans looking for material that has not come back.

Then there is ITC-04, the return that reports goods sent to and received from job workers. The data it needs — challan-wise details of despatch and receipt — is precisely the data that lives in the notebook and nowhere else. Firms above the turnover threshold file half-yearly, others annually, and the filing is only as good as the underlying register. Where it is compiled retrospectively from challan books, a gap in the register becomes a permanent gap in the return.

None of this is exotic. It is just record-keeping that a paper system is structurally incapable of doing on time, because paper cannot alert you.

The commercial leak nobody measures

Compliance risk is the loud problem. The quiet one is money.

Rate drift. A job worker quotes ₹14 per piece in April. By October the bills arrive at ₹16, citing a verbal revision. If the agreed rate is not stored anywhere the accounts team can see, the bill gets passed because someone in stores vaguely remembers a conversation. Multiply a two-rupee gap by 40,000 pieces a year across five vendors.

Unreconciled loss. A wastage allowance is only worth agreeing if you can measure against it. If yours is 3% and one vendor consistently returns at 6%, you are funding that vendor's scrap sales. You will never see this from individual challans. You see it only when quantity sent and quantity received are totalled per vendor, per process, over months.

Material that never came back. Not fraud, usually. A pallet left in a corner, a batch rejected and quietly set aside, a vendor who shut down and still has your dies. Old open challans are working capital sitting in someone else's godown.

Un-invoiced processing. The reverse leak, for units who do job work for others: work completed, material returned, and the job work invoice never raised because the challan closed the loop physically and nobody translated it into a bill. This is revenue you have already earned and will not be paid.

What job work software should actually do

The useful test for any tool that claims to support job work is whether it treats a challan as a live open item or as a printed document. Here is what genuinely closes these gaps.

1. Treat the outward challan as an open balance, not a print job

The moment you issue a challan, the system should hold an open quantity against that vendor and that process. Every inward receipt reduces it. Every challan therefore has a running status: fully received, partially received, or open with a number of days on it. Nothing else in this list works without this one thing.

2. Handle partial and multi-batch returns properly

Job work rarely comes back in one lot. Send 5,000 pieces, receive 1,800 on Monday, 2,400 the following week, 700 after rework, 100 rejected. If the software forces a one-in-one-out match, staff will stop using it inside a month and go back to the notebook. Partial receipt against a challan is the workflow, not the exception.

3. Convert units, and record loss as a category

Sent 1,000 kg, received 940 kg of finished pieces. The system should let you define the conversion and classify the difference — process loss within the agreed norm, scrap returned, scrap retained by the vendor, or shortage to be recovered. Once that classification exists, per-vendor loss reporting is a byproduct rather than a project.

4. Store the rate contract, then price the bill from it

Rate per piece, per kilo, per square foot, per process, per vendor, with effect from a date. When the job worker's bill arrives, you compare it against the received quantity valued at the agreed rate, and the difference is on screen rather than in someone's memory. For units doing job work for others, the same structure raises the outward job work invoice from received-and-returned quantities, which is what stops un-invoiced work.

5. Age the open challans and alert on the deadline

An open-challan ageing view — 0-90 days, 91-180, 181-270, 271-365, over 365 — is the screen that earns its keep in a job work system. Add an alert well before the statutory return period expires and you have converted a compliance risk into a Tuesday morning task.

6. Produce the compliance data as a report, not a reconstruction

Challan-wise despatch and receipt data, ready to hand to your CA for ITC-04, should fall out of the same records that run your floor. If the compliance data has to be rebuilt separately from the operational data, you have two systems and they will diverge.

Where this sits in the rest of the business

Job work is not a standalone island. The vendor you send material to is also a payables account. The dispatch is also a logistics event. The customer order waiting on that batch is also a delivery commitment your sales person is being chased about. The person driving the material out is a field employee. The rejected batch becomes a quality complaint, which becomes a support conversation.

This is why job work registers so often live outside the accounting package: the package is built around vouchers and ledgers, and a challan with a 60 kg discrepancy and a pending vendor bill is not a voucher. It is an operational state.

Platforms that run the whole business rather than one function have an advantage here, because the surrounding records are already connected. GroviaOS covers that surrounding layer for Indian SMBs: purchase and vendor records, GST-compliant invoicing with HSN/SAC and place-of-supply handling behind the processing bill, projects and tasks so an overdue challan can carry a real owner and a due date, support tickets for the rejection that turns into a complaint, and field operations with GPS for the people physically moving material. What it does not ship today is a dedicated job work challan register with outward-challan balances and ITC-04 output — if that register is your first requirement, ask any vendor, us included, to show it working on your own challans before you buy. The principle holds either way: a challan pending for 200 days should be able to become a task with an owner and a due date without anyone re-typing it into a second system.

Making the shift without stopping production

The realistic path off the register is not a big-bang migration. It is this:

• Open the balance first. Enter only the currently open challans — the material genuinely lying outside. Do not backfill years of closed history. Whatever that list turns out to be, it is the only balance you need on day one.
• Put the challan on the floor, not in the office. If the stores in-charge cannot issue a challan from a phone at the loading point, the notebook survives. Mobile issue and mobile receipt are what make the record real.
• Lock the rate master before the next billing cycle. One session with each job worker to confirm rates in writing pays for the software.
• Run the ageing report monthly for one quarter. By the third month, the pattern of which vendor sits on your material and which process quietly loses more than the agreed allowance is unmistakable.

The register is not the problem in itself. Plenty of factories have been run beautifully out of one. The problem is that a register cannot alert you, cannot total by vendor, cannot age itself, and cannot tell your CA what to file. Everything a job work system does that matters is something paper structurally cannot do.

If your material is sitting in three vendors' sheds and the only record of it is a notebook in the stores, that is the place to start. Start a free trial of GroviaOS and get the vendor records, the GST billing and the follow-up on overdue material out of the notebook first.

Frequently Asked Questions

What is job work under GST, and does sending material out attract tax?

Job work is any treatment or process carried out by one person on goods belonging to another registered person — machining, coating, dyeing, stitching, assembly and so on. Sending goods to a job worker is not treated as a supply, so no tax invoice is raised for the movement; goods go out on a delivery challan with the prescribed particulars, and an e-way bill applies where the consignment value crosses the threshold. Tax applies to the processing charges, which the job worker invoices to you. Confirm the current treatment for your specific process with your CA, as rates and conditions differ by industry.

What happens if material sent for job work does not come back in time?

If inputs are not returned within the prescribed period — with a longer window for capital goods — the movement is deemed to be a supply from the date the goods were originally sent out, which means tax along with interest for the intervening period. That is the strongest argument for tracking open challans by age rather than by page number in a register. Software that ages open challans and alerts you before the deadline converts a tax exposure into a routine follow-up.

Can I manage job work in my accounting software?

Partly. Accounting packages are designed around ledgers, vouchers, GST returns and books of account, and they do that job well. Where small factories run past that design is the operational layer: a live open balance per challan, partial multi-batch returns, unit conversion between despatch and receipt, per-vendor process loss, and rate contracts that price the job worker's bill. Where a parallel register survives alongside the accounting package, it is usually that operational layer it exists to hold — and that is the gap a job work module is meant to close.

How does software handle the quantity difference between what I send and what I get back?

By treating the difference as a classified category rather than an unexplained gap. A good system lets you define the unit conversion for the process, then record the shortfall as process loss within the agreed norm, scrap returned to you, scrap retained by the job worker, or a shortage to be recovered. Once every receipt is classified this way, per-vendor and per-process loss reporting becomes automatic, and a vendor consistently running above the agreed wastage allowance becomes visible within a quarter.

What is ITC-04 and how does a job work system help with filing it?

ITC-04 is the GST return reporting details of goods sent to and received back from job workers, filed half-yearly or annually depending on turnover. It needs challan-wise despatch and receipt data — the same data a physical register holds and nothing else does, which is why it is often reconstructed at filing time. If your job work records are captured operationally as challans are issued and material is received, the return data is a report your CA can pull rather than a reconstruction exercise.

Does this apply to us if we are the job worker rather than the principal?

Yes, and the leak is usually on the revenue side. Job working units receive material on someone else's challan, process it, return it, and then have to raise a processing invoice for the work done. Because the physical loop closes when material goes back, the invoice is often the step that gets missed or under-billed against the agreed rate. A system that holds inward challans, records processed quantity, and raises the job work invoice from the agreed rate stops completed work from going unbilled.