


The carrier audit profile in the custom records contains values that control
the behavior of the financial audit process. These records have the following
layout:
Carrier Audit Profile
| Seq
| DB Field
| Field Name
| Purpose
|
| 0
| RCRD_KEY
| SCAC
| The Vend_Labl for the vendor that this record controls. Note that a special
vend_Labl “<Default>“ is reserved as a record which supplies default values when no vendor specific
record exists or the vendor specific record contains a Null in the field being
retrieved. This field must have a value.
|
| 1
| %DTM001
| Cutover DTM
| The date on which invoice processing was cutover to the Trax FPS system.
Freight bills with a shipment date prior to the cutover will generate a “Shipment_Prior_To_Cutover” freight bill level FA_CODE. This is usually used to prevent automatic
approval for freight bills date ranges for which the system has no duplicate history.
Note: If no shipment date was supplied by the vendor, the ATA (actual date of arrival) is used. If the ATA was not provided, the invoice date is used. A Null value causes the system to get the value from the <default> record. If one does not exist, then a value of 1/1/0001 is defaulted. |
| 2
| %CUR001
| FB Rated High Tol
| If the system rates the total of all freight bill charges for more than the
billed amount, how great should the difference be before investigating the cause
of the difference and applying the financial audit policies found as a result
of the investigation. This value has no effect unless Sys Rated contains a
value of “Yes”.
For example, if this field is set at $5.00 and the vendor's freight bill totals $57.92 and the system rates the charges on the freight bill at $62.91, the difference would be less than the high tolerance. No investigation into the freight, accessorial, or tax charges would be performed and the billed amount would be approved for payment. However, if the field had a value of $2.50, the difference would be greater than the tolerance and all of the diagnostic performed in the FA_Issues_FB_Chrg class would be performed. The issues discovered by this class and their associated policies would govern what was paid and whether an exception for human review would be generated. Null value causes the system to get the value from the <default> record. If one does not exist, then a value of $0.00 is defaulted. |
| 3
| %CUR002
| FB Rated Low Tol
| If the system rates the total of all freight bill charges for less than the
billed amount, how great should the difference be before investigating the cause
of the difference and applying the financial audit policies found as a result
of the investigation. This value has no effect unless Sys Rated contains a value
of “Yes”.
For example, if this field is set at $2.00 and the vendor's freight bill totals $125.95 and the system rates the charges on the freight bill at $124.45, the difference would be less than the low tolerance. No investigation into the freight, accessorial, or tax charges would be performed and the billed amount would be approved for payment. However, if the field had a value of $1.00, the difference would be greater than the tolerance and all of the diagnostic performed in the FA_Issues_FB_Chrg class would be performed. The issues discovered by this class and their associated policies would govern what was paid and whether an exception for human review would be generated. A Null value causes the system to get the value from the <default> record. If one does not exist, then a value of $0.00 is defaulted. |
| 4
| %CUR003
| High $ Limit
| This field controls the amount for this vendor which the system can approve
for payment without generating a freight bill level issue and implementing the
associated policies. This is normally used to prevent the system from
automatically approving payment of a freight bill which has a dollar amount that is
unusually high without human review.
A Null value causes the system to get the value from the <default> record. If one does not exist, then a value of $99,999.00 is defaulted. |
| 5
| %CUR005
| Audit Min $ Limit
| The audit minimum limit is the amount that the total charges on a freight bill
must exceed before it is worth performing any investigation or applying any
policy other than paying the billed amount.
A Null value causes the system to get the value from the <default> record. If one does not exist, then a value of $0.00 is defaulted. |
| 6
| %T001
| All Bills FA Exc.
| Can have a value of “Yes”, “No”, or Null. “Yes“ causes all freight bills for this vendor to be financial exceptions even when
no other issues with the freight bill exist. This is helpful when testing a
new set of financial audit rules or when no rates exist and you want to review
the bills manually.
A value of “No” or any value other than “Yes” or Null turns this off. A Null value causes the system to get the value from the <default> record. If one does not exist, then a value of “No” is defaulted. |
| 7
| %T002
| Sys Rated
| Can have a value of “Yes”, “No”, or Null. A value of “Yes” informs the financial audit process to expect a rated amount and to consider
the inability to rate all charges as a problem.
A value of “No” (and any value other than “Yes” or Null) causes the financial audit process to ignore the difference produced simply because the rated amounts do not exist. A Null value causes the system to get the value from the <default> record. If one does not exist, then a value of “No” is defaulted. |
| 8
| %T005
| Pay Billed Amt
| Can have a value of “Yes”, “No”, or Null. When this field has a value of “Yes”, the system will not look for any customer specific, accessorial charge,
freight charge, tax charge, BOL charge, or BOL weight issues. The system will
still check for vendor specific and freight bill level issues such as “Shipment_Prior_To_Cutover”.
A value of “No” (and any value other than “Yes” or Null) does not override the normal behavior of the financial audit process. A Null value causes the system to get the value from the <default> record. If one does not exist, then a value of “No” is defaulted. |
| 9
| %T004
| Compare BOL Rate
| Can have a value of “Yes”, “No”, or Null. A “Yes” will cause the system to look for and expect a value in the rules engine
variable “BOL_Rated_Amt” which contains the sum of the matched BOLs rated amounts. The BOL rated
amount will be compared against the rated freight bill amount and the billed
freight bill amount.
A value of “No” (and any value other then “Yes” or Null) will turn off the BOL rate diagnostic and the system will not expect “BOL_Rated_Amt” to exist. A Null value causes the system to get the value from the <default> record. If one does not exist, then a value of “No” is defaulted. |
| 10
| %T006
| Compare BOL Wt
| Can have a value of “Yes”, “No”, or Null. A “Yes” will cause the system to look for and expect a value in the rules engine
variable “BOL_Tot_Wt” which contains the sum of the matched BOLs weights. The total BOL weight
will be compared against the actual weight presented on freight bill by the vendor.
A value of “No” (and any value other then “Yes” or Null) will turn off the BOL weight diagnostic and the system will not expect “BOL_Tot_Wt” to exist. A Null value causes the system to get the value from the <default> record. If one does not exist, then a value of “No” is defaulted. |
| 11
| %CUR004
| BOL Rate Diff $ Tol
| This field sets the amount of difference which must be exceeded positively or
negatively before the financial audit process will consider a problem to exist.
This field's value is not used unless Compare BOL Rate contains a value of “Yes”.
A Null value causes the system to get the value from the <default> record. If one does not exist, then a value of $0.00 is defaulted. |
| 12
| %DBL001
| BOL WT Diff % Tol
| This field sets the percentage difference which must be exceeded positively or
negatively before the financial audit process will consider a BOL weight
problem to exist. The value is any valid number expressed as a percentage (e.g.
1=1%, 20=20%) This field's value is not used unless the Compare BOL Wt contains a
value of “Yes”.
A Null value causes the system to get the value from the <default> record. If one does not exist, then a value of 1 is defaulted. |
| 13
| %T008
| Pay Billed on Interline
| Can have a value of “Yes”, “No”, or Null. A “Yes” will prevent the system from performing freight charge or BOL charge
comparisons.
With a value of “No” (and any value other then “Yes” or Null), the system will compare the rated charges and the BOL rate with the invoiced charges on interline shipments. A Null value causes the system to get the value from the <default> record. If one does not exist, then a value of “No” is defaulted. |
| 14
| %CUR006
| Freight Tol
| When the total charges are out of tolerance, how much difference must exist
between the net freight rated amount and the net freight billed amount before
freight charge issues should be reported. This is helpful in preventing
meaningless messages on the exception screen or $0.01 adjustments being made on freight
when the real problem is on an accessorial charge.
Because different vendors use different rounding techniques during the calculation of their rates, it is not uncommon to have a several cents difference between the rated charge and the billed charge. By setting this value at something like $0.50, you prevent the system from reporting or making extraneous adjustments. This field's value is not used unless Sys Rated is “Yes” and the FB Rated High Tol or FB Rated Low Tol is exceeded. A Null value causes the system to get the value from the <default> record. If one does not exist, then a value of $0.00 is defaulted. |
| 15
| %CUR007
| Accessorial Tol
| When the total charges are out of tolerance, how much difference must exist
between the total of all accessorial rated amounts and the total billed
accessorial amounts before any accessorial charge issue policies other than Pay_Billed
should be executed. This is helpful in preventing meaningless $0.01 adjustments
being made on accessorial when the real problem is in the freight charges.
Because different vendors use different rounding techniques during the calculation of their rates, it is not uncommon to have a one or two cents difference between an accessorial rated charge and the billed charge. By setting this value at something like $0.10, you prevent the system from reporting or making extraneous adjustments. This field's value is not used unless Sys Rated is “Yes” and the FB Rated High Tol or FB Rated Low Tol is exceeded. A Null value causes the system to get the value from the <default> record. If one does not exist than a value of $0.00 is defaulted. |
Overview of the Financial Audit Process
Financial Issue Categories
Financial Action Policies
Financial Policy Application
Financial Policy Hierarchy
Policy Locations
Overriding the Universal Policy of Each Issue
FA_Policy Table Structure
Financial Audit Issue Variables
Carrier Audit Profile
Financial Audit Policy Classes
Execution Order of Classes
Universal FA_CODEs