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

Announcements

News and Announcements icon
Community site session details

Community site session details

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

D365 advanced bank reconciliation best practices on matching rules

(2) ShareShare
ReportReport
Posted on by 227
Hi all,
 
Hope that your summer is going well.
 
First of all, i am sorry for taking from your time because i am an IT person and not a "Cash and Bank" or "Accounting" specialist.
 
I have been doing some reviews on internal processes, and 1 particular thing got me.
 
"Advanced bank reconciliation".
 
What i have seen is not something i like based on the fact that Microsoft offers so much more in this space.
What we are doing basically is the following - we import the bank statement and match manually like click on the bank statement and afterwards find the corresponding line in d365 books.
No matching rules, no matching sets, no anything.
Of course, for small legal entities this is fine, but for LE with 1k transactions a month this is nightmare.
 
Today i have been reviewing one "Bank Reconciliation" statement and i noticed the following.
Basically, besides amount and date there is nothing else i can create a rule and match automatically on.
All the videos and documentation i have gone through almost every time uses the Reference No. that most of the time = the Payment reference...
 
 
 
My question is.
The payment reference is something that accountants are putting in the journal, correct?
If they leave it blank it will be blank during reconciliation?
 
Can you please advise me on the best basic matching rules we can implement initially?
 
In your experience does a rule based only on amount and date working properly or it opens the door for mistakes ?
 
I will appreciate any advice and proven working practise in this area as it is brand new to me.
 
From configuration perspective i don't have questions right now, because everything else will require the matching rules/sets to be working in the first place.
 
Thank you.
 
 
Categories:
I have the same question (0)
  • Suggested answer
    BillurSamdancioglu Profile Picture
    21,381 Most Valuable Professional on at
    Date is mostly be different and date and amount might be very often the same.
    Reference is better. Why, because when this was done manually, accountants do it by to check the reference.
    Auto reconciliation is to help accountants. 
    Even there is auto reconciliation, accountants still approve/control what is matched and match the one that are not matched.
    Accounting users do not make errors so often.
    Even so, there is a less risk by to match by reference.
  • Martin Dráb Profile Picture
    240,281 Most Valuable Professional on at
    Moved from Integration, Dataverse, and general topics forum to Finance | Project Operations, Human Resources, AX, GP, SL forum, because it's clearly about a particular product (not D365 in general) and I believe it's F&O.
  • Verified answer
    vishalsahijwani Profile Picture
    343 on at
    Hi ,
     
    Before making the matching rules please make sure you have made payment reference entry mandatory or make sure it gets populated on its own.
     
    It can be really effective if you can make the matching rules as per combinations in the exact sequence mentioned below : - 
     
     
    1) Payment Reference and Amount
     
    2) Payment Reference and Amount (With a small date tolerance with 3 days more or less)
     
    3) Amount fetched from Transaction code and Amount - Transaction codes tells us what kind of transaction it is - Wire Transfer , Cheque , Credit card etc
     
    4) Many to One Or One to many sum matching - There can be chances like one bank statement can reference to multiple customer receipts and multiple bank statements can lead to settlement of a single customer invoice.
     
     
  • SM-17050844-0 Profile Picture
    227 on at
    Thanks Vishal,
     
    Actually, last Friday i made it work for my testing.
    The key is the payment reference, and the information accounting team is putting there.
    Unfortunately, this not aways match the bank statement and therefore in such cases they will have to manually match the transactions....
     
    Anyhow i created 2 simple rules based on the payment reference
    one to one
    one to many [to capture the scenario that you were talking about]
    This wokrs and solves the majority of the transactions i guess in time we can enhance with other rules, but for now this is going to do the job just fine.
     
    Just out of curiosity is there a way to assign number sequence to this "payment reference" field ?
  • Suggested answer
    vishalsahijwani Profile Picture
    343 on at
     
    Actually as per my knowledge Payment reference is a string based field and usually it has been kept as a loose text as most of the organizations enter their own free text values for their own identification. So even as per Microsoft best practices using a number sequence is not recommended and also is not a viable solution. 

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

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the July Top 10 Community Leaders

These are the community rock stars!

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

#1
Martin Dráb Profile Picture

Martin Dráb 265 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 261 Super User 2026 Season 2

#3
Subra Profile Picture

Subra 229 Super User 2026 Season 2

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans