Skip to main content

13 docs tagged with "RKSV"

View all tags

Cash Register Integration

Receipt workflows, special receipts, receipt structure and data collection log (RKSV-DEP, E131-DEP) for the Middleware in Austria.

Data Structures

Austria-specific fields of the receipt response, charge items, pay items and signature entries in the Middleware data structures.

FinanzOnline Management

Managing FinanzOnline connections and notifications for PosOperators in Austria, with status checks per Queue, SCU or operator and troubleshooting.

Introduction

What the Austrian RKSV requires of a POS system — signing, DEP-7 exports, FinanzOnline — and where to start in the Austrian Middleware docs.

Introduction

RKSV.Sign, the cloud signing-only service for Austria without the Middleware, and the CashBox needed before using it.

Receipt Case Definitions

How single- and multi-purpose vouchers, agency business, delivery notes and tips are handled under RKSV in Austria.

Reference tables

The hex-based tagging format used for Austrian ftReceiptCase, ftChargeItemCase and other case values, with links to each table.

Reference Tables v0

Austrian v0 values for ftState, ftReceiptCase, ftChargeItemCase, ftPayItemCase, signature types and formats, and ftJournalType.

RKSV.Sign

Rollout of the RKSV.Sign signing-only product for Austria — entitlements, creating instances via the API, credentials and instance overview.

RKSV.Sign API

REST and SOAP endpoints of the Austrian RKSV.Sign API, with authentication and the Echo, Sign, Certificate, and ZDA methods.

Service Status: ftState

ftState global and local flag values returned by the Middleware in Austria, and how they combine with OR.

Terminology

Austrian legal and technical terms used in the Middleware docs, such as RKSV, BAO, DEP, Nullbeleg, Startbeleg and SSCD.

Type of receipt: ftReceiptCase

ftReceiptCase format, receipt case types, case values and flags for processing receipts under Austrian law (country code 0x4154).