Tourist tax — Kurtaxe — looks trivial: a small per-person, per-night charge you pass to the municipality. In practice it is one of the fiddliest numbers a campsite handles, because almost nothing about it is constant.
Why Kurtaxe is deceptively hard
The rate is not one number. It varies by:
- Municipality — every commune sets its own tariff.
- Season — many charge more in high season.
- Guest type — children under a certain age, day visitors and long-stay seasonals are often exempt or reduced.
- Accommodation — a pitch, a cabin and a glamping tent may be treated differently.
Multiply those together and a single site can have a dozen effective rates running at once. That is why the spreadsheet method quietly breaks.
Where the weekend goes
The manual routine looks like this: at month-end, someone opens the booking list, works out how many chargeable overnights each stay generated, applies the right rate for each guest’s age and the season, subtracts exemptions, and produces one total for the commune. On a busy month that is genuinely a weekend of work — and it is the kind of arithmetic that is wrong often enough to matter.
The failure isn’t laziness. It’s that the rules live in someone’s head and the data lives somewhere else.
The fix: charge it at the source
The clean approach is to attach the Kurtaxe rule to the booking, not to a month-end spreadsheet. When a reservation is made, the system already knows the dates, the party composition and the accommodation type. If it also knows the municipal tariff and the exemptions, it can calculate the tax per overnight, at the moment of booking, and add it to the folio.
Two things fall out of that automatically:
- The guest sees the tax itemised on their bill, correctly, every time.
- You get a running total that is always current — no reconstruction required.
What month-end becomes
Instead of a weekend of arithmetic, month-end becomes a report. Because every overnight was taxed correctly when it happened, the figure the commune wants is already sitting there, itemised and auditable. You read it; you don’t rebuild it.
If a rate changes mid-season — and they do — you update the tariff once, and every future booking picks it up. No memo to staff, no forgotten exemption.
Getting it right the first time
If you automate Kurtaxe, set these up carefully once:
- The exemption rules — children’s age cutoff, seasonal contracts, day visitors.
- The seasonal calendar — the exact dates high-season pricing starts and ends.
- Per-accommodation tariffs — if your commune distinguishes pitches from cabins.
Verify the first month against a manual count, then trust it.
The takeaway
Kurtaxe is hard not because the tax is large, but because the rules are many and the data is scattered. Move the calculation to the point of booking, where all the facts already are, and the month-end weekend collapses into a single figure you simply read off.