HRMIM
BDGT - Budget Planning: What Hotel Budgeting Software Builds, and What It Doesn't

BDGT - Budget Planning: What Hotel Budgeting Software Builds, and What It Doesn't

Onur Işık · Data Analytics & Reporting Lead· 18 November 2026· 13 min read

Seven posts in this series have been about budgeting, and none of them named a product. This one does: BDGT - Budget Planning, HRMIM's hotel budgeting software. The rule for what follows is simple. I describe only what works on screen today, in the screen's own words, and I close with a separate section on what the product does not do.

Building a budget and tracking one: which half this post covers

The series made the reader two promises. The first was one structure across properties: starting from the financial case for a budget, it argued that revenue and expenses should be built the same way at every property. The second was one structure across whatever gets compared: budget against actual, target against outcome, one period against the next. What targets do to behaviour explained why that second half is the hard one.

BDGT - Budget Planning answers part of the first promise. Of the second it answers only period against period, and only at one property. It does not answer budget against actual or target against outcome.

The product builds one property's annual budget. It does not track that budget once it is built: no screen sets actuals against it, it calculates no variance, and it does not roll properties up into a single view. That is not an apology; it is the scope, and it is better stated up front than discovered in a demo. The sections below follow the product's tabs in build order, not screen order. The last one lists, item by item, what it leaves out.

One budget, one property, one period

A budget is opened from the Budget Events menu with New Budget Event. It belongs to one company and one property. On screen, the field where you pick the property is labelled Branch, and it is mandatory. Each budget sits on an annual licence, and its dates must fall inside that licence's window. The same dialog sets the Budget Type, the required Expense Breakdown Level, Starting Data and the optional Stock Budget, Shops and Distribute.

You cannot open a second budget for the same property over overlapping months. The system does not quietly block it; it refuses and says a budget already exists in that date range for this branch. One property, one period, one budget.

A budget's state comes from its dates, not from a start button: upcoming, in period, or period ended. Edit Budget changes the title, the description, the season and, in an Advanced Budget, Wage Entry. The dates, the branch, the licence and the other options are read-only once the budget exists. Any budget that is not locked can be deleted.

Access follows scope. Every read and every write checks company, property and product scope, so a user tied to one property sees only that property's budgets.

The boundary that follows is plain: a budget is a property. There is no view that gathers several properties into one budget or one report. The Distribute tab lists the other branches on one grid, but it is an allocation: it writes one budget's operating expenses into other branches' budgets as figures, by ratio. Each budget also runs on its own period; there is no shared calendar across properties.

The chart of accounts sits with the company, the budgets with the property

The chart of accounts is held at company level, not property level. Every property budget in a company uses the same chart, and the chart carries over from year to year: next year's budget inherits this year's mapped chart.

On the Chart of Accounts tab, the chart comes in through a template from your own accounting system's export, and goes back out the same way. An import updates accounts that exist, adds the ones that don't, and never deletes a line behind your back.

The account list is created in one place only. The Revenue, Expenses and Personnel screens read that list; they cannot add lines of their own. Each account is mapped to a top-level group, and two things about that group are fixed: its direction (revenue or expense) and its level in the P&L (operating, above EBIT, below EBIT). An account cannot be revenue on one screen and an expense on another. The set of top-level groups ships with the product and is the same for every company; companies do not define their own.

The industry has a reference account structure: the 12th Revised Edition of USALI, effective 1 January 2026. This product holds one chart of accounts per company and maps it onto a fixed P&L grouping. The mapping is yours to do.

There is one more safeguard. An account or cost centre used in a locked budget cannot be edited, deactivated or overwritten by an import. The system refuses, and names the budget you would have to unlock. Adding new accounts is still allowed. So a closed year cannot be quietly restated through the shared chart.

The Trial Balance panel on the Chart of Accounts tab takes a branch's 6xx/7xx accounts for a year as an .xlsx, stores them and shows them by account and month. Its job is to be a source for a budget; the product's own label is Last Year's Actuals. No screen sets the trial balance against the budget.

Cost centres: the same list as the HR unit list

The Cost Centres tab holds the company's cost-centre list. Each centre is tied to a company department, which in turn sits under the wider department and division structure. Template, import and export work as they do for the chart of accounts.

The detail worth knowing: this is the same list as the company's HR unit list. There are not two lists to keep in step, so a department in the budget and a department on the personnel record do not need separate upkeep.

A cost centre is structure, not an owner. Nobody is assigned as responsible for a centre or a department.

The Statistics tab: occupancy, capacity and the budget's own exchange rates

The Statistics tab holds the budget's assumptions, month by month: operating days, room count, bed count, room occupancy and bed occupancy. Occupancy is entered as a rate, and a value above full occupancy is refused.

Some figures are not entered at all. Rooms and beds available for sale, rooms and beds sold, and persons per room are calculated from those assumptions and never stored, so they move whenever an assumption moves.

The same tab holds the budget's own monthly exchange rates against the Turkish lira. They are not fed from the market and they do not change by themselves. That is deliberate: a budget year you have locked does not shift because the market did. The budget stays on the assumptions it was written on.

The revenue budget: account × month, as a total, per room or per person

On the Revenue tab, the rows are the accounts mapped to revenue and the columns are the budget's own months. The budget does not have to start in January; the columns follow its period. Fill on the ribbon populates lines from last year's trial balance or the last budget, with a rate and a preview.

Each line gets an amount type and a currency. The amount type is a total, per room or per person. A per-room line's monthly figure is the amount entered multiplied by that month's rooms sold, and rooms sold come from the occupancy on the Statistics tab. A per-person line works the same way off the number of persons derived from those assumptions. Change the occupancy and those lines recalculate on their own.

An empty cell means "not budgeted" and is kept distinct from a budgeted zero. It looks like a small distinction. It is the only thing that tells you whether a line was forgotten.

The optional Shops tab writes monthly shop rents to a revenue account.

This needs saying plainly. How the revenue budget is built built rooms revenue as ADR × occupancy × segment. This product does not budget revenue by segment, channel, ADR or RevPAR. It builds revenue per room and per person against the property's occupancy assumptions. ADR and RevPAR are outputs on the Summary, not inputs. The argument about segment mix in that post still holds; that calculation lives outside this product.

The expense budget: the same chart, the same months

The Expenses tab starts from the same frame as revenue: the accounts mapped to expense, the budget's months, an amount type and currency per line, the same distinction between an empty cell and a zero, and the same Fill.

The product does not sort costs into fixed and variable. Drawing the fixed and variable split is your call. What the screen gives you is the amount type: enter an expense line per room or per person and it moves with the occupancy assumption; enter it as a total and it doesn't. Which line behaves which way is your decision.

Where it parts from revenue is the breakdown. Every new budget has a required Expense Breakdown Level: Division, Department or Cost Center. Each Expenses line opens into those parts, and the choice cannot change afterwards. Revenue lines are not split.

On the optional Stock tab, the materials, Opex and Capex plan arrives by Excel. An amount not mapped to an account does not reach the Summary.

Personnel (Basic Budget): headcount by department and month

In a Basic Budget, the Personnel tab works on a department-by-month grid. On the Personnel Counts sub-tab you enter each department's headcount for each month. A new Basic Budget has no wage entry: Personnel Wages appears only if the budget already holds wage figures. Headcount can be fractional, which is how you budget a head-office person shared between two properties.

The screen labels this as budgeted headcount and states in its own words that it is not connected to actual headcount in HR. What you enter here is a plan, not a count.

The Personnel Expenses sub-tab holds personnel cost accounts such as meals, uniforms and transport. Each line is split across cost centres, and the undistributed remainder is shown separately, so nothing left unassigned slips past.

Basic or Advanced: a choice made once, at creation

Every budget is either a Basic Budget or an Advanced Budget. The choice is made once, when the New Budget Event is created, and it does not change afterwards.

A Basic Budget runs on the screens above. An Advanced Budget adds position-level staffing, payroll calculation, booking of payroll cost to expense accounts, and mid-year raises to the personnel side. The next two sections cover them.

Advanced Budget: positions and Payroll Parameters

In an Advanced Budget, the sub-tabs are, in order, Payroll Parameters, Personnel Counts, Staff Salaries, Personnel Wages and Personnel Expenses. On Personnel Counts, each row is a department and a job title, both picked from the company's own lists; there is no free text. Counts can be entered monthly, weekly or daily; the monthly wage sits on Staff Salaries.

Build from Employees generates position rows from the property's current active employees, grouped by department and job title. No wage is filled in, because the HR record holds none. This is the only point at which the product touches HR data.

In the live view, employer cost is computed when the budget is read; every draft and V.NN keeps a frozen copy as priced at that moment. Wages are written in one place, Staff Salaries. Personnel Wages is a read-only computed table.

The Payroll Parameters sub-tab holds the year's payroll parameters for each budget month: categories such as minimum wage, social security, tax brackets and provisions. For years the central set contains, the values come from that set; a year it does not contain starts empty. The company can overwrite the values and, as the screen says, owns their accuracy. Reloading the central values is a separate, deliberate action; a change to the central set does not silently re-price a budget that already exists.

The settings are per budget: Wage Entry (net-to-gross or gross-to-net), Incentive Points, Provision Method, Notice Period and Annual Leave Days. A calculation scheme is also applied by staff type: standard, working retiree, compulsory intern, subcontractor. Those schemes are configured centrally by the platform, not by the company.

Expense Accounts and Raises: booking payroll cost to accounts

Expense Accounts, opened from the Personnel Expenses ribbon, breaks payroll cost into its components and books each one to a personnel expense account: gross pay, employer social security after incentive, employer unemployment contribution, severance, leave and notice. Whatever is not mapped to an account stays in departmental payroll.

Raises, opened from the Staff Salaries ribbon, holds mid-year increases. A raise is set as a rate or a fixed amount from a given month, and applies to all rows, one department or one staff type; each Staff Salaries row also has its own Raise Month and Raise %. Several raises compound in month order. Pay-scale raises are not part of it.

The Summary tab: G.O.P, EBIT and N.O.P, live figures and frozen copies

The Summary tab (İcmal in the Turkish interface) is a hotel P&L ladder. Revenue less operating expenses gives G.O.P. G.O.P less above-EBIT expenses gives EBIT. EBIT less below-EBIT expenses gives N.O.P. The ladder's lines come from the top-level groups the accounts are mapped to, so the Summary is a direct result of the structure you built on the Chart of Accounts tab.

The live Summary stores nothing. It is recomputed from the entered figures every time it is opened, which means it cannot disagree with the Revenue, Expenses or Personnel screens. The second copies exist on purpose: every draft and every V.NN stores a frozen Summary as it stood, and it can drift from the live view.

The Summary has three views: Table, Indicators and Departments. Table can be read as a total, per room or per person, in any currency with a rate in every month. Indicators computes ADR, RevPAR, TRevPAR, GOP Margin and GOPPAR from the budget's own figures. Headcount sits in Departments and is not added into the P&L.

This is one property's summary. There is no group or consolidated P&L that brings several properties together.

Approve, lock, compare: fixing a year and setting it beside the last budget

The General tab shows how much of the budget is filled in, and it counts in cells rather than impressions: cells expected against cells entered. Its setup counters double as a to-do list, pointing at whatever step is still open.

Approve And Lock freezes the figures, account mappings, cost centres and assumptions and writes a numbered version: V.NN. Unlock reopens them, and the version stays. A locked budget carries the Locked badge. The button approves, but one person approves: a user with edit permission does it in one click, and it does not ask for a second person's sign-off.

The budget calendar ended on "approve and lock". This product carries that step in one click. It does not carry the process around it: no calendar, no deadlines, no reminders, no workflow and no second person.

The Drafts tab compares drafts, each saved with a note, and versions in columns with a Difference. You can return to a draft; drafts can be deleted, versions cannot.

Copy carries the whole budget into next year at the same branch, with no percentage applied; draft and version history does not travel. Every figure keeps its position in the year. Months that fall outside the new period are dropped, and the dropped figures are counted and reported to you rather than lost quietly. A new budget can also begin from Starting Data: Empty, Last Year's Budget or Last Year's Actuals, with a % Increase. Because the chart of accounts also carries over, and a locked year cannot be restated through it, two years end up defined the same way.

Being defined the same way is what makes a comparison mean something. The Comparison tab sets the previous budget beside this one, with Difference and Change Ratio; the Approved Version can be set against it too. It works within one branch, against the single previous budget the system picks. The Difference here is budget against budget, not against actual. There is no screen that puts several properties side by side.

Export writes the budget's main sheets to a single Excel workbook using the same arithmetic as the screens, and anyone who can view a budget can export it.

What this product does not do

This section is not a footnote. It is what makes every claim above testable: each one comes with its edge written down.

  • No budget-versus-actual. A trial balance can be uploaded and used to fill a budget, but no screen or report sets actuals against the budget, and no variance is calculated. The argument in the budget-vs-actual variance stands as written; this product does not answer it.
  • No link to actual headcount in HR. Apart from Build from Employees, there is no HR connection: neither actual headcount nor pay comes in from HR.
  • No group or consolidated view, and no screen putting several properties side by side. Comparison stays within one branch, and Distribute is an allocation.
  • No shared budget calendar. No common deadlines, milestones or reminders across properties.
  • No approval workflow. No submit-review-approve chain and no four-eyes check. Approve And Lock is one person's action and writes a V.NN that cannot be deleted.
  • No owners. Nobody is assigned to an account, a department or a cost centre. The case made in departmental budget ownership still stands, and this product does not meet it.
  • No link to the KPI product. The scorecard on the measurement side is a separate product, and nothing connects the two.
  • Revenue is not budgeted by segment, channel, ADR or RevPAR. Exchange rates are not pulled from the market; that is a design choice, not a gap.

In short, this product does the building half of a budget and sets a new budget against the last one. For tracking a budget against actuals, everything the series argued still applies, and it is still your work.


If you want to walk through your own budget structure against these tabs, and see which parts of it already sit in one chart of accounts and one Summary and which parts don't, get in touch.

Get New Posts by Email

We will email you when a new blog post is published.

Loading the form…

Related Posts

Revenue Budget: Building Rooms Revenue from ADR × Occupancy × Segment

Revenue Budget: Building Rooms Revenue from ADR × Occupancy × Segment

Rooms revenue is not one number, it is a product: ADR × occupancy × rooms × days. Without a segment breakdown that product disappears into averages, and the budget loses its power to explain what actually happened. This piece builds a revenue budget segment by segment: separate ADR and occupancy assumptions for OTA, corporate, direct and group business, what a shift in mix does to total revenue, and why RevPAR alone is a weak budget target. Works through a table labelled hypothetical throughout.

9 September 2026 · 13 min read

Hotel Budgeting: The Real Cost of Running the Season Blind

Hotel Budgeting: The Real Cost of Running the Season Blind

The season closes, you have the numbers — and nothing to compare them against. A budget is not a forecast; it is a record of decisions, committing on paper which cost you took on and why. This piece sets out what managing without one costs: decisions arrive late, variances stay invisible so they never get corrected, cash flow stays exposed mid-season, and purchasing loses its negotiating position. Ends with a hypothetical side-by-side and how the USALI account structure makes budgeting easier.

12 August 2026 · 14 min read

Expense Budget: Fixed or Variable in a Seasonal Operation?

Expense Budget: Fixed or Variable in a Seasonal Operation?

In a seasonal operation the fixed-versus-variable split is never as clean as the textbook. Is a caretaker's wage through the closed months fixed, or is it a decision about how long the season runs? This piece builds the expense budget on that distinction: how payroll, energy, maintenance and cost of goods actually behave, why costs do not fall as fast as revenue does, and how capacity commitments should appear in the budget. Closes on a break-even calculation for a seasonal property.

7 October 2026 · 16 min read

Let's work with HRMIM

Explore our platform free of charge.