Net Payout Before You Accept: One Line in the Booking Workflow

The gross number is the one on the screen. The number that decides whether the booking is worth taking is one subtraction away.

Last updated: October 21, 2026

A request comes in for four nights at a rate that looks fine. You accept, the stay goes well, and three weeks later the payout lands below what you'd assumed. Nothing went wrong. You compared the wrong number to your costs, and one subtraction at the request stage fixes that.

Key Takeaways

• Gross is a headline, net is a decision. The screen shows what the guest pays. Your bank shows what you keep.
• The gap has four sources. Channel fees, payment processing, taxes you collect, and the cost of servicing the stay.
• Net payout isn't profit. Two different subtractions, and the second one is the one that changes your answer.
• Put the check at the request. Thirty seconds before you accept beats an hour at month end.
• A booking below the floor can still be right. The reason has to be named in advance, though, or it's just a habit.

Gross, net, and the gap between

Three numbers sit behind every booking, and hosts routinely use the first one as if it were the third.

Gross is the total the guest pays: nightly rate times nights, plus the cleaning fee, plus anything else itemised. It's the number on the screen and the number in the conversation. It's also the number that has nothing to do with your bank account.

Net payout is what actually arrives: gross minus the channel's fee, minus payment processing, minus any tax you collect and remit on the guest's behalf. It's the number your accountant sees, and it's usually the first time a host looks at it.

Contribution is net payout minus the cost of servicing that specific stay: the turnover, the linen, the consumables, the extra utilities, the welcome items. This is the number that answers "was this booking worth taking", and it's the one almost nobody calculates before accepting.

The three move in different directions. A longer stay usually improves contribution per night, because the turnover spreads over more nights. A discounted stay worsens it twice: once on the rate, once on the fees charged against a smaller total. Extra guests can improve gross and worsen contribution, since linen and cleaning scale with people.

Two rules keep the arithmetic honest. Compare like with like: if you're judging a booking against your costs, use net, not gross. And never compare a single night's net against a monthly average, because the average already carries the empty nights.

Where the gap comes from

Four sources, and each behaves differently.

Channel fees. Every channel that brings a booking takes a cut, and the cut isn't the same everywhere. It varies by platform, region, listing setup and the terms you accepted. So no article should quote a percentage at you; the figure that matters is on your own statement.

Payment processing. Some channels fold this into the fee; others pass it through separately. Either way, it's deducted before the money reaches you, and it applies to the total the guest paid, not to your nightly rate.

Taxes you collect. Occupancy tax, tourist tax, VAT on the accommodation: names and rules differ by jurisdiction, and so does whether the channel collects it for you. Money collected on someone else's behalf isn't revenue, and counting it as revenue overstates a booking fast.

The cost of servicing the stay. This one doesn't touch the payout at all, which is exactly why it gets forgotten. It leaves your account later, in cleaning invoices and utility bills, and by then the booking is a memory.

There's a fifth source that shows up irregularly: adjustments. A refund you granted, a damage waiver, a currency conversion, a chargeback. None of them are predictable, and all of them are visible on the statement if you look at the line level rather than the total.

The gap, then, isn't a proportion you can memorise. It's a set of deductions that move with the booking's shape, its channel and its jurisdiction, which is why the check belongs at the moment of decision.

Adding the check to your workflow

The check is small enough to fit in the pause between reading a request and answering it. Four steps, in order.

Read the total, not the rate. The guest's total includes fees and taxes, and the request screen usually shows it. Start there, because that's the base every deduction is calculated against.

Subtract the known deductions. The channel's fee for this booking, payment processing if it's separate, and any tax you'll remit. If you don't know the exact figure, use the last statement from that channel for a booking of similar size. An estimate from your own statement beats a guess from memory.

Subtract the cost of this stay. One turnover, linen for the number of guests, consumables, and the utilities for the extra nights. If the stay is longer than usual, the turnover is amortised over more nights and the number improves — which is the whole reason long stays can be worth a discount.

Compare to a floor set in advance. Not last month's average, and not the rate you hoped for. The floor is the number below which you'd rather leave the nights empty, chosen while you were calm.

Then write the answer where you'll see it again. One line per booking is enough: nights, channel, gross, net, contribution. After twenty, you'll know which channel and stay length actually pay, and the check becomes a glance.

Where the booking side holds your data, the arithmetic gets easier. On localsbnb.com, read-only questions about your own operating data return figures to check a request against, with no export. Airbnb, Booking.com, Agoda and Trip.com sit in one calendar, so the request and its history are in one place.

One warning about placement. Don't run this at month end, and don't run it after the guest has booked. A check that runs after the decision isn't a check; it's a report. The value sits in the thirty seconds before you accept.

When the answer is still yes

A booking below the floor isn't automatically a no, and hosts who treat the floor as a hard rule leave money on the table.

Four reasons justify a yes, and each has to be named before you accept, not invented afterwards.

It fills a gap that would otherwise be empty. Two nights between two stays that would sit void anyway carry almost no incremental cost, because the turnover was going to happen. Compare against zero, not against your average.

It's the first booking on a new listing. Reviews take time to accumulate, and the first few guests buy you the visibility that later bookings are priced on. That's a real return, just not one that appears in the payout.

It removes a harder problem. A stay that ends on a Tuesday can be worth less than one that ends on a Sunday and lines up with your cleaner's schedule. The contribution calculation doesn't see the schedule; you do.

The guest is one you want back. Repeat guests cost less to serve and cause fewer problems, and a small concession on a first stay can be cheaper than the acquisition cost of the next one.

What doesn't justify a yes: hoping the next booking is better, copying a competitor's rate without checking your own costs, or assuming an empty night is always worse than a cheap one. Those are reflexes, not reasons.

The habit worth building is narrower than it sounds. You're not modelling a business. You're refusing to compare a gross number to a net cost, and you're doing it while the request is still open. That single change moves more decisions than any dashboard does.

FAQ

Is net payout the same as profit?

No. Net payout stops when the money reaches your account. Profit also subtracts the cost of the stay and the fixed costs: mortgage or rent, insurance, software, the empty nights. A healthy net payout can still lose money once the turnover is counted.

Why not just apply a percentage to the gross?

Because the deductions don't behave like a percentage. Fees vary by platform and terms, payment processing is charged on the total, and taxes depend on jurisdiction. A percentage you memorised last year will be wrong on at least one, usually in the direction that flatters the booking.

What about direct bookings?

They usually carry lower fees, which makes them look better on net — and they carry costs the channels absorb, such as payment processing, your own admin time and the marketing that produced the enquiry. Run the same four steps and the comparison becomes fair.

The check is one line in a routine you already have. Run it before you accept, and you'll stop finding the gap three weeks later. If your bookings and numbers already sit together, localsbnb.com is where to keep them, so the next request arrives with its history beside it.

---

This article is general guidance for hosts and isn't legal, tax or insurance advice. Fee structures, tax obligations and what counts as taxable revenue differ by platform, by region and by how a listing is held. Confirm the current terms of each platform you use and the current rules with the competent authority before you rely on a figure.