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

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Date issues in bank st...
Finance | Project Operations, Human Resources, ...
Suggested answer

Date issues in bank statement import (ISO20022).

(0) ShareShare
ReportReport
Posted on by Sevren 5

Hi,

I’ve been trying to set up the import of ISO20022 bank statements following these instructions:
https://docs.microsoft.com/en-us/dynamics365/finance/cash-bank-management/set-up-advanced-bank-reconciliation-import-process

Using following recousreces:

BankStatementDocumentEntity.xml
ISO20022XML-to-Reconciliation.xslt
BankReconciliation-to-Composite.xslt

 

But I ran in to an issue. The XML-file we receive from the bank doesn’t contain the tags from and to date.

<FrToDt>
      <FrDtTm></FrDtTm>
      <ToDtTm></ToDtTm>
</FrToDt>

 

Instead of the tags above the file we receive only contain the tag created date and time: 

<CreDtTm></CreDtTm>

 

How/can I change so during import the fields From and to date gets populated by <CreDtTm> instead? Been experimenting and looking for instructions on similar changes in the forum but can find any helping instructions/solutions.

Thankful for all kinds of help!

  

Note: Just to check everything else was OK with set up I manually added these and then the import succeeded.

Version : Finance and Operations (10.0.6)

/ Sevrén

I have the same question (0)
  • Suggested answer
    Community Member Profile Picture
    Community Member on at
    RE: Date issues in bank statement import (ISO20022).

    Hi,

    I had a similar issue with BankAccount number in the import file with the branch code like 123-456 2345931 where 123-456 was the branch code and shouldn't be there, which resulted in error since it couldn't find the bank account.

    I had to extend a method searchBankAccountTable() in the BankAccountTable, which was used by the statement import process to truncate the first 7 characters of the string and then select the correct bank account.

    Hope this helps to find a solution for your issue by extending the staging table used by the import process.

  • Andrew Jones a1x Profile Picture
    Andrew Jones a1x 136 on at
    RE: Date issues in bank statement import (ISO20022).

    Did you ever find an answer to this? I have the same requirement (and many more) that we were previously doing with xslt transformations, but now that MS is deprecating the DMF import and we are going to use the ISO20022 ER import I'm struggling to achieve the same result

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

News and Announcements

Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft

Quick Links

Responsible AI policies

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

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

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

#1
CA Neeraj Kumar Profile Picture

CA Neeraj Kumar 2,028

#2
André Arnaud de Calavon Profile Picture

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

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 579 User Group Leader

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans