That would be the correct report. It is not pulling the customer invoice number from the AR Tables. It is a field on the PO. You can modify the columns to remove the customer invoice number column.

Gina, you are not understanding the problem. The CUSTOMER INVOICE number is not the correct field that should even be available. The PO is balanced against Receipts/Bills. However, SAGE does not provide the valid option for these fields. Instead, the report provides the Customer Invoice Field.

A PO issued to a vendor needs to have a simple report to help identify which transactions are fulfilling the PO.

I would say you're right that I am not understanding the problem. The PO Report shows open POs for number of items ordered, received (if not fulfilled completely), and remaining to receive. I use the report to determine which orders I need to follow-up on because the timeframe to receive items has not met my expectations. 

I balance my POs against bills and receipts when I go to enter them in the system, on the Purchases/Receive Inventory screen. When you have a PO open, you can click on the link to View Related Transactions, which will allow you to view any sales order or payments attached to it.

I still say providing the customer invoice number as an available column on the PO report is not a programming error when that field is available for use on POs. If one does not use that field, they would remove it from view on the report, same as any other report. 

Are you looking for something more like the vendor transaction history report?

More like the Transaction History Report, but that report begins with the Invoices and shows related POs.

I want a report that begins with the POs and shows the related Invoices, and ideally also be able to show item details. I need to explain to a customer and validate with the Vendor Side as well. The Sales Order Report works and allows drill down. The PO Report not so much. To me the PO Report should provide the like functionality as the Sales Order Report, just from an AP perspective instead of the AR perspective.

The Related Transactions is a lead but requires drilling down on multiple transactions to the details required. This is also problematic in not having the view by product, as similar or same items may be on multiple POs that the customer has received to the wrong PO, which then has to be resolved. SAGE does not appear to facilitate resolving this type of problem.

I do believe that SAGE has made an error in programming in that the Vendor Invoice Data is not available on the report I first mentioned. Required Data should always be available. Optional data, well that would be more optional and could be an added convenience. 

Open POs do not have vendor invoices, so that is why you would not have that data on the PO report.

The best I can suggest with existing reports is the Purchase Journal, but you may need to reach out to someone that creates custom reports if that doesn't give what you need.

Hi Brian -- if you're not finding what you need in any of the canned Sage 50 reports we can assist by creating a custom report using the XLGL reporting tool -- if you'd like to discuss this option feel free to reach out -- [email protected] or 800-339-8224.