Purchasing in WorkGuru is designed to be very flexible to suit a number of project requirements around purchasing stock and services, ensuring the accounting is automated correctly in the background.


The purchasing workflows generally breakdown into the following 3 scenarios:


  1. Stock Purchase Orders - Stock orders are orders for FIFO or NonStock products that aren't associated to a particular project number.   FIFO SKU quantities on a stock order will be added to the SOH in WorkGuru, these stock lines will coded to the WorkGuru Inventory account in the accounting system.  NonStock SKU quantities will be treated as an expense line in the accounting system.
  2. Project Purchase Orders - Project orders are purchases orders that are associated with a particular project and are treated as an disbursements.  For this purchase order, it is assumed that all the costs are being attributed to that project as a whole.  Project POs as a disbursement on the project are able to be marked up invoiced directly through to the client.  This is perfect for easily invoicing sub-contracting work on a project for example. Note - Project Orders handle the account coding differently.  As they are classed as disbursements and the assumption is all the SKUs on the orders are being used on the assigned project, FIFO SKUs on project orders do NOT increase the SOH in WorkGuru or code to the inventory in the accounting system.  All project orders are classed as expenses.
  3. Landed Cost Purchase Orders - Landed cost orders are purchases raised for expenses that you have been invoiced to land your stock orders.  Examples include shipping/freight, duties and customs expenses.   These orders are raised like other purchases and costed agains the suppliers invoice. The difference is the value of these orders are attributed back to an existing received stock purchase.  In landed cost purchase orders, the SKUs, even if they are NonStock,  are coded to the WorkGuru inventory account in the accounting system as they are increasing the value of the products on the attributed POs SKUs.   The costing is split by qty and value.