RO | EN

Improvements and new features

Liquidity

Planning of payments
In this version a significant extension was made to the Planning of Payments feature. Planning of Payments is an extremely useful process for managing the company’s cash flow and is used to easily and quickly carry out mass payments to suppliers and creditors. The relevant screen shows, grouped by supplier/creditor, all of the company liabilities to them, in order for the amounts to be paid partially (or fully). Planning of payments facilitates the user, since it includes a multitude of features, such as the proposal of the agreed method of payment for each trade account (cash, fund transfer, company check or customer receivable check), mass payment of all outstanding balances, payment with new checks or checks from the company’s portfolio, the display of additional information such as the company's bank account from which the withdrawal will be made, or the bank account of the trade account to which the deposit will be made. In fact, it's possible to pay out a specific balance (invoice), as well as an amount for a set of documents, starting from the oldest ones.

This version's new implementation makes it possible to add a deposit for Orders meant for suppliers/creditors, through the Planning of payments screen. Very often, agreements made between the counterparties (company and supplier/creditor) stipulate the payment of an amount upon making the order. It's therefore essential to make the deposit through an environment such as Planning of payments, which deals with overall balance management.

Thus, through the Planning of payments screen, it is possible to view, using the relevant criterion, the invoices (confirmed forecasts) and orders (scheduled outflows) that have been made and have not yet been paid (have not been converted into invoices).

The new criterion is displayed in the parameter group “All” and is called “Entry type”. The available values are:

• Confirmed forecasts -> the supplier/creditor invoices (default value)

• Planned outflows -> supplier/creditor orders

• All

The payment document to be created for the order deposit through the Planning of payments cannot belong to  the same type as the payment documents created for open invoices. This is determined by a new company parameter in the Workflows/Processes category titled: “Payment plan process =>16. Doc type for automatic creation of deposits”. If the parameter is left blank, a relevant prohibition message appears at the start of the process and the parameter must be configured to proceed.

Cash Flow Monitoring

The new feature added to the Planning of payments facilitates the monitoring of the company cash flow, since financial indicators such as Planned Inflows and Outflows are reflected in a more integrated way.
In essence, deposit amounts are now covered, concerning deposits added for orders, i.e. non-value official documents.

• Liquidity concerns actual receipts/payments.

• The Confirmed forecasts are derived from the sales & purchase invoices and show the amounts agreed to enter or leave the company, since the relevant value documents exist.

•  Planned liquidity displays amounts that are to be released in the (immediate) future as available to the company and concern orders (sales orders/purchase orders).

The Confirmed forecasts, amounts related to invoices, are ones that change as receipts/payments added are matched to them and “settle” them. Planned liquidity (order-related amounts) also changes, as receipts/payments that are added and are associated with them leave them with a balance until their invoicing.

It is very important to understand that while the deposit is initially given for an order, in order to validate the agreement of the future sale/purchase, other documents may then follow within the system that illustrate the course of this order, such as its confirmation, loading etc. In this case, the deposit (partially or fully) no longer relates to the initial order, but to the ensuing documents. Thus, we end up with sales/purchase order documents consisting of many consecutive steps. We can monitor the deposit that corresponds to each of them, after the part of the deposit that corresponds to them is transferred.
In general, in every new document that is made and is a continuation of the initial document that created the planned inflow/outflow:

• a forecast is created;

• the inputs/outputs are updated;

• the previous inflow/outflow is undone.

More information including examples, configuration and prints associated are presented here in this document: Liquidity - what's new in 5.9.0.0 (in full). 

Miscellaneous improvements

• Increased the number of KeyOnSave characters to 255 characters from 100.

• Improved the screen layout, to add the possibility to create a new trade account through the document. There is an option for a customer/debtor in the sales documents or for a supplier/creditor in the purchase documents.

• An improvement was made so that when saving company parameters, if there are incorrect values, the names of these parameters are indicated with a message, for the user to correct them.

• Added a new company parameter for customer search in Retail. The parameter is called “Max number of entries when searching for retail customers", belongs to the "Document management" category and determines the maximum number of customers that will appear during the search. This was deemed necessary for cases of databases with a large number of customers, in order to avoid delays. If the parameter has value 0, the search brings all customers.

• Improvements were made to cubes “Expenses per cost center” and “Expenses by period”, so that all available expense types (22 in total) are displayed in the “Expense type” criterion.

• The Tax Offices list has been updated. The existing Tax Offices were updated with their new addresses, new Tax Offices were added or those that were removed became inactive.

• The check of change to closed import folders was improved, in order to cover more cases. More specifically, the process checks additional fields such as item, quantity, alternative quantity, weight, net value, VAT value and the total value in base currency.

• In the “Warehouse balance without intercompany transactions” bit, the “Intercompany transactions” parameter was added (default value “No”). That way, if the user wishes to have a Balance Report with only intercompany transactions, all they have to do is select value “Yes” in the new parameter.

• From within the document and during the preview of the trader account register, an improvement was made to show both the code and the trade account name in the print title.

• Improvements were made to the Data Type History Log scroller:

  • the default value in the "Create" parameter changed from “Any” to "Current week",

  • A new "Data type title” parameter was added.

Horizontal functionality

This version supports a network connection with Microsoft EntraId, for users to log in to EBS, beyond the existing functionality of LDAP login for companies with on-premises servers.

For this reason, two optional fields were added in CSConfig\ESClientConnect.xml: the AzureClientId and the AzureTenantId. Therefore:

• In case a user is logged in with EntraId, at least the AzureClientID must be specified with the application ID created in the Azure domain.

• In case of a multi-tenant installation, the AzureTenantID must be specified so that users of only one specific organization can log in. If there is no such need, the field can be left empty.

Additionally, in the Azure domain the installation admin must specify the following:

• User.Read

• User.Read.all

• CrossTenantInformation.ReadBasic.

All the last two require admin consent for them to be available to users.

Of course, as in the network connection with LDAP, the EntraId account that needs to be able to log in must be selected in the user's communication profile.

Romanian version specific improvements

Reverse charge document according to VAT rates

#1091339

In order to cover the case where the reverse charge document (TXV) value differs from the VAT Journal record by some decimal places, a new way of generating the document, cumulated on each VAT rate, has been implemented.

New fields for invoices sent via e-Factura (outbound) and other changes

#1091028

Some new fields have been included in the .xml file for e-Factura: Trade Reg. No., customer order number.

D300 - ANAF structure update

#1090988

The D300 declaration has been adapted to cover the changes to the .xml structure published by ANAF.

Print forms

#1090594, #1090736

New printing forms have been added.

These can be found in the ESPrintForms/Trade application folder.

In order to make them available for use, it is necessary to add them to the appropriate document type series.

• NIR standard prints

• Standard printouts of Customer Delivery Note - with and without price

New document types

#1090226, #1090225, #1090224, #1090222, #1090220, #1090219

A number of new documents have been included in the application.

In order to make them available for use, if they have not been previously installed, the Import from Entersoft .xml option will be used.

• FAV.AUTO - Self invoice issued by the beneficiary on behalf of the taxable person

This type of document impacts the statements as follows:

• in D300: similar to a regular sales invoice;

• in D394: to be declared only in the series/invoice sections;

• in e-Invoice they are not transmitted;

• in SAF-T they are transmitted as invoices of type 389 (Self Invoices).

• NVC.AUTO - Revoke auto invoice issued as beneficiary

This document has a similar impact to the previous one, the only difference being the document sign.

• FAC.AUTO - Self invoice issued as beneficiary

This type of document impacts the statements as follows:

• • in D300: similar to a regular purchase invoice;

  • in D394: to be declared both in the series/invoice area and in the OP1 area;

  • in e-Invoice with document type 389;

  • in SAF-T they are transmitted as invoices of type 389 (Self Invoices).

• CHS.CM - Expenditure on sick leave

This document is needed to record sick leave expenses.

• BFC.RO - Fiscal receipt with RO

The document type is similar to the existing BFC, with the only difference that BFC.RO is included in D394.

• FS - Simplified invoice

The document type is similar to the existing document, FSC, with the only difference that in D394 it appears in the simplified invoices section.

EBS-RO, documentation and translations improvements

For more info, browse the EBS-RO website.
We constantly update it with instructions and documentation in Romanian.

We also constantly update and correct all translation or localization errors, so that the application will better serve the Romanian users.

Commercial management

Documents

• Fixed issue when changing information field value in document header where the closure type is unchecked and there is an access rights profile.

• Fixed problem when modifying quantity in a document resulting from a transition when the item is tracked with basic and alternative PM.

• A correction was made to rows of documents where the "Next Number" field was being changed by simply clicking on the field.

• Fixed problem of displaying difference in row value with document value under some cases. The problem occurred when in the document line the user typed more than one comma-separated serial number in the "SN Code" field.

• Fixed an issue when printing and saving a copy to PDF in Related Documents when "Full Print" is set in the Document Row in the Reprint field and "Number of Copies" is more than 1.
  
  

Reports

• In the view "Sales based customer evaluation" a correction was made so that even customers with a credit invoice value higher than the invoice value are displayed correctly

• Fixed an error in the prices in the "Sale prices in effect" view that was appearing under conditions. It was noted that the column Value of closing inventory in the bit: 'Closing inventory balance (detailed)' in case the action of value conversion is performed is not converted to the currency of choice. A correction has been made.

• Fixed the "Justification of vendor discounts" view so that double-clicking opens the vendor form and not the customer form.

• Fixed incorrect behavior in the Fixed and Serial Number criteria in the "Register of serial number contents" view

• Improved the projects list to bring only projects and in the subprojects list to bring only subprojects and not their projects. Also fixed the project code filter to filter only projects and only subprojects respectively.
  
  

Miscellaneous

• Fixed a problem with a delay in the display of accounting entries through the import folder screen.

• A problem was solved with a delay in retrieving information on price list lines.

• Transaction data by address on the customer form now only shows active sellers.

• Fixed an error occurring when transferring an accounting account to another company.

• It is no longer allowed to delete item dimensions (color, size, etc.) that participate in a dimension table and a prohibition message is displayed.

• Fixed display problem in property values when there were property categories without description.

• Removed the "Recommended by" field from the Bulk change of fields in the person list since it doesn't make sense to do this en masse. In this field within the person form when searching is filtered out the person in which I am located which cannot be supported in the bulk change.

Related cases

Horizontal functionality

• Fixed problem with activating gRPC from within the ESConfig.exe screen.

• Fixed a problem in the behavior of check boxes when they trigger some behavior in a form. For example, if a check of a checkbox was set in a warehouse item property sheet to trigger something else within the item form, this still required a click somewhere in the form to be applied.

• Fixed an issue in sorting records when exporting an excel file via automation.

Related cases

Bug fixes for the Romanian version

Declaration D406 (SAF-T)

• Corrected the tax year selection in the csv/xml file generation process. Initially it was only possible to select open years. This made it impossible to generate fixed asset files for the previous year if it was already closed.

• The selection of fiscal periods for monthly return generation has also been corrected. Initially it was only possible to select periods from the current and previous fiscal year.

• Fixed the bug that excluded the last day of the month in the process of calculating tax codes for accounting notes (Prepare Tax information).

• Fixed validation errors (test 7 and 9) for Ledger Accounts Entries (Ledger Accounts Entries) regarding the reverse charge tax type code and its 0 value.

Declaration D390 (VIES)

• Fixed the case of credit note documents (negative total) and lines with opposite sign.

• The lack of D390 declaration creation automation from the menu in EBS EXP-RO versions has been corrected.
  
  

e-Transport

• The xml file download automation for documents that have received ITU code has been corrected.

• The ITU Status Update automation has been corrected.

• The xml file download automation has been corrected for documents that have received ITU code.
  
  

e-Invoice

• An error was corrected when checking the supplier/customer address (where instead of the main address of the supplier/customer the delivery address was displayed).

Related cases