Skip to main content

Hi IFS network,

I have an issue at a customer who is not able to match a supplier invoice against a PO which is created from a Work Task. The Work Task is in status finished, now it is not possible anymore to match the invoice against the PO receipt (only when you reopen teh work task it is possible again). 

I see that from UPD16 there is a fix deployed, see 

 

This fix was related to invoices without a PO reference. I think it should be possible to match an invoice with a PO Receipt, even when the connectexd Work Task is in status finished. Normally the person who is responsible for the status of work tasks is not the same as the person who is booking the invocies. The invoice will come weeks later than the work is executed, so this is really a timing issue.

Please advice on this issue 

@Thommy and @Nethmini Kosvinna 

Hi Robert,

You are correct, the fix should be related to invoices without a PO reference.

It should be possible to match an invoice with a PO Receipt even though the Work Task is Finished.

If that isn’t possible please raise a support issue on that so it can be looked at.


Thanks @Thommy , I will create a case for this issue. When I have an answer, I will update this tpoic.


Hi! Wondering if you had received any updates on this issue @EqeRobertK ? We’re having the same problem and it’s becoming a pain to have to re-open the work tasks. 

Thanks!


@kristi.king , This is fixed from UPD18 onwards. Can you check your upd?

BR, Robert


@EqeRobertK  @Thommy  Can you tell us which version of Cloud has the fix?  We are on version 23.1.8.

 

Thank you,

Joann


@jtobin , needed to do some detective work to find information.
Seems that the problem with matching invoices on PO receipt from Work Task was introduced by another fix.
This other fix was only applied to App10, so the correction for matching invoices on PO receipt from Work Task was only applied on App10.
So to my understanding there shouldn't be a problem with this matching in Cloud.
If you have problem in Cloud with this flow, please raise a separate support issue for this.


@Thommy  Thank you.  We’ll submit a case.

 


Reply