Freight Bill Version fields overview

Depending on the method by which you are creating Freight Bills, the decision as to which fields will be used and which will not depend on how you initiated the Freight Bill creation process.

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

• Default: Established as a default when creating a freight bill using the version.
• Filter: Field is used as a filter criterion when considering vouchers during Auto Pay batch process.
• Control: Controls validation or other behavior.

Field	Freight Bill Sources
	Auto Pay Run Request	Create Freight Bill (UI or API)
Carriers	Filter	Default *
Exclude Carriers	Filter
Customers	Filter	Default **
Exclude Customers	Filter
Start Adjustment Days	Filter
Cut-Off Adjustment Days	Filter
Division ID	Filter	Default
Logistics Group ID	Filter	Default
Print Requested	Default
Immediate Reconciliation		Control
Freight Bill Type	Default	Default
Carrier Freight Terms		Default (for NOFs only) ****
Invoice Adjustment Days	Control
Hold Freight Bill Upon Creation	Control	Control
Freight Bill Confirmation Mode	Control	Control
Maximum One Detail per Freight Bill	Control	Control
Include Initial Vouchers***	Filter
Include Post Charge Vouchers***	Filter
Include Miscellaneous Vouchers***	Filter
Ignore Customer IDs for Operational Vouchers	Control
Voucher Level	Filter
Voucher Type	Filter
Fixed Charge Handling*****	Filter
Separate Freight Bill Per Trip/Booking	Control
All Vouchers for Trip/Booking Must be Eligible	Control

* 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.

***** Fixed Charge Handling indicates whether A/P Vouchers with Voucher Reference Number Type as Fixed Charge should be included, excluded or to only consider the fixed charge vouchers during Autopay batch process.

***** If Fixed Charge Handling is set to Only Fixed Charges, the following fields will not be considered: Freight Bill Confirmation Mode, Separate Freight Bill Per Trip/Booking, Immediate Reconciliation, Include Miscellaneous Vouchers, Include Post Charge Vouchers, All Vouchers for Trip/Booking Must Be Eligible.

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