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.