TriumphPay Audit

Automate carrier bill approval and document management with AI and OCR technology.

Workflow

1. Tai provides shipment information to TriumphPay Audit; this occurs when the shipment hits the Dispatched status. 
2. Updates go over to TriumphPay Audit anytime an update is made on the load.
3. Three requests are sent out. (these are to update TriumphPay Audits side)
   1. 1. Load - This provides detailed information regarding the shipment (Stops, Commodities, Weight, Type, and Carrier information)
      2. Shipment - This provides similar information as load but excludes information such as requirements for POD/Weight/Rate Confirmation
      3. Broker Carrier - This provides any updated information for the Carrier.
4. TriumphPay Audit provides information to Tai; this occurs when the Approve has been sent over from TriumphPay Audit.
   1. They can check any document on Hubtrans end with a flag ("Use as POD") that will enable the document sent over to be set as a POD Document in our TMS after the shipment has been Approved; this will have to be triggered for retrieval by updating the Shipment Status.
5. They will verify that the Bill has the correct or revised amount.
   1. Should they require any revisions, they need to modify the amount on our TMS end and update the Shipment Status to send the revised amount to TriumphPay Audit.
   2. They can Approve the Bill, which sends the information to our end and creates the Bill (This will follow the similar steps of an EDI 210.)

Reference/Variance - Load Note

Brokers can put a hold on approving a bill from TriumphPay Audit by sending the shipment to the variance list. These rules need to be set in TriumphPay Audit, which will throw an exception that must be acknowledged and cleared during the audit process.

Disclaimer: 
This integration is only intended to support Truckload and LTL shipments. Marketplace shipments are not supported.