← All releases

Version 1.5.1.0

Released November 4, 2026

6 new features 4 fixes

What's new

AC Solution - Core

General features

AC Feature management v2 – subscription licensing through the License Hub

ASL features are now enabled only when they are switched on in the feature setup and the environment's subscription covers them. Nothing changes until the environment is registered: all features keep following the local setup.

  • New forms License parameters and License status (System administration > Setup). Enter the License Hub address and activation key there to register the environment, check the subscription status of every feature and synchronize manually. An offline license file can also be imported there.

  • The license is synchronized daily by a batch job, which is retried automatically if it fails.

  • The feature setup forms now show the package, the subscription status, the paid-until date and the end date of each feature. Adding a feature that the subscription does not cover gives a warning.

  • System administrators get Action center notifications when the license expires within 7 days, during a grace period, when the License Hub cannot be reached and when licensed features are switched off.

  • Once the environment is registered, licensed features are switched off if there is no valid license (for example, it has expired or was rejected). Features that are not licensed keep following the local setup.

  • Scheduled integration jobs and e-invoice queues skip their work while the feature is off. Queued messages and documents keep their status and are processed once the feature is on again.

  • New security roles: License administrator (AslCore_ACLicenseAdministrator) and License remote control (AslCore_ACLicenseRemoteControl).

  • Available in English, Czech, Slovak and German.

After installation, run a database synchronization.

Feature management v2

AC Solution - Core · General features

AC Feature management v2 – subscription licensing through the License Hub

ASL features are now enabled only when they are switched on in the feature setup and the environment's subscription covers them. Nothing changes until the environment is registered: all features keep following the local setup.

  • New forms License parameters and License status (System administration > Setup). Enter the License Hub address and activation key there to register the environment, check the subscription status of every feature and synchronize manually. An offline license file can also be imported there.

  • The license is synchronized daily by a batch job, which is retried automatically if it fails.

  • The feature setup forms now show the package, the subscription status, the paid-until date and the end date of each feature. Adding a feature that the subscription does not cover gives a warning.

  • System administrators get Action center notifications when the license expires within 7 days, during a grace period, when the License Hub cannot be reached and when licensed features are switched off.

  • Once the environment is registered, licensed features are switched off if there is no valid license (for example, it has expired or was rejected). Features that are not licensed keep following the local setup.

  • Scheduled integration jobs and e-invoice queues skip their work while the feature is off. Queued messages and documents keep their status and are processed once the feature is on again.

  • New security roles: License administrator (AslCore_ACLicenseAdministrator) and License remote control (AslCore_ACLicenseRemoteControl).

  • Available in English, Czech, Slovak and German.

After installation, run a database synchronization.

Parameter Aricoma solutions which is responsible for managing ASL packages on legal entities has been added into Legal Entity data entity.

Feature management - ASL features parameter - Data entity modification

AC Solution - Core · General features

Parameter Aricoma solutions which is responsible for managing ASL packages on legal entities has been added into Legal Entity data entity.

AC Solution - Electronic Documents Exchange

eInvoice

This feature allows usage of OAuth2 of Flowis electronic provider. (New setup needed: Flowis X-account-ID needs to be specified as a supplementary header on Web application form in FO)

Electronic invoicing - Export core - Electronic invoicing - OAuth2 feature

AC Solution - Electronic Documents Exchange · eInvoice

This feature allows usage of OAuth2 of Flowis electronic provider. (New setup needed: Flowis X-account-ID needs to be specified as a supplementary header on Web application form in FO)

AC Solution - Finance SK

Finance SK - general

Release notes: SK VAT control statement (KV DPH), faster settled-invoice dates

Summary

The SK VAT control statement report now runs much faster. Previously, it looked up the settled-invoice dates (transaction date, VAT due date, vendor VAT date, invoice date, document date) one record at a time while the report ran. SQL Server now computes these dates inside the tax transaction view, and the new ER mapping version reads them from there.

Changes

X++ (AslFinanceSK, project AslFinSK - LeanRootsVAT)

  • View extension TaxTransDeclarationDetailsNoAdjustmentView.AslFinSKExtension: adds 5 computed date columns, controlled by configuration key AslFinSk_FinanceSK:

  - AslFinSK_SettledInvoiceTransDate

  - AslFinSK_SettledInvoiceVatDueDate_W

  - AslFinSK_SettledInvoiceVendorVATDate

  - AslFinSK_SettledInvoiceInvoiceDate

  - AslFinSK_SettledInvoiceDocumentDate

  • New class AslFinSK_TaxTransSettledDatesComputedColumn: builds the SQL for these columns.

  - Checks the dates in the same order as the standard Microsoft SettledInvoice* columns, so the results are identical.

  - Looks up each settled transaction once per row (OUTER APPLY). Rows without a settlement skip the lookup.

  - Checks configuration keys with isConfigurationkeyEnabled(configurationKeyNum(...)): Project, CzCustVendAdvanceInvoices, InventTransferOrders.

  - Builds the SQL through the SysComputedColumn API (comparisonField, equalExpression, and, max, comparisonLiteral). Table and field names come from DictTable/DictField, so no SQL names are hardcoded.

  • New class TaxTransDeclarationDetailsNoAdjustmentViewAslFinSK_Extension: holds the view methods for the computed columns.

  • Model descriptor AslFinanceSK: adds a reference to the Project package.

  • New resource AslFinSK_ERTaxDeclarationModelMapping_LITE_SK_v171_344_7_2: contains the new ER mapping version.

ER configuration

  • Asl Tax declaration model mapping LITE (SK) 171.344.7.2 (based on 171.344.7.1):

  - 40 aggregations now read the new AslFinSK_* view columns instead of the slow lookups.

  - Aggregation names are unchanged, so the format needs no changes.

  - 5 view fields are added to the selected table items.

Tooling (er-configs repo)

  • scripts/tax-declaration-sk/gen-sk-kh-settled-dates.ps1: generates mapping 7.2 from 7.1.

  • scripts/tax-declaration-sk/measure-sk-kh-settled-dates.ps1 and measure-sk-kh-settled-dates-candidates.sql: measure performance and compare results between the old and new columns.

  • docs/sk-vat-performance-analysis.md: performance analysis and the evaluated variants.

Performance

  • Production data copy (company s128): 63.4 s → 21.9 s for the KV DPH data-source evaluation. Measured with a prototype of the same approach (columns computed in the view).

  • Development environment: a full ER control statement run went from about 3.5 min to about 1.5 min.

The final implementation has not been measured on production yet. Run measure-sk-kh-settled-dates.ps1 after deployment.

Verification

  • Full build of AslFinanceSK: 0 errors. DB sync of TaxTransDeclarationDetailsNoAdjustmentView completed.

  • Test data (company fsk, period 2026-06: 5,032 view rows, 1,404 of them with a settlement): the 5 new columns match the standard Microsoft SettledInvoice* columns, with 0 differences.

Deployment

  1. Deploy the AslFinanceSK package and run the database sync. The view must contain the ASLFINSK_* columns.

  2. Import ER mapping 171.344.7.2 and set it as the default mapping.

Do not import the mapping before step 1. Without the new view columns it fails.

Optimization of ER configurations and Views for generating the VAT control statement for Slovakia

AC Solution - Finance SK · Finance SK - general

Release notes: SK VAT control statement (KV DPH), faster settled-invoice dates

Summary

The SK VAT control statement report now runs much faster. Previously, it looked up the settled-invoice dates (transaction date, VAT due date, vendor VAT date, invoice date, document date) one record at a time while the report ran. SQL Server now computes these dates inside the tax transaction view, and the new ER mapping version reads them from there.

Changes

X++ (AslFinanceSK, project AslFinSK - LeanRootsVAT)

  • View extension TaxTransDeclarationDetailsNoAdjustmentView.AslFinSKExtension: adds 5 computed date columns, controlled by configuration key AslFinSk_FinanceSK:

  - AslFinSK_SettledInvoiceTransDate

  - AslFinSK_SettledInvoiceVatDueDate_W

  - AslFinSK_SettledInvoiceVendorVATDate

  - AslFinSK_SettledInvoiceInvoiceDate

  - AslFinSK_SettledInvoiceDocumentDate

  • New class AslFinSK_TaxTransSettledDatesComputedColumn: builds the SQL for these columns.

  - Checks the dates in the same order as the standard Microsoft SettledInvoice* columns, so the results are identical.

  - Looks up each settled transaction once per row (OUTER APPLY). Rows without a settlement skip the lookup.

  - Checks configuration keys with isConfigurationkeyEnabled(configurationKeyNum(...)): Project, CzCustVendAdvanceInvoices, InventTransferOrders.

  - Builds the SQL through the SysComputedColumn API (comparisonField, equalExpression, and, max, comparisonLiteral). Table and field names come from DictTable/DictField, so no SQL names are hardcoded.

  • New class TaxTransDeclarationDetailsNoAdjustmentViewAslFinSK_Extension: holds the view methods for the computed columns.

  • Model descriptor AslFinanceSK: adds a reference to the Project package.

  • New resource AslFinSK_ERTaxDeclarationModelMapping_LITE_SK_v171_344_7_2: contains the new ER mapping version.

ER configuration

  • Asl Tax declaration model mapping LITE (SK) 171.344.7.2 (based on 171.344.7.1):

  - 40 aggregations now read the new AslFinSK_* view columns instead of the slow lookups.

  - Aggregation names are unchanged, so the format needs no changes.

  - 5 view fields are added to the selected table items.

Tooling (er-configs repo)

  • scripts/tax-declaration-sk/gen-sk-kh-settled-dates.ps1: generates mapping 7.2 from 7.1.

  • scripts/tax-declaration-sk/measure-sk-kh-settled-dates.ps1 and measure-sk-kh-settled-dates-candidates.sql: measure performance and compare results between the old and new columns.

  • docs/sk-vat-performance-analysis.md: performance analysis and the evaluated variants.

Performance

  • Production data copy (company s128): 63.4 s → 21.9 s for the KV DPH data-source evaluation. Measured with a prototype of the same approach (columns computed in the view).

  • Development environment: a full ER control statement run went from about 3.5 min to about 1.5 min.

The final implementation has not been measured on production yet. Run measure-sk-kh-settled-dates.ps1 after deployment.

Verification

  • Full build of AslFinanceSK: 0 errors. DB sync of TaxTransDeclarationDetailsNoAdjustmentView completed.

  • Test data (company fsk, period 2026-06: 5,032 view rows, 1,404 of them with a settlement): the 5 new columns match the standard Microsoft SettledInvoice* columns, with 0 differences.

Deployment

  1. Deploy the AslFinanceSK package and run the database sync. The view must contain the ASLFINSK_* columns.

  2. Import ER mapping 171.344.7.2 and set it as the default mapping.

Do not import the mapping before step 1. Without the new view columns it fails.

VAT reduction coefficient SK

This feature allows you to post and subsequently report a reduction in the right to an input deduction for VAT transactions using a coefficient in accordance with § 50 of Act No. 222/2004 of the Collection of Laws.

The functionality differentiates between regular input tax credits and input tax credits for fixed assets for monthly reductions using a coefficient and yearly recalculations.

VAT reduction coefficient SK

AC Solution - Finance SK · VAT reduction coefficient SK

This feature allows you to post and subsequently report a reduction in the right to an input deduction for VAT transactions using a coefficient in accordance with § 50 of Act No. 222/2004 of the Collection of Laws.

The functionality differentiates between regular input tax credits and input tax credits for fixed assets for monthly reductions using a coefficient and yearly recalculations.

Release notes – AslFinanceSK: VAT reduction coefficient – use tax

New features

  • The VAT reduction coefficient field (AslFinSK_VATReductionCoefficientType) on sales tax codes has two new values:

  - Coefficient VAT use tax - standard

  - Coefficient VAT use tax - fixed assets

  • The existing values have been renamed:

  - VAT reduction - standard → Coefficient VAT receivable - standard

  - VAT reduction - fixed assets → Coefficient VAT receivable - fixed assets

  • The field help text now explains what the field does.

Behavior changes

  • During the monthly sales tax settlement, the VAT reduction is grouped by the coefficient type of the sales tax code and by the sales tax rate. Each of the four types creates up to 3 Sales tax receivable transactions, one per tax rate.

  • The reduction is posted with a sales tax code from the sales tax settlement period. That code must have the same tax rate and the same VAT reduction coefficient type as the reduced transactions.

  - The standard types use the Sales tax code – end of month field.

  - The fixed assets types use the FA - Sales tax code – end of month field.

  • The yearly coefficient recalculation works the same way, using the end of year fields. Reductions already posted monthly and yearly are taken into account separately for each type.

  • Transactions of the sales tax codes selected on the settlement period for posting the reduction are not included in the amount being reduced.

  • The warning about two sales tax codes with the same rate in one field now appears only when they also have the same coefficient type. The "no sales tax code with the rate … is selected" error now also states the coefficient type.

Required setup changes

  • Set the correct VAT reduction coefficient type on the sales tax codes used for posting the reduction on the settlement periods. Otherwise the monthly settlement fails with an error about a missing sales tax code. The yearly recalculation would also ignore reductions posted earlier.

  • For use tax, create separate reduction sales tax codes for each tax rate, with the Coefficient VAT use tax - … type, and add them to the relevant fields of the settlement period.

New VAT use tax types

AC Solution - Finance SK · VAT reduction coefficient SK

Release notes – AslFinanceSK: VAT reduction coefficient – use tax

New features

  • The VAT reduction coefficient field (AslFinSK_VATReductionCoefficientType) on sales tax codes has two new values:

  - Coefficient VAT use tax - standard

  - Coefficient VAT use tax - fixed assets

  • The existing values have been renamed:

  - VAT reduction - standard → Coefficient VAT receivable - standard

  - VAT reduction - fixed assets → Coefficient VAT receivable - fixed assets

  • The field help text now explains what the field does.

Behavior changes

  • During the monthly sales tax settlement, the VAT reduction is grouped by the coefficient type of the sales tax code and by the sales tax rate. Each of the four types creates up to 3 Sales tax receivable transactions, one per tax rate.

  • The reduction is posted with a sales tax code from the sales tax settlement period. That code must have the same tax rate and the same VAT reduction coefficient type as the reduced transactions.

  - The standard types use the Sales tax code – end of month field.

  - The fixed assets types use the FA - Sales tax code – end of month field.

  • The yearly coefficient recalculation works the same way, using the end of year fields. Reductions already posted monthly and yearly are taken into account separately for each type.

  • Transactions of the sales tax codes selected on the settlement period for posting the reduction are not included in the amount being reduced.

  • The warning about two sales tax codes with the same rate in one field now appears only when they also have the same coefficient type. The "no sales tax code with the rate … is selected" error now also states the coefficient type.

Required setup changes

  • Set the correct VAT reduction coefficient type on the sales tax codes used for posting the reduction on the settlement periods. Otherwise the monthly settlement fails with an error about a missing sales tax code. The yearly recalculation would also ignore reductions posted earlier.

  • For use tax, create separate reduction sales tax codes for each tax rate, with the Coefficient VAT use tax - … type, and add them to the relevant fields of the settlement period.

Bug fixes

AC Solution - Bank Communication

Bank statements

oprava tagů v MT ČS

Not correctly calculated final balance

AC Solution - Bank Communication · Bank statements

oprava tagů v MT ČS

Payment reference is in some cases, where the transaction type is 030 = Cross-border payments is transmitted with the following format "VS/xx/SS//KS/", that is not taken into account during filling of the Reference No. field on bank statement line.

Not correctly recognized payment reference

AC Solution - Bank Communication · Bank statements

Payment reference is in some cases, where the transaction type is 030 = Cross-border payments is transmitted with the following format "VS/xx/SS//KS/", that is not taken into account during filling of the Reference No. field on bank statement line.

Bank statement import – leading zeros in reference number, ČSOB MT940 (CZ) fixes

Asl ABR Bank statement Mapping to destination – version 3.15.6

  • Fix: Leading zeros in the payment reference (variable symbol) are kept when the statement is imported.

  Previously, every leading zero was removed (000123456 was imported as 123456).

  Now only a reference that is exactly 0 is changed to an empty value.

  • Impact: This mapping is shared, so the change applies to all bank statement formats (MT940, Camt.053, ABO, CSV).

  This includes Camt.053 Commerzbank (CZ), which stripped leading zeros.

Asl ABR MT940 Format ČSOB (CZ) – version 3.15.1.6

  • New: For other transactions (type 040), the variable symbol from subfield ?20 (VS:…) is now imported as the reference number, with leading zeros kept.

  Previously the reference number was empty for these transactions (for example, ATM cash deposits and card transactions).

  • Fix: Foreign payments: the original amount from :61: /OCMT/ is read correctly when the bank adds the conversion exchange rate after it.

  Previously the import could fail with an error.

  • Fix: Line endings in :61: are handled for CRLF, CR and LF.

  Previously a trailing carriage return could stay at the end of the bank transaction reference (Entry reference).

Deployment

Import Asl ABR Bank statement Mapping to destination 3.15.6 first, then Asl ABR MT940 Format ČSOB (CZ) 3.15.1.6.

The string is trimmed of leading zeros

AC Solution - Bank Communication · Bank statements

Bank statement import – leading zeros in reference number, ČSOB MT940 (CZ) fixes

Asl ABR Bank statement Mapping to destination – version 3.15.6

  • Fix: Leading zeros in the payment reference (variable symbol) are kept when the statement is imported.

  Previously, every leading zero was removed (000123456 was imported as 123456).

  Now only a reference that is exactly 0 is changed to an empty value.

  • Impact: This mapping is shared, so the change applies to all bank statement formats (MT940, Camt.053, ABO, CSV).

  This includes Camt.053 Commerzbank (CZ), which stripped leading zeros.

Asl ABR MT940 Format ČSOB (CZ) – version 3.15.1.6

  • New: For other transactions (type 040), the variable symbol from subfield ?20 (VS:…) is now imported as the reference number, with leading zeros kept.

  Previously the reference number was empty for these transactions (for example, ATM cash deposits and card transactions).

  • Fix: Foreign payments: the original amount from :61: /OCMT/ is read correctly when the bank adds the conversion exchange rate after it.

  Previously the import could fail with an error.

  • Fix: Line endings in :61: are handled for CRLF, CR and LF.

  Previously a trailing carriage return could stay at the end of the bank transaction reference (Entry reference).

Deployment

Import Asl ABR Bank statement Mapping to destination 3.15.6 first, then Asl ABR MT940 Format ČSOB (CZ) 3.15.1.6.

AC Solution - Set Off

Set off transactions

Unmultiplyed lines in printed set off

Multiplying lines while printing posted setoffs

AC Solution - Set Off · Set off transactions

Unmultiplyed lines in printed set off