Custom app for the night register and tourist tax
Appfront builds apps that let hotels, holiday parks, campsites and rental providers keep the overnight register the way the municipality requires: per guest the arrival, the departure and the details the register demands, per overnight stay the tourist tax that applies there, exemptions with the reason alongside, and at the end of the period a tax return per municipality that follows directly from the register. So an inspection by the municipality is an export, not a search through bookings and registration cards.
What is an app for the overnight register and tourist tax?
The overnight register is the mandatory record of who stays where: providers of accommodation are legally required to keep a register of their guests, and municipalities levy tourist tax based on overnight stays, each with its own rate, its own exemptions and its own reporting period. An overnight register app records the guest on arrival with the required details, counts the overnight stays per accommodation and per municipality, applies that municipality's rate and exemptions, and produces the tax return for each period from that data.
Without such an app, the record sits on a card at reception or in a field in the booking system, the administration counts the nights from an export at the end of the quarter, looks up the rate for each municipality and estimates the exemptions. For a provider with properties in five municipalities, that means five returns with five calculation methods, and an inspection reveals that the March register is missing the departure dates.
We build custom because the registration has to fit your guests and your municipalities: which details you already have from the booking at arrival, whether guests check in themselves, in which municipalities you have accommodation and which booking system you use. A booking system knows the booking, but not the municipality's register or its exemptions.
Registration on arrival
On check-in, the guest confirms the details the register requires, pre-filled from the booking, on a tablet at reception or on their own phone.
Overnight stays per municipality
Every night per guest and per accommodation, with the rate and exemptions of the municipality where the accommodation is located, so the return per municipality is correct.
Tax return and inspection
For each period, the tax return per municipality from the register, and an export that lets the municipality see, night by night, who stayed and why a night was exempt during an inspection.
How we build your overnight register and tourist tax app
We start with your last tax return and your last inspection: how the nights were counted, which exemptions were applied and what the municipality asked for. The app follows from that.
Which details you currently record on arrival, in which municipalities you have accommodation, which rates and exemptions apply there, how guests check in and which booking system you use.
Per accommodation the municipality, per municipality the rate per night or per person and the exemptions, with effective dates for rate changes.
Check-in on tablet or phone with the details from the booking pre-filled, overnight stays counted automatically, exemptions recorded with a reason.
The return per municipality per period, the audit export, the integration with your accounting, and then maintenance and new municipalities.
What a guest register and tourist tax app actually does
The components below come up for almost every accommodation provider. Which ones you need depends on the number of municipalities and on how your guests check in.
Guest registration
On arrival, confirm the required details, pre-filled from the booking, with a signature or confirmation from the guest and a retention period per municipality.
Night counter
The overnight stays per guest and per accommodation, calculated automatically from arrival and departure, including extended or early departures.
Rates per municipality
The rate per municipality, the basis (per night, per person, percentage) and the exemptions, with effective dates.
Exemptions
Children, residents, business stays or other categories under the municipality's bylaw, recorded with the reason against the guest.
Return per period
The return per municipality with the number of taxable and exempt nights and the amount, ready to submit, with the supporting detail underneath.
Booking system integration
Bookings, guests and accommodations from your booking system, the tax passed back onto the guest's invoice and the return sent to your accounting.
Who we build a guest register and tourist tax app for
The app is intended for accommodation providers for whom registration is mandatory and the tax return is currently manual work per municipality.
Hotels
Daily check-ins and check-outs with many guests. Registration at check-in and the automatic night counter are the core.
Holiday parks and campsites
Long stays, families and seasonal pitches with their own rules. Exemptions per category and counting per accommodation matter most.
Rental organisations across multiple municipalities
Properties spread across municipalities with different rates. What you need is a rate table per municipality and a return per municipality.
B&Bs and small providers
Few accommodations, but the same obligation. Checking in on the guest's phone and a simple return are the core.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology and integrations
This page is about the register and the tax. For settling up with the property owner, see our page on owner statement software, for the hotel as a whole our page on hotel software, and on the municipality's side our page on software for municipal taxes. You can read about our way of working on building custom software.
For central administration with the rules for each municipality and the return for each period, there is our night register and tourist tax software.
Why Appfront for your guest register and tourist tax app?
The guest register is an obligation that only gets noticed when the municipality carries out a check. That is what we build around: registering on arrival, a return drawn from the register, proof for every night.
Registering is checking in
On arrival, the guest confirms what the register requires, pre-filled. No separate card, no field that turns out to be empty later.
The return follows from the register
Nights, rates and exemptions are already there per municipality. The return is a check of a figure the app already has.
The audit is an export
For each night, who stayed, which rate applied and why a night was exempt. The municipality gets a list, not a story.
Security and privacy for a guest register and tourist tax app
The register holds guests' personal data, sometimes including ID details, and the municipality sets requirements for what is recorded and for how long. Access is set up per role and per location: reception registers guests, administration sees the returns, and during an inspection the municipality receives an export for the requested period and nothing more. Data is deleted automatically once the municipality's retention period has passed, and every access is logged.
The app runs in a European data centre, with encrypted storage and daily backups. Integrations with the booking system and the accounting software use their own keys, which can be revoked per integration.
Frequently asked questions about an app for the overnight stay register and tourist tax
Questions that hotels, holiday parks and landlords ask before getting started.
It registers every guest on arrival with the details the register requires, counts the overnight stays per guest and per accommodation, applies the rate and exemptions of the municipality where the accommodation is located, and prepares the return per municipality for each period. In the event of an inspection, it provides an export per night with the supporting evidence.
That is determined by the municipality in its bylaw, and it differs per municipality; usually it covers name, address, arrival and departure, and sometimes nationality or the number of people. The app records which fields are mandatory per municipality, so that the registration on arrival only asks for what is needed there.
Yes. Before arrival, the guest receives a link where they confirm their details, or they do so on arrival on a tablet at reception or on their own phone. Whatever the booking already contains is pre-filled; the guest confirms and adds anything missing.
Each accommodation is assigned to a municipality, and each municipality has its own rate, tax base and exemptions, with effective dates for changes. A landlord with properties in five municipalities gets five returns, each calculated according to its own bylaw, from the same register.
Against the guest, with the category and the reason, for example a child under that municipality's age limit or a resident. The night then counts in the register but not in the tax, and the return and the inspection export show why.
Yes. Bookings, guests and accommodations come from the system you use, the tourist tax goes back onto the guest's invoice and the return goes to the accounting software. We connect to what you already have; the app does not become a second booking system.
Check that first. Many systems calculate tourist tax on the invoice, and that is enough with a single municipality and few exemptions. Custom development makes sense if you operate in several municipalities, if exemptions need to be recorded with a reason, if the register must be deliverable per night during an inspection, or if the return is currently recalculated from exports.
Every overnight stay registered and every return produced from the register?
Tell us how many municipalities you have accommodations in, which booking system you use and how your last inspection or return went. We will show you what the registration, the rate table and the return look like.