TMS Documentation
      Back to home
      1. Knowledge Base
      2. Tai Software Write Ups
      3. TMS Documentation

      Customer Facing EDI Support

      Tai TMS can add EDI Functionality to support the needs of your end customers when automating shipment creation, tracking, and invoicing functionality. This will require a setup by the Integration Team. Setup fees may be incurred. 

      Tai TMS will process EDI files based on the X12 - 4010 Standard

      Files can be transmitted via FTP / SFTP / FTPS / AS2

      Please fill out and return the following form:  Tai Software EDI Information Sheet along with any sample files or specs the customer needs us to adhere to.

      Table of Contents

      1. Supported EDI Documents

      2. EDI Workflow For Shipments

      3. EDI Project Discovery/Integration Workflow

      Supported EDI Documents:

      • 204 (Load Tender - Incoming) Customers send Tai a load tender and we Create Shipment (Requires setup and mapping to customer).
        • Only '00' Original EDI 204s are processed.  Other EDI 204s such as Cancellation and Change can be received but are not able to be processed to update existing shipment details.
      • 997 (Functional Acknowledgement) We send an acknowledgment indicating that we received the 204.
      • 990 (Load Tender - Response) We do support sending both an acceptance and rejection for Truckload shipments; LTL auto-accepts.
      • 214 (Status Updates - Outgoing) When we receive status updates from Carriers and the status of shipment changes, we submit this change to the customer in this file.
        • The EDI 214 process is based on actual status changes occurring on the shipment
      • 210 (Invoicing) When this is active (Customer Invoicing Method = Digital), we will submit a 210 for the customer.

      EDI Workflow For Shipments:


      The key points to keep in mind are:
      • The customer will be sending over the dispatch request (204) which will build the shipment in the TMS.
      • Once we receive the dispatch request we'll send them an automatic response (997) essentially just letting them know that the file was successfully received.
      • At that point, the created shipment will be in "Quote" status.
        • From there when a shipment is moved from Quoted to Committed, we'll generate an Acceptance file (990 acceptance)
        • When a shipment is moved to Canceled, we'll generate a Rejected file (990 Rejected)
      • Then as the shipment's status gets updated, we'll send the status updates (214). These are triggered with the In transit, Out for Delivery, and Delivered statuses.
      • Lastly, once the invoice is created in the TMS, we'll send over the Invoice via EDI (210).
        • Customers set up for EDI 210s also will be able to re-generate the EDI 210, if needed. a 'Generate Digital Invoice' button will be available on the Accounting dropdown on the Shipment Profile. 
          • Availability of the button is based on the Customer's Preferred Invoicing Method being set to 'Digital' and the EDI 210 setup existing for the customer.

       

      EDI Project Discovery/Integration Workflow:

      1. Project Initiation and Requirement Gathering:

        • Upon receiving a project request and specifications from the partner, we initiate the process by thoroughly reviewing the provided specifications.

      2. Scope Definition:

        • A comprehensive scope is drafted based on the specifications received, outlining the project's objectives, requirements, and deliverables.

      3. Scope Review and Confirmation:

        • The drafted scope is shared with the broker for review and discussion. Any necessary changes, including hardcoding or default settings, are addressed during this phase to ensure alignment with project goals.

      4. Dynamic Scope Document Management:

        • The scope is maintained as a live document using Google Docs, facilitating real-time updates and additions. This serves as a centralized repository for all project-related information, enabling easy access and future reference.

      5. Statement of Work (SOW) Preparation:

        • Upon approval of the scope, we proceed with the preparation of the Statement of Work, outlining the project's terms, deliverables, and timelines.

      6. SOW Approval and Commencement:

        • Once the Statement of Work is finalized and signed by both parties, we initiate the mapping process on our end in accordance with the agreed scope and SOW.

      7. Mapping and Configuration:

        • Our team completes the mapping process to configure the necessary systems and interfaces as per the agreed-upon specifications and requirements.

      8. Testing and Feedback:

        • We engage with the EDI partner/customer to commence testing, allowing for any necessary tweaks or additions to be addressed. Testing is preferably conducted in a production environment to ensure accurate evaluation and feedback for all parties.

      9. Finalization and Go-Live Planning:

        • Following successful testing and validation, we collaborate with the partner/customer to determine the optimal go-live date, ensuring alignment and readiness across all stakeholders.