Vrbo & Booking.com payout to Excel

Why these two are harder than Airbnb's format

None of these four are unusual for either platform — they're simply the normal shape of how each one documents a booking, and exactly why a host trying to force both into the same spreadsheet template by hand tends to give up somewhere around the third owner statement.

What this doesn't do, stated up front

What's left is narrow, and it's exactly the part that eats an evening every month: turning an owner statement or a commission invoice into a spreadsheet a host can actually work with.

What gets read

flowparse.io

Reading a Vrbo owner statement

A Vrbo owner statement generally covers a booking window rather than a single stay, with each reservation's nightly rate, cleaning fee, service fee and payment-processing fee listed as its own set of lines within the larger document. The net figure at the bottom is the sum across every reservation in that window, not a single stay's payout.

Reading it means parsing every reservation-level block individually rather than treating the document's bottom-line total as the only number worth extracting — the same discipline applied to a multi-reservation Airbnb payout report, adapted to Vrbo's own layout.

Reading a Booking.com commission invoice

In many markets, Booking.com doesn't collect payment from the guest at all — the guest pays the property directly at check-in or check-out — and instead sends the property an invoice afterward for its commission on each completed stay. That invoice is the document to reconcile, and the “reconciliation” is closer to matching an invoice to a bank payment than to a marketplace-style net deposit.

Where Booking.com does handle payment collection — increasingly common through its own payments product in some markets — the document looks more like a conventional payout report, and is read the same way as Vrbo's.

flowparse.io

Why the same platform can look different by market

A host with properties in more than one country quickly discovers that neither Vrbo nor Booking.com issues a single, universal document format. Vrbo's owner statement layout varies slightly depending on which regional entity processes the payout, and Booking.com's invoicing structure depends heavily on whether the property is in a market where the platform collects payment directly or one where the guest still pays at the property.

None of that variation is arbitrary — it follows from local payment regulation and how each platform has rolled out its own payments product market by market. But it does mean a host comparing a statement from one property against a statement from another, in a different country, shouldn't assume the two will share a layout just because they came from the same platform.

Reading each document on its own terms rather than assuming a fixed template is exactly what handles this correctly without a host needing to track which regional format applies to which property themselves.

How a line finds its reservation

Matching runs on three signals together, not any single one alone, because any one signal in isolation is too weak to trust on its own.

A line that lines up on all three — a total that matches the source document's figure, a reference consistent with the platform's known pattern, arriving near the expected date — is a confident match. A line that lines up on only one is exactly the case flagged for a person to confirm rather than resolved silently.

flowparse.io

A statement and an invoice, structured

A Vrbo owner statement covering three reservations in one window, run through the structuring process.

The $2,050 deposit on the bank statement, taken alone, gives no indication it actually represents three separate reservations at three separate nightly rates and fee structures. Structured into Excel, each reservation lands in its own row, with the statement total confirmed to equal the sum of all three — a spreadsheet a host can actually filter, sort and check against a booking calendar.

flowparse.io

How it works

flowparse.io

Running both platforms side by side

A host listing the same property on both Vrbo and Booking.com ends up with two structurally different source documents describing overlapping calendar availability. Structuring both into the same spreadsheet shape — one row per reservation, the same column set regardless of source platform — makes it possible to compare occupancy and net revenue across the two directly, something neither platform's own dashboard is built to do since each only shows its own bookings.

That combined view is often the first time a host sees, in one place, which platform is actually producing better net revenue per night for a specific property — a comparison that's effectively impossible from either platform's dashboard alone.

Attributing lines across several listings

A host running more than one property through the same Vrbo or Booking.com account faces the same attribution problem as with Airbnb — several reservations, sometimes combined into one statement or invoice, with no obvious indication of how much belongs to which listing without reading every line.

Where the source document itself identifies which reservation belongs to which property — which both platforms generally do, at least by listing name or internal ID — that attribution carries through into the structured spreadsheet, so a multi-property host gets a per-listing breakdown alongside the consolidated total.

What happens to what doesn't match

A bank deposit or payment that doesn't match any line in the owner statement or invoice isn't discarded or hidden — it's kept as its own visible group, with the amount, date and whatever reference exists, so the host can look at it directly instead of it disappearing into a structured total that quietly absorbed a mistake.

In practice, unmatched items turn out to be one of a small number of things: a payment from a reservation not yet included in the current batch of documents, a delayed transfer, or occasionally a genuinely unrelated deposit. Each has a specific, quick fix once it's visible.

flowparse.io

Who this is for

This isn't a connected-account sync

Worth being precise about the boundary. This doesn't connect to your Vrbo owner dashboard or your Booking.com extranet — there's no login, no OAuth, no ongoing sync. You download the owner statement or invoice yourself, the same way you already download a bank statement, and upload it here.

flowparse.io

How this differs from the Airbnb-focused tool

Airbnb's payout report is structured closely enough to a conventional net-deposit format that it gets its own dedicated reconciliation flow — see short-term rental payout reconciliation for the Airbnb-focused version, including a side-by-side comparison of how Airbnb, Vrbo and Booking.com each structure a payout.

A host running properties on all three platforms typically uses both tools together — the Airbnb reconciliation for that platform's per-reservation payouts, and this page for the Vrbo owner statement and the Booking.com invoice — with results that roll up into the same overall picture of portfolio revenue.

Handling a mid-statement adjustment

Occasionally a Vrbo owner statement or a Booking.com invoice includes an adjustment line that doesn't correspond to any current reservation at all — a correction for a prior period's commission miscalculation, a one-off goodwill credit issued to smooth over a guest complaint, or a retroactive fee change applied after the fact. None of these are errors on the host's part, but each one breaks the simple assumption that every line in the document maps cleanly to a reservation in the current period.

Rather than forcing an adjustment line into a reservation it doesn't actually belong to, it's read and kept as its own labeled row — visible, traceable to the statement it came from, and clearly distinguished from ordinary reservation-level fees. A host reviewing the spreadsheet sees exactly which rows are adjustments and can decide whether each one needs a closer look.

In practice, adjustment lines are uncommon enough that most statements have none at all, but common enough — a handful of times a year for an active multi-property host — that pretending they don't exist would leave real money unaccounted for on the statements where they do appear.

How often to run this

Vrbo owner statements typically arrive on a period basis rather than per reservation, so matching your reconciliation cadence to the statement schedule — weekly or monthly, depending on your account setup — is the simplest rule that works. Booking.com invoices tend to arrive per completed stay or on a monthly billing cycle, whichever the property's account uses.

For a host running both platforms, batching the reconciliation on a fixed monthly rhythm is usually easier to sustain than chasing each platform's individual schedule — slightly less immediate, but far more likely to actually happen consistently through a busy season.

What accuracy actually looks like

A useful way to think about matching accuracy isn't a single percentage — it's the shape of the distribution across the three confidence levels. A host with a handful of straightforward reservations sees most lines land at high confidence, with only a small tail needing review. A host with a messier document — a statement covering an unusual booking window, an invoice with an adjustment line — sees a larger medium-confidence tail, which means more review time, not necessarily more errors.

In practice, most hosts with a mix of ordinary reservations see somewhere between 85% and 95% of lines land at high confidence on a given statement or invoice, with the rest split between a quick medium-confidence confirm and a small number of genuine discrepancies worth investigating individually.

Privacy

Full details are on the security page.

Frequently asked questions

Keep reading