Processing date should be in format YYYY-MM-DD error during SEPA vendor payment generation

(0) Share

Report

Posted on by omesh

141

Hi all

a am facing error "Processing date should be in format YYYY-MM-DD" during vendor payment generation below is the screenshot. can anyone known this error occurs. i have entered same date format i.e. YYYY-MM-DD still it gives error.

6355.date.png

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (0)

Anand.kushwaha 55 on at

Like (0)

Report

Hi Hemesh,

This error usually pops up when the SYSTEM date format and AX date format are different.

Regards,

Anand

Was this reply helpful? Yes No
Suggested answer

Oleg van den Boogaard 556 on at

Like (0)

Report

You could check your payment lines, maybe there is a date stamp that has a different format which is not in line with YYYY-MM-DD.

For changing date format see forum post community.dynamics.com/.../548590 and check respons of MattyHerby

Was this reply helpful? Yes No
Oleg van den Boogaard 556 on at

Like (0)

Report

Hemesh,

Did you find the solution? if so, can you share it with the community so others can learn from it.

Best regards,

Oleg

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

You need to check the format of the date on the AOS and AX.

Was this reply helpful? Yes No
Francesco 524 on at

Like (0)

Report

A 5-year old post, but one of my customers (AX2012R3) gets this error as of January 1st of this year. None of the proposed solutions suggested in this thread apply since nothing has changed in the date format on the server or in the application. They were always set to the "normal" German DD.MM.YYYY format and SEPA would function just fine. Y2K23 bug?

Was this reply helpful? Yes No
Martin Winkler 119 on at

Like (0)

Report

I encounter exactly the same thing today - SEPA payment requires YYYY-MM-DD, which is the format they enter. Also makes me suspect something fishy is going on, have not found reason yet

Was this reply helpful? Yes No
Martin Winkler 119 on at

Like (1)

Report

OK, resolving my issue was simple enough - although very strange, I have no idea how it came to it.

Looking into the SEPACreditTransfer.xsl, I found the error message. I then extended the XSL a little and noticed that I do get format, variant, and country, and the date string was empty. So after some more checking, I noticed that in the payment processing data screen of the credit transfer, the name of the processing date was no longer "Processing date", but something else. No idea who/how changed that, but anyway. Setting the name back to "Processing date" -> all was working again.

Was this reply helpful? Yes No
Francesco 524 on at

Like (0)

Report

I traced the error all the way down to the SEPA pipeline where it went in the black box so I also figured that the problem must be with the XML. I then compared the message from Jan 4th with the last one from Dec (which processed correctly), but didn't notice any difference. Mind you, I was more focused on the data then on the labels, so I might have missed it.

In the mean time one of the beancounters removed (accidently) the line with the processing date in the dialog and then added it again. That mysteriously solved the issue in my case.

Was this reply helpful? Yes No