// Industry · Hospitality Ops

A fractional AI Ops Department for hospitality, PMS recon to group billing.

Boutique hotel groups run ops out of the GM inbox and a spreadsheet maintained by whoever has the latest version. PMS reconciliation lags by weeks. OTA commission errors compound until quarter close. F&B inventory variance is a guess. Group billing reconciliation requires the GM, the finance contact, and the corporate sales manager in the same Zoom. Fractional AI Ops for hospitality runs the back office across every property, every PMS line, every OTA channel. Live in 14 days against Opera, Mews, Cloudbeds.

// The hospitality ops shape

Four properties, six PMS lines, no single source of truth.

The ops function at a boutique hotel group with three to eight properties is usually nobody officially. The GM at each property runs ops on the side of running the property. The finance contact at the corporate office handles month-end close, vendor payments, and the OTA commission invoices when she can get to them. The corporate sales manager owns the group billing reconciliation because she signed the contract. The F&B side runs on the chef inventory count and a supplier spreadsheet that nobody outside the kitchen has seen in three months. Nobody owns the back office because every person who could own it is also doing two other jobs.

The PMS environment compounds the problem. Each property has its own Opera, Mews, Cloudbeds, Protel, or RoomRaccoon instance. Each instance produces its own occupancy report, ADR report, RevPAR report, and reservation export on its own cadence. The corporate office tries to pull a multi-property weekly report by exporting CSVs from each PMS, normalizing the columns in Excel, and emailing a deck to the GMs by Tuesday afternoon. The deck is stale by the time it lands because the channel manager has shipped new reservations into the PMS overnight. The revenue manager brief that should land in the GM inbox by 7am every morning lands in the GM inbox once a week, on a good week. Pricing decisions get made on stale data, which means rate parity issues, OTA commission leaks, and missed yield opportunities.

The OTA commission picture is the most expensive of the ops failures. Booking.com, Agoda, Expedia, and Trip.com each ship their own commission statements on their own cycles, with their own dispute windows and their own reconciliation formats. A typical boutique group lets two to four percent of OTA commission billing go unchallenged because nobody has the bandwidth to reconcile the statements line by line against the PMS booking record. On a 2M room revenue book that is 40K to 80K a year flowing out the door on commission lines that never get audited. The finance contact knows this and knows there is no way for her to fix it inside the time she has. See AI for Hospitality for the integrated picture across all four functions.

// Why hospitality ops fits the agent model

Reconciliation is structured work. Multi-property is a load problem.

The ops work inside hospitality is structured, repetitive, and high-leverage. PMS reconciliation against the channel manager is a line-by-line match across reservation IDs, rate codes, room nights, and total revenue. OTA commission reconciliation against the PMS booking record is the same shape of work, performed monthly against four to seven OTA statements. F&B inventory reconciliation is a count against a purchase log against a sales log. Multi-property reporting is the same aggregation performed once per property and rolled up. Group billing reconciliation is a contract-against-actuals comparison across rooming list, F&B attach, meeting space, and AV. Each of those workflows is exactly the shape of work that the agent model handles structurally better than a single finance contact running them on the side.

The data shapes are clean. The PMS holds the reservation record, the rate code, the room nights, the revenue, the guest history, the F&B attach. The channel manager holds the OTA distribution and the rate parity picture. The accounting system (Xero, QuickBooks, NetSuite, or property-level systems) holds the GL accounts, the vendor records, and the commission liability lines. The POS system on the F&B side holds the sales record. The supplier portal holds the purchase invoices. Each system has an API or a standard export. The agents pull all of those in parallel, perform the reconciliation, flag the variances, and ship the exception report into the finance contact inbox with the resolution suggested.

The output across hospitality ops engagements is consistent. PMS reconciliation goes from weekly lag to daily refresh. OTA commission audit catches the two-to-four percent leak that was going unchallenged. F&B inventory variance drops to under one percent with daily reconciliation against the POS sales log. Multi-property reporting lands in the GM inbox by 7am every morning with occupancy, ADR, RevPAR, and the day-before flash. Group billing reconciliation drops from a multi-day Zoom marathon to a one-page exception report the corporate sales manager approves in twenty minutes. The finance contact stops being a spreadsheet operator and becomes the controller the boutique group needs.

// Five things the hospitality ops engine runs

PMS recon, OTA audit, F&B inventory, multi-property report, group billing.

The fractional AI Ops Department for hospitality does not pick a workflow. It runs all five at once because the agents do not run out of hours the way one finance contact does. Configured against your real hospitality stack from day one. Opera, Mews, or Cloudbeds as the PMS. SiteMinder, RateGain, or Cloudbeds Channel Manager. Xero, QuickBooks, NetSuite, or property-level accounting. The POS systems on the F&B side. The supplier portals on the procurement side.

01

Daily PMS reconciliation across every property

Agents pull the daily reservation export from each PMS, match it line by line against the channel manager record and the booking engine record, flag variances on rate codes, room nights, and revenue, and ship the exception report into the finance contact inbox by 6am. Reconciliation goes from a weekly lag to a daily refresh. The Tuesday afternoon multi-property deck becomes obsolete because the GM and the finance contact already have the data fresh by Monday morning.

02

OTA commission audit against PMS booking record

Agents pull the monthly commission statements from Booking.com, Agoda, Expedia, Trip.com, and the regional OTAs, match each commission line against the PMS booking record, flag overcharges and double-charges, and prepare the dispute filings inside the OTA dispute window. The two-to-four percent of commission billing that was going unchallenged gets challenged. On a 2M room revenue book that is 40K to 80K a year recovered against commission lines.

03

F&B inventory and supplier reconciliation

Agents reconcile F&B inventory daily against the POS sales log and the supplier purchase log. Variance reports flag the shrinkage on the high-value SKUs (wine, spirits, premium proteins) and the patterns that indicate process issues. Supplier invoices get matched against the purchase orders and the receiving logs, with variances flagged for the chef and the finance contact. Inventory variance drops to under one percent and the F&B GP picture finally matches the menu engineering assumptions.

04

Multi-property daily revenue manager brief

Every GM gets a one-page brief in the inbox by 7am with occupancy, ADR, RevPAR, the day-before flash, the upcoming 14-day pace, the rate parity flags, the OTA distribution mix, and the action items for the day. The corporate office gets the rolled-up multi-property version with cross-property comparisons and yield opportunities flagged. Pricing decisions get made on fresh data instead of last week stale data.

05

Group billing reconciliation and contract-vs-actuals

Every group booking that bills out gets a contract-vs-actuals reconciliation. Rooming list vs the PMS reservation record. F&B attach vs the BEO and the POS sales record. Meeting space vs the contract pull. AV vs the supplier invoice. Variances get flagged with the resolution suggested and the corporate sales manager approves the final invoice in twenty minutes instead of a multi-day Zoom marathon. Group billing accuracy improves and the cash cycle shortens.

// The hospitality ops math

One finance contact running spreadsheets vs a fractional AI Ops Department for hospitality.

Honest numbers from production engagements with boutique hotel groups between three and eight properties. Rebuild them against your OTA commission statements and your PMS export history in an afternoon.

Weekly to daily
PMS reconciliation cadence
across every property, with variance flagged by 6am
2 to 4%
OTA commission recovery
against billing lines that were going unchallenged
<1%
F&B inventory variance
with daily reconciliation against POS sales
14
Days to live ops engine
vs 6-month controller hire
// Side by side

Hiring a controller plus revenue manager vs a fractional AI Ops Department for hospitality.

Both run a year. Both cover the same multi-property group across the same PMS environment. Honest comparison, no rigging the numbers.

Hire controller + revenue manager
  • $160K to $260K loaded annual (2 hires)
  • + accounting tooling, BI subscription, freelancer pool
  • 6-month ramp before controller knows the properties
  • PMS reconciliation lags by 1 to 2 weeks per property
  • OTA commission audit happens at quarter close, badly
  • F&B inventory variance is a quarterly count
  • Revenue manager brief lands weekly on a good week
  • Group billing reconciliation is a multi-day Zoom
AI Ops Department for Hospitality
  • Single monthly retainer, smaller than one of those hires
  • Tooling, infrastructure, and operator time included
  • Live in 14 days, full output by week four
  • PMS reconciliation runs daily with variance flagged by 6am
  • OTA commission audit runs monthly, dispute filings on time
  • F&B inventory reconciled daily against POS, variance under 1%
  • Brief lands in the GM inbox by 7am every morning
  • Group billing reconciled in 20 minutes by exception report
// The 14-day hospitality ops sprint

From kickoff call to live ops engine in two weeks.

Step 01

Days 1 to 3 · Hospitality ops audit

We map every property, the PMS at each property (Opera, Mews, Cloudbeds, Protel, RoomRaccoon), the channel manager, the accounting system, the POS stack on the F&B side, the supplier portals on procurement, the OTA mix, and the existing reconciliation workflow. We pull three months of OTA commission statements and the corresponding PMS booking record to scope the leak that has been going unchallenged.

Step 02

Days 4 to 10 · Build against the hospitality ops stack

Agents get integrated with each PMS through the documented API, the channel manager for OTA distribution data, the accounting system for GL posting, the POS for F&B sales reconciliation, and the supplier portals for purchase reconciliation. Multi-property reporting templates configured to the GM brief format and the corporate office rollup format. OTA commission audit logic wired against each OTA dispute window. Group billing contract-vs-actuals templates built per major contract type.

Step 03

Days 11 to 14 · Go live, all five workflows

Daily PMS reconciliation goes live first because it has the highest immediate impact on data freshness. The 7am GM brief follows in days. OTA commission audit fires at the next monthly statement cycle. F&B inventory reconciliation starts the day after the next physical count. Group billing reconciliation goes live against the next group contract bill-out. By week four the back office is running continuously and the finance contact is reviewing exception reports instead of running spreadsheets.

// Inside a hospitality ops day

What 6am looks like on a multi-property ops engine.

6am, corporate office: the agents have shipped the overnight PMS reconciliation across all four properties. Three properties reconciled cleanly. The fourth has a six-reservation variance against the channel manager record where SiteMinder failed to push the inventory updates between 11pm and 1am. The exception report flags the affected reservations, the rate code mismatch, and the recommended resolution (call the SiteMinder support line, push the missing updates manually, audit the period for double-bookings). The finance contact reviews the exception report in fifteen minutes and the GM at the affected property gets a heads-up before the front desk opens.

7am, every property: the revenue manager brief lands in every GM inbox. One page per property. Occupancy yesterday, ADR yesterday, RevPAR yesterday, the day-before flash, the upcoming 14-day pace against the same period last year, the rate parity flags from the channel manager scan, the OTA distribution mix, the two action items for the day. The corporate office brief lands at the same time with the multi-property rollup, the cross-property comparison, and the yield opportunities flagged. The GMs walk into the morning meeting with fresh data instead of last week stale data.

Mid-month: the OTA commission statements arrive from Booking.com and Agoda. The agents pull the statements, match each commission line against the PMS booking record across the four properties, flag eighteen variances (twelve overcharges, four double-charges, two cancellation commission errors), and prepare the dispute filings inside the Booking.com seven-day dispute window. The finance contact reviews the dispute pack in thirty minutes, approves the filings, and the agents submit through the OTA dispute portal. Three weeks later the corrected statements arrive and 4K of commission billing comes back against billings that would have been written off in the old workflow.

End of quarter: the group billing reconciliation for the wedding season runs against six group contracts that billed out across the quarter. Each contract gets a contract-vs-actuals report showing the rooming list reconciled against the PMS reservation record, the F&B attach reconciled against the BEO and the POS sales log, the meeting space reconciled against the contract pull, and the AV reconciled against the supplier invoice. Two contracts have variances over a thousand dollars that need a corporate sales manager call with the planner. Four reconcile cleanly. The cash cycle on the group AR shortens from forty-five days to twenty-eight days because the invoices ship the day after the event instead of two weeks later. For the integrated view across all four hospitality functions, see AI for Hospitality. For the ops department mechanics across all industries, see AI Ops Department.

Excellent communication and top-notch quality of service. EOI has been a choice to accelerate our company, not only on a technical level, but also business-wise and creatively. If you need anyone to do your AI workflows, these guys are the experts.
Gregory Benjamins
CEO · Green Collective
// Pricing

Single monthly retainer for the hospitality ops engine. No BI subscription stack.

Monthly retainer · 14-day kickoff · 30-day notice

Smaller than a single controller hire, fully loaded. Replaces the controller plus the revenue manager plus the BI tooling stack. Tooling, infrastructure, and operator time included.

  • Daily PMS reconciliation across every property with variance flagged by 6am
  • OTA commission audit against every Booking, Agoda, Expedia, Trip.com statement
  • F&B inventory and supplier reconciliation against POS sales and purchase logs
  • Multi-property revenue manager brief in every GM inbox by 7am
  • Group billing contract-vs-actuals reconciliation per major contract type
  • PMS integration with Opera, Mews, Cloudbeds, Protel, RoomRaccoon
  • Channel manager integration with SiteMinder, RateGain, Cloudbeds Channel Manager
  • Direct line to the operator running your hospitality ops department
Apply for a sprint
// Further reading

For the integrated breakdown of why boutique hospitality groups end up with no one officially owning the back office, and what shipping continuous multi-property ops looks like across PMS reconciliation, OTA audit, F&B, and group billing, read the hospitality industry page.

Read the hospitality breakdown
// FAQ

The questions founders ask before they apply.

01Which PMS platforms do you integrate with?
Opera, Mews, Cloudbeds, Protel, RoomRaccoon, Little Hotelier, StayNTouch, RMS Cloud, and most of the boutique-focused PMS platforms. The agents pull the daily reservation export, the rate code mapping, the occupancy and ADR data, and the guest history through the documented API. For legacy PMS instances we run a daily extract pipeline that lands the data into a clean operating layer.
02How does the OTA commission audit actually work?
The agents pull the monthly commission statements from Booking.com, Agoda, Expedia, Trip.com, Hotelbeds, and the regional OTAs, match each commission line against the PMS booking record (reservation ID, rate code, room nights, total revenue), and flag overcharges, double-charges, and cancellation commission errors. The dispute filings get prepared inside each OTA dispute window and submitted through the OTA dispute portal. Most engagements recover 2 to 4 percent of commission billing that was going unchallenged.
03What about F&B inventory and the POS systems?
Agents reconcile F&B inventory daily against the POS sales log (Toast, Square, Lightspeed, Oracle Simphony, in-house POS) and the supplier purchase log. Variance reports flag shrinkage on the high-value SKUs and the patterns that indicate process issues. Supplier invoices get matched against the purchase orders and the receiving logs. Inventory variance typically drops to under 1 percent with daily reconciliation, against the 3 to 8 percent variance most boutique groups run at on quarterly counts.
04How does the multi-property report stay accurate across properties on different PMS instances?
Each property PMS feeds into a unified operating layer through the documented API. The agents normalize the data across PMS platforms so the multi-property report rolls up cleanly regardless of whether one property runs Opera and another runs Mews. Currency, rate code taxonomy, and room category mapping are reconciled once at the corporate level. The GM brief and the corporate office rollup land at the same time every morning.
05Can you do the group billing reconciliation across the contract, the BEO, and the POS?
Yes. Every group billing reconciliation pulls the contract terms, the rooming list, the BEO (banquet event order), the POS sales record from the event, the meeting space contract pull, and the AV supplier invoice. The contract-vs-actuals report flags variances over a threshold you set, and the corporate sales manager approves the final invoice in twenty minutes. Cash cycle on group AR typically shortens from 45 days to 28 days because the invoices ship the day after the event.
06What accounting systems do you support?
Xero, QuickBooks Online, NetSuite, Sage Intacct, FreshBooks, and property-level accounting modules in the PMS itself. The agents post journal entries, reconcile against GL accounts, match commission liability lines against the OTA audit results, and prepare the month-end close pack. The finance contact reviews the close pack and approves it instead of building it from scratch in Excel.
07How do you handle rate parity monitoring against the channel manager?
The channel manager (SiteMinder, RateGain, Cloudbeds Channel Manager, STAAH, eRevMax) gets monitored continuously against the OTA distribution channels for rate parity violations. The agents flag rate disparities, identify the source channel that is breaching parity, and ship the resolution recommendation to the revenue manager or the GM. Rate parity violations get caught and resolved within hours instead of festering for weeks.
08Do you have hospitality clients now?
Yes. EOI has worked with Da Giovanni, the Italian restaurant group, and Pursuit of Passion in the hospitality and lifestyle space, plus boutique hotel groups currently under NDA. The hospitality ops engagement is built on the same fractional AI Ops Department model that ships for SaaS and ecommerce clients, adapted to the PMS reconciliation, OTA commission audit, F&B inventory, multi-property reporting, and group billing reality of the industry.
// From the notes
// Also worth a look
// Ready to ship this?

Start a AI Ops for Hospitality sprint. 14 days from kickoff.

Apply in 7 questions. EOI reviews every application within 24 hours.