The Monthly Close in Forty Minutes: Reading a Payout Report Line by Line

A payout report is not a bank statement. Every line is an instruction somebody wrote, and the odd ones are where the money went.

Last updated: September 24, 2026

A payout report doesn't describe money that arrived. It reconstructs money that was decided: what the reservations billed, what somebody adjusted afterwards, and what came off before the transfer. Read it in that order — sections first, then the five line types behind nearly every "this doesn't add up" message, then a calendar check that catches the one error a bank statement can't show you.

Key Takeaways

• Three sections, in order. What billed, what was adjusted, what was deducted. Read them in that sequence.
• Five line types. Gross, pass-through fees, refunds, deductions, and the reference-less adjustment.
• Reconcile nights, not money. A missing stay hides in the nights figure long before it shows in the total.
• Dates belong to two clocks. A stay can bill in one period and refund in the next, and both lines are correct.
• Close on a fixed day. Same day, same snapshot, or next month's comparison is fiction.

What the report is actually reconstructing, and where its three sections come from

The first thing to unlearn is that a payout is a list of payments. It isn't. It's a reconstruction of decisions, assembled from three places that don't speak to each other on the same schedule.

Section one: what reservations billed. Nightly rate times nights, plus whatever the booking carried — cleaning, extra guests, a length-of-stay adjustment. This section is the only one that reads like revenue, and it's the one hosts check first, which is a shame, because it's the one that's least often wrong.

Section two: what was adjusted afterwards. Cancellations, partial refunds, no-shows, a rate corrected after a complaint, a guest moved between units. These lines are negative or mixed, they carry the date of the decision rather than the date of the stay, and they're why a month never looks like the calendar it came from.

Section three: what came off before the transfer. Channel deductions, taxes collected or withheld under local arrangements, and any adjustment carried forward from a previous period. This is where the money actually went, and it's the section most hosts skip because the numbers are small and the labels are unfamiliar.

Read the sections in that order and stop reading them as one column. The total at the bottom answers a question nobody asked. The three sections answer "where did my month go".

One structural warning. When a channel alters its fee or settlement structure, the transition can leave two structures running at once. A US regional operator's blog described exactly that — mixed accounting during a fee-and-settlement changeover, in a September 2026 account (one-party claim, industry blog, checked 23 September 2026). One operator on one change, not a prediction about yours. But it's why a month that looks wrong deserves a look at what changed, not just at what was paid.

The five line types that account for almost every query, and how to read each

Gross reservation lines. Nights, rate, and the fees attached to the booking. Check the nights first, always. A stay billed for four nights when the guest stayed three is a calendar problem wearing a finance costume, and it won't be visible in the total.

Pass-through fees. Cleaning, extra-guest charges, anything the guest paid that you either keep or hand on. The question isn't how much, it's whose it is. A cleaning fee you hand to a cleaner belongs in a different column from one that's yours, and mixing them makes the month look better than it was.

Cancellations and refunds. Negative lines dated when the decision was made, not when the guest would have slept. A cancellation from last month's booking can land in this month's report and be entirely correct. Before you chase it, match it to a reservation reference.

Channel deductions. What the booking channel took. Here's the arithmetic, as an example rather than as a rate. If a stay bills at €400 and the line shows €60, that's 15% of that stay. Compute the percentage from the line, then read the real figure off the channel's own current billing, because it's theirs to set and it changes. Never carry a percentage forward from one period to the next.

The adjustment with no reference. A line with an amount, a date, and nothing tying it to a booking. This is the one worth an email, and it's the only one. Everything else you can resolve from your own records.

Short version: nights tell you if a stay went missing, references tell you which stay a negative line belongs to, and a bare number with no reference is the only line needing somebody else's help.

Reconciling against the calendar: the check that catches a missing stay

Here's the check. It takes ten minutes and it's the one that finds the expensive error.

Take the nights figure from section one. Then count the nights actually occupied in the same period — sold, not blocked, not held, not a gap you closed for maintenance. The two should agree. When they don't, three things cause it, in order of likelihood.

A stay that never reached the report. Booked direct, added by hand, or a channel that isn't reflected where you're looking. This is the one that costs real money, and it's invisible from the bank because nothing was ever billed.

A cancellation that left the calendar occupied. The guest cancelled, the money was refunded, and the dates stayed blocked. Nights on the calendar exceed nights billed. Nobody has lost money, but your occupancy for the month is a lie.

A stay straddling the boundary. Arrived on the last night of the month, left in the next. The nights land in one period or the other depending on how the report is cut. Not an error — a convention, and you need to know which one yours uses.

Run it per unit, not per account. A portfolio-level nights figure can balance perfectly while one unit is over and another is under, and you'll never see either.

The calendar side of that check is the part that takes longest when bookings live in four places. Reservations from Airbnb, Booking.com, Agoda and Trip.com sit on one grid at localsbnb.com, so the count is a read rather than a reconstruction across four logins.

Closing the month so next month's comparison means something

A close isn't an accounting ritual. It's what makes next month's numbers comparable, and comparability is the only reason to keep any of this.

Four things, on a fixed day. Pick it and never move it — the fifth of the following month suits most hosts, because the channel lines have settled by then. Move the date and you silently change what's in the period, which alone can produce a swing you'll spend an afternoon explaining.

Snapshot the three figures. Occupancy, average daily rate, and revenue per available room, read on the close date. Those three sit on the Home dashboard at LOCALSBNB, which is the point of a dashboard: the snapshot is the same shape every month, so a change is a change rather than a redefinition.

Write the anomalies down. One line each: what looked odd, what you concluded, what you did. Three lines is enough, and it's what turns next year's close from an investigation into a comparison. Unrecorded anomalies get investigated twice.

Carry forward anything unresolved. List an open line with its date, so next month expects it. An open item that arrives as a surprise gets investigated from scratch.

Then stop. The close is finished when the note is written, not when every question is answered. Chasing a €12 discrepancy past forty minutes costs more than €12.

FAQ

My payout doesn't match what I think I sold. Where do I start?

With nights, not money. Count occupied nights for the period and compare them to the nights billed in section one. If those agree and the total still looks wrong, it's a fee-treatment or deduction question rather than a missing booking — a smaller problem.

Why is a refund from last month appearing in this month's report?

Because lines carry the date of the decision, not the date of the stay. A cancellation agreed in this period produces a negative line in this period, even when the booking was made months earlier. Match it to a reservation reference before you treat it as an error.

Should I close on the first of the month or the last day?

Whichever you'll actually do, as long as it never moves. Earlier means some channel lines haven't landed yet; later means you're reconciling further from the month. Pick a day you can defend and hold it, because consistency is the whole value.

Three sections, five line types, one calendar check, one fixed day. That's the close, and it fits in forty minutes once the note exists — the first run costs more, because you're still deciding your own conventions. Start with nights rather than totals, and let a bare number with no reference be the only thing you escalate. If you'd rather count occupied nights on one grid than rebuild them from four extranets, that grid is at localsbnb.com.

---

Fee structures, settlement arrangements, tax treatment and payout timing are set by each channel and by local rules, and they change; the percentage shown here is a worked example used to demonstrate the arithmetic, not a rate. Read every figure off the current billing for the channel and period you're closing. This is general guidance for hosts and isn't tax, legal or accounting advice.