Tourist Tax Management for Local Authorities for Odoo Online — SaaS version with no Python code: tourist tax software (actual-occupancy basis) for a tourist office: rate schedule by accommodation type and rating, capped percentage calculation for unrated accommodation, 10% departmental surcharge, detection of non-filers.
Overview
Tourist Tax — DYONYSOS
App for the municipal or inter-municipal tourist office that collects the tourist tax, on Odoo 19 Community — from the local authority's point of view, not the accommodation provider's.
Also searched as: tourist tax software, actual-basis tourist tax, quarterly tourist tax return, unclassified percentage per night, additional departmental tax, reminders to non-declaring accommodation providers.
Tourist tax on actual stays is self-declared, and that is the whole point. For each period (most often the quarter), the accommodation provider declares its number of taxable overnight stays, its exemptions and, if it is not rated, the cost per person per night. The local authority invoices nothing: it checks what is declared, collects, and above all knows who has not declared — the number one problem of every tourist office, and the module makes it visible at a glance, period by period.
The rate depends on the type and classification, and takes two forms. A 4-star hotel, a 2-star furnished rental and a 3-star campsite have a fixed rate per night and per person, voted as a grid. An unclassified accommodation has no fixed rate: its tax is a percentage of the cost of the night per person, capped at the highest rate in the grid — the rule in force since 2019, the one that catches out the most accommodation providers and the most local authorities. The module calculates both forms and refuses to validate a percentage-based return until the cost of the night is entered, stating what to do.
Exemptions are exhaustive and declared separately. Minors, seasonal workers employed in the municipality, people in emergency accommodation or temporary rehousing: the host counts them, they never enter the calculation, and they remain visible separately on the return — so that the local authority can respond to an audit.
The 10% departmental surcharge is calculated and tracked separately. It is added to the municipal share and passed on to the département: the two amounts are never mixed, otherwise the transfer is wrong.
Membership of the tourist office is not the tax. An accommodation provider can join and benefit from tourism promotion without being up to date with their tourist tax, and vice versa: the module tracks the two separately, never one through the other.
What the module does not do
No online filing service for accommodation providers: the local authority's staff enter the data, based on what the provider sends them. No interface with booking platforms (Airbnb, Booking…) that collect the tax on behalf of the municipality: those amounts are entered like any other return. No tourism website or destination marketing. No payment collection: the amount due is calculated and tracked, its collection is handled by the local authority's revenue office (régie de recettes). No electronic filing with the DGFiP.
Two roles
Front desk agent: entry of declarations received from accommodation providers, reminders. Manager: rate grid, periods, collection, accommodation providers.
Specifications
| Price | €259 excl. VAT |
|---|---|
| License | OPL-1 |
| Odoo series | 19.0: published on the Odoo Apps Store; 20.0: published on the Odoo Apps Store |
| Version | 1.0.0 |
| Edition | Odoo Online (SaaS) and Odoo.sh |
| Technical name | dyo_public_tourisme_online |
| Domain | Municipalities and public sector |
Price excluding VAT as displayed on the Odoo Apps Store; purchase and installation are done on the Store or through your Omnifloo instance.