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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Modern Bank Reconcilia...
Finance | Project Operations, Human Resources, ...
Suggested Answer

Modern Bank Reconciliation

(4) ShareShare
ReportReport
Posted on by Dixita 296
Hello,
 
I am trying to post customer payment journal through IBAN, I have setup as below,
 
1. I have mapped IBAN and bank account number on customer master
2. Getting the IBAN in payment reference field of bank statement lines
3. Enabled  'Automatic customer account matching' toggle on Generate customer payment matching rule
 
But while running the matching rule, it's posting the customer payment journal for different customer. Have anybody tried this feature yet?
 
Thanks
Categories:
Dynamics 365 Finance
I have the same question (0)
  • André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 303,730 Super User 2026 Season 1 on at
    Hi Dixita,

    Can you share some screenshots of the current behavior? Have you checked if the same IBAN is linked to another bank account from the other customer?
  • Suggested answer
    DAnny3211 Profile Picture
    DAnny3211 11,417 Super User 2026 Season 1 on at

    Hi Dixita,

    Thanks for sharing your setup. It looks like you're using Modern Bank Reconciliation in Dynamics 365 Finance and encountering issues with customer payment journal posting to the wrong customer despite having IBAN mapping and automatic matching enabled.

    Here are a few things to check:

    1. IBAN Uniqueness:

      • Ensure that the IBAN is unique across all customer records. If multiple customers share the same IBAN or if there are formatting inconsistencies, the matching rule may select the wrong customer.

    2. Matching Rule Configuration:

      • Review the Generate Customer Payment Matching Rule setup. Confirm that the rule prioritizes IBAN over other fields like name or reference.
      • You may need to adjust the matching priority or add conditions to narrow down the match.

    3. Bank Statement Format:

      • Check if the IBAN format in the bank statement exactly matches the format stored in the customer master (e.g., spacing, country code, etc.).

    4. Test with a Sample Statement:

      • Try running the matching rule with a simplified bank statement containing only one known IBAN to verify if the rule behaves correctly.

    5. Custom Matching Logic:

      • If the built-in rule doesn’t meet your needs, consider creating a custom matching rule using X++ or Power Automate to enforce stricter logic.

    Let me know if you'd like help reviewing your rule setup or designing a custom match!

    Best regards,
    Daniele

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

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

#1
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 663

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 439 Super User 2026 Season 1

#3
Syed Haris Shah Profile Picture

Syed Haris Shah 337 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP
License usage reporting (in-app and PPAC) with Entra dynamic groups

Product updates

Dynamics 365 release plans