Freight Bill Version fields overview

Depending on the method by which you are creating Freight Bills, the fields in the Freight Bill version might or might not be used. The decision as to which fields will be used and which will not depends on how you initiated the Freight Bill creation process.

The following information is displayed for fields in the following table:

* This column will be used as a default only if there is exactly one Carrier ID specified and the Exclude Carriers check box is not checked.

** This column will be used as a default only if there is exactly one Customer ID specified and the Exclude Customers check box is not checked.

*** If an Auto Pay request is triggered using a Freight Bill Version where the three "Include" flags for Voucher Category are all False, no Vouchers will be identified as being eligible.

**** The Carrier Freight Terms will be used to establish defaults for Audit-no-Match NOFs attached to a Freight Bill Detail. It will also be used to establish a default when creating an Audit-Match Non-Operational Freight Transaction even though these transactions are initially not associated with a Freight Bill.

The User Profile allows two separate Freight Bill Versions to be defined for each user. The Freight Bill Version that will be used to control the freight bill creation process will vary based on the source of the request:

Freight Bill (or NOF) Creation Source

Freight Bill Version (from User Profile)

Auto Pay Run Request

Ad Hoc Freight Bill Version

Create Freight Bill (UI or API)

Individual Freight Bill Version

Create Non-Operational Freight (Audit-Match)

Individual Freight Bill Version

 

See Also

Immediate reconciliation

List of Freight Bill Versions (Employee)

Ignore customer IDs for operational vouchers