TruckMate 2024.4 New Features: Back Office

The logic for reason codes has been improved for Customer Service, Dispatch, and Multi Mode Dispatch. The default reason code that appears is now the last code that was entered for the freight bill or trip.

The field stays blank if there was no previous reason code.

When you copy and past trace numbers, blank spaces and unprintable characters are now automatically removed from the Trace Number field, Reference Qualifier field, and user fields before they are saved to the trace record.

For client rating, the range-based account Charge Code allows you to set value ranges. It can also define specific ranges for clients, start and end zones, or even service levels. Because of this, a single code may have thousands of rules.

The logic for calculating range-based account charges has been optimized to filter irrelevant rules based on the freight bill’s information. It now only retrieves the applicable rules for calculation. This significantly improves system performance and saves substantial database resources.

Three main fields in the Accessorial Charges tab of Codes Maintenance will have performance improvements for client rating (freight bill charges):

Some of the validations used for checking accessorials that are added to carrier trips have been centralized.

Updated the Trips API to use the newly centralized validations when adding accessorials to a carrier trip.

Added the ability to prorate the carrier cost using Length. It is now available as an option in the Cost Rule dropdown list.

Four new fields have been added to the EDIlink format in the 204 inbound map:

These fields, if populated with a value that is a valid TruckMate zone code, will override the existing methodology.

Changes have been made to avoid situations where a consolidated master bill ends up having a delivery window that is earlier than the pick up window:

The option Completion is mandatory before Freight Bill can be assigned or added to a Trip has been added to the Checklist Item Wizard.

For more information about this option, see Added support for mandatory checklist items (TM-178380).

You can now exclude carriers based on the bill-to party of a freight bill.

Excluded carriers do not show up as an option when selecting vendors. The carrier becomes invalid if entered manually.

Added a security setting that controls whether the Carrier Exclusions tab is available in Customer & Vendor Profiles.

An option has been added to the Pickup/Delivery Appt security option called Audit Edits (Override Audit Code).

If this option is selected, a confirmation message opens when a user tries to:

The user then must provide a reason for the change and enter an Audit Status Code and a Reason Code. The reason code defaults to the last used reason code.

The GL Journal Entries format now includes a Year End Entry field. This field is optional. The valid values for the field are True and False.

If the Year End Entry field is added, then it is expected that all records in the import file have that field.

Fields have been added to Payroll Configuration and Payroll Returns Generator to support CPP2 and QPP2 values for T4 and RL-1 forms.

When you run the T4 wizard, you must now put the combined maximum earnings of both CPP and CPP2 in the Maximum amount of pensionable earnings field:

This is the amount you used to calculate your employee’s CPP/QPP and CPP2/QPP2 that you reported using box 16, box 16A, box 17, and box 17A, up to the additional maximum pensionable earnings for the year, even if you did not withold CPP/QPP or CPP2/QPP2 contributions on all or any of those earnings. In many cases, boxes 14 and 26 will be the same amount.

You can now load rating items into staging tables rather than directly into production tables. This lets you upload many rating records at once.

To minimize the effect of record locking and table locking on users, staging tables and stored procedures have been added. This moves the rating information from the staging tables to the production tables in more consumable pieces. The new tables provide staging for multi-point, multi-break, detention, and storage rate sheets.

There is no UI for this process. This process is done at the database level, such as through ODBC or JDBC types of drivers.

Here is an overview of the process:

Additional processes include:

List of tables:

List of procedures: