This page presents all hold conditions that currently exist for the selected voucher.
When an A/P or A/R Voucher is Held based on system activity (as opposed to being manually placed On Hold), an entry will be recorded in the Voucher Held Log table. Each entry in this table must be resolved before the voucher will be removed from its Held state. Once the condition causing a Held condition is resolved, the entry in the Voucher Held Log table will be eliminated. If after an entry has been eliminated there are no additional entries exist in the Voucher Held Log for the Voucher, the System Held state will be removed.
If a Voucher is System Held or Manually Held, the Voucher is not eligible for the Auto-Pay (A/P) or Invoicing (A/R) process. Also, if the voucher has been matched, the corresponding Freight Bill (A/P) or Invoice (A/R) will also be System Held. A Freight Bill (Invoice) will only be eligible to be transferred to A/P (A/R) once all System Held and Manual Held conditions have been eliminated.
A/P Vouchers can be placed on hold by the system for any of the following reasons:
POD Not Received - Status Verification for the Carrier is "POD Required" and POD has not been reported for at least one Shipment Leg or Shipment Leg Container associated with the voucher.
Delivery Notification Not Received - Status Verification for the Carrier is "POD or Delivery Notification Required" and Delivery or POD has not been reported for at least one Shipment Leg or Shipment Leg Container associated with the voucher.
Confirmation Required - The Freight Bill Confirmation Mode for the Freight Bill Version used to create a Freight Bill is "Confirmation Always Required" and the Confirm operation has not been performed for the matched Freight Bill Detail.
Held Pending Approval - Approval Chain functionality has been enabled for Voucher Adjustments globally and the Approval Document generated for at least one of the Adjustments for the Voucher has not yet been Approved or Rejected.
Duplicate Reference Numbers - Applicable only for A/P Vouchers corresponding to Non-Operational Freight transactions using Audit Mode of "Audit No Match". This System Held condition will apply when at least one other NOF exists for the same Customer with the same Matching Reference Number.
A/R Vouchers can be placed on hold by the system for any of the following reasons:
POD Not Received - Status Verification for the Customer is "POD Required" and POD has not been reported on the carrier side for at least one Shipment Leg or Shipment Leg Container associated with the final leg of the shipment's itinerary.
Delivery Notification Not Received - Status Verification for the Carrier is "POD or Delivery Notification Required" and Delivery or POD has not been reported on the carrier side for at least one Shipment Leg or Shipment Leg Container associated with the final leg of the shipment's itinerary.
Carrier Not Paid - The Carrier Payment Required flag is True for the Customer for a Non-Operational Freight transaction and the corresponding Freight Bill Detail is not in "Approved" status, or Freight Bill Payment Status for the corresponding Freight Bill is not "Paid".
Responsible Customer Undefined - When a load or stop level A/P Voucher Adjustment is replicated to an A/R Voucher, the A/R Voucher will be placed on System Hold to force a manual review if Responsible Customer functionality has been enabled for "Other Customer" but a Responsible Customer ID has not been defined at either the Tariff Charge or Shipment/Master Charge level.
No Customer Shipping Location - When a load or stop level A/P Voucher Adjustment is replicated to an A/R Voucher, the A/R Voucher will be placed on System Hold to force a manual review if Responsible Customer functionality has been enabled for "Shipping Location", "Origin Shipping Location" or "Destination Shipping Location" but an equivalent Customer ID has not been established for the Shipping Location entity in the Customer / Shipping Location Cross-Reference table (that is, row does not exist with a Relationship Type of Same Entity). The declaration that the charges are to be payable by the entity associated with either of the locations for a Shipment could have be made at Tariff Charge or Shipment/Master Charge level.
Note: For the last two cases, the new A/R Charge Detail will be assigned to an A/R Voucher associated with the Shipment's Customer, even though this may not be the Customer to whom the charge should actually be applied. Resolution may involve reversing the A/R Charge Detail on the Voucher assigned to the Shipment's Customer and then creating a Miscellaneous A/R Voucher associated with another Customer and then adding a Charge Detail to that voucher for the same amount.