Home blog-details

Blog Details

Pin to Pin Distance in GST: Why One Wrong Digit Can Get Your Truck Detained

11 July 2026

Type one wrong digit into a PIN code field, and your e-way bill can expire before the truck even crosses the state border. That's the real, underrated power of pin to pin distance, the number that quietly decides how many days your shipment is legally allowed to stay on the road.

Here's the thing: most businesses never think about pin to pin distance until a check post stops their vehicle and they realise the validity window has already closed. By that point, the penalty notice is already on its way.

This guide walks through what pin to pin distance actually means under GST, how the e-way bill portal calculates it, and more importantly where businesses slip up during multi-leg and transhipment movements. Having gone through hundreds of e-way bills and GST compliance cases at gstfilling.co, we've seen the same pincode-related mistakes keep costing businesses real money in penalties. That's exactly why this piece digs into the gaps most other articles simply skip over.

What Exactly Is Pin to Pin Distance?

Pin to pin distance is the road distance the GST e-way bill system works out between your shipment's source PIN code and its destination PIN code. You'll also see it called pin code to pin code distance in km, since the whole calculation runs on India's familiar six-digit postal system. Any business that has completed its GST registration and generates e-way bills regularly ends up relying on this number almost every day.

It's worth clearing up one misconception first: this is not a straight-line, as-the-crow-flies measurement. The system checks both PIN codes against the NIC distance database and pulls out an approved road-route figure. Its main job is to set the validity period for the e-way bill.

Interestingly, the PIN code system itself was not built for GST at all. India Post introduced it decades ago simply to make mail routing easier. GST later borrowed this existing framework because nearly every business address, warehouse, and delivery point already carries a six-digit PIN, making it a ready-made, standardised reference for distance-based compliance.

The moment you key in the source and destination PIN codes while generating an e-way bill, the pin to pin distance search feature fills in the kilometre figure automatically. That single number then runs the entire validity clock for the shipment. This is exactly why searches for GST pin to pin distance stay so high month after month this figure directly decides whether your shipment remains compliant while it is still in transit.

How to Look Up Pin to Pin Distance on the GST Portal

You don't actually have to wait until you're generating the e-way bill to check this. The portal also lets you run a pin to pin distance search on its own, which is handy if you're planning dispatch schedules ahead of time.

Here's how:

  1. Go to the official e-way bill portal ewaybillgst.gov.in.
  2. Click on Search in the top menu.
  3. Choose Pin to Pin Distance from the dropdown.
  4. Enter the source PIN code this is your dispatch point.
  5. Enter the destination PIN code; this is the delivery point.
  6. Click Get Distance, and the system-approved kilometre figure will show up.

This same pin to pin distance calculator for e-way bills also works quietly in the background every time you generate an actual e-way bill, pulling from the PIN codes entered in Part A of the form. If you want the full official rulebook behind all of this, the CBIC e-way bill FAQ document is worth bookmarking.

One quick warning about searching this on Google directly: a plain Google search for "pin to pin distance" will show you a travel or mileage tool meant for road trips, not the GST-approved number. For e-way bill purposes, always stick to the figure from the official portal that's the one tax officers actually go by during verification.

How This Distance Figure Decides E-Way Bill Validity

The validity period of your e-way bill is tied directly to whatever distance the portal returns. For regular cargo, the rule gives you one day of validity for every 200 km, or part of it. Over Dimensional Cargo has a much tighter rule just one day for every 20 km.

Here's a quick reference for regular cargo:

Distance (Pin to Pin) 

Validity Period (Regular Cargo) 

Up to 200 km 

1 day 

201–400 km 

2 days 

401–600 km 

3 days 

601–800 km 

4 days 

801–1,000 km 

5 days 

Every additional 200 km

+1 day

So a shipment of 450 km gets 3 days of validity, since 450 is divided by 200 rounds up to 3. Something a lot of people miss is that the validity clock starts the moment the e-way bill is generated, not when the truck actually starts moving. If you generate it too early, you are quietly burning through your transit window before the vehicle has even left the loading bay.

Since your e-way bill data and outward supply figures eventually flow into your monthly return anyway, keeping distance and delivery records clean here makes reconciliation a lot smoother when you sit down with our GSTR-3B filing guide at month-end.

Multi-Leg and Transhipment Shipments — The Part Most Guides Ignore

Nearly every article on pin to pin distance stops at the simple origin-to-destination example. But a large chunk of Indian logistics actually moves through a hub, warehouse, or transhipment point before it reaches the final buyer, and this is exactly where businesses get penalised most often.


How the rule plays out across hubs

When goods travel from a factory to a regional warehouse, and then separately from that warehouse to the end customer, GST treats these as two distinct movements, provided two separate invoices or delivery challans are raised. Each leg needs its own e-way bill, and each leg gets its own pin to pin distance based on that specific leg's PIN codes.

A mistake that comes up constantly is entering the final customer's PIN code as the destination on the first leg, even though the truck is only heading as far as the warehouse. This artificially inflates the declared distance, hands you a longer validity window than you should have, and creates a mismatch that a GST officer can easily flag at a roadside check, because the vehicle's actual route does not match the PIN pair on record.

For journeys stretching beyond 3,000 km in a single haul, say, a movement from the deep south to one of the Himalayan states the system requires the shipment to be split into staged e-way bills, each carrying its own pin to pin distance and validity period.

This trips up online sellers especially, particularly those dispatching from multiple fulfilment warehouses. If you sell through marketplaces, our Meesho GST registration guide covers how multi-warehouse dispatch affects compliance well beyond just this distance field.

Pin to Pin Distance for E-Invoice vs. E-Way Bill

These two get mixed up a lot, but they are not the same thing. Pin to pin distance for e-invoice and pin to pin distance for e-way bill are related, sure, but the e-invoice system generates the Invoice Reference Number and QR code purely from invoice data, while the actual distance calculation that determines validity happens strictly within the e-way bill workflow.

When an e-invoice gets linked to an e-way bill which is the standard flow for B2B transactions above the e-invoicing threshold the Ship-to GSTIN and address feed straight into e-way bill Part A. If there is any mismatch between the invoice's billing address PIN and the actual dispatch PIN, the pin to pin distance figure can go wrong before the truck has even left the dock.

If your business runs ERP-integrated e-invoicing, always double-check that the dispatch PIN used for the e-way bill matches the actual warehouse or plant location, not the company's registered head office PIN. These two are more often different than people expect.

Getting the e-invoice and e-way bill details aligned is not just your problem either. A mismatched delivery record on your end can complicate how the buyer later works through their own Input Tax Credit calculation for that purchase.

The Mismatch Errors That Keep Showing Up (and How to Avoid Penalties)

Most pin to pin distance disputes trace back to a handful of repeat mistakes. Here's what shows up most often in GST notices and detention cases:

  • Swapping the source and destination PIN codes this does not change the distance, but it flips who is on record as consignor and consignee.
  • Using the billing address PIN instead of the actual dispatch warehouse PIN.
  • Entering the final delivery PIN on an intermediate leg of a multi-hub shipment.
  • Generating the e-way bill a day before the vehicle is actually ready to move this quietly eats into your usable validity window.
  • Ignoring the 10% tolerance rule, which only allows a higher manually-entered distance, up to 10% above the system figure, and never a lower one.

If your real route genuinely runs longer than the system's figure by more than 10% because of a hilly detour, a closed highway, or any other reason the safer move is to split the journey into separate e-way bills for each verifiable segment, rather than trying to manually override the distance.

Beyond pincode accuracy, GST officers now cross-check e-way bill movement against FASTag and RFID data at toll plazas. A declared pin to pin distance that does not line up with the actual toll-plaza trail is far more likely to get questioned today than it would have been even a year ago.

It is also worth remembering that the item description and HSN details on the same invoice matter just as much. An incorrect goods classification, alongside a distance mismatch, tends to raise a lot more questions during a check. Our NIC code and business classification guide is a useful cross-check if your invoice descriptions look off.

Why This Actually Matters: A Practitioner's Take

"In almost every detention case I've reviewed, the real dispute was never about tax evasion. It came down to a pincode entered in a hurry, at a warehouse, without anyone checking whether it matched the invoice."

Working closely with SEO and compliance content for gstfilling.co, part of the LegalDev group, means going through GST advisories, e-way bill portal updates, and real business queries around distance mismatches on a near-weekly basis. The pattern holds up every time: businesses that build a simple two-minute PIN code check into their dispatch process almost never run into a distance-related detention. The ones that skip it eventually do.

That is really why this guide spends extra time on multi-leg shipments and the e-invoice connection. These are the exact situations that turn into GST notices and detention cases when left unchecked.

Conclusion

Three things matter most with pin to pin distance under GST. First, the distance you declare directly sets your e-way bill's validity window, so getting the PIN code right protects your entire shipment timeline. Second, multi-leg and transhipment movements each need their own PIN-based distance, not one inflated figure covering the whole journey. Third, the 10% tolerance rule is there for genuine route variations, not as a workaround, and staged e-way bills remain the safer path for longer detours.

Getting pin to pin distance right is a small habit, but it saves you from a genuinely large compliance headache. It is worth building into every dispatch checklist your team follows. Still setting up the basics? Our GST registration process guide is a good place to start before diving into e-way bill workflows.

Need Help With E-Way Bill or GST Compliance?

If your business is running into e-way bill mismatches, distance disputes, or any other GST compliance issue, our team at gstfilling.co can review your setup and fix it before it turns into a notice. Talk to a GST expert today.

FAQ

1 What is pin to pin distance in GST?

It is the system-calculated road distance between a shipment's source and destination PIN codes, used mainly to set e-way bill validity.

2 What is PIN code to PIN code distance in km?

It is the same figure as pin to pin distance, just expressed in kilometres between two Indian postal codes. It is the exact number the e-way bill portal uses to determine how many days a consignment can legally remain in transit.

3 How do I check pin to pin distance for an e-way bill?

Log in to ewaybillgst.gov.in, go to Search, select Pin to Pin Distance, and enter the source and destination PIN codes to get the distance in kilometres.

4 What is the GST pin to pin distance?

It is the same road-distance figure, just referenced specifically in the context of GST compliance and e-way bill validity, as opposed to a general map or travel distance search.

5 Is there a separate pin to pin distance calculator for e-way bill use?

Yes. The e-way bill portal has a dedicated Pin to Pin Distance tool under its Search menu, and it is the only calculator whose figures are accepted for e-way bill validity and GST verification.

6 Can I search pin to pin distance directly on Google?

A regular Google search usually returns a travel distance or mileage estimate, not the GST-approved figure. Stick to the official e-way bill portal for compliance purposes.

7 What about pin to pin distance for unregistered transporters?

Unregistered transporters who enrol using PAN and Aadhaar on the e-way bill portal see the exact same pin to pin distance calculation as registered taxpayers. The tool is tied to the PIN codes entered, not the type of user account.

8 What if the pin to pin distance shown is wrong?

You can manually enter a higher distance, but only up to 10% above the system-calculated figure. Entering a lower distance to shorten validity is not permitted.

9 Does pin to pin distance apply to e-invoice as well?

Pin to pin distance itself is an e-way bill feature, but since e-invoice data feeds into e-way bill generation, an incorrect dispatch PIN on the invoice can throw off the distance calculation downstream.

10 What happens if my e-way bill expires mid-transit?

An expired e-way bill counts as non-compliant even if the goods are genuinely still moving, which can lead to detention and penalties under GST rules. Extensions should be requested within the permitted window, before expiry, not after.

Tags: