Integrating Sunnybrook TMS with Navix

🚀 Key Benefits

🆚 Workflow Comparison

🧩 What the Integration Includes

🔄 How the Integration Works

⚙️ Setup Overview

🧠 Additional Resources

 

🚀 Key Benefits 

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

🆚 Workflow Comparison

Below is a visual of the typical steps taken to perform an audit with no exceptions in Sunnybrook 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 

Functionality	Supported
Shipments imported from Sunnybrook	✅
Documents sent back to Sunnybrook	✅
AP(carrier) charges pushed back to Sunnybrook	✅
AR(customer) charges pushed back to Sunnybrook	✅
Invoices auto-created & sent in Sunnybrook	✅
Carrier invoices approved in Sunnybrook	✅
Multi-carrier (multivendor) loads supported	✅
Rate Engine Connection	❌
Disputes Integration	❌

🔄 How the Integration Works

The integration moves data in two directions:

1. Sunnybrook → Navix (Shipment Ingestion). Navix polls for updated shipments in Sunnybrook every 15 minutes. Navix then pulls in carrier, remit-to, and customer information to auto-create Navix orders for audit with 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 → Sunnybrook (Rate Updates, Approvals, Billing & Payment). Once an audit is completed and approved in Navix, the integration writes finalized rates, documents, and carrier invoice back into Sunnybrook. Sunnybrook automatically creates and sends the customer invoice.

💵 What Happens After Approval

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

1. Rates (both AP and AR) are pushed to the shipment's charges, broken out by vendor so multi-vendor shipments are handled correctly.

2. Documents are pushed to Sunnybrook; carrier/vendor documents are attached to the shipment, mapped to the correct Sunnybrook attachment type.

3. Navix approves the customer facing documents.

4. The carrier invoice is created and approved. 

5. A customer invoice is created and sent from Sunnybrook. 

🚚 Multi-Carrier (Multivendor) Loads

For loads with more than one carrier, Navix reconciles each carrier's bill individually. Sunnybrook waits until all customer facing documents are approved before creating the customer invoice. 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 Sunnybrook shipment.

- When an order is approved, Navix pushes and approves all customer facing documents, which creates the customer invoice in Sunnybrook. 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 your Sunnybrook Production Environment: 

🔐 Step 1: Create a User 

We will utilize this user to create an API Key.
If you would prefer to complete this operation yourself and not provide a user login please let us know.

🧩 Step 2: Configuration 

Navix will pull enums from specific fields in your Sunnybrook environment to create the Master Data inside of Navix.

🧪 Testing (UAT) 

In Implementation users will be asked to validate that data is being sent and received correctly from both systems.

📞 Need Help? 

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

🛠️ FAQs

How often does Navix check Sunnybrook for updates? Navix polls on a recurring interval (currently every 15 minutes). Because Sunnybrook doesn't expose webhooks for shipment events, polling is the only supported way to pick up new and changed shipments; ie there's no way for Sunnybrook to notify Navix the moment something changes.

Will a shipment that changes status several times in one day create duplicate orders in Navix? No. Sunnybrook may return the same shipment more than once if it was modified multiple times between polls, but Navix's order creation call is keyed on the shipment's ID, so repeat updates apply to the existing order instead of creating duplicates.

Why isn't a shipment showing up in Navix yet? Only shipments in specific statuses are created or updated in Navix: Covered, Dispatched, At Shipper, En Route, At Receiver, Delivered, On Hold, Cancelled, Accounting Review, or Payment Processing. A shipment still sitting in an earlier planning status in Sunnybrook won't appear in Navix yet; that's expected, not an error.

Will our historical shipments be pulled in when the integration first turns on? Yes. When a new tenant is enabled, Navix backfills a historical window of shipments (60 days by default) before switching over to normal day-to-day polling.

Can we update rates through the integration? Yes. When there is a variance between what was expected (rates recorded in the TMS) and what is Approved in Navix, rates are updated back to Sunnybrook before sending or approving documents and invoices.  This prevents users from having to manually update rate variances in the TMS.

🧠 Additional Resources 

🗺 Integration Architecture