It’s 7:40 a.m. on the Tuesday of close week, and Priya, director of finance for an eight-property portfolio, is already three tabs deep into a spreadsheet before her coffee is done. Somewhere in the next ten days, she needs to deliver a consolidated P&L to two ownership groups, reconcile eight properties’ worth of PMS and POS exports, and figure out why Property 4’s departmental profit margin looks wrong again. She’s done this enough times to know it’s not going to be a short day.
Priya is a composite, but if you run finance for a multi-property hotel portfolio, some version of her Tuesday probably looks familiar. Her stack is a generic accounting system, stretched year over year with spreadsheets, custom mappings, and manual workarounds to approximate what a hotel finance ERP would do natively. Here’s what that day tends to look like on generic accounting software, and what changes when the platform underneath it is a hospitality-specific ERP built for exactly this.
8:15 a.m. — The Export Queue
Before Priya can do anything close-related, she has to get the data into the system. That means logging into each property’s PMS, exporting yesterday’s night audit, then doing the same for the POS system at properties with F&B outlets. Two of her eight properties run a different PMS than the rest, so those exports come out in a different format and need to be remapped before they’ll sit next to everything else.
By 9:30, she has eight spreadsheets open, none of which talk to each other, and none of which have touched the general ledger yet. This is the quiet cost that never shows up as its own line item: hours spent moving data by hand, before any actual accounting work has started.
On a hospitality-specific platform, this hour and a half doesn’t happen. A system like DP Finance connects directly to PMS, POS, payroll, and time & attendance at each property, pulling night audit and revenue data into the general ledger automatically, overnight. Priya’s 8:15 a.m. on a hospitality-built system starts with data that’s already posted, not a queue of exports waiting to be reconciled by hand.
10:45 a.m. — The USALI Patch Job
With the raw numbers finally in the GL, Priya turns to the part of her job that never quite goes away: making sure everything lines up with USALI. Her chart of accounts was custom-built years ago to approximate USALI structure inside a generic system, and it mostly works, but now when a new revenue stream gets added, or a property’s outlet mix changes, and someone has to remember to update the mapping. Today it’s a new resort fee category at Property 6 that isn’t classified correctly, which means manually reclassifying three weeks of entries before departmental profit will calculate correctly.
This is the kind of task that’s invisible until it isn’t: a workaround holding up under normal conditions, until something changes and the whole structure needs to be patched by hand.
On a hospitality-specific platform, USALI 12th Edition structure isn’t something Priya’s team builds and maintains. It’s the foundation the chart of accounts is built on from day one. New revenue categories map to the correct departmental structure automatically, because the system was designed around USALI in the first place, not retrofitted to approximate it.
1:30 p.m. — The Property 4 Mystery
After lunch, Priya finally gets to look at why Property 4’s numbers looked off in yesterday’s flash report. It takes forty minutes of cross-referencing spreadsheets to find it: a manual journal entry from two weeks ago, made to correct a different error, that never got reversed. It’s a small mistake, but finding it required tracing through entries that live only in a spreadsheet trail, not in any system that would have caught the inconsistency on its own.
Multiply this by eight properties and a portfolio-wide close, and this kind of manual-entry archaeology becomes one of the biggest hidden time costs of close week.
On a hospitality-specific platform, the volume of manual journal entries drops substantially in the first place, because revenue and cost data are flowing in automatically, correctly coded, from source systems. Real-time portfolio KPIs and daily P&L visibility also mean an anomaly like Property 4’s would have surfaced the day it happened, not two weeks later and buried in a spreadsheet.
4:00 p.m. — The Consolidation
By late afternoon, Priya starts the part of the day she’s been building toward: consolidating eight properties into one portfolio-level statement for ownership. Three properties sit under one entity, five under another, with management fees and intercompany charges that need to net out correctly between them. This is manual mapping, property by property, checking that nothing was double-counted or missed. It’s the same process, more or less, every month.
On a hospitality-specific platform, multi-property and multi-entity consolidation happens as data comes in, not as a separate end-of-month event. Intercompany transactions and management fees are handled within the platform’s structure, so the portfolio-level view Priya needs for ownership is already assembled, not something she has to build from eight separate files on the fifth day of close.
6:50 p.m. — The Owner Packet
The last task of the day is the one with a hard deadline: the owner packet is due tomorrow morning, and it needs to look consistent across properties that have historically reported slightly differently with different formatting from when Property 7 was acquired two years ago and different rounding conventions someone set up at Property 2 that never got standardized. Priya spends the last hour of her day making sure the packet looks like it came from one system, even though it came from eight spreadsheets and a lot of manual formatting.
On a hospitality-specific platform, every property reports into the same structure from the start, so the packet doesn’t need to be manually reconciled for consistency. It already is one.
What Changes, Concretely
None of this is about Priya working harder or smarter. The gap between her two Tuesdays is simply a platform problem. Generic accounting software was never built to connect to a PMS, enforce USALI structure, or consolidate multi-entity hotel portfolios in real time, so all of that work falls to her team by default. A hotel ERP accounting software platform closes that gap by design, connecting the general ledger to the operational systems of the PMS, POS, payroll, and procurement that generic accounting software was never built to talk to.
On a hospitality-specific ERP like DP Finance, that same close week typically finishes five to seven days faster, with substantially fewer manual journal entries and a portfolio-level report that didn’t need to be reassembled by hand. The work Priya’s team does shifts from data assembly to actual analysis.
The Takeaway for Multi-Property Finance Leaders
If Priya’s Tuesday sounds close to your own, the fix usually isn’t a better spreadsheet template or a more disciplined process. It’s the difference between a generic accounting system stretched to cover hotel operations and a true hotel finance ERP — a hotel accounting system for multiple properties built around how hotels actually operate: daily revenue, multiple departments, multiple entities, and reporting obligations to owners and brands, instead of one that’s been patched together to approximate it.
Curious what your own close week could look like on a platform built for this? Book a demo with Data Plus and we’ll walk through how DP Finance turns a ten-day close into a five-day one across your full portfolio.
