A common paymaster arrangement lets related companies treat a single employer for FICA and FUTA wage base purposes, so an employee working for two or more related entities has payroll taxes capped once instead of twice. The controlling authorities are IRC §3121(s), §3306(p), and Treas. Reg. §31.3121(s)-1-1). The arrangement only holds up if your group meets one of four relatedness tests and can prove concurrent employment. State unemployment tax agencies often ignore the federal rule entirely, so treat that piece as a separate compliance project.
TL;DR:
- The common paymaster arrangement only benefits related groups that meet at least one of four specific relatedness tests during a quarter, locking in eligibility regardless of later changes.
- Real disbursement, genuine concurrent employment, and proper documentation are critical to prevent IRS invalidation and joint liability for unpaid taxes.
- State unemployment agencies often do not recognize federal common paymaster status, requiring separate applications and compliance efforts per state.
- The primary tax savings stem from capping FICA and FUTA contributions on each employee once their wages hit the annual wage base, especially beneficial for high-wage earners in multiple entities.
- Poor recordkeeping and unauthorized retroactive claims are the main audit triggers, making robust documentation of employment, ownership, and reimbursements essential.
Table of Contents
- How the Common Paymaster Rules Work
- Who Qualifies: The Four Relatedness Tests
- Setting Up a Compliant Paymaster Arrangement
- Filing, Withholding, and Employer Responsibilities
- State Unemployment Tax Traps for Multi-Entity Groups
- When Common Paymaster Rules Actually Save Money
- Common Mistakes That Trigger an Audit
- Why Documentation Matters More Than the Tax Code Here
- How Thetaxrefinery Helps Multi-Entity Owners Get This Right
- Sources
- FAQ
How the Common Paymaster Rules Work
The IRS common paymaster rules treat qualifying related entities as a single employer for FICA and FUTA wage base purposes only, not for income tax withholding or state unemployment tax. One entity, designated the paymaster, disburses wages to employees who work concurrently for two or more related companies. Once that employee's wages hit the Social Security wage base, no other related entity has to restart the count.
Disbursement has to be real, not nominal. The IRS accepts a combined paycheck, a common bank account the paymaster draws from, or paychecks physically issued by the paymaster entity. Concurrent employment means the employee performs substantial services for more than one entity in the group during the same period, not a title on paper.
- The paymaster must actually pay the wages, not just record them.
- Employees need genuine job duties at each entity, backed by real work product or supervision.
- If the paymaster fails to remit withheld taxes, every entity in the group faces joint and several liability.
Who Qualifies: The Four Relatedness Tests
Treas. Reg. §31.3121(s)-1 sets four tests, and a group only needs to satisfy one during any point in the calendar quarter for that entire quarter's wages to qualify.
- Ownership test. A common owner, or group of five or fewer people, owns at least 50 percent of each related entity. A husband and wife who each hold controlling interests in an HVAC company and a separate plumbing LLC typically clear this bar.
- Board or membership overlap test. At least a significant share of one entity's officers also serve as officers of the other, satisfied in reverse if that ratio runs the other direction.
- 50 percent common officers test. At least half of the officers of one entity also hold officer positions at the related entity, common in closely held groups where one person wears multiple hats.
- 30 percent concurrent employees test. At least 30 percent of one entity's employees also work concurrently for the related entity, which fits staffing-heavy operations like commercial cleaning franchises running under separate legal entities.
Meeting any single test at any moment during the quarter locks in eligibility for that whole quarter, even if the relationship later changes.
Setting Up a Compliant Paymaster Arrangement
Documentation is where most common paymaster arrangements succeed or fail on exam. Build the file before you need it, not after an IRS letter arrives.
- Draft a board resolution or formal designation naming the paymaster entity and the effective date.
- Put an intercompany reimbursement agreement in writing, specifying dollar amounts and how each entity records the expense.
- Keep concurrent employment records: timekeeping data, job descriptions, and signed service agreements for every dual-duty employee.
- Maintain payroll allocation records showing how wages, taxes, and W-2 issuance tie back to actual hours worked at each entity.
- Set a retention schedule and confirm your payroll provider can export allocation reports on demand.
Pro Tip: Ask your payroll vendor for a sample allocation report before you finalize the arrangement. If they can't produce one cleanly, that's a sign the mechanics will break down at tax season, not a sign to skip the paperwork.
Examiners reviewing a common paymaster typically request the reimbursement agreement, time records, and payroll allocation detail first. Assemble those into one file per quarter so you're never scrambling.
Filing, Withholding, and Employer Responsibilities
The paymaster entity carries the compliance burden for wages it disburses. That means filing Form 941 quarterly and Form 940 annually, and issuing W-2s under its own employer identification number for the wages it paid.
- The paymaster deposits withheld employee FICA and its own employer FICA and FUTA shares on the standard federal deposit schedule.
- Reimbursement accounting between entities should record the tax expense allocation clearly, matching actual payroll costs incurred.
- Every related entity in the group remains jointly and severally liable if the paymaster fails to remit, so this isn't a way to shift risk away from the other entities.
- If a third-party service provider handles filings, confirm whether they're acting under a Form 2678 agent designation, which is a separate mechanism from common paymaster status and carries its own IRS approval process.
State Unemployment Tax Traps for Multi-Entity Groups
Federal common paymaster status does not automatically extend to state unemployment insurance. Some states accept the federal designation, some require a separate application, and at least one state disallows it outright.
Pennsylvania prohibits common paymaster reporting for UC purposes and can penalize employers who misreport wages that way. Florida requires a pre-approval application, and approval isn't retroactive, so status typically starts the quarter after the state signs off.
- Check each state's labor agency guidance before assuming federal treatment carries over.
- Apply for state-level approval where required, well ahead of the quarter you want it to take effect.
- Misreporting can distort your unemployment experience rating and trigger separate penalty assessments.
When Common Paymaster Rules Actually Save Money
The core benefit is capping FICA and FUTA exposure once per employee across the group, instead of letting each entity independently restart the wage base for the same person.
- Separate-entity scenario: an employee earning $90,000 from Company A and $60,000 from Company B, both above the annual Social Security wage base, means both entities pay employer FICA on their full share, and the employee's Social Security withholding gets overpaid across two employers.
- Common paymaster scenario: the same $150,000 in combined wages gets tracked against one wage base, so FICA stops accruing once the cap is hit, and the employee reclaims any overwithholding through one W-2 instead of two.
- Savings scale with headcount: groups with several employees earning above the wage base across multiple related entities see the most meaningful reduction; a single dual-duty employee earning modest wages at each entity won't move the needle much.
The tradeoff is administrative load. Recordkeeping, state filings, and payroll coordination costs can eat into savings for smaller groups, which is why modeling the numbers before implementation matters more than the concept itself.
Common Mistakes That Trigger an Audit
Examiners unwind common paymaster arrangements more often for documentation failures than for genuine ineligibility.
- Payrolling an employee under the arrangement without contemporaneous proof of actual work performed at each entity.
- Attempting to apply common paymaster treatment retroactively, particularly at the state level where retroactive approval typically isn't available.
- Missing or informal corporate authorization, with no signed reimbursement agreement between entities.
- Confusing a common paymaster role with a professional employer organization or staffing arrangement, which carries different liability protections entirely.
- Inconsistent accounting between entities, or records that don't survive the retention window an IRS examiner would expect to see.
Pro Tip: If you can't produce a signed board resolution and matching time records within a day of an examiner's request, treat that as your real audit risk, not the tax savings math.
Why Documentation Matters More Than the Tax Code Here
Most owners come to a common paymaster arrangement chasing the wage base savings and underestimate how much the IRS cares about proof of substantive concurrent employment. The regulation itself is straightforward. What trips groups up is treating the paperwork as an afterthought instead of the foundation.
This structure is recommended only when there is real, ongoing dual-entity work, not a payroll convenience dressed up as a tax strategy. When the documentation is thin, the arrangement is often not worth the audit exposure it creates, even if the math looks appealing on paper.
— Melissa
How Thetaxrefinery Helps Multi-Entity Owners Get This Right
Tax advisors can build the documentation infrastructure most groups skip: board resolutions, intercompany reimbursement agreements, and payroll allocation files that hold up if an examiner ever asks.
If you're running two or more related entities and think a common paymaster could reduce your payroll tax exposure, the real work is proving relatedness and concurrent employment before you ever touch a wage base calculation. A multi-entity tax structuring service can walk through your ownership chart, officer overlap, and payroll mechanics to confirm eligibility, then build the governance file an auditor would actually want to see. For groups worried about state unemployment exposure on top of federal treatment, an engagement may cover the state-by-state check most owners never think to run. Start with a tax strategy consultation to see whether the arrangement fits your specific entity structure before you implement anything.
Sources
Primary references: the IRS common paymaster page, 26 CFR §31.3121(s)-1, a sample IRS letter ruling, and Pennsylvania's UC guidance on state divergence. For ownership documentation methods, see this beneficial ownership verification guide.
- Common paymaster | Internal Revenue Service
- IRS letter ruling (example) on common paymaster provisions
- Pa
FAQ
What are the IRS rules for a common paymaster?
The IRS requires related entities to meet one of four relatedness tests under Treas. Reg. §31.3121(s)-1 and to show genuine concurrent employment before treating wages under a single FICA and FUTA wage base.
Can an LLC be a common paymaster?
Yes, an LLC can serve as the paymaster if it's part of the related group, meets one of the relatedness tests, and actually disburses the remuneration to employees working concurrently for multiple entities.
Do employers have to use a common paymaster to pay employees?
No, using a common paymaster is elective. Related groups choose it specifically to avoid duplicating the FICA and FUTA wage base when the same employee earns wages from more than one related entity.
What are common payroll tax mistakes with multi-entity structures?
The most frequent errors include weak documentation of concurrent employment, attempting retroactive common paymaster treatment, skipping required state unemployment applications, and confusing paymaster status with a staffing or PEO arrangement. Thetaxrefinery's audit trigger guide covers related recordkeeping gaps that draw IRS attention.