Ten systems. One version of the business.
Bookings, POS, payments, payroll and banking each hold a piece of the truth, and none of them agree. This is the work of making them reconcile.
The guest has one stay. The business has ten systems.
A property runs on a property management system, a point-of-sale, a payments processor, a payroll platform, a banking feed and whatever the spa and the restaurant chose independently. Each is competent. None of them share a definition of a guest, a booking or a dollar.
So the month closes, and finance spends the first week of the next one deciding which number is real. By the time the answer exists, the period it describes is over and nobody can act on it. Meanwhile the decisions that needed it — staffing, pricing, whether to run the promotion again — were made on a guess.
Find the seams before writing any code.
We start with a diagnostic architecture audit, not a deployment. The goal is to find where the same entity is described differently in two systems, because that is where the reconciliation will fail and where the manual work is hiding.
Map the estate
Every system that holds a guest, a transaction or an hour — including the ones that are not on anyone's list.
Find the identity seams
Where the same guest, booking or payment exists under two different keys. This is almost always the real problem.
Agree the definitions
What counts as revenue, when a booking is confirmed, which timestamp is authoritative. Written down before anything is built.
Build the reconciliation
Then, and only then, the pipelines — against definitions the business has already signed off.
A reconciliation layer the business can question.
Not a dashboard on top of the mess: a modeled layer underneath it, where every figure can be traced back to the source rows that produced it. When someone disputes a number — and someone always does — the answer is a query, not a meeting.
What changes once it holds.
- The month closes on the numbers, not on the argument. Reconciliation runs continuously rather than as a week of manual work after the period ends.
- A disputed figure has a traceable answer. Every number resolves to source rows, so disagreements end in minutes instead of becoming standing meetings.
- Forecasting becomes possible at portfolio level. Demand and pricing models can finally read the whole estate rather than one property at a time.
- New properties join the model instead of extending the spreadsheet. The same foundation supports one property or a hundred.
Where this has run.
-
A mountain retreat center · Hospitality
Ten systems reconciled into one version of the business.
A retreat and hospitality operation running bookings, point-of-sale, payments, payroll and banking across separate systems, with no single figure anyone could defend.
10+Systems unified386KCustomer records99.8%Payment reconciliation$84M+Revenue mapped -
Next
Room for the next customer under this solution. Adding one is a new entry here, not a rewrite of this page.
Bring us the hard part.
Every one of these began as a diagnostic, not a deployment. If the problem above is yours, that is where we would start too.