Platform Data-Sharing Reports: What You Agree to When You Connect

Connecting a channel is also a data agreement. Knowing which figures leave your account, and on what schedule, is the difference between a surprise and a line item.

Last updated: October 2, 2026

Connecting a channel is a calendar link and a data agreement at the same time. The calendar part you can see; you watch nights fill and rates move. The reporting part is quieter. Certain figures about your listing and your bookings travel to the platform on a schedule you didn't set, and knowing which ones turns a surprise into a line item you can plan around.

Key Takeaways

• A connection carries two things at once. Availability moves one way, and data about your listing moves the other.
• Reports serve the platform's obligations, not yours. They exist so the platform can meet duties placed on it, and they're built from what it already holds.
• The categories are knowable, even when the detail isn't. Booking counts, guest numbers, property details, revenue totals and account identity usually form the set.
• You won't see the submitted file. What you can see is your own record of the same facts, kept well enough to compare.
• The rules that apply are local, and they change. Check your local authority and the platform's current terms rather than working from memory.

What a platform report is for, from their side

It helps to start from the platform's position rather than your own, because a report exists to answer a question somebody else is asking.

In a growing number of places, platforms are required to collect certain information about the hosts and listings they carry, and to pass it on. The requirement sits on the platform, not on you. That distinction explains most of what follows. The platform is gathering a defined set of facts, on a defined schedule, for a defined recipient, and your listing is one row in that.

Which facts, which schedule and which recipient are matters of local law and of the platform's current terms. They differ between places, they change, and they're not something a host can negotiate. So the useful posture isn't to memorise the rules. It's to know the categories, keep your own records clean, and check the current position with your local authority and the platform when it matters.

A report can serve a second purpose, which is the platform's own compliance with how it's allowed to handle data. That part is internal to them. The version that concerns you is the outward one: what leaves your account, in what shape, and how often.

The practical upshot is simple. You aren't being asked to file anything. You're being asked, indirectly, to make sure the facts a platform holds about you are accurate, because those facts are what travel.

The categories of data that typically travel

The detail varies by platform and by jurisdiction. The categories are more stable, and there are five worth recognising.

Booking counts and nights. How many bookings your listing took, and how many nights they covered, over the period in question. This is the spine of most reporting, because it's the figure the platform already computes for its own accounting.

Guest numbers, and sometimes where they came from. How many guests each booking involved, and in some cases their country of residence. That second part is what makes a report about cross-border activity rather than just volume.

Property details and registration. The address and the registration or permit information the platform holds for your listing, where your area requires one. If those details are stale, the report carries the stale version.

Revenue or booking totals. The value the platform records against your listing, whether that's a per-booking figure or a period total. Which of the two it uses is a matter of the platform's current approach.

Account identity. The host or account holder's details on file. This is the category most often out of date, because it's the one that has to be updated when an account changes hands.

Notice what this list isn't. It's not everything you've ever typed into a channel. It's the narrow set of facts a platform needs to satisfy an external duty, gathered from what it already holds about you.

What the host sees, and what they do not

The asymmetry here is worth naming, because it's where most of the confusion sits.

What you can see is your own version of the same facts: your bookings, your nights, your totals, your registration details. If you keep them in one place, you can reconstruct, for any period, roughly what a platform would be able to say about your listing.

What you generally can't see is the file itself. The shape it takes, the aggregation step, the exact date it's sent and the recipient it goes to all sit on the platform's side, and platforms aren't obliged to hand you a copy of what they submit. That's not a reason for alarm. It's a reason to keep your own half accurate, because a discrepancy you can't see is one you can't fix.

There's a consequence for how you keep records. If the platform's submitted figure and your own total disagree, you want that to be something you'd notice. That only happens if your records are complete enough to total, and recent enough to compare. A drawer of unopened statements isn't a record. A single ledger you update monthly is.

Keeping your own records in step with it

Since the submitted file stays on the platform's side, the work is all on yours, and it's smaller than it sounds.

Export your own booking data on a fixed rhythm. Monthly suits most hosts, and the point isn't the file, it's the habit of pulling the same fields every time: dates, guests, nights, and the channel each booking came from. Where a platform gives you its own summary of the same period, keep that alongside your export so the two sit next to each other.

Then keep one ledger, and let it hold what a platform would report. Not a report of your own, just a running record of bookings, nights and totals per channel, updated as the month closes. If a figure in it ever needs explaining to anyone, the ledger is where the explanation comes from.

Check the account details that feed the categories above. Registration and permit details where your area requires them, the address the platform holds, and the identity of the account holder. These are the fields that turn a report wrong quietly, and updating them is a two-minute job when you do it on the same schedule as everything else.

localsbnb.com keeps your credentials on your own machine and masks guest names, phone numbers and ID numbers automatically, with access scoped by domain rather than handed out whole. That matters for exactly this reason: the records a report draws on are the ones you'd want under your control. One boundary is worth stating plainly — LOCALSBNB doesn't file reports or act for you in any reporting duty, and nothing here changes what a platform or an authority requires of you. It's where your own records live, kept accurate so you can compare them with what a platform holds.

FAQ

Do I have to send a report myself?

Not because you connected a channel. The reporting duties that exist sit on the platform, and what it gathers and passes on is set by local law and by the platform's current terms. What falls to you, directly or through your own adviser, is keeping the underlying facts about your listing accurate.

Why can't I see what was sent?

Because the submission is the platform's own filing, not a shared document, and platforms aren't required to give you a copy. What you can do is keep your half of the same facts well enough to reconstruct the picture for any period, which is what makes a discrepancy visible if one appears.

Where do I check what applies to me?

With your local authority and the platform you use, in that order, and at the current date rather than from memory. The categories of data stay fairly stable while the rules around them move, so check the rules when it matters and keep the records continuous in between.

The whole subject shrinks once it's split in two. The platform's half — what it gathers, where it sends it and how often — is set by rules you don't control. Your half is a monthly export, one ledger, and current registration and identity details. localsbnb.com keeps that half under your control, with credentials staying on your machine and guest details masked, so the version of the facts you hold is one you can actually compare against.

---

This article is general guidance for hosts, not legal or tax advice. Which figures a platform reports, to whom, and on what schedule are set by local law and by the platform's current terms, and both differ by place and change over time. Check the current requirements of your local authority and of the platform you use.