Allows you to set up a fuel surcharge pay rate that is based on an Average Fuel Price table. An Average Fuel Price table consists of a list of effective dates and the corresponding average fuel prices in effect for those dates. These tables are set up in File Maintenance.

Allows you to base pay on the combined number of axles recorded for the assigned resources (tractor, trailer 1, and trailer 2). For details, see Setting up rates based on axle count.

Customer being billed; this selection corresponds to the company ID in the Bill To field on the order.

Classifications recorded in the Other Type 1 and Other Type 2 fields in the profile of the Bill To company recorded on the order.

Note: Your company defines the names and options for these fields in the OtherType1 and OtherType2 labels in the System Administration application.

Commodity transported on the order.

Note: If there are multiple commodities on the order, the system only looks at the first one.

Classification code of the commodity transported on the order.

Note: If there are multiple commodities on the order, the system only looks at the first one.

Freight count of an order.

Define pay rate tables based on the Arrival date for the first stop.

1.  

Define pay rate tables based on the Earliest date for the first billable stop

Note: For details, see Creating pay rates based on day of week or time of day.

This option is designed for split trips. The rate will pull if the order’s last billable stop is on any trip segment that is part of the move associated with the segment being settled.

Note: The rate will be applied even if the resource being paid was assigned to a segment that did not include the order’s last billable stop.

Note regarding the following Destination options: On a pay rate table, these options relate to the final delivery location on the segment. If the trip segment does not have any billable stops, the destination is the stop at the end of the empty move.

City where the last stop took place.

ID of the company where the last stop took place.

State/province where the last stop took place.

First three characters of the ZIP/postal code of the location where the last stop took place.

When you select this option, the rating engine will apply the rate only when the ZIP Code used to define the rate is an exact match to the ZIP Code recorded in the profile of the company where the last stop occurred. If the company's ZIP code has:

Allows you to set up rates for mile ranges based on the tractor’s odometer readings.

 

Allows you to set up rates based on round trip miles.

Custom

This option works in conjunction with the Loaded field on the rate’s index to set up rate tables based on just loaded miles or just empty miles.

For example, suppose a trip has 10 empty miles and 100 loaded miles. If you define the table using:

For details, see Calculating pay based on loaded or empty mileage ranges.

This option allows you to set up a table for mileage ranges based billable miles. The system determines the rate by looking at the quantity of billing miles, and then applies that rate to the number of Settlement miles. It is intended to be used when the mileage quantity used for billing is not the same as the mileage that Settlements uses.

During the rating process, the rating engine does the following:

1. Looks at the total number of billed miles on the order.

2. Determines where that quantity falls in the mileage-based table to find the rate associated with that quantity.

3. Multiples the rate times the Settlement miles to create a pay detail.

Origin to destination miles.

Note: When this option is used, miles between interim stops are not considered.

Custom

Custom

Total miles (loaded and empty) on a trip for which the driver is being paid.

Custom

The company with which the driver is associated in his/her profile.

 

The division to which the driver belongs, as identified in his/her profile.

 

The home location for the driver, as identified in his/her profile.

 

The fleet to which the driver is assigned in his/her profile.

 

Allows you to set up a rate for a specific driver or co-driver.

The driver’s team leader, as identified in his/her profile.

 

Terminal to which the driver is assigned in the driver profile.

 

Driver classifications to which the driver is assigned in the driver profile.

 

Used to define secondary pay rate tables that will calculate pay based on the number of drop stops recorded on a trip. You can specify whether pay is created for all stops, or only for stops that are more than a user-defined number.

Note: This option (along with the Pickup Stops option) allows you to create separate pay rates for pickup stops and for drop stops. In addition, you can use the existing incremental rating feature to specify a different number of free stops for each rate. For details, see Setting up separate stop pay rates for pickups and drops.

Allows you to create a rate schedule that is based on events assigned to stops that occurred during a trip. It is applicable when:

For details, see Basing pay rates on event types.

Allows you to set up a rate schedule that is based on events assigned to stops that occurred during a trip. It is applicable when:

For details, see Basing pay rates on event types.

Supported only for billing rates.

Supported only for billing rates.

Supported only for billing rates.

Custom.

This option is designed for split trips. The rate will pull if the order’s first billable stop is on any trip segment that is part of the move associated with the segment being settled. For details, see Restricting pay based on origin/destination.

Note: The rate will be applied even if the resource being paid was assigned to a segment that did not include the order’s first billable stop.

Note regarding the following Origin options: On a pay rate table, these options relate to the initial pickup location on a trip segment. If the trip segment does not have any billable stops, the origin is the stop at the start of the empty move.

City where the first stop took place.

ID of the company where the first stop took place.

State/province where the first stop took place.

First three characters of the ZIP/postal code of the location where the first stop took place.

When you select this option, the rating engine will apply the rate only when the ZIP Code used to define the rate is an exact match to the ZIP Code recorded in the profile of the company where the first stop occurred. If the company's ZIP code has:

Note: When setting up full ZIP Code rate tables for nine-digits ZIP codes, the format used in the rate table must match the format used in the company's profile. For example, if the nine-digit ZIP Code is hyphenated in the company's profile, it must also be hyphenated in the rate table, e.g., 44060-1234 is not the same as 440601234 or 44060 234.

Classifications recorded in the Other Type 1 and Other Type 2 fields in the profile of the Order By company recorded on the order.

Note: The names and options for these fields are defined in the OtherType1 and OtherType2 labels in the System Administration application.

Supported only for billing rates.

Allows you to set up secondary pay rates that will calculate add-on pay based on the number of miles traveled through specified states or provinces. When the rate is applied to a trip, the system creates a separate pay detail for the miles traveled in each state on the trip.

 

Used to define secondary pay rate tables that will calculate pay based on the number of pickup stops recorded on a trip. You can specify whether pay is created for all stops, or only for stops that are more than a user-defined number.

Note: This option (along with the Drop Stops option) allows you to create separate pay rates for pickup stops and for drop stops. In addition, you can use the existing incremental rating feature to specify a different number of free stops for each rate. For details, see Setting up separate stop pay rates for pickups and drops.

Revenue classification on the order header for the order for which the driver is being paid. If multiple orders exist on the trip, the system looks only at the first one.

 

Number of months a driver has been employed. To determine the driver’s seniority level, the system checks the entry in the Seniority Date field in the driver's profile in File Maintenance. If a Seniority Date is not specified, the system uses the entry in the Hire Date field. For details, see Setting up a line haul rate that is based on driver seniority.

Custom

These options are used in conjunction with the options selected in the existing Event field to set up secondary rates that will be applied only when the specified event occurs at the specified stop.

1. The Stop Other Type 1-2 options:

2. For details, see Calculating pay for events that occur at specific stops.

Applicable for secondary stop pay rates. Pay is based on the number of loaded stops on an order.

Allows you to create flat pay based on when a trip starts. You can use it to set up a matrix of flat pay amounts to accommodate different rates for shift pay. For details, see Creating flat pay rates based on when a trip starts.

The company that owns the tractor, as identified in the tractor's profile. This field is most commonly used for multi-company organizations.

 

The division to which the tractor belongs, as identified in the tractor's profile.

 

The fleet to which the tractor belongs, as identified in the tractor's profile.

 

Terminal to which the tractor is assigned in the tractor profile.

 

Tractor classifications to which the tractor is assigned.

 

The company to which the trailer is associated, as identified in the trailer's profile. Most commonly used for multi-company organizations.

 

The division with which the trailer is associated, as identified in the trailer's profile.

 

The fleet to which the trailer belongs, as identified in the trailer's profile.

 

Terminal to which the trailer is assigned in the trailer profile.

 

Trailer classifications to which the primary trailer is assigned.

 

Allows you to set up a rate table that is based on the LghType1 classification assigned to the trip segment.

1. This option can be used with consolidated orders and split trips.

2. When orders on separate trip segments are consolidated onto one trip segment, the system resets the LghType1-4 values to the values associated with the order that is listed first in the stop sequence.

3. Use of this option is not supported for cross docked orders.

4. LghType1 classifications are assigned in the Assign Driver/ Equipment window in Order Entry, or the Asset Assignment window in Dispatch.

5.  

Freight volume of an order for which the resource is being paid.

Freight weight of an order for which the resource is being paid.

Supported only for billing rates.