A resort is a hotel with more departments arguing over the same guest folio — rooms, F&B outlets, spa, golf, watersports, retail shop — and the Acumatica fit inherits everything true of the hotel case (it is not a PMS, do not pretend otherwise) plus one extra wrinkle: multi-department revenue that all needs to reconcile back to a single guest bill, and often a mix of owned outlets and concessioned third-party operators sharing the property.
Start from the hotel baseline
Everything about PMS boundary and nightly reconciled feeds in the hotel-vertical piece applies here unchanged — I am not repeating that setup, read it first if a resort project is on the table. What resorts add is departmental complexity on top of that same PMS bridge.
Branches or sub-accounts per revenue center
The decision that shapes the whole chart of accounts: model each revenue-generating department (rooms, F&B, spa, activities) as a branch or as a sub-account dimension under one branch. I lean toward sub-accounts over separate branches when departments share the same legal entity, tax registration, and bank accounts — which is the common case for a single-property resort — because branches in Acumatica imply a heavier operational separation (their own numbering sequences, potential inter-branch transactions) that is more machinery than a resort's internal department reporting actually needs. Sub-accounts give you the same P&L-by-department visibility with less structural overhead.
Sub-account segment structure: DEPT-COSTCTR
DEPT values: ROOMS, FNB, SPA, GOLF, WATER, RETAIL
COSTCTR: direct cost centers within each department
GL entries from PMS/POS feeds tagged by DEPT at import time,
so a departmental P&L is a standard GL report filter, not a custom build.Concessioned outlets need their own AR relationship, not a department code
Resorts frequently license out the dive shop or a specialty restaurant to a third-party operator who charges to the guest's room folio but settles with the resort separately, usually on a commission or rent basis. That is not a departmental cost center — it is a vendor/customer relationship with its own AR and AP, and I have seen this modeled incorrectly as "just another department" more than once, which quietly hides the fact that the resort owes the concessionaire a settlement each month. Model the concessionaire as a proper Business Account with both AR (guest charges collected on their behalf) and AP (commission or rent owed to them) sides, settled through a recurring reconciliation, not folded into departmental revenue as if the resort owned it outright.
If a concessionaire's guest charges post as resort revenue instead of a pass-through liability, the P&L overstates true resort revenue and understates the payable to the concessionaire — a problem that surfaces at year-end audit, not at go-live, which makes it expensive to unwind. Flag this explicitly during discovery for any resort with outsourced outlets.
Wrapping up
A resort is the hotel PMS-boundary problem plus departmental revenue structure plus, often, concessioned operators that need real AR/AP relationships rather than a department tag. Sub-accounts usually beat branches for departmental reporting within one legal entity, and getting concession accounting right up front avoids an audit-time correction nobody enjoys explaining.
Independent software engineer in Nairobi specialising in Acumatica customisations, Laravel backends, and tax fiscalisation integrations across East and Southern Africa.