Ask a hotel controller what eats the most unplanned time in a given month, and bank reconciliation usually makes the list. It’s not because the concept is complicated, but because a single hotel’s cash touches more disconnected systems than almost any other business of comparable size. A retail company reconciles a bank account against a general ledger and calls it done. A hotel reconciles cash drops, credit card batches, OTA payouts, POS settlements, PMS folio postings, and payroll withdrawals, often across a dozen bank accounts and several properties.
This piece breaks down that process end to end: what actually needs to be matched, where it typically falls apart, and what a practical daily or periodic workflow looks like when it’s built to catch exceptions early instead of letting them pile up into a month-end scramble.
Why Hotel Bank Reconciliation Is Harder Than Standard Back-Office Reconciliation
In most industries, reconciliation is a two-party comparison: what your books say, versus what the bank says. In hospitality, that same comparison has to survive contact with several intermediary systems before the cash ever lands in the account.
A single guest folio might involve a room charge posted by the PMS, an incidental charge run through the POS, a portion paid by a corporate card, a portion covered by an OTA prepayment, and a tax calculation layered on top. By the time it settles, it may arrive in the bank account as one lump batch deposit with no line-level detail at all. Multiply that by every guest, every outlet, every day, across a portfolio of properties each with their own bank accounts, and the reconciliation problem stops being “does the number match” and becomes “which of the six systems introduced the difference, and where.”
This is also a timing problem, not just a data problem. A card transaction authorized on Friday night might not settle and deposit until Monday. An OTA might not remit funds for a stay until weeks after the guest has checked out. That’s normal hospitality cash flow, but if your reconciliation process doesn’t account for the lag, it looks exactly like one, and someone has to spend time proving it isn’t.
The Main Data Sources and Exception Points Hotel Teams Must Manage
A practical reconciliation process starts with knowing exactly which sources feed the bank account and where each one is most likely to introduce a mismatch.
- PMS folio revenue. Room revenue, taxes, and resort fees post from the property management system, but PMS revenue codes don’t always map cleanly to your chart of accounts, and posting errors at check-out or during night audit are a routine source of variance.
- POS outlet transactions. Restaurant, bar, spa, and other outlet revenue has to reconcile separately, and it’s easy for POS batch totals to disagree with what actually settles, especially around discounts, comps, and split payments.
- Credit card and merchant settlements. This is one of the most common failure points: authorization amounts, settled amounts, processor fees, and chargebacks rarely land in the bank on the same day, or in the same batch structure, as they were recorded in the PMS or POS.
- OTA payouts and commissions. Booking.com, Expedia, and similar channels often pay in bulk, net of commission, on their own schedule and late cancellations or early departures can result in a hotel being billed full commission on a booking that never fully materialized as revenue.
- Cash deposits. Physical cash drops from front desk and outlets still have to be verified against deposit slips and bank confirmations, and timing gaps between the drop and the bank’s recorded deposit are common.
- Payroll and AP disbursements. Payroll withdrawals and vendor payments (checks, ACH, virtual cards) need to match the general ledger, with particular attention to outstanding checks and payments initiated but not yet cleared.
- Intercompany transfers. In multi-property portfolios, funds moving between entities need to reconcile on both sides. A transfer recorded in one property’s books but not yet reflected in another’s is a common source of quiet, lingering variances. Every one of these is a potential exception point on its own. Add them up across a multi-property portfolio and it’s easy to see why reconciliation, done manually, consumes so many hours every month.
Every one of these is a potential exception point on its own. Add them up across a multi-property portfolio and it’s easy to see why reconciliation, done manually, consumes so many hours every month.
A Practical Workflow for Daily or Periodic Reconciliation
The controllers who keep this under control tend to follow a similar rhythm, whether they’re doing it manually or with automation support.
1. Start from the night audit. Once the PMS closes out the day, it produces a revenue summary by department, i.e. rooms, F&B, spa, and any other operating departments. This becomes the baseline every other system gets checked against.
2. Match POS and ancillary revenue to the PMS summary same-day. Outlet totals should tie back to what was posted through the PMS before the day is more than 24–48 hours old. Waiting longer makes it dramatically harder to trace a discrepancy back to its source, because supporting detail (receipts, shift reports, void logs) becomes harder to retrieve the further out you get.
3. Reconcile cash deposits against bank confirmations daily. Physical cash drops should be checked against deposit slips and the bank’s posted deposit as soon as it clears. This is the fastest-moving and easiest-to-lose-track-of category if it’s allowed to batch up.
4. Reconcile credit card settlements on a rolling basis, not at month-end. Because settlement timing rarely lines up with the original transaction date, this category needs its own cadence, typically a few times a week, matching settled batches against what was recorded at the point of sale, and flagging anything still outstanding after a defined number of days.
5. Reconcile OTA payouts against booking and cancellation activity. This is best done on whatever cycle the OTA pays on (often monthly or bi-weekly), cross-checking commission charged against actual completed stays, not just reservations made.
6. True up payroll and AP disbursements against the bank statement. Confirm cleared payments match the payroll register and AP ledger, and separately track anything issued but not yet cleared, so outstanding items don’t get miscounted as missing.
7. Close out intercompany transfers before consolidating. Every transfer between properties or entities needs to be confirmed on both the sending and receiving side before portfolio-level numbers get finalized. Reconcile elimination entries between properties.
8. Review exceptions as a distinct, named list, not a general “cleanup” bucket. Anything that didn’t match by the end of each cycle should be logged individually, with an owner and an expected resolution date, rather than left to be rediscovered at month-end.
Done consistently, this daily-and-weekly rhythm turns month-end bank reconciliation into a review of a short, known exception list, not a from-scratch rebuild of the entire month.
Common Causes of Unreconciled Balances and Close Delays
Most persistent reconciliation problems trace back to a handful of recurring causes:
- Batching work until month-end. The longer a discrepancy sits, the harder it is to trace because supporting documentation gets harder to pull, and the people who could explain a specific transaction may not remember it.
- Settlement timing mismatches. Treating a timing difference (a transaction that simply hasn’t cleared yet) as if it were an error wastes investigation time on things that will resolve themselves.
- Manual re-keying between systems. Every manual transfer of a number from one system to another is a chance for a transposition error or a missed decimal point.
- Inconsistent account mapping across properties. In a multi-property portfolio, if each hotel maps revenue and payment types to the chart of accounts slightly differently, consolidated reconciliation becomes an exercise in reconciling the mappings themselves before you can even reconcile the cash.
- No clear ownership of exceptions. When a discrepancy doesn’t have a named owner and a deadline, it tends to sit until someone is forced to deal with it which is usually during close, under time pressure.
- Disconnected systems with no shared source of truth. When PMS, POS, payroll, and the general ledger don’t talk to each other automatically, someone has to be the integration layer manually, and that role is expensive, slow, and error-prone.
How Automation Changes Reconciliation Speed, Control, and Audit Readiness
The workflow above is sound whether it’s done by hand or with software, but the manual version is genuinely brutal at scale. A Controller running that process across a multi-property portfolio using spreadsheets and manual bank downloads is, in effect, running an integration project every single day.
This is where a platform like Data Plus’ DP Finance changes the economics of the process rather than just the tooling. Bank feeds and internal records
match automatically, with the system doing the line-by-line comparison work and surfacing only what genuinely needs a human look. This turns reconciliation into a single-click, exception-first process rather than a manual matching exercise. Recurring items like prepayment amortization and standing journal entries convert automatically instead of being re-created by hand every period, and scheduled imports sync data directly from PMS, POS, and Time & Attendance systems so the “which system introduced the difference” question gets answered by the platform instead of by hours of manual tracing.
That shift matters for three distinct reasons:
- Speed. Exceptions get surfaced same-day instead of discovered weeks later, which means the daily-and-weekly workflow above is actually sustainable instead of aspirational.
- Control. Automated matching reduces the chance that a genuine error such asa duplicate payment, an unauthorized transaction, or an OTA overcharge, hides inside a pile of unreviewed timing differences.
- Audit readiness. A platform that reconciles continuously and keeps a running exception log produces a much cleaner audit trail than a process reconstructed retroactively at month-end, because the resolution of each item is documented close to when it happened, not weeks later from memory.
How Reconciliation Quality Affects Month-End Close and Owner Reporting
Reconciliation isn’t a standalone task. It’s usually the load-bearing wall underneath the entire close. If cash isn’t reconciled cleanly, nothing built on top of it can be trusted: the P&L carries unexplained variances, departmental profitability numbers are only as good as the revenue postings feeding them, and any KPI calculated from that data inherits the same uncertainty.
This is exactly where slow or error-prone reconciliation shows up most visibly to the people outside the finance team. Owners and asset managers who see inconsistent numbers month over month start to question the reliability of the reporting itself, not just the reconciliation process behind it. In a management-company relationship, that’s a credibility cost that compounds over time.
Conversely, a portfolio with a disciplined, largely automated reconciliation process tends to close faster and with fewer late adjustments, which is precisely why close-speed improvements (DP Finance customers typically see closes accelerate by 5–7 days) trace back to reconciliation quality as much as any other single factor. When the bank reconciliation is already done by the time month-end arrives, because it happened continuously throughout the month, close becomes a review of finished work instead of a race to finish it.
Fewer Manual Exceptions, Starting With Your Next Close
If your team is still spending the first week of every month chasing down unmatched deposits, unexplained card settlement gaps, or OTA commission disputes, that’s a solvable systems problem, not an inevitable feature of hotel accounting. DP Finance brings bank feeds, PMS and POS data, payroll, and AP activity into one platform so reconciliation happens continuously instead of in a month-end scramble with exceptions surfaced automatically instead of discovered the hard way.
If you want to see what that looks like against your own portfolio’s reconciliation volume, talk to the Data Plus team about where your current process is creating the most manual work.
