COGS for Non Inventory Purchasing | IFS Community

COGS for Non Inventory Purchasing

  • 20 October 2021
  • 3 replies

Userlevel 3
Badge +5

When Apps 10 came out there was a disconnect from purchasing in Work Order for non-inventory parts. Case G1981255 was filed at the time. It seems that this is still a problem. The Non-Inventory purchase that is extremely common in Service Work Orders for subcontracting is still not hitting WIP or COGS. I see that it hits M93 and then TP3 it never converts. Is there a plan to fix this? We also lost the ability to capture the cost at receipt which is also a huge problem in the Service industry, as we need to bill the customer as quickly as possible and not have to wait until the invoice is put through.

3 replies

Userlevel 1
Badge +2

Hi Cindy,

I seems to not understand the case, it all starts with a purchase requisition on the Work Oder for an non-inventory part. From the purchase requisition a purchase order is created.

Then the non-inventory part arrives and we get a cost line on the work task, this line is seen as a preliminary cost on the work task and we don’t handle the accountings on the work task for it, it is there to facilitate for early invoicing of the customer.

Then the supplier invoice comes and we handles the M93 from the invoice and repost it to TP3.

I’m not following as this is as it was in IFS Application 9 also with the use of Cost Sold service with T3 on the supplier invoice cost.


Userlevel 3
Badge +5

Hi Hans,


The above mentioned case was entered when we saw this issue in Apps 9. It has just never been handled in a way that makes sense to Service and/or the accounting that happens in Service oriented businesses.

Userlevel 2
Badge +3

Hi all,

I have a question/problem related to the above.

You mention that when the Supplier Invoice comes, IFS handles the M93 from the invoice, and reposts it to TP3. This doesn’t happen if the Work Task Transaction is marked as “Finally Posted” though.

As you say, the preliminary cost is there to facilitate the early invoicing of the customer. Once this is done, we close the Work Order (so that both the Work Order and Work Task move to a Finished state). Once the Transfer Reposting Transactions has run again (overnight), then the Work Task Transaction is automatically marked as “Finally Posted”.

It is possible to re-open the Work Task, and there is a Right Mouse Button available to “Remove Finally Posted” - however this errors. Having dug into the code, this is because the Work Task Transaction is now in a status of Overtaken.

As a result of this, there is no TP3 posting, and the amount just remains sitting on the M93 posting with no way to remove it.