Job work manufacturers can use AI to build custom job work management software for inward material challans, operation-wise rate cards, work in progress by challan, scrap and process loss accounting, partial returns, outward challans, job work invoicing and the records that support ITC-04 filing. Pentoggle is an AI platform that generates production-ready software from a plain English description, which means a job work unit can build an application shaped around its own operations instead of adapting to a system built for someone else.
Most job work units in India already run Tally for accounting alongside a physical challan book, some run Busy or Marg, and larger businesses may run SAP Business One. Those systems handle purchase, sales, GST and accounting well. This is not a proposal to replace them. Pentoggle builds the material and challan application around them, covering the workflows they were never designed for.
A job work unit earns differently from a manufacturer that owns its material. A manufacturer's profit sits in the spread between material cost and selling price. A job worker never buys the material, so the entire business is the conversion charge, the throughput and the discipline of returning what came in. The material on your floor belongs to your customer. It sits on your premises as a liability and never appears in your stock ledger as an asset. That single fact reshapes what the software has to do.
Key takeaways
- Job work software is built around challans, not invoices. The challan is the document that governs when material arrives, how long it can stay and what has to go back.
- Material issued, material returned, scrap retained and process loss have to reconcile challan by challan, because that reconciliation is what supports ITC-04.
- Most job workers run this in a challan book and an Excel sheet, and the reconciliation is done once a year under pressure.
- Rate cards in job work are per operation and per part, and often per customer, which is why generic invoicing tools produce wrong bills.
- The number that runs a job work business is the value of customer material lying against open challans, and how old those challans are.
Why job work is badly served by existing software
Almost every job work unit in India runs Tally for accounting, and Tally handles the books correctly. What it does not do is track a partial return against a specific inward challan across three operations, with scrap retained at the second stage and a rejection replaced from a later challan. That is not an accounting problem. It is a floor problem, and it happens daily.
The alternative has been a job work module inside a manufacturing ERP. Those exist, and they assume a single clean flow: material in, one operation, material out. Real job work is messier. Material comes in against one challan and goes out across four. Two customers send identical material and it gets stored together. A rejected piece is replaced from your own stock and has to be squared later. A customer sends material for plating, you send it onward to a second job worker, and now there is a challan chain.
The gap often shows up when ITC-04 is due. Somebody sits down to reconcile challans against returns, and the numbers do not agree.
Filing frequency and thresholds under the job work provisions change from time to time, and the treatment of scrap and process loss depends on the terms in your agreement with the principal. Confirm both with your tax advisor rather than relying on a software default.
Most units are running some combination of the first two columns below.
What job work units use today, and what they can build instead
| Challan book and Excel | Job work module in a packaged ERP | Application built with Pentoggle | |
|---|---|---|---|
| Inward challan entry | Manual, duplicated into Excel later | Structured, fixed fields | Your challan format, your fields, your customer terms |
| Partial and split returns | Tracked by memory and notes | Often one-to-one only | Many-to-many, one inward against several outward |
| Operation-wise rate cards | Rate list in a separate sheet | Single rate per item is common | Rate by operation, part and customer, with revisions |
| Scrap and process loss | Recorded loosely, agreed verbally | Standard percentage assumption | Your agreed norm per part, with variance flagged |
| Challan ageing against the return window | Nobody is watching | Report exists, rarely configured | Live ageing with alerts before the window closes |
| ITC-04 preparation | Annual reconstruction exercise | Export in a fixed format | Continuous reconciliation, data ready when filing is due |
| Cost to start | Low, until an error costs you | Licence plus implementation | Describe the process, get a working application |
What a job work unit can build
Each of these can be built as a separate module or combined into one application. Most units start with the first two.
Inward material register
Customer, challan number and date, part, quantity, weight, expected operation and agreed return window, with the material tagged to a physical location on your floor.
Job cards by operation
The job card carries the challan reference, so every operation on the floor is linked back to whose material it is running.
WIP by challan
What quantity of which customer's material is at which stage right now, including what is with a second-tier job worker.
Material reconciliation
Received against returned, scrap retained, process loss and rejection replacement, computed per challan and totalled per customer.
Outward challan and job work invoice
Delivery challan on return with the correct references, and a job work invoice built from the operation-wise rate card rather than typed by hand.
Challan ageing dashboard
Open challans sorted by age, with the material value against each, and alerts before the return window closes.
Customer portal
Your principal logs in and sees what they sent, what is in process and what has returned, which stops most of the daily phone calls.
ITC-04 data view
Challan-wise inward and outward with quantities and descriptions, maintained continuously rather than assembled at filing time.
The reconciliation is the business
A job work unit does not fail because it priced the operation wrong. It fails because material went out the gate unaccounted, or sat on the floor past the window and became a tax event, or because a customer's reconciliation does not match yours and the dispute costs more than the job.
The reconciliation has four moving parts and most systems track only two. Received and returned are easy. The two that cause the trouble are scrap and process loss. If your agreement says scrap stays with you, its value is part of your economics and has to be recorded and valued. If it goes back, it needs a challan of its own. Process loss is different again: burning loss in heat treatment, weight loss in machining, wastage in cutting. Every part has a normal loss and your customer has an assumption about what normal is. When the actual loss exceeds it, somebody pays, and the argument is settled by whoever has the better record.
An application built for your unit records the agreed norm per part, computes actual loss on every return, and flags the variance the day it happens rather than at year end. That single change converts an annual dispute into a same-week conversation.
Rate cards are per operation, not per part
Generic invoicing tools carry one rate per item, which is why job work invoices get typed manually. Real job work rates are structured differently. A part may go through turning, hardening and grinding, each with its own rate. The same part may carry different rates for two customers because one gives you volume. Rates change mid-year and the revision applies from a date, which means an invoice raised in August for material received in June has to use the June rate.
Building this properly means the rate card is a table with an effective date, keyed on customer, part and operation. Once that exists, the invoice generates itself from the outward challan and the operations completed, and the argument about which rate applied stops happening.
Challan chains and second-tier job work
Sending your principal's material onward to another job worker is common and it is where records break down most often. The material is not yours, it is now not even on your premises, and the documentation has to hold the chain together. Your inward challan from the principal, your outward challan to the second job worker, their return to you, and your return to the principal all have to reference each other.
Off-the-shelf systems generally model one hop. An application built around your process can model the chain, show where material physically is at any moment, and keep the return window clock running against the original inward date rather than restarting it.
Why building this is now practical
A job work unit with twenty machines has never been able to justify custom software. A development team, a specification document and a six month build were never going to be repaid by a plant doing conversion work at rates set by the customer.
That calculation has changed. With Pentoggle you describe the flow in plain English, including your challan format, your operations, your customers' terms and your scrap treatment, and get a working application. When a customer changes their return format or a new operation is added, you describe the change and the application updates. This matters more in job work than in most manufacturing, because your process is defined by your principals and they change it without asking you.
Why job work units choose Pentoggle
Your challan format, your operations, your terms
The application is built around your agreements rather than a vendor's assumption of standard job work.
Works alongside Tally
Pentoggle handles the challans, material movement and reconciliation. Your accounting stays where your CA already works.
Built for Indian documentation
Delivery challans with the required references, GST invoicing with HSN codes, e-way bill workflows and challan-wise records that support ITC-04 preparation.
Customer visibility without extra staff
A portal your principals can check themselves.
Changes in days
A new customer with a different reconciliation format does not become a three month project.
The one number that runs a job work business
Value of customer material lying against open challans, and the age of those challans.
Utilisation matters, rates matter, and rejection rates matter. None of them carry the same risk. Material sitting unreturned past the applicable statutory window can create significant tax and compliance issues, even though you never owned the goods. Track the open challan value daily and the ageing weekly, and the rest of the business becomes manageable.
Ready to build job work software?
Your customer's material is on your floor right now. Every day it stays there, it is your liability and not your inventory.