RO | EN

New features and extensions

1. Scheduling PDF printing

1.1. New automation action - “Cancel pending PDF prints”

In the case of scheduling tasks that run PDF printing using automations, it’s not possible to run the existing “Cancel PDF printing” action (Settings > System administration - DB), due to documents accumulating in the printing queue.

For this particular case we implemented a new automation action, Cancel pending PDF prints, with parameters Workstation and Server. It’s possible to select both parameters in order to deal with the failure to cancel pending PDF prints in both the workstation and the server.

1.2. Configuration and use

Below you can see in detail the necessary steps required to use the new automation action:

At Configuration… > General > Company parameters > in parameter Printer management settings from ESERPServer specify the printing methods preferred: 

Note: When it comes to PDF printing, you must select the Entersoft Document Printer.

In the Document type series preferred, select the preferred printers: 

Attention: The same values selected in the aforementioned field must be copy-pasted into the respective field of the client.

For print cancellations to be executed via scheduling and take place in both the Server and Client, take the following steps:

1. Create a new Scheduled task (Settings > Scheduling > Scheduled tasks > +)

Go to View/Automation > Automation and parameters and open the new automation. 

1. Then, select the new automation action Cancel pending PDF prints (CancelPendingPrintRowAction) from the available actions.

2. Define a Title and check that the field values (Workstation and Server) are set to true.

3. Save.
   Attention: You may need to de-select and re-select the checkboxes of the parameters to make sure that the values are set as true.

4. Finally, click on Accept.

Back in the application, you can now execute the pre-existing action for cancelling PDF prints, from System administration - DB > Cancel PDF printing. A window will appear for you to choose whether to run this process in the Server & Workstation, or only one of the two.

The PDF prints that were pending have all been cancelled and we can now execute the PDF printing scheduling as usual.

2. Transferring data to companies

2.1. Column addition - Name & TRN

Two new columns were added to the screen Select Company – Companies entries will be copied to, which appears when selecting the action Copy to other Companies... of the page Companies – Full list. 

The two new columns were added in order to offer more information to the user and concern:

1. The name of the company

2. The company TRN

3. Scroller Designer improvements

In version 5.14.0.0, a series of improvements were implemented in the Scroller Designer, to facilitate the user:

3.1. Filter data

In an already created sub-filter, when the user makes a change in the Filter data screen, the fields Name and Name in DB change the entry in the sub-filters list. 

3.2. Warning message - Column addition

A new, enriched warning message appears now when the user attempts to add a column with the same name as an existing one in the list of available fields. The process fails and the warning message appears: 

3.3. Improved display of fields list

The display of the available fields list has also been improved. Now, the columns appear grouped by table, while the tales appear by alphabetical order: 

4. Payment method

4.1. Skip holidays

Now, when the Skip holidays flag is enabled in the payment method and the due date is the end of the month, the system stops on the last business day of the month and does not carry over to the next month. 

New features and enhancements in the Romanian version

1. D300 Update for 2026 

From January 2026, D300 was amended by Order No. 174/2026, removing the rows specific to the old VAT rates. 

In EBS, the automation for creating the .xml file has been modified, while the calculation process remains unchanged. The automation takes into account the declaration date. Thus, if a file needs to be generated for a period prior to January 2026, the .xml file will also contain the old VAT rates.

Note: The changes are already in effect if you install the hotfix for the latest version—5.13.0.3—and will be available in the next version, 5.14.0.0.

If it is necessary to record documents with the old rates, they must be reported under the adjustment headings.

This is done either at the document level, if all lines in the document have the old VAT rates, or at the document line level, for lines with the old rates.

Therefore, if the entire document is reported under adjustments, select the “VAT Return” option and choose the corresponding line from D300 in the Tax Code field. 

If there are both lines with old rates and lines with new rates, the corresponding row from D300 will be selected in the Transaction Type field. This applies only to lines with old rates.

The format of the return and the VAT journals in EBS have also remained unchanged. 

In the new ANAF form, two new fields have been added that contain information regarding:

•  the total value, excluding VAT, of services provided to non-taxable persons in other EU Member States as provided for in Article 278(8)(b) of the Tax Code, 

• namely telecommunications, radio, and television services, as well as electronically supplied services: Total for the previous year and Total for the current year (including the reporting period).

In EBS, the two fields were added as parameters to the .xml file generation process.

If there are no such transactions, leave this field blank.

2. Improvements to e-Factura

The integration of e-Factura with ANAF has been enhanced with the following new features:

2.1. Improving CPV code retrieval

Starting with version 5.14.0.0, the CPV code retrieval feature has been expanded with the addition of the CPV Code field to document lines.

Additionally, in the parameters section, there is a new parameter MARK_CPV_CODE — access it via the menu: Tools and Settings > Customization… > General > Company Parameters > Electronic Transaction Parameters: The UDF field in the document line where the item’s CPV code is specified. 

Depending on the value of the MARK_CPV_CODE parameter, the retrieval mechanism is as follows:

If set to None, the CPV code will be taken from the document line.

If this field is left blank, the CPV code will be taken from the item card.

If set to Comment 1 through Comment 5, the values will be taken from the corresponding lines in the document (fields Comment 1 through 5).
However, if nothing is entered in the corresponding comment, the CPV code will be taken from the document line. If this is not filled in, the CPV code will be taken from the item card. 

2.2. e-Factura information received in other relevant scrollers

The functionality for downloading and matching/unmatching invoices received from SPV has been extended to the Purchasis/Arrivals scrollers (menu: Purchases & Procurement > Receipts & Purchase Invoices > Purchasis/Arrivals) and Expense Documents (menu: Accounting > Expenses > Expense Documents).

Three new automations are available in these:

• Download e-Factura

• Matches

• Delete correlation

The automation Download e-Factura is functionally identical to the one available in the e-Factura - inbound invoices management scroller. Specifically, invoices received from SPV are stored in the database without, however, being linked to invoices already recorded in EBS.

The Matching automation feature allows one or more selected invoices to be matched with a single invoice received from the SPV. The list of invoices from the SPV contains only those invoices that have not already been matched with an invoice in EBS.

The Delete correlation automation "unlinks" the invoice in SPV from the invoice(s) in EBS.

In addition, these scrollers have been expanded by adding three new columns:

• e-Factura document: supplier invoice number.

• RequestID: e-Invoice ID for download from SPV.

• Correlated: Indicates whether the invoice in EBS is linked to a document in SPV.

These columns are initially hidden, but can be displayed in the scroller by right-clicking on the column header and selecting the Add/Remove Columns command.

The three columns are updated through the e-Factura-specific automations mentioned above.

2.3. Self-invoices (389) – bank/business trade account

Until now, the bank accounts listed in the PaymentMeans section of e-Factura were limited to those of the company itself. However, this is not accurate when it comes to self-invoices. Therefore, for self-invoices (389), the supplier’s main account is now provided.

3. Improvements in e-Transport

3.1. Routes for transport outside Romania without a border crossing point (for intermodal transport)

In order to introduce new functionalities, ANAF has developed a new version of e-Transport. This still works in parallel with the first version. To simplify things, SBS e-Transport, which is the basis for ensuring the integration of e-Transport into EBS-RO, can differentiate, depending on the parameters in which the request is formulated, which of the versions will be used to continue communication with ANAF. Therefore, only minimal parameterization is required for the EBS-RO user.

Important: Only e-Transport v2 covers intermodal transport.

In order for EBS-RO to use these new features, the following must be in place beforehand:

1. Make sure the latest hotfix for EBS-RO version 5.13.0-3 is installed.

2. Configure the shipping destinations.

3. Configure the routes (for intermodal transport only).

3.2 Purpose of shipment

Go to the settings page: Configuration and Tools> Customization... > Transaction Parameters > Shipping Purposes.

Two pieces of information are extracted from the Shipping value field for UIT: 

• Type of operation and 

• Scope of the operation - purpose of the shipment. 

The scope of the operation will indicate whether the UIT structure is v1 or v2.

The purpose of shipping in v1 - the shipping purpose will contain:

• Shipping purpose: all digits.

• Operation type: first 2 digits.

The purpose of shipping in v2 - The value of the goal contains:

• Shipping purpose: first digits before #.

• Operation type: the 2 digits after #.

3.3. Routes

For intermodal transport, routes must contain:

• Address

• City

• District

• Country

• Postal code

No customs codes or border crossing points will be established for this type of route.

The route will be used in documents in the same way as it is currently used.

To define a route, go to the settings page: Configuration and Tools > Customization... > Transaction Settings > Routes.

3.4. Expanding the use of e-Transport in EBS

All changes made to integrate e-Transport into EBS were implemented from the perspective of the Document Trade automation workflow. Since there are companies that may use other document workflows that subsequently require an e-Transport request, all these changes have also been implemented in the automation for transfer documents (Document Stock) as well as in the automation for correction documents.

Additionally, it is now possible to submit a UIT request to e-Transport based on multiple supporting documents.

4. SAF-T Improvements 

4.1. Optimization of SAF-T declaration generation

When processing a SAF-T declaration, the CSV file corresponding to that section is uploaded to SBS. However, only one CSV file can be associated with a section, so until now we had to make sure that previously generated files were deleted from SBS before uploading newer ones. To simplify the generation of the declaration, a warning message has been added with the option to delete previously generated files when uploading a new CSV.

4.2. Delete data from the TaxCodes table to delete documents

There may be cases where a document needs to be deleted (because it was issued in error) even though the Tax Code calculation process has already been run. In this case, EBS-RO will display an error message and will not allow the deletion.

To address this issue, a new scroller has been added to the SAFT menu: 

Accounting > Period completion processes > SAF-T > SAF-T Tax information. 

This displays the transactions included in the Tax Code calculation. From here, you can delete a specific document (only from the Tax Code calculation), after which the user can delete the document in the usual way.

4.3. Add Tax Code to document lines

To provide greater flexibility when entering the tax code, the SAF-T Tax Code field has been added to the document lines related to:

• Items (any type)

• Special accounts

• Cash accounts

Selecting a tax code in the document lines will cause the Tax Code calculation process to skip that line and use the information entered by the user. In other words, the information entered in the document lines takes precedence over the system’s subsequent calculation.

This displays the transactions included in the Tax Code calculation. From here, you can delete a specific document (only from the Tax Code calculation), after which the user can delete the document in the usual way.

4.3. Add Tax Code to document lines

To provide greater flexibility when entering the tax code, the SAF-T Tax Code field has been added to the document lines related to:

• Items (any type)

• Special accounts

• Cash accounts

Selecting a tax code in the document lines will cause the Tax Code calculation process to skip that line and use the information entered by the user. In other words, the information entered in the document lines takes precedence over the system’s subsequent calculation.

4.4. Add a new field to the General Ledger Entries to exclude accounts from the Tax Code display

Since the General Ledger Entries scroller contains a number of accounts for which the tax code (and, by extension, the tax amount) does not need to be entered—such as VAT accounts or accounts for business partners—a new field has been added to the database to flag these accounts.

The goal is to make it easier to exclude information related to the tax code in this scroller by using a single criterion.

4.5. Field D300 in the Tax Codes list

The corresponding row from D300 has been added to the list of tax codes.

It can be updated manually or by running a migration script. The file template and the migration script are located in the ESMigration\SAFT application folder.

• SAF-TTaxCodesD300LineUpdate.emi

• Import SAFT New TaxCodes.xlsx

The script simply updates this information for existing codes without altering any other settings.

4.6. Consistency tests

To date, ANAF has published two sets of tests designed to verify certain information submitted via SAFT. The two sets were published in 2023 and 2024, respectively; the first set contains 19 tests , while the second, which also generates notifications, includes 11 VAT-specific tests. On our support website, in the file Consistency Tests, you can find a detailed presentation of these tests.

5. Bank statement import in MT940 format 

5.1. Bank Configuration

Go to the menu Configuration and Tools > Configuration…> Liquidity > Banks.

For each bank defined, enter the bank’s BIC/SWIFT code in the SWIFT Code field.

Here are a few examples of SWIFT codes:

• Banca Transilvania: BTRL;

• ING: INGB;

• BRD: BRDE.

5.2. Company bank accounts

In the menu Accounting > Cash & Bank Accounts > Liquidity accounts: enter the IBAN for each of the company's bank accounts. 

5.3. Bank accounts of business partners

The business partners' bank accounts will be added to their business partner cards (in the Accounting tab). The business partner will subsequently be identified in the statement based on this field.

A business partner may have multiple accounts.

Note: Bank accounts are stored in the database on a per-person basis. Therefore, if a business partner is both a customer and a supplier, they will be identified in the statement based on the transaction sign: Debit (Payment) or Credit (Receipt), respectively.

5.4. Generic items fees/interest

To identify generic items that will be assigned to Commission Payment (CBN) or Interest Collection (VBC) documents, they must be set to the Interest type.

Therefore, it doesn't matter how they are encoded in EBS.

The two items must have a VAT rate of 0%.

5.5. Types of banking transactions

In the menu Configuration and Tools > Configuration… > Liquidity > Bank operation type, for each bank, identified by its SWIFT code, the following fields must be filled in:

5.5.1. Operation description

Fill in the text in tag 86 to identify the transaction. For example:

• PO payment;

• PO collection;

• Promissory note payment;

• Commission;

• Cash withdrawal.

5.5.2. EBS document type

Based on the description of the transaction type, the type of document to be generated in EBS will be identified. In the bank’s MT940 file, tag 86 contains the text that is searched for in the configuration described above.

Note: If the same bank offers two ways to record the same transaction (for example: OP Payment and Lei Payment), two identical lines should be entered, differing only in the transaction description.

5.6. Imported data

The import of the bank statement is performed in two steps:

1. Import file;

2. View data and generate documents.
   
   

The automation process that imports an MT940 file into the database decodes and separates the information contained therein into specific EBS fields so that, based on the configurations, the corresponding documents can be generated.

The import automation has only one parameter: the file to be imported.

If the file has already been uploaded, a warning will be displayed.

The user has two options:

• Continue import – in this case, any data previously imported will be deleted*;

• Give it up.

*) The data can only be deleted if no documents have been generated yet.

5.7. Documents generation

The uploaded data can be found in the Bank Transactions section (under the Accounting > Cash & Bank Accounts menu – context reports: Bank Statement Table).

Report parameters (filters):

• Registration date (this will be the date on the statement);

• Bank;

• Cash account;

• Business partner;

• Status;

• Initially (the recording was just uploaded);

• Processed (A document has also been generated);

• Document EBS.

Report information (columns):

• Date;

• Amount;

• Partner;

• Tag 61;

• Tag 86;

• EBS doc type;

• Generated doc;

• Sign: debit/credit;

• Status: Initial, Processed.

The system will check whether all lines in the statement have a document type identified and, for those of the Receipt/Payment type, whether the business partner has been identified.

To generate the documents, select all rows and run the Create Documents automation.

All generated documents will include the following additional information:

• Alternative document: Transaction No.;

• Argument: Imported data. 

After the documents are generated, the document number will be displayed in the scroller and the status will change to Processed.

If the automation is run again for a line that already has a document, the system will not take any further action.

If you wish to restart the file import and there are generated documents, select the relevant rows and run the Delete Documents automation. 

6. New Report - Debits in Account 418

Until now, the balance of account 418 could only be viewed by business partners, and there was no report showing unbilled invoices as of a specific date. This report, which allows the balance of account 418 on a specific date to be reconciled with the unbilled invoices, is intended to identify the source document/partner that created a discrepancy between accounting and operations.

You can access the new report under Accounting > Chart of Accounts & Entries > context reports - Analytic Account Open Debits 418 

7. Import payroll documents from Socrate Salarii

Payroll documents can be imported from an Excel file based on the template in the ESMigration\ImportSalarii folder:

• ImportSalarii.emi

• Template import salarii.xlsx

First, the following entities must be configured (which is done anyway when entering documents manually):

1. Business partners (separate accounts receivable for accounts 421, 423, 425)

2. General expense items

3. Special accounts

4. Business dimensions (as applicable): Activity, Business Unit, Dimension 1, Dimension 2, Project.

The import template contains a number of fields, of which the following are required:

• Month: Enter the last day of the month for which the import is being run

• Debit account: Enter the analytical account as it appears in EBS

• Creditor account: Enter the analytical account as it appears in EBS

• Debit: Debit amount

• Credit: Loan amount.

The "Center Cost," "Dept," and "Project" columns may be filled in with the information available in the payroll application. This information must be found in one of the five classifications mentioned above for business dimensions.

The Excel columns for cost center/department/project will be mapped to the business dimensions in EBS at the time of import using parameters.

The other columns in the file are currently optional and are not included in the documents.

The actual import is done as follows:

• The payroll file is saved locally (it does not have to be in the application folder where the Excel template is located)

Open the migration wizard from Configuration and Tools > Import/export data > Import data (advanced mode)... 

The migration script contains three parameters that specify which business dimensions in EBS correspond to the columns in Excel.

These will be allocated to the general expense accounts.

The first step in the process is to select the file to be imported. By default, the program looks for the file in the application folder, but you can select any file from your local drive.

Click the Execute button.

Once the import is complete, the following types of documents can be generated:

• CHS.ANG - Employee salary expenses.

• CHS - Payroll expenses – employer contributions.

• CHS.CM - Sick leave.

• CPC - Settlement(closing) for salary advance.

8. New document types

Starting with version 5.14.0.0, the following new document types have been introduced in EBS.

• AF - Self-invoicing of protocol expenses.
  This is used for various receipts for small income items listed in this document along with their payment into a cash account (it does not cover commercial bills). It contains only generic items/services. The customer is neither debited nor credited, and in Accounting, only revenue and cash are recorded. It must be configured so that it is always paid, because they are not tracked in the cash flow forecasts. If the customer leaves a balance or pays by commercial paper, the NDS document (Service Receipt) must be used.

• RAMB - SGR Packaging Receiving.
  This is used for invoices that are not linked to a delivery note and are issued by suppliers. It supports both generic items—such as services—and fixed assets, and facilitates simultaneous payment. It updates cash outflow forecasts.

• SMFI - Initialization of Fix asset subsidy amortization.
  It is used to track the depreciation of subsidies at the beginning of the useful life of fixed assets.

• Extend the functionality for NCV/NDV correction documents:
  NCVV - Used for Discount Credit Notes issued based on turnover with the customer or based on another commercial agreement. It negatively affects turnover. It updates the accounting negatively in the original sales accounts. Generic items are not accepted. Alternatively, the NDA document type can be used, which accepts generic items and updates the granted Discount accounts in accounting.
  NDVV - Used for Corrections - Surcharges - Additional invoices to customers due to errors in value or price during initial invoicing. It generates forecasts for financial receivables but does not cover simultaneous collection. It is important not to use a simple value-based invoice (for a delivery note) as the document type because it produces a different update (it does not update the “invoiced quantity”). However, you can use a common numbering system for both.

• ETR.S - e-Transport document for deliveries.

• ETR.P - e-Transport document for procurement.

• ETR.T - e-Transport document for domestic transfers.

9. New printable forms

• Inventory List

• Bank statement

• Packing list

• Promissory note - BO

• CEC Compensation.

10. Miscellaneous

10.1. Improvements to the import of delimited text files

The feature for importing text files with delimiters was developed by adding a parameter to define the escape character used to delimit field values that are of the text type — “Text qualifier”.

10.2. Retrieve price from the Previous Transactions Report

In the Previous Transactions for Item scroller, which can be accessed from the OFV/COV forms, prices are displayed in LEU regardless of the currency in which the previous transactions were recorded or the currency of the source document. This is an inconvenience when we want the prices to be displayed in the currency of the document from which the scroller was accessed. Therefore, from now on, in the Previous Item Transactions scroller, prices are displayed in the transaction currency, and when the Transfer button is clicked, the price will be converted to the currency of the current document, taking into account both the currency of the original document and the currency of the current document.

10.3. SBS Integration - Removing API Key Entries from logs

The way the SBS is called has been updated so that the API access key is no longer logged, thereby eliminating a potential security vulnerability if someone were to gain access to these logs.

11. Translation corrections and documentation updates

For more information, visit our support site EBS-RO.

We constantly update it with instructions and documentation in Romanian.

We also constantly update and correct any translation or localization errors so that the app can better serve Romanian users.

Bug fixes

General bug fixes

Accounting

• Resolved an error that would occur when attempting account bulk modification, with the error message: Must declare the scalar variable "@AccountingChart".

Receipts/Payments/Portfolio

• Fixed an issue where the scheduled date would be deleted from the Document payment settlement upon saving.

• Resolved an error occurring when updating a budget based on actual data.

• Fixed an issue of settlement entries failing to be created for payroll documents that failed to be created using ESExperimentalFeatures.xml.

Form designer

• A system error has been fixed that would cause inactive salespeople to appear in the customer's main information.

• Fixed an issue with assigning a counterparty to Task-UI that resulted in the error message “An error occurred during search. Please check the search parameters again”.

Scroller & Cube Designer

• Resolved an error that would occur in views where union would be used in SQL additions, specifically in a sub-filter imported as .esq into a view from another one, with the following message: "ForeignKeyConstraint ODSTablesODSRelationsD requires that the child key values (6e6c719c-ab9a-4341-80e8-9fd68b35ab32) exist in the parent table."

• Fixed an issue in the columns of the "Sales/shipments" view and the fields in the column management section, which would display in Greek.

• Fixed the absence of the AccountingChart column in periodic VAT codes.

Import\Export & Migration

• Fixed a bug related to incorrect formatting in freelancer’s certification files.

• Fixed an issue that caused lines from the clipboard to be merged with incorrect charge when the values were identical.

• Resolved an error that would occur when selecting a txt file in an EMI.

• Fixed an issue with the advanced data export feature.

DB Upgrade\Backup\SQL\MSDE\Maintenance Plan

• Fixed an issue that would occur when saving a document. Query "exec sp_executesql N'SELECT TaxMachineProvider FROM ESGOTaxMechanism WHERE GID = @GID',N'@GID nvarchar(4000)',@GID=NULL” would run multiple times, resulting in application performance issues.

Miscellaneous

• Fixed an issue where the total quantity would not display in "Quantity fulfillment", when there were 9 or more item lines.

• Resolved an error of resource group lookup due to the absence of @resourceGID (CRM Service)

• Fixed an issue that would cause an incorrect cost value to appear on a document line (Orders – Reservations).

• Fixed an issue that caused incorrect data to appear in the tab with the breakdown of outstanding balances (Accounting > Receivables > Registers/Jorunals > Registers (with outstanding amounts analysis)) when the user selected a specific date range (Reports-Statistics).

• Fixed an issue with the display of depreciations in the "Annual depreciations" view (Fixed assets).

• Resolved an error that would occur when pasting rows based on headers in budgets (Budget – CashFlow).

• Fixed an issue that would occur when launching the Entersoft Price Checker as a service (Prices).

• Fixed an issue that would occur when copying a serial number to a new serial number. Quantities would not transfer correctly when the measurement unit for the serial number differed from the item's Service MU.

• Fixed an issue that would cause the application login to fail and the following message to appear: «The group or resource is not in the correct state to perform the requested operation».

• Resolved a terminal synchronization error, with the message "The binary stream '62' does not contain a valid BinaryHeader. Possible causes include an invalid data stream or a change in the object version between serialization and deserialization" (LiveUpdate\synchronization issues).

Relevant cases

PS-91588, PS-113260, ΥΠΘ_SUP-222673, PS-115942, PS-117651, ΥΠΘ_SUP-228245, PS-118605, PS-118017, ΥΠΘ_SUP-235071, PS-119796, ΥΠΘ_SUP-236066, PS-119760, PS-108272, PS-108272, PS-108788, PS-117820, ΥΠΘ_SUP-230354, PS-120653, PS-116594, PS-118864, PS-119616, PS-120229, PS-111585, PS-120443, PS-116127, PS-110774, ΥΠΘ_SUP-230574, PS-66545, PS-105798, PS-117491, PS-118751, PS-119802, PS-114003, PS-119021, ΥΠΘ_SUP-225950, ΥΠΘ_SUP-229624, PS-118219, PS-119161, PS-119284, PS-119938, PS-119948, PS-120161, PS-120161, PS-120448, ΥΠΘ_SUP-234130, PS-118294, PS-120845, PS-120575, PS-108369, ΥΠΘ_SUP-210725, PS-117292, PS-116752, ΥΠΘ_SUP-232045, PS-120037, PS-117953, PS-119500, PS-119303, PS-119498, PS-117456, PS-119186, ΥΠΘ_SUP-226063, PS-118772, PS-116593, PS-119225, PS-118851, PS-120420, PS-117964, PS-113826, PS-120012, PS-116407, PS-117759, PS-120321

Fixes for the Romanian version

Accounting

• An error in reconciling deductible VAT with collected VAT has been corrected.

• The business rule for verifying the cash limit, which was operating with incomplete data, has been corrected.

• An error that caused duplicate information to be displayed in the Fixed Assets Register has been fixed.

Declarations

• A reporting error in SAF-T for self-invoices (code 389) has been corrected.

• An error that occurred when generating the D300 form, caused by the different time zones listed on some documents, has been fixed.

• An error that caused certain lines to appear twice in the Intrastat declaration, due to the "active" flag in the Intrastat code dictionary, has been fixed.

• The automatic display of the “VAT on collection” checkbox on all invoices has been corrected, regardless of whether the client’s CUI includes “RO”.

e-Factura

• A sending error in e-Factura has been fixed when invoices have a payment amount of zero.

• An error has been corrected regarding the sending to e-Factura of invoices with partial payments made via multiple payment methods.

• An inconsistency in the recording of the reference numbers for correction invoices received via e-Factura has been resolved.

Miscellaneous

• The Help menu (?) in the application's top bar has been re-updated to reference the Romanian-language support site.

• A mistranslation that affected the logical operators used in Visual Basic expressions has been corrected.

Relevant cases

1098656, 1099342, 1099860, 2000437, 2002986, 2004433, 2005022, 2005584, 2005749, 2005916.