Can you provide details on how to print Purchase journal which shows expense as well tax amounts?
QuickBooks makes it simple to access your Purchase data and I'd glad to show you which report to run in order to view your that important info.
Based on your description, you can either run a Purchases by Product/Services report or a Purchases Supplier Detail report among many other helpful reports. To find these reports, click on Reports on the left navigation menu and enter the keyword "purchase" in the search field to see which report are related to purchases.
Once you have the report pulled up, you can click on each transaction to check for details such as tax etc. QuickBooks offers the flexibility to customize the report so you can view it the way you'd like to. To customize a report, click on Customize > navigate to Filter or any other options to see which info you'd like to work with on the report.
Give this a try and if you have further questions, I recommend contacting our support team using this link.
I was going to answer the same thing to this OP, but then realized that if you are in a non-participating (meaning are a GST province not an HST province), then the report you cite does not give you correct information, especially if you include the Net Amount column and the Tax Amount column.
In this report, the PST does not show as becoming part of the cost of the item, which should be included in the Net Amount on the report. Instead, it is included in the Tax Amount column, which only the GST should be in. Interestingly enough, QBO treats the PST tax paid on purchases correctly when it comes to the P & L, and other reports citing costs/expenses. Before you posted your answer, I had just sent a private message to @LauraAB letting her know this is the case.
I don't know if the OP is in an HST or a GST province; if he/she is in an HST province, then the report is fine. But for persons in a GST/PST province who want to know their true net cost separated from tax using this report, the existing report will give them erroneous information.
Hopefully it would be an easy fix for your developers . . . ? :)