What Is Pin to Pin Distance in E-Way Bill? Complete GST Guide

There’s a specific kind of phone call every logistics or accounts manager dreads. The driver is stuck at a check post two states away, the e-way bill has technically expired, and nobody in the office can immediately explain why. Nine times out of ten, when you trace it back, the problem started with the pin to pin distance entered while generating the bill.

It’s a strange thing to have this much power over your supply chain. Two PIN codes and a distance figure decide how many days your goods are legally allowed to be on the road. Get it wrong, and you’re not just looking at an awkward phone call; you’re looking at a detained vehicle, a possible penalty, and a client asking why their delivery is three days late.

This piece covers what pin to pin distance in e-way bills are, how it’s worked out, what goes wrong when it’s off, and what you can realistically do to stop this from happening every other week.

What Is Pin to Pin Distance?

 It’s the road distance between where your goods are dispatched from (the supplier’s PIN code) and where they’re going (the recipient’s PIN code). Nothing exotic. But under GST, this number stops being a shipping detail and becomes something closer to a legal parameter, because it directly sets how long your e-way bill stays valid.

When you generate the bill, you punch in both PIN codes and the system spits out an approved distance. That distance is what everything downstream depends on. Validity, essentially, is this number divided into chunks of time. Mess up the PIN code, or decide to type in your own estimate instead of trusting the system, and the whole validity calculation goes sideways with it.

Why Not Just Let People Enter the Distance Themselves?

Because that’s basically what used to happen, and it went about as well as you’d expect. Transporters and suppliers would fill in whatever number seemed reasonable. Some shortened it to make their paperwork look tidy. Others padded it out to buy extra days when a delivery was running behind schedule. Either way, the number on the form often had little to do with the actual route the truck was taking.

Tying distance to PIN codes fixed most of that at once. The same two PIN codes always produce the same distance no matter who’s filling out the form. Officers at check posts can verify what’s declared against what the system says. Audits get a fixed reference point to work from instead of someone’s best guess. And it works the same whether you’re shipping across three states or just across town.

It’s not a glamorous fix. But it took a lot of the guesswork, and honestly, a fair bit of the fudging, out of the system.

How the Distance Actually Gets Calculated

The government portal has a calculator built in for this, and it’s not hidden away anywhere. Go to ewaybillgst.gov.in, click Search in the top menu, then pick Pin to Pin Distance from the dropdown. Type in the source PIN and the destination PIN. The portal comes back with the road distance in kilometres, and that’s the figure the entire e-way bill validity calculation runs on.

If you’ve never generated an e-way bill from scratch and want the full walkthrough before getting into distance specifics, this guide on what a GST e-way bill is and how to generate one online covers the basics well.

From Distance to Days: How Validity Actually Works

Once you have the distance, the validity math is genuinely simple:

Distance (PIN to PIN)	E-Way Bill Validity
Up to 200 km	1 day
Every extra 200 km, or part of it	+1 day

To explain the idea, one can take two examples. First, for instance, Delhi and Mumbai are 1,451 kilometers apart, which would mean a travel time of eight days. And the distance from Bangalore to Chennai is 350 kilometers, with a duration of two days. 

The surprising thing is that as soon as the e-way bill is generated, the time starts. Not when the truck actually pulls out of the yard. So if there’s a half-day delay loading the vehicle, or the driver doesn’t show up until the next morning, that time comes straight out of your validity window. Nobody adds it back.

Over-dimensional cargo runs on a tighter clock altogether, 1 day of validity per 20 km instead of 200. Which means a distance error on one of these shipments does a lot more damage, a lot faster.

What Actually Happens When the Distance Is Off

This is where a lot of businesses genuinely underestimate the stakes. A wrong distance figure doesn’t get treated as a harmless clerical slip; GST law gives officers fairly sharp teeth to act on it.

If the distance was entered too short, the e-way bill can lapse before the shipment even reaches its destination. The goods are moving in good faith, nothing shady is going on, but the document says otherwise the moment an officer checks it at a check post.

That’s when Section 129 of the CGST Act comes into play. An expired or mismatched e-way bill gives the officer the authority to detain both the vehicle and the goods, demand the tax due, and slap on a penalty, either equal to the tax amount or ₹10,000, whichever works out higher. They can also order the whole consignment inspected on the spot, which, if you’ve ever had a truckload of goods pulled apart at a check post, is not something you want to sit through twice.

Auditors pick up on patterns too. If a business keeps showing unusually short distances on high-value shipments, that starts to look less like carelessness and more like something worth investigating for potential tax evasion, even when it really was just a typo.

And the costs don’t stop at the penalty. There’s the detention charge while the truck sits there. The missed delivery window. The scramble to arrange another vehicle on short notice, usually at a worse rate. And somewhere down the line, a client who’s starting to wonder if they can trust your dispatch process at all.

Do this often enough on the same GSTIN, and you’ll notice the pattern following you: closer scrutiny on future audits, slower refund processing, more clarification notices landing in your inbox than you’d like.

Where These Mistakes Actually Come From

It may be helpful to understand the reason for these mistakes in order to avoid making them, because in most cases, it happens due to many small things.

One of the common mistakes is when a person types “New Delhi” instead of typing the exact code of the address of delivery, thus making the calculation of the distance quite illogical. 

Another: transporters generating the e-way bill using whatever PIN details the client handed over. If that data’s wrong, the transporter’s stuck holding a non-compliant document they didn’t actually create the error in.

Then there’s just volume. A business pushing out 50 or 100 shipments a day is going to fat-finger a PIN code sooner or later. It’s not a matter of if. One wrong digit and the calculated distance can swing wildly.

And occasionally, it’s deliberate: someone manually overrides the system’s suggested distance to “adjust” the transit window. Usually without realising this is exactly the kind of thing that gets flagged first in an audit.

Fixing It After the Fact

What you can do depends entirely on whether the truck has left yet.

If it hasn’t: cancel the e-way bill within 24 hours of generating it, then create a fresh one with the correct PIN codes and the system-verified distance. Keep a quick internal note on why it was cancelled; future-you, or whoever’s handling the next audit, will thank present-you for it.

If the vehicle’s already gone: cancellation is off the table. Your options narrow down to applying for a validity extension, and that only holds up if there’s a genuine reason behind it, an accident, bad weather, a law-and-order issue, something documented. Otherwise you’re relying on whatever explanation you can give the officer if the shipment gets stopped.

Realistically, catching the error before dispatch is the only version of this that doesn’t cost you money or time. A two-minute portal check beats every alternative on this list.

Why Manual Entry Is the Real Problem

Almost every error described above traces back to one root cause: someone typing a PIN code by hand. Which means the fix isn’t “train people to be more careful”; that only works until the next busy day. The fix is removing the manual step.

This is really where decent GST billing software earns its keep. GST billing software, for instance, pulls the system-approved distance straight from the e-way bill network rather than leaving it to whoever’s at the desk that afternoon. There’s no PIN-code guesswork sitting between your invoice and the e-way bill it generates.

A few things worth checking if you’re deciding whether your current setup is actually pulling its weight:

Does it fetch distance automatically, or is someone still typing it in? Can e-way bills be generated straight off invoice data without re-entering PIN codes in a second system? This is also where e-invoicing ties in, since IRN generation and e-way bill creation can happen in one motion instead of two? Does it validate PIN codes against a master list before the bill goes out, rather than after something’s already gone wrong? Does it warn you when a shipment’s validity is about to run out, while there’s still time to act? And is there an actual audit trail sitting behind each bill, invoice reference, PIN codes, distance, timestamp, so an audit doesn’t turn into a scavenger hunt through old records?

For a business moving goods regularly, this stops being a nice-to-have somewhere around the second or third time a check post calls with bad news.

A Short List Worth Keeping Near the Dispatch Desk

None of this requires new software, necessarily; some of it’s just discipline:

Don’t override the system-calculated distance, ever, no matter how tempting it is to “fix” a transit window manually. Check new delivery PIN codes before the bill goes out, not after. The dealer’s own calculator can be used to verify any unfamiliar matter. It is important to ensure a person dealing with dispatch knows how the validity is calculated and why a certain figure is found on the document. High-value shipments should be checked manually instead of using mass auto-generation. Keep your PIN code records for regular customers and suppliers clean and current. And set some kind of internal alert so shipments already on the road are being watched against their expiry, not just checked at the moment of generation and then forgotten.

Who Actually Feels This the Most

The makers face the greatest risk, primarily due to the scale of operations; daily shipment of high-value items implies that one mistake in a large shipment can lead to a really huge fine.

The traders and wholesalers sending shipments to multiple destinations keep updating the PIN data, which is exactly the type of repetitive manual work that gives rise to errors.

The small and medium businesses usually have one or two people managing billing, dispatch as well as compliance at once, leaving hardly any opportunity to double-check the work. 

Transporters, meanwhile, frequently inherit risk they didn’t create, generating e-way bills off PIN data the client supplied, with no easy way to verify it themselves.

Conclusion

Pin-to-pin distance in e-way bills looks like a footnote on the e-way bill form, but it’s quietly doing a lot of work, setting your validity window, and by extension, deciding whether your shipment moves cleanly or ends up detained somewhere with a very unhappy driver on the phone. Getting it right almost always comes down to five minutes of checking, done at the right moment.

The more durable fix, especially past a certain shipment volume, is taking manual distance entry out of the picture entirely. Software that fetches system-approved distances automatically, checks PIN codes before generation, and tracks validity in real time turns this from a recurring headache into something you stop thinking about.

If you want to see what that looks like in practice, MargBooks Software handles e-way bill generation, e-invoicing, and distance validation as one connected workflow, worth a look if distance errors have already cost you more than one afternoon standing around a check post.

FAQs

Q1. What is pin to pin distance in an e-way bill? 

It’s the road distance between the supplier’s PIN code and the recipient’s PIN code. The GST system uses this figure to calculate how long the e-way bill stays valid.

Q2. How to find out the distance between two PIN codes to generate an e-way bill?

Go to ewaybillgst.gov.in, click on Search, choose Pin to Pin Distance, and then enter the two PIN codes. 

Q3. Is there a minimum distance needed to generate an e-way bill? 

No. The trigger is the value of goods, above ₹50,000 and you need one, regardless of how short the actual route is. Distance affects validity, not whether the bill is required.

Q4. What happens if the distance on an e-way bill is wrong? 

Understated, and the bill can expire before the goods arrive, risking detention under Section 129. Overstated, and it can get flagged as a potential red flag during audits.

Q5. Can distance be corrected after the e-way bill is generated? 

Only if the vehicle hasn’t moved yet, cancel within 24 hours and regenerate. Once it’s departed, cancellation’s off the table; a validity extension is your only option, and it needs a genuine reason behind it.

Q6. How exactly does validity get calculated from distance? 

Standard cargo gets 1 day of validity per 200 km or part thereof. So 350 km gets you 2 days. Over-dimensional cargo is stricter: 1 day per 20 km.

Q7. Does the system’s distance always match the actual road route? 

Not perfectly. It’s based on an approved mapping engine, but the real route a driver takes can vary slightly, which is part of why extensions exist for genuine situations like accidents or diversions.