Operator-side compliance

Compliance tooling for the taxes and registrations your platforms only partly handle.

Registration tracking, tourist and occupancy tax computed per booking to each jurisdiction's own rules, channel-aware collection status, and filing-ready reports.

Built for operators in more than one market, where the platforms collect some of it, some of the time, and the liability stays yours.

The situation

Every market you operate in has its own registration requirement, its own tax base and rate, and its own filing rhythm. Airbnb collects and remits in some jurisdictions and not in others. Booking.com collects in fewer, and in many markets what it collects still has to be remitted by you. Direct bookings are entirely yours. Across a portfolio spread over three or four markets, nobody at the operation can say, booking by booking, who collected what and what remains to be filed, and the answer changes every time a city amends its rules.

Underneath the paperwork problem sits a money problem. Collected tourist tax is not revenue. It is held funds, someone else's money sitting in your account until filing day, and in most operators' books it is commingled with everything else from the day it arrives. An operator can be current on every filing and still be running the risk that matters, because the tax that was collected and not yet remitted has no separate existence anywhere in the accounts.

Enforcement has stopped being theoretical. Spain's €64 million fine against Airbnb was upheld on appeal in March 2026. Amsterdam charges 12.5 percent, the highest percentage tourist tax in Europe. In the US, a broker's license has been revoked over commingled lodging taxes. And in most jurisdictions the obligation stays with the operator even where a platform collects, so the platform's coverage narrows your workload without moving your liability.

What we build

The operator-side compliance layer, built for the markets you actually operate in.

01

Registration and permit tracking per property, per jurisdiction, with renewal dates that surface before they expire.

02

Tax computed per booking to the rules of the booking's own jurisdiction, rate, base, and exemptions, held as maintainable data your team or your advisor keeps current rather than logic hardcoded and left to go stale.

03

Channel-aware collection status. Which channel collected which tax on which booking, and what remains yours to remit, answered per booking instead of guessed per quarter.

04

A tax ledger that keeps collected tax segregated as third-party funds from the day it arrives, the same discipline as owner money.

05

Filing-ready reports and a remittance calendar per jurisdiction, matching each market's own rhythm.

06

An audit trail from booking to filing, so any figure on a return traces back to the bookings that produced it.

You will not find a rate table on this page. Rates and bases change mid-year, and the rules belong inside the build as data, current and yours, not on a marketing page going stale.

Why not platform collection or generic tax software

Platform auto-collection is real and worth keeping wherever it exists, and it covers some channels, some taxes, in some places. The gaps between those are yours, and so is the liability inside them. Generic tax software is built for sales tax and VAT flows, not for lodging registrations, per-booking occupancy rules, and the question of which channel already collected what. And the spreadsheet that currently answers all of this is the real status quo, carrying the risk unseen until a filing is challenged. We build the layer that makes the per-booking answer automatic, on top of the channels and the PMS you already run.

How the build goes

01

Show us your markets and your channels.

Free fit call. We map, jurisdiction by jurisdiction, what the platforms handle and what falls to you. If your existing setup already covers it, we will tell you on the first call.

02

A $2K discovery, one week.

We confirm against your real booking and channel data which taxes are actually being collected for you and which are not, and hand you a firm fixed quote. Credited in full toward the sprint if you proceed.

03

A working prototype in two weeks.

One market's bookings computed to that market's rules and checked against a filing you know was right.

04

The decision point.

The remaining markets, the tax ledger, and the remittance calendar. Fixed scope, fixed price, your code.

Proof

Compliance money is other people's money, and that is the discipline we are proven at. We built the trust accounting of Vacation Rental Connect, in production for fourteen years, keeping owner money split correctly and separate from the platform's own at every step. Collected-but-unremitted tax asks for exactly that ledger discipline, applied to a different creditor. And VRC already handles taxes and fees as their own numbers: every booking carries its tax separately from the room total, and reservation taxes and fees are charged, receipted, and reported on their own statement line, reversed on cancellation, tracked apart from the owner's money. The per-jurisdiction computation, collection status, and remittance calendar this page describes are the extension of that discipline, built to your markets.

Owner Money, Right to the Cent

Questions operators ask about compliance

In some jurisdictions Airbnb collects and remits, in others it collects only some of the applicable taxes, and in many it does nothing at all. Booking.com covers fewer markets, and in many of them the tax it collects still has to be remitted by you. Direct bookings are always entirely yours. The booking-by-booking answer to who collected what is exactly what this tooling exists to give you.

Tell us which markets you operate in and which channels you sell on. We will map what the platforms handle, what falls to you, and what a first sprint would fix.

Free call focused on your operation or your platform, not a generic pitch. If a custom build is not the right answer for your situation, we will say so.