Advanced bank reconciliation has been designed but no bank statement report provides clear information.
Bank statement report is required base on cutoff date. This report should have option to detail
* reconciled transactions
* Un-reconciled transactions
Customer should be able to have a statement at date of what is in his bank account for Audit, cash management, management decision.
Please make a foreign currency revaluation feature available in the bank module for all countries/regions.
This was a painpoint in prior systems and currently still is an issue in D365fO.
Some additional information especially about the related 'pain' and how a lot of companies resolved this in prior versions can be found here: https://dynamicsax-fico.com/2015/04/12/foreign-currency-revaluation-cash-and-bank-management-module/
In the bank management, the Central European way of posting payments is not supported at all.
In Central Europe, instead of performing bank reconciliation, all bank transactions are posted directly based on bank account statement lines. However the possibility to import and post statements to the GL is dismissed (finally the import method "Finnish Basic").
We need a link from bank statement to GL posting functionality (all ledger/sub-ledgers, mainly customers). According to what we heard in the TechConference 2016, this was already "high priority" but nothing has been released since then.
When a payment transaction is imported via Coda, an automatic settlement between payment and invoice is possible.
But in case the customer is not found, no automatic settlement is possible. This is a very sad result, knowing that a structured message (=unique payment reference) is available on the invoice, which is linked to the customer.
lookup the customer based on the structured message (=unique payment reference available on the invoice) and not based on the IBAN or exact customer name derived from the payment transaction.
The number of automatic settlements will increase enormously!
It should be interesting if Dynamics 365 for Operations would be able to Delete, reverse or undo a reconciled bank statement, since this process is subject to human error.
For reference see Solution document Solution 1068001How to Delete, reverse or undo a reconciled bank statement
Give users the ability to set up a batch job to automatically import bank statements from a designated file server at times to be defined by the user. This functionality existed in AX 2012 but does not exist in 365. Some 365 users have 250+ bank accounts that need to be tracked & reconciled. It is reasonable for a user to want batch mode so they don't have to load lots of bank statements every day.
On Bank statement, posting date cannot be selected for transactions mark as
new. Then transactions is posted at bank statement creation date.
When bank statement line is created with May30th, accounting distributions form is showing accounting date with today's date. The expected posting date should be the statement date, not today's date.
The Payment Reference is a key field that very often used to record information relating to the payment instrument being recorded in D365. For instance,
• In the case of Outgoing Payment, the field is used to capture any of the following (a) check number; (b) Wire transfer reference; or (c) ACH reference, depending on the payment instrument that is used when paying a vendor invoice.
• In the case of Incoming payment, the field is used to capture any of the following (a) check number; (b) Incoming wire transfer; of (c) incoming ACH reference, depending on the payment instrument used by the customer in paying an invoice.
Though the “Payment reference” is a freeform field, it is invaluable in the periodic bank reconciliation activity as the value stored in this field is available in the Bank transaction table. This works well for where both the outgoing and incoming payments are entered through AP and AR Payment Journals.
However, in a scenario where customer payments are entered through the “Call Center” module, the payment reference is not transferred to the Bank transaction table. When then payment is entered a field labeled “Check number” is displayed and the freeform value is not carried over to the Bank module. The system inserts the Sales Order number being paid in the “Payment Reference” field and it also takes the same Sales Order Number and inserts it in the “Description” field of the Bank Transaction table module.
We are requesting that a change is made in the “Call Centre” module that any payment reference entered by the user is carried over to the Bank Transaction table in order to help in bank reconciliation activities.