SimpliServDocs

RKSV logic & fiscalization

Standard flows, POS receipts, number ranges and fiscalization in SimpliServ

→ Open registers in SimpliServ

This document explains how receipts are processed behind the scenes in SimpliServ, which receipt types exist and when fiscalization is required. It's aimed at tenants working with invoices, payments and the register.

Basic principle

In SimpliServ, payments and receipts are processed cleanly separated:

  • Invoice / order represents the business case
  • Payment documents how it was paid
  • Receipt documents the payment process and is fiscalized or not depending on the payment method

That keeps it traceable which receipts belong to the register and which don't.

Standard flow with an invoice

A typical flow in the system is:

  • An invoice is created (often based on an order)
  • A payment is recorded
  • A matching Receipt is generated from it

The payment flow is:

Invoice → Payments → Receipts

Partial payments are possible. A separate receipt can be created for each payment.

Payment methods and receipt behaviour

Which kind of receipt is created depends on the payment method.

Cash or card payment on site (POS)

For payments directly at the register, a BON receipt is created.

  • Receipt type: BON
  • Fiscalization: Yes
  • QR code: Yes

These receipts are fiscalized via RKSV and belong to register accounting.

Online payment

For online payments (e.g. Stripe, Mollie) a PAYMENT receipt is created.

  • Receipt type: PAYMENT
  • Fiscalization: No
  • QR code: No

These payments don't run directly through the register and are therefore not subject to RKSV.

Bank transfer

For manually recorded transfers, a PAYMENT receipt is also created.

  • Receipt type: PAYMENT
  • Fiscalization: No
  • QR code: No

POS flow for walk-in customers

For sales directly at the register, SimpliServ supports a fast POS flow.

When you create a quick invoice, the following happens in the background:

  • An invoice is created in the system (so line items are stored correctly)
  • This quick invoice technically exists but isn't listed like normal invoices in the regular invoice list
  • Payment at the register creates a fiscalized BON receipt

This is the recommended flow for walk-in customers and fast register sales. How you operate the register day to day is described in Point of sale (POS).

Cancelling receipts

Cancellations are represented via receipts in SimpliServ.

That means:

  • A dedicated cancellation receipt is created
  • The cancellation receipt references the original receipt
  • Whether the cancellation is fiscalized depends on whether the original receipt was fiscalized

That keeps the receipt chain complete and traceable.

Number ranges and prefixes

Each receipt type uses its own number range with its own prefix. That makes receipts easier to tell apart day to day. How the format and digit count can be configured is explained in the section on number ranges.

BON

BON receipts are used for on-site cash and card payments.

  • Key: BON
  • Prefix: B
  • Usage: POS cash / POS card payment
  • Format: B{register number}-{sequential number}

Examples:

  • B1-0001 – first BON on register 1
  • B1-0002 – second BON on register 1
  • B2-0001 – first BON on register 2

CASH_MOVEMENTS

This number range is used for cash deposits and withdrawals.

  • Key: CASH_MOVEMENTS
  • Prefix: EA
  • Usage: deposit / withdrawal
  • Format: EA{register number}-{sequential number}

Examples:

  • EA1-0001 – first deposit/withdrawal on register 1
  • EA1-0002 – second deposit/withdrawal on register 1
  • EA2-0001 – first deposit/withdrawal on register 2

VOUCHER

This number range is intended for voucher receipts.

  • Key: VOUCHER
  • Prefix: GS
  • Usage: voucher receipts
  • Format: GS{register number}-{sequential number}

Examples:

  • GS1-0001 – first voucher receipt on register 1
  • GS1-0002 – second voucher receipt on register 1
  • GS2-0001 – first voucher receipt on register 2

PAYMENT

PAYMENT receipts are used for non-register payments, e.g. online payments or transfers.

  • Key: PAYMENT
  • Prefix: P
  • Usage: online payment / bank transfer
  • Format: P-{sequential number}

Examples:

  • P-00001 – first PAYMENT receipt
  • P-00002 – second PAYMENT receipt

Structure of receipt numbers

For all register-bound receipts, the register number is included in the receipt number. That way it's immediately clear which register a receipt belongs to.

This applies in particular to:

  • BON
  • CASH_MOVEMENTS
  • VOUCHER

For the PAYMENT type there's no register number, since these receipts aren't tied to an open register.

Cash report

The cash report brings together all register-relevant transactions. This typically includes:

  • cash payments
  • on-site card payments
  • deposits and withdrawals
  • voucher transactions (depending on the process used)

Payments that don't run directly through the register (e.g. online payments or transfers) are generally not part of the cash report, unless they're deliberately processed as register revenue.

The cash report can be exported for freely chosen periods.

Fiscalization explained simply

Fiscalization ensures that register-relevant payments are recorded tamper-proof. In Austria this is governed by RKSV.

When is it fiscalized?

Payments made directly on site at the register are fiscalized, for example:

  • cash payment
  • card payment at the terminal

These receipts get a QR code and are signed into the fiscal receipt chain.

When is it not fiscalized?

Payments that don't take place directly at the register aren't fiscalized, for example:

  • online payments
  • bank transfers

These receipts get no RKSV QR code.

Overview

TypeNumber rangePrefixCash sessionFiscalization
Cash / card on site (POS)BONBYesYes
Deposit / withdrawalCASH_MOVEMENTSEAYesNo
VoucherVOUCHERGSYesYes
Online payment / bank transferPAYMENTPNoNo

How is this guide?

On this page