Settlements Invoice Filtering Improvements
The matched and unmatched invoice list views now support new filters that customers have been requesting for more precise invoice management.
New Filters
Delivery date — filter invoices by delivery date (exact, before, after, or range) on both matched and unmatched (staging) invoices.
Origin/Destination address fields — filter by company name, location name, external reference, address line, city, state, country, and postal code for both origin and destination stops.
Service provider SCAC — filter invoices by carrier SCAC code.
Stop location name and external reference — filter across all stops on an invoice.
The Unmatched Invoices detail view is now also included in the freight configuration section, making it accessible directly from Financials.
Itinerary & Planning Window Automation
Building on the Distance & Drive Time feature introduced in 26.03, this release delivers the next phase: automatic planning window calculation based on travel time between stops. This was previewed in the 26.03 notes as a future capability.
Planning Window Cascade
When creating or editing a shipment, planning windows for subsequent stops are now automatically calculated based on:
Travel time between stops — uses the distance/drive time data from the configured distance provider to determine the earliest feasible arrival at the next stop.
Address book operating hours — if a stop’s address book entry has operating hours defined, the planning window automatically snaps to the next open day and time window for that location.
Hours of Service (HOS) rules — the cascade engine accounts for driver HOS limits, inserting required rest breaks and advancing the planning window accordingly.
As users add or reorder stops, planning windows cascade forward automatically. Manually-scheduled stops are respected as fixed anchors, and downstream stops recalculate from there.
Additional Stop & Scheduling Improvements
Improved distance/drive time tooltip details between stops.
Planning window time now correctly populates minutes from address book entries (previously only hours were parsed).
Planning window timezone is now set per-stop rather than globally.
Dock scheduling Gantt calendar now correctly renders overlapping appointments on the correct dock.
Calendar time zone handling corrected so appointments display in the expected time zone.
v3 Orders List Page Updates
Several improvements to the v3 Orders list page to give users more control and visibility:
Separate date columns — Pickup Range and Delivery Range are now split into four individual columns: Pickup Date Start, Pickup Date End, Delivery Date Start, and Delivery Date End. All four are sortable and can be added, removed, or rearranged via the column configurator.
Order consolidation strategy — A new consolidation strategy selector is available when adding orders to a shipment, supporting Separate, Latest, and Earliest strategies. This is also configurable as a company-level default in company profile settings.
Line item fixes — Freight class now auto-updates correctly after deleting a line item, and Product Category populates properly when loading from Products.
Credit Limit - Accrued Balance
The system allows you to calculate the accrued value of shipments for customer to include this amount in the credit limit calculation. The formula for calculating the credit limit is Accrued Balance + Outstanding Balance (typically downloaded from an ERP) + cost to be applied to a shipment < Credit Limit.
In order to calculate the Accrued Balance, go to the Manage, Company screen and set all the shipment statuses that should be included in the amount. Typically these statuses would include any shipments where rates have been applied but they have not been delivered. The user can choose any shipment statuses to be included in the Accrued Balance.
After setting the Accrued statuses, you can go to the Manage, Customer screen and view the current accrued amount for the customer.
Based on the Customer Credit currency, only shipments in the selected currency will be included in the Accrual Amount calculation.
When applying rates to a shipment via the tender, bid acceptance, or instant rates processes, the system will check to see if the Accrual Amount + Outstanding Balance + Shipment Cost will put the customer over their credit limit. If so, a warning message will appear showing the information. If the user has been set up with permission to override the warning, an Approve button will appear on the screen. If the user does not have this permission, the system will stop them from assigning a carrier with costs to the shipment.
T&T Worker Enhancements
Summary
This sprint delivers improvements to carrier tracking communications, making it easier for carriers to provide accurate information and giving operations teams visibility into carrier engagement, even when carriers choose to update shipments manually.
What's New - Confirmation Messages for Carrier Tracking Responses
When carriers respond to missing tracking requests, they now receive immediate confirmation that their response was received and processed.
Successful updates: Carriers see exactly what was processed, which stops were updated, new statuses, departure times, and locations
Incomplete responses: If the response doesn't contain enough detail, carriers automatically receive helpful guidance showing exactly what information is still needed, with a pre-filled example using their shipment's actual route and dates
No guessing: Carriers know instantly whether their response worked or what else is needed
Benefit: Reduces confusion and back-and-forth by giving carriers instant feedback on their responses.
Improvements - Smart, Shipment-Specific Tracking Request Guidance
Tracking request emails and SMS messages now provide personalized examples based on each shipment's actual route, stops, and timing. Instead of generic instructions, carriers see pre-filled examples using their shipment's real pickup location, scheduled dates, and next destination.
For example, a carrier hauling from Aurora to Chicago scheduled for pickup on 2/4 will see: "Picked up in Aurora on 2/4 at 3:00 PM."
The system also shows the route, next scheduled stop, and how long it's been since the last tracking update, giving carriers all the context they need to provide accurate information.
Benefit: Carriers can respond more quickly and accurately because they see exactly what information is needed in the format required, no guessing about dates, locations, or what to include.
Improved Activity Logging for Carrier Engagement
When carriers click the "Enter Tracking Update" button in exception emails and manually update shipment information, this engagement is now properly logged in the activity history.
What gets logged:
Response marked as "Received" immediately when the link is clicked
Hover tooltip shows "Shipment Link Clicked" for context
System monitors and automatically verifies the shipment was updated and marks the activity as resolved with "Shipment updated manually"
Full audit trail of carrier engagement even for manual updates
Previously: Link clicks weren't logged, making it look like carriers never responded even when they manually updated shipments.
Now: Operations teams see the complete story which outreach led to carrier action, how long it took, and whether carriers updated through the link.
Benefit: Full visibility into carrier responsiveness and tracking request effectiveness. Teams can accurately measure which carriers engage with requests and how outreach efforts drive manual updates.
API Changes
Added charge_code Field to Freight Invoices
We added support for an optional charge_code field on charge line items in freight invoice creation.
What’s new
charge_codecan now be included incharge_line_itemswhen creating a freight invoice.The field is returned in the response upon successful invoice creation.
Affected endpoints
POST /invoicing/shipments/{shipmentId}/freight-invoices/
Impact
Backward compatible. The field is optional and existing integrations will continue to work without modification.
Added Shipment delivery_date Support
We added support for an optional delivery_date field across multiple shipment-related APIs.
What’s new
delivery_datecan now be included when creating or updating shipments.The field is now returned in responses across multiple shipment-related endpoints.
Affected endpoints include
POST /shipments/PUT /shipments/{shipmentId}/GET /shipments/GET /shipments/{shipmentId}/PUT /shipments/{shipmentId}/add-orders/PUT /shipments/pickups/{shipmentPickupId}/Spot negotiation shipment endpoints
Shipment pickup endpoints
Carrier power unit shipment endpoints
Purchase order shipment build/update endpoints
Impact
Backward compatible. The field is optional and existing integrations will continue to work without modification.
Added order_mappings Support for Shipments
We introduced a new optional order_mappings property for shipment-related APIs to support mapping orders within shipment payloads.
What’s new
order_mappingscan now be passed in requests when creating or updating shipments.The property is also available in responses for shipment-related endpoints.
Affected endpoints include
POST /shipments/PUT /shipments/{shipmentId}/PUT /shipments/{shipmentId}/add-orders/Shipment quoting and negotiation endpoints
Purchase order shipment build/update endpoints
Shipment retrieval endpoints
Impact
Backward compatible. The property is optional and will not affect existing integrations.
Added consolidation_strategy to Add Orders Endpoint
A new optional request parameter was added to support order consolidation behavior.
Endpoint
PUT /shipments/{shipmentId}/add-orders/
New parameter
consolidation_strategy(optional)
Impact
Backward compatible.
Description |
ODFL Dispatch - sending cube instead of ODFL valid values. |
Central Transport (Direct Connection) tracking updates not working |
Expand fuel surcharge percent to 5 decimal places |
[Genesis] - Bill to Bug |
XPO tracking error |
Update Compass to handle Shipments with IoT attachments |
Breakthrough Fuel - Integration MarketPlace Card & Authentication |
New Charge Codes |
MacroPoint tracking is getting stopped while Shipments are in transit |
Pick up times getting assigned to non-pick up stops |
FCL Map Tracking Failure |
Open Track didn't update Discharge and LFD info |
Script-Add Consolidation Cooler to existing integration-cooler code is FLCO |
Orders uploaded via SFTP is showing incorrect pickup date in TMS |
Tive - Stop times updating incorrectly |
Carriers and Suppliers Receiving Duplicate Tender, BOLs and RPOs |
Shipments created without any validation |
Error when converting v2 orders to shipments |
Permissions failure preventing dock scheduling |
FCL/Ocean container tracking shows no history when shipment is created after container's last milestone |
Updated Activity Log Worker Filtering |
Investigate order optimization error when order pickup windows are blank |
Check on Activity Log rows where Outreach/Response Failed but Exception shows Resolved |
V3 Optimizer Fail in Sandbox |
Enable Order Groups consolidation for shipment creation through shipment assembly |
Order to Shipment Conversion Failure |
Enable Teams Swifty App for Sandbox |
Hotfix: Build doc classifier dataset, retrain, and deploy retrained doc classifier |
Invoice creation silently failing for large shipment volumes — document uploads were not generating FreightInvoice records in certain cases. |
Carrier invoice creation — Remit-to field not populating with the carrier’s information. |
TriumphPay section shows blank when carrier has a TriumphPay ID. |
Unable to add order to shipment due to consolidation failure. |
Consolidation failure when adding orders to an existing shipment. |
Consolidation failure when stop address has no timezone. |
Order number, purchase order, and line item ID missing on shipment line items for v3 orders. |
Custom fields on purchase order line items not copying to shipment line items. |
Shipment dashboard now refreshes automatically after bulk actions are executed. |
Custom selection field inline edit on shipment dashboard saving incorrect value and displaying as lowercase. |
Dock scheduling Gantt calendar displaying overlapping appointments on the wrong dock. |
Time zone incorrect on dock scheduling calendar. |
Appointment type transitions causing infinite loop between scheduling services. |
FullCalendar license key expired, causing calendar rendering issues. |
Date columns on the v3 Orders dashboard are now sortable. |
Settlement service database connection pool exhaustion under high load. |