Amcbanking

This document provides an overview of the releases for the AMC Banking 365 BC extension.

How to Update the App to the Latest Version

 is already installed, you can update it to the latest version from the  Microsoft Dynamics 365 Business Central Admin center. Check for available updates, and if a newer version is available, select 

 and follow the on-screen instructions. After the update is complete, verify that the correct app version is installed and review the 

 for any required configuration changes or post-update actions.

Follow this guide to easily manage and install the latest updates for your AMC Banking 365 BC application. Keeping your software current ensures you have access to the newest features and essential performance improvements.

AMC Banking 365 BC - How to Install Updates

AMC Banking 365 BC - Release 26.0.2.2

AMC Banking 365 BC - Release 26.0.2.1

AMC Banking 365 BC - Release 26.0.2.0

AMC Banking 365 BC - Release 26.0.1.3

AMC Banking 365 BC - Release 26.0.1.2

AMC Banking 365 BC - Release 26.0.1.1

AMC Banking 365 BC - Release 26.0.1.0

AMC Banking 365 BC - Release 26.0.0.8

AMC Banking 365 BC - Release 26.0.0.7

AMC Banking 365 BC - Release 26.0.0.6

AMC Banking 365 BC - Release 26.0.0.5

AMC Banking 365 BC - Release 26.0.0.4

AMC Banking 365 BC - Release 26.0.0.2

Oktober 2025 - First release of AMC Banking 365 BC

AMC Banking 365 BC - Release 26.0.0.0

Improve error handling when calling standard Business Central functions to ensure errors are propagated more clearly to the caller, making it easier to identify where and why an error occurred.

We now show an error message when a call to a standard Business Central function fails.

[BCBA-307] Automatch takes a long time in version 26.0.2.1

, a recursive search was inadvertently introduced. As a result, multiple Payment Reconciliation lines could attempt to apply against the 

, creating conflicting application attempts.

Should you experience any issues with a release, please reference case number 

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

, based on the assumption that all payments were transmitted. This assumption is incorrect.

. AMC has now been updated to follow the standard Business Central behavior.

If a bank account is configured for check printing in Business Central (

 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

 region in BC make currency factor being calculated wrong

 value from the XTL XML file, the value was converted from 

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.

, which specifies that the value should be interpreted using the 

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.

Automatch stops when using TextToAccount mapping

In this scenario, Automatch identified two valid match candidates:

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.

Automatch has been updated to compare the 

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 

 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

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.

Invoice 785.40 (STD BC will stop automatching because invoice exceed net amount,

                              when the invoice is applied to "Applied Payment Entry (Table 1294)"

Credit Memo -1514.03 (Must be first to “make” net amount big enough to handle rest invoices)

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.

[BCBA-287] Move the data upgrade from Installation of BC App to quick guide 

                        and change online manual

Previously, the data upgrade from earlier AMC apps (

) was handled automatically by the system codeunit 

This process ran silently during app installation and across all companies at once.

For environments with large data volumes or multiple companies, this could result in long installation times without any visible progress, making it appear as if the installation had stalled.

To improve transparency and performance, the data upgrade process has been redesigned:

The data upgrade is no longer executed automatically during installation.

The data upgrade step will only appear in the Quick Guide if:

This allows better control and avoids unnecessary processing across all companies.

Follow this guide to successfully execute a data upgrade within the AMC Banking 365 Business Central environment. This process ensures your banking integration is updated and synchronized to the latest version, preventing potential service disruptions.

AMC Banking 365 BC - Data upgrade is required

[BCBA-288] Link XTL data id with Business Central company using CompanyWrite

The Assisted Setup has been updated to use 

[BCBA-272] BankSetupValidate changed to a method

BankSetupValidate changed to a it own method, instead of being part of BankMainList

[BCBA-271] Service URL Availability Check

When opening the AMC Banking setup, the system now verifies whether the configured 

A validation has been introduced for the 

AMC Banking 365 BC - 26.0.0.5 (Hotfix 5) 

[BCBA-234] Bank, signer and code not included when save password

Fixed an issue where the system did not send the 

 option was selected. This caused the error message 

AMC Banking 365 BC - 26.0.0.6 (Hotfix 6) 

[BCBA-233] Documentation about Custom Automatch possibilities in AMC Banking 365 BC

AMC Banking 365 BC - Custom Automatch CU

Bank Account Card / Payment Reconciliation Journal

[BCBA-235] Save reference setup values in manual advice text, 

                        for user to explore data and be used in automatching.

New feature in Reference Rule Setup (Bank Account Card):

[BCBA-239] Review and improvement of Danish label file.

 with spelling corrections and improvements.

[BCBA-279] Make a more specific description in our online manual about the data migration

Created a detailed online manual covering the installation data migration process and defining key data validation checks to ensure accuracy post-migration.

AMC Banking 365 BC - Data upgrade

[BCBA-276] The assisted setup is not running - user does not have sufficient permissions to 

                        change data on the bank export/Import settings.

Resolved an error in the assisted setup caused by missing user permissions to alter bank export/import settings by implementing indirect permission handling, ensuring successful completion of the setup process.

[BCBA-277] Rules for importing FINSTA/CREMUL/DEBMUL to Business Central

Created a detailed online manual covering the import rules and setting for importing bank feeds to Business Central using AMC Banking 365 BC.

AMC Banking 365 BC - Bank feeds import rules 

[BCBA-280] The automatch breaks down with error, if expression contains 

Resolved an issue in the automatch logic where party-related data (such as customer names) containing regex metacharacters (

) caused matching failures, by implementing proper escaping of these characters.

[BCBA-283] Automatch does only every second time created exchangerate diff. lines

Resolved an issue in the automatch process where, with the “create exchange difference lines” setting enabled, exchange difference lines were generated only on every second execution within the Payment Reconciliation Journal.

[BCBA-284] Expand table with value to Malaysia

Some banks in Malaysia require a “Beneficiary bank code” for domestic payments. 

To support this requirement, the Bank Clearing Standard table has been extended with a new value, 

, allowing specification of the relevant bank transfer format.

AMC Banking 365 BC - 26.0.0.8 (Hotfix 8) 

[BCBA-278] Improve performance and reduce upgrade time.

 to improve performance and reduce upgrade time.

[BCBA-274] Service URL inside Setup is ending with "/" 

 because the URL contained double slashes (

[BCBA-275] When a payment journal contains more than one sender bank account, 

                        the system deletes the existing XTL journal and creates a new one.

: when a payment journal included multiple sender bank accounts, the register did not accurately reflect which 

 was created in the web service. This has now been resolved.

AMC Banking 365 BC version 26.0.0.0 is the first release that updates the AMC Banking 365 Fundamentals and AMC Banking 365 Business extensions.

The functionality from AMC Banking 365 Fundamentals and AMC Banking 365 Business Extension has been 

The new extension generally continues to support:

Fix synchronization failure for bank accounts belonging to another 

                        Business Central company

When running the synchronization, either manually or through the Job Queue, the process fails with an error indicating that the bank account does not exist.

This behavior is technically correct because the bank account belongs to a different Business Central company. The import code is missing the required 

 call when accessing the bank account, causing the lookup to be performed in the current company instead of the company where the bank account exists.

If a bank account belongs to another company—for example, COMPANY-B—while synchronization is running for the current company, COMPANY-A, the XTL journals associated with that bank account will not be collected in COMPANY-A’s import log.

Those journals will instead be collected when synchronization is run for COMPANY-B.

In a future release, we should evaluate whether COMPANY-A and COMPANY-B can be processed within the same synchronization job. This could reduce the number of synchronization jobs and calls to XTL.

Check for temporary record is now made, and check for if "Journal Template Name" is empty,

to avoid the error in Transfer difference to account.

Automatch is breaking down when applying to open currency transactions.

When the bank account uses the local currency in which the payment is received, standard Business Central validates 

In our case, we attempted to match against FCY in order to create exchange rate difference lines. However, we populated 

 was still in FCY, causing an incorrect validation.

The AMC Automatch codeunit has been refactored to handle both LCY and FCY amounts for all lines, ensuring that exchange rate difference lines are created correctly.

[BCBA-291] AMC Text-to-Account mapping page

This page will be used when the bank account is configured to use 

replacing the standard Business Central page.

AMC Banking 365 BC - Mapping Text to Accounts

AMC Banking 365 BC - 26.0.0.2 (Hotfix 3) 

[BCBA-225] Easy registration - Quick Guide not update after registration

 to clearly indicate that the process has been completed.

[BCBA-222] Custom Advice removed when changing recipient bank in Payment Journal

The Payment Advice is now correctly updated instead of being deleted.

[BCBA-223] Placeholder %2 in the file name

 field on the Bank Account Card now supports the following placeholders:

These placeholders are automatically replaced when generating the bank file.

[BCBA-212] Double lines in Pay Rec Journal

Fixed an issue where the bank feed was imported twice when importing into 

[BCBA-215] Under/over payment and multiple invoices

 did not correctly match the sum of multiple invoices when the payment was an 

[BCBA-224] When trying to post in a US version, an error message is issued from standard BC

 Microsoft Dynamics 365 Business Central, 

“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:

 sets all three values due to the following behavior in the US localization:

However, when posting the payment journal, another validation is executed by standard Business Central:

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

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.

[BCBA-228] Changes for quick guide to make onboarding easier

To provide a better user experience, several steps in the 

 have been simplified and made more straightforward.

[BCBA-230] Rewrite manual for pages that has changed

[BCBA-229] Links in register are old hyperlink

Updated old hyperlink in the Quick Guide registration page.

AMC Banking 365 BC - 26.0.0.7 (Hotfix 7) 

 Remove postfix when calling licenseserver

License registration is not stored with a postfix, and this caused errors. 

Bank Account / Payment Reconciliation Journal

[BCBA-282] Improvement of the AMC Auto matching

We have improved the bank account auto matching rules in four ways:

1. Improved Auto-Matching of Invoice Numbers

We have enhanced the auto-matching functionality to better handle invoice number variations commonly used in Business Central.

Many companies use prefixes in their invoice numbers, for example:

However, when customers make payments, they often reference only the numeric part:

As a result, the matching process was sometimes unable to identify the correct invoice.

Users can now define prefixes or text strings that should be ignored during matching. For example, by configuring 

 as an omitted word, the system will compare:

as equivalent values, significantly improving the success rate of automatic invoice matching.

We have redesigned the party-related matching functionality by replacing the previous 

Previously, party-related matching required the payer to provide the full customer name to achieve a match.

the payer reference would typically need to contain the complete name to create a party-related match.

You can now define how much of the customer name must match before a party-related match is considered valid. 

this represents approximately 20% of the full name.

Party Match Percentage = 50% (Default setting)

 feature can also be used with party-related matching.

The match percentage is then calculated against the cleaned customer name, improving matching accuracy. Representing approximately 27% of comparison value.

 are ignored during party-related matching and are not taken into account when calculating the match percentage.

Using a very low match percentage may increase the time required for the auto-matching process, as more potential matches must be evaluated.

Party-related percentage matching can be disabled by setting the value to 

We have introduced a new feature that can automatically split lump-sum incoming payments into multiple customer payments.

In some cases, a parent company or central payment office pays invoices on behalf of several customers. These payments are often received as a single amount and only include a list of the invoice numbers being paid.

Previously, such payments required manual processing. With the new functionality, the auto-matching process can:

If the payment amount equals the total of these invoices, the system will automatically split the payment into three separate customer payments and perform the matching accordingly.

Automatic splitting is only performed when all of the following conditions are met:

If any invoice cannot be found, an invoice is missing from the payment reference, or the payment amount does not match the total invoice amount, no automatic splitting will be performed.

4. Copy Auto-Match Rules Between Bank Accounts

To support the new auto-matching features and expanded configuration options, we have introduced the ability to copy auto-match rules from one bank account to another.

This feature makes it easier to maintain consistent matching configurations across multiple bank accounts and reduces the time required to set up new accounts.

When copying auto-match rules, all related settings and configuration options are transferred to the selected bank account, eliminating the need for manual reconfiguration.

AMC Banking 365 BC - Release notes

How to Update the App to the Latest Version

Releases:

August 2026

July 2026

June 2026

Maj 2026

April 2026

Marts 2026

February 2026

January 2026

December 2025

November 2025

Oktober 2025 - First release of AMC Banking 365 BC