ERP-RO01-5.2.0.1

Από

Entersoft Business Suite®

New features and extensions

= Brief description of contents

Invoicing and Financial administration

  • Added support for e-factura

Next up, the new functionalities & improvements catalog is broken down per category, along with use instructions & examples.

  1. e-Factura

It is possible to send the contents of the invoice with a special type of file (xml) to ANAF. The sending of invoices is mandatory for the following transactions:

  • B2G Transactions (Business to Government)
  • B2B Transactions which contains at least one «high risk» item

Invoices can be sent when the document is issued, at the same time as it is printed, but additionally manually or scheduled after it is issued.

E-factura Invoice management

The main screen for managing "to transmit" invoices is done through the E-factura Invoice management (menu: Sales). All transaction documents that must be sent to ANAF are displayed here. Documents are grouped based on their shipping status.

  • Failure. Sent but failed due to errors
  • Success. Delivery completed successfully
  • To be sent. Has not been sent yet.
  • Pending. It’s has been sent but it's still being processed by ANAF

For any documents that failed to send due to errors, the user can display the errors by clicking on the “Errors” field

ERP-RO01-5.2.0.1-image3.png

The following actions are available to use to manage documents pending and documents with that failed to send due

to an error:

  • Send invoices. Resend a document that failed to send.
  • Refresh Status. Update the delivery status of all documents in "pending" status
  • Download Zip. If a document fails to send, you can download the file to be sent to your disk, along with a full report of its errors. Useful when contacting support.
  • Download XML. If an invoice is rejected by the ANAF, you can download the generated file that failed to send

E-factura Configuration

  • Document Series

In the series of documents involved in e-invoice, select values in the following fields:

  • E-invoicing. Select the value “via Provider”
  • Transaction kind. Select one of the B2B or B2G values, as appropriate. Only the document series with the above values can be sent to the ANAF.
  • Document Type

For document types involved in e-factura, select the value in the SAF-T Invoice Type field, to be sent in the Invoice Type field of the file.

  • Document

In the header of trade documents, the Transaction kind field has been added, that shall be updated with the value assigned, as long as it’s been specified in the document series.

  • Items

The user must fill-in the following item fields, as appropriate:

  • Intrastat code. For transactions classified as B2B, in the transaction kind homonymous document field, the intrastat code must be filled in for all items used in the transactions.
  • Related to e-invoicing. Any items that have been classified by the ANAF as “high risk”, must have this field selected.
  • CPV Code. For transactions that have been classified as B2G, the transaction kind homonymous document field must be populated with the CPV code, for all items used in this transaction type.
  • Company parameters

Under the category “ΑNAF Services and Declarations” three new parameters added to enter all the necessary authentication data, in order to communicate with ANAF services for e-factura:

  • BIT Services – login key (Api Key). Provided by BIT software, used also for SAF-T declarations.

  • E-factura – Organization info. Should be completed with all necessary company information. In case of error check that the login company’s person has a main bank account.

  • Entersoft webApi – login key. Provided by Entersoft and is necessary to get access to e-Factura through Entersoft web services. During the creation of the EndPoint in the ES API, the key is completed automatically in the parameter.

Graphical user interface, text, application Description automatically generated


PDF Version