What a delivery challan is, and what it proves

A lorry arrives. The driver climbs down and hands somebody a slip of paper, usually creased, usually in triplicate, usually carbon-copied so faintly that the quantity is the hardest thing on it to read.

That slip is a delivery challan. It is one of the most important documents in construction and one of the least carefully handled, and the reason is that almost everybody treats it as a receipt when it is nothing of the sort.

What is actually written on it#

A delivery challan is the seller's statement of what left their premises. In its ordinary form it carries the date, a serial number, the consignor and the consignee, the vehicle number, a description of the goods, the quantity, and somewhere near the bottom a space for a signature at the other end.

Under the GST rules a delivery challan is the right document for movements where a tax invoice is not — goods sent out for job work, goods sent on approval, a single order delivered in several vehicles, material moved between two of your own premises. In those cases the challan is not a lesser version of an invoice. It is the correct paper for that movement, and the invoice comes later or not at all.

What it proves#

It proves dispatch. Somebody at the other end loaded a stated quantity into a stated vehicle on a stated day and wrote it down.

That is genuinely valuable. It fixes a date, it fixes a vehicle, and it fixes a number that the seller cannot later quietly revise, because you are holding their own copy of it. It cuts both ways, which is why it is worth writing a challan that protects the supplier if you are the one dispatching.

What it does not prove#

It does not prove that the quantity written on it is the quantity that reached your store.

This is the whole point, and it is the part people skip because the paper looks so official. The challan was written at the loading point. Between there and your gate a load can be short, wet, broken, partly delivered somewhere else, or simply counted differently by two people using two methods. A challan signed at your gate proves the driver got a signature. It does not, by itself, prove agreement about quantity.

The document that records what you say arrived is a different document, and it is written by your side. That is the goods receipt note, and keeping the two separate is the foundation everything else in purchase accounting is built on.

Why the difference matters at the gate#

The gate is where a challan is either turned into a record or lost.

If the person at the barrier signs the challan, hands back the top copy and keeps a carbon that goes into a spike file, you have a stack of paper and no data. Six weeks later, when an invoice arrives for a quantity nobody remembers, the only way to check it is to send somebody to the spike file.

If instead the gate writes the challan number, the vehicle number and its own count into a register at the moment the lorry is standing there, the challan becomes checkable. We have written separately about what makes a gate register somebody will actually keep, because the difficulty is never that people do not understand why it matters. It is that the register was designed by somebody who has never held a pen in one hand and a torch in the other.

A challan filed against nothing#

Here is a failure we found in our own software, because it is a good illustration of how this document gets lost even after it has been captured correctly.

Site staff were photographing delivery slips and sending them in. The photographs were being read, the challan details extracted, and each one offered a match against the purchase it belonged to. All of that worked.

But the matcher only ever considered purchases that had not yet been paid. In our own process, payment is required before a lorry is dispatched at all. So by the time material arrived and somebody photographed the slip, the correct purchase was always in the paid state, and therefore was never offered as a candidate. The challan matched nothing. And a challan filed against nothing is displayed on no screen anywhere, which means that from the outside it looks exactly like a challan that was never captured.

Nothing errored. The photographs kept arriving, the reading kept working, and the result kept being invisible. The fix was one sentence long: paid purchases are offered the match too, closed ones still are not.

What to do with one, in order#

1. Count before you sign. The signature is the moment your side commits. Everything after it is an argument.
2. Write your own number down, even when it is the same as theirs. Especially when it is the same as theirs.
3. Keep the challan number. It is the only handle that connects the physical arrival to the paperwork that follows — the receipt note, and later the invoice.
4. Note the vehicle number. Disputes about deliveries are very often disputes about which delivery, and the vehicle is what separates them.
5. Photograph it before it goes into the file. Paper on a construction site has a survival rate nobody would accept from any other record.

Then, when the invoice appears, you have three independent statements of the same event — what was ordered, what was delivered, and what is being charged — and you can hold them against each other. That comparison is three-way matching, and it is the only reliable defence against paying for material that never arrived.

The short version#

A delivery challan is the seller's word about what left. Your goods receipt note is your word about what came. An invoice is the seller's claim about what you owe. Three documents, three authors, one event.

Treat any of them as a substitute for the others and you have quietly agreed to pay for whatever the vendor writes down.