Wednesday, July 3, 2024

EDI : Transportation Flow ANSI-X12 200 Series

 Below is a detailed, step-by-step flow of transportation processes using ANSI X12 transactions.


1. Order Creation and Shipment Planning

Transaction Set Used:

  • 204 - Motor Carrier Load Tender
    • The shipper (customer) sends a load tender to a carrier, specifying shipment details, including:
      • Pickup and delivery locations.
      • Shipment details like weight, volume, and special handling instructions.
      • Requested service type and schedule.

Key Steps:

  1. Shipper gathers shipment requirements.
  2. An EDI 204 document is generated and transmitted to the carrier.
  3. Carrier acknowledges receipt using 997 Functional Acknowledgment.

2. Shipment Confirmation and Acceptance

Transaction Sets Used:

  • 990 - Response to Load Tender
    • Carrier responds to the load tender with acceptance, decline, or modifications.

Key Steps:

  1. Carrier evaluates the 204 request for feasibility.
  2. Carrier sends back a 990:
    • "Accepted" if they can fulfill the request.
    • "Declined" if they cannot handle the shipment.
  3. Shipper receives the 990 and updates their systems.

3. Shipment Scheduling

Transaction Sets Used:

  • 210 - Motor Carrier Freight Details and Invoice
    • An invoice specifying shipment costs is created.
  • 211 - Motor Carrier Bill of Lading
    • Details about the shipment (items, quantities, weights, etc.).

Key Steps:

  1. Shipper provides load information to the carrier using the 211.
  2. Carrier uses this to prepare the shipment and sends the 210 invoice for approval.

4. Shipment Pickup and Tracking

Transaction Sets Used:

  • 214 - Transportation Carrier Shipment Status Message
    • Updates on shipment status (e.g., pickup confirmation, in-transit status, delays).

Key Steps:

  1. Carrier picks up the shipment and sends a 214 confirming pickup.
  2. Status updates (e.g., "In Transit", "Delayed", or "Delivered") are sent regularly via the 214.

5. Delivery Confirmation

Transaction Sets Used:

  • 214 - Transportation Carrier Shipment Status Message (with delivery update).
  • 824 - Application Advice
    • Used if there are discrepancies or issues during delivery.

Key Steps:

  1. Carrier delivers the shipment and sends a final 214 with the "Delivered" status.
  2. Any delivery issues or adjustments are communicated using an 824.

6. Invoicing and Payment

Transaction Sets Used:

  • 210 - Motor Carrier Freight Details and Invoice
    • Final invoice from the carrier to the shipper.
  • 820 - Payment Order/Remittance Advice
    • Payment details sent by the shipper to the carrier.

Key Steps:

  1. Carrier sends the 210 with the finalized shipment charges.
  2. Shipper reviews the invoice and makes payment via 820.
  3. Payment confirmation is sent back to the carrier.

7. Reporting and Reconciliation

Transaction Sets Used:

  • 214 - Transportation Carrier Shipment Status Message
  • 997 - Functional Acknowledgment
  • 824 - Application Advice

Key Steps:

  1. Both parties reconcile invoices, shipment statuses, and payments.
  2. Functional acknowledgments (997) confirm the receipt of all transactional messages.
  3. Any errors or disputes are addressed through 824 documents.

End-to-End Flow Overview:

  1. 204: Shipper sends load tender.
  2. 990: Carrier responds to the tender.
  3. 211: Bill of lading shared by the shipper.
  4. 214: Shipment status updates during transit and delivery.
  5. 210: Final invoice sent by the carrier.
  6. 820: Payment made by the shipper.
  7. 997: Acknowledgments exchanged to confirm receipt of transactions.
  8. 824: Discrepancy resolution

No comments: