Headcount infrastructure

What is headcount infrastructure?

Headcount infrastructure is the system that holds every position, planned, open, or filled, keeps it reconciled across your ATS, HRIS, and FP&A tools, and enforces the approvals, permissions, and audit trail around it.

Two colleagues talking at a desk with large monitors in a bright open office

How it fits together

One layer between your systems and everything on top

headcount365 reads from your HRIS, syncs with your ATS, and feeds your FP&A, so every headcount has one ID from plan to hire. Everything on top of it uses the same data and the same permissions.

Diagram: your HRIS (read, never written to), ATS (two-way sync), FP&A, and other sources feed headcount infrastructure: unified dataset, reconciliation, approvals engine, access control, integrations, and security and reliability. On top of it run the headcount365 app, your AI tools through MCP, your own tools through API, and scheduled reports. Each headcount keeps one ID from hiring plan seat to ATS requisition to HRIS employee.

What happens on it, every time a role moves from request to hire, is headcount orchestration. How orchestration works →

Four colleagues around a conference table, smiling as they review a plan on a laptop

Why it matters

Why headcount needs its own infrastructure

Headcount is usually the largest line in an operating budget, yet it lives in three systems that each describe a seat differently.

  • One ID for every seat, instead of a different ID for the same seat in Finance, Recruiting, and HR.
  • Reconciled automatically, with mismatches flagged for a person to confirm, instead of spreadsheets reconciled by hand.
  • Permissions that follow your org, from your HRIS reporting structure, instead of compensation traveling in exports.
  • Live data for AI, read under each user’s permissions, instead of stale copies.
  • Every decision on record, with each request and approval logged, instead of decided in email.

One ID for every headcount, in every system.

The parts

What headcount infrastructure is made of

Six parts work together. Remove any one and the numbers stop agreeing across teams.

A headcount verified as one record across ATS, HRIS, and FP&A, with a resolved discrepancy

Unified dataset

Every headcount, whether an existing employee, a vacant seat, a new hire, or a backfill, carries one ID across the hiring plan, ATS, HRIS, and FP&A.

Unified dataset →
Reconciliation view comparing plan, ATS, and HRIS values for each headcount, with a mismatch flagged

Reconciliation

An automated process, with human review, that confirms each headcount stays one ID as it moves from plan to requisition to employee.

Employment action requests, such as backfills, transfers, and promotions, routing to approval

Approvals engine

Approval routing built for headcount, with backfill salary comparisons and routing by headcount owner, office tier, and title.

Requisition form with field-level permissions set for each user

Access control

Field, action, and hierarchy permissions, so compensation is visible only to the right people.

Also part of the infrastructure

  • Integrations and security

    Maintained connectors to your ATS, HRIS, and FP&A tools, under an audited security program.

    Integrations
  • Agentic access

    A governed connection, such as an MCP server, that lets AI agents read and update headcount data, with each user’s role-based permissions applied.

    headcount365 MCP

How it compares

Headcount infrastructure and the systems you already have

Headcount infrastructure connects these systems. It doesn’t replace any of them.

SystemBuilt forWhat it leaves out for headcount
HRISEmployee records, payroll, and benefitsPositions before someone is hired, and approvals for new roles
ATSCandidates and requisitionsThe budget behind a role, and the employee after the hire
FP&A toolBudgets and forecastsLive requisition status and hires as they happen
Data warehouseStoring and analyzing copies of dataApprovals, field-level permissions, and maintained connectors
Headcount infrastructureOne ID per position across all of the above, with approvals, permissions, and an audit trailNothing it needs to replace: it reads from and connects the others

Infrastructure and orchestration

What it runs on, and what happens on it

Headcount infrastructure

The foundation: the unified dataset, reconciliation, approvals, access, integrations, and security.

Headcount orchestration

What happens on the foundation, every time a role moves from request to hire.

Where it happens

In an app such as headcount365, in tools you build, or both, on the same data.

Dave Govert
“HC365 is a single source of truth spreadsheets simply couldn’t deliver, bringing real proactivity and transparency to our hiring process.”
Dave GovertVP, Talent Acquisition
Three colleagues standing in an office, laughing during a conversation

Common questions

What is headcount infrastructure?

Headcount infrastructure is the system that holds every position, planned, open, or filled, keeps it reconciled across your ATS, HRIS, and FP&A tools, and enforces the approvals, permissions, and audit trail around it.

Is headcount infrastructure the same as an HRIS?

No. An HRIS manages people who are already employed. Headcount infrastructure manages positions, including planned and open ones, and keeps them reconciled with the HRIS, the ATS, and FP&A tools.

Do we need it if we have a data warehouse?

A warehouse stores copies of data for analysis. It doesn’t run approvals, enforce who can see whose salary, or maintain connectors to your ATS and HRIS. Many teams keep the warehouse for analytics and send reconciled headcount data into it.

How do AI tools use headcount infrastructure?

Through a governed connection such as an MCP server. AI tools read and update the same unified data as everyone else, and each user’s role-based permissions apply to every request.

How long does it take to put in place?

With headcount365, most teams are live in 2 to 4 weeks.

See headcount infrastructure on your data

We’ll connect your systems and show you every headcount reconciled to one ID.