Hotel chain accounting under Circular 99: one system, many properties

Part 1: Why accounting for a chain is harder than for a single hotel

The difference is not the volume of documents. A five-property chain is not simply one hotel multiplied by five; it is a structure in which each property has its own operating profile yet all of them have to roll up into a single financial picture.

Four sources of complexity

• Revenue is generated in many places, each in a different way. A city property is mostly room revenue plus one restaurant; a resort has a main restaurant, a pool bar, a mineral bath area, a tour desk and conference services. Same chain, but completely different revenue mixes.
• Inconsistent account structures. Each property names its own line items out of habit — and when it is time to consolidate, nothing adds up, because "other services" in one place does not mean the same thing as "other services" in another.
• Inter-property transactions. Stock transfers, shared staff, one property booking rooms on behalf of another. If these are not identified, they get counted twice in the group picture.
• Two kinds of reporting at once. Management needs departmental reporting to assess the performance of each area; regulators and banks need statutory financial statements prepared under the accounting regime. Neither substitutes for the other, and doing either one by hand is a poor choice.

This is why a hotel management system at chain scale cannot stop at operations. A system that is strong on front office and housekeeping but has no route down into the ledger simply pushes all that volume into the finance department as spreadsheets — and spreadsheets have to be re-keyed.

Part 2: Circular 99 for multi-property businesses

Circular 99/2025/TT-BTC is the corporate accounting regime replacing Circular 200/2014/TT-BTC, applicable from 1 January 2026. The three points below are what a chain has to prepare for, and all three get heavier as the number of properties rises.

Three tasks that must be done across every property at once

• Update the chart of accounts. Some accounts are renamed, reordered or have their reporting content adjusted — account 112, for instance, is now titled Demand deposits. In a chain this has to be done consistently; if each property updates according to its own reading, consolidation in the next period will break.
• Migrate balances to the new chart of accounts. This is a one-off task that affects the whole financial year. Across several properties it needs a common cut-off date, one person accountable for the cross-check, and a before-and-after reconciliation kept on file for audit purposes.
• Make sure the tooling is updated in time. If the accounting software does not support the new chart of accounts by the deadline, the remaining option is manual work across several properties simultaneously — right at the start of the financial year, the busiest stretch for the entire finance team.

On the third point, we will state our own position plainly: DiACC hotel accounting software has updated its chart of accounts to Circular 99 and is running live at hotels and 4–5 star chains. That is a statement about product status, not a promise: balance migration and review remain the professional work of the finance team, something a tool supports rather than performs on its behalf.

Part 3: One shared chart of accounts for multiple properties

The foundation of chain accounting is a single shared account structure used across the whole portfolio, with analysis dimensions that let you break it back down by location. Doing it the other way round — one structure per property, mapped to each other at period end — is how you create permanent manual work.

The four minimum dimensions

• Property dimension. Each hotel, each resort is a code. This is the dimension you split reports by and also the dimension you consolidate on.
• Department dimension. Rooms, food and beverage, wellness, conference and events, administration. This is the dimension for management reporting and for assessing the performance of each area.
• Outlet dimension. A department can contain several outlets — the main restaurant and the beach restaurant both sit under food and beverage but need to be measured separately, as we set out in our article on room charge posting and multi-outlet management.
• Revenue type dimension. Accommodation, food, alcoholic beverages, services, retail goods, third-party collections. This dimension serves tax and invoicing obligations, and it must be independent of the three above — a bottle of wine sold at the beach restaurant belongs to all four dimensions at once.

Three rules that keep the account structure from breaking

• One owner for the account structure. Properties propose, group finance approves and opens the code. If every location opens its own codes, within two years the structure will hold multiple codes with the same meaning under different names.
• No "other" line item at reporting level. If you need one, open a new code; do not use a holding bucket — information that goes into "other" never comes back out.
• A code in use never changes meaning. If something has to change, open a new code and close the old one, so historical data stays comparable with the present.

Part 4: Revenue flowing from the management system into the ledger

This is the core of the matter and the point where an integrated platform genuinely differs from a set of disconnected tools. In a chain, thousands of lines are generated every day across many outlets; the question is not "can it be entered" but "by what route does each line reach the ledger, and can it be traced back".

Three levels of integration, only one of which is good enough

• Low level — a daily summary sheet. Operations exports one sheet at the end of the day and finance enters it into the ledger. It sounds tidy, but every trace is lost: when there is a discrepancy, nobody can track it back to a particular room night or service voucher.
• Middle level — a detailed file imported periodically. More detail, but still a delay and still a human step in the middle, which means there is still room for errors and omissions.
• Good enough — data passing straight through at transaction level, with a reference back. Every entry carries its property, department, outlet, revenue type, accounting date and source document number. Finance does not re-key anything; the work of the finance team shifts from data entry to review and analysis — exactly where value is created.

What it takes for the good-enough level to work

• Every outlet sits on the same platform, or connects to it at transaction level. Within the DiHotel Solutions ecosystem, food and beverage is handled by the DiPOS module, the mineral bath area by the DiONSEN module, purchasing and inventory by the DiPO module — all of them looking at the same room folio and the same account structure.
• The accounting date is defined consistently by the night audit run, not by the clock. This point matters enough that it is the whole of the next section.
• There is an automatic reconciliation between the two ends — total activity in operations must equal total recognised in the ledger, every day, for every property. Discrepancies have to surface the next morning, not at quarter end.

If your chain runs a separate hotel accounting software and wants to keep it, the minimum condition to write into the contract is that data must transfer at individual transaction level with a reference back, along with a clause establishing which party is accountable when the two ends disagree. Syncing a single daily total sounds tidy, but it discards exactly what you need when you have to explain yourself.

Part 5: Four hospitality-specific transactions that go wrong on the books

The four transactions below are specific to the accommodation industry. They do not go wrong because accountants are careless; they go wrong because the moment of the transaction differs from the moment of payment, and that gap multiplies with the number of properties.

Four places to solve by design, not by being careful

• 1. Night audit and the day boundary. A hotel's working day ends at the night audit run, not at midnight. A guest checking in at 00:30, a bottle of wine sold at 1 a.m. — which accounting day each belongs to is decided by the audit cut-off. In a chain, if properties close at different cut-offs while the consolidated report adds up by calendar day, the group figures will be out in a way that is very hard to trace.
• 2. Intermediary channels, tour operator contracts and negotiated rates. Selling through an online channel means the channel retains a commission; selling through a tour operator means a negotiated rate and a receivable settled after the period. Recording revenue at the amount actually received understates revenue and makes selling costs disappear — while also destroying any ability to compare channel performance.
• 3. Deferred revenue. Room deposits, prepaid packages, service vouchers, conference deposits. The money is in but the service has not been delivered — this is an obligation to the guest, not yet a result of operations. For a chain with pronounced seasonality, the deferred amounts that pile up at year end for the following year's holiday season are large enough to distort both periods entirely if recognised wrongly.
• 4. Room charge posting and internal accounts. Revenue belongs to the day of service, the cash to the day of check-out. Alongside that are the entries that belong to no guest — partner hospitality, internal trials, service recovery compensation — which must have their own place to be recorded and their own approver, or they will sit mixed into revenue and ruin both the figures and the ability to explain them.

Part 6: Consolidating the numbers while keeping per-property reporting

A chain needs two pictures at once, and those two pictures serve two different audiences. What matters is that both are produced from the same source of data, rather than being two spreadsheets built by two people in two different ways.

Two reporting views, one source of data

• Statutory financial statements. Prepared by legal entity, following the Circular 99 chart of accounts, serving reporting obligations and dealings with banks, auditors and regulators.
• Departmental management reporting. Revenue and costs broken down by property, department and outlet so management can assess the performance of each area — the structure we set out in detail in our article on the USALI hotel P&L. The two standards do not conflict: one is a presentation for the outside, the other a view for the inside.

Three technical decisions that determine consolidation quality

• Identify and eliminate inter-property transactions. Stock transfers between properties, services one property provides to another — these must be flagged the moment they occur, not hunted down at period end.
• Align the closing period. All properties must close at the same cut-off; one property closing late means the entire consolidated report has to be redone.
• Maintain a single definition sheet for every metric. What net revenue includes, which rooms are excluded from occupancy, whether service revenue includes third-party collections. Agree once, document it, and do not change it mid-year — otherwise every year-on-year comparison loses its meaning.

Part 7: Controls, audit trail and the ability to explain

At chain scale, the quality of the books is not measured by how neat the numbers look but by whether every line can be explained when an auditor, a bank or the tax authority asks. The four mechanisms below are the minimum.

Four minimum mechanisms

• A complete trail for every amendment and void — who did it, when, why, and the value before and after. This mechanism protects the business and honest staff alike.
• Controlled period closing. After closing, every adjustment is a new journal entry rather than an overwrite. The right to reopen a period must sit with one identified person, not be a default user permission.
• Permissions by role and by property. Property accountants see their own property's data; the group team sees the whole portfolio. Assign by job position, not by individual.
• A path back from the ledger to the source document. From a revenue line in the ledger you must be able to trace back to the room folio, to the outlet check, to the transaction time and the person who entered it. Without that path, every dispute and every review is settled on gut feeling.

This is also the set of criteria to put on the due diligence list when choosing a vendor, alongside the items we listed in our article on vendor due diligence for chains and 4–5 star hotels. An AI hotel management software serving a chain must be able to demonstrate all four mechanisms on real data, not with a line in a brochure.

Part 8: Summary table — which transaction, where it goes wrong at chain scale

Part 9: A migration roadmap for a chain

The order below is deliberate: clean up the account structure first, connect the data second, migrate balances last. Do it the other way round and the parts already migrated will have to be redone.

Five steps

• Step 1 — Agree the shared account structure. One chart of accounts, one set of codes for property, department, outlet and revenue type across the whole portfolio. This is the most time-consuming step and also the decisive one.
• Step 2 — Standardise the accounting date and the closing process. The same night audit cut-off, the same closing calendar, the same rules for post-close adjustments.
• Step 3 — Connect the data at transaction level. From the management system and the outlets down into the accounting module, with a reference back and a daily reconciliation between both ends.
• Step 4 — Run in parallel for one period. Reconcile the old and new figures and break down differences using exactly the seven groups in Part 8. We set out the principles of parallel running and the rollback plan in our article on the system migration checklist.
• Step 5 — Migrate balances and close the first period under the new regime, keeping the before-and-after reconciliation for each property.

When these five steps are done, what the chain gains is not just a compliant set of books. It is the ability to see the portfolio's monthly results without anyone stitching spreadsheets together — which is exactly the view that the reporting app for owners serves. Smaller properties in the same portfolio run on cloud AI hotel management software DiCloud and still share the same set of metric definitions, so the picture does not fracture between the two product tiers.