Skip to main content

Performing Bank Account Reconciliation in D365 Business Central

Introduction:

In Microsoft Dynamics Business Central Bank Account Reconciliation is relatively easier task.
You can make use of Suggest Vendor Payments or make use of Bank Reconciliation Statement file from the Bank to verify payments.

Pre-requisites:

Microsoft Dynamics Business Central

Demonstration:

1. Creation of Bank Account Reconciliation:
Click on New > Select the Bank to create the Bank Account Reconciliation Card
Creation of Bank Account Reconciliation 

Bank Account Reconciliation


2. Bank Account Reconciliation using Suggest Lines:
Select Process > Suggest Lines > Fill in the required details to filter suggestions
Suggest Lines Criteria

Note: When you use Suggest Lines, the lines are suggested from Bank Account Ledger Entries.
Thus Bank Account Ledger Entries and Payment Journal is reconciled

3. Bank Account Reconciliation using Bank Reconciliation Statement File:


4. Reconciling / Matching:
i. Filtering the NonMatched using Show Nonmatched:

ii. Filtering to ShowAll Transactions:

iii. Automatically Matching Transactions: When you automatically matching the transactions, based upon Posting Date, Tolerance Date, Amount, Vendor and Applied Entries, the transactions are automatically matched.

Criteria for Matching by Tolerance Date
After Matching

iv. Matching Manually:
Select the transactions and then select Match Manual


v. Remove Match:
Removing Match
After Removing Match and Filtering Show NonMatched


5. Posting of Reconciled / Matched statements:
i. Transferring Bank Reconciliation to Gen. Journals:
Select Process Action > Transfer Bank Reconciliation to General Journals > Select General Journal Template and General Journal Batch



After Transferring Bank Account Reconciliations.
NOTE: Transfer to General Journals is used when you Import Statement Transactions from Bank Reconciliation Statement File.

ii. Posting Reconciliations:
After all the transaction have been matched and Balance  is equal to Total Ending Balance, you can post the reconciliation

Select the Post Action
During Posting
After all the transactions have been posted then the Reconciliation is removed from the Bank Account Reconciliation List.

Conclusion:

Thus using Bank Account Reconciliations, we can match up the Bank Account Transaction Vs. Payment Journals. You can do manually or system can help you do it automatically.
Until all the transactions are reconciled you cannot post the Bank Account Reconciliation so be sure to do this activity periodically.


Comments

Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: https://community.dynamics.com/nav/f/microsoft-dynamics-nav-forum/261301/nav-2018-web-client-an-error-has-occurred https://community.dynamics.com/business/f/dynamics-365-business-central-forum/421987/error-something-went-wrong-an-error-has-occurred-azure-ad-tenant Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta

Universal Code Error and Resolution

Introduction: On Friday, May 12th, 2023, the Business Central On-Premise Production Environments started throwing universal code errors as follows. This occurred to every customer on a lower version of BC 19,20 and 21 irrespective of their localization, customization, and license. Pre-requisites:  Understanding of Technical Upgrade in Business Central On-Prem References: BC20 On prem. Universal Code requirement error after installing customer's license. - Dynamics 365 Business Central Forum Community Forum (40) Yammer : Dynamics 365 Business Central Development : View Conversation Root Cause: The certificate that signs Microsoft Base Application was expired. Errors started occurring if you Uninstalled, Installed Extensions, Restart Server Instances or for some even out of random started popping out. We first thought could be a license issue as we had fixed that before but this did not solve the issue. Resolution: Microsoft identified the issue and posted the following update The mi

How to resolve 'Edit in Excel' issues

  Introduction: As you know that D365 BC offers Edit in Excel functionality. But manipulating or customizing such a  standard functionality is difficult as there is not much control available. Hence, solving issues is also a difficult task. I will be resolving the issue for this specific issue, however, the debugging steps are similar. Pre- requisites : ODATA V4 Connectivity tool for Webservices Microsoft Dynamics 365 Business Central Books & References: https://community.dynamics.com/business/f/dynamics-365-business-central-forum/448226/issue-with-excel-add-in/ Demonstration: The way Edit in Excel works is that for a given page a Webservice is created adding PageID and Page Name. Hence, there are some Webservice connectivity checks in place to validate. 1. Edit in Excel Custom Action on the page: If you are adding Edit in Excel Action on the page, please ensure that you are providing appropriate PageName and Filter criteria as Webservice is using these parameters Refer Editworkshe