Compliance Fields on a New Channel: The Ones You Must Fill Before Publishing

On most channels the registration number is no longer a nice-to-have on a profile. It sits between your listing and its first bookable night.

Last updated: September 28, 2026

Adding a channel used to be a matter of copying a listing and watching nights appear. That's no longer how it works. A set of compliance fields now stands between a listing and its first booking, and a channel will hold the listing back until those fields are complete and consistent with the property behind them. Knowing what those fields are, and the order a channel checks them in, is what keeps a new channel from stalling for weeks.

Key Takeaways

• A licence number isn't decoration. It ties the listing to a specific property, and a channel uses it to verify that link.
• It gates the go-live. On channels covered by the EU's 2024/1028 rules, verification happens before publishing, not after.
• Order matters. Channels check identity, then property, then validity, so filling fields out of order invites re-work.
• A half-filled listing is visible. Guests see the gap as hesitation whether or not they can name it.
• Renewal is a re-check trigger. When a licence is replaced, the fields that carry it need updating on every channel.

Which fields your licence number actually feeds

A registration or licence number looks like a single box, and it isn't. On a channel it's the anchor for several fields that have to agree with each other, and filling one without the others produces a listing that looks complete and isn't.

Start with the number itself. It has to be entered in the form the channel expects, matching the issuing authority's own format, because a number entered loosely is a number that fails a check. Then the authority that issued it, which tells the channel who to verify against. Then the property it applies to, which has to match the address and unit details on the listing. Then the validity period, where the channel expects a start and, where the regime issues one, an end.

Around those sit the fields the number doesn't feed directly but that have to stay consistent with it. The property type and capacity, the letting type, and any local category the regime uses. These aren't licence fields, and they're part of the same check, because a licence for one kind of unit sitting on a listing that describes another is exactly the mismatch verification looks for.

This is where a new channel exposes old inconsistencies. If you've run one channel for years and never updated the capacity, that stale figure comes with you. If the details disagree with the registration, the registration wins the check and the listing waits.

So gather the documents in one place, and read the fields off them rather than off your memory. The licence itself, the registration confirmation, and anything that names the property. What you enter should be reproducible from what you can show.

Filling them in the order the channel checks them

A channel doesn't read your fields in the order you filled them. It checks them in a sequence, and a field that fails early stops the ones behind it from being assessed. Filling in that same sequence is what stops the loop of submit, wait, correct and re-submit.

What the channel checks against has a floor in some places. In the European Union, Regulation (EU) 2024/1028 has applied since 20 May 2026, and it requires platforms to verify a registration number before a listing is published (official source, in force). How that lands differs by member state and by platform, so the current local requirement and the platform's current terms decide your case.

The sequence runs from identity outward. First, who you are and the account you're publishing under. Second, which property this is — the address, the unit and the details that distinguish it from another unit at the same address. Third, the registration or licence that applies to that property. Fourth, the dates that registration is valid for. Fifth, the listing details that have to agree with all of the above.

Filling in that order has a benefit beyond the channel's own logic. Each step constrains the next. Once the property is fixed, the licence options narrow. Once the licence is fixed, the validity dates are known.

Where a channel lets you import a listing from another one, that's a helper, not a substitute for the compliance fields. Importing carries across the title, photos, basic capacity and calendar structure from Airbnb, which saves retyping. It doesn't carry the registration details, and it shouldn't — those are entered against the new channel's own verification. Only four channels connect directly here: Airbnb, Booking.com, Agoda and Trip.com. Publishing anywhere else means entering the fields separately, and the same order still applies.

When a listing is held, check the earliest step first rather than the last. A problem in the identity or property fields produces a failure that looks like a problem somewhere else, so hosts often fix the wrong field and stay stuck.

What a half-filled listing looks like from the guest side

A listing whose compliance fields are incomplete usually can't be found at all, which is the clean version of the problem. The messier version is a listing that publishes with fields that don't agree, and that's where guests see it.

Guests can't inspect your registration, and they're not trying to. What they register is inconsistency. A listing that says it sleeps six when the property details say four. An address that appears in two forms in two places. A location description that doesn't match the map pin. None of those is a compliance failure on its own, and together they read as uncertainty about what the property actually is.

That uncertainty shows up in behaviour before it shows up in a booking count. Guests ask more questions before booking, compare more listings, and ask about details a complete listing would have answered. Read that as a signal that the listing is describing itself inconsistently, and go back to the fields.

There's a worse version than inconsistent, and it's a listing going live while a licence is in the wrong state. If a channel verifies before publishing and the verification passes, that's a good sign, not a guarantee the underlying registration is current. The channel checks the number; it doesn't renew your obligations for you. Keeping the fields accurate is what makes the check mean something.

Consistency is the cheap part of all this, and it pays twice. When the registration number, the property details and the listing description all say the same thing, a guest has less to resolve and a channel has less to verify. Every channel you're on shows its own source rate and source status on the calendar at localsbnb.com, which is how you spot the listing where the fields drifted apart.

Re-checking the fields when a licence is renewed

A licence renewal is when the compliance fields go stale, and when hosts are least likely to revisit them, because the renewal feels like the end of the process rather than the start of an update.

Treat the renewal as a re-check trigger, and work through the same sequence you filled the first time. The number, if it changed. The authority, if it changed. The property details, if anything about the unit changed with it. The validity dates, which almost always change. Then the listing details that have to agree.

The reason to redo the whole sequence rather than just the dates is that renewals and property changes often travel together. A renewal is a natural moment to have updated a capacity or added a unit, and any of those moves the fields that have to agree. Fixing only the date leaves the mismatch in place until the next check finds it.

Do it on every channel, not just the one you renewed on. Channels verify independently, and a licence updated on one listing and stale on another is a mismatch that exists only because the update was done once. If you hold several listings, make the renewal a per-listing checklist item rather than a single task.

Then close the loop the way you'd close any renewal: note what changed, the date it changed, and where each channel now stands. That note answers the question the next time a channel holds a listing, and it turns a scramble into a lookup.

FAQ

Do I need a registration number to publish on every channel?

Not necessarily. It depends on the channel and the jurisdiction — some places and platforms require verification before publishing and others don't. Check the current rule where the property sits and the current terms of the channel rather than assuming either way.

What if the channel rejects my licence number?

Check the earliest steps first, because a rejection often traces back to an identity or property field rather than the number itself. Confirm the number's format matches the issuing authority's, and that the listing's property details match the ones the registration names.

Can I just import my Airbnb listing and skip the fields?

Importing is a helper, and only four channels connect directly — Airbnb, Booking.com, Agoda and Trip.com. An import can carry the title, photos, basic capacity and calendar structure, but not the registration details, which are entered against the new channel's own verification.

None of this is complicated, and most of it is done once per channel and then maintained. Fill the fields in the order the channel checks them, keep them consistent with the property they describe, and treat a licence renewal as a prompt to re-check every channel. When you want to see how each listing is standing, localsbnb.com keeps each connected channel's rate and status on one calendar, so a field that's drifted is easier to catch.

---

This article is general guidance for hosts and isn't legal or platform policy advice. Whether a registration number is required, what it must contain and how a channel verifies it are set by local rules and by each platform's current terms, which differ by place and change over time; the current requirements of your local authority and of the platform you're publishing on prevail.