E-Way Bill Generation – Supplier Using Own Vehicle / Own Transport

1. Overview

This document explains the configuration and statutory requirements for generating an E-Way Bill in Merciglobal Cloud ERP when goods are transported by:

The supplier himself
The supplier’s own vehicle
The supplier’s own personnel
Any internal company logistics arrangement (not a third-party transporter)

In such cases, the supplier legally acts as the transporter under GST provisions, and system configuration must reflect the same.

2. Transporter Master Configuration (Mandatory Setup)

When the supplier transports goods using his own vehicle, a transporter master entry must be created as follows:

2.1 Transporter Master Entry

Field	Value
Transporter Name	Supplier’s Company Name
GST Number	Supplier’s Registered GSTIN
Transporter Type	Registered (if GSTIN available)

Note: Even if supplier and transporter are the same legal entity, a separate transporter master record is required in the ERP for E-Way Bill mapping.

3. Invoice Generation Process

During Sales Invoice creation:

Navigate to Sales → Invoice Creation.
Enter complete invoice details.
In the Transporter Field, select the supplier’s own company name (as created in Transporter Master).
Enter Vehicle Number if available.

4. PART A and PART B Generation Logic

Condition	System Behavior
Vehicle Number provided	PART A and PART B generated automatically
Vehicle Number not provided	Only PART A generated; PART B must be updated later

Vehicle number entry enables automatic generation of Part B in the E-Way Bill JSON payload.

5. Government of India – Standard E-Way Bill JSON Payload Structure

Merciglobal Cloud ERP generates the E-Way Bill JSON as per NIC (National Informatics Centre) E-Way Bill System specifications prescribed under GST Rules.

Below is the standard structure required for successful API submission.

5.1 Root Structure

The payload must be in JSON format with the following primary sections:

Version
TranDtls (Transaction Details)
DocDtls (Document Details)
SellerDtls
BuyerDtls
DispDtls (Dispatch Details – if different)
ShipDtls (Ship To – if different)
ItemList
ValDtls (Tax & Value Details)
TransDtls (Transport Details)

5.2 Standard JSON Payload Format

{
  "Version": "1.1",
  "TranDtls": {
    "TaxSch": "GST",
    "SupTyp": "OUTWARD",
    "RegRev": "N",
    "EcmGstin": null,
    "IgstOnIntra": "N"
  },
  "DocDtls": {
    "Typ": "INV",
    "No": "INV-001",
    "Dt": "20/02/2026"
  },
  "SellerDtls": {
    "Gstin": "29ABCDE1234F1Z5",
    "LglNm": "ABC PRIVATE LIMITED",
    "Addr1": "Address Line 1",
    "Loc": "Bengaluru",
    "Pin": 560001,
    "Stcd": "29"
  },
  "BuyerDtls": {
    "Gstin": "27ABCDE5678G1Z2",
    "LglNm": "XYZ TRADERS",
    "Addr1": "Address Line 1",
    "Loc": "Mumbai",
    "Pin": 400001,
    "Stcd": "27"
  },
  "ItemList": [
    {
      "SlNo": "1",
      "PrdDesc": "Product Name",
      "IsServc": "N",
      "HsnCd": "847130",
      "Qty": 10,
      "Unit": "NOS",
      "UnitPrice": 5000,
      "TotAmt": 50000,
      "Discount": 0,
      "AssAmt": 50000,
      "GstRt": 18,
      "IgstAmt": 0,
      "CgstAmt": 4500,
      "SgstAmt": 4500,
      "TotItemVal": 59000
    }
  ],
  "ValDtls": {
    "AssVal": 50000,
    "CgstVal": 4500,
    "SgstVal": 4500,
    "IgstVal": 0,
    "CesVal": 0,
    "StCesVal": 0,
    "Discount": 0,
    "OthChrg": 0,
    "RndOffAmt": 0,
    "TotInvVal": 59000
  },
  "TransDtls": {
    "TransId": "29ABCDE1234F1Z5",
    "TransName": "ABC PRIVATE LIMITED",
    "TransMode": "1",
    "Distance": "100",
    "TransDocNo": null,
    "TransDocDt": null,
    "VehNo": "KA01AB1234",
    "VehType": "R"
  }
}

5.3 Mandatory Rules as per GST E-Way Bill System

A. General Rules

Version must match NIC supported schema.
Date format: DD/MM/YYYY.
GSTIN must be valid and active.
State code (Stcd) must match GSTIN first two digits.
HSN code must be valid as per GST classification.
Total invoice value must match tax calculations.

B. Transaction Details (TranDtls)

SupTyp must be one of: OUTWARD, INWARD, IMPORT, EXPORT.
TaxSch must be "GST".
IgstOnIntra must be "Y" only if IGST is applied on intra-state supply.

C. Transport Details (TransDtls)

TransId is mandatory when transporter is registered (GSTIN).
TransMode values:
1 = Road
2 = Rail
3 = Air
4 = Ship
VehNo mandatory for Part B generation (Road transport).
Distance must be numeric (in KM).

D. Item Rules

IsServc = "N" for goods.
Quantity cannot be zero.
Tax amounts must reconcile with GST rate.

6. Own Vehicle Scenario – JSON Mapping Logic

When supplier transports goods using own vehicle:

JSON Field	Value Source
TransId	Supplier GSTIN
TransName	Supplier Legal Name
VehNo	Entered Vehicle Number
TransMode	"1" (Road)

In this case, supplier GSTIN is used both under SellerDtls and TransDtls.

7. Validation Checklist Before Submission

Transporter master created with correct GSTIN.
Vehicle number entered in valid format (e.g., KA01AB1234).
Invoice total matches tax calculation.
Distance entered (if required).
HSN and GST rates verified.

8. Error Handling Guidelines

Error Type	Possible Cause	Resolution
Invalid GSTIN	Incorrect transporter GSTIN	Verify master configuration
Invalid Vehicle Number	Wrong format	Correct vehicle format
Tax mismatch	Calculation inconsistency	Recalculate invoice
State code mismatch	Wrong Stcd value	Match GSTIN state code

9. Summary

When supplier acts as transporter:

Create transporter master using supplier GSTIN.
Select supplier company in transporter field during invoice.
Enter vehicle number for automatic Part B generation.
Ensure JSON payload complies with NIC E-Way Bill schema rules.

Proper configuration ensures seamless E-Way Bill generation without rejection from the GST portal.