The short answer: Integration theatre is when HR, payroll and workforce software looks like one platform on screen but runs as separate systems underneath. Every hidden handoff is a place for pay errors, compliance gaps and reconciliation work to creep in. This paper is written for CEOs, CFOs and payroll and HR leaders. It explains how integrated and unified human capital management (HCM) platforms differ and sets out five tests to run before you sign.

The demo looked perfect. Month six told a different story.

Consider a typical evaluation (a composite scenario, for illustration only). The demo is flawless: single sign-on, slick navigation, leave approvals that update payroll, rostering changes that flow into compliance reporting. Six months after go-live, leave approvals need manual payroll corrections. Performance data is exported and re-imported to model pay reviews. A rostering change triggers a compliance alert that takes days to trace across three data structures. The interface was real. The integration underneath was theatre.

Why this is an executive issue, not an IT one

Pay and compliance risk. Modern awards, enterprise agreements and the National Employment Standards all apply at once. A rule change has to land consistently across payroll, rostering, leave and reporting, or underpayments follow. Tighter payment obligations, such as Payday Super, leave less time to find and fix errors after the fact.

Hidden running costs. Reconciliation hours, integration maintenance and custom development rarely appear in the business case, but they recur every year.

Slower, less trusted decisions. If workforce reports need exporting and manual manipulation, leaders get late numbers they are reluctant to rely on.

No single owner. When an issue crosses systems, vendors can point at each other while your team absorbs the delay.

Integrated vs unified HCM: what is the difference?

Integrated HCM connects separate systems so data and processes can work together. Unified HCM operates as one environment, with shared data, workflows and security and one accountable owner for the whole platform. Integration is about the connections between systems. Unification is about whether those connections are needed at all.

Area
Integrated
Unified
Employee data
Held in separate databases and synchronised.
One employee record referenced by every function.
Workflows
Handoffs between separate workflow engines.
Processes run end to end across functions.
Award and policy change
Updated in several places, then checked.
Changed once and applied consistently.
Security and audit
Separate permissions and logs to stitch together.
One permissions model and a complete audit trail.
Support and accountability
Module-specific teams with blurred ownership.
One accountable owner for cross-functional issues.
Reporting
Often needs export and manual consolidation.
Cross-functional reports built directly from shared data.

A single vendor is not the same as a unified platform. One login, one contract and one logo can still sit on acquired or bolted-together modules. What matters is how the platform behaves under operational pressure, not how it is packaged.

Five tests to run before you sign

Ask each vendor to run these scenarios live, in a production-like environment and using your own rules where possible. Watch for re-keyed data, manual steps and handoffs.

Role change.

Change an employee’s reporting line, pay, access and roster. Does it flow from one entry, with no re-keying or manual follow-up?

Extended leave.

Can one request drive approval, payroll adjustment, roster backfill, compliance records and return-to-work planning without re-keying or reconciliation?

Award or agreement change.

Update the rule once. Do payroll, rostering and compliance reporting pick it up consistently, and can you see who was affected?

Cross-functional reporting.

Can recruitment, performance, pay and retention data be reported on directly, without a spreadsheet in the middle?

Data currency.

Are dashboards current across functions? Batch processing is not automatically a defect, but unexplained delays and synchronisation warnings are. Ask which updates are immediate, which are scheduled and whether any delay affects pay, compliance or access.

A platform that needs workarounds in the demo will need them in production.

Six questions that expose integration theatre

Where does the authoritative employee record sit?

Does employee data exist once and get referenced everywhere, or is it synchronised between copies? References to “sync” or “replication” deserve follow-up.

Who owns an issue that crosses modules?

Specialist support is fine, but ownership should sit with one accountable team and one escalation path.

How much custom work connects standard processes?

If linking payroll to leave or rostering needs professional services, is the requirement genuinely yours, or a gap in the platform?

Do security and audit work as one?

Look for one permissions model and one complete audit trail per transaction, not logs to correlate across modules.

How do upgrades and updates reach every module?

Do they arrive together as one release, or on separate schedules that need coordinating and re-testing across your environment?

Can we see it live and speak to a similar customer?

Ask for a demonstration in a production environment, and for reference calls about processes that span modules rather than general satisfaction.

Phased rollouts can be sensible risk management. The red flag is a plan where each phase means building connections between separate products.

What integration theatre costs

Ask finance to put numbers on these in your current environment before comparing vendors:

  1. Hours spent reconciling data and correcting errors each pay cycle
  2. Annual cost of maintaining integrations and custom development
  3. Effort spent on audits, underpayment reviews and remediation
  4. Management time lost to late or distrusted workforce reports
A simple starting point: (reconciliation and correction hours per pay cycle × pay cycles per year × loaded hourly cost) + annual integration maintenance and custom development spend.

Then ask each vendor to show, in writing, how their platform reduces each line.

Keep testing after go-live, and protect it in the contract

Unification is proven in business as usual, not in the demo. Track these after go-live:

  • How long a pay-affecting rule change takes to apply across payroll, rostering and reporting
  • How long it takes to diagnose and resolve issues that cross functions
  • Reconciliation and manual correction hours
  • The effort needed to apply updates and patches

Then write those expectations into the agreement, with procurement and legal advice: service levels for end-to-end processes rather than individual modules, warranties on which standard processes should run without custom development, re-keying or reconciliation, and defined ownership and escalation for issues that cross functions.

How Frontier Software approaches unified HR and payroll

Frontier Software’s view is that a platform should be judged on how it behaves under operational pressure, not on how it looks in a demonstration. We encourage buyers to put every platform, including ours, through the five tests above. Payroll accuracy, compliance confidence and strategic capability all depend on what happens beneath the interface.

Frequently Asked Questions

What is integration theatre in HR and payroll software?

Integration theatre is when software looks unified through shared branding, navigation or single sign-on, while data, workflows, security or support remain fragmented underneath.

What is the difference between integrated and unified HCM?

Integrated HCM connects separate systems. Unified HCM operates as one environment, with shared data, workflows, security and accountability.

Is a single vendor the same as a unified platform?

No. A single vendor can still supply modules that were built separately or acquired. Test how data, workflows and support behave across functions.

How can I tell if HR and payroll software is truly unified?

Run real cross-functional scenarios, such as a role change, extended leave, an award update and a cross-functional report. Look for manual steps, duplicated data and unclear ownership.

Does batch processing mean a platform is not unified?

Not necessarily. Establish which updates are immediate, which are scheduled and whether any delay affects pay, compliance, access or reporting.

What should I ask an HR and payroll vendor before signing?

Ask where the employee record sits, who owns cross-functional issues and how much custom work connects standard processes. Then ask to see the five tests run live.