Skip to main content

Fiscal Requirements

Functions of the EFR​

  • Fiscal message generation upon ESR data delivered
  • Local message signature using the Fiscal Certificate
  • Request to the fiscal system TicketBai over HTTPS TLS 1.2
  • Response to the cash register application
  • Transaction protocol
  • Protocol of Grand Totals per tax group
  • Retry handling according to regulations in case of network failure
  • Tamper-proof archiving (encrypted cloud-storage)

Test (Playground) Environment​

For testing transactions should be fiscalized against the playground system. Therefore the profile has to be set to fiscal test mode http://localhost:5618/profile:

fiscal_test

Please set this attribute and confirm with [Save].

For testing you will need a Test/Demo certificate, which can be obtained like productive ones (see next section).

Fiscal Certificate Handling​

By law receipts have to be digitally signed. The certificate used (device specific) is issued over the fiscal authority's online system. Certificate file (xxx.p12) and password are confidential.

Local upload​

On page http://localhost:5618/control you can upload the certificate file:

upload_certificate

The certificate is installed correctly as soon as the green OK bar and the ES-Certificate is shown:

certificate_uploaded

Certificate assignment​

For NumSerieDispositivo (Certificate number) the number of the received and uploaded certificate (CN=...) has to be entered like in the example seen below.

certificate_uploaded_2

trm_cfg

If the certificate is not loaded and assigned correctly you will get error #CERT_NF for transactions.

This is necessary because installed certificates are valid for the local machine, not for a specific client and multiple certificates can be loaded.

TaxId has to be specified in client profile http://localhost:5618/profile:

profile_cfg

Certain information must be entered to successfully send data to TicketBAI:

cfg

If SeriaFactura is not filled out TL_TT is used. SW_EntidadDesarrolladora_Version may be optional.

Network Access​

The Spanish fiscal law stipulates online registration of each sale transaction via web request. A transaction code (TBAI) and its QR representation has to be printed on the receipt or invoice. Therefore the machine running EFR must be granted access to the fiscal system TicketBAI. Network devices (Router, Firewall) have to be configured accordingly or a web proxy is used.

The hosts for the firewall settings can be found in chapter firewall setting.

A proxy can be defined in the default profile http://localhost:5618/profile and is shown in the control web page; example:

proxy

By default a network timeout of 5000 ms is used (can be changed using Attribute Fiscal_timeout=).

Offline Transactions​

If the fiscal acknowledgement cannot be obtained within the timespan defined (5000 ms by default), the registration response is sent from EFR to the cash register software with an empty fiscal tag. It is marked with Errorcode="#OFFLINE", and the operator is informed with the first offline transaction (not to interfere cashier action) with UserMessage="Server offline".

Offline transactions are stored in folder /EFR/rn/def/retry (see chapter "Local Storage" in EFR Reference), and delayed an automatic retry is performed.

Typically, the fiscal response should be received within less than one sec.

Retry Handling​

Automatic retry is performed for all offline transactions, the retry interval is increased up to one hour, as long as the fiscal system is not accessible.

A finally successful fiscal retry is logged in the fiscal journal file, so the whole transaction is tracked.

If retries remain unsuccessful, EFR gives a UserMessage once a day.

Special ESR Element​

NameDescription
ES_NIFoperOperator's Tax Number

Field NIFoper is optional in the fiscal message, so ES_NIFoper is optional in the transaction data registered.

<Tra>
    <ESR D="2017-05-15T09:28:00" TL="01" TT="1" TN="2071" ES_NIFoper="01234567890" …>

For convenience on systems with only one operator, a fixed value can be set in http://localhost:5618/profile. If standard ESR field Opr is provided, also an automatic assignment list (Opr=ES_NIFoper) can be entered:

ES_NIFoper

UserMessage​

Independent of the success of a transaction a message for the operator of the cashier may be requested by the EFR in <UserMessage>: this shall be printed to a display (e.g. MessageBox).

UserMessage (ES)UserMessage (EN)ReasonAction
Sistema Fiscal fuera de líneaFiscal System offlinenetwork error, Tax Authority does not respondTransaction has been successfully registered locally, it will be sent to the fiscal CIS system as soon as the network error has been solved. Check internet access. An echo test can be performed using the EFR web interface.
Cambiar NIFTaxId changedfiscal certificate replacedmay occur only during testing
#CERT_NF#CERT_NFcertificate not loadedPlease revisit Fiscal Certificate Handling -> Local upload!
#MISS#MISSmissing data in requestcheck for mandatory information missing in your REST command

Automatic Recovery with the Fiscal System​

In case the signature request to the fiscal system of the Tax Authority fails (network error, response timeout > 5 sec), a transaction is registered without signature. The EFR resends transactions in original order in background as soon as the network connection is restored. The cash register operator is informed via UserMessage. Offline transactions do not contain a "TBAI" / "Fiscal" tag and are marked with ErrorCode="#OFFLINE".

According to fiscal law network repair has to be performed within 48 hours.

Acceptable Warnings​

There are certain situations when Warnings might be acceptable, normal or even unavoidable. One case is at the beginning of transactions for a new device. “w-009-AVISO: Posible error de encadenamiento validation failed” for example is unavoidable when starting transactions on a new device.