PMS configuration-audit program

Across ten properties, tiny PMS misconfigurations accumulate: wrong room capacities, stale open balances on cancelled reservations, tax residuals left behind when a flat per-night code doesn't clean up after a shortened stay. No human eyeballs all of it, and each one is a small, quiet cost.

How it works

It's a portfolio-wide program with three sweeps: room-type and capacity checks, open-balance sweeps of the guest ledger, and tax-residual root-causing. Today it drives the PMS admin app by URL, navigating by enterprise GUID because the property switcher resists synthetic clicks, and it reads the app's React Query cache directly instead of scraping the grid. As the Connector API comes online per property, each audit migrates from the browser to a clean API call. Findings ship as Excel deliverables.

• Room-type and capacity: clean across all ten after fixes.
• Open-balance sweep: done for five of ten, already surfacing dozens of stale rows plus systemic patterns like tax residuals, one-cent OTA rounding, and uncollected cancellation fees.
• API path enabled at seven of ten, replacing the browser method as it rolls out.

It's building, and already paying for itself in caught misconfigurations. The next step is finishing the remaining properties and moving fully to the API where it's enabled.

Config drift is the invisible tax on a small operator. An audit agent that runs the whole portfolio is how the exception rate keeps falling instead of quietly growing.