Multi-Company Payroll Software: What One Account Covers
Updated: 6 hours ago
A payroll salesperson demonstrates a company switcher with three business names. Your administrator can move between them without signing out. Before treating that as a multi-company solution, ask what happens after the switch: which employers the subscription covers, which tasks remain separate and what the finance team can actually combine.
Multi-company payroll software can give a shared team access to several employers while preserving the records and processing each employer needs. The useful buying question is how much of your required work the quoted package supports. One login, one subscription, one payroll approval and one consolidated report are different capabilities. An offer may provide some without providing all.
Use this guide to compare the account structure, authorized work, reports and billable units. The Multi-Company Payroll Purchase Scorecard below turns a demonstration into a record of demonstrated capability, priced workarounds and unresolved conditions. The buying situations and prices are fictional; they are not vendor test results or current market quotes.
An employer list and a few concrete workflow requirements can make a software conversation more useful. SelectSoftware Reviews offers a free advisor consultation about HR and payroll software. Bring the companies you need covered, the tasks you want to share and the reporting you need, then ask each proposed provider to confirm its package.
Contents
Unpack the promise of one account
Separate four layers during the first sales conversation. Login access determines how an administrator signs in and moves between authorized companies. Company context determines which employer's records, settings and pending work are on screen. Licensed processing determines the companies and services the purchased subscription permits. Combined reporting determines which data can be viewed together and whether the original company detail remains available.
These layers can support different purchasing arrangements. A shared login may lead to separately subscribed company profiles. A broader platform may offer several employers within a group agreement. An accountant's client dashboard may give useful oversight while each client still has a separate service relationship. Ask the seller to identify the offered arrangement rather than treating the word account as a specification.
For a concrete example, Gusto's administrator instructions describe one email address accessing multiple companies and adding a separate company profile through that login. The documented setup also includes choosing a package and acknowledging billing. Those instructions establish a convenient access route. They do not, by themselves, establish one group price or a consolidated payroll report.
A different source illustrates why the edition matters. Intuit's payroll-subscription instructions say that Intuit QuickBooks Workforce allows one federal EIN per payroll subscription, while the same article describes different EIN limits for named QuickBooks Desktop Payroll services. Ask about the exact service and edition being quoted. A statement about one edition should not be carried into another.
Record the product name, edition, included employers and separately charged services beside the proposal. Where documentation and a sales answer differ, obtain a written resolution that identifies the applicable contract or service schedule. A demonstration in a seller's broadest environment is not confirmation that those features are included in your purchase.
One account can describe access, processing rights or a reporting view. Confirm each layer separately in the quoted package.
Give the seller an employer list, not an office count
Build the list from the business's approved employer and tax-account records. For each employer, identify the internal reference, payroll population, jurisdictions in scope, current provider company identifier and the person who can approve account setup. Share references through an appropriate secure process; a comparison worksheet does not need complete EINs, bank details or employee identifiers.
Keep offices, departments, brands and ledger segments in a separate column. They can affect reporting and access requirements without representing additional employers. The IRS instructions for Form SS-4 say not to apply for another EIN merely because an existing business is adding another place of business. Have the responsible tax adviser resolve the employer structure before asking software to implement it.
For example, a business with four storefronts under one accepted employer arrangement may need location reporting rather than four payroll company subscriptions. A group with three employing companies may need three employer setups even if all staff work in one building. These are purchasing examples, not determinations of how a particular business should organize its employment or tax affairs.
Add known changes to the list: an employer expected to start next quarter, a company being sold or an existing operation leaving the service. Ask which changes require a new subscription, onboarding fee, agreement or implementation lead time. A package that fits today's company count can become a different purchase when the next employer is added.
Finish this step with a coverage statement the seller can answer: these named employers, these payroll services, these locations and these start dates. Leave uncertain employers visibly conditional. An unresolved legal-employer question should not disappear inside an implementation assumption.
Choose which work should be shared
List recurring tasks before choosing an architecture. Useful candidates include reviewing the status of each company, collecting approved inputs, preparing separate payrolls, coordinating approvals and producing a finance summary. For each task, say whether one person performs it across the group or whether a local owner must retain control.
A shared login with separate company processing can be a reasonable fit when the team wants consistent access but needs distinct schedules, settings and approvals. Its value depends on the number of company changes, repeated entries and exports the team will actually perform. Count those actions rather than describing every separate step as waste.
A platform with broader group functions deserves attention when the same team repeatedly combines data, administers access or coordinates many employer runs. Ask which functions operate across companies and which still require opening each company separately. A group dashboard showing overdue work is different from the ability to prepare or approve that work in a group action.
Consider a payroll manager responsible for three employers. The manager wants a single list of due payrolls but wants each local approver to authorize only their employer's preview. A product that shares the status list and preserves separate approvals could meet that need. A universal approval button would not necessarily improve it.
Also distinguish shared administration from sharing a sensitive change. Updating a person's mailing address, changing a bank destination and changing a pay rate have different consequences. Ask how the product identifies the affected employment records, which changes propagate and how the user confirms their scope. Do not accept automatic propagation as an advantage until the intended behavior is clear.
Write a short requirement for each shared task: who initiates it, which companies it affects, who reviews it and what record proves completion. That gives the demonstration a set of observable outcomes.
Give permissions a two-company demonstration
Use two test companies and at least two roles in the proposed edition. One role should have the central access the group needs. The other should have access to only one company or a defined set of tasks. Use demonstration data or appropriately protected samples rather than sending real payroll records to a sales environment.
Ask the seller to show what the restricted role can see and do in company lists, employee searches, reports, exports and administrative settings. Then ask it to attempt an action outside that role's scope. The useful evidence is the actual restriction and any recorded attempt, not a slide containing the word permissions.
Test the distinction between reading, changing, approving and releasing. A company manager may need to see a preview without changing bank instructions or administering other users. A central preparer may need all companies without holding final release authority. Record unsupported combinations as a workaround or a limitation requiring a decision.
Include access introduced indirectly. A report builder, integration credential or group administrator may have a different scope from the ordinary payroll screen. Ask who can widen that scope, how the change is recorded and who reviews it. If the seller cannot demonstrate an integration credential, request its documented scope and make verification an implementation condition.
Finally, add a new test company and show its default access behavior. Existing roles should receive the access your approved design intends. If someone must update every role manually, record that task and its owner. A demonstrated permission model still needs an operating process to keep it correct as the group changes.
Follow a payroll from preparation to company-specific evidence
Choose an ordinary payroll for each test employer. Give them different pay dates or approval owners if that reflects your business. Ask how the shared team finds the right run, identifies unresolved input and knows which version each approver is reviewing.
Follow the authorized release through the outputs you require. Request the employer identity, run reference, approved amounts, funding instructions and processing status for the relevant company. Ask which records can be exported and which remain available only inside the service. A screenshot of a group total cannot answer a question about one employer's payroll.
Funding is a separate part of the demonstration. Establish which party initiates each debit, which bank instruction it uses, which deadline applies and where a failed or changed instruction appears. If the group uses a central funding arrangement, have the responsible finance and tax reviewers approve that arrangement; the software demonstration should show how it records the approved setup.
Keep tax-service claims specific. Ask which employer accounts, returns, payments and correction services are included in the quote, what authorizations are needed and which responsibilities stay with your business. Request a sample employer-specific service record. A statement that the platform handles taxes is too broad to establish the service you are buying.
Also show an exception affecting only one company. Suppose two payrolls are ready while the third has an unresolved input. Can the team see the separate statuses and release only the authorized runs? If the required workflow depends on a manual reminder or a separate approval channel, include that work in the comparison.
Save the demonstration date, edition, scenario and evidence reference. Mark anything shown only in another edition as unproven for the current quote until the seller confirms availability and price.
Count people and employment records separately
The same person can have records associated with more than one employer. Ask how the product distinguishes a person's login or identity from each employer's employment and payroll history. One employee portal should not be interpreted as proof that all underlying records have been combined.
Bring a realistic example to the seller. A person works for Alder and Birch during the same period, under an arrangement your advisers have already approved. Show how the authorized users find each employment, apply the correct company settings and produce the required company-level output. Ask what the employee sees and how support staff avoid changing the wrong record.
For a transfer, distinguish ending one employment, starting another, moving a department and correcting an earlier assignment. Ask which event the software supports, what history follows, what remains with the former employer and how effective dates are recorded. Obtain the responsible tax review before accepting a proposed treatment of year-to-date wages or tax bases.
Common ownership and a shared payroll account do not establish common paymaster treatment. The IRS common paymaster guidance describes a specific arrangement involving related corporations and concurrent employment that can affect FICA and FUTA wage bases. Have a qualified tax reviewer determine applicability before configuring shared treatment. This guide does not determine eligibility.
Use separate counts for purchasing as well. A seller may price people, company-level employee records, active workers, payments or another defined unit. Ask whether a person appearing in two companies is charged once or twice, when the count is measured and how a person who leaves during the month is treated.
In this fictional group, 44 single-employer records plus eight records for four dual-employer people produce 52 company records. The group has 48 unique people. These are quote units, not a tax calculation.
Require a report that can be taken apart
Start with the finance question. Do you need a weekly status view, total group labor cost, employer-level liabilities, a journal export by ledger company or a report for a particular management team? Each request needs a defined population, period and measure.
Ask the seller to produce a combined report for the two test companies and then separate it into its source amounts. Match each company subtotal to the appropriate underlying report. Use a controlled difference, such as a payroll with a different pay date or a correction posted later, to see which date basis the report uses.
Do not compare unlike measures simply because they appear under a common heading. Gross wages, employer payroll cost, net pay and provider funding answer different questions. Ask for the field definitions, included components, adjustment treatment and whether the report is based on final, pending or voided payrolls.
Company identifiers must survive the export. A readable company name can be useful, but finance may also need a stable identifier for its ledger mapping. Check whether account codes, departments or cost centers have the same meaning in every company. A combined column labeled department can obscure different local coding schemes.
Inspect intercompany or allocation information separately from original payroll amounts. Ask how the proposed report prevents duplicate counting when a shared cost is reallocated. If a spreadsheet is needed to reconcile the result, preserve the calculation and assign an owner. Calling the output consolidated does not prove that the resulting total is suitable for your close.
For integrations, request an output sample or a documented field mapping. Confirm company identifiers, authorized scope, correction behavior and how an export can be reproduced. A connection to a named accounting product does not establish support for every company structure within it.
Take these requirements into a payroll software conversation
Give SelectSoftware Reviews your actual employer list, permission needs and company-level reporting requirements when discussing payroll systems. Ask prospective providers to demonstrate the account structure using more than one company.
Put the billable unit into the quote calculation
Normalize each offer to the same employers, services, workforce assumptions and period. Separate recurring charges from onboarding, implementation, conversion and exit charges. Ask about company minimums, inactive employers, off-cycle runs, year-end forms, amended filings, integrations and support levels relevant to your actual requirements.
The following example uses invented prices. It compares the same required service scope for three employers, with no additional fees or taxes assumed in the arithmetic. It is not a statement that real plans have equivalent features or that any provider offers these rates.
Alder has 22 company-level employee records, Birch has 18 and Cedar has 12. Four people have one record in both Alder and Birch; there are no other overlaps. The total is 52 records and 48 unique people.
Offer X: Three company fees at $100 a month produce $300. A charge of $6 for each of 52 company employee records adds $312. The recurring monthly total is $612. Twelve months cost $7,344, and setup at $300 per company adds $900. The first-year cash total is $8,244.
Offer Y: A $300 monthly group fee includes all three employers. A charge of $7 for each of 48 unique people adds $336. The recurring monthly total is $636. Twelve months cost $7,632, and a $1,200 setup charge produces a first-year cash total of $8,832.
Offer Y costs $24 more each month and $588 more in the first year under these assumptions. Comparing the employee rates alone would miss both the different counting units and the setup difference. Confirm the seller's definition before entering a headcount into its calculator.
Now record retained work separately. If Offer X requires four hours of monthly consolidation and Offer Y requires one, the claimed difference is three staff hours a month. Validate that estimate with your process and the demonstrated output. Those hours are not an invoice reduction, a proven performance result or cash savings unless the business actually avoids a cost.
If the offers cover different services, stop treating the price totals as an equivalent comparison. Obtain the missing service price or state the exclusion and its owner. A lower subtotal is useful only when the business understands what it must still buy or perform.
Price the next company and the last day of service
Ask the seller to describe adding a company after go-live. Establish the trigger for a new charge, onboarding lead time, required account authorizations, opening balances and who validates the first payroll. Ask whether the additional employer changes the group agreement, minimum commitment or access administration.
Then consider removing one employer while the others remain. Can its payroll stop independently? What happens to administrator access, employee records, reports, integrations and unpaid service charges? Request the contractual treatment of partial termination rather than relying only on the process for canceling the entire account.
Include records access in both scenarios. Identify the reports and underlying detail your organization needs to retain, the export format, who may retrieve them and the access period after service ends. Decide retention requirements by record type with the appropriate advisers. A vendor's access period is not your organization's record-retention policy.
A sale or acquisition introduces employer and reporting decisions beyond software setup. Obtain those decisions from the responsible specialists, then ask the seller how its system implements the approved dates and history. Do not let a convenient transfer function select the legal or tax treatment.
Make an exit sample part of the evaluation when the records are important to finance. Ask for a representative export containing the company identifier, period, run reference and necessary detail. Check that your team can read it without buying continued access to an unspecified service.
Copy the Multi-Company Payroll Purchase Scorecard
Complete one scorecard per offer using the same employer list and scenarios. Keep the blank master and a dated copy of the seller's responses. Use secure document references rather than employee data or complete account numbers.
For each required capability, use Demonstrated, Priced workaround or Unresolved. Demonstrated means the required result was shown in the quoted edition and supported by the purchase terms where relevant. A priced workaround needs an accepted owner, steps, cost and evidence. Unresolved means that the needed answer or proof is still missing.
Record a separate result for each required capability, repeating the Required work and proof group where needed.
This is a decision record, not a weighted vendor ranking. An unresolved required employer, prohibited access route or unsupported payroll treatment should hold the relevant buying decision. Several convenient features cannot average away a required failure.
Offer and employer coverage
Offer, edition and response date: ____.
Covered employer references and start dates: ____.
Locations or reporting units that are not additional employers: ____.
Subscription limits, additional-company price and evidence reference: ____.
Required work and proof
Required shared task and affected employers: ____.
Role, permitted actions and excluded companies: ____.
Demonstration scenario, result and evidence reference: ____.
Employer-level payroll, funding and filing-service outputs: ____.
Combined report, source subtotals and retained company identifiers: ____.
Dual-employer or transfer handling and approved treatment reference: ____.
Result: Demonstrated, Priced workaround or Unresolved: ____.
Quote and retained work
Billable unit, counting date and overlapping-person treatment: ____.
Recurring calculation and first-year one-time charges: ____.
Excluded service or manual task, owner and estimated workload: ____.
Required workaround, quoted cost and acceptance condition: ____.
Addition, exit and purchase decision
New-company setup, permission changes and lead time: ____.
Partial exit, readable exports and records-access terms: ____.
Unresolved requirement, decision owner and next evidence due: ____.
Purchase decision, conditions and approved comparison version: ____.
Keep the proof reference visibly separate from a salesperson's general answer. A promise to send an example later remains unresolved until the appropriate reviewer accepts the evidence. Review revised offers against the same scorecard so a cheaper edition does not silently remove a required function.
A completed entry for one requirement
Required result: Finance can export one group report and reconcile it to employer-level labor costs.
Observed result: The seller shows a combined screen, but its sample export omits company identifiers.
Current status: Unresolved; the displayed total does not prove a usable employer-level export.
Next evidence and owner: Seller supplies a quoted-edition sample with company identifiers; finance matches both employer subtotals before accepting the requirement.
Decision effect: Hold the reporting requirement open. Price a manual alternative only if finance is willing and able to own it.
The same offer could still be acceptable for a team that does not need consolidated exports. The scorecard makes the difference visible without pretending the product has passed a requirement it has not demonstrated.
Multi-company account questions
Can one payroll account cover several EINs?
It depends on the specific subscription and service. Confirm each named employer, supported services, limits and charges in the offer. Shared sign-in access alone is insufficient evidence. Preserve the written coverage answer with the final agreement so implementation begins from the same understanding as the purchase.
Do we need one platform for every company?
A common platform can simplify some tasks, but the decision depends on supported employers, local requirements, access and reporting. If one employer needs a different service, define how the shared team will coordinate it and how finance will receive comparable evidence. Evaluate the additional handoff rather than assuming a mixed setup must fail.
Will one employee login reduce the billed employee count?
Only the seller's billing definition can establish that. Ask about a person paid by two companies, a person transferred during the month, an inactive record and a contractor. Record the counting date and unit in the quote. An employee-facing identity and a chargeable payroll record serve different purposes.
What if the seller cannot demonstrate our structure?
Ask whether a documented configuration, sample output or limited proof exercise can establish the requirement before commitment. Set a clear acceptance condition and responsible reviewer. If a required capability remains unsupported, keep it unresolved and consider another offer; do not label a sales roadmap commitment as a currently available feature.
When should we keep the simpler arrangement?
A separate-company setup may be sufficient when the employers run independently, the shared tasks are limited and the team can reliably produce the required outputs. Compare that known work with the proposed alternative's demonstrated benefit, implementation effort and recurring cost. Buy the additional capability when it answers an actual requirement the business values.
A next step if you are comparing payroll services
Use the purchase scorecard to brief a SelectSoftware Reviews advisor conversation. Confirm each proposed provider's company limits, billable units, access boundaries and exit terms directly before choosing.
Explore related payroll resources:
About the author
Ben Scott writes and maintains payroll decision guides for founders and operators. His work focuses on execution realities and how decisions hold up under growth, complexity, and controls and documentation pressure. He works hands-on in HR and leave-management roles that intersect with payroll-adjacent workflows such as benefits coordination, cutovers, and compliance-driven process controls.
