# e-Way Bill
An e-Way Bill is the GST movement permit for goods. In FreeSpace you add transporter or vehicle details on an approved document, confirm the four party blocks, and generate the bill on the GST portal without leaving the ERP.
What an e-Way Bill is
Under GST, an e-Way Bill (Form EWB-01) is required when goods move and the consignment value is generally above ₹50,000. The value includes tax. You can still generate one below that threshold if the transporter or the destination state asks for it. Inter-state job work and some handicraft movements need a bill regardless of value.
The bill has two parts on the GST portal:
| **Part** | **What it records** | **Who typically fills it** |
|----------|---------------------|----------------------------|
| **Part A** | Who is sending, who is receiving, the supporting document, the goods, HSN, value, and the reason for movement. | The registered person causing the movement (your company in FreeSpace). |
| **Part B** | How the goods move — mode, distance, and either a vehicle number or a transport document (LR / RR / AWB / Bill of Lading). | You, if you know the vehicle; or the transporter, if you only assigned them in Part A. |
FreeSpace submits both parts in one request when you choose **Generate EWayBill**. Item lines, HSN, quantities, tax, document number, and document date come from the approved document — they are not typed on the confirm form.
Validity on the portal is based on distance (typically one day for the first 100 km for regular cargo, then one extra day per 100 km). Over-dimensional cargo uses a shorter distance per day. FreeSpace stores the portal's **valid till** date after a successful generate.
> An e-Invoice (IRN) and an e-Way Bill are independent in FreeSpace. Generating one does not create the other.
Where it is available
| **Document** | **e-Way Bill** | **Typical movement** |
|--------------|----------------|----------------------|
| Sale Invoice | Yes | Outward supply to a customer. |
| Delivery Challan | Yes | Outward or inward movement that is not itself a tax invoice — job work, own use, exhibition, line sales, inward receipt. |
| Purchase Debit Note | Yes | Outward purchase return to the supplier. |
| Credit Note | No | e-Invoice only. |
| Sale Debit Note | No | Not supported. |
Actions sit in the three-dot menu (⋮) after the document is approved:
| **Action** | **Sale Invoice** | **Delivery Challan** | **Purchase Debit Note** |
|------------|------------------|----------------------|-------------------------|
| **Add Transportation** | Approved, Closed, Pre Approved | Approved, Closed | Approved, Closed |
| **Generate EWayBill** | Approved, Closed, Pre Approved | Approved, Closed | Approved, Closed |
| **Cancel EWayBill** | Those statuses plus Cancelled / Pre Approved Cancelled | Approved, Closed, Cancelled | Approved, Closed, Cancelled |
**Add Transportation** and **Generate EWayBill** are hidden once a bill exists. **Cancel EWayBill** is shown only when one exists. The company plan must include e-Way Bill; otherwise the list column and actions stay hidden.
Prerequisites
- GST e-Way Bill enabled — your company plan includes e-Way Bill, and the business GSTIN is registered with the GST provider.
- Company GSTIN and phone — a 15-character GSTIN and a contact phone (6–12 digits) on the company, or on the branch when the branch prints its own address.
- Complete addresses — billing, shipping / consignee, and shipping-center addresses each need State (with a GST state code), District, Area, PIN, and both address lines. The generate step requires Address Line 2 even when the master address looks complete with one line.
- Party GSTIN — a 15-character GSTIN, or
URP for an unregistered person.
- Transportation details — add them with Add Transportation before you generate. The generate step fails if no transportation record exists.
Quick Start
- Approve the Sale Invoice, Delivery Challan, or Purchase Debit Note.
- Open the three-dot menu (⋮) and choose Add Transportation. Enter the mode, distance, and either a transporter (Part A) or a vehicle (Part B). Confirm.
- Choose Generate EWayBill. Review the pre-filled transaction type and the four party blocks. Correct anything the document did not carry (especially Address Line 2, state codes, and Ship To GSTIN).
- Confirm. On success the EWB number, date, validity, and portal link are stored and printed on the bill.
Add Transportation
**Add Transportation** saves one transportation record on the document. The generate step reads that record and sends it to the portal as Part A and/or Part B.
You cannot add a second record. Opening **Add Transportation** again edits the existing one. After an e-Way Bill is generated, the screen hides the action — change vehicle details on the GST portal (or cancel and regenerate) rather than editing in FreeSpace.
The form has three sections.
Transport Details
| **Field** | **What it means** | **Example** |
|-----------|-------------------|-------------|
| Transportation mode | How the consignment travels. Road (1), Rail (2), Air (3), or Ship (4). Defaults to **Road**. | A Kochi-to-Bengaluru truck movement: **Road**. A same-day spare-part dispatch on a passenger flight: **Air**. |
| Distance | Approximate kilometres between the dispatch PIN and the delivery PIN. The portal accepts 0–4000. Validity of the bill is calculated from this distance. | Kochi (682001) to Bengaluru (560001) is about 550 km — enter **550**. Do not enter 5500; the portal rejects values above 4000. |
> Intra-state movement of up to 50 km to a transporter's godown for further onward movement does not require Part B (vehicle) on the portal. In FreeSpace you can still save Part A only.
Part A — transporter
Use Part A when a third-party transporter will carry the goods and the vehicle is not known yet. The transporter later updates the vehicle on the GST portal using their Transporter Id.
| **Field** | **What it means** | **Example** |
|-----------|-------------------|-------------|
| Transporter Id | The transporter's GSTIN, or the 15-character enrolment id issued on ewaybillgst.gov.in to an unregistered transporter. This is the identity handed to the portal. | FastMove Logistics is GST-registered: enter their GSTIN, e.g. 29AABCF1234M1Z8. An unregistered lorry-broker enrolled on the portal: enter the TRANSIN they received at enrolment. |
| Transporter Name | Legal / trade name of the transporter. | FastMove Logistics Pvt Ltd |
| Transporter GSTN | Shown on the form next to Transporter Id. The saved record uses **Transporter Id** as the transporter identity. | Same GSTIN as Transporter Id when the transporter is registered. |
| Transporter Doc No | Lorry Receipt (LR), Railway Receipt (RR), Airway Bill, or Bill of Lading number. Required on the portal when mode is Rail, Air, or Ship. | LR **FM/2026/18442** issued by FastMove. |
| Transporter Doc Date | Date of that transport document. | The LR date, e.g. 20 Sep 2026. |
Part B — vehicle
Use Part B when you know the conveyance. Completing Part B is what makes the bill valid for movement on the road.
| **Field** | **What it means** | **Example** |
|-----------|-------------------|-------------|
| Vehicle No | Registration number of the truck or tempo. Letters and digits, typically 4–20 characters as the portal stores them (no spaces). | **KL07AB1234** for a Kerala-registered truck. |
| Vehicle Type | **Regular** (R) for a normal goods vehicle, or **ODC** (O) for Over-Dimensional Cargo that exceeds standard length / width / height. ODC uses a shorter validity (about one day per 20 km). | A 9-tonne closed container: **Regular**. A 16-metre wind-turbine blade on a hydraulic trailer: **ODC**. |
When to use Part A, Part B, or both
| **Situation** | **Fill** | **What happens** |
|---------------|----------|------------------|
| Own or hired truck; driver is at the gate and you know the number | Part B (and mode + distance) | The bill is complete for movement. Transporter Id can stay empty. |
| Goods handed to a transporter; vehicle will be assigned tonight | Part A only — Transporter Id is the important field | Part A is complete. The transporter updates the vehicle on the GST portal before the truck starts. |
| Transporter already issued an LR and told you the vehicle | Part A and Part B | The bill is complete (transporter + vehicle). |
| Rail / air / ship | Mode + transport document number and date. Vehicle No is not used. | The transport document stands in for the vehicle. |
Worked example — own truck on a sale invoice:
1. Approve invoice SI-2026-1044 for Southern Spices, Kochi → a Bengaluru distributor, value ₹1,80,000.
2. **Add Transportation**: mode **Road**, distance **550**, Vehicle No **KL07AB1234**, Vehicle Type **Regular**. Leave transporter fields blank.
3. **Generate EWayBill**. The portal returns an EWB number that the driver carries (print or SMS).
Worked example — transporter will assign the vehicle:
1. Same invoice. You have booked FastMove but they have not allocated a truck.
2. **Add Transportation**: mode **Road**, distance **550**, Transporter Id = FastMove GSTIN, Transporter Name = FastMove Logistics. Leave Vehicle No blank.
3. **Generate EWayBill**. FastMove logs into the GST portal with that Transporter Id and fills the vehicle before departure.
Generate EWayBill
After transportation is saved, **Generate EWayBill** opens the confirm form. Most fields are pre-filled from the document. You can edit them before Confirm.
The form is organised as:
1. **Transaction Details** — direction, reason, supporting document, and how the four parties relate.
2. **Consignor Details – Bill From** — who is billing as the sender.
3. **Consignor Details – Dispatch From** — the physical place the goods leave.
4. **Consignee Details – Bill To** — who is billed as the receiver.
5. **Consignee Details – Ship To** — the physical place the goods arrive.
On an **Outward** document the consignor is your company (or branch) and the shipping center; the consignee is the customer (sale / challan) or the supplier (purchase debit note). On an **Inward** delivery challan the roles reverse — the supplier is the consignor and your company is the consignee.
Transaction fields
| **Field (screen)** | **What it means** | **When to use it** | **Example** |
|--------------------|-------------------|--------------------|-------------|
| Supply Type | Direction of movement. **Outward** = goods leaving you. **Inward** = goods coming to you. | Sale Invoice is always Outward (the screen refuses Inward). Purchase Debit Note is always Outward (return to the supplier). Delivery Challan can be either. | Invoice to a customer: **Outward**. Delivery Challan for goods arriving from a vendor who did not generate their own e-Way Bill: **Inward**. |
| Sub Type | Reason for the movement, reported to the portal. | Match the commercial reason, not just “it is a sale”. | See the Sub Type table below. |
| Document Type | The supporting document the officer would ask for. | Must match the FreeSpace document you generated from. | Sale Invoice → **Tax Invoice**. Delivery Challan → **Delivery Challan**. Purchase Debit Note → **Debit Note**. |
| Transaction Type | Whether Bill-From equals Dispatch-From, and whether Bill-To equals Ship-To. Codes match the NIC master: Regular (1), Bill to ship to (2), Bill from and ship (3), Combination 2 and 3 (4). | Driven by comparing the Bill-From state with the Dispatch-From state, and the Bill-To state with the Ship-To state. | See Transaction Type examples. |
| Sub Supply Description | Free-text reason. Shown only when Sub Type is **Others**. Required on the screen before Confirm. | Purchase returns, samples, or any reason not in the list. | On a purchase debit note this defaults to **Purchase Return**. |
Defaults the screen sets before you edit:
| **Document** | **Supply Type** | **Sub Type** | **Document Type** | **Transaction Type** |
|--------------|-----------------|--------------|-------------------|----------------------|
| Sale Invoice | Outward | Supply | Tax Invoice | Regular (1) |
| Delivery Challan | Outward or Inward (from the challan) | Line Sales | Delivery Challan | Regular (1) |
| Purchase Debit Note | Outward | Others, description Purchase Return | Debit Note | Regular (1) |
**Sub Type** values and a real use for each:
| **Sub Type** | **Use it when** | **Example** |
|--------------|-----------------|-------------|
| Supply | A normal taxable sale of goods. | Invoice for 200 cartons of spice mix sold to a distributor. |
| Line Sales | Route / van sales where goods leave the warehouse for a sales beat. Default on a delivery challan. | Morning load of packed snacks on a delivery van that will invoice shops during the day. |
| Exhibition or fairs | Goods sent to a stall and expected back (or sold there). | Sending display machines to a Kochi trade fair on a delivery challan. |
| For Own Use | Movement between your own locations, not a sale. | Transfer of packing material from the factory to your own retail store. |
| SKD/CKD/Lots | Semi- or completely-knocked-down goods moved in lots. | Motorcycle kits shipped in three lots from the assembly plant to a dealer. |
| Export | Goods moving toward an export shipment. | Cartons moving from the factory to the Cochin port CFS against an export invoice. |
| Import | Inward movement of imported goods (usually with a Bill of Entry). | Container cleared at the port, moving to your warehouse — inward challan, Document Type **Bill of Entry**. |
| Job Work | Goods sent to a job worker. Inter-state job work needs an e-Way Bill even below ₹50,000. | Fabric sent from your mill to a dyeing unit in another state on a delivery challan. |
| Job work returns | Goods coming back from (or going back to) a job worker. | Dyed fabric returning to the mill — inward challan, Sub Type **Job work returns**. |
| Sales return | Goods coming back against a sale. | Customer returning damaged stock on an inward challan. A purchase-side return uses a debit note with **Others** / Purchase Return instead. |
| Recipient Not Known | The final buyer is not identified at dispatch (e.g. some approval / line-sale models). | Van leaves with stock to be placed at whichever retailer confirms the order that day. |
| Others | Any other reason. **Sub Supply Description** becomes mandatory. | Purchase return of rejected raw material — description **Purchase Return**. |
**Document Type** values:
| **Document Type** | **Meaning** |
|-------------------|-------------|
| Tax Invoice | Movement backed by a GST tax invoice. |
| Bill of Supply | Exempt or composition goods — no tax invoice. |
| Bill of Entry | Import clearance document. |
| Delivery Challan | Movement that is not a sale invoice (job work, own use, exhibition, and the Delivery Challan document). |
| Credit Note | Movement backed by a credit note. Not generated from FreeSpace Credit Note. |
| Debit Note | Movement backed by a debit note — used on Purchase Debit Note. |
| Others | Any other supporting document. |
Transaction Type examples
Think of four boxes: **Bill From**, **Dispatch From**, **Bill To**, **Ship To**. Transaction Type tells the portal which boxes are the same person/place and which are different.
| **Type** | **What is the same** | **Real example** |
|----------|----------------------|------------------|
| Regular (1) | Sender place is one; receiver place is one. | Southern Spices invoices and ships from its Kochi warehouse to North Foods' Delhi godown. Billing address and shipping address are both Delhi. States match on each side. |
| Bill to ship to (2) | Sender is one place. The party you bill is not the place the truck goes. | North Foods (Delhi GSTIN) buys the goods, but asks you to deliver to its Pune warehouse (Maharashtra). Bill To = Delhi; Ship To = Pune. From 1 August 2026, Ship To GSTIN is mandatory and must differ from Bill To GSTIN. |
| Bill from and ship (3) | Receiver is one place. You invoice from one registration and dispatch from another state. | Head office in Bengaluru raises the invoice (Bill From = Karnataka). Goods leave the Chennai warehouse (Dispatch From = Tamil Nadu). Customer in Hyderabad is both Bill To and Ship To. |
| Combination 2 and 3 (4) | Both sides differ. | Bengaluru HO invoices a Delhi company, goods leave the Chennai warehouse, and the truck delivers to the Delhi company's Pune site. Ship To GSTIN is mandatory. |
**Bill to–Ship to as the GST Council describes it**
Three parties, two invoices, **one** e-Way Bill:
- **A** orders **B** to send goods directly to **C**.
- Invoice 1: B → A. Invoice 2: A → C.
- Either A or B may generate the e-Way Bill, not both.
If **B** (you, the supplier) generates it in FreeSpace:
| **Block** | **Fill with** |
|-----------|----------------|
| Bill From | B — your company GSTIN and name. |
| Dispatch From | B's warehouse address. |
| Bill To | A — the party you invoiced. |
| Ship To | C — delivery address, plus C's GSTIN in **Ship To GSTIN**. |
| Transaction Type | **Bill to ship to (2)** if you dispatch from the same state you bill from; **Combination (4)** if the warehouse is in another state. |
Bill From & Dispatch From (consignor)
The consignor is the sender. **Bill From** is who appears as the supplier on the bill. **Dispatch From** is the pin-coded place the truck actually leaves. In a Regular transaction they describe the same business; in types 3 and 4 the warehouse is in a different state from the billing GSTIN.
| **Field** | **Block** | **What it means** | **Pre-filled from (outward)** | **Required to generate** |
|-----------|-----------|-------------------|-------------------------------|--------------------------|
| Name | Bill From | Legal name of the consignor. | Company legal name, or branch company name when the branch shows its address on the bill. Inward challan: the supplier name. | Yes |
| GSTIN | Bill From | 15-character GSTIN of the consignor. | Company or branch GSTIN. Inward challan: supplier GSTIN. | Yes, exactly 15 characters |
| State | Bill From | State of the billing GSTIN (Bill-From state). Must have a GST state code (32 for Kerala, 29 for Karnataka, …). | Company / branch state, or the billing address state on an inward challan. | Yes, including state code |
| Address Line 1 | Dispatch From | First line of the physical dispatch address. | Shipping center address line 1. Inward challan: supplier shipping address line 1. | Yes |
| Address Line 2 | Dispatch From | Second line of the dispatch address. | Shipping center line 2. | Yes — add a landmark or area if the master has only one line |
| Country | Dispatch From | Country of dispatch. State / District / Area lists filter from this. | Shipping center country. | Needed so State can be selected |
| State/Province | Dispatch From | Actual state the goods leave (Dispatch-From state). | Shipping center state. | Yes, including state code |
| District/Region | Dispatch From | District of the dispatch PIN. | Shipping center district. | Needed on the form; send the matching location |
| Area | Dispatch From | Locality / area (Place of consignor on the portal). | Shipping center area. | Yes |
| Pincode | Dispatch From | 6-digit PIN of the dispatch location. | Shipping center PIN. | Yes |
Worked example — Regular outward invoice:
- Bill From Name: Southern Spices Pvt Ltd
- Bill From GSTIN: 32AABCS1234A1Z5
- Bill From State: Kerala (code 32)
- Dispatch From: Plot 12, KINFRA Park, Kakkanad, Ernakulam, 682030
Worked example — type 3 (dispatch from another warehouse):
- Bill From stays the Bengaluru HO GSTIN and Karnataka.
- Dispatch From Address / State / PIN switch to the Chennai warehouse (Tamil Nadu, 600001).
Bill To & Ship To (consignee)
The consignee is the receiver. **Bill To** is who is billed. **Ship To** is the pin-coded place the truck arrives. In a Regular transaction they are the same party; in types 2 and 4 the delivery location (and often the GSTIN) is different.
| **Field** | **Block** | **What it means** | **Pre-filled from (outward)** | **Required to generate** |
|-----------|-----------|-------------------|-------------------------------|--------------------------|
| Name | Bill To | Legal name of the billed party. | Customer name. Debit note: supplier name. Inward challan: your company. | Yes |
| GSTIN | Bill To | GSTIN of the billed party, or URP. | Customer / supplier GSTIN. Empty becomes URP on the portal. | If present, must be 15 characters |
| State | Bill To | Place of supply / Bill-To state. Must have a state code. | Billing address state. Inward challan: company state. | Yes, including state code |
| Address Line 1 | Ship To | First line of the delivery address. | Shipping address, or the separate consignee address when one is used. | Yes |
| Address Line 2 | Ship To | Second line of the delivery address. | Shipping / consignee line 2. | Yes |
| Country | Ship To | Country of delivery. | Shipping address country. | Needed so State can be selected |
| State/Province | Ship To | Actual state the goods arrive (Ship-To state). | Shipping / consignee state. | Yes, including state code |
| District/Region | Ship To | District of the delivery PIN. | Shipping / consignee district. | Needed on the form |
| Area | Ship To | Locality of delivery (Place of consignee on the portal). | Shipping / consignee area. | Yes |
| Pincode | Ship To | PIN of the delivery location. | Shipping / consignee PIN. | Yes |
| Ship To GSTIN | Ship To | GSTIN of the party who physically receives the goods. | Consignee address GSTIN, else customer / supplier GSTIN, else URP. Inward challan: your company GSTIN. | Mandatory for types 2 and 4 |
| Ship To Trade Name | Ship To | Trade name of the receiving party. Optional. | Consignee or customer / supplier name. | No |
Ship To GSTIN & Trade Name
GSTN/NIC require the Ship-To GSTIN separately from the Bill-To GSTIN. This matters from **1 August 2026** for Transaction Types **2** and **4**.
| **Rule** | **Detail** |
|----------|------------|
| When mandatory | **Bill to ship to (2)** and **Combination 2 and 3 (4)**. |
| Valid values | A 15-character GSTIN matching the usual pattern (2 digits + 13 letters/digits), or URP if the receiving party is unregistered. |
| Must be distinct | On types 2 and 4, Ship To GSTIN cannot equal Bill To GSTIN — the two parties are expected to be different. |
| Types 1 and 3 | A distinct Ship To GSTIN is not required. If you leave it empty, the portal is sent URP. |
| Trade Name | Optional. |
| Editable | Pre-filled, then editable on the confirm form. |
Worked example — type 2:
- Bill To GSTIN: 07AABCN5678B1Z9 (North Foods, Delhi)
- Ship To GSTIN: 27AABCN5678B1Z1 (North Foods' Maharashtra registration at the Pune warehouse)
- Ship To Trade Name: North Foods — Pune DC
- If the Pune site has no GSTIN, enter URP — do not copy the Delhi GSTIN.
After generation
On success the document stores:
| **Stored on the document** | **Source** |
|----------------------------|------------|
| EWB number | Portal e-Way Bill number (12 digits). |
| EWB date | Generation date/time from the portal. |
| Valid till | Portal validity. |
| Portal link | URL printed on the bill. |
| The confirm-form values | Supply type, parties, Ship To GSTIN, and the rest of the form you confirmed. |
The list shows an **e way** flag. The printed bill shows the number, date, validity, Ship To GSTIN, and link.
Item lines sent to the portal are built from the document: item name, HSN (dots removed), quantity, unit short form, CGST / SGST / IGST / cess rates, and taxable amount. Lines hidden as FOC on the print are omitted. Document number is the bill number; document date is the transaction date.
Cancel an e-Way Bill
Use **Cancel EWayBill** when the goods will not move as declared. The GST rule is: cancel within 24 hours, and only if the bill has not been verified in transit.
| **Field** | **What it means** |
|-----------|-------------------|
| Cancel Reason | **Duplicate**, **Order Cancelled**, **Data Entry mistake**, or **Others**. Required. |
| Cancel Remarks | Optional explanation. |
The action is shown only when an e-Way Bill already exists. After a successful cancel, add transportation again if needed and generate a new bill.
Typical reasons:
- **Duplicate** — you generated twice for the same movement.
- **Order Cancelled** — the customer cancelled before the truck left.
- **Data Entry mistake** — wrong vehicle, PIN, or GSTIN. Cancel and regenerate.
- **Others** — any other reason, with a remark.
FAQ
Does generating an e-Invoice also create the e-Way Bill?
No. Add transportation and generate the e-Way Bill as its own action.
What do I enter when the receiving party has no GSTIN?
Enter URP (Unregistered Person) in the GSTIN field. The same value is valid for Ship To GSTIN.
When is Ship To GSTIN required?
For Transaction Type Bill to ship to (2) and Combination 2 and 3 (4), from 1 August 2026. It must be a valid GSTIN or URP, and different from the Bill To GSTIN.
Why did generate fail with a list of missing fields?
The usual gaps are Address Line 2, a state without a GST code, missing Area, missing PIN, missing company phone, or no transportation record. For types 2 and 4, also check Ship To GSTIN.
Can I generate an e-Way Bill for an inward movement?
Yes, from a Delivery Challan with Supply Type Inward. The supplier becomes the consignor and your company becomes the consignee. Do not use Inward on a Sale Invoice.
Can I generate an e-Way Bill on a purchase debit note?
Yes. The movement is outward (goods going back to the supplier). Defaults are Sub Type Others, description Purchase Return, Document Type Debit Note. Sale debit notes do not support e-Way Bill.
Why can't I add a second transportation record?
Only one record is allowed per document. Open Add Transportation again to edit it. After a bill is generated, the screen hides that action.
Is an e-Way Bill required below ₹50,000?
Usually no, except inter-state job work, some handicraft movements, and when the destination state or the transporter requires it. FreeSpace will still generate one if you ask.
Do I need Part B for a short intra-state hop to the transporter?
GST allows skipping the vehicle when goods move up to 50 km within the state to the transporter for further transportation. You can save Part A only in that case.
## Errors and warnings
Exact messages for e-Way Bill from the ERP screen and `fs_api`. Visitors do not see this section; Vertex AI Search uses it to answer questions about on-screen errors.
### Transportation details required
- **Type:** Error (blocks Generate EWayBill)
- **Action:** Generate EWayBill
- **When:** No `transportationOnTransaction` record exists on the document.
- **Example message:** *Transportation details required* (`fs_api`, in the numbered HTML list).
- **Outcome:** e-Way Bill is not generated.
- **Solution:** Use **Add Transportation**, then Generate EWayBill again.
### Consignor phone missing or invalid
- **Type:** Error
- **Action:** Generate EWayBill
- **When:** Company (or branch, when the branch prints its address) has no phone, or the phone is shorter than 6 or longer than 12 characters.
- **Example message:** *Consignor Phone number is required* or *Invalid Consignor Phone Number*
- **Outcome:** e-Way Bill is not generated.
- **Solution:** Save a 6–12 character phone on Company Details or the branch, then generate again.
### Consignor GSTN / legal name / Bill From state
- **Type:** Error
- **Action:** Generate EWayBill
- **When:** Confirm-form / request body is missing consignor GSTIN, name, Bill From state, or the state has no `code`. GSTIN length is not 15.
- **Example message:** *Consignor GSTN is required*; *Invalid Consignor GSTN*; *Consignor legal name is required*; *Consignor Bill From State is required*; *Consignor Bill From State - state code is required*
- **Outcome:** e-Way Bill is not generated.
- **Solution:** Fill Bill From Name, 15-character GSTIN, and State with a GST state code.
### Consignor dispatch address incomplete
- **Type:** Error
- **Action:** Generate EWayBill
- **When:** Dispatch From Address Line 1, Address Line 2, Dispatch From state (or its code), Area, or PIN is empty.
- **Example message:** *Consignor Address1 is required*; *Consignor Address2 is required*; *Consignor Dispatch From State is required*; *Consignor Dispatch From State - state code is required*; *Consignor Place/Area is required*; *Consignor Pincode is required*
- **Outcome:** e-Way Bill is not generated.
- **Solution:** Complete both address lines, State/Province with a code, Area, and Pincode on Dispatch From.
### Consignee party incomplete
- **Type:** Error
- **Action:** Generate EWayBill
- **When:** Bill To name, Bill To state (or code), Ship To addresses, Ship To state (or code), Area, or PIN is empty. Consignee GSTIN is present but not length 15.
- **Example message:** *Cosignee legal name is required*; *Invalid Consignee GSTN*; *Consignee Bill To State is required*; *Consignee Bill To State - state code is required*; *Consignee Address1 is required*; *Consignee Address2 is required*; *Consignee Ship To State is required*; *Consignee Ship To State - state code is required*; *Consignee Place/Area is required*; *Consignee Pincode is required*
- **Outcome:** e-Way Bill is not generated.
- **Solution:** Complete Bill To Name / State and both Ship To address lines, State/Province, Area, and Pincode.
### Ship To GSTIN missing, invalid, or same as Bill To
- **Type:** Error
- **Action:** Generate EWayBill
- **When:** `transactionType` is 2 or 4 and `shipToGstin` is empty, not `URP` and not a 15-character GSTIN, or equals `gstinConsignee`. Also when a Ship To GSTIN is sent on other types and is neither `URP` nor a valid GSTIN.
- **Example message:** *Ship To GSTIN is required*; *Invalid Ship To GSTIN*; *Ship To GSTIN should not be the same as Bill To GSTIN*
- **Outcome:** e-Way Bill is not generated.
- **Solution:** Enter a valid GSTIN or `URP` that differs from Bill To GSTIN on types 2 and 4.
### Sub supply description required (ERP screen)
- **Type:** Error (blocks Confirm on the screen)
- **Action:** Generate EWayBill → Confirm
- **When:** Sub Type is **Others** and Sub Supply Description is empty. Checked in the ERP before the API call. `fs_api` generate validation does not emit this string.
- **Example message:** *Sub supply description is required*
- **Outcome:** The request is not sent.
- **Solution:** Enter a description (for a purchase debit note the default is *Purchase Return*).
### Supply type inward on sale invoice (ERP screen)
- **Type:** Error
- **Action:** Generate EWayBill
- **When:** Sale Invoice confirm data has Supply Type inward.
- **Example message:** *Supply type inward not handled for sale invoice*
- **Outcome:** The request is not sent.
- **Solution:** Leave Supply Type as **Outward**. Use a Delivery Challan for inward movements.
### Delivery Challan consigner / consignee missing (save)
- **Type:** Error (blocks save of the challan, not generate)
- **Action:** Save, Save And Approve
- **When:** Outward challan has no customer, or inward challan has no supplier.
- **Example message:** *Please provide consignee details* (outward) or *Please provide consigner details* (inward)
- **Outcome:** Challan is not saved.
- **Solution:** Select the customer (outward) or supplier (inward).
### E-Way Bill not generated (cancel)
- **Type:** Error
- **Action:** Cancel EWayBill
- **When:** The document has no stored e-Way Bill.
- **Example message:** *EWayBill not generated for this invoice*; *EWayBill not generated for this delivery challan*; *EWayBill not generated for this debit note*
- **Outcome:** Cancel is rejected.
- **Solution:** Generate the e-Way Bill first, or open the document that already has one.
### Portal / GSP rejected generate
- **Type:** Error
- **Action:** Generate EWayBill
- **When:** The GSP or NIC portal returns `error_description`, `errorMessage`, or HTTP-style code 204.
- **Example message:** The portal text is returned as `INVALID_EWAYBILL`. No single fixed string.
- **Outcome:** e-Way Bill is not stored.
- **Solution:** Fix the field the portal names (distance, HSN, GSTIN, PIN mismatch, and so on) and generate again.
### Portal / GSP rejected cancel
- **Type:** Error
- **Action:** Cancel EWayBill
- **When:** The portal rejects cancel (window expired, already verified in transit, or GSP error).
- **Example message:** Portal `errorMessage` is returned as `INVALID_EINVOICE` or `BAD_REQUEST`.
- **Outcome:** The bill stays active in FreeSpace.
- **Solution:** Cancel on the GST portal if the 24-hour window or verification rule blocks the API, or wait and issue a new bill after the movement is resolved.
### Multiple transportation details
- **Type:** Error
- **Action:** Add Transportation (`PUT …/transportation/`)
- **When:** More than one transportation row already exists for the document.
- **Example message:** *Multiple tranportation details found. Contact Developer*
- **Outcome:** The record is not updated.
- **Solution:** Contact support to clean the extra row. Normal use never creates a second row.
### Generate / cancel success
- **Type:** Success
- **Action:** Generate EWayBill, Cancel EWayBill
- **When:** Portal accepted the request and FreeSpace stored the result.
- **Example message:** Generate: *E-Way Bill generated successfully*. Cancel: *E way bill cancelled successfully*. Delivery Challan cancel currently returns *E invoice cancelled successfully*.
- **Outcome:** Number / cancel flag is stored on the document.
- **Solution:** None.