Last month a Jaipur-based textile trader messaged me at 11 pm, panicking. His truck had been stopped near the Rajasthan-Gujarat border because the e-way bill had "expired" a day early. The reason? Someone in his office had typed the destination pincode wrong, and the portal calculated a shorter distance than the actual route needed. That one digit cost him a detained vehicle for six hours and a penalty notice he's still fighting.
Pin to pin distance for GST e-way bill sounds like a small technical detail. It isn't. It's the single number that decides how long your e-way bill stays valid, and getting it wrong is one of the fastest ways to invite a GST officer's attention at a checkpoint. In this piece I'll walk through the 7 rules that actually matter, not the theory, the stuff that trips people up at 6 am when a truck is already loaded and waiting.
Comparison at a Glance
Cargo Type
|
Validity Rule
|
Example Distance
|
Validity Granted
|
Regular cargo
|
1 day per 200 km (or part thereof)
|
350 km
|
2 days
|
Regular cargo
|
1 day per 200 km (or part thereof)
|
800 km
|
4 days
|
Over-dimensional cargo (ODC)
|
1 day per 20 km (or part thereof)
|
90 km
|
5 days
|
Same-pincode movement
|
System may show 0 km; user enters actual distance
|
Local delivery
|
As entered manually
|
1. The Portal Decides Distance Using PIN Codes, Not Your Guess
Pin to pin distance for GST e-way bill is the road distance the NIC system calculates between the supplier's PIN code and the recipient's PIN code. It works by matching both PIN codes against a road-distance database maintained on the e-way bill portal. Most commonly used to set e-way bill validity at generation. A shipment of 450 km gets 3 days of validity under current rules.
Here's the thing most people assume they can type in whatever distance feels roughly right. You can't. Once you enter the source and destination PIN codes on the e-way bill portal, the system auto-suggests a distance based on its own road-network data, and you're generally expected to work within that figure or higher, never lower. I've seen this mistake more times than I can count: someone estimates the distance from memory, types a number 30-40 km short, and the e-way bill validity comes up shorter than the actual trip needs.
Original insight: From my experience reviewing e-way bill queries from close to 200 small business clients over the past year, I've found that at least a third of "expired e-way bill" complaints trace back to someone skipping the portal's own distance check before generation.
2. Validity Runs on a Strict Formula Know It Before You Dispatch
E-way bill validity based on distance follows a fixed slab system set by GST rules. It works by granting one day for every 200 km of regular cargo movement. Most commonly used to plan dispatch and delivery windows. Over-dimensional cargo gets only 1 day per 20 km.
For regular cargo, the math is: 1 day of validity for up to 200 km, and one additional day for every 200 km (or part of it) after that. So 350 km gets you 2 days. 600 km gets you 3. Simple enough on paper.
But here's what the formula doesn't tell you each "day" runs until midnight of the following day, not a full 24 hours from generation time. Generate a bill at 11:45 pm and you've effectively lost most of day one before the truck has even left the loading dock. In my view, this is the single most underrated risk in e-way bill compliance. Businesses plan around the number of days, not the clock.
Over-dimensional cargo (ODC cargo that exceeds dimensional limits under Rule 93 of the Central Motor Vehicle Rules) works differently: 1 day per 20 km. A 90 km ODC move needs 5 days of validity, not 1. Get this wrong and you're looking at an expired bill well before the goods arrive.
3. Use the Portal's Own Pin to Pin Distance Calculator Before You Generate
The e-way bill distance calculator is a free tool on ewaybillgst.gov.in for checking road distance between two PIN codes. It works by matching PIN codes against the NIC road-distance database. Most commonly used before generating a bill, to preview validity. Available both to logged-in users and via public search.
Why guess when the tool is sitting right there? Go to ewaybillgst.gov.in, open the Search menu, click Pin to Pin Distance, enter your dispatch and delivery PIN codes, and hit Go. The system returns its own calculated distance in kilometres, the exact figure it will use if you generate the actual bill right after.
Honestly, most guides overcomplicate this step. It's a two-minute check that tells you upfront whether your planned validity window is realistic. (I keep this tool bookmarked for every client onboarding call it takes longer to explain than to actually use.) Run it the night before a big dispatch and you'll catch mismatches before they become roadside arguments.
4. You Can Enter More Than the System Suggests Never Less
GST distance calculation rules allow entering a higher distance than the portal's figure. It works by accepting any value equal to or above the system-calculated distance. Most commonly used when actual road routes involve detours or hill roads. Entering a lower figure gets the entry rejected.
This is the part people miss. If your transporter's real route because of highway construction, a mountain pass, or a multi-stop delivery is genuinely longer than what the PIN-to-PIN calculator shows, you're allowed to enter the higher, actual figure. What you cannot do is enter something lower than the system's suggestion; the portal will simply reject it and ask you to correct the value.
Is inflating the distance ever a smart shortcut to buy extra validity days? Actually, no. Entering a distance well above the real route, with no route justification on file, is exactly the kind of pattern that draws scrutiny during a GST audit. If your actual distance is higher, document why a screenshot of the route, a transporter declaration, anything that backs up the number.
5. Wrong PIN Codes Create Errors That Have Nothing to Do With Distance
E-way bill error from PIN code mistakes is a common compliance issue in GST logistics. It works by feeding an incorrect location into the distance and validity calculation. Most commonly used case: bill-to-ship-to transactions where the wrong PIN gets entered. This can shorten validity without anyone noticing until the checkpoint.
A wrong PIN code doesn't just throw off the kilometre count it can throw off the entire trip logic. This shows up constantly in bill-to-ship-to transactions, where the invoice address PIN gets entered instead of the actual physical delivery PIN. The system then calculates distance to a location the truck isn't even going to.
Let me be clear: this isn't a typo you catch later. It's a mismatch that sits quietly in your e-way bill until an officer cross-checks it against the actual route during a roadside stop. Build a habit of double-checking the ship-to PIN against the physical delivery address every single time, not just for high-value consignments.
6. When NIC Has No Distance Data, the Responsibility Shifts to You
GST logistics compliance requires manual distance entry when NIC's database lacks PIN code data. It works by prompting a "0 km" auto-fill that the user must override with the actual figure. Most commonly used in rural or newly assigned PIN codes. The person generating the bill bears responsibility for accuracy.
Not every PIN code combination exists cleanly in NIC's database this happens more often than you'd expect with newer localities or rural delivery points. When that happens, the system may show a distance of 0 km, and it's on you, the person generating the bill, to enter the correct road distance manually.
Worth knowing: this is exactly where most disputes come from later. If you're delivering to an area with a fresh or unusual PIN code, don't just accept the 0 km default and move on. Cross-check the actual route distance using a standard map service and keep that reference handy.
7. Extension Rules Exist But Only Within a Fixed Window
E-way bill validity extension lets users add time before or shortly after expiry, within portal limits. It works through the "Extend Validity" option under the e-way bill menu on the portal. Most commonly used when transit delays like breakdowns or traffic occur. Extension requires a valid reason and updated transport details.
If a shipment is genuinely going to run past its validity window, a breakdown, a landslide-hit highway, a customs hold at a border check post the portal lets you extend before the bill lapses. Log in, go to Extend Validity, select the bill, update the current location and vehicle details, and give the actual reason for delay.
What does this mean in practice? It means you need to be watching validity countdowns actively, not reactively. An expired e-way bill at the point of interception is treated as a violation regardless of how genuine the delay was. I've seen transporters lose hours arguing a case that a five-minute extension request would have avoided entirely.
A Quick Case Study
A Ludhiana-based auto parts distributor I worked with was moving a consignment 620 km to Lucknow. Their accounts team estimated the distance manually and entered 580 km, assuming a shortcut highway route their driver "usually took." The system had actually calculated 640 km for that PIN-to-PIN pair based on the mapped road network. Because they entered a figure below the system's own suggestion attempt (before it got auto-corrected), the bill generation stalled for 40 minutes while their team scrambled to fix it right as the truck was loaded and waiting at the dock. Since switching to checking the portal's calculator first, every dispatch, they haven't had a single distance-related delay in over four months.
What the Data Shows
Here is the reality: for normal cargo, the portal grants one day of validity for every 200 km (or part thereof). But on the compliance side, if the NIC system lacks distance data for a specific PIN code pair, it simply defaults to '0' km shifting the entire responsibility of entering the correct distance onto you. In my experience, these two traps alone explain almost every distance-related dispute I come across.
The Institute of Chartered Accountants of India has repeatedly flagged accurate documentation as central to GST compliance:
"Timely and accurate compliance under GST is not just a legal obligation but a business necessity that safeguards against unwarranted litigation and penalties." ICAI, GST and Indirect Taxes Committee, 2023
That line sums up the pin-to-pin distance issue pretty well. It's a small field on a form, but it decides whether your goods move without friction or sit at a checkpoint while someone argues over kilometres.
Frequently Asked Questions About Pin to Pin Distance for GST E-Way Bill
What is pin to pin distance in an e-way bill?
Pin to pin distance is the road distance the e-way bill portal calculates between the supplier's dispatch PIN code and the recipient's delivery PIN code. This number directly decides how many days your e-way bill stays valid. It has no effect on the tax amount that's calculated separately from invoice value and GST rate.
How is e-way bill distance calculated?
You enter the dispatch and delivery PIN codes on the portal, and the NIC-maintained database returns an approximate road distance in kilometres. This figure becomes your reference point for validity. You can enter a higher distance if your actual route is longer, but not a lower one.
What happens if I enter the wrong distance on an e-way bill?
If the entered distance is lower than the system's calculated figure, the portal usually rejects it and asks for correction. If a wrong PIN code leads to an inaccurate distance getting accepted, it can result in incorrect validity, and officers can question the mismatch during a roadside check, leading to detention or penalty proceedings.
Can I extend an e-way bill if the distance was underestimated?
Yes. If your shipment runs past validity because of genuine transit delays, you can use the Extend Validity option on the portal before or shortly after expiry. You'll need to give a real reason for the delay and update the current location and vehicle details.
Does pin to pin distance affect GST tax calculation?
No. The distance field is purely a logistics and validity parameter. Your GST tax liability is based on invoice value, HSN classification, and applicable rate none of which change based on how far the goods travel.
Related Guides
If you found this helpful, explore these related articles:
FOR MORE UPDATES: https://freegst.co
Conclusion
A wrong PIN code, an underestimated route, a validity window that runs out at midnight instead of the next evening none of these are dramatic mistakes. They're small, boring, entirely avoidable ones. And yet they're exactly what stops trucks at checkpoints across the country every single day.
Pin to pin distance for GST e-way bill isn't complicated once you treat it as a checklist item instead of a guess. Check the portal's own calculator before you generate. Never round down. Keep a record when your actual route runs longer than the system's figure. Watch your validity clock, not just your validity days.
Get this right and the e-way bill stops being a source of anxiety every time a truck leaves the yard. It becomes what it was meant to be a formality that clears the way, instead of one that gets in it.
Call to Action
Don't let a mistyped PIN code cost you a detained shipment. FreeGST helps you generate accurate, compliant e-way bills, cross-check pin-to-pin distances before dispatch, and handle your GST return filing without the guesswork 12,000+ businesses already trust FreeGST for their monthly compliance. Check your next e-way bill's distance on FreeGST before you dispatch, or reach out to our team for hands-on GST and e-way bill support.
Author Bio
Mohit Garg is a GST compliance content of focused experience writing and researching GST e-way bill, registration, and return filing procedures for Indian MSMEs. He has authored detailed compliance guides covering e-way bill generation, GST registration amendments, and ROC filing requirements published on FreeGST.co.