RO | EN

New features and extensions

1. Promotions

1.1. New tables

Two new tables have been added to the promotion documents:

1. Promotional action - Trade Account List and 

2. Promotional action - List of trade acc. branches.

Keep in mind that the new table Promotional action - Trade Account List fills in case a list of trader accounts has been declared in the Promotion and contains the trader accounts included in the list.

1.2. New actions for lists

Two actions were also added to the promotion screen, to update the new tables from the corresponding lists. These actions are the Refresh Trade account list and the Refresh Branch list: 

When the user selects the promotion Trade acc. list and/or the Trade acc. branch list one, the question arises ("Do you wish to add the Trade accounts/Branches of the list?") to update the new tables from these lists. If the user selects YES, the detail will be populated, while with NO it will not be created, as is the case for the list of items.

Note: The promotion will be valid for any list created within the promotion at the 3 details, otherwise it will refer to the entries of the list outside of the offer.

2. Miscellaneous improvements

2.1. Login screen values

The default values on the Login screen (Server, Database, User, etc.) are now suggested based on the application folder, like its main screen location. This implementation improves the login suggestions in environments with multiple installations.

The fields suggested in relation to the last login in the same application folder are the database, user, company & branch.

2.2. Context menu – OLAP Designer

In version 5.13.0.0, OLAP the Designer has been extended to support a context menu with the ability to define, for example, a dynamic data source.

By selecting Configuration and Tools > Development & customization tools > Menu configuration, you can create a menu and store it in the ..\CSMenus folder. Its commands may have the following format: bInvoke|esmmstockitem|LOAD|{fItemGID}, where within the {..} the Data source field must be entered.

Then, through the Configuration and Tools > Development & customization tools > OLAP Designer, after selecting the desired OLAP report, go to Edit view > Definition, and the stored menu can be selected as a Context menu. Right-clicking on an OLAP cell in the updated report, it displays the context menu, where the cell value can be sent within an invoke.  

2.3. Connection protocol - Online users

On the connected users screen (menu: Configuration and Tools > Connection to the application server > Online users) it is now possible, by adding a new column, to view the Protocol information with which a user is logged-in (e.g. .Net removing / gRPC). 

2.4. Other improvements

• ESCommand Monitor: New buttons were added with the "Select all" and "Deselect all" options in the ESCommand Monitor, to prevent excessive list navigation when the user wants to select the entire record.

3. Enhancements for the Romanian version

3.1. New VAT rates

(1) With the introduction of the new VAT rates on August 1, 2025, it was necessary to introduce four new parameters in the Accounting System section related to VAT on payment - TVAI.

For the 21% rate, the codes:

• VAT_PAYMENT_ITEM_SALES_STANDARD_CATEGORY

• VAT_PAYMENT_ITEM_PURCHASES_STANDARD_CATEGORY
  with the name:
  VAT on payment regime: VAT on payment Item (standard rate starting August 1, 2025).

For the 11% rate, the codes:

• VAT_PAYMENT_ITEM_SALES_REDUCED_CATEGORY

• VAT_PAYMENT_ITEM_PURCHASES_REDUCED_CATEGORY
  with the name:
  VAT on payment regime: VAT on payment Item (reduced rate starting August 1, 2025).

(2) To cover all cases related to VAT on payment, the following functionalities have been extended:

1. Scroller through documents with unpaid TVAI on DPV and DPE.

2. Scroller Documents in queue.

3. Reverse charge VAT automation.

4. Business Rule applicable to BO/CEC payment/collection documents for automatic completion of invoices from the initial DPE.

3.2. Fiscal Declarations

3.2.1. Updates for the D406 - SAF-T declaration

(1) According to the SAF-T nomenclature, ANAF has introduced four new codes:

• NORMA36 for insurance and/or reinsurance brokerage companies that apply Regulation No. 36/2015 of the Financial Supervisory Authority (ASF).

• NORMA14 for companies in the private pension sector that apply to IFRS (Norm 14/2015) of the Financial Supervisory Authority (ASF).

• NGO for non-profit legal entities (NGOs), according to OMFP No. 3103/2017.

• ONGE for non-profit legal entities (NGOs) according to OMFP No. 3103/2017 - legal entities with a VAT code for economic activity.

These will be found in the Tax Accounting Basis list in the SBS_SERVICES_ORGANIZATIONID parameter in the SBS Services section (menu: Configuration and Tools > Customization… > General > Company Parameters). 

(2) The quarterly SAF-T declaration for small companies with VAT on payment requires an adjustment to the quarterly run of step 1 - <A10>Prepare/Update tax data<A11>, compared to the monthly run as originally implemented. 

In this step, the tax codes are populated in the SAF-T GL Entries scroller, and each time it is run per month, the data from the previous month is lost, so that this scroller did not contain all the tax codes for the entire quarterly period, but only those for the last month run. 

Now that all tax codes for the quarter have been saved, the data resulting from the preparation process is complete.

(3) Another important improvement for SAF-T is the possibility to consider documents without SAF-T document type code. There are cases where documents do not need to be declared in SAF-T as transactions but are only of interest for their accounting records. Until now, we were required to declare a SAF-T document type code, even if there was no corresponding one. For this purpose, a new Attribute of a document has been added: CONCERNS-SAFT (with the description: To participate in SAF-T). Thus, from now on, when preparing information for SAF-T, documents with the SAF-T document type code field filled in or, if empty, with the CONCERNS-SAFT attribute set will be considered.

This functionality will be used in the future to include non-commercial documents in SAF-T that involve certain tax codes, such as withholding tax for non-residents.

3.2.2. Updates to the D300 declaration

(1) The new declaration, related to the requirements that came up with the new VAT rates of 11% and 21% starting August 1, 2025, means keeping the old D300 declaration for the previous months and making a new one that lets you settle VAT starting August 2025. Thus, the tables necessary for calculating the new declaration have been expanded, a new type of declaration and its presentation form have been created, automation has been implemented to perform the necessary calculations, and a separate entry has been added to the menu:

Accounting > Financial declarations > Data calculation... > Calculate data Declaration 300 (2025). These improvements are specified below. 

(2) The new declaration will have a new type with the code ES.D300_2025, which will be assigned to the new form. This type is entered in Configuration and Tools > Customization… > Financial Declarations > Declaration types.

(3) Given the new form of the D300 declaration in which the new VAT rates must be reported, additional fields are required in the database for the new VAT rates. Thus, Table ESFIFinancialDeclaration has been extended by 14 columns to cover the new rows required in the new form.

(4) The current form ESFIFinancialDeclaration_D300_DEF, which was used for reports prior to August when the new VAT rates were introduced, has been duplicated, renamed to ESFIFinancialDeclaration_D300_2025_DEF and completed in accordance with the new reporting requirements.

3.2.3. Updates to the D394 declaration

(1) Due to the introduction of new VAT rates and the D394 declaration regarding internal transactions, it must be updated.
This has been done to cover all the requirements set out in the new ANAF requirements regarding the reporting of transactions with the new VAT rates so that the .xml file resulting from the automated calculation passes the new validator. The form also had to be modified to accommodate the new requirements.

(2) Also, to facilitate the verification of the accuracy of the information prepared for the D394 declaration, starting with this version, you have access to a Verification Report for each section of the declaration. After you have made the calculations for the desired declaration, in the Declaration Management scroller you have a Reporting button that provides you with a list of the sections of the declaration that you can view for verification. 

3.3. Various improvements in the e-Factura subsystem

Sending (outbound) and receiving (inbound) invoices via e-Factura has been improved in several ways.

(1) Inbound e-Factura - Multiple invoice correlation:
When you click the Correlate button in the E-invoice Received Invoice Management scroller (in the Purchases menu), you can already select different document types in the Document Type field. From now on, in the Correlation Document field, it will be possible to select multiple invoices.

(2) Outbound e-Factura - Additional bank accounts:
Following customer requests, we have included the option to add multiple bank accounts in IBAN format for invoices sent in e-Invoice. This is done by changing the value of a newly introduced parameter - E_FACTURA_BankAccount_Source. The values mean:

• 0 (default): only the IBAN for the main account.

• 1: IBANs related to accounts that have checked Flag 1.

• 2: IBANs related to accounts that have checked Flag 2.

• 3: IBANs related to accounts that have checked Flag 3.
  
  

(3) Outbound e-Factura - upload method changed:
Until now sending an invoice to ANAF required two calls in the SBS API - one to create the invoice, second to upload it to ANAF. In a few cases between the two steps an error may arise that leaves the system in an unwanted state. To solve this SBS offer now another API call sendInvoice that ensures the process in a single step, clarifying the state of the process. With this enhancement we also changed the upload automation in EBS-RO to use this new API call.

(4) Outbound e-Factura - Remove condition for checking the e-Invoice check on items:
Due to the fact that there may be cases where the sales invoice contains only special accounts and no items, it is necessary to remove the condition that items must have eInvoicing = 1 (condition for selecting invoices in the sales invoice scroller to be sent to ANAF e-Factura), so that these invoices also appear in the scroller presented in the menu Sales > e-Invoice - Management of sent invoices.

(5) e-Factura outbound - Transmission of invoices issued in EURO:
According to the legislation, invoices can be issued in another currency regardless of the type of transaction (goods or services) if VAT is declared in RON. How the ISO code of the document currency is transmitted in field BT-5: field BT-6 must be expressed in RON; the same applies to BT-111, except that it is only filled in if BT-5 is different from RON; the rest of the fields - BT-106, BT-109BT-110, BT-112, BT-115, BT-116, BT-117, BT-131, BT-146, BT-148, and BT-149 will have the values corresponding to the transaction currency. The meaning of these fields can be found on the e-Invoice instructions page on our support website.

(6) A new parameter has been introduced to select the source of the maturity field. (BT-9) - E_FACTURA_DueDate_Source (e-Factura - Due Date Source).

(7) A new parameter has been introduced for adding the exemption reason field. (BT-120) - E_FACTURA_TaxExemptionReason_Source (e-Factura - Tax Exemption Reason source).

8) The mappings of the BT-7 and BT-72 fields have been modified so that the delivery date is taken first, followed by the document date. In a future version, other date fields from the document header will also be available for use.

3.4. New print forms

This version comes with a bunch of standard print forms, so if you don't have any special customization needs, you can start using them right away.

• Supplier order (EN).

• Consumption receipt.

• Cash receipt.

• Customer order confirmation.

• Customer order.

• Transfer note.

• Payment order.

• Sales invoice (EN).

• Delivery Note (EN).

Over time, we will cover all common cases with standard forms to shorten the implementation time of our EBS-RO suit as much as possible.

You can find them all in the application folder, subfolder: ESPrintForms, grouped into several functional subfolders.      

Attention: The print form setting is made for each series separately.

Select the desired form from the Print form list for the selected series. In order to be selected, the desired forms from ESPrintForms will be manually copied to the CSPrintForms folder.
Two or more print forms can be selected, separated by commas. If there are more than one, the same number of elements must appear in the fields Printing device, i.e. the device/printer (instead of setting a specific one, you can enter the value def – default or ask - which offers the possibility of selecting the desired one at the time of printing), and the Set Commands field - where the call mode for print commands must appear the same number of times - for example, WinPrint2. 

3.5. Reports

3.5.1. Fixed Assets Grants scroller changes 

1090716

The scroller, accessible from the menu Accounting > Fixed Assets List > Information > Fixed Asset Grants  has been extended by two more columns:

1. Value of  depreciated grants up to date - calculated as the sum of all grants amortizations up to date (including  the initial depreciated balance of the grant). The calculation of this depreciated grant should not consider the time interval selected for analysis but should refer to the reference date.

2. Remaining grant amount to be depreciated - calculated as the difference between:
   
   Grant value  - Grant depreciated value up to date

The grant amount will be stored on the Fixed Asset card in the field Amount Grant (SponsorshipValue), and its depreciation will be calculated in accordance with the life cycle of the fixed asset.

3.5.2. Order traceability report

This improvement aims to generate a report indicating the status of certain documents in the sales flow.

The report aims to highlight the following information:

• What orders were issued during the selected period?
  Regardless of whether and when they were delivered/invoiced.
  
  

• What notices were issued during the selected period?
  Regardless of the order date and/or whether they were invoiced.
  
  

• Which invoices were issued during the selected period?
  Regardless of the order/notification date.

Access the menu Sales > Sales orders > Orders/Reservations. In the vertical tab Related reports you’ll find the Order traceability report. 

3.5.3. Justification of Stock Item Balance Columns

To facilitate the verification of the results of the inventory write-off, a report is required detailing the operations displayed in a specific column of the inventory balance sheet.

There is a standard report with the same name - menu: Inventory > Trial balances > Justification of trial balance columns - However, it is structured in levels, does not have sufficient parameters, and has conditions for excluding canceled documents. Also, this report does not allow exporting to Excel to the item and line level.

The new report has the following parameters:

• Period

• Item

• Document type

• Accounting category item

• Branch

The report displays only items with stock and where one of the columns Debit amount, Credit amount, Debit value, Credit value has a value <> 0 - meaning that all transactions that have a quantitative, value-based, or quantitative-value-based effect on inventory are displayed. This report can also be exported to Excel with all the information related to these transactions. It can be accessed in the menu: Inventory > Items - Related Reports > Justification of Stock Item Balance Columns.

3.6. Other improvements

3.6.1. Parameter for POS payments with VIVA Wallet

An additional configuration parameter has been introduced for making payments via POS VIVA Wallet (which until now only worked for the Greek installation - ESPOS_INSTALATION, to which the value Viva is assigned). 

3.6.2. Update scroller SAF-T Invoices - Line Account ID on Fixed Assets sales

In the SAF-T Invoices scroller, in the Line Account ID field, for Fixed Asset sales, it is necessary to use a different accounting category code than for inventory sales (currently, Code 2 is used for both). The change means that for fixed asset sales, Code 4 Accounting Category Revenue 7583 will be used.

Bug fixes

4. Core Fixes

• Resolved an error that would occur when editing a current promotion from a gift line: “Object reference not set to an instance of an object”.
  
  

• Fixed the incorrect behavior of erroneous display of promotion items for free products in a discount promotion. In each promotion, the system applied the 1st item-gift.
  
  

• Fixed the erroneous behavior in document creation, where a document belonging to an inactive document type could be registered.
  
  

• Resolved an error that would occur while deleting document series, with the message "Failed to run the entry delete process. For further information consult the Technical Details tab of this message”.

4.2. Attachments

• Resolved an error that would occur when opening a pdf from the Courier receipt list view, with the message "Input data is not recognized as valid pdf".

4.3. Accounting

• Resolved an error that would occur when calculating the ledger chart of a document via the accounting model.

4.4. Orders - Reservations

• Resolved a document line discount error with the message: “Net value in line {0} of item {1} has not been calculated correctly”.

4.5. Price lists

• Fixed an issue that caused items to appear within promotions they did not belong to, after applying the “Add/remove columns” action that cleared all filters.
  
  

• Fixed an issue with the wrong application of invoicing policy in the Retail application, which would occur when lines were collapsed.

4.6. Miscellaneous

• Resolved a problem where a document was printed without an error message, even though a printer was not set in the document series.
  
  

• Fixed the "Created by" parameter of the product view (menu: Inventory > Stock entries > Item movements), which would not apply filters on the view’s results.
  
  

• Fixed the "Created by" parameter of the product view Orders (menu: Purchases & Procurement > Purchase orders > Purchase Order List), which would not return unique values. 

Related cases:

PS-96823, PS-105448, PS-107926, PS-106232, PS-107596, PS-109190, PS-110724, ΥΠΘ_SUP-209749, PS-111583, PS-111718, PS-113140, PS-113088, PS-115708, PS-113023, PS-114646, PS-115220, PS-115630, PS-115976, PS-116321, PS-116780, PS-117374, PS-106747, PS-108446, PS-113841, PS-115517, PS-112891, PS-116222, PS-116653, PS-108551, PS-107615, PS-112586, PS-113502, PS-100509, PS-102388, PS-111059, PS-112822, PS-113178, PS-114456, PS-111900, PS-109812, PS-112921, PS-115353, PS-111606, PS-112872, PS-112938, PS-114967, PS-116930, PS-116509, PS-116261

5. Bug fixes for the Romanian version

• SAF-T - The Prepare Tax Information process has been refined in terms of the conditions under which it runs regarding tax codes and transaction types.
  
  

• The method of completing the VAT regime on sales documents has been corrected by means of a business rule that starts with the VAT characteristics of the company and then those of the trading partner.
  
  

• Automatic updating of the Business Partner’s TRN In the case of international partners, the alphanumeric code does not need to be pre-filtered; only Romanian codes are required to consist solely of digits.
  
  

• Several cases were resolved in which, although we had an error in SBS that was not displayed in EBS. This could happen when attempting to connect with expired authorization when sending/reading from SBS.
  
  

• e-Transport bug fixed when the document number is not forwarded in SBS.
  
  

• Fixed a bug for e-Factura outbound doubling the PaymentMeans field. 

• A calculation error has been corrected for D394 - summary of domestic reverse charge transactions. For reverse charge transactions based on Art. 331 and the nature of the product completed in Table 10 - Type C, we had a difference of 1 leu between the summary value and the calculated value, both on a base and VAT.
  
  

• An error in the document TCM has been corrected for a Fixed Asset transfer before it has been processed in a closing year valuation. 

Related cases:

1097193, 1097822, 1100413, 1100833, 2000091, 2003787, 1099179, 1100346