Release date: November 2025
[BCBA-225] Easy registration - Quick Guide not update after registration
Release Description
After a successful registration, the Register label now turns green to clearly indicate that the process has been completed.
[BCBA-222] Custom Advice removed when changing recipient bank in Payment Journal
Release Description
Fixed an issue where Payment Advice in the payment journal was removed
when changing the Recipient Bank Account.
The Payment Advice is now correctly updated instead of being deleted.
Bank Account
[BCBA-223] Placeholder %2 in the file name
Release Description
The Bank File Name field on the Bank Account Card now supports the following placeholders:
%1 – Bank Account No.
%2 – DateTime
These placeholders are automatically replaced when generating the bank file.
[BCBA-212] Double lines in Pay Rec Journal
Release Description
Fixed an issue where the bank feed was imported twice when importing into Payment Reconciliation Lines. This has now been resolved.
[BCBA-215] Under/over payment and multiple invoices
Release Description
Fixed an issue where Automatching did not correctly match the sum of multiple invoices when the payment was an underpayment.
[BCBA-224] When trying to post in a US version, an error message is issued from standard BC
Release Description
When posting payments in the US version of Microsoft Dynamics 365 Business Central,
the following error could occur:
“Bank Payment Type must not be filled if Currency Code is different in Gen. Journal Line and Bank Account.”
This error originates from standard Business Central logic.
The issue occurs because the payment line contains the following values:
GenJnlLine."Bank Payment Type" = Electronic Payment
GenJnlLine."Check Transmitted" = TRUE
GenJnlLine."Check Exported" = TRUE
The AMC Banking 365 BC Extension sets all three values due to the following behavior in the US localization:
In the Bank Account Card, the Export Format field must have the value Other.
This value is validated in Codeunit 11 – "Gen. Jnl.-Check Line", in the local procedure CheckElectronicPaymentFields.
In this procedure, the fields Check Transmitted and Check Exported are checked to determine whether they are set to TRUE.
However, when posting the payment journal, another validation is executed by standard Business Central:
Codeunit 12 – "Gen. Jnl.-Post Line"
Local procedure PostBankAcc
Here, Business Central performs an additional validation where Bank Payment Type must not be filled if the Currency Code differs between the Gen. Journal Line and the Bank Account, which results in the error.
The safest approach was to make an EventSubscriber to Event OnPostBankAccOnBeforeModifyCheckLedgerEntry to work around the inconsistency in standard Microsoft Dynamics 365 Business Central, so the validation in Codeunit 12 – "Gen. Jnl.-Post Line" does not fail.
Should you experience any issues with a release, please reference case number BCBA-XXX when contacting support.