Microsoft Dynamics 365
on 9/14/2020 4:09:31 PM
Thank you for your feedback. This is a great suggestion! We will consider this in our roadmap.
Dear product group, we just had another partner emphasizing the need for a change in this current design.
Following their insight: "This is a bug need to be fixed.
The function auto create journal, (the match rule) can’t be used when the posting date doesn’t match the bank statement booking date. Specially the bank fees normally happen at the end of the month. The file will be imported earliest the first date of next month. It will be caused different balance between the bank statement and bank transaction at the end of the month. "
Kindly review the matter again and reconsider the possible design change.
Cash and bank management
Please give an information when do you plan to fix this issue as it is stopping point for using the functionality..
To fix this issue it takes 5 minutes of work (we have fixed this internally).
Please fix this as soon as possible since Bank statement is never received on actual statement date.
We have dozens of legal entities and need to use the Adv Bank reconciliation but can’t because of this issue.
I personally see this as a design defect and flaw and I cannot imagine how other customers handle this. The bank reconciliation is really a fundamental accounting principal but the process cannot be fully supported based on the current functionality that lays within the advance bank reconciliation in Dynamics. As noted and explained previously, the business will always have a discrepancy between the accounting records posted to GL vs the transactions executed on the banks side. The two sources will never be mirrored.
So what is the real purpose of having any matching rules configured with the “Action” set to “Mark new transactions” in this case. The functionality doesn´t support the base so why should we map any transaction codes to bank transaction types. This is very misleading from an accounting and audit perspective, and I highly doubt that this is accepted somehow from an internal accounting group perspective.
As noted, the voucher date when the records are posted to GL are indeed todays date or equal to the date when you imported posted the “New” transactions.
This is the issue that we are currently facing. The system should consider the value date in the statement lines and set that to the posting date on voucher level.
The business impact of the issue is inability to use “mark as new” function during the bank reconciliation because of probability of a transaction to be posted into the next fiscal period.
Even if we do a reconciliation daily bank sends a statement for a previous business day the next day. It means that we receive the last statement in the month the next day which is already in a new fiscal period. D365 will post any “new” transaction by todays date while they must be posted into the previous period.
It became even more complicated if a company decides to do a bank reconciliation once at the end of the month (meaning first date of the next fiscal period)