Bank Entry; "To Suspense" can create Suspense Items with a Payment Method belonging to the wrong Bank Account

Using the "To Suspense" function in Bank Entry can create Suspense Items with a Payment Method belonging to the wrong Bank Account.

If this occurs, when attempting to allocate the Bank Suspense Item it fails with "Failed to commit Batch. Cannot partially commit Bank Batch. Payment Method 'XX' does not belong to the Bank Account.".

The following sequence creates the issue:

• Add a new Bank Entry batch for Bank Account "A"
• Add a new line for an Account, setting Payment Method, Value etc
• Save the batch
• Close the batch
• Re-open the batch, but change the Bank Account to "B"
• Do not change details on the line
• Click "To Suspense"

The Bank Suspense Item now shows as Bank Account "B", but the Payment Method is one of Bank Account "A".

Note, this can also be recreated when importing a Bank File.

Now, when clicking "To Suspense" and this issue is detected the item is not moved to Suspense. In addition the Summary Page below the grid will show a warning "Payment Method does not belong to this Bank Account.".

The following Standard Summary Page Block has been updated:

• BatchBankTransaction_Summary
• Version: 2.02 (24/03/2022)