Integrating Tai with Navix

🚀 Key Benefits 

• Eliminate up to 8 manual audit steps per load
• Speed up exception handling and dispute resolution
• Unlock meaningful analytics without lifting a finger

🎥 Watch It in Action: Tai + Navix Integration Demo 

See how the integration works from end to end—without touching a spreadsheet. 

Click the gif to open the full video in a separate window.

In this video: 

1. A load is dispatched in Tai 
2. Navix pulls in and auto-creates the order 
3. Audit is completed and approved in Navix 
4. Finalized rates are updated, documents are attached, and bills and invoices are created and approved back into Tai 

🆚 Workflow Comparison 

Below is a visual of the typical steps taken to perform an audit with no exceptions in Tai without Navix and with Navix. Every red outline indicates a manual step.  Our customers typically see between 50-90% of their invoices flow through with no exceptions depending on mode split (LTL, TL, Dray, etc.): 

🧩 What the Integration Includes 

🔄 How the Integration Works

The integration moves data in two directions:

1. Tai → Navix (Load Ingestion). When a shipment is created or updated in Tai, Tai sends a `ShipmentUpdate` webhook to Navix. Navix pulls the full shipment and pricing detail, looks up carrier, remit-to, and accounting/payment-term information, and auto-creates a Navix order for audit—no manual entry. Navix protects against out-of-order updates, so a newer version of a shipment is never overwritten by a stale one.

2. Navix → Tai (Approval, Billing & Payment). Once an audit is completed and approved in Navix, the integration writes finalized rates, documents, invoices, and approved bills back into Tai. This is where the PreBill / Customer Billing, multivendor, and auto-invoicing / bill-approval capabilities come in.

💵 Billing & Payables Push-Back (What Happens After Approval)

When you approve an invoice in Navix, the integration writes results back into Tai in a defined sequence so nothing is billed before its charges are confirmed:

1. Documents are pushed to Tai — carrier/vendor documents are attached to the shipment, mapped to the correct Tai attachment type and access level (public/private).

2. Carrier (AP) charges are pushed to the shipment's carrier charges, broken out by transit type so multi-leg loads are handled correctly.

3. Customer (AR) charges are pushed to the shipment charges.

4. A customer invoice is created in Tai. 

5. Carrier bills are approved in Tai, one bill per transit type. If any step fails, Navix posts a named Shipment Alert to the Tai shipment—for example `Navix Add Doc Fail`, `Navix AP Update Fail`, `Navix AR Update Fail`, `Navix Create Invoice Fail`, or `Navix Approve Bill Fail`—so your team can spot and resolve the issue directly inside Tai. Because charge push-back and the invoice/bill steps are handled in two coordinated phases, Navix only creates the invoice and approves bills once the underlying rates have been confirmed.

🚚 Multi-Carrier (Multivendor) Loads

For loads with more than one carrier, Navix reconciles each carrier's bill individually. When Tai sends a `bill-create` event, Navix ties that bill to the correct shipment and carrier. Navix waits until all carrier bills are present before creating the customer invoice, and approves a separate bill for each transit type (numbered `-A`, `-B`, and so on). This ensures multi-leg and multi-carrier shipments bill accurately.

🧾 PreBill / Customer Billing*

PreBill is a dedicated billing path that lets documents and invoices move as soon as a document or order is approved in Navix, rather than waiting on the full invoice-approval cycle above.

- When a document is approved, Navix pushes it to the correct Tai shipment.

- When an order is approved, Navix creates the customer invoice in Tai. This is useful for customers who want billing to start moving earlier in the process.

*PreBill can be enabled on a per tenant basis.

⚙️ Setup Overview 

You’ll need to complete the following in both Sandbox and Production: 

1. Create a user for Navix
2. Configuration

🔐 Step 1: Create a User 

1. Go to Setup > Users > New User 
   1. We will utilize this user to create an API Key and direct the ShipmentUpdate webhook to our endpoint. 
      1. If you would prefer to complete these operations yourself and not provide a user login please let us know.

🧩 Step 2: Configuration 

1. Create the custom Shipment Alert ‘Navix Active Dispute’ in Tai

🧪 Testing (UAT) 

Navix will perform validations in Sandbox first, then Production. 

📞 Need Help? 

Contact your onboarding manager or email support@navix.io. 

🛠️ Considerations

- Navix pushes carrier (AP) and customer (AR) charges, attaches documents, creates the customer invoice, and approves carrier bills back into Tai automatically on approval.

- For multi-carrier loads, Navix waits until all carrier bills are present before creating the customer invoice.

- If something fails on push-back, look for a Navix Shipment Alert (e.g., `Navix Create Invoice Fail`, `Navix Approve Bill Fail`) on the Tai shipment.

- If a load needs to be re-pulled from Tai (for example, after a data correction), Navix support can trigger a manual re-ingestion without waiting for a new Tai webhook—contact support if you believe a load didn't import correctly.

🧠 Additional Resources 

📋 Tai Knowledge Center Article

Follow this link to Tai's knowledge center article.

🗺 Integration Architecture 

📋 Field Mapping Chart 

This link is a csv for Tai Field Mapping to Navix.  The link includes the following tabs: 

• Field Mapping Overview 
• Field Mapping Detail