Release Notes 3/30/26 - 4/12/26

🚀 Enhancements

ADD SERVICE TYPE AS FILTER

• Navix customers with multiple freight teams (e.g., Truckload vs. LTL vs. Drayage) previously had no way to filter workflow queues by Service Type. This forced users into constant workarounds — building large carrier-based filter groups or using imperfect proxies like Source (Email vs. EDI). For some tenants, who submit all invoices via API, even these workarounds are unavailable, making this a go-live blocker. To solve this issue, we’ve added a Service Type filter to all workflow queues across the Navix platform. Service Type data already exists in our system via the Order API (Vendors[].Service.Type), so the primary work is surfacing it as a filterable attribute in the UI. This feature will save customers meaningful time every day and eliminate a category of filter-building complexity that shouldn't exist.

Queues in scope:

• Duplicates
• Unmatched Orders
• Unmatched Invoices
• Customer Billing queues
• Invoice Audit / Ready to Approve
• Disputes
• Analysis tabs (Approved, Terminated, All)

AUDIT HISTORY - ADD DETAILS (PART 2)

• The following event types have been added to Audit History in Navix
  • Stops (Remit To being added and updated, etc)
  • Invoice Status Changes (displaying when an invoice moved from Audit -> Ready to Approve, Ready to Approve -> Approved Status, etc)

TENANT ENVIRONMENT TYPE CHANGES

• We've introduced the "environment type" to tenants, so we can indicate which tenants are production, pre-production (onboarding tenant), post-production (no longer active for a tenant due to TMS change, etc.), sandbox, or internal.
• There are four places in the app where we display tenant names:
  • The top-left nav in the UI shows the tenant name and logo
  • The "Switch Tenant" dialog box shows a list of tenants
  • The top-left nav of the rules editor shows a tenant dropdown
  • The admin "Tenants" page
  • Tenant list in reports
• We've made the following changes:
  • We'll never include an environment descriptor in the name of a tenant -- that's what the environment type is for. For instance, if KCH has both a production and sandbox environment, the name of both will be "KCH Transportation". We'll use the environment type to change how we display that name in the UI -- but the name itself won't include the environment type.
  • In general, we won’t show the environment type for production environments, but will show it for all others. For instance, the name of both prod and sandbox KCH tenants would be "KCH Transportation". The production would display that way in the UI, but the sandbox (in certain places) would display as "KCH Transportation (Sandbox)".
  • In the admin "Tenants" page, add a column for "Environment Type".
  • In the top-left nav, we’ve removed the word "Tenant" that currently appears. For non-production environments, we’ve added a badge that displays the environment type.
  • In the "Switch Tenant" dialog, sort tenants by environment type and then name. The list is split into three groups with separators between them:
    • Production/pre-production/post-production
    • Sandbox
    • Internal

AUTOMATICALLY TAG TURVO SHIPMENTS WITH NAVIXDISPUTE ON DISPUTE CREATION AND NAVIXINVOICEAPPROVED ON INVOICE APPROVAL

• NavixDispute Tag:
  • When a dispute is created (manual or auto-dispute) for an invoice matched to a Turvo order, the system shall attach a NavixDispute tag to the corresponding Turvo shipment
  • Tagging shall apply to all Turvo tenants — no per-tenant opt-in required
  • If the invoice has not been matched to an order yet, the tag shall not be attached (no error)
  • If the Turvo API is unavailable, the system shall retry automatically (up to 5 attempts before dead-lettering)
  • Alerts shall fire if dispute tagging messages are failing or backing up
• NavixInvoiceApproved Tag:
  • When an invoice successfully completes the approval process and is matched to a Turvo order, the system shall attach a NavixInvoiceApproved tag to the corresponding Turvo shipment
  • The tag shall only be attached if the customer invoice step was successful (no NavixCustInvoiceFail)
  • If the tag fails to attach, invoice processing shall still complete successfully (non-blocking)

TURVO: INGEST ORDERS WITH CARRIER ORDERS THAT HAVE NO COSTS INSTEAD OF DROPPING THEM

• When a Turvo shipment is received with a carrier order that is active (deleted: false) but has no costs (costs: null), the system should ingest the order instead of rejecting it
• A default charge of $0.00 with charge code 1600 ("Freight - flat") should be applied to the carrier order so the order can proceed through the normal ingestion and audit workflow
• Orders that already have costs/charges should not be affected
• This applies to all tenants using the Turvo integration
• Business justification: Valid orders are currently being silently dropped during ingestion when a carrier has been assigned but costs haven't been entered yet. This causes operational delays since these orders must be manually identified via logs and re-created. Ingesting them with a $0 default charge allows the audit team to process them normally and adjust charges as needed.

EDIT INVOICE DOCUMENTS UI UPDATES

• A user can now navigate to an Invoice in Audit, click the Documents tab, click the "Pencil" icon to edit the following values:
  • Document type
  • Has Signature
  • Signature Date
• Previously a user had the ability to edit these values, however the UI made the screen stretch vertically, which made it more difficult for a user to easily see and edit each of these values quickly. The user experience has been improved by no longer requiring a user to scroll when editing the values above

TAI INVOICES SENT WITH INCORRECT INVOICE DATE

• When Navix creates an invoice in TAI, the invoice date is set to the current timestamp at the moment the system processes the message — not the date the invoice was actually approved in Navix. This means the invoice date in TAI can drift by hours or days from the real approval date, depending on processing delays, retries, or queue backlogs. This creates discrepancies between Navix and TAI records and can affect payment term calculations downstream.

Updates have been made to correct the following:

• Invoice date sent to TAI must be the date the invoice was approved in Navix
• When a multi-carrier Turvo shipment is blocked from completion, logs must identify the specific carrier that is pending approval

ENABLE PRE-BILLING PROCESSING FOR TURVO AND TAI TENANTS

• We've removed the opt-in gate from the Turvo and TAI integrations, so that now all configured tenants will automatically process pre-billing events (document uploads and order status updates) without requiring a per-tenant configuration override each time

IDP 2.0 - BILL OF LADING EXTRACTOR

• Bill of Lading documents now have identification and transcription activity taking place within our Azure Content Understanding Model
• This is yet another document type that has been completely removed from HS (Invoice is the only document type that remains!)

TENANT SPECIFIC CHARGE CODE MAPPING

• "Contains" matching logic has been added at the Tenant specific level (previously only offered this at the Global level for all tenants)
• Level of priority with logic is as follows:
  • Exact match (Charge codes and descriptions mapped to Navix Charge Types)
  • Global Contains Logic
  • Tenant Specific Contains Logic (overrides Global logic if a conflict exists)
• This enhancement allows for the ability to support our tenants in a customized manner. The Global level is more of a one-size fits all, however now with Tenant specific "Contains" logic being offered, we can tailor our solution for each individual tenant to be as efficient as possible
• Analysis will be run ~once per month for all tenants to evaluate any mapping updates that need made to improve the overall experience (cadence may fluctuate for newly onboarded tenants)

SUPPORT MULTI-CUSTOMER LOAD CHARGE AND ITEM VISIBILITY IN TURVO INTEGRATION

• Now when a Turvo shipment contains multiple customers, all customer charges and items are captured in the Navix order during ingestion
  • Previously only the first customer's financial and cargo data was reflected, leaving the remaining customers' data invisible in our app

REMOVE UNNECESSARY SUFFIX FROM TAI BILL NUMBERS FOR SINGLE-LEG SHIPMENTS

• When Navix sends a bill approval to TAI for a shipment with only one transit leg, the bill number should match the original invoice number exactly. The alphabetic suffix (e.g., -A, -B) should only be appended when a single invoice generates multiple bills across different transit legs
• With this update bill numbers sent to TAI will match the original invoice number when a shipment has a single transit leg, and bill numbers will remain unique when a single invoice produces multiple bills

🐞 Optimizations

READY TO APPROVE CHARGE GRID CORRECTIONS

• The export download of the grid now includes all new columns that are included on the grid view
• The search bar is functioning as expected when pulling up a specific order number, invoice number, etc
• Invoice records with open disputes were previously displaying in the Ready to Approve queue when they shouldn't have been. This has been corrected and now any records with open disputes are not showing in the Ready to Approve queue
• The issue causing the Created Date value to incorrectly default to 12/31/1969 has been fixed

FIX DUPLICATE DOCUMENT DELIVERY AND ENFORCE PROCESSING ORDER IN PRE-BILLING PIPELINE

• Resolved a defect in the pre-billing integration pipeline where approved documents were sent to TMS partners (Turvo, TAI, Revenova) twice — once when each document is individually approved and again when the entire order is approved. Additionally, we're now enforcing the correct processing order so that all document deliveries to the TMS complete before the order-level billing action (status update, invoice creation, or billing approval) is triggered, eliminating race conditions that cause missing documents on the TMS side.

INVOICE COUNT NOT REFRESHING AFTER BULK ACTION

• When a user would bulk assign numerous invoices to themselves or to another member of their team, the invoices were correctly being assigned, however the count was not updating as expected in the Audit/Ready To Approve/My Invoices tabs
• This issue has been corrected and the counts are updating as expected now

VIEW ENVIRONMENT TYPE WHEN ADDING USER

• When adding a new user, with the new environment(s), previously a user couldn't determine which one was the correct tenant to add. This has been updated to now enable the user to see which specific tenant environment they are selecting

📊 Reports

DUPLICATES DASHBOARD - USER REPORTING

• Enhancements have been made to the Duplicates Dashboard to now provide insight on user productivity metrics while working the Duplicates queue. Tenants can now easily see the following:
  • Manually Terminated Duplicates by User
  • Manually Kept Duplicates by User
  • Auto-Terminated Duplicates

REMOVE NAVIX INTERNAL ACCOUNTS FROM DAILY REPORT

• The following internal Navix tenants have been removed from the daily efficiency export that is shared
  • QA Account for Automated Testing
  • Turvo Integration Development

ORDERFUL SCAC AND PARTY IDENTIFICATION CODES REPORT

• A new report that contains the following information to be utilized by our BPO team members when managing Orderful/EDI relationships, so they can see which ones exist
  • Tenant
  • Carrier SCAC Code
  • Party Identification

EMAIL AGENT REPORT

• A new report that allows users to have visibility to the work completed by our Email Agent
• A user can see the following information for every email
  • Date/Time for when the email was received
  • Email Subject
  • Sender Email and Domain
  • Vendor/Factor involved
  • Category (Payment Status, Rate Verification, IDP or Other)
  • Did we reply or not?