We are using procurement categories for raising expense related POs on projects. We also use procurement categories for non project related POs too.
The problem i am having us, for normal non-project POs we quite rightly want the cost going to the profit and loss account codes which we have linked to the procurement categories using posting profiles. However, for project POs we want the costs going to the WIP accounts. What i am seeing though is that the 'goods receipt' posted cost is going to the nominals linked to the procurement category, but when the PO is invoiced the cost is going to the project category nominal. Problem with this is, the supplier does not always invoice in time monthend etc, so we really do not want costs going to the P&L nominal code, but instead the WIP codes linked to the project groups so the costs are posted and sitting in the correct account regardless of received only or received and invoiced.
I know i could setup seperate procurement categories for just projects (and the nominals for these could be direct to the WIP accounts), however we do not want to just be creating project specific procurement categories if we could avoid it.
Any suggestions on how we can get the 'goods receipt' posting going to the nominals linked to the project categories (i.e. WIP accounts).
PO Receipt on PO using Procurement Categories nominal setup instead of project category
Hi Umar,
This wil be a challenge as receiving goods or services is not a trigger for project consumption in the application. When the invoice is posted, the project transaction will be created and settings on the project group then determines if the costs should be posted as WIP or P/L.
As you mentioned, you can create separate categories to have it posted to another main account, but then still, the project transaction is not created. You can then only report from financial transactions where the project is not aware of them.
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.