What a TSE actually is, and why every counter needs one
A TSE — Technische Sicherheitseinrichtung — is a certified security module that German law requires electronic cash registers and point-of-sale systems to use. Every transaction is signed and logged by the TSE so that later tampering is detectable: sales cannot be quietly deleted or altered after the fact. Receipts must carry TSE data, and the signed records must be exportable for a tax audit in the prescribed format. The TSE can be a hardware element or a cloud service, but its use has been mandatory for electronic tills for several years.
The thing operators underestimate is scope. A campsite is not a single till. It is the camp shop, the kiosk, the restaurant, the bar, the activity desk, and the payments taken at reception. Each of those is an electronic till in the eyes of the rule.
Which is why the common answer — a fiscal box wired next to each register — gets expensive and fragile fast, and why the honest question to ask any vendor is not "do you support TSE" but "is it in the till, or is it a box I have to buy".
In Grondia, it is in the till
Grondia’s point of sale is TSE-ready: fiscalisation is designed into the till rather than added as a bolt-on box. Germany is part of our DACH rollout — ask us for the current TSE/DSFinV-K status before planning a migration. Swiss sites get the same folio and reconciliation behaviour today, without the TSE requirement, from the same product.
The till is designed for the physical reality of a campsite rather than a high-street shop. It is offline-tolerant: when the wifi drops in a field, it keeps selling and syncs every transaction the moment the connection returns, with stock and folio postings catching up automatically. Stock counts down as you sell, so you see the firewood running low before a guest does.
And it is joined up with the rest of the site. A guest buys firewood, two coffees and a bike hire; each item posts to their reservation and settles on one running folio at check-out, alongside the pitch and any tourist tax — rather than as three separate transactions to reconcile at close.
GoBD — what it asks of you, and what Grondia contributes
Be careful with the phrase "GoBD-compliant software", because it is slightly a category error. GoBD is Germany’s set of principles for the proper keeping, retention and auditability of books and records held in electronic form. It requires that tax-relevant records are complete, accurate, timely, orderly, unalterable and retained for the statutory period, in a form the tax authorities can inspect. Those duties fall on the operator. No vendor can certify them away on your behalf.
What software can do is make the compliant path the default. Grondia contributes three things that matter here: sales recorded through a TSE-fiscalised till are signed at the point of sale so alteration is detectable; every access and action against the records is written to a tamper-evident audit log with user, timestamp and action; and retention is enforced automatically rather than left to someone to remember.
Beyond that, every payment, tax line, deposit and refund exports in a DATEV-friendly, VAT-aware format, so your Steuerberater imports rather than re-keys.
Grondia does not claim a GoBD certification, and you should treat any vendor that claims one for you with some curiosity. What we will do is tell you precisely which mechanics exist so you and your advisor can assess them.
An honest note on the German market
Grondia is built in Switzerland and its deepest compliance work is Swiss: HESTA, cantonal Meldeschein, per-commune Kurtaxe, Swiss QR-Bill. The German-market features that exist today are TSE fiscalisation in the point of sale and DATEV-friendly accounting exports.
What is market-neutral — the booking engine and pitch map, the property-management core, the guest portal, the point of sale, analytics, and the bookable website — works the same wherever your site is.
What is Swiss-specific does not have a German equivalent in the product today: German guest registration (Meldeschein) and any Landes- or Kurbeitrag reporting are not built. Data is hosted in Switzerland, which is a fact worth raising with your own advisor rather than one we will characterise for you.
If you run a German site, that is the accurate picture. Talk to us about what your operation actually needs before assuming either way.