If you operate staff accommodation and sell bed capacity to corporate clients, your invoice is the product. Everything else — the rooms, the catering, the maintenance — is delivery. The invoice is where the commercial relationship is settled, disputed, and either renewed or lost.
It is also where most providers quietly lose money.
This article covers how accommodation billing actually works at scale, and the four places revenue leaks.
Why accommodation billing is harder than it looks
Residential property billing is straightforward: a tenancy, a monthly rent, a fixed period. Accommodation billing has none of that stability.
- A resident checks in on the 8th and out on the 22nd
- Another transfers between rooms — at different rates — on the 15th
- A third goes on leave for eleven days, and whether the bed is held or released changes the charge
- A crew of 40 arrives mid-month against a contract with a 200-bed minimum commitment
- Catering and laundry consumption vary per person per day
- All of it has to land on one VAT-compliant invoice per client, per period
Doing this in spreadsheets is possible. Doing it accurately, repeatedly, at thousands of beds, is not.
The unit that makes it work: the stay segment
The concept worth understanding is the stay segment — one billing record per uninterrupted stay, rather than one record per person per day.
When a resident checks in, a segment opens. When anything changes their billing basis — a check-out, a room transfer, a rate change, a leave period — the segment closes and a new one opens.
Two things follow from this.
It's dramatically more efficient. A per-day ledger for 20,000 beds generates 600,000 rows a month. A segment model generates a fraction of that — around 96% less data in our own implementation — while carrying the same billing information.
It handles mid-period changes cleanly. A resident who moves from a standard room to a premium room on the 15th produces two segments at two rates, and the invoice splits correctly without anyone calculating pro-rata by hand.
Our contract and billing module is built on this model.
The four places revenue leaks
1. Minimum-commitment shortfalls that nobody applies
Most corporate accommodation contracts carry a minimum guaranteed occupancy — the client commits to 200 beds whether they fill them or not. When actual occupancy comes in at 170, the contract entitles you to bill the 30-bed shortfall.
In practice this is frequently missed, because catching it requires someone to compare actual occupancy against contracted commitment for every client, every period, before invoicing. That comparison is exactly the kind of manual reconciliation that gets skipped in a busy month-end.
It should be automatic: the invoice run compares actuals against the commitment and applies the top-up as a line item. Not a report someone reads and acts on — a calculation inside the billing process.
2. Damage that never reaches an invoice
A resident checks out. The room has damage. The cost is assessed, noted, and absorbed.
The break is almost always structural rather than intentional: the person who inspects the room and the person who raises the invoice are different people using different systems, and nothing connects them. A clearance gate at check-out — inspection, damage valuation, then automatic routing to the client's next invoice, itemised and traceable back to the inspection — closes it. The traceability matters as much as the charge, because unsupported damage charges get disputed and written off.
3. Service consumption billed approximately
Catering and laundry are where estimates creep in. Meals are counted roughly, laundry is bundled, and the charge becomes a negotiated figure rather than a measured one.
The alternative is consumption captured at the point of service — a scan at the serving line producing an entitled or not-entitled verdict per resident, laundry tracked against per-contract entitlements with chargeable extras recorded as they occur. That data then feeds the same invoice as accommodation, rather than arriving as a separate estimate. Resident services covers the operational side of this.
Providers who move from estimated to measured service billing routinely find they were under-recovering.
4. Occupancy that the invoice never sees
Late-recorded movements. A transfer entered three days after it happened. A return from leave nobody logged. Each is small; in aggregate, across thousands of bed-nights, they are material — and they always err in the client's favour, because unrecorded occupancy is unbilled occupancy.
The fix is architectural rather than procedural: derive billing from movement records rather than maintaining a separate billing dataset. If check-in, transfer and check-out events are the billing input, there is no reconciliation step to fall behind on.
The question that decides disputes: can you rebuild it?
Every accommodation provider eventually faces the same moment. A client disputes three months of invoices. Or a rate was configured wrong in March and nobody noticed until June. Or an audit asks you to demonstrate that a period was billed correctly.
The honest answer in most operations is that you cannot rebuild it. The invoice was produced by a process that has since moved on, the underlying data has been edited, and reconstructing what should have been billed means a spreadsheet exercise that takes weeks and satisfies nobody.
The structural fix is to treat the billing sub-ledger as derived rather than authored — fully re-derivable from the movement journal and rate history at any time. If billing is a calculation over movements rather than a separate dataset, any period can be rebuilt from source: preview the corrected result, compare it against what was issued, then apply — scoped to a property or block, without touching a single operational record.
That distinction matters more than it sounds. It's the difference between billing you trust and billing you can prove. When a client challenges a quarter, you can rebuild it in front of them rather than promising to investigate.
The revenue you're not billing at all
One category deserves separate mention because it's usually invisible: non-residential space.
Most camps contain shops, offices, stores, workshops and service units. These are frequently occupied by contractors or service providers under informal arrangements — a handshake, a fixed monthly figure, sometimes nothing at all. They sit outside the accommodation billing system entirely because they aren't beds.
Handled properly, these units are classified so they never appear as available bed space, allocated to a company and department for a defined period at a monthly rent, and billed on a rent roll alongside the accommodation pack. Every rate or occupant change closes the old record and opens a new one, so the history is never rewritten.
Providers who formalise this often find it's a meaningful revenue line that had been running on goodwill.
Getting the invoice itself right
Beyond accuracy, corporate clients have expectations about the document:
- One consolidated invoice covering accommodation, catering, laundry, utilities and recoveries — not four separate bills
- Approval before issue, with drafts clearly watermarked so an unapproved invoice can never be mistaken for a final one
- Correct VAT treatment applied consistently, with your TRN on a properly formatted tax invoice
- Supporting detail on request — the client's finance team will ask which residents, which rooms, which nights
- Deposits and statements — security deposits and advances tracked per customer and adjusted against invoices, with ageing visible
That last point causes more friction than it should. A client disputing an invoice wants the underlying occupancy detail. If producing it takes three days of manual work, the dispute escalates before you've answered it.
The stronger answer is not to produce it faster but to stop being the bottleneck. A client-facing portal where corporate customers view their own statements and invoices removes the request entirely — invited users, email-OTP login, no passwords to manage. Service requests raised through it still land in your staff approval queue before becoming operational work, so nothing bypasses your team. Clients get transparency; you don't get a helpdesk.
The upstream problem: selling what you don't have
Billing accuracy starts before the contract exists.
If your sales team quotes bed capacity from a spreadsheet that doesn't reflect live inventory, you will oversell. Overselling produces one of two outcomes, both expensive: you fail to deliver, or you deliver by displacing another client.
Quotations that read live bed availability — counting only genuinely sellable beds, with reservations and maintenance holds already subtracted — make overselling structurally impossible rather than a matter of diligence. That's the logic behind our CRM and quotation engine, and it's why we built quoting on the same inventory operations runs on rather than a separate sales database.
The same applies to discounting. Where deals are priced below a defined floor, that should escalate for approval automatically regardless of the discount percentage — because a 5% discount on an already-thin rate can be more damaging than 20% on a healthy one.
A quick self-assessment
Seven questions. Each “no” is a leak.
- Does your invoice run apply minimum-occupancy top-ups automatically?
- Do checkout damage valuations reach the invoice without manual re-entry?
- Is catering billed on measured consumption rather than estimates?
- Can you produce bed-night detail behind any invoice line in minutes?
- Do your sales quotes read live availability, so beds can never be oversold?
- Could you rebuild a disputed quarter from source data — and prove the result?
- Is every commercial unit in your camps — shops, offices, workshops — actually on a rent roll?