Plan your hotel’s operating result.
Not just the revenue.

Plan, outlook and variance to GOP in one view, payroll at department level, and every number traceable to where it came from.

Commit the version the team agreed, keep closed months read-only in a mid-year revision and record why the rest changed.

Pick a recipe per line and set its parameters; the platform computes twelve months. The F&B manager plans F&B and nobody else’s payroll.

Commit the plan once. Watch the expected year change beside it.

Committing a plan freezes its values, exchange rates and rules: that is the reference the year is measured against. Beside it, Outlook is the live read. Closed months take actual revenue; open months take the bookings already on the books plus the pickup the committed forecast still expects. Cost lines with a recipe follow the volumes either way, such as cleaning per room night or commission per booking, while payroll and manual cost lines stay at plan. So the outlook GOP is an expected result built on actual revenue and modelled costs, not a closed accounting figure: Peaqplus receives no cost actuals.

Variance shows where the hotel stands against plan, with GOP margin in percentage points. Scenarios answer “what if” without touching the plan: override the six base metrics, such as −10% room nights or +5% covers, and read the effect on every recipe line and on GOP. Up to ten named scenarios per plan.

Every department rolls up to one GOP.

Operating Budget follows the departmental layout of USALI, the international standard for hotel management accounts: operated departments such as Rooms, F&B, Spa and Other, and undistributed areas such as Administration, IT, Marketing, Maintenance and Utilities (Energy, Water and Waste in USALI 12). Each department carries its own revenue, cost of sales, payroll and other expense lines.

Department results and GOP are calculated the same way for every hotel, so the plan reads the same in the Department, USALI or general-ledger view. A line that fits no catalogue item waits in a visible “unassigned” group until you classify it.

Choose the depth line by line, not for the whole plan.

Every line starts as one annual number that the platform spreads over twelve months. When a line deserves more, open it: type twelve monthly values, paste a column from your spreadsheet, or pick a recipe such as room nights × average rate, guest nights × 40% × €17 for breakfast, or 28% of F&B revenue for cost of sales.

A controller can chain lines together, with a cost that refers to a revenue line or to the whole hotel’s revenue, without writing a formula. The platform checks the chain for circular references before saving, and a manual value stays as a fallback if the recipe is removed.

What we know about your hotel is filled in. What we do not know, we ask.

The structure wizard asks only what the platform cannot read from your data, in four steps: which departments exist, whether you plan by segment, and how deep the payroll should go. A department you switch off is never created. Values fill in layers: last year’s actuals, then the committed forecast, then the anonymous peer median where at least three similar hotels exist, otherwise the cell stays empty. No invented ratios.

Every filled cell shows where its value came from, and a value you type is never overwritten. A completeness list, not an error list, shows what is still missing: a required department, an energy line, a payroll position, an empty base metric. One click adds it.

Plan people and hours. The platform adds the employer cost.

Payroll is planned by position and month, not as one percentage: FTE, base pay and working days per position, with joiners, leavers and a mid-year raise on the timeline. Four employment forms are modelled separately: permanent, casual (Hungarian EFO), agency and contractor.

The employer contributions for Hungary in 2026 are built in and verified against the official rates, so the plan shows total employment cost, not just wages. When a plan would exceed the casual-day ceiling per person or the headcount limit for casual staff, it warns in yellow and lets you decide. A rule change becomes a new rule version; a committed plan keeps the rules it was committed with.

A committed plan is not edited. A revision is a new version with a reason, and the past months of the running year stay read-only, so the history is never rewritten.

Viewer, editor or plan owner; payroll by position or aggregated by department; a department head limited to their own lines. Two editors cannot overwrite each other silently.

Planned and expected monthly occupancy, ADR and RevPAR against the average and median of an anonymous peer pool, with at least three peers behind every cell.

Contracts in EUR, payroll in HUF: a line in any currency converts at the plan’s fixed rates, frozen on commit, into the hotel’s operating currency.

Start the Operating Budget from the committed revenue Budget in one click, with a preview first. The Budget stays where it is; nothing is migrated away.

During onboarding we set which plan the year’s reports, Insight tiles and email reports read from, and it can be set back. Until then the revenue Budget stays the source.

The GM answers seven questions, switches off the spa the hotel does not have, and gets a draft filled from last year’s actuals, the forecast and the peer median.

The F&B manager plans covers and cost of sales at 28% of F&B revenue; the controller chains card commission to total revenue.

Values, exchange rates and payroll rules freeze. The plan becomes the reference, and the rollout team sets it as the live source for the year’s reports.

Two closed months at actual revenue with modelled costs, ten open months at bookings plus expected pickup. The written summary names the month and the line that move GOP most.

The market shifted. A new version with the reason “mid-year revision”: January to May stay locked, the rest is updated, v1 remains for comparison.

Plan GOP beside expected GOP in one view, payroll aggregated by department. Nothing to ask for, nothing to reconcile.

Hotel operating budget software builds the full annual operating plan for a hotel, revenue, costs and payroll by department, and rolls it up to department results and gross operating profit (GOP). Peaqplus Operating Budget does this in USALI structure, with versions, an outlook against the committed plan and scenarios, from the data already in the platform.

Budget, included in BI Core, is the commercial revenue plan for room nights, ADR and revenue. Operating Budget is the optional add-on for the full P&L: departmental cost lines, payroll, GOP, outlook and scenarios. The two coexist: an Operating Budget can start from the committed revenue Budget in one click, and during onboarding we set which plan the year’s reports read from.

Forecasting is the revenue manager’s committed expectation of room nights and revenue. Outlook is the P&L reading of that expectation beside the plan: actual revenue for closed months, bookings on the books plus the remaining expected pickup for open months, with recipe-driven cost lines following the volumes. Payroll and manual cost lines stay at plan, because Peaqplus receives no cost actuals, so the outlook GOP is an expected figure, not a closed accounting result.

No. It plans; it does not post entries, run payroll or reconcile actual costs. The general ledger, cost actuals and payroll processing stay in the hotel’s accounting and payroll systems. Plan-versus-actual comparison in Peaqplus is available on the revenue side.

The 2026 Hungarian employer contribution rules (social contribution tax, the tax on SZÉP benefits, casual-employment daily rates and ceilings) are built in and verified against the official values. For other countries you enter an effective employer contribution rate; progressive bands are not modelled yet. The warnings are guidance, not legal advice.

Not yet. Monthly values can be pasted in from a spreadsheet, and the plan is read inside Peaqplus in the Department, USALI or general-ledger view. A spreadsheet export of the operating plan is not available at the moment; the Excel and PDF export listed on the pricing page covers the BI report library, not this plan. If export is a condition for you, say so at the demo and we will tell you plainly where it stands.

Operating Budget is €79/month per property at the current intro price, as an add-on to any plan; it is not included in Starter, Growth or Pro. Setup is a one-time €135 with 2 hours of team training. For a new hotel with up to 49 rooms, Starter plus Operating Budget is €188/month with a €270 one-time setup. Prices are net of VAT; yearly billing receives a 10% discount.