Hotel Payment Reconciliation: Workflow & Exception Guide

Written by: Kelly Campbell, Vice President of Marketing, Stayntouch

Key Takeaways

• Hotel payment reconciliation is a daily exception-management discipline that matches PMS folios against processor settlements, OTA payouts, and bank deposits so every dollar earned is collected.

• The night audit serves as the daily control point and follows a structured checklist that includes exporting reports, reconciling payments, matching OTA payouts, clearing exceptions, and documenting adjustments before closing the business date.

• Common exceptions include settlement timing differences, OTA virtual credit card shortfalls, commission invoice mismatches, FX differences, duplicate payments, unposted outlet charges, and chargebacks that require systematic tracking and resolution.

• Automation reduces reconciliation time by posting charges automatically, running night audit in minutes rather than hours, and applying taxes instantly to cut manual errors and exception volume.

• Stayntouch is a cloud-native PMS that connects with accounting systems including M3, Sage Intacct, QuickBooks Online, and Xero to streamline hotel payment reconciliation.

Talk With Stayntouch About Automating Reconciliation

Daily Hotel Payment Reconciliation Checklist

The night audit is the end-of-day process that closes out the day’s transactions, posts room charges and taxes, and rolls the system into the next business date. It acts as the daily control point. The controller or finance lead validates the full picture monthly. The sequence below gives the night audit team a defensible routine and gives the controller a clean handoff.

1. Export the PMS payment report and folio-level payment detail. Pull the day’s revenue summary by department, including rooms, food and beverage (F&B), spa, and other outlets. Export the folio-level payment detail that shows how each charge was settled.

2. Reconcile PMS payments to processor settlement batches. Because PMS revenue codes do not always map cleanly to the chart of accounts, and posting errors at checkout or during night audit are a routine source of variance, you should match gross card revenue to processor batches and flag any difference before moving forward.

3. Reconcile OTA payouts and virtual credit card (VCC) settlements to reservations. OTA virtual credit cards are single-use card numbers issued by the OTA to pay the hotel the net amount after commission. Match each VCC to its reservation, confirm the face value, and charge within the activation window. Flag any shortfall where the folio total exceeds the VCC amount.

4. Match bank deposits to processor settlements. Card processors deduct interchange and processing fees before the deposit posts, so the batch total reflects gross sales while the deposit reflects gross sales minus fees. The two figures rarely match penny for penny. Classify the difference as fees, timing, or a genuine exception before closing the step.

5. Clear the exception queue. Work through every flagged item from the current day. Assign an owner and a resolution deadline to anything that cannot be resolved before the business date closes.

6. Post adjustments and document each one. Give every adjustment a reference such as folio number, booking ID, and reason. This documentation lets the controller validate it at month-end without reconstructing the context from memory.

7. Close the night audit. Once all clean cases are matched and exceptions are documented, close the business date. Legacy PMS platforms built around a nightly batch close could not post new transactions while the audit ran. Cloud-native platforms post charges in real time throughout the day, so the close becomes a reconciliation checkpoint rather than a processing bottleneck.

8. Carry unresolved items to the weekly review. Move any exception that survives the night audit to a named exception log with an aging date. When a discrepancy has a named owner and deadline, it is less likely to sit until close and get handled under time pressure.

Get a Sample Night Audit Reconciliation Checklist

The Hotel Payment Reconciliation Exception Taxonomy

Once the daily checklist is in place, the next step is giving each exception a name. The single biggest gap in most hotel reconciliation processes is the absence of a named exception taxonomy. When discrepancies land in a general “cleanup” bucket, they age invisibly until month-end. The table below names each exception type, its likely cause, and its resolution path, giving the night audit a shared vocabulary that turns vague cleanup items into trackable, ownable tasks. Following the table, each type receives a brief explanation of what causes it and how the night audit catches it.

Settlement Timing Differences

A charge can post in the PMS today, settle with the payment processor two days later, and hit the bank statement a day after that. Each timing gap becomes a reconciling item that needs an explanation. The night audit catches these by comparing the PMS payment report to the processor batch report and classifying any difference as a timing item with an expected settlement date.

OTA Virtual Credit Card Shortfalls

The OTA issues a single-use card for the net amount after commission. If the folio total exceeds that amount due to incidentals, an extended stay, or a rate change, the hotel cannot collect the difference from the VCC. When a booking changes after VCC issuance, such as an early checkout or shortened stay, the OTA may not update the funding amount. That gap creates underfunded or mismatched cards that leave a balance the hotel cannot collect. The night audit catches shortfalls by matching each VCC face value to the corresponding folio total at check-in, before the guest departs.

OTA Commission Invoice Mismatches

OTA commission rates are typically 15% to 25% depending on program tier, geography, and rate plan, and are calculated server-side by the OTA on net room revenue with adjustments for shortened stays, cancellations, and resort fees that may or may not be commissionable. Commission invoices arrive two to four weeks after the stay, and the bank settlement line does not identify which booking it corresponds to. Without automation, line-level matching remains a manual discipline.

FX Differences

FX differences are one of the reconciliation challenges that arise because data arrives from OTAs, agents, direct bookings, cards, and local payment methods at different times and in different formats. They must be isolated from commission differences and booked as foreign-exchange gain or loss rather than folded into revenue.

Duplicate Payments

When a payment provider approves a transaction but the response to the PMS fails, the hotel holds two conflicting records. The provider shows payment succeeded while the PMS shows no payment recorded. The SOP should require staff to establish the transaction state at the provider before retrying anything.

Unposted Outlet Charges

POS outlet transactions for restaurant, bar, spa, and other outlets must reconcile separately from PMS folios. POS batch totals can disagree with what actually settles, especially around discounts, comps, and split payments. The night audit catches these by comparing each outlet’s daily-Z report to the charges posted to in-house folios before the business date closes.

OTA Commission Reconciliation: Matching Invoices To Bookings And Payouts

OTA commission reconciliation runs on a different timeline and touches more systems than standard payment reconciliation. The standard workflow has five steps:

1. Pull the OTA settlement report from the OTA extranet for the relevant period.

2. Match each line to a PMS reservation by booking ID and stay date.

3. Gross up the net payout by adding commission back to confirm the full room revenue figure.

4. Investigate differences such as cancellations, no-shows, rate mismatches, and shortened stays where commission was billed on the original booking value rather than the revenue actually earned.

5. File disputes within the OTA’s dispute window. Booking.com’s extranet operates a rolling 48-hour close window: every cancelled or no-show reservation has a 48-hour countdown from the scheduled checkout, after which the commission is locked in and unrecoverable.

Commission reconciliation often frustrates staff new to hotel finance for three structural reasons. OTA commission invoices arrive two to four weeks after the stay, while bank settlements of the corresponding VCC charges arrive two to five business days after the transaction, so three to six weeks typically pass between the original booking and the point the commission is booked in the accounting system. The bank settlement line also does not identify which booking it corresponds to. Commission rules then vary by rate plan, geography, and program tier. Resort fees, destination fees, and similar surcharges may or may not be commissionable depending on the OTA’s contract terms. When the OTA applies commission to a fee that should have been excluded, the hotel overpays, and the error is detectable only by reading the commission invoice line by line against the original contract.

A monthly commission review should run on a calendar-driven cadence. A structured 30-day OTA reclaim cadence places invoice-versus-PMS reconciliation on the 5th of the month, with dispute filing for flagged items running from the 6th to the 10th. Flag any variance above a defined threshold and file disputes before the OTA’s window closes. VCCs expire, so once a card expires the window to capture that revenue is gone. Finding errors at month-end may already fall outside the recovery window and turn the amount into a write-off.

Who Owns Hotel Payment Reconciliation And How Long It Takes

Because reconciliation tasks run on different timelines, ownership must be assigned by cadence:

• Daily (night audit): The night audit owns operational exceptions such as unposted outlet charges, VCC shortfalls, payment-posting mismatches, and anything that can be corrected before the business date closes.

• Weekly (controller or finance lead): The controller or finance lead reviews the exception queue, ages open items, and escalates anything approaching the OTA dispute window or the card network chargeback deadline.

• Month-end (controller): The controller validates the full reconciliation, closes open items, and signs off on the period.

Settlement reconciliation is owned by finance, while operational payment exceptions are owned by the property.

Reconciliation time varies by property size, channel mix, and how much is automated. With a modern PMS, night audit takes 10–20 minutes for supervisor review and one-click close, versus 3–4 hours for legacy manual processes. A property running manual charge posting from disconnected POS systems and reconciling OTA commissions by hand will spend materially more time than one where charges post automatically and the exception queue is pre-filtered. The goal is a shrinking exception queue, not a benchmark number.

Hotel Payment Reconciliation At Multi-Property Scale

Reconciliation changes materially at multi-property scale. Exception volume grows with the number of properties and channels. Centralized close, shared guest and company profiles, and portfolio-level reporting become necessary rather than optional.

The most underappreciated challenge is account mapping. In multi-property hotel portfolios, inconsistent account mapping across properties, where each hotel maps revenue and payment types to the chart of accounts slightly differently, forces finance teams to reconcile the mappings themselves before they can reconcile the cash. A portfolio-level reconciliation that surfaces a variance cannot be investigated until the finance team knows whether the variance reflects a real discrepancy or a difference in how two properties coded the same charge type.

Each property often reconciles differently using different templates, account groupings, and sign-off habits. That inconsistency stays invisible until an audit, a system conversion, or a new controller arrives. Standardizing the chart of accounts, the exception taxonomy, and the close cadence across every property is the prerequisite for portfolio-level reconciliation to work. Configuration pushed centrally from a single login, rather than rebuilt property by property, makes that standardization achievable at scale.

Multi-site hotel groups that grow without an automated reconciliation layer hit a hard wall around 8 to 12 properties, where the finance team is consumed by reactive reconciliation and senior controllers stop doing the margin analysis the group depends on.

Where Automation Changes The Night Audit

Automation reduces what lands in the exception queue by eliminating the clean cases, so the team only touches the ones that genuinely require judgment.

The highest-value automation targets in hotel payment reconciliation are:

• Automated charge posting from every revenue center. When charges from the POS, spa, mobile booking, and the Grab & Go Kiosk post automatically to the guest folio as they occur, the unposted outlet charge exception disappears. The night audit does not need to chase down what was signed for at the bar because it is already on the folio.

• Automated night audit and end-of-day. Automation cuts the reconciliation step from three hours to roughly five minutes and turns the four-hour overnight audit into a fifteen-minute exception review.

• Instant application of occupancy tax and local taxes. Occupancy tax, the per-night tax on the room rate set locally by city, county, or state, and any additional city or district taxes applied instantly at posting remove the tax variance exception before it is created. Rates and exemptions differ between jurisdictions, so system-level handling removes a category of manual error entirely.

Stayntouch integrates with accounting systems including M3, Sage Intacct, QuickBooks Online, and Xero. Stayntouch charges nothing for its accounting integrations, though users must pay each third-party platform its own platform fee. The data flow from the PMS to the general ledger no longer requires a manual export, and the exception log the controller reviews at month-end reflects the same data the night audit worked from the night before.

See How Stayntouch Automates Your Reconciliation

Why Stayntouch Is The Best-In-Class PMS For Hotel Payment Reconciliation

Stayntouch is a cloud-native hotel property management system (PMS) for independent hotels, boutique brands, and multi-property groups. Charges post automatically from every revenue center, night audit and end-of-day run automatically, and taxes apply instantly, so fewer exceptions reach the controller. The exception queue the controller reviews at month-end reflects genuine discrepancies rather than the administrative backlog of a manual process.

According to Stayntouch customer data, hotels using Stayntouch see up to a 42% improvement in accounting efficiency. That figure reflects the compounding effect of several features: automated charge posting, automated night audit, instant tax application, and clean integration with accounting systems. No single feature drives it alone.

Stayntouch provides 1,400+ integrations with unlimited connections at no additional cost from Stayntouch, though users must pay each third-party platform its own platform fee. The platform is cloud-native on AWS with 100% system uptime, a performance record sustained over the past two years rather than a contractual guarantee. For multi-property groups, the multi-property dashboard manages configuration, rate types, charge codes, and user permissions centrally and pushes standardized settings to every property in the portfolio. That standardization makes portfolio-level reconciliation possible because every property codes the same charge type the same way, so the controller reconciles cash rather than mappings.

The 2026 TravelTech Breakthrough “Hotel PMS Company Of The Year” award and a 97% customer retention rate reflect what finance and operations leaders find when they move from a manual reconciliation process to one where the exception queue is pre-filtered before it reaches them.

Schedule A Stayntouch PMS Demo

Frequently Asked Questions

What Are the Three Types of Reconciliation in a Hotel?

Hotels run three distinct reconciliation processes that feed each other:

1. Revenue reconciliation matches PMS postings to source documents such as the night audit report, outlet daily-Z reports, and banquet settlement records to confirm that every charge posted in the system corresponds to a real transaction.

2. Merchant and settlement reconciliation matches gross card revenue to processor batches and net payouts after fees and chargebacks, confirming that what the processor received matches what the PMS recorded.

3. Bank reconciliation matches net deposits to expected amounts and clears timing differences, including the gap between when a transaction is authorized, when it settles with the processor, and when it posts to the bank account.

All three must be completed before the controller can sign off on a period.

How Long Should Hotel Payment Reconciliation Take?

Reconciliation time depends on property size, channel mix, and automation level. Daily operational reconciliation at the night audit should be part of the close routine. As noted earlier, a modern PMS can bring the supervisor review and close down to 10–20 minutes, but the exact time depends on the operation. Weekly exception review and month-end validation follow separate cadences with different owners and scopes. A property reconciling manually across disconnected systems will spend materially more time than one where the exception queue is pre-filtered by automation. The goal is a shrinking exception queue and a month-end close that reviews finished work rather than races to complete it.

Who Owns Hotel Payment Reconciliation?

Ownership is divided by cadence. The night audit owns daily operational exceptions such as unposted outlet charges, VCC shortfalls, payment-posting mismatches, and anything that can be corrected before the business date closes. The controller or finance lead owns weekly exception review, aging open items, and escalating anything approaching a dispute window or chargeback deadline. The controller owns month-end validation and sign-off. Settlement reconciliation, which matches gross card revenue to processor batches and net deposits, is owned by finance. In multi-property groups, a centralized finance team typically owns portfolio-level reconciliation while property-level night audit teams own the daily operational close.

How Do You Reconcile OTA Virtual Credit Cards?

Match each VCC to its reservation using the booking ID, confirm the face value equals the net rate after commission, and charge within the activation window. The activation window typically opens a few days before check-in and runs until shortly after checkout, and charging outside that window produces a decline. If the folio total exceeds the VCC amount due to incidentals, an extended stay, or a rate change, flag the shortfall at check-in and contact the OTA partner desk for reissuance or modification. If the VCC declines, common causes include the activation window not yet being open or the OTA releasing the card late. Document every VCC exception with the booking ID, the shortfall amount, and the resolution date. VCCs expire, so unresolved shortfalls must be escalated before the card’s expiration date because after that point the revenue is unrecoverable.

What Causes Settlement Timing Differences Between the PMS and the Bank?

Card processors batch settlements daily while sales occur throughout the day. A transaction made late in the evening may not settle until two days later, so systems that record the sale at transaction time without tracking the actual deposit date remain perpetually out of sync. OTA payouts follow their own remittance schedule, which varies by OTA, often monthly or bi-weekly, and in some cases within 7–30 days of the booking. The bank settlement line does not identify which booking it corresponds to. Cash banked after the bank’s cut-off credits the next working day. These are timing differences rather than errors. The correct response is to classify them as in-transit items with an expected settlement date and clear them when the deposit posts.

How Does Reconciliation Change Across Multiple Properties?

Exception volume grows with the number of properties and channels, so centralized close, shared guest and company profiles, and portfolio-level reporting become essential. As covered earlier, the biggest challenge is inconsistent account mapping across properties, which forces finance to reconcile mappings before cash. Standardizing the chart of accounts, the exception taxonomy, and the close cadence across every property is the prerequisite for portfolio-level reconciliation to work. Configuration pushed centrally from a single login, rather than rebuilt property by property, makes that standardization achievable. Multi-property groups that grow without a standardized reconciliation layer typically reach a point where the finance team is consumed by reactive reconciliation rather than forward-looking analysis.

What Accounting Systems Integrate With a Hotel PMS for Reconciliation?

Stayntouch integrates with M3, Sage Intacct, QuickBooks Online, Xero, and other accounting platforms. As mentioned, Stayntouch does not charge for the integration itself, but each third-party platform may charge its own fee. The integration means that the data flow from the PMS to the general ledger does not require a manual export or re-keying, which eliminates a category of transposition errors and ensures the exception log the controller reviews reflects the same data the night audit worked from.

Read Next

• Hotel Payment Processing Issues: A Front Desk Guide

• Hotel Payment Integration With PMS: Operator’s Guide

• Hotel Payment API Integration Guide for PMS Platforms

• Hotel Payment Best Practices for Independent Hotels

• Automated Hotel Billing: A Complete Operational Guide