Fiscal point of sale
Retail and hospitality systems with the TSE built in, not bolted on; the certification travels with the product.
Germany & Europe
The habits we export everywhere else come from here.
Daleenda began in Stuttgart, and it shows in every market we work in: fixed scopes, written decisions, documentation procurement can read. Here the work simply starts further ahead. Our point of sale has met the TSE requirement since its first release, and our lab platform carried 300+ German test centres through the pandemic.
The gate: KassenSichV / TSE
Every till in Germany needs a certified technical security element, and that one requirement decides whether a system can go live at all. Ours ships with fiskaly SIGN DE under a direct agreement with fiskaly Germany GmbH, certified from the first release rather than retrofitted after the first audit. Everything else on this page comes after it.
- German TSE
- GDPR
- GoBD
- XRechnung / ZUGFeRD
- EAA / BFSG
- GDPR
- Data-processing agreements and EU hosting as standard, with the records to show what is processed, where it sits, and why.
- GoBD
- Books and records in the form, and for the retention period, the German tax authority expects, so an audit finds what it is looking for.
- XRechnung / ZUGFeRD
- Structured invoices to EN 16931. The B2B receiving obligation began January 2025; issuing follows in phases, and the systems are ready for both.
- EAA / BFSG
- The European Accessibility Act has applied since June 2025. Interfaces are built to WCAG AA from the first screen, not corrected before a deadline.
300+
test centres ran on the laboratory platform we built and operated for KVBW, through the pandemic's load, when going down was not an option. That is the reference to ask about.
The work itself
What we build here
Platforms that carry load
Multi-tenant systems built to be audited and to stay up; the KVBW platform is the working example.
Operations software
Inventory, sales, finance and HR for companies that outgrew their spreadsheets, GoBD-shaped from the start.
The arrangement
How the work runs
- Hours
- European working hours; same-day answers are normal, not lucky.
- Language
- A German-speaking line; English throughout the written trail.
- Delivery
- Fixed scopes and the documentation European procurement asks for.
- Ownership
- Code, repository and cloud account are yours from day one.
Getting started
How the work begins
30-minute meeting
You talk to an engineer. We listen, ask, and tell you honestly if we're the right fit.
A proposal scoped to the work
Fixed scope and price for a defined build; a phased plan for a larger programme. In writing, without obligation, and small asks come back in days.
Delivery in the rhythm the work needs
Short cycles with a demo at each for product work; staged milestones for large programmes. Either way you own the code and the repo from day one.
Launch, run, improve
Monitoring, support and a roadmap. We stay after go-live.
Questions
What companies here usually ask
- Have you shipped German fiscal compliance before, or would we be first?
- Before. The TSE requirement has been met through fiskaly SIGN DE since our point of sale's first release, under a direct agreement with fiskaly Germany GmbH, and the GDPR-compliant systems are the ones we already run.
- Do you actually work European hours?
- Yes, with enough overlap that a same-day answer is normal rather than lucky, and a German-speaking line for the conversations that need one.
- Is the accessibility work real, or a checkbox?
- Interfaces are built to WCAG AA from the first screen. Since June 2025 the European Accessibility Act has made that a legal requirement for e-commerce rather than a preference.
The other markets
Thirty minutes, in German if you prefer.
With a senior engineer who would do the work, not a sales call.