Skip to main content

πŸ‡¦πŸ‡Ή Austria

This document describes all necessary configuration for a compliant setup in Austria following the RSKV.


In order to configure your store in Austria to be compliant, the following configurations need to take place.


All settings below should be set on the most convenient level possible. In other words, if your organization structure has a country organization which houses all Austrian stores, then that's where they should go.

Auditing:ProviderAUSTRIASets the certified aspects.
Auditing:GenerateTerminalTotalstrueMakes sure EVA will track totals for stations.
ATrust:Host***The host URL for the A-Trust a.sign application.
ATrust:Username***Your A-trust username.
ATrust:Password***Your A-Trust password.
Auditing:Austria:AESKey***AES key used to encrypt the transaction counter value.
Auditing:Austria:DEP:Host***The host URL for the e-Tresor DEP application.
Auditing:Austria:DEP:Username***Your e-Tresor DEP username.
Auditing:Austria:DEP:Password***Your e-Tresor DEP password.
UniqueInvoiceNumberSequencetrueMakes sure EVA creates separate invoice chains.

In a scenario where the A-Trust:Username value is correct but ATrust:Password isn't, your account becomes blocked on A-Trust after 5 invalid attempts.


When configuring your Austrian organization unit(s), a company needs to be attached. If there isn’t an Austrian company present yet, a new one can be created within Admin Suite under the Companies chapter. The following fields need be filled:

  • Name
  • VatNumber
  • RegistrationNumber
  • Address (VisitorAddress)
    • Street
    • HouseNumber
    • ZipCode
    • City
    • CountryID

Organization units​

Once a company is in place, you need to attach it to an organization unit.

Make sure the following fields are filled when creating an organization unit:

  • Name
  • BackendID (store number)
  • BranchNumber
  • Address
    • Street
    • ZipCode
    • City
    • CountryID
  • CompanyID

It is crucial that you have the CompanyID field filled when creating the organization unit. You can retrieve this ID from the Austrian company you created/have. This is the legal entity under which this OU/store is operating and will be referred to when filling in the details on the invoices and receipts.

Further, please make sure to fill all the auditing fields for your respective Austrian OU's.

Creating Stations​

Stations need to be created both in EVA and in FinanzOnline.

Creating stations in EVA​

You can find steps on adding a new station here.

When creating a station, make sure the following fields are filled in:

  • Station name.
  • The checkmark This station is a fiscal station and will be used for transactions needs to be checked.

All payment types must have a category, otherwise the payment can't be correctly mapped, and Ship Orders would fail.

Creating EVA stations in FinanzOnline​

When creating stations, these should also be registered in FinanzOnline as a 'Registrierkasse'. To do so properly, fill the KassenID field with a combination of OrganizationUnitID and StationID.

E.g. if OrganizationUnitID = 13 StationID = 236, fill KassenID in FinanzOnline with 13.236.

Taking stations into use​

Before a station can be used, we need to register a StartBeleg. When creating the station in EVA and adding a thermal printer to it, EVA will print the related document automatically. This document and the QR-code on the receipt should be checked with the BMF application.

Closing down stations​

When closing down stations, we need to register a Schlussbeleg. After deleting the station in EVA, a related document will automatically print, which can then be checked with the BMF application.


To comply with RSKV requirements, the following tasks need to be set up under Management β†’ Tasks.

EVA.Auditing.PrintLegalDocumentTaskGeneratorYearlyControlDocumentYearly interval
EVA.Auditing.PrintLegalDocumentTaskGeneratorMonthlyControlDocumentMonthly interval

Periodic documents​

There's two legal documents that need to be generated periodically;

  • MonatsBeleg
  • JahresBeleg

As mentioned before under tasks, these should be set up with the correct interval. Generally, those are generated at the very beginning of the month/year. The task generates the documents, stores it, and in turn makes a QR code of it (the QR code is what's scanned using the government app) that is retrievable by an Admin user via the Fiscal archiving β†’ Control documents.

Special documents​

Finally, there are two special documents for special situations.


A control document can be requested during a tax audit or other legal store checks. This document can be printed from the Companion App at any time. To do so, go to the Information tab. There you will find a button called Print control document.


Whenever the A-Trust security device in your store loses connection, EVA will include the phrase "Sicherheitseinrichtung ausgefallen" on every receipt that's printed. When the connection is restored, you are legally obliged to print a SammelBeleg. This will be automatically printed when the connection is restored.


The following Stencils are important for a compliant setup in Austria;


An invoice template which is preconfigured for your convenience.


No special settings need to be applied to create the zero document, as they use the same stencil template as regular receipts.