1. Write the PSI Load ID in the upper left hand corner of the POD
2. Write the Owner Load Number in the upper right hand corner of the POD.
3. Circle the owner load number on the document, total weight and number of pieces on the POD.
4. When scanning the POD, include the load tender sheet or a copy of the rate agreement if it is available.
5. On the back of the POD sheet that is not scanned and is a blank sheet of paper, write down the rate, what the load should invoice at, who the bill to customer is. Write down the backhaul index that includes the Ship From, Ship To & Bill To on the back.
6. Create the backhaul with all of the information including the PD label. Leave it in scheduled status.
7. Have another associate review all the information written on the POD and make sure it is correct on the Backhaul information in Genesis.
8. Once approved by the other associate, the other associate will move the load status to delivered status and scans the POD documents.
9. Once their is an Image Doc present, the load will invoice. The original associate that created the load will then go into Accounting Quick check, make sure the load invoiced correctly, write the Invoice number in the upper left hand corner under the load id and the amount of the invoice.
10. If everything is correct , then can file the paperwork. If it is incorrect, need to contact Accounting immediately to cancel the invoice.
IT Use Only:
The only thing that currently that exists is to not have freight automatically invoice after it is in delivered status and the POD appends to the load to put it in Invoiced status is Choice Field 685 Backhaul Approval Reqd.
This Field Choice contains a list of bill to customer ids. If PSI is billing 1 of these customer bill to ids, then after the POD Scans from the backhaul being in delivered status, it goes to awaiting approval status instead of invoiced. The issue with this is that it is customer id based and currently can not be set up by plant.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article