A pallet of components leaves the factory for an operation the plant is not performing in-house for this job. Plating, perhaps, or heat treatment, or a grinding pass on a machine nobody on site owns. Physically the material is gone. Nothing else about it has changed. It is still the manufacturer's property, still committed to a work order that cannot be finished without it, and still part of the stock the accounts will eventually have to stand behind.
Sending it out is the easy part. The difficulty arrives the following week, when production asks where those components are and the most honest answer available is that they are with a vendor across town, and the quantity is more or less what went out. That answer is normal in a lot of factories, and it is why job work becomes a manual reconciliation exercise instead of a routine transaction.
Why work goes outside
Outside processing is usually a capability decision before it is a cost decision, which is worth remembering because it changes what you should be testing in an ERP.
- A process the plant does not own and has no intention of owning, such as plating, anodising or heat treatment.
- Capacity that is short for a season, a large order or the duration of a breakdown.
- An operation whose volume never justified buying the equipment, and probably never will.
None of these is unusual, and none is a problem in itself. The problem is structural: a step in the production sequence now happens somewhere nobody at the plant can walk over and look at.
Job work is not the same as buying the part
Job work is treatment or processing carried out by an outside party on goods belonging to the manufacturer. The processor supplies labour, equipment and sometimes consumables. The defining point is that the goods being processed belong to the manufacturer, which is what separates it from buying a component outright.
Physical custody changes; the manufacturer's claim on the material does not. That sounds academic right up to the point where stock is counted. Treat job work as a purchase and you write material out of inventory when it leaves, then discover at stock-take that a real asset has no home. Keep it identified as your own material sitting somewhere else, and it stays accountable, along with the obligation to know where it is and get it back.
The moment material leaves
Three questions have to stay answerable from the time the vehicle leaves the gate. What went out. Where it is now. Which work order is waiting for it. Systems that handle job work well are the ones that never let any of the three go unanswered. A fourth question sits underneath them, which is whether the material is still identifiable as the same batch or lot when it comes back; that is covered in batch and lot traceability.
The first is the job work challan, and what it carries decides how much use it is later. A challan recording the material description, the quantity and the expected return date, linked to the work order that needs the material back, is a control record. A challan that only proves something left the premises is a gate pass. The return date matters most: it is what makes ageing and overdue status measurable later, instead of an impression somebody forms while walking past a pile of paper.
The second question is inventory. Material at a job worker should behave like stock in a location, because that is what it is. Kept that way it appears in ordinary stock reporting next to raw material, work in progress, semi-finished and finished goods, where a storekeeper will see it without being told to look somewhere special. Kept in a spreadsheet beside the system, it is invisible to everyone but the person maintaining the spreadsheet.
The third question tends to be forgotten until a delivery date is missed. A work order waiting on an outside operation is not blocked by anything on the shop floor, so it never appears in the usual places people look for delays. The link between challan and work order is what keeps that dependency visible, and it ties back to how the material was planned to begin with, which is the subject of material structure and multi-level BOM.
What has to reconcile when it comes back
Take an illustrative case, with numbers chosen only to show the shape of the problem, not to describe any particular system's behaviour. Five hundred pieces go out for one operation. Four hundred and ninety-two come back processed.
The other eight need an answer. They might have been rejected at the processor, damaged in transit, or still in progress and following next week. They might never have left at all. Each has a different consequence, and only one of them is somebody else's problem.
The system must preserve that unexplained difference until somebody resolves it. It needs to refuse to let the eight disappear. A return recorded against the original challan can capture the processed quantity, any rejected quantity and the balance still outstanding, so a partial return leaves the challan open with a remainder on it, not closed with a rounding. Returns, rejections and shortages reconcile back to the issue they came from, and when the challan does close the work order is updated, which is when production can stop treating that operation as pending.
This is the discipline that decides whether job work is controlled or merely recorded. A system that forces the return to equal the issue invites workarounds, and the workaround will be a spreadsheet.
| What leaves | What should come back | What the system must still explain |
|---|---|---|
| Material, in a stated quantity | Processed quantity, plus any rejected quantity | The gap between what was issued and what has been accounted for |
| Physical custody of the material | Custody back at the plant | Where that stock sat, and appeared, while it was outside |
| A work order's dependency on one operation | That operation completed | Which production job is still waiting, and for how long |
| An expected return date | An actual return | How old the challan is, and whether it is now overdue |
| A processing requirement | A processing charge | Which work order that charge belongs to |
Outstanding material across many job workers
One open challan is a note on somebody's desk. Once there are dozens of open challans across several processors, it is a different problem. Individually every challan is known to somebody. Collectively nobody can state the position without spending a morning on it.
What is worth seeing is the aggregate: outstanding material by job worker, how long each challan has been open, and which ones are past the date they were due back. Overdue challans can be flagged, so follow-up happens on the strength of the ageing and not on somebody remembering.
The useful question to put to a system, then, is not whether it can display one challan. It is whether it can produce the whole outstanding picture without a person assembling it first. Anything needing assembly gets done monthly at best, and job work moves faster than that.
GST context
There is a statutory dimension to this in India, worth understanding briefly because it explains why return dates and challan ageing matter beyond production control.
Under section 143 of the CGST Act, goods sent out for job work must, within the relevant period, either be brought back to the principal or be supplied from the job worker's premises in accordance with the applicable provisions. That period is one year for inputs and three years for applicable capital goods, with moulds and dies, jigs and fixtures and tools falling outside the capital-goods period. Where neither happens within the applicable period, the law can treat the original despatch as a supply. Extensions are available under the Act subject to its conditions. Material moves under a challan, and responsibility for maintaining proper accounts of what was sent stays with the principal, meaning the manufacturer and not the processor.
This is general background, deliberately short, and not tax advice. Provisions and their qualifications change, and how they apply depends on the goods, the transaction and the business, so verify your own position with your tax adviser. Nothing above says an ERP calculates statutory deadlines for you or prepares statutory returns. What a system can reasonably do is keep the dates, quantities and balances accurate enough for the people responsible to act on.
Where the job-work cost goes
Outside processing costs money, and that cost belongs to the item the operation was performed on. If it never reaches the work order, the recorded cost of the item is missing a step that genuinely happened, and every comparison built on that figure inherits the omission.
Those charges form part of cost accumulation, and subcontract or job work cost can participate in the actual cost of the work order. How that interacts with expected cost, overhead treatment and variance by cost driver is a larger subject, and it is properly covered in work-order costing and variance rather than repeated here.
What to make an ERP vendor demonstrate
Do not accept "we support job work" as an answer. A vendor saying that does not tell you how the system behaves when quantities differ or challans remain open. What differs is behaviour at the edges, and the edges are where month-end arguments come from. The wider method for an evaluation like this is set out in the ERP selection and evaluation guide; the asks below are the ones specific to subcontracting.
- Issue material outside against a real production requirement, not a standalone transaction with no work order behind it.
- Show where that stock appears in stock reporting while it is outside.
- Show the link back to the work order, and the work order acknowledging that it is waiting.
- Receive back less than was issued. Show whether the challan remains open, what is rejected, what remains outstanding, and how any shortage is reconciled.
- Produce the outstanding position across several job workers, with ages, without anyone compiling it by hand.
- Show how the processing charge reaches the cost of the work order it belongs to.
Use your own difficult case, not a demonstration dataset: the job worker who returns short, the operation that never quite closes, the challan somebody found open from March.
How exactllyERP handles job work and subcontracting
In exactllyERP, material sent to job workers is tracked from issue through processing to return. The job work challan carries the material description, the quantity and the expected return date, and is linked to the work order that depends on it.
Material at the job worker is tracked as a separate inventory location and is visible in stock reports, so raw material, work in progress, semi-finished goods, finished goods and material sitting with a processor can all be seen across warehouse, shop floor and job-worker locations. Returns, rejections and shortages are recorded against the original challan, capturing processed quantity, rejected quantity and balance outstanding, and closing the challan updates the work order.
Outstanding material by job worker is available at any time, along with challan age and overdue position, and overdue challans can be flagged for follow-up. A job work operation can form part of the routing, so an outside step sits in the process sequence rather than beside it. Job work charges are captured in cost accumulation, and subcontract or job work cost can participate in the actual cost of the work order.
The case for considering it here is that the outside operation stays inside the production record instead of becoming a parallel process. The wider workflow it sits in is on the manufacturing ERP page, and the functional scope on the features page.
This page describes capability, not configuration. How job work should be modelled for a particular plant, which operations belong in routing, and how outside processing charges should be structured are implementation decisions that depend on the operation and on what the business needs to see. They are worth settling deliberately, because each one changes what the resulting position means.
Common questions
What is job work in a manufacturing ERP?
Job work is an operation performed by an outside processor on goods belonging to the manufacturer. The processor supplies labour, equipment and sometimes consumables; the defining point is that the goods being processed belong to the manufacturer. In an ERP that means the material has to remain identifiable and accountable while it is outside. It moves to a job-worker location, stays linked to the production order that needs it, and has to be accounted for on return.
How should an ERP track material sent to a job worker?
Against a job work challan that records what was sent, in what quantity and when it is expected back, linked to the work order depending on it. The material should then be visible as stock at a separate job-worker location in ordinary stock reporting, not in a side register. Together those answer the questions that matter later: what is outside, who has it, how long they have had it, and which job is waiting.
What should happen when the job worker returns less material than was issued?
The shortfall should survive as a number, not be absorbed. A return recorded against the original challan can capture the processed quantity, any rejected quantity and the balance still outstanding, so a partial return leaves the challan open with a remainder instead of closing it. Whether the difference is rejection at the processor, damage, a short despatch or material still in progress is a question for the people involved. The system's job is to make it visible enough that someone has to answer it.
Is job work the same as purchasing a finished component?
No, and the difference is what makes job work harder to control. When you purchase a finished component, you are acquiring that component from the supplier. In job work, you send your own goods out for processing and remain responsible for accounting for those goods while they are outside. That is why the material still has to be counted, valued and reconciled even though nobody at the plant can see it.
What should manufacturers ask an ERP vendor to demonstrate for subcontracting?
One real outside operation, run from issue to return, using the awkward case and not a clean one. Ask to see material issued against an actual production requirement, then show where that stock appears in stock reporting. Ask to receive back less than was issued, and watch what the system does with the difference. Ask for the whole outstanding position across job workers, with ages on it, and for how the processing charge reaches the cost of the work order. A vendor who can only show the tidy path has not shown the part that causes arguments.
How does exactllyERP handle job work and subcontracting?
Material sent to job workers is tracked from issue through processing to return. A job work challan carries the material description, quantity and expected return date, and is linked to the work order. Material at the job worker is tracked as a separate inventory location, visible in stock reports alongside raw material, work in progress, semi-finished and finished goods. Returns are recorded against the original challan with processed quantity, rejections and balance outstanding, and closing the challan updates the work order. Outstanding material by job worker, challan age and overdue position are available, with overdue challans flagged. A job work operation can form part of the routing, and job work charges can participate in the actual cost of the work order.
Where to start
Pick the one job-work transaction that regularly causes trouble. Not the standard case, the awkward one: the process that always returns short, or the challan that stays open past anybody's comfort. Then ask every system you are evaluating to run it from issue to return in front of you, and watch specifically what happens to the quantity that does not come back.
That single test tells you more than a feature list will. If exactllyERP is on your shortlist, bring that same transaction to the demonstration and ask for it end to end.