Position control: budgeted positions, vacancies, and the HR-finance link

Reference article · 6 min read

Headcount questions sound simple until two reports disagree. HR counts employees on the roster. Payroll counts people who were paid in the last cycle. Finance counts salary lines in the adopted budget. Each system is internally correct, and none of them directly answers the question a council member or board chair actually asked, which is how many authorized seats exist, how many are filled today, and what the rest will cost between now and the end of the fiscal year.

Position control is the discipline, and usually the software module, that makes those views reconcile. It treats an authorized position as a record in its own right, separate from whoever occupies it, and ties that record back to the budget authority that funds it. Agencies with working position control answer a vacancy question in minutes. Agencies without it rebuild the answer in a spreadsheet every time someone asks.

The position record is not the person record

The most common design failure is treating a position as an attribute of an employee. It is the reverse: the position exists first, and people move through it. A usable position record generally carries:

• Position number. A stable identifier that survives turnover, reorganization, and system migrations.
• Authorized FTE. Often 1.00, but part-time and shared seats need fractional values that roll up cleanly.
• Classification and pay range. The class, grade, and step range the seat is authorized at, which is what drives cost projection for a vacancy with no incumbent.
• Organizational placement. Department, division, and reporting unit, aligned to the same hierarchy finance uses.
• Funding distribution. One or more account strings with percentages that total 100.
• Status and effective dates. Filled, vacant, frozen, abolished, or proposed, each with a date so history is reconstructable.
• Incumbent history. Who held it, when, and at what step.

When the position record holds this, a vacancy still has a cost. That is the point. Finance cannot project salary and benefits for an empty seat unless the seat itself describes what it is authorized to pay.

From adopted budget to authorized FTE

Position control is the bridge between a legislative act and an operational roster. A governing body adopts a budget that, in most jurisdictions, also authorizes a specific staffing level, sometimes in a position ordinance, staffing schedule, or personnel complement exhibit attached to the budget document. Authority to create, abolish, or reclassify positions mid-year, and whether the executive can do it administratively or must return to the governing body, is set by local charter, ordinance, or state law. Confirm your own rules with counsel rather than assuming a neighboring agency's practice applies.

The chain to maintain is: adopted authority, then authorized positions in the system, then filled and vacant seats, then payroll actuals. Every link should be reconcilable to the one before it. Mid-year amendments, reclassifications, and transfers between departments are the points where the chain usually breaks, so each should produce a dated record in the position module, not just an email approval.

Funding splits, grants, and allocation

Split-funded positions are where position control earns its cost. A seat funded partly by a federal grant, partly by an enterprise fund, and partly by the general fund needs distribution percentages that sum to 100 and that flow to payroll distribution automatically. Two practices matter:

• Tie grant-funded positions to the award period. When a grant ends, the position record should surface that date well in advance so the agency decides deliberately whether to absorb, abolish, or hold the seat.
• Keep charging consistent with effort. Federal awards generally require that charges to the award reflect work actually performed on it, supported by records maintained by the recipient. The specific documentation expectations sit in the federal uniform administrative requirements and in individual award terms, and they change. Verify current requirements with the awarding agency and your grants staff.

Frozen, underfilled, and overfilled positions

Real staffing does not stay tidy, and the system has to represent the exceptions rather than force staff to work around them:

• Frozen or held vacant. A seat retained in the authorized count but deliberately left unfilled to generate savings. It should still show as authorized, and its projected cost should be adjustable.
• Underfill. Hiring at a lower classification against a higher authorized seat, common for trainee and apprentice paths. The projection should follow the incumbent's actual pay, not the authorized ceiling.
• Overfill or double encumbrance. Two incumbents briefly occupying one seat during training or a retirement overlap. If the system forbids this outright, departments will process the second hire somewhere invisible to finance.
• Vacancy factor. Many agencies budget a negative adjustment reflecting expected turnover savings. Record where that factor is applied, because applying it both centrally and at the department level double counts the savings.

Reconciling the roster to the salary projection each month

Make reconciliation a scheduled routine with a named owner, not an exercise triggered by a surprise.

1. Snapshot HR's position roster and finance's salary projection as of the same date and pay period.
2. Compare authorized, filled, and vacant counts by department and by fund.
3. Categorize every variance: mid-period hires and separations, transfers, positions added or abolished by amendment, reclassifications, changed funding splits, and timing differences between the effective date and the pay date.
4. Reproject the remainder of the year using actual steps and current benefit rates for filled seats, and authorized-range assumptions for vacant ones.
5. Log unexplained differences and carry them forward until cleared.

Recurring mismatches usually trace to a small set of causes: temporary and seasonal staff paid outside position control, contractors coded as employees, employees paid from a position abolished on paper but not in the system, and effective-dated changes entered retroactively.

What to ask vendors and how to start

When evaluating an HR, payroll, or ERP system, ask for demonstrations rather than assurances:

• Show a vacant position projecting salary and benefits with no incumbent attached.
• Show a position split three ways, including a grant with an end date, and the resulting payroll distribution.
• Show what the system does when a hire would exceed authorized FTE, and who can override it.
• Show an as-of-date report reconstructing the roster for a prior month, after later retroactive changes were entered.
• Show the audit trail for creating, reclassifying, and abolishing a position.

In a contract, require conversion of position history and not only current incumbents, a documented reconciliation report between the HR roster and the financial salary projection, and acceptance criteria tied to a clean reconciliation across at least one full budget cycle before final payment.

To start without a new procurement, take one department, build a clean position list from the adopted budget, reconcile it against payroll for a single pay period, and write down every discrepancy and its cause. That list will tell you whether your problem is configuration, process, or software.

HQT works with state and local agencies on enterprise systems and data integration, including the reporting and reconciliation layers that connect HR, payroll, and budget data.

Frequently asked questions