receiving_goods:show_outstanding_purchase_order_lines

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
Last revisionBoth sides next revision
receiving_goods:show_outstanding_purchase_order_lines [2017/08/25 13:46] – [Managing outstanding purchase order lines (pipeline stock)] Gary Willettsreceiving_goods:show_outstanding_purchase_order_lines [2020/05/19 00:09] – [Finalising purchase orders] Mark Glover
Line 1: Line 1:
-{{indexmenu_n>50}} +{{indexmenu_n>40}} 
-===== Managing outstanding purchase order lines (pipeline stock) =====+====== 7.04. Managing outstanding purchase order lines (pipeline stock) ======
 Stock that you have ordered and waiting to be delivered is called your pipeline stock. Sometimes it's helpful and important to monitor this stock so mSupply has functions to help you do that. Stock that you have ordered and waiting to be delivered is called your pipeline stock. Sometimes it's helpful and important to monitor this stock so mSupply has functions to help you do that.
  
Line 50: Line 50:
 It is good practice to finalise purchase orders for which you have received everything because it also removes the purchase order from the list you can create a goods received note from (see [[receiving_goods:goods_receipts|Receiving goods (goods receipt function)]]), making it easier to find a purchase order you're wanting to create a goods received note for, and means that no changes can be made to the purchase order in the future. It is good practice to finalise purchase orders for which you have received everything because it also removes the purchase order from the list you can create a goods received note from (see [[receiving_goods:goods_receipts|Receiving goods (goods receipt function)]]), making it easier to find a purchase order you're wanting to create a goods received note for, and means that no changes can be made to the purchase order in the future.
  
-But beware: don't finalise a purchase order **before** you have received everything the supplier is going to send because you won't be able to make any changes to it or receive goods against it using the goods receipt function ([[receiving_goods:goods_receipts|Receiving goods (goods receipt function)]]).+But beware: don't finalise a purchase order **before** you have received everything the supplier is going to send because you won't be able to make any changes to it or receive goods against it using the [[receiving_goods:goods_receipts|Receiving goods (goods receipt function)]].
  
  
-// Previous: [[receiving_goods:editing_pack_sizes|Editing Pack Sizes]]     Next: [[receiving_goods:donors|Managing Donors]]//+=== Why can't we just un-finalise this PO ourselves? === 
 +Purchase orders are a legal contract, for payment, and referred to for auditing purposes.  As such they must be protected from misuse. 
 + 
 +When a PO is finalised somebody with authority has said "we are not receiving anything more on this PO". 
 +This will be because either: 
 +  - all ordered stock has been delivered 
 +  - the supplier has failed to supply in accordance with the PO contract e.g. supplier has been super late and still hasn't supplied stock.  This PO is finalised because the contract is in breach, and nothing further will be received/accepted against the PO.\\  It is **most irregular** for an organisation to turn around and say, "wait, we'll continue to deal with the supplier on this order even though the contract is in breach" and unfinalise the PO - auditors will likely want to see good documented evidence to support why this is appropriate.  No manager in their right mind would sign such a document...\\  A new purchase order, needing new approval by management would be more appropriate. 
 + 
 +\\ 
 +\\ 
 +|  //  Previous:  **[[Receiving_goods:editing_pack_sizes|7.03. Editing pack sizes]]** | | Next: **[[receiving_goods:custom_stock_fields|7.05. Custom stock fields]]** //  |
 ---- struct data ---- ---- struct data ----
 ---- ----
  
  • Last modified: 2020/05/19 00:22
  • by Mark Glover