How to keep hotel accounts (a practical guide for error-free management)

Q: How often do I need to reconcile cash register, POS and payment gateways?

As a minimum, reconcile cash register and POS on a daily basis if there is relevant movement, because differences are best corrected when the shift is recent and there are supporting documents. Payment gateways should be reconciled at least weekly (or more if the volume is high). The longer the delay, the more costly it is to reconstruct the case.

Reliable hotel accounting is not just about “recording invoices” at the end of the month. For owners, managers and decision-makers, the real goal is to have a traceable and repeatable system that connects daily operations (bookings, collections, consumption, returns) with a consistent accounting closure, without relying on manual adjustments that are difficult to explain.

In this guide you will find an operational approach: what data to capture, what processes to repeat (daily, weekly and monthly) and what controls reduce slippage and margin losses. It does not replace the judgement of your accountant or advisor: where there are judgement decisions (revenue recognition, local taxation, required documentation), it is prudent to validate with a professional according to your country and business model.

The 5 “pain points” that complicate hotel accounting (and how to solve them)

Multi-source revenue (direct/OTA/company/agency)

The risk is to mix channels and duplicate revenues. Solution: channel bookings and collections with clear rules per channel, and closing reports that separate “origin of sale” and “method of collection”.

Advances and deposits

Charged before the service is provided, and then dates, persons or conditions change. Solution: Internal policies and an account/transaction structure that differentiates “charged” from “recognised income”, with documentary support.

Mixed payments (cash/card/card/swipe/transfer)

When the method is not properly recorded, differences appear. Solution: daily reconciliation, POS/gateway reconciliation and mandatory “payment method” for each transaction.

Commissions and net/gross from OTAs

One of the most frequent errors is to register gross and commission inconsistently (or duplicate). Solution: define by channel whether “hotel charging” or “OTA charging”, and always reflect commission and charging method with the same criteria.

Departmental sales (accommodation, F&B, extras)

If everything is mixed in one bag, there is no margin control. Solution: departmentalise revenues and costs, and ensure that PMS/POS/ERP feed the same “hubs” consistently.

Design your accounting structure: departments, cost centres and accounts you do need

A hotel usually requires two levels of tidiness:

Financial accounting (compliance and accounting statements).
Analytical/management accounting (area profitability and operational control).

For decision making, the second level is the one that avoids “surprises” when the business grows or diversifies. A practical and fairly universal scheme separates:

Income: Accommodation, Catering (F&B), Events/MICE, SPA/Wellness, Other income (parking, late check-out, amenities, etc.).
Costs: Direct costs (external cleaning, laundry, amenities), Personnel costs, Overheads (supplies, technology, maintenance, rents/general services, etc.).

Indicative table to “ground” data and sources (adjust it to your reality):

Department	Examples of revenues/costs	Usual data source
Accommodation	rooms, upgrades, early/late	PMS
Catering (F&B)	breakfast, bar, restaurant	POS + PMS (room charges)
Events/MICE	rooms, coffee breaks, packages	PMS/CRM + billing/ERP
SPA/Wellness	treatments, vouchers, products	POS/agenda + ERP
Other income	parking, transfers, extras	PMS/ERP
Direct costs	laundry, amenities, commissions	ERP + PMS/OTA reporting
Staff	payroll, extras, shifts	ERP/HR
Overheads	supplies, maintenance, licences	ERP

The idea is not to complicate: it is that each income and cost always “falls” in the same place so that it can be compared month by month.

How to map revenues and costs to “sites” without complicating things for you

Start small and grow with maturity. Rule of thumb: 4-6 well-defined sites are usually sufficient for the first few months (or in small/medium hotels). Examples:

Boutique hotel with minimal F&B: Accommodation, Breakfasts, Extras, Direct costs, Staff, Overheads.
Aparthotel with longer stays: Accommodation, Cleaning/services, Parking/Extras, Direct costs, Staff, Overheads.

Simplification criteria that work:

If an area contributes little volume, group it under “Other income” until it makes sense to separate it.
Avoid centres “on a whim”: a centre only deserves to exist if it makes choices (price, costs, opening hours, staff, investment).
Changing centres every quarter breaks comparability. Better to keep them stable and document when and why they are expanded.

What internal policies should you define before opening (or before switching systems)?

Before “moving data”, define internal rules. Otherwise, the accounting is filled with manual entries without traceability. Minimum recommended policies:

Internal recognition criteria: When do you consider “sale” for reporting purposes: when booking, when hosting, when charging (and how do you report it consistently)?.
Deposit/advance processing: when they are ordered, where they are registered, when they are converted to final collection or returned.
Returns and adjustments: reasons admitted, minimum documentation, and approval circuit.
No-shows/cancellations: how they are documented, what generates the charge (if applicable) and how it is reflected in reporting.
Box cuts and closures: who closes, at what time, what to do if proof is missing.
Who authorises sensitive changes: off-rate discounts, reversal of charges, changes of payment method, credit/credit notes.

Daily flow that avoids slippage: from day-end closing to accounting entry

When the daily routine is good, the monthly closing is no longer a “reconstruction”. A typical (adaptable) operational flow would be:

Closing of the day in PMS (night audit or equivalent): block the operational day and generate baseline reports.
Review of arrivals/departures/no-shows/cancellations: matching occupied rooms and internal documentation.
Cash countCash, vouchers, invitations, differences and registered motive.
POS and gateway accountingTotal for the day by terminal/gateway vs. PMS/POS reports.
Review of issued invoices/receipts: numbering, cancellations, subscriptions and exchange support.
Control of accounts receivable (companies/agencies/groups): outstanding charges, internal credit limits, and approval documentation.
Export/accounting: dumped into ERP or recorded in accounts on a stable basis (ideally automated and auditable).

The key point for management: each step must leave a trace (report, justification, comment, user and date). Without traceability, correcting becomes expensive.

Tonnage and reconciliation: what to check each day vs. each week

Daily (minimum viable):

Cash differences and documented explanation.
Total POS vs. PMS/POS (per terminal if applicable).
Payments to be validated (pre-authorisations, payment links, transfers).
Returns/day passes with reason and approval.
Vouchers/vouchers consumed (if applicable) and their support.

Weekly (control without saturating the team):

Reconciliation of gateways (settlements vs. sales).
Review of OTA commissions and associated charges.
Tipping (if applicable): internal rules and matching with POS/shifts.
Analysis of manual adjustments: how many, why and by whom.
Review of accounts receivable: ageing and follow-up.

Bookings and receipts: how to record advances, deposits, no-shows and refunds

The typical confusion is to confuse “charging” with “recognising revenue”. Operationally, it is useful to separate concepts:

Advance payment: pre-collection linked to a future booking/stay.
Refundable deposit: warranty (e.g. damage), which should not be treated as a sale unless it is enforced as a matter of policy.
Final collection: settlement at check-out or at the end of the stay.
No-show/cancellation with charge: collection conditioned by an accepted and documented policy.

Practical table for aligning bracket and register (without going into regulations):

Case	Supporting document	Movement that generates	Where to register
Advance for reservation	confirmation + proof of payment	prior charge associated with a reservation	PMS + ERP/accounting
Refundable deposit	policy + justification	warranty (and return if applicable)	PMS/ERP (depending on circuit)
No-show with charge	policy + evidence of non-arrival	no-show fee	PMS (cargo) + ERP
Cancellation with refund	application + voucher	full/partial refund	gateway/TPV + PMS/ERP
Change of dates/holder	request + traceability	reallocation of the advance	PMS (adjustment) + ERP

The management recommendation: defines which fields are mandatory (reason, reference, authoriser) for the adjustment to be auditable.

OTAs: commissions, net/gross models and how to avoid duplications

Scenario A: the hotel charges the guest.

The revenue is recorded as a sale of the hotel and the OTA invoices/retains its commission according to agreement.
Typical risk: recording the gross income and, in addition, re-recording the OTA charge (duplicity).

Scenario B: the OTA charges the guest and settles with the hotel.

The hotel receives a net transfer (or settlement) and must correctly reflect which part is revenue and which part is commission/service.
Typical risk: recording only the net as “revenue”, losing visibility of the cost of distribution and distorting margins.

Good practices to avoid errors:

Define by channel “who gets paid” and “how the commission is reflected”.
Ensure that PMS/ERP distinguish between method of charging y source channel.
Reconcile OTA settlements with bookings and stays, not only with the bank.

Hotel billing: documents, series and operational traceability

Hotel billing usually follows an operational circuit: reservation → check-in → consumptions → check-out → final document (invoice/receipt) → collection/conciliation. To be auditable:

Keep numbering and series clear (by document type or channel if applicable).
Avoid “delete”: use cancellations and credit notes/credit memos with reason and support.
Ensure that any changes (discount, upgrade, extra charge) are traceable: who made them, when and why.
It establishes a single criterion for company/agency invoices: tax data, authorisations, payment conditions and minimum documentation.

The exact document requirements, series or formalities vary by country and hotel situation; when in doubt, it is prudent to validate with local tax/accounting advice.

In this circuit, having a PMS that accompanies the hotel's real operations is key. With LEAN Hotel System, invoicing is not limited to check-out: it is possible to issue invoices at any time during the stay, adapting to long stays, corporate clients or specific administrative needs.In addition, the system allows you to edit, regroup or unify invoices when the operation requires it (for example, several charges in a single final document), always maintaining accounting consistency. In the event of any modification, LEAN automatically generates the corresponding corrective invoices, ensuring that the information is always up to date and that the complete traceability of the process is maintained.

This allows the team to work flexibly without losing control or accounting rigour, which is particularly relevant in environments where changes during the stay are commonplace.

Technology and integrations: how to bring PMS, POS, gateways and ERP together to automate accounting

Hotel accounting becomes sustainable when data flows without manual re-entry. A cloud PMS with integrations (channel manager/booking engine, payment gateways, POS and ERP) enables:

Reduce “handwritten” entries and transcription errors.
Standardise closures and reconciliations.
Maintain user/date/reason traceability in settings.
Consistently export data to the ERP.

In an integrated ecosystem, for example with a PMS such as LEAN Hotel System, a POS (Tilby/TCPos) and an ERP, the value is not in the name, but in the fact that the daily closing and the accounting dump are repeatable, and that the reconciliation is based on consistent data, not on “fixing Excel”.

What data must travel automatically for accounting to be reliable

Income by department/centre.
Taxes or fees (if applicable) broken down according to the defined criteria.
Payment methods and transaction references (POS/gateway).
Commissions and distribution costs (per channel).
Gratuities (if applicable) with defined internal treatment.
Accounts receivable and conditions (companies/agencies).
Settings with reason, user and date.
Link between document (invoice/receipt) and transaction (booking/stay/consumption).

Signs that you are doing too much manual bookkeeping

Closures with frequent “unexplained” differences.
Parallel Excel to find out “the truth” of the business.
Recurrent adjustments without documented reason.
Reconciliations that are only done at the end of the month.
Unreserved“ invoices or charges without traceability.
Dependence on a specific person to balance.
Discrepancies between PMS, POS, bank and accounting that are normalised as “business as usual”.

Financial scorecard: essential reports for decision making (not just for “compliance”)

For management, useful accounting is accounting that improves decisions. Recommended reports/indicators (with their purpose):
- P&L by department: see which areas generate margin and which ones consume it.
- GOP and GOPPAR: measure operational result and compare by available room.
- RevPAR and ADR (operational): understand business performance, not to be confused with accounting recognition.
- Weekly cash flow: anticipate cash tensions and plan payments/collections.
- Ageing of balances (AR): monitoring accounts receivable from companies/agencies and risk of non-payment.
- Cost of distribution: commissions, net/gross and profitability by channel.
- Forecast vs. actual: detect deviations early and correct before closure.
- Closing incidents: number and type of settings (process fault signal).

ADR/RevPAR are business performance and occupancy metrics; accounting requires consistency in accrual and recognition according to agreed internal criteria. The key is to define rules: which date rules (stay, charge, document issuance) and keep them stable. If you change rules, document the change and separate comparatives so as not to distort trends.

Internal control and security: permits, adjustments and auditing without slowing down operations

Control is not bureaucracy: it protects the business and the team. Recommended basic controls:

Segregation of duties: The fee-earner should not be able to adjust or override without control.
Permissions by role: reception, supervision, administration, management; each role with clear boundaries.
Audit trail: user, date, reason and purpose of the change.
Locked locks: limit retroactive modifications or require authorisation.
Periodic review: weekly/monthly sampling of credit memos, discounts, changes of payment method and credit invoices.

Good control reduces unintentional errors and also avoids internal conflicts due to lack of traceability.

Recommended implementation plan (30 days): from “chaos” to stable system

Week 1 - Diagnosis and sources

Inventory of systems and sources (PMS, POS, gateway, bank, ERP).
Flow map: from booking to collection to document.
List of “vanishing points”: where to rewrite by hand and why.

Week 2 - Structure and policies

Define 4-6 initial centres/departments.
Document minimum policies (advances, returns, no-shows, adjustments).
Design closure reports and responsible persons per step.

Week 3 - Routine and reconciliation

Implement daily closure (1-7) with checklist.
Single reconciliation template (POS/gateway/bank vs. PMS/POS).
Operational training for front desk and shift managers.

Week 4 - Integrations and validation

Tests of export/dumping to ERP (or standardised accounting register).
Testing of critical scenarios: OTA charges, returns, no-shows, invoice to company.
Review with external accounting/consultancy to validate criteria and documentation.

The key deliverable on day 30 is not “to have it perfect”, but a system that closes with traceability and improves week by week.

Common mistakes in implementation (and how to avoid them)

Set up accounts/centres without criteria → start simple and document rules.
Do not define advance/credit policies → agree them in advance and require reason/support.
Do not train reception → train in closures and in “mandatory fields” of collection/adjustment.
Ignore OTAs and settlements → define scenarios per channel and reconcile weekly.
Do not test reconciliation before trading → test with real cases and historical data.
Mix revenue KPIs with accounting → separate “operational” vs “accounting” in reporting.
Depend on Excel for the truth → use Excel only as a control, not as the main system.
Permits too open → clear roles and active audit trail from day one.

Frequently asked questions on how to keep hotel accounts

Do I need a specialised hotel accountant or is a generalist consultancy sufficient?

It depends on the complexity: if you work with OTAs, several departments (F&B, events), high volume and multiple charging methods, it helps a lot to have hotel experience to avoid errors in judgement and reconciliation. A generalist consultancy can work if your internal processes and data (PMS/POS/ERP) are well structured.

How do I account for advances and reserve deposits without “inflating” income?

The key is to separate “collection” from “recognised income” and to document consistent internal criteria (e.g. recognise per stay and treat advances as balances until the service is rendered). Operationally, always record the support of the charge and its link to the booking. The final criteria should be validated with your local tax advisor/accountant.

What do I do with OTA commissions and platform managed collections?

First define the scenario: if you collect, record the revenue and commission as distribution cost; if the OTA collects, record the settlement correctly, avoiding treating the net as “total revenue”. The main risk is duplicating sales or losing commission visibility. PMS/ERP should reflect channel, charging method and commission consistently.

How often do I need to reconcile cash register, POS and payment gateways?

At the very least, it reconciles cash desk and POS on a daily basis if there is relevant movement, because differences are best corrected when the shift is recent and there are supporting documents. Payment gateways should at least be reconciled with the following weekly (or more if the volume is high). The longer it takes, the more expensive it is to reconstruct the cause.

What reports should a hotel manager review each week?

A practical weekly package includes: 7-14 days cash flow, P&L summarised by department, ageing of company/agency balances, distribution cost by channel, variances vs budget/forecast and a closing incident report (adjustments, credits and differences). The objective is to detect variances early, not “when the month closes”.

What software do I need as a minimum to keep good accounting records for a hotel?

In layers: a PMS as the operational core, an invoicing/ERP system for accounting and reporting, POS if there is F&B, and POS/gateway connection to register and reconcile receivables. The important thing is integration and traceability (user, date, reason), rather than the number of tools. An integrated cloud approach reduces manual work.

When should I consult a tax advisor/accountant?

When you change revenue recognition criteria, open a new unit or service (F&B, events, SPA), design complex packages, manage local taxes/fees, face inspection or audit, or integrate/change systems (PMS, ERP, POS, gateway). At these points, a professional validation avoids later corrections with manual entries and documentary risk.

REQUEST YOUR DEMO TODAY

Discover how Lean Hotel System can transform your hotel business