PO unit cost error

SOLVED

Hello, there's a unit cost issue with purchase orders in Technisoft Service Manager that we've been grappling with for a while and I wanted to see if this forum could assist.  When a line from a PO is only partially received (cost only) against a job in document entry, the unit cost of the item is changed in order to make the total cost of the COS equal the total cost of the line on the PO.  To explain the below screenshot, the PO has an estimate of 280 quantity at $81.50 unit cost, for a total cost of $22.820.00.  When this line is partially received with a quantity of 240, the unit cost it uses is $95.083333, for a total cost of $22,820.00.  The subsequent receipt from the line of 40 uses a unit cost of $570.50, again reaching an extended cost of $22,820.00.  Also below are screen shots of the item and supply settings.  Please let me know if you require any further information and thanks for your assistance.  

      

  • +1
    SUGGESTED

    Have you talked to Technisoft about this?  They are helpful.

  • +2
    verified answer

    Makarios

    There is a fix for that issue when performing supply to Job operations from multiple Receipts. This fix is available for version 2018, 2019 and 2020 of Service Manager. 

    The supply option "Add to existing" however is usually used when previous receipted values have been supplied but not yet posted in the job. Basically it takes whatever un-posted values on supply for the line and adds the new receipts value to them in a consolidated manner.

    If you are posting the jobs cost though basically after the supply function, the better option is the "Override" which replaces whatever is on supply un-posted with the new receipted values.

    As I said though, there was an issue with the "Add" supply method so if you can send me an email to [email protected] I will send you the details for downloading and applying that fix. I have extensively tested the process using your scenario and values for the best part of today.

    Regards

    Chris van der Waal

    Technisoft

  • 0

    How good is that? Within 24 hours the developer has not only responded in detail, but spent time to create a fix to your point issue. Great work Technisoft.