Settings and activity
2 results found
-
360 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.An error occurred while saving the comment 
Thomas Hedberg Jr
supported this idea
·
-
118 votesThomas Hedberg Jr
supported this idea
·
We thought this was a critical function for us until we had a customer who issued us multiple POs for a project. We add each PO as Tasks to our projects (see attached). This way we can invoice across multiple POs on a single invoice and the customer can accurate apply the invoice task lines to the appropriate PO. This also lets us track our status for POs from within the Project app. We use this practice whether our customers issue a single PO or multiple POs per project.