Blog/GST & ITC
Your goods, their machine, your credit

Your goods left the gate. No sale happened.

Come with me after one batch of rods: out on Monday, back as bolts on Friday, and not a single sale in between. The loop runs on three papers and one clock. Lose any of them and scrutiny writes its own story.

Monday: the rods leave

Two tonnes of steel rods, challan number 214, out the gate at 9:15 for the threading shop across the industrial estate. The challan lists your GSTIN, their GSTIN, item, quantity, value. It looks, to an untrained eye, exactly like a sale. A clerk who has never been told otherwise will post it as one, and just like that you have sold your own steel to yourself, on paper, with tax implications nobody intended.

Nothing changed hands in ownership. Say it till it sticks: your steel left your gate and your steel will come back, with threading added. No supply of goods, no goods invoice in either direction. The only invoice this whole week will produce is the job worker's bill for labour. Everything else is movement paper.

Consider the alternative for a moment, because one of your clerks is considering it right now. Post challan 214 as a sale and your books show output tax on your own steel leaving the gate. Reverse it next month when the CA spots it and you have paid tax you never owed, filed it, and now get to explain the reversal. I have seen the reversal take longer than the job-work itself. The challan is not a sale. It never was. The five seconds that distinction takes is the cheapest tax planning you will do this year.

Definition: job-work in 55 words

Job-work is processing of your goods by another person: you send material out, they machine, polish, assemble, or finish it, and return it. The goods stay yours throughout. Movement runs on delivery challans, and only the processing fee is invoiced. Section 19 of the CGST Act carries the ITC conditions. Read it, don't memorise this box.

Friday: the bolts return

Friday, the tempo is back. Bolts, same steel, plus threading, plus a delivery challan inward and a labour invoice for the processing fee with its own GSTIN, service HSN, and tax. That labour bill posts like any purchase and claims ITC like any purchase, through 2B and the 16(4) clock like any purchase. It is the only voucher in the loop. Everything else is a challan, and challans never post. Ever. That sentence is worth memorising even though I told you not to memorise the box.

Now the part factories fumble: between Monday and Friday your inputs sat on someone else's machine, and the ITC on them sat in your return. Do you keep it? Broadly yes, with conditions and with time limits for the goods to come back, all in section 19. I am deliberately not printing the periods. They have numbers, the numbers matter, and a blog is the wrong place to memorise them from. Open the Act, confirm with your CA, diary the dates per challan. That diary is the next section.

The loop, drawn once

Here is the whole week on one card. Tape the shape to your wall and every job-work question answers itself:

Challan 214: one loopTwo movements, one invoice, one clock
MON · YOU
rods out
challan 214
→
MID · THEIR SHOP
threading
your steel, their machine
→
FRI · YOU
bolts in
challan 309 + labour bill

The clock runs from Monday. The register below watches it.

Notice what is missing from the card: any sale. And notice what our gate does with the two challans if they arrive as scans: tries to keep them out of purchase posting, exactly as I wrote in the challan page. A job-work challan reads like a bill, GSTINs, lines, quantities, values, and posted as a purchase it invents a purchase of your own goods. From yourself. The gate exists to prevent precisely that embarrassment.

The notebook that watches the clock

One page per outward challan. I have seen fancy ERPs and I have seen a ruled notebook, and honestly the notebook wins when it is actually maintained, because the person who writes in it owns the loop. Five columns, written the day the goods leave:

Out date, job worker, item, quantity, challan number. Then the expected return date, and hear me on this: not your guess, but your CA's reading of section 19, written down per challan. Then in date and labour invoice number when the loop closes. An in-challan without the labour bill is an unpaid worker. A labour bill without the in-challan is material still missing. Both gaps shout from a maintained page and whisper from a neglected one.

Then the monthly ritual, last Friday, thirty minutes: every open loop past its expected return goes on the chase list next to the supplier calls. Open loops are where ITC quietly bleeds, and a monthly glance is the cheapest insurance I know. Challan 214 closed on Friday with all three papers filed together. Somewhere out there is a challan 215 still open, and its clock does not care that nobody is watching. Watch it.

Sources
Frequently asked questions
Is sending goods for job-work a sale?+

No. Your goods travel on delivery challans. Only the processing fee gets invoiced. Nothing changes hands in ownership, so say it till it sticks.

Do I keep ITC while my inputs sit at their shop?+

Broadly yes, with conditions and return time limits in section 19. I won't print the periods here. Read the Act, confirm with your CA, diary per challan.

What is the one register that matters?+

The challan register: out date, expected return, in date, labour bill. Open loops reviewed monthly. A ruled notebook beats a neglected ERP.

Why do challans scare your gate?+

Because a job-work challan reads like a bill: GSTINs, lines, quantities, values. Posted as a purchase, you buy your own steel. The gate exists to prevent that embarrassment.

The labour bill still gates like any bill

Upload the job worker's invoice. Watch the checksum, HSN and arithmetic checks decide. Five runs, no signup.