The problem here is that the PO 'Orderer' is set to the Employee of the F&O User that created the Purchase order.When the Purchase order is created from a Purchase requisition, it is quite common for the Purchase order to be created by a batch job, in which case, the F&O User is the system account which is running the batch job.In Purchase requisition scenarios, it would make much more sense for the default PO Orderer to be the Preparer of the Purchase requisition (from the Purchase requisition header).This problem also causes an issue in PunchOut (External catalog) scenarios.In the cXML which is sent to the Vendor (Request XML), there is a section for the 'Buyers' name and contact details. The Buyers name and contact details come from the Orderer on the Purchase order header. This makes complete sense, but unfortunately in many PunchOut scenarios the Orderer is blank or an Admin employee, because the Purchase orders are created by a batch job.