odoo-addon-l10n-at-pos-rksv 19.0.1.4.3.2

Austrian RKSV (a.sign) integration for Point of Sale

POS Austria RKSV

This module integrates the Austrian RKSV (Registrierkassensicherheitsverordnung) signing flow into the Odoo Point of Sale.

It uses the a.sign RK online service of A-Trust to sign every receipt with a chained AES-encrypted turnover counter, producing the QR code, DEP entry and zero/start receipts required by the Austrian fiscal authority.

Table of contents

• Configuration

• Usage

• Bug Tracker

• Credits

  • Authors

  • Contributors

  • Other credits

  • Maintainers

Configuration

1. Open Point of Sale > Configuration > a.sign RKSV and create an a.sign Certificate record. For the online method, supply the certificate file together with the API user and password received from A-Trust.

2. Open Point of Sale > Configuration > Point of Sale and edit the POS you want to enable RKSV for. In the Settings tab, expand RKSV Austria and:

   • tick RKSV Austria;

   • select the Method (online or card);

   • enter the Serial # of the certificate created above;

   • enter the Fiscal ID (VAT number) of the company;

   • leave POS ID and Encryption Key empty to let the module generate defaults, or override them as needed.

3. Save the configuration and click Assign to lock the parameters and activate signing for new orders.

A scheduled action POS a.sign: Sign Missed runs daily and re-signs orders that could not be signed at checkout time (for example because the online service was temporarily unreachable).

Usage

Once the POS is configured and assigned, every receipt closed at checkout is automatically signed and the resulting QR code is printed at the bottom of the receipt. Special receipts are produced when needed:

• Startbeleg – the very first signed receipt of a POS, stamped with the marker STARTBELEG on the printed receipt.

• Nullbeleg – manually triggered via the Create Zero-Receipt button on the POS configuration; printed with NULLBELEG.

• Storno – cancellation of a previous receipt, printed with STORNO.

Cancelled orders consume a receipt number at creation. To keep the receipt range gapless, they are signed as zeroed receipts (NULLBELEG); orders without any payment have their lines zeroed first. This signing runs right after a session is closed (triggered asynchronously) and additionally once a day via cron; a POS with an open session is skipped. Signed orders are protected against concurrent cancel requests overwriting their state or name.

The list and form views of Point of Sale > Orders > Orders expose the RKSV fields (a.sign Type, a.sign State, a.sign Sequence, a.sign Counter, a.sign DEP, a.sign QR-Code) for auditing and exporting the DEP.

Printable PDF reports are available for the certificate and the POS configuration via the Print menu of the corresponding form.

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

• Weboffice IT-Service und Marketing GmbH & Co KG

Contributors

• Martin Reisenhofer <[e-mail]>

• Weboffice IT-Service und Marketing GmbH & Co KG

Other credits

The integration tests rely on the regkassen-verification DEP verification tool published by the Austrian A-SIT Plus initiative. The related Java archives shipped under tests/regcheck/regkassen-verification-1.1.1 remain the property of their respective authors.

Maintainers

This module is maintained by the OCA.

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

This module is part of the OCA/l10n-austria project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.