What IFS Version and update number are you on?  There are some known bugs with this exact error.

Its UPD17

Thanks

Hi @BLLBrucemo 

Do you have an event action defined for this and if so there in To field have you included &PDF_PARAMETER_1

Thanks Dhananga, yep. The ‘to’ field does have &PDF_PARAMETER_1

I have tried using report rules instead, but seems same issue! grrr

Bump.

We are seeing this as well, and have configured our suppliers correctly.

I am confused about the Event Action -- is a Custom Event actually needed here? I do not see one for us, and payment advice emails have been going out correctly in the past.

Did anyone figure this issue out? We are seeing the exact same thing in the App Message log.

Thanks,

Joe Kaufman

@BLLBrucemo were you able to find a solution for this? We have the same issue where we too use a report rule for the payment advice email. In our case I noticed this is happening specifically for one of the three companies we have. So my suspicion was on their mail server. However with this query you have posted, I’m wondering if the issue we are having is the same as yours.

Hi All,

As the issue is happening randomly, I believe this might be connected with a load/amount of application messages processes at any given time. Anyway, it is better you can report the case to IFS support to identify the exact issue. Rather Finance team, I believe this should be investigated by the Framework team as it seems connected with the mail server.

I can’t get to your document but we have had similar issues with customer order invoices failing with the same message.  It came down to one field on the customer order a user could/had manually amended which over-wrote the default (required) information from a list of values.  Is there any such field on the Payment transaction/order?

Linda