Settings and activity
2 results found
-
489 votes
Hi community, some time passed since our last update in the thread here we do want to return and share - while our product teams explored possibilities for how we might represent Purchase Orders in Projects research has confirmed that there is underlying work needed to the platform Purchase Orders are built on before we can achieve any good outcomes of your needs here.
We have enthusiasm and a close eye remaining on the support for this, but want to be honest that this is not something that we’ll be able to focus our attentions on in the near future.
Once we have completed work first needed in the Purchase Orders space we can reassess how to integrate purchase Orders into Projects and will update you all of steps forward, here.
Tristan Wheadon
supported this idea
·
An error occurred while saving the comment -
1 voteTristan Wheadon
shared this idea
·
The functionality to be able to raise and approve a Purchase Order which, at the point of approval, would create a double entry in the general ledger. Specifically:
• Debit a Work in Progress (WIP) expenses account (to reflect anticipated expenditure),
• Credit a creditors account (to reflect the anticipated liability).
This would allow the PO to reflect a commitment in the accounts, enabling better management of Work In Progress and projected costs before the supplier invoice arrives.
In an ideal world, to be able to allocate the PO to a Xero Project, so that WIP and anticipated costs appear within the project reporting as well. This would give far more accurate forecasting and project-level financial visibility.
As it stands, it is understood that Xero POs are non-posting documents and only affect the ledger once a bill is created and approved. That leaves a visibility and accounting gap for committed costs — especially problematic for longer-term projects or cashflow planning.