Last updated: April 2026
The Common Paymaster Rule: How Related Companies Stop Double-Paying Payroll Taxes on Shared Workers
A common paymaster stops two related companies from double-paying payroll taxes on shared workers.
Two corporations share one worker. Each runs a separate paycheck. Each withholds 6.2% for OASDI plus 1.45% for Medicare tax up to the $176,100 OASDI wage base in 2025. That employee ends up filing a Schedule 3 refund claim, while both companies quietly pay the full employer match across that bottom slice of combined wages.
That doubles what employers owe on FICA at the high end. Knowing how much payroll tax you actually owe on shared employees starts with the election under IRC §3121(s). Both corporations stack their employer tax obligations under the same OASDI ceiling unless the election is filed. Get it right, and only one entity reports the wages. Miss the election, and both corporations hit the cap twice.
Why Two Related Companies Overpay Payroll Taxes on Concurrent Wages
Picture a founder who owns two S corporations. A tech company and a consulting LLC taxed as an S-corp. Same chief executive.
The tech side pays her $120,000. Her consulting side pays her $90,000. On both W-2s together, combined OASDI wages hit $210,000.
OASDI withholding stops at $176,100 in 2025. She overpaid by roughly $2,100 between the two employers. That piece a worker recovers by claiming excess Social Security tax withheld on Schedule 3 of Form 1040. What neither entity recovers is its own employer match. Each paid 6.2% up to the ceiling on its own paychecks, which means the two corporations collectively matched FICA on $352,200 of wages.
The real worker was one person earning $210,000.
Medicare tax is not the issue here. Medicare tax has no income cap, so paying it on concurrent employment wages is correct. The 0.9% Additional Medicare Tax above $200,000 sits on the employee, not the employer, so this election leaves that calculation alone. The OASDI portion is the piece that breaks. Multiply across a dozen shared executives or technicians, and unrecovered employer FICA hits six figures fast.
The tradeoff is administrative. One entity runs all the concurrent employment FICA through a single paymaster account. Your other entity loses direct control of its own payroll records for that shared worker. For family-owned groups that already bundle accounting, that is a small cost.
Payroll tax deadlines do not shift because of this election. Quarterly federal return filings stay on their normal cadence, and W-2 issuance still follows a January 31 delivery rule to each employee. The election changes who reports the wages, not when.
How Common Paymaster Actually Works in Practice
IRC §3121(s) treats two or more related corporations as a single employer for FICA purposes when one of them acts as a common paymaster. All wages paid to a concurrent employee run through that single corporation. Only that corporation files Form 941 for the concurrent employee and issues the W-2. Each other related entity reimburses the paymaster for its allocated share.
The reimbursement is where the math gets clean.
Your paymaster pays the employee, withholds once, and issues one W-2 with combined wages. Withholding cuts off at the $176,100 OASDI ceiling one time. Each related corporation funds its portion of gross wages plus its allocable share of employer FICA, but the cap never resets per entity. That entity runs federal income tax withholding off a single W-4. Doing so prevents the under-withholding that happens when each entity treats that person as a separate payroll relationship for withholding purposes.
Before the election, two entities were each paying 6.2% on wages up to the cap. After the election, one entity pays 6.2% on the capped wages one time. IRS Publication 15-A walks through the bookkeeping for this arrangement and the federal income tax withholding mechanics that go with it. You begin operating that way, document the relationship, and keep the allocation records on file.
The tradeoff is concentration of risk. The paymaster carries every Form 941 line for the shared worker, which means every late deposit, classification error, or unfunded reimbursement now creates one large exposure rather than two smaller ones. Your paymaster must also be a bona fide employer of that employee.
You cannot designate a shell entity with no employment relationship. Common paymaster also requires concurrent employment, not sequential. An executive who moves from Company A to Company B mid-year is not sharing employment. This rule only helps when both corporations employ the worker during the same calendar quarter.
Which Related Corporations Qualify Under IRC §3121(s)
Qualification is the gate. IRC §3121(s) defines related corporations narrowly enough that the rule avoids sweeping in unrelated vendors, but broadly enough to cover almost every real holding company structure.
Two corporations qualify if they meet one of three tests. They share 50% or more common ownership. Or they share 30% or more ownership combined with concurrent employment of the same workers. Or they sit in a parent-subsidiary chain under IRC §1563.
Most owner-operated corporate groups clear the first test without thinking about it. A founder who owns 100% of Entity A and 100% of Entity B is obviously the 50%-plus common owner. A founder plus spouse owning jointly across multiple S-corps usually clears it too. The controlled-group rules of §1563 are where you double-check before writing your documentation file.
Partnerships do not qualify. The statute specifies corporations. An LLC taxed as a corporation counts, which includes every LLC that filed Form 8832 to elect C-corp treatment and every LLC that elected S-corp treatment with Form 2553. An LLC taxed as a disregarded entity or a default partnership cannot be a common paymaster. The qualifying structure also dictates how each entity satisfies its remaining employer tax obligations on the shared worker.
Sole proprietorships are also out.
Unless your second business is a corporation or a corporate-taxed LLC, this election is not available even though one owner runs both operations. The federal workaround for sole proprietors is different, and it runs through the FICA refund for overpaid Social Security tax process on the worker's 1040 rather than employer-side netting. The tradeoff for that route is that the worker recovers the employee share, but neither business owner gets back the duplicated employer payroll taxes.
Partnerships that own corporations create an edge case worth flagging. If a partnership holds 100% of two S-corps, the corporations below pass the related-corporation test because they meet the ownership threshold, even though the partnership layer above is not itself a qualifying entity. The statute focuses on whether the corporations qualify, not on whether every upstream owner is a corporation. Your holding-company structure does not have to be pristine for the downstream election to work.
The Common Paymaster Mistake Most Multi-Entity Owners Make
Here is the mistake.
A founder runs two entities, both pay one person, neither company coordinates with the other. Your payroll provider processes each paycheck as if it were a separate employer relationship. OASDI gets withheld twice on concurrent employment wages up to the cap.
Year-end comes, the worker files for a refund of the excess, and both entities quietly pay the employer match twice across that bottom slice while claiming no credit. The combined federal income tax withholding can also come up short when each entity treats that employee as if those wages were the only ones. Each W-4 calibrates against its own paycheck rather than the combined annual figure.
A $220,000 shared executive earning equal splits across two S-corps leaves roughly $10,800 of employer-match FICA uncollected every year. Over five years that compounds to $54,000 of pure waste. Both companies wrote the checks.
Treasury kept the money. Your worker might be owed a refund, but the employer portion is never coming back unless you file Form 941-X within the statute of limitations. A late or amended deposit during cleanup can also draw a payroll tax penalty under §6651, so the cure has its own cost if you mishandle the timing of the corrected payroll taxes.
The second layer of the same mistake is believing common paymaster requires a complex legal restructure. Not true. Section 3121(s) requires that the corporations be related under common ownership or a defined family relationship.
For most multi-entity founders, the relationship already exists on the day Entity B is formed. An election is a documentation step, not a merger. The tradeoff is the small administrative lift of running intercompany allocations, which is trivial compared to the FICA overpayment it stops.
A third variant: electing the arrangement, then failing to document it. An IRS examiner on audit will ask for allocation schedules, intercompany reimbursement records, and a payroll ledger showing which entity funded which wages. Without that file, any paymaster defense collapses, both corporations get hit as separate employers retroactively, and a payroll tax penalty for the unpaid balance can stack on top of the recovered tax itself.
The IRS wrote this rule to stop double-billing. Use it.
Form 941 Reporting When One Company Pays All the Wages
On Form 941, your paymaster reports 100% of the wages paid to each concurrent employee. Related corporations report zero wages for that worker. Allocation of the underlying expense happens in each entity's ledger, not within Form 941 itself. Each entity's general ledger shows its portion as a reimbursement to the paymaster, typically through an intercompany payable account. The paymaster's Form 941 lines for federal income tax withholding, Social Security, and Medicare tax all carry the combined number for the shared worker.
Schedule R of Form 941 is worth knowing about even though it never applies here. Schedule R is used by §3504 agents and Certified Professional Employer Organizations, not by common paymasters under §3121(s). A CPEO is a different IRS status that requires formal application on Form 14737 and annual surety bonding. This paymaster election does not require any of that.
At year end, only the paymaster issues a W-2 to the shared employee. Related entities issue no W-2 for that worker, even though they economically funded a portion of the wages. Your W-3 reflects the paymaster as the employer of record. If the worker also has non-shared wages from only one of the entities, that piece stays on that entity's W-2 as a separate reporting relationship.
The tradeoff sits in liability concentration. Federal unemployment is where a small drawback appears. This election covers FICA under §3121(s) and FUTA under §3306(p) for related corporations, so federal unemployment plays nicely.
But every late deposit, missed Form 941, or allocation error now lands on one EIN instead of being diluted across two. A single payroll tax penalty against your paymaster can be larger in absolute dollars than two smaller penalties would have been against each entity. State unemployment is a different story, which the next section covers.
Why States Almost Always Ignore the Federal §3121(s) Election
State unemployment insurance does not care what the IRS says.
The tradeoff at the state level is bigger than the one at the federal level. Most states run their own taxable ceiling and their own experience rating. The federal election under §3121(s) applies to OASDI, Medicare tax, and FUTA. It does not extend to SUI or SUTA in the overwhelming majority of states.
That means each related corporation pays SUTA on the shared worker independently, up to each state's separate ceiling. A worker earning $220,000 split across two entities in the same state may trigger two separate SUTA wage-base applications. Some states offer a successor-employer or common-ownership transfer that mirrors the federal rule, but you have to file state-level paperwork for each one that does.
California, New York, and Texas handle this differently. California's EDD treats concurrent employment as separate employer relationships for UI purposes. New York follows a similar pattern. Texas allows a limited form of common-ownership wage-base transfer between related entities if the state paperwork is filed before the quarter ends.
New Jersey, Pennsylvania, and Washington add their own wrinkles. New Jersey's UI taxable ceiling resets at each related employer because the state treats each EIN independently. Pennsylvania allows a partial experience-rating transfer when a shared employee moves between affiliated entities. Washington runs a case-by-case continuity-of-business review before granting a transfer.
The cost shows up on your annual SUI reconciliation. Multiply a shared executive's state taxable ceiling by two entities and the tax hits quickly for first-quarter wages. A business running concurrent employment across five states will have five different answers on whether the federal election helps with state unemployment.
The Dollar Math Across a Three-Year Recovery Window
Run the number on your own group before you file anything.
A multi-entity holding company with three shared executives at $200,000 each, split evenly across two S-corps, will have paid employer FICA on $352,200 per person instead of $176,100. That works out to roughly $10,900 of unrecovered employer match per shared worker per year. Multiply by three shared executives and the group is leaving $32,700 uncollected every year.
Over the open quarters that the statute of limitations allows a Form 941-X claim, the recovery pool for one year of back-quarters hits $32,700. Two full years of open quarters pushes the claim past $65,000. Three full years and your entity is filing for roughly $98,000. That is before counting the interest the IRS owes on valid overpayments under §6611.
Practical math runs differently for solo owner-operators.
A worker earning $175,000 out of one entity and nothing out of the other has no doubling problem. The cap is never reached twice on one person. Your arrangement helps when both corporations employ one worker during a single quarter AND combined wages cross the annual OASDI ceiling. Below the cap, there is no double-payment to fix. The tradeoff for filing anyway is professional fees and audit exposure on a claim that recovers nothing.
That is the single biggest reason this election gets overlooked. Advisors look at one entity's payroll, see wages well under $176,100, and conclude the rule does not apply. But when you combine paychecks to one worker, combined totals are what counts. A $150,000 salary at Entity A plus a $60,000 salary at Entity B triggers a $34,000 overpayment band above the cap. The administrative lift of running reimbursement accounting between entities is small compared to $98,000 of recoverable employer FICA.
Your Next Steps Before the Next Payroll Run
Start with ownership documentation.
Pull your operating agreements, shareholder registers, and Form 2553 filings. Confirm the entities meet the §3121(s) relationship test. That file is what an IRS examiner asks for on audit, so having it ready before you elect saves an argument later. Map out each entity's full set of employer tax obligations on the shared worker so the allocation worksheet later reflects all four pieces: OASDI, Medicare tax, FUTA, and federal income tax withholding.
Decide which entity serves as the paymaster. The simplest answer is whichever one already runs the most complex payroll. If one corporation has 40 employees and the other has three, the 40-employee entity is your paymaster. Run concurrent employee wages through it going forward, and have each related entity reimburse quarterly via intercompany transfer.
Your payroll software will not elect common paymaster for you.
Gusto, Rippling, and OnPay can handle multi-entity payroll, but none of them automatically configure the arrangement. A payroll admin has to tell the software that Entity B's workers will be run through Entity A's payroll account with intercompany cost allocation. Ask your provider how multi-EIN support works before committing, and confirm the system can run a single W-4 for federal income tax withholding rather than splitting the worker across two profiles.
File a protective Form 941-X for any open quarters where you can still recover the double-paid employer FICA. The statute of limitations on Form 941-X corrections is three years from the original filing, so wages paid in the prior three open quarters are usually recoverable. If you run a multi-entity group and have never elected the arrangement, there is almost certainly money to claim, and waiting another quarter only forfeits another tranche of recoverable payroll taxes.
Review your Form 941 reporting. Scan the broader payroll tax hub for related employer tax obligations you may be missing, and check whether a PEO for small business consolidation fits better. File the election documentation this quarter to head off any future payroll tax penalty for amending late.
Frequently asked questions
Does common paymaster apply to sole proprietors?
No. The statute names corporations, which includes LLCs taxed as C-corps or S-corps but excludes sole proprietorships and default-partnership LLCs. A sole proprietor who runs a second operation cannot use this election, although the worker still claims excess Social Security tax on Schedule 3 when wages from two jobs exceed the annual wage base.
Is Form 941-X the only way to recover double-paid FICA from prior quarters?
Yes for the employer side. Workers can recover their own overwithheld Social Security on Schedule 3 of Form 1040 or via Form 843, but employer-side FICA credits only flow through Form 941-X and only within the three-year statute of limitations from the original Form 941 filing date.
Does the common paymaster election affect state unemployment wages?
Almost never. The §3121(s) rule covers federal FICA and FUTA, not state SUI or SUTA. Most states treat concurrent employment across related entities as separate employer relationships for state unemployment purposes, which means each entity pays SUTA up to the state wage base unless the state has a specific successor-employer or common-ownership statute.
Can an LLC act as a common paymaster?
Only if the LLC has elected corporate tax treatment. An LLC that filed Form 8832 for C-corp treatment, or Form 2553 for S-corp treatment, qualifies. A default-partnership LLC or a single-member disregarded LLC does not, because IRC §3121(s) applies to corporations and corporate-taxed entities.
This is not legal or financial advice. Consult a qualified professional for your specific situation.