Consider a hypothetical: a payroll director at a specialty logistics company can tell you exactly when the model stopped working. The company had grown from a single warehouse operation into four legal entities across eleven states, the result of two acquisitions in under three years. Payroll still ran the way it had when the business was a fraction of its current size: one payroll administrator, a patchwork of state tax registrations added as each entity came online, and a benefits program that had never been rebuilt to match the new entity structure. Nobody had made a bad decision along the way. The operating model simply hadn't been revisited since the business looked completely different.
This is where that gap gets expensive. Once a company is running payroll across more than one legal entity and more than a handful of states, the payroll operating model question, who actually does the work of processing, filing, and administering payroll, stops being a background decision and becomes a live one.
Asure has published a pillar guide, Six Payroll Operating Model Frameworks for Growth-Stage B2B Companies, covering all six frameworks companies use to make that call. This piece goes deep on the two that matter most for companies operating across multiple entities and states: the Payroll Compliance Risk Scoring Rubric and the PEO vs. Payroll Provider Evaluation Scorecard.
The compliance math changes once entities and states start multiplying
The Payroll Compliance Risk Scoring Rubric weighs five factors: state count, worker classification, filing history, benefits integration, and payroll frequency. None of those factors is unique to companies of any particular size. What's unique is what happens to each one once a company is operating through more than one legal entity.
State count doesn't add up cleanly across entities, it compounds. Each entity can carry its own state withholding accounts, unemployment insurance registrations, and local tax obligations, and a single new location or acquired subsidiary can quietly add several jurisdictions to the total exposure at once.
Worker classification gets harder to keep consistent when a company is running hourly field crews in one entity, salaried professional staff in another, and a mix of contractors inherited from an acquisition in a third. The rubric treats classification as its own risk factor for exactly this reason: a single inconsistent judgment call, repeated across entities, becomes a pattern rather than an isolated error.
Filing history gets murkier through mergers and acquisitions, when entities carry different tax ID histories, different prior providers, and different notice trails that don't automatically reconcile into one record. Benefits integration follows a similar pattern: entities that joined the company at different points often carry different benefits programs, and unifying them without breaking compliance in the process takes real coordination. And payroll frequency, whether an entity runs weekly, biweekly, or semimonthly, often reflects whatever system that entity inherited rather than a deliberate choice, which adds operational friction every time entities need to be reported together.
None of this means a multi-entity company is doing anything wrong. It means the same five factors that matter for any employer carry more weight once they're multiplied across entities, which is exactly the read the Risk Scoring Rubric is built to surface.
Why the PEO conversation tends to show up right about here
Elevated compliance exposure is also, not coincidentally, when a PEO pitch becomes common. A broker or PEO sees a company juggling multiple entities and states and offers to take the operational and compliance burden off the table entirely. For HR leaders trying to add compliance expertise without increasing headcount, and payroll leaders trying to avoid missed filings and penalties, that pitch can sound like relief.
This is where the PEO vs. Payroll Provider Evaluation Scorecard is the right lens, because it forces the decision to be evaluated on its own terms rather than accepted on the strength of the pitch. Its factors are co-employment risk, benefits leverage, HR infrastructure needs, cost per employee, compliance accountability, and exit flexibility.
Co-employment risk is usually the sharpest one. Owners and executives at this stage often describe the fear as PEO lock-in or co-employment restrictions, and it's a real structural tradeoff: a PEO becomes a co-employer of record, which changes who is legally accountable for the workforce.
Benefits leverage is worth reassessing at this size specifically, because a PEO's pitch often leans on group purchasing power, and that advantage shrinks as a company's own headcount grows large enough to negotiate benefits directly. HR infrastructure needs come down to an honest read of internal capacity: does the team need help executing the work, or help being legally relieved of it, because those are different problems with different solutions. Cost per employee matters because PEO fees typically scale per head, which can outpace the cost of the actual administrative work as headcount grows. Compliance accountability asks a blunt question: when a state agency sends a notice, who is actually on the hook to respond. And exit flexibility matters most for companies that have just been through, or might go through again, a restructuring, merger, or acquisition, since unwinding a PEO relationship cleanly can be its own project.
The scorecard doesn't hand every company the same answer. What it does is force a company at this size to score its own situation against these six factors, rather than defaulting into whichever model got pitched first.
Two paths, one portfolio
Whichever way that scorecard leans, keeping the operational work internal or handing it off, doesn't have to mean choosing an entirely different kind of vendor relationship for each option.
For companies that want to keep the work internal but need it consolidated across entities, AsureCentral is built for that. It gives multi-entity, multi-state employers one connected system of record for payroll, HR, tax, benefits, and time, with role-based access so a payroll or HR team can see across entities without losing entity-level control.
For companies whose scorecard points toward outsourcing the operational load, but whose co-employment risk factor rules out a PEO, AsureWorks is built for that scenario specifically. AsureWorks lets a company hand off payroll processing and day-to-day HR administration to Asure specialists while remaining the employer of record, with no co-employment. That is a direct answer to the co-employment risk factor in the scorecard: it separates who performs the operational work from who is legally the employer, which a PEO structure does not do. Companies choosing AsureWorks also keep their existing benefits broker, retirement provider, and other workforce partners, rather than being moved into a bundled PEO program.
AsureCentral and AsureWorks run on the same underlying platform, so a company can move between running payroll internally and having Asure specialists manage day-to-day operations without switching systems as its entity structure or internal staffing changes.
Back to the hypothetical logistics company
Continuing the illustration, the payroll director at the logistics company eventually ran both frameworks. Mapping the four entities against the Risk Scoring Rubric's factors showed the exposure was concentrated in worker classification and benefits integration, both legacies of the two acquisitions that had never been fully reconciled. Around the same time, a PEO broker was circling for a renewal pitch on the company's smallest entity, which is what forced the second question.
Running the PEO vs. Payroll Provider Evaluation Scorecard made the decision more concrete than the sales conversation had. Co-employment risk and exit flexibility were the deciding factors: the company had just spent two years integrating an acquisition and had no appetite to hand employer-of-record status to a third party right after, especially with another acquisition under discussion. Benefits leverage was also no longer a clear PEO advantage at this size. What the company needed was help executing the operational work across four entities, not relief from being the employer.
They moved to AsureWorks, keeping their employer-of-record status while Asure specialists ran day-to-day execution, and consolidated their internal reporting onto AsureCentral as one system of record across all four entities. The compliance exposure the rubric had flagged didn't disappear overnight, but it stopped compounding silently, because someone was accountable for tracking it entity by entity.
Questions worth asking before the decision gets made for you
A few questions translate both frameworks into something a payroll, HR, or finance leader can actually use in a meeting:
Across your entities, how many separate state withholding and unemployment accounts are you maintaining today, and would a new location or acquisition add several more before anyone notices?
Do worker classifications and pay frequencies differ across entities, and would a consolidated system catch an inconsistency before a state agency does?
If a PEO pitch is already on the table, who becomes the legal employer, what happens to your current benefits broker and retirement plan, and what does it cost to exit in two years if the company's structure changes again?
The decision is worth making on purpose
Companies running payroll across multiple entities and states rarely get here through one bad choice. They get here because the operating model that fit when the business was smaller and simpler kept running long past the point where it still fit. The Risk Scoring Rubric and PEO vs. Payroll Provider Evaluation Scorecard exist to make that gap visible before an agency notice or a broker pitch makes it visible for you.
Whether the answer is running payroll internally with the connected view AsureCentral gives across every entity, or handing routine execution to Asure specialists through AsureWorks while your company stays the employer of record, the decision belongs to your team, made deliberately, rather than to whichever pitch reached your inbox first. Read the full framework set in the Six Payroll Operating Model Frameworks guide from Asure, and talk to Asure about whether AsureCentral or AsureWorks fits your entity structure today.
