Design receipts, share them digitally and check fiscal status. Signing, cash-register notification and archiving have separate requirements. One POS, the same features — in the cloud or on the venue’s box.
Explore the workflows
Arrange guest-receipt blocks in the designer and check the preview. You can add your own logo. The TSE/QR block remains mandatory. Add a hospitality receipt when needed. A screen preview does not prove successful printing; nothing is printed for this presentation.
Step by step
Use the arrow keys or swipe to move on
Step 1 of 2
The hospitality receipt adds the occasion and participants to the existing receipt. It does not replace its fiscal status.
Step 2 of 2
The design preview uses sample data. Actual evidence comes from the finalised receipt and its stored status.
After fiscal finalisation, the receipt receives a protected link. Guests can open it by QR code or link instead of taking paper. With Nova integration configured, the guest receipt can also be made available there. Translations of individual visible fields still need checking before product captures.
With a configured certified TSE, a regularly signed receipt carries signature data and a QR code. The demo uses the sandbox. Simulated receipts and documented outages are not regularly signed receipts. Check the actual status; the designer preview is not evidence of signing.
Enter business and register details for Germany’s § 146a AO notification from the till. Prepare the notification and inspect its preview. This presentation describes the simulated process. A ready notification has not yet been transmitted; no actual transmission to the tax office is claimed here.
Find receipts in the fiscal archive and open their details. Completed export files have a separate WORM mirroring path with checksum comparison. It requires a configured, attested archive target with write protection. A stored file alone does not prove that protection; successful mirroring is not demonstrated for this presentation.
Select a period and available closings for DSFinV-K export. TSE-TAR has a separate export workflow. In the previous run, the ZIP contained only a manifest and no TSE-TAR files were available. Only opened, checked files containing actual records demonstrate an outcome for auditors and accountants.
LidoOS Copilot
No AI in this module
Receipt design, signature status, register notification and exports are operated here without AI.
You check data, status and files.
An AI statement cannot replace a signature, transmission confirmation or verified export.
Nova ↔ POS
Maintain menus, tables and staff in Nova. The POS handles orders, payments and receipts.
The limits
Sandbox signing, simulated notification and live operation are distinct states. The previously blocked closing explains the export without records. New fiscal operations screens are not advertised as completed features. Archive configuration, write protection and export contents need their own evidence.
Availability
LidoOS POS — coming soon. Terms in the shop; we will plan the introduction together.
Talk to us about how LidoOS POS fits your venue’s workflows.
Short answers
With a certified TSE set up, a regular receipt carries signature and QR code. The demo uses the sandbox; simulated receipts and documented failures are separate things.
No. You prepare the declaration in the till and trigger the transmission yourself. No job and no schedule transmits on its own.
The export builds on completed periods. In the demo venue an earlier export contained only the manifest; what counts is the opened content of a finished file.
The captures show the demo venue Via Palermo: sandbox signatures, an existing sandbox run of the fiscal declaration and actual states of archive and export.
Tell us how you work: dining room, terrace, counter or self-service. Together we will define your operating mode, devices, Nova modules and terms.