Minor Update 2026.10/1 for SMART Accounting solution

minor update en 1200x628 1

This partial update addresses issues identified after the 2026.10 release. It also includes tasks related to legislative changes and improvements to overall system performance and stability.

image
  1. The logic for recognizing counterparties during bank statement import has been unified. During import, after the amount sign is determined, a check is now performed automatically according to the logic of the “Validate” function, which ensures that the counterparty, account type, account number, and document type are determined correctly.
  2. The logic for generating the iFobs UAH XML and iFobs UAH TXT export files has been updated. For recipients with the RNRCT (individual entrepreneur’s tax ID) or USRC (legal entity’s EDRPOU code) identifier type, the CORRCLIENTTYPE field is no longer populated. The existing population logic has been retained for other identifier types.
  3. The “Control of VAT invoice when posting an adjusting credit note” setting has been added to the “VAT Setup (Ukraine)” page. It allows you to control whether a posted VAT invoice exists for the invoice being adjusted. If the setting is enabled and a posted or registered VAT invoice exists for the invoice, posting an adjusting credit note is prohibited. If the setting is disabled, an adjusting credit note can be posted without changes to the related VAT invoices.
  4. The Rounding factor field has been added to the financial report row definition. It allows calculated values to be rounded at the individual row level before they are used in subsequent calculations. The rounded row value is used in dependent formulas and passed to regulatory reports. If both a row-level and a column-level Rounding factor are specified, they are applied sequentially: the row factor is applied to the calculated value first, and then the column factor is used to present and scale the value. The column-level Rounding factor does not change the base value that is used in subsequent calculations or passed to regulatory reports.
  5. The generation of XML files in Regulatory reports has been improved: values configured with the Decimal data type in XML element rows are now exported with their decimal places preserved.
  6. The “Payment purpose” field has been added to the “Financial journals” page. The field is hidden by default and can be displayed via Page personalization.
  7. The preview mode in the “Exchange rate adjustment” report has been fixed. The selected value of the “Dimension accounting” parameter is now taken into account during preview, ensuring that the preview results match the actual posting of transactions.
  8. An error in the Inventory write-off act has been fixed, which prevented the “Split lines by application” action from being performed if a line was split into several inventory ledger entries.
  9. An error has been fixed where the value of the “FA number” field was not transferred when a correction was created for a posted Inventory write-off act with the “Transfer to FA” type by using the “Copy document” action with the “Copy as correction” option. The “FA number” is now transferred to the new document together with the other line values.
  10. The logic for canceling FA ledger entries created by an Inventory write-off act has been changed. Such operations can now be corrected only via a write-off act with the correction flag.
  11. An error in the depreciation calculation for low-value fixed assets (Low-Value FAs) has been fixed for the case where the depreciation start date coincides with the calculation end date. Depreciation is now calculated correctly in such cases.
  12. The additional filters in the Turnover Sheet and Turnover Sheet (quantity accounting) reports have been fixed. Previously, refreshing the statement could fail after the “Type = Inventory” filter was selected. The statements are now generated according to the specified filters.
mail
Cookies

We use cookies to improve your web experience, display personalized content and analyze traffic. By clicking «Accept All», you agree to their use. To manage your settings, click Settings. Learn more about the use of cookies in the privacy policy.

Functional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Statistics
The technical storage or access that is used exclusively for statistical purposes
Analytics
Analytical purposes are used to measure traffic and optimize content.