Austria (SIGN AT)

SIGN AT at a glance

	Details
Regulation	RKSV (Registrierkassensicherheitsverordnung) — Austrian cash register security regulation
What it requires	Cryptographic signing of all cash transactions, QR codes on receipts, FinanzOnline registration
Certification	fiskaly handles the security device (SCU) — no separate POS certification required
Integration effort	1-2 weeks if already on SIGN DE; 3-5 weeks from scratch
Key difference from DE	Simplest country after DE. Uses SCU instead of TSS. Requires FinanzOnline registration.

📘Specialized API — closest to SIGN DE

SIGN AT is a Specialized API — purpose-built for Austrian RKSV compliance. Of all the SIGN products, it is the most similar to SIGN DE in terms of API patterns and integration effort. If you are already on SIGN DE, Austria is typically the fastest country to add. For the multi-country Unified API architecture (France, Italy, Sweden), see The Unified API.

What is RKSV?

The Registrierkassensicherheitsverordnung (RKSV) requires Austrian cash registers to:

• Cryptographically sign every cash transaction using a secure cryptographic unit (SCU)
• Generate QR codes on receipts containing the signature data
• Register with FinanzOnline — the Austrian tax authority’s online platform
• Store transaction data securely with regular exports

Key differences from SIGN DE

Concept	SIGN DE	SIGN AT
Signing resource	TSS (Technical Security System)	SCU (Secure Cryptographic Unit)
Initialization	Create TSS, set Admin PIN, initialize	Create SCU, register with FinanzOnline
Receipt QR code	KassenSichV format	RKSV format (different fields)
Fiscal export	DSFinV-K (separate product)	Built-in export via SIGN AT API
Tax filing	SUBMIT DE to ELSTER	Via FinanzOnline (not through fiskaly)
Complexity	Most complex (3 products: SIGN + DSFinV-K + SUBMIT)	Simpler — SIGN AT covers signing + exports

Integration effort

Scenario	Duration	Notes
Already on SIGN DE	1-2 weeks	Adapt SCU provisioning, update receipt QR code format, add FinanzOnline registration step
New integration	3-5 weeks	Full flow: auth, SCU setup, FinanzOnline registration, transaction signing, receipt QR codes

💡Austria is a good second country

If you are planning multi-country expansion, Austria is often the best second market to add after Germany — the integration patterns are nearly identical and the regulatory requirements are simpler (no separate DSFinV-K or SUBMIT product needed).

Getting started

1. Create your organization

   Register on fiskaly HUB and create an organization for Austria.

2. Generate API credentials

   Create an API key in HUB. The same authentication flow used for SIGN DE applies here.

3. Register with FinanzOnline

   Complete the FinanzOnline registration for your taxpayer. This is a prerequisite before going live. See the integration guide for details.

4. Integrate the API

   Use the SIGN AT API endpoints to create an SCU, register clients, and sign transactions.

5. Test and go live

   Validate your integration in the sandbox environment, then contact fiskaly to enable production access.

Documentation

Introduction

Overview of RKSV and the SIGN AT solution

Integration Guide

10-step integration walkthrough including FinanzOnline registration

Receipt Data

Required receipt fields and RKSV QR code format

Glossary

Key terms for Austrian fiscal compliance