web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Answered

Possible error in ISO20022 SEPA Credit Transfer (FR) xml file

(0) ShareShare
ReportReport
Posted on by 15

Hello everyone,

I am currently testing file exchanges with my company's bank and I ran into an issue about the SCT file generated from the vendor payment journal. The file is also known as the pain.001.001.03 in SEPA vernacular.

I went to check the XSD file provided by the European Payment Council here https://www.europeanpaymentscouncil.eu/document-library/implementation-guidelines/sepa-credit-transfer-scheme-customer-bank-implementation in order to validate the SCT file. A statement was unexpected. Meanwhile, the bank also rejected the file.

The statement in bold is the source of the error as shown below:

<CdtrAgt>
   <FinInstnId>
      <BIC>XXXXXXXX</BIC>
      <Nm>whatever</Nm>
   </FinInstnId>
</CdtrAgt>

I fixed the problem by removing the statement in the template in Organization administration > Electronic reporting > Configurations, but Microsoft might want to think of a more permanent fix.

Am I the only one who ran into this problem ?

I am using ISO20022 Credit Transfer (FR) version 39.47.16.

Kind regards to all,

Alexis

I have the same question (0)
  • Verified answer
    Mea_ Profile Picture
    60,284 on at

    Best way to provide feedback to MS is to log a bug and say that current configuration does not work, so they can fix it.

  • Suggested answer
    MhaU Profile Picture
    on at

    Dear Alexis,

    Thank you for posting the issue on our community.

    The Nm is the name of the vendor bank account. What is the error that you are getting from the bank? Perhaps it is related to a different field. Or if the bank does not require this field to be populated, then leave the vendor bank account name value blank. The fields that do not require to be populated on the XML file should not be filled into the application.

    Let me know if you have any further questions and I will be happy to assist further.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 646 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 529 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 285 User Group Leader

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans