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, ... / Advanced bank reconcil...
Finance | Project Operations, Human Resources, ...
Suggested answer

Advanced bank reconciliation: automatic reconciliation for partially transactions

(2) ShareShare
ReportReport
Posted on by CS-03030850-0 6
 
Hi,
 
I am trying to automatically match many bank statement transactions to one bank transaction (FO) transaction.
 
As you can see in the screenshot below, the last 6 digits of the "entry reference" in Bank Statement transactions equals "payment reference" in FO as seen below.
 
 
 
I want to match two bank statement transactions with one bank transaction, with the references mentioned.
 
Here is my current setup


I can only find it possible to match from Bank transaction field, to bank statement field.
I think it would work if Bank transaction field would switch position with Bank statement field, but it is not designed this way.
 
Do you have any suggestion on how I can set this up for this to work?
 
 
 
 
 
 
 
Categories:
Dynamics 365 Finance
I have the same question (0)
  • Suggested answer
    Saif Ali Sabri Profile Picture
    Saif Ali Sabri 2,346 Super User 2025 Season 2 on at
    Advanced bank reconciliation: automatic reconciliation for partially transactions

    You're correct—since the standard matching functionality only allows comparisons from bank transactions (FO) to bank statement fields, it won't work for your use case where the comparison needs to be reversed.

    Possible Workarounds:

    1. Custom Matching Logic via X++ Development

      • A developer can modify the BankReconciliationMatchRule logic to allow reversed comparisons.
      • This would require extending the matching logic in BankReconciliationStatementLineEntity to enable matching based on "Entry reference" rather than "Payment reference."

    2. Preprocessing the Bank Statement Before Import

      • If customization is not an option, you could preprocess the bank statement file by reformatting the "Entry reference" to match how FO expects "Payment reference."
      • This could be done using Excel, Power Automate, or a simple script.

    3. Manual Matching as a Last Resort

      • If automation is not feasible, manually selecting and reconciling the transactions might be the only alternative.

    Unfortunately, without the ability to switch the comparison direction, the standard functionality does not support your requirement directly. Would you like guidance on implementing the X++ customization?

  • CS-03030850-0 Profile Picture
    CS-03030850-0 6 on at
    Advanced bank reconciliation: automatic reconciliation for partially transactions
    Hi Saif, 
     
    I see you write that you can only match bank transactions field to bank statement fields and that there is no way of reversing the comparison, which answers my question.
     
    Without any function to do matching the other way this will be useless for me.
     
    Appreciate you time,
     
    Chris
  • Suggested answer
    Saif Ali Sabri Profile Picture
    Saif Ali Sabri 2,346 Super User 2025 Season 2 on at
    Advanced bank reconciliation: automatic reconciliation for partially transactions

    Advanced Bank Reconciliation – Automatic Matching for Partial Transactions

    In Dynamics 365 Finance, the standard reconciliation matching setup only allows bank transaction fields to be matched to bank statement fields, preventing you from reversing the comparison. Since your requirement is to match the last six digits of the "Entry reference" (Bank Statement) with the "Payment reference" (FO Bank Transactions) for a Many-to-One match, follow the steps below to achieve this.

    Option 1: Modify the Matching Rule to Extract the Last 6 Digits

    Since D365 Finance does not allow direct reversal of bank fields, you can manipulate the data by using "Contains" filtering and a workaround within the system.

    Steps to Adjust the Matching Rule:

    1. Go to:
      • Cash and Bank Management > Bank Statement Reconciliation > Reconciliation Matching Rules
    2. Edit the Matching Rule:
      • In Step 1: Define the Grouping Conditions, ensure Entry Reference is used for grouping.
      • In Step 2: Define the Matching Rule, do the following:
        • Bank Transaction Field: Payment reference
        • Operator: Contains
        • Bank Statement Field: Entry reference
    3. Test Matching with Partial Values:
      • If your system does not automatically recognize partial values, you may need data transformation before import.

    Option 2: Preprocess the Bank Statement Data (Recommended Workaround)

    Since the system cannot match partial values directly, preprocessing the bank statement before importing is an effective workaround.

    Steps:

    1. Extract Last 6 Digits from Entry Reference (Bank Statement Transactions)

      • Use Excel or Power Query to create a new column that contains only the last 6 digits of "Entry Reference."
      • Save the modified file.

    2. Import the Adjusted Bank Statement Data:

      • Go to Cash and Bank Management > Bank Statements
      • Import the file containing the adjusted "Entry Reference" field.

    3. Run the Matching Rule with Adjusted Data:

      • Since the Entry Reference field in the statement will now match the Payment Reference, the system should successfully reconcile Many-to-One transactions automatically.

    Option 3: Customization (If Required for Automation)

    If preprocessing data externally is not feasible, you can ask a developer to modify the standard reconciliation logic in X++ to:

    • Extract and compare the last six digits dynamically.
    • Enable flexible field mappings in the matching rule setup.

    📌 This requires technical development in D365 Finance.

    Final Recommendation

    ✅ For a quick solution, preprocess the data before import.
    ✅ For a semi-automated approach, modify matching rules with "Contains."
    ✅ For full automation, consider a customization.

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
Our Community Code of Conduct has been updated!

Quick Links

Responsible AI policies

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

Andrés Arias – Community Spotlight

We are honored to recognize Andrés Arias as our Community Spotlight honoree for…

Congratulations to the August Top 10 Community Leaders!

These are the community rock stars!

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

#1
Sohaib Cheema Profile Picture

Sohaib Cheema 844 User Group Leader

#2
André Arnaud de Calavon Profile Picture

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

#3
CA Neeraj Kumar Profile Picture

CA Neeraj Kumar 553

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans