Integrating McLeod with Navix

The Navix-McLeod integration helps automate your freight audit process with minimal effort.

๐Ÿš€ Key Benefits 

  • Eliminate up to 11 manual audit steps per load 
  • 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 McLeod 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.): 

McLeod Current State - Sunny Day

๐Ÿงฉ What the Integration Includes 

Functionality 

Supported 

Loads Imported 

โœ… 

Audit Results Sent Back 

โœ… 

Documents Sent Back* 

โœ… 

AP/AR Approvals 

Optional 

Rate Engine Connection 

โŒ 

Disputes Integration

โŒ

*see Setup Overview section below 

โš™๏ธ Setup Overview 

PREREQUISITES: 

YOU MUST PURCHASE API ACCESS FROM MCLEOD DIRECTLY TO INTEGRATE 

TENANT MUST CONFIRM MCLEOD IMAGING IS CONFIGURED TO AUTOMATICALLY ATTACH DOCUMENTS INGESTED VIA THE API; WE ALSO SUGGEST REMOVING THE DEFAULT SETTING THAT COMPRESSES IMAGES  

If you need more information on what to communicate to McLeod to enable the above, please let us know and we can send you our playbook. 

Below are the set-up steps to enable the integration after you have API access and have confirmed the McLeod Imaging is configured appropriately: 

  1. API Credentials 
  2. Document Mapping
  3. Custom Fields 

๐Ÿ”’ Step 1: API Credentials 

  1. Create/fetch the API URL and API tokens for both the Dev and Production McLeod tenants.
  2. Send these to your implementation manager either via email or secure one-time share.

๐Ÿ”’ Step 2: Document Mapping 

  1. Provide Navix the nomenclature you currently have set up in McLeod for document types. 
  2. Your implementation manager will work with you to map Navix doc types to your standard doc types. 

๐Ÿงฉ Step 3: Configuration 

Work with your Navix implementation manager to provide any custom fields your team uses in McLeod. Here is a list of the custom fields we already pull into the Metadata section: 

  • DispatcherUserId 
  • HoldReason 
  • OrderType 
  • OrderStatus 
  • PaymentMethod 
  • VendorStatus
  • VendorMC
  • CommodityId
  • Commodity
  • BillingMethod 

Also, let us know if youโ€™d like the integration to mark the Orders Ready to Bill, aka Release them in McLeod.  Please note, McLeod does not allow RATE UPDATES to be made via the API so any rate updates must be manually made directly in McLeod.

๐Ÿ“Œ Here is a link to our Custom Field Form to get started. 

๐Ÿงช Testing (UAT) 

Navix will perform validations in Dev first, then Production. Not required, but highly recommended, you may grant a viewer-only license for Navix during testing, if available, to speed the UAT process. 

๐Ÿ› ๏ธ FAQs 

How often are updates sent to Navix, how often are updates sent to McLeod? This will vary depending on your volume anywhere between 15-120 minutes.  We spread out our push/pulls with higher volume to not bog down McLeod.What status do Order/Movement updates start flowing to Navix? We start pulling data in from McLeod when the Order moves to 'In Process'; this is something we can modify if there is a valid reason to deviate.Does Navix support Multi-Movement Orders? Yes; we can absolutely support this and process each invoice individually.

๐Ÿ“ž Need Help? 

Contact your onboarding manager or email support@navix.io