How to run a headcount and FTE report with HRMS data

A reliable workforce report should show more than the number of people on your payroll. Headcount tells you how many employees your organisation has, while full-time equivalent (FTE) data shows the amount of working capacity those employees represent. Used together, these measures support workforce planning, budgeting, recruitment decisions and executive reporting.

An HR management system can bring employee records, organisational structure, payroll, attendance, leave and recruitment data into one reporting process. For Australian organisations, this is especially useful when teams include full-time, part-time, casual and fixed-term workers across different states, sites or award arrangements.

Define what the report needs to measure

Start by agreeing on the business question. A board report may need total employees and FTE by division, while a finance team may need labour capacity by cost centre and location. A workforce planning exercise could compare approved positions, filled positions, vacancies and projected hiring requirements.

Headcount is a simple people count. One full-time employee counts as one person, and one part-time employee also counts as one person. FTE adjusts the result according to contracted or scheduled hours. For example, two employees working half of the organisation’s standard full-time hours represent one FTE, even though they count as two people in headcount.

The calculation should reflect your own HR policies and employment arrangements. If ordinary full-time hours are 38 per week, an employee contracted for 19 hours contributes 0.5 FTE. However, the correct denominator may differ by role, industrial instrument or agreement. Australian employers should check whether an award, enterprise agreement or employment contract sets a different ordinary-hours arrangement.

Prepare clean HRMS data

Before running the report, review the fields that determine who is included and how each person is classified. At a minimum, check employee status, commencement date, termination date, employment type, contracted hours, standard full-time hours, position, department, manager, location and cost centre.

Decide how to treat employees who join or leave during the reporting period. A month-end snapshot may count anyone active on the final day, while an average headcount report may calculate daily or monthly values across the period. Neither approach is automatically right; the important point is to document it and apply it consistently.

Leave records also need careful handling. Paid annual leave, personal leave and other absences usually do not remove an employee from headcount, because the employment relationship remains active. A well-configured system can keep these categories separate, as explained in this guide to managing leave types, so an absence does not accidentally reduce the reported workforce.

Build the headcount view

In the HRMS reporting area, select the employee population and set the reporting date. Use an active-employee filter for a snapshot, or a date-range filter if the system supports hires, exits and average headcount calculations. Exclude terminated workers after their final employment date, but retain their historical records for turnover and trend analysis.

Add grouping fields that help managers understand the result. Department, business unit, job family, manager, employment type, work location and cost centre are useful options. An organisation with teams in Sydney, Brisbane and Perth may need location-level results, while a national employer could also compare corporate, regional and remote workforces.

Separate permanent full-time, permanent part-time, casual, fixed-term and temporary workers where the HRMS stores those categories. Casual employment can make a raw headcount look larger than the stable labour capacity available on a typical week. Showing employment type beside the total prevents a misleading interpretation and gives finance a clearer basis for forecasting wages and recruitment needs.

Add FTE and compare the measures

The usual FTE calculation is:

FTE = employee’s ordinary or contracted hours ÷ standard full-time hours

If the organisation uses 38 hours as its full-time standard, an employee working 30 hours contributes 0.79 FTE. Three employees working 19 hours each contribute 1.5 FTE in total. For casual workers, use the method approved by your organisation, such as rostered hours, average paid hours or a defined reporting-period average. Avoid mixing methods within the same comparison.

Configure the HRMS to calculate FTE from the appropriate hours field rather than from salary alone. Payroll hours may vary because of overtime, unpaid leave, public holidays or one-off adjustments, whereas contracted hours are generally more suitable for a position-capacity report. A separate utilisation or paid-hours report can show how much work was actually performed.

Review headcount and FTE together. A department with 50 employees and 42 FTE has a different workforce profile from one with 42 employees and 42 FTE. The first may contain many part-time roles, job-share arrangements or reduced-hour positions. That difference affects service capacity, rosters, supervision, recruitment and the cost of filling vacancies.

Validate the report for Australian operations

Run a reconciliation against payroll and the employee register before distributing the results. Compare total active employees, total FTE, starters, leavers and employment types. Investigate mismatches caused by duplicate profiles, missing contracted hours, outdated position assignments or employees assigned to the wrong cost centre.

Pay close attention to Australian payroll settings. Public holidays differ between states and territories, and organisations with sites in Melbourne, Adelaide, Darwin or regional New South Wales may have different operating calendars. Leave balances, roster patterns and ordinary hours should be interpreted alongside the applicable National Employment Standards, award or enterprise agreement.

The reporting period also matters. Many Australian organisations plan against the financial year from 1 July to 30 June, while operational teams may work to calendar quarters or monthly payroll cycles. Set the HRMS date range to match the decision being made. A July budget review should not be compared casually with a January snapshot if seasonal hiring, school holidays or project work changes staffing levels.

Use exception checks before accepting the final version. Look for active workers with zero hours, FTE values above one without a valid explanation, casuals with no reporting basis, terminated employees still assigned to departments and vacancies counted as employees. A short audit trail showing filters, dates and calculation rules makes the result easier to defend.

Turn the report into workforce decisions

Once validated, present the results in a format that connects people data with business activity. Useful outputs include headcount and FTE by department, monthly movement, vacancy levels, employment-type mix, location, cost centre and manager. A dashboard can show current figures, while a downloadable report can preserve the detail needed for payroll, finance or compliance review.

Use trends rather than a single number whenever possible. Rising headcount with flat FTE may indicate a shift towards shorter hours. Falling headcount with stable FTE may suggest consolidation into more full-time roles. A growing vacancy count alongside overtime or contractor costs could signal that recruitment targets are too low or that approval workflows are slowing down hiring.

For workforce planning, compare actual FTE with approved establishment and forecast demand. A contact centre in Melbourne may need more rostered capacity during a seasonal campaign, while a mining services business in Western Australia may need to distinguish office-based employees from site-based rosters. These comparisons help managers decide whether to recruit, redesign roles, adjust hours or redistribute work.

The report should have an owner and a repeatable schedule. Monthly reporting is often enough for stable office teams, while high-volume employers may need weekly figures. Limit access to authorised users, protect salary-related fields and retain the report definition. Organisations reviewing platforms can also use these HRMS selection considerations to check whether their system supports dependable workforce reporting.

Build the report once, document the assumptions and review the figures with HR, payroll and finance. With consistent employee records and clear FTE rules, your HRMS becomes a practical planning tool rather than a simple employee database. Start with a defined reporting date, validate the underlying data and schedule the headcount and capacity view as a regular management report.