Ankit Dynamics

There are currently few options available under bank reconciliation rules to set for finding and sorting bank transactions. Since each bank have its own way to produce statements and provide references in the statement, it is found that the current available fields are not enough to set up rules and would lead to do customer a manual reconciliation, which involves much human efforts and increase client cost to run the process.

It would be beneficial if bank reconciliation rules have the followings fields for the D365 bank transaction to setup additional criteria and grouping.

Voucher: A voucher on the customer/vendor payment line is mostly unique and can help to sort out the transactions easily.

Document number: A document number available on the customer/vendor payment line (not the deposit slip document number.

Method of payment and Payment specification, Category purpose, Charge bearer, Local instrument, Service level -

Methods of payment, payment specification, and various purpose selected on the journal lines could.

Cheque number - Cheque number on journal line.

Reason code - Reason code selected on journal line

FINANCIAL DIMENSIONS - financial dimension selected on journal line.

These fields are most commonly used for vendor/customer payment journal. Currently these are not available in additional criteria for bank reconciliation rules. With having these fields, it would be more easy to sort out the bank transaction and thus enables the bank transactions to match transaction with bank statement transactions. It reduce the client manual activity to find out the transactions manually.

Also, D365 should provide option to auto generate two field value in vendor payment journal / customer payment journal based on journal names and number sequence.

The field basis on the journal name will allow to fill a default fixed value on vendor payment journal / customer payment journal. This will help in the group condition setup, where a bank provide one line amount for multiple transactions.

The field basis on number sequence allow to have a value in vendor/customer payment journal which can be mapped to the file sent to bank for payment and thus getting the same value back in bank statement.

1. Parameter "Require manual matching with advance bank reconciliation find multiple documents that match on amount" is set to yes. The bank statement has transaction code 195 and two lines for the same amount of 2500 dated 01-Jul-23, but the D365 bank transaction has one line for of 2500 dated 01-Jul-23. A bank reconciliation rule is created where the bank statement line transaction code is 195 and in bank transactions, it will match with amount and date. Here, D365 is randomly matching one statement line amount of 2500 with a bank transaction line amount of 2500. D365 should stop matching if statement find two/more lines with same amount, as it could match the wrong statement line with the wrong transaction line.
2. Many customers use BAI2 statements or other statements as provided by their bank which does not mention its a reversal transaction. For the reversed transactions in the bank statement, the imported statement from BAI2 format in D365 does not enable the Reversal field. It is not possible to clear the statement reversal transaction with the statement positive transaction manually and also by the reconciliation rules in the reconciliation worksheet. Solution is required for this issue as first step in reconciliation to clear the reversed transaction.
3. Bank transaction types should allow selecting account type (Ledger, Bank etc.) and Account. A new parameter which override the 'Allow multiple transactions within one voucher' will be applicable for this. This will allow auto creation of transaction from bank for bank to bank transfer.
4. Default description for offset account. Bank account generally entered as offset account (vendor payment journal, customer payment journal). D365 should allowed auto defualt description to be created for offset accounts as well.

Other related idea for advance bank reconciliation - https://experience.dynamics.com/ideas/idea/?ideaid=09763ae3-de7e-ee11-a81c-6045bd8043.

A Customer generally have multiple Sites/branches where users create multiple journals to post the customer payments for multiple banks, multiple transaction types, method of payment etc. and the bank statement provide total amount for a transaction type. This cause difficult, time-consuming and cost impacted to match the D365 transaction with Bank statement. The finance department also wants to see daily transaction summary in the system.

The parameter "Summarise amounts in bank account" available under Journal names is not sufficient due to its limited capability to summarize the transactions by journal name.

It would be quite helpful if this parameter would be extended to allow summarize the transaction for a given date range for multiple journal names based on criteria set by the functional consultant.

So, it should allow the consultant to configure the summarization by

1. Selection of required Journal names

2. Selection of other criteria such as Methods of payment, transaction type, document number, description, offset account, financial dimensions, financial tags, payment reference, payment id, reason code etc. The more fields available from the journal to select, the easier for the consultant to meet the client requirements.

3. It Should allow to run a daily batch job for the date range, relative dates like today, yesterday etc.

Another functionality available in D365 is Deposit slip generation. It can be tried extend the deposit slip functionality and make it for both vendor and customer with above mentioned change.