Sue Clifford said:

I can't be the only company that issues one purchase order to a vendor, but has to apply it to multiple projects

Hi Sue,

If you are buying and selling inventory items, the automatic COGS accounting takes care of allocating the costs to each project as it is invoiced, so it doesn't matter that you don't know where each of those dozen air filters are going over the next three months, code it all to a project for 'Stock' or 'Warehouse'. 

If you are doing Assemblies or Bill of Materials, there's no Project tracking through from purchase to sale.

If you need to keep track of unallocated / unbilled inventory, or are coding the purchase order items as expenses /  'Service Items', then you would have to change the allocation for each line when posting the Purchase Order into an Invoice, or keep each Purchase Order separate.

We make a lot of notes in the Description column, then have the person 'flipping' the Order to an Invoice code each line to a Project. 

Or just issue individual Purchase Orders by project.   If the vendor bills these as individual Invoices, they are easy to track to billable Project (even / especially in a paper system.  If a Project is cancelled, you pull all the Orders to cancel them, pull the purchase invoices to return them).

I hope that helps, please post back.

We do not buy and sell into inventory and we aren't doing assemblies or Bill of Materials.

I am doing what you do with lots of notes and then flipping each line once the invoice comes in.  

I am trying to issue purchase orders by project but some of our suppliers want one PO for volume discounts.  

The biggest reason I was hoping to do this is so that I can export the Open POs report and know what is still outstanding by project.  But it doesn't look like I'll be able to do this on the POs where our supplier wants one PO.  It's manageable, just not as seamless as I was hoping for.

Thanks for your help!

Sue Clifford said:

The biggest reason I was hoping to do this is so that I can export the Open POs report and know what is still outstanding by project.  But it doesn't look like I'll be able to do this on the POs where our supplier wants one PO.  It's manageable, just not as seamless as I was hoping for.

The data is stored internally line-by-line, so I'd guess the PO linking to Projects has been limited to a 1:1 choice when it was brought over from a more 'advanced' product to be more limited in the 'entry level' Sage 50 product.

I'm sure some of the other more 'advanced' Sage products would do multiple Projects on a single PO.  We occasionally look at converting to one, but the cost  and learning curve chases us away.

Thank you.  I may investigate,but I feel the same about overcoming the cost increase and learning curve