Vacation rental invoice template: one payment, three units

How do I invoice one payment that covers three units?

Group the reservations inside your property system first, then raise one invoice from the grouped guest accounts instead of three separate ones. A group booking is one guest paying once for more than one of your units over the same dates, and it lands in an ordinary week at an eight-unit serviced-apartment building, at a small inn holding a wedding party, or at a row of cabins taken by one family.

Guesty's page on creating a group reservation for multiple listings books several listings under one payer and makes you pick a billing mode when you set the reservation up: Charge per property splits the payment per listing, Charge all properties takes the lot on one. One detail matters if you hand this off to a bookkeeper: an Accounting user cannot pick Charge all properties at all, so that role has to select Per property every time. The page has no recent date stamp on it, so walk the flow once yourself before you plan a season around it. Other property systems reach the same result a different way, so confirm how yours handles it before you rely on it.

Every row above came off the vendor's own documentation, checked on October 2026.

Should the guest get one invoice or three?

Send the guest one invoice, with every unit itemized on its own line. The guest's card shows one charge, so one document is the only thing they can reconcile it against, and your own books still have to know which unit earned which slice. An accommodation line is the row that charges the nights for a single unit, named by the unit number or its address. A pooled tax line is one tax row covering the whole invoice rather than a tax row repeated under each unit.

Lodgify's 2026 invoice guidance for hosts says to list occupancy taxes and mandatory fees as their own line items so guests see exactly what they are paying for. On a group booking that matters more, because the tax total is the number a company's finance department queries first.

Three invoices against one card charge will work too, though the guest then has to match three separate documents against the single line that shows up on their statement. Cloudbeds lets you email a group invoice to just one guest's bill rather than the whole group's invoice. This is useful when a company has paid for two of the three rooms and the third guest is covering her own stay. It backfires when someone picks the single-guest send by mistake.

What the invoice shows the guest and what your own records track

The accommodation lines go first, one per unit, then the fees, then one tax line, then the total that matches the charge on the card. Copy this layout into your own invoicing tool and fill in your own numbers:

Accommodation, unit [A]        [nights] nights @ $[rate]    $[amount]
Accommodation, unit [B]        [nights] nights @ $[rate]    $[amount]
Accommodation, unit [C]        [nights] nights @ $[rate]    $[amount]
Cleaning, [N] units at $[rate]                               $[amount]
Occupancy tax at [your rate]%                                $[amount]
Total charged to one card                                    $[amount]

Add another accommodation line for every additional unit in the group. Here is that same layout filled in for a group of three units over four nights, invoiced the way the rule above describes.

Use your own tax rate there rather than mine; 11 percent is a placeholder and the rate changes by county. Name the unit on every accommodation line even when all three are yours and all three are in the same building. QuickBooks says the same thing in its own property management invoice guidance: when more than one property is billed to the same payer, put the specific property or unit address on each line to avoid confusion.

No template covers the other half of this: tracking which reservation sits behind each line. Do that in a mapping row of your own: track each reservation against the invoice it was billed on, and carry only the amount it actually contributed. You don't need special software for this. A tab in the spreadsheet you already keep works, so does a custom field in your property system if it has one, or a line in whatever tool you invoice from. Just keep the reservation and the amount together, in a place you control.

Each unit's amount is its own nights plus its own cleaning plus its share of the tax, and the three amounts add back to the invoice total exactly. If they do not add back, fix the split before the invoice goes out. It matters even on a booking this small, because a mapping row that carries the wrong number is what turns one cancellation into a refund against the whole group instead of just the unit that dropped.

Free templates are fine for what they cover. Lodgify publishes a downloadable vacation rental invoice template, and QuickBooks publishes its property management template as Excel, Word and PDF downloads. Neither addresses a booking that spans more than one unit, which is the part you add by hand.

What happens if one unit in the group cancels?

You refund that one unit's own total off the single charge and leave the other two alone. Stripe's own refunds documentation states that you can issue more than one refund against a charge as long as the total refunded never exceeds the original charge amount, which is exactly what a group booking needs: the charge stays whole and you take pieces out of it as units drop. Stripe also never returns its processing fee from the original transaction, so the fee on the refunded amount stays with you, and the amount you take out comes off that unit's mapping row.

Stripe will process the second refund without complaint, because it is a legal refund against that charge. Reconciliation is where this catches up with you weeks later: you match what the platforms paid out against what you actually booked, and two paid stays show no money behind them, leaving you to trace back why.

Your property system will offer you a route for the cancellation itself, and the routes are not identical. OwnerRez's cancel or refund page gives four: follow the policy for no refund, a partial refund, a full refund, or update the charges yourself. The same page notes that Stripe does not support a void, so a Stripe-paid booking can only be refunded. Whichever you pick, the number you type comes off the mapping row, so it has to be right before anyone cancels anything. The tax half of the question sits with who collects occupancy tax and when it applies to a cancelled stay, and more of the cancellation and tax edge cases are covered in the FAQ.

What we settled on for our own apartments

MINT @Naschmarkt is ours, 18 serviced apartments in five apartment types in Vienna, and group bookings there are families and small company trips. When we designed how those get billed we landed on one invoice, one accommodation line per unit, one pooled tax line, and each mapping row still carries only its own total, never the group total, so a single cancellation cannot bill the whole group.

Our own team at Ekamoira built the piece that carries it: we kept easybill, the invoicing tool we already used, put a thin bridge between the property system and it, and left Stripe to take the direct payments. The bridge only has to know which reservation owns which amount, every time, including on the day a finalized invoice turns out to be wrong.

Lodgify's guidance for hosts is to never edit an invoice you have already sent, and to void it and issue a corrected one with a new number. Where the rules allow the other route, correcting a finalized invoice in place doesn't burn a single new legal invoice number. We used that live on a batch of Airbnb invoices, and cancel and reissue is the expensive alternative. Our invoice numbering sits under Austrian rules and yours does not, so take that as the question to ask your accountant rather than as permission. Smoobu's US invoicing guide notes that the IRS prescribes no single federal invoice format at all, which gives a US operator more room here than we have. The rest of what we have built and what it produced is on the MINT case.

When does this approach not fit your property?

Your software cannot put two units on one booking in the first place, a limitation more common than the feature lists suggest. OwnerRez staff answered a 2023 request on its own community forum plainly:

"As you've noted, it's not possible to create a quote (or a booking) that covers more than one OwnerRez property. Because of the fundamental design of not just OwnerRez, but most of the listing channels as well, it'll likely be a long time if ever before this changes."

The operator who asked had more than 10 properties in the account and was building a separate quote for each one, slow for them and confusing for the guest. Operators in that position end up invoicing several bookings together after the fact. Billing one group reservation isn't an option for them, so Amenitiz or Sirvoy style grouping is the closest thing to it.

This same approach breaks down in a handful of other situations too:

• The group wants to pay on separate cards. OwnerRez's split payments page says it does not support this automatically: you confirm the booking on one guest's card, then collect from the others individually, which means you are now billing several separate payments, not one, so invoice each one on its own and skip the pooled tax line.
• Each unit is a separate company paying separately. You now have three customers of record, not one, and an invoice addressed to just one of them will not satisfy the other two's own accounting, no matter how convenient a single charge seemed at the time.
• Your reporting has to be per unit and your system reports per listing. Hostaway's multi-unit listings bill per unit while analytics, listing financials and occupancy reports stay at listing level, so a group invoice built on top of that hides the per-unit view you need at year end.

Hostaway's own multi-unit help pages never say whether a guest can book more than one unit in a single reservation through its booking engine, so ask them directly before you design around it.

Test this on your next group booking

Test your own setup against the last group booking you took, whether it already closed out or is still on the books.

1. Pull the last group booking you took on one payment and open the invoice the guest received.
2. Count the accommodation lines. There should be one per unit, each naming its unit, and one tax line for the whole document.
3. Open your own records and find the row for each reservation in that group. Read the amount on each one out loud.
4. Add the three amounts. If they do not come to the invoice total, stop and fix them before anything else today.
5. If any row shows the full group total, that booking is one cancellation away from refunding everybody. Correct it now, then check the last three group bookings for the same thing.
6. Keep the invoice and the mapping together where you can find them. The IRS suggests keeping business records for three years and at least four years for employment tax records, and a group invoice is the one you will be asked to explain.

If you would rather have the invoicing, the direct booking site and the tracking built over the property system you already run, that build takes about three weeks and you can book the call.