FREE 40-point ERP Buyer's Checklist — the questions to ask before you buy any ERP Download
+91-9724927225
Rajkot, India

Subcontracting & Outsourcing in ERP: Managing Outsourced Manufacturing End to End

Very few Indian manufacturers make everything themselves. A pump maker sends castings out for machining. An auto-component supplier sends parts out for plating and heat treatment. A garment house sends cut fabric out for embroidery and stitching. A furniture manufacturer sends panels out for polishing. In every one of these cases material leaves your gate, an operation is performed by someone else, and the material comes back to continue its journey to a finished product. It is still your material, still your cost, still your quality obligation to the customer — it just spent part of its life on someone else's floor.

That arrangement is where a surprising amount of money quietly leaks. Material goes out on a hand-written challan and nobody is entirely sure how much is still lying at which vendor. Processed goods come back short and the shortage is written off as "process loss" without anyone checking whether the loss was legitimate. The subcontractor's bill is passed on trust because reconciling it against what was actually issued is too tedious. And every quarter the ITC-04 return becomes a frantic reconstruction from a pile of challan books, with the ever-present risk that material sent out months ago and never returned has become a taxable deemed supply nobody noticed.

None of this is a failure of effort — it is a failure of visibility. The moment stock leaves your premises, a manual system loses sight of it, and everything downstream becomes an act of faith. An ERP closes that gap by treating outsourced work as a first-class part of the production flow: material issued on a proper challan, work-in-progress tracked while it sits at the vendor, returns reconciled against issues, outsourced operations costed into the product, and the whole ledger ready for ITC-04 on demand. This article walks through how subcontracting and outsourcing work end to end inside ApicalERP — and, with a worked rupee case study, what that control is actually worth.

Subcontracting, Outsourcing and Job Work: Getting the Terms Straight

These three words get used loosely on the shop floor, so it is worth pinning them down before going further, because an ERP treats them as distinct flows.

Subcontracting and outsourcing — the principal's side

Subcontracting is what you do when you send your own material or a semi-finished part to an outside vendor to have an operation performed, and receive it back to continue your production. The ownership of the material never leaves you; only its physical location and its state of processing change. Outsourcing is the broader business word for the same decision — choosing to have an activity done outside rather than in-house — and in a manufacturing context the two are effectively interchangeable. The key point is that you remain the principal: the material is on your books the whole time, the finished product is yours to sell, and the vendor is paid a processing charge, not a sale price.

Job work — the vendor's side

Job work is the mirror image: it is what the vendor does for you, treating your material as job-work stock they process and return against a challan. A business can sit on either side of this relationship — or both at once, outsourcing some operations while taking in job work on others. We covered the receiving end in depth in our guide to job work & subcontracting management; this article looks at the other end of the same rope — the principal who is sending work out and needs to keep control of it.

Why the distinction matters in the ERP

Because ownership does not transfer, a subcontracting movement must never be recorded as a sale and a return as a purchase — that would inflate turnover, distort GST, and misstate stock. Instead the ERP moves the material into a "stock with subcontractor" location that stays on your balance sheet, issues a delivery challan rather than a tax invoice, and books the vendor's charge as a processing cost. Getting this modelling right is what keeps your books, your inventory and your GST position honest while the material is out of your sight.

The Outsourced Manufacturing Lifecycle: 7 Steps From Decision to Costing

1

Make-or-Buy Decision

For each operation, weigh in-house cost, capacity and control against the subcontractor's rate, quality and lead time — using real numbers from the system rather than a gut feel that never gets revisited.

2

Raise the Subcontract Work Order

Issue a work order to the chosen vendor specifying the operation, the input material, the expected output, the rate and the due date — so both sides agree on scope, price and timing before anything moves.

3

Issue Material on a Challan

Material leaves against a subcontracting delivery challan — not a sale — moving it into a "stock with subcontractor" location that stays on your books while it sits on the vendor's floor.

4

Track WIP at the Vendor

The system holds a live balance of what is lying at each subcontractor, how long it has been there, and which work orders are overdue — so nothing disappears into a vendor's godown unnoticed.

5

Receive the Processed Goods

Returned goods are booked against the original challan and work order, moving the processed item back into your stock and reducing the balance still pending at the vendor.

6

Reconcile & Quality-Check

Material issued is reconciled against material returned, legitimate process loss and scrap — and incoming inspection accepts or rejects the work — so shortages and rework are caught, not absorbed.

7

Vendor Bill, Costing & ITC-04

The vendor's processing charge is verified against the reconciled quantity and costed into the finished product, and every challan feeds the quarterly ITC-04 return automatically.

Why Outsourced Work Leaks Money Without a System

The reason subcontracting is so prone to loss is that it breaks the single most useful assumption a manual stock system relies on: that material you can see is material you have. Once stock leaves the gate, it becomes invisible to everyone except the person holding the challan book — and invisibility is expensive in several distinct ways.

Material lying at vendors that nobody is counting

When a dozen challans a week go out to fifteen vendors, the running total of what is physically sitting on other people's floors climbs into lakhs of rupees of working capital — and in a manual system nobody holds that number. Material gets forgotten, vendors quietly hold stock long after the job is done, and some of it never comes back at all. That is working capital frozen in someone else's godown and, eventually, stock written off because no one remembers it was there.

Process loss that is never questioned

Every outsourced operation has some legitimate loss — turnings in machining, drag-out in plating, trimmings in stitching. But when 100 kg goes out and 94 kg comes back, the 6 kg gap is almost always accepted without a second look. Some of that loss is real; some of it is material that should have come back and did not. Without a reconciliation of issued-versus-returned per challan, the two are indistinguishable, and the difference — repeated across hundreds of challans a year — is a steady, unremarked bleed.

Vendor bills passed on trust

The subcontractor bills you per piece or per kilo processed. Verifying that bill means matching it against the quantity you actually issued and received back on that work order — tedious enough by hand that most bills are simply passed. Overbilling, double-billing a rejected lot that was reworked, or charging for quantity that never returned all slip through, because the check that would catch them is too much manual effort to do every time.

ITC-04 exposure building up quietly

Under GST, goods sent to a job worker must be reported in the ITC-04 return and returned within the prescribed period, or the sending itself can be deemed a supply and taxed. In a manual system the return is reconstructed each quarter from challan books, and material sent out long ago and never returned is exactly the thing that gets missed — until it surfaces as a compliance problem. The exposure is invisible precisely because the tracking is manual.

The Capabilities That Make Outsourcing Controllable

The difference between outsourcing as a leak and outsourcing as a managed, cost-effective strategy comes down to a handful of system capabilities — each one restoring visibility to a moment where a manual process goes blind.

📋

Subcontract Work Orders

Every outsourced operation starts as a work order that fixes scope, rate and due date before material moves.

  • Operation, input material and expected output defined up front
  • Agreed processing rate captured for automatic bill checking
  • Due date drives overdue tracking and follow-up
  • Linked to the production order the outsourced step belongs to
🚚

Challan & Material Movement

Material leaves on a proper subcontracting challan, never a sale, and stays on your books at the vendor.

  • Delivery challan with item, quantity and batch, tied to the work order
  • Stock moved to a "with subcontractor" location, not off the books
  • Returns booked back against the originating challan
  • No false turnover or purchase from a movement that is not a sale
📍

WIP-at-Vendor Visibility

A live view of what is lying where, for how long, and which jobs are overdue — nothing disappears.

  • Running balance of stock held at each subcontractor
  • Ageing of material out at vendors, oldest surfaced first
  • Overdue work orders flagged for follow-up
  • Pending-return quantity per challan always current
⚖️

Reconciliation & Costing

Issued versus returned versus loss reconciled per challan, and the vendor charge costed into the product.

  • Material issued reconciled against returned, scrap and process loss
  • Vendor bill verified against reconciled processed quantity
  • Processing charge rolled into finished-goods cost
  • ITC-04 data compiled from live challans, not reconstructed

How It Works End-to-End Inside ApicalERP

Outsourcing only stays controlled if the thread from work order to material issue to return to bill is never dropped. In ApicalERP each step hands its data to the next, so the material stays accounted for from the moment it leaves your gate to the moment its cost lands in the finished product.

The work order: agreeing scope before anything moves

An outsourced operation begins as a subcontract work order raised on the chosen vendor. It records the operation to be performed, the input material and quantity to be sent, the expected output, the agreed processing rate and the due date. Because the rate is captured here, the vendor's eventual bill has something to be checked against; because the due date is captured, an overdue job can be chased. Where the outsourced step is part of a larger build, the work order links to the parent production order, so the outsourced operation sits inside the plan rather than beside it.

Material issue: out on a challan, still on your books

When material is sent, ApicalERP issues it on a subcontracting delivery challan tied to the work order — capturing item, quantity and batch where relevant. Crucially, this is not a sale: the stock moves into a "stock with subcontractor" location that remains on your balance sheet. Your usable inventory drops, but the material is not lost from the books; it is simply shown as being physically at the vendor. This is the modelling that keeps stock, accounts and GST all telling the same true story.

WIP at the vendor: the number nobody used to hold

While the material is out, ApicalERP maintains a live balance of what is lying at each subcontractor, how long it has been there, and which work orders have passed their due date. This is the single most valuable thing the system restores: the number that a manual process simply does not have. At any moment you can see the total value of stock sitting on other people's floors, age it to surface the oldest, and act on it before it becomes a write-off or an ITC-04 problem.

Receipt and reconciliation: closing the loop honestly

As processed goods come back, each return is booked against the originating challan and work order, moving the processed item into your stock and reducing the pending-return balance. Then the reconciliation: material issued is set against material returned, scrap and legitimate process loss, so any unexplained shortage is visible rather than absorbed. Incoming quality inspection accepts or rejects the work, and a rejected lot can be sent back for rework rather than paid for as good. Only the reconciled, accepted quantity flows on to costing.

Vendor bill and costing: paying for exactly what was done

When the subcontractor's bill arrives, it is checked against the reconciled processed quantity at the agreed rate from the work order — so overbilling and charges for material that never returned are caught before payment. The verified processing charge is then rolled into the cost of the finished product, so your product costing reflects the true, fully-loaded cost of an item that spent part of its life outside your walls — not just the material and your own operations.

ITC-04: a report, not a reconstruction

Because every challan out and every return has been booked as it happened, the data for the quarterly ITC-04 return already exists in structured form. Instead of reconstructing it from challan books under deadline pressure, you compile it from live transactions — challan by challan, quantity sent, received and still pending — and the material lying unreturned beyond the prescribed period is visible well before it becomes a tax liability.

Industries That Live on Outsourcing

Some manufacturers outsource an operation or two; for others, subcontracting is the backbone of how they produce. For these sectors, control over outsourced work is not a refinement — it is the difference between a healthy margin and a leaking one.

Engineering, machining & fabrication

Castings and forgings routinely go out for machining, grinding, plating, heat treatment and special processes that need capability the principal does not want to build in-house. A single part may visit three vendors before it returns, and the accumulated outsourced cost is a large share of the finished price — so reconciliation and costing decide the margin.

Auto components

OEM supply chains push tight cost and quality discipline down to their vendors, who in turn outsource plating, coating, heat treatment and sub-assembly. Traceability of which vendor processed which lot, and reconciliation of material issued against returned, are audited by the OEM as a condition of continued supply.

Textiles & garments

Cutting, embroidery, printing, dyeing, washing and stitching are frequently spread across specialist units. Fabric and trims move constantly between the principal and a web of job workers, and the quantity lying at each — measured in metres and pieces worth lakhs — is exactly the number that goes missing without a system.

Pharma, cosmetics & contract manufacturing

Loan licensing and third-party manufacturing mean whole products are made outside, with the principal supplying inputs or specifications. Batch traceability, reconciliation and compliant documentation across the outsourced boundary are non-negotiable here, tying subcontracting directly to batch and lot control.

Outsourcing Task Manual / Challan-Book Process With Subcontracting in the ERP
Material at Vendors No one holds the total; stock forgotten at vendors Live balance of what is lying where, aged and valued
Make-or-Buy Decision Decided once on gut feel, never revisited Compared on real in-house cost vs vendor rate and lead time
Process Loss Shortage accepted as "loss" without a check Issued vs returned vs loss reconciled per challan
Vendor Bill Check Passed on trust; overbilling slips through Verified against reconciled quantity at the agreed rate
Overdue Jobs Chased only when a customer order is stuck Overdue work orders flagged automatically for follow-up
Product Costing Outsourced charge estimated or omitted Verified processing cost rolled into finished-goods cost
ITC-04 Compliance Reconstructed each quarter from challan books Compiled from live challans; unreturned stock visible early
Quality on Return Rejects paid for, then reworked and paid again Inspection gates receipt; rejects returned before payment
Outcome Frozen capital, silent losses, quarterly scramble Controlled cost, recovered capital, compliance on demand
Not sure how much of your stock is sitting at vendors right now? Get a free, no-obligation demo and watch ApicalERP show you every subcontract challan, WIP-at-vendor balance and reconciliation in one view — ITC-04 included. Not ready to talk? Grab the free ERP Buyer's Checklist first.

Benefits of Running Subcontracting Inside the ERP

📍
Nothing Lost at Vendors
A live, aged balance of stock at every subcontractor means material never disappears into someone else's godown.
💰
Working Capital Freed
Recovering stock stuck at vendors and chasing overdue jobs pulls frozen capital back into the business.
⚖️
Reconciled Process Loss
Issued-versus-returned checks per challan separate real loss from material that should have come back.
🧾
Verified Vendor Bills
Every processing charge is checked against reconciled quantity at the agreed rate, ending payment on trust.
🎯
True Product Cost
Outsourced operations are costed into finished goods, so margins reflect the fully-loaded reality.
📊
Data-Driven Make-or-Buy
In-house cost, vendor rate, lead time and quality compared on real numbers, not one-off gut calls.
🛡️
ITC-04 On Demand
The GST return compiles from live challans, and unreturned material surfaces before it becomes a liability.
🤝
Better Vendor Discipline
On-time and quality scorecards per vendor turn allocation into a managed decision and improve returns.

Implementation Checklist: Getting Outsourcing Right

Subcontracting control succeeds or fails on discipline at the boundary — the moment material crosses your gate in either direction. The businesses that get clean outsourced operations from the start follow the same handful of steps.

1. Model every outsourced operation as a work order

2. Never let material leave without a challan

3. Watch the WIP-at-vendor balance actively

4. Reconcile every return before you pay

5. Cost it in and compile ITC-04 from the system

What Outsourcing Control Actually Saves: A Worked View

The value of controlling outsourced work is abstract until it is put in rupees. Consider a mid-size engineering unit that sends out roughly ₹80 lakh of material a year across a dozen vendors for machining, plating and heat treatment. In a manual system, assume that at any time around ₹12 lakh of stock is lying at vendors with no one holding the total, that unexamined "process loss" runs about 2% higher than it should across the year, and that perhaps 3% of vendor billing is overcharged because bills are passed on trust. Those three leaks alone — a slice of the frozen ₹12 lakh eventually written off, the excess process loss, and the overbilling — quietly cost several lakh rupees a year, none of it appearing on any report as a loss.

Under an ERP-driven flow, the WIP-at-vendor balance is visible and aged, so stock is recovered instead of forgotten and working capital comes back into the business; reconciliation per challan pulls the excess process loss back towards its true level; and bill-checking against reconciled quantity stops the overbilling before it is paid. Add the outsourced cost now flowing correctly into product costing — so under-priced items are repriced — and the return on getting subcontracting under control is measured in lakhs a year, before counting the compliance risk removed from every ITC-04 cycle. The next section shows how this played out for a real business.

Real-World Success Story

🔧 Case Study: Rajkot Precision Engineering & Auto-Component Manufacturer

Company Profile: A ₹42 crore turnover manufacturer of precision machined components and sub-assemblies based in Rajkot (Gujarat), supplying pumps, valves and auto-component OEMs across India. The company machines and assembles in-house but outsources plating, heat treatment, specialised grinding and some sub-assembly to a network of around eighteen subcontractors. On a typical day, material is out at a dozen vendors at once. Accounts ran on Tally, while subcontracting was managed through hand-written challan books and a set of Excel registers maintained by the stores team, with a separate scramble each quarter to build the ITC-04.

The Outsourcing Problems Before ApicalERP:

  • Nobody held the material-at-vendor number: Stock lying at subcontractors was tracked only in challan books, and a physical review found close to ₹14 lakh of material at vendors — several lots months old, one vendor holding parts from a job everyone had assumed was long closed
  • Process loss was never questioned: Shortages on returns were booked as process loss without reconciliation; when a sample of challans was checked, unexplained shortage beyond legitimate loss was running at an estimated ₹6-7 lakh a year
  • Vendor bills passed on trust: Processing bills were rarely matched against issued and returned quantities, and a spot audit found overbilling and charges for rejected-then-reworked lots adding up to roughly ₹3 lakh a year
  • Outsourced cost missing from product cost: Because the processing charge was not reliably costed in, several regularly-outsourced parts were priced on material and in-house cost alone, quietly eroding margin on every sale
  • ITC-04 was a quarterly fire drill: Each return meant reconstructing sent-and-received quantities from challan books, and unreturned material sitting past the prescribed period was a standing compliance risk nobody could see coming

The ApicalERP Subcontracting Implementation:

  • Work orders for every outsourced operation: Each plating, heat-treatment and grinding job was raised as a subcontract work order with the input material, expected output, agreed rate and due date, linked to the production order it belonged to
  • Challan-based material movement: Material left only on a subcontracting challan into a "stock with subcontractor" location, so it stayed on the books at the vendor and returns booked back against the originating challan
  • Live WIP-at-vendor tracking: A running, aged balance of stock at each subcontractor surfaced the oldest and overdue jobs for active follow-up rather than annual discovery
  • Reconciliation and inspection on return: Every return was reconciled issued-versus-returned-versus-loss and gated through incoming quality inspection, with rejects returned for rework before billing
  • Bill-checking, costing and ITC-04: Vendor bills were verified against reconciled quantity at the agreed rate, the processing charge was rolled into finished-goods cost, and the ITC-04 was compiled from live challan data each quarter

Results After the First Year:

  • Working capital recovered: Active WIP-at-vendor tracking brought the material lying at subcontractors down from around ₹14 lakh to under ₹6 lakh, with old and forgotten lots recovered or written back — roughly ₹8 lakh of working capital pulled back into the business
  • Process loss brought back to reality: Per-challan reconciliation cut unexplained shortage sharply, recovering an estimated ₹5 lakh a year that had been leaking as unquestioned "loss"
  • Vendor overbilling stopped: Bill-checking against reconciled quantity ended the roughly ₹3 lakh a year of overbilling and double-charged rework
  • Margins corrected: With outsourced cost finally flowing into product costing, several under-priced parts were repriced, protecting margin on every future order
  • ITC-04 became a report: The quarterly return was compiled from live data in a fraction of the time, and unreturned material now surfaced well before it could become a deemed supply

Total Annual Financial Impact: Around ₹8 lakh of working capital recovered from stock stuck at vendors, roughly ₹5 lakh a year saved on reconciled process loss, about ₹3 lakh a year of vendor overbilling stopped, plus corrected margins on outsourced parts and a compliance risk removed from every quarter — all from restoring visibility to material the business could no longer see. The works manager's summary at the year-end review: they had always known outsourcing was essential to how they made parts, and had never realised how much it was costing them to do it blind — the fix was not to outsource less, but to finally watch what left the gate as carefully as what stayed inside it.

Frequently Asked Questions

What is the difference between subcontracting and job work in an ERP?

The two describe the same relationship from opposite ends. Subcontracting (or outsourcing) is what you do when you, the principal, send material to an outside vendor to have an operation performed and receive it back to continue production — the material stays on your books throughout. Job work is the mirror image: what that vendor does for you, processing your material as job-work stock. In an ERP, the subcontracting flow manages the principal's side — work order, material issue on challan, WIP at the vendor, receipt, reconciliation, costing and ITC-04 — while the job-work flow manages the receiving side. The same system can run both, and a business often sits on both sides at once.

How does ERP track material sent to a subcontractor?

Material leaves against a subcontracting delivery challan that records the item, quantity, batch and vendor — never as a sale, because ownership does not transfer. The stock moves into a "stock with subcontractor" location that stays on your books while physically at the vendor. As processed goods return, each is booked against the original challan, and the ERP reconciles issued against returned, legitimate process loss and pending quantity. That running ledger is also the source data for the quarterly ITC-04 return.

What is ITC-04 and how does ERP help with it?

ITC-04 is the GST return through which a principal declares goods sent to and received back from a job worker, protecting input tax credit even though the material left the premises. It reconciles challan by challan — sent, received, still pending — and material not returned within the prescribed period can be deemed a supply and taxed. An ERP that books every challan and return as it happens holds this in structured form, so ITC-04 is compiled from live data rather than reconstructed under deadline, and unreturned material is visible before it becomes a liability.

How do you decide whether to make in-house or outsource an operation?

A make-or-buy decision weighs the true landed in-house cost and the control of doing an operation yourself against a subcontractor's per-piece rate, quality and lead time. In-house gives control of quality and timing at a fixed cost; outsourcing converts that into a variable cost, buys specialised capability and adds flexibility, at the price of depending on a vendor. An ERP informs the call with real numbers — actual in-house cost from production costing, quoted and historical vendor rates, on-time and quality performance, and the capacity freed or consumed. The right answer usually differs by operation and by season, and is best revisited with data.

Can ERP handle multi-level and multi-vendor subcontracting?

Yes. Outsourced chains are rarely a single hop — a part may go to one vendor for machining, another for plating and a third for assembly, and the same operation may be split across vendors to balance capacity. A capable ERP models this as a chain of work orders and challans, each with its own issue, return and reconciliation, so work-in-progress can be located at any vendor and the accumulated outsourced cost rolls up into the finished item. It also compares vendors doing the same operation on rate, quality and on-time return, making allocation a managed decision.

Conclusion

Outsourcing is not a weakness in a manufacturing operation — it is often the smartest way to access capability, convert fixed cost to variable, and stay flexible as demand moves. What turns it into a liability is doing it blind. The moment material crosses your gate on a hand-written challan, a manual system loses sight of it, and everything after that — how much is lying where, whether the shortage on return was real, whether the vendor's bill is fair, whether the material came back before the GST clock ran out — becomes an act of faith. The losses that follow are quiet, spread across hundreds of challans, and never labelled as losses on any report.

An ERP restores the one thing outsourcing takes away: visibility. When every outsourced operation is a work order, every movement a proper challan, every rupee of stock at a vendor a number you actually hold, and every return reconciled before the bill is paid, subcontracting stops leaking and starts doing what it was meant to do — lower your cost without lowering your control. Alongside disciplined production planning and honest product costing, tight subcontracting is what lets a manufacturer outsource confidently instead of cautiously. ApicalERP manages the whole outsourced flow end to end — work orders, challans, WIP-at-vendor, reconciliation, costing and ITC-04 built in. See the full ApicalERP feature set and the manufacturing solution, then bring us one week of your subcontracting challans — we will show you exactly what has been leaving your gate unwatched.

Want to See Every Rupee That Leaves Your Gate?

ApicalERP manages outsourced manufacturing end to end — subcontract work orders, material issued on challan, a live WIP-at-vendor balance, per-challan reconciliation, verified vendor bills, outsourced cost rolled into product costing, and ITC-04 compiled from live data. No forgotten stock at vendors, no unquestioned process loss, no quarterly compliance scramble. See it live in a free, no-obligation demo tailored to your operations.

Book a Free Demo →