That is exactly why they do not appear on the Summary page: there is nowhere to put them, because they have not resulted in a posting to any account.
This is why I was opposed to including purchase orders in projects. It leads to confusion and contradictions.
Iām not against Manager tracking the future business. I am against lumping the tracked amounts in a āSuspenseā account.
When utilizing Purchase Orders and Purchase Invoices to track Contractor Employees, it is relevant to be able to track the costs of the use of those contractors on the Project Wise tab to properly capture contract expenses vs. labor rates used to charge customers.
Since, a project can be chosen in the creation of a Purchase Order, It is useful and important to be able to assign those charges to a particular Project when creating a Purchase Invoice.
What is your point, @DDM?
I need to be able to include a Project Code on the Purchase Invoice so that I can track my expenses incurred through the use of 1099 contractors on my various projects. Currently, when copy a Purchase Order into a Purchase Invoice you cannot include a Project Code. All of the 1099 Contractor incurred expenses end up in a suspense file in the Project Report. Makes it hard to track all expenses for a project to properly determine profit/loss on a project.
That is because it was already included on the purchase order. If you create a purchase invoice without a preceding purchase order, the option is available. This prevents double-counting. Personally, as I mentioned above, I do not like the fact that purchase orders appear in project reports. But that is how the program works.
That is because purchase orders do not include posting accounts. This was explained by @Ealfardan in post #17 above.
If you want to add the project designation at the purchase invoice stage, you need to create a purchase invoice manually, not by copying the purchase order. After you have selected a posting account, the Project field appears. This is an effect of the developerās decision to include purchase orders in project direct costs, and is one of the reasons I objected when the feature was introduced. But several users complained that purchase order costs were not being included in project reports, and their viewpoint carried the day.
Me neither.