AMC Banking 365 BC - Release 26.0.1.3 | Scribe

AMC Banking 365 BC - Release 26.0.1.3

  • AmcbankingAmcbanking

Release Notes

AMC Banking 365 BC - 26.0.1.3

Release date: June 2026

Payment Journal

[BCBA-292] Payment journal – investigate why voiding the transaction is not working

Release description
The "Check Transmitted" field on Gen. Journal Line was previously set by AMC to always be TRUE, based on the assumption that all payments were transmitted. This assumption is incorrect.

In standard Business Central, the "Check Transmitted" field on the Bank Account is used to determine the value on the Gen. Journal Line. AMC has now been updated to follow the standard Business Central behavior.

Important

If a bank account is configured for check printing in Business Central ("Check Transmitted" = TRUE on the Bank Account), that same bank account can still be used for electronic payments.

However, electronic payments created from that bank account cannot be voided from the Payment Journal, because the "Check Transmitted" flag is set to TRUE.

Payment Reconciliation Journal

[BCBA-294] Users region in BC make currency factor being calculated wrong

Release description
When importing the AmountDetail value from the XTL XML file, the value was converted from Text to Decimal using EVALUATE.

The conversion was dependent on the user's regional settings, which could cause incorrect results when the decimal separator in the XML did not match the user's locale settings.

Resolution

The conversion has been updated to use EVALUATE with parameter 9, which specifies that the value should be interpreted using the XML number format.

By using the XML format during the conversion, the value is now parsed consistently regardless of the user's regional settings before being used in subsequent calculations.

[BCBA-295] Automatch stops when using TextToAccount mapping

Release description
Automatch could breakdown when Text-to-Account Mapping was enabled and there were also open Bank Account Ledger Entries that matched the same Payment Reconciliation Line.

In this scenario, Automatch identified two valid match candidates:

  • A match based on Text-to-Account Mapping

  • A match against an open Bank Account Ledger Entry

The process then attempted to apply both matches to the same Payment Reconciliation Line. Since a Payment Reconciliation Line can only be applied once, the operation failed and caused Automatch to breakdown.

Resolution

Automatch has been updated to compare the match scores of competing match candidates.

When both a Text-to-Account Mapping match and a Bank Account Ledger Entry match are found for the same Payment Reconciliation Line, the candidate with the higher match score is selected, and the other candidate is rejected.

This ensures that only a single match is applied to each Payment Reconciliation Line,
preventing the failure and allowing Automatch to complete successfully.

[BCBA-296] Automatch on lines containing a Creditmemo does not work properly

Release description
The automatching fails when a matching combination contains a credit memo that is evaluated after invoices whose individual amounts exceed the bank statement amount. The matching algorithm should consider credit memos before applying amount-based rejection logic, allowing valid net combinations (invoices + credit memos) to be automatically matched against the statement amount.

Wrong order :
Invoice 785.40 (STD BC will stop automatching because invoice exceed net amount,
when the invoice is applied to "Applied Payment Entry (Table 1294)"
Invoice 287.15
Invoice 168.27
Invoice 160.00
Invoice 139.10
Credit Memo -1514.03
------------------------
Net 25.89

Correct order :
Credit Memo -1514.03 (Must be first to “make” net amount big enough to handle rest invoices)
Invoice 785.40
Invoice 287.15
Invoice 168.27
Invoice 160.00
Invoice 139.10
------------------------
Net 25.89

Resolution

The transaction settlement process in the automatching has been enhanced for matched open customer and vendor transactions. Credit memos are now applied before invoice transactions, reducing the outstanding amount prior to invoice application. This prevents payment amount overflow issues and improves the accuracy and reliability of transaction matching.

Should you experience any issues with a release, please reference case number BCBA-XXX when contacting support.