Six questions to ask before buying white-label payroll

“White-label” is used for two very different things. One is a logo upload. The other is a product your clients experience as yours from the first screen to the last email. The questions below separate them before a contract does it for you.

1. How far does the branding actually go?

Ask to see three things, not a marketing page: the login screen a client sees, an email the platform sends to an employee, and the URL in the address bar. A platform that brands the dashboard but sends payroll notifications from its own domain has told your client who really runs their payroll. A custom domain is the honest test — it either serves your clients at your address, or it does not.

2. Who signs the filing, and can you see it?

This is the question with the sharpest consequences. If the platform files on its own authority, your firm is a referrer with a dashboard. If the filing is made under your firm’s own IRS authorisation — a Reporting Agent authorisation, with a Form 8655 signed per client — then the relationship with the agency is yours too.

Then ask what you are shown after the return is sent. A status chip that says “filed” is not an answer. Ask whether you see the acknowledgement itself, and what the screen says between “transmitted” and “accepted” — because a submission ID means received, and only the acknowledgement means accepted. A product that blurs those two will let you close a quarter that was rejected.

3. Who holds the money?

There are two models and they are not interchangeable. In one, the platform debits your client, holds the funds, and pays out. In the other, the platform prepares the files and the employer’s own bank originates every transfer.

The first is more convenient and puts a licensed intermediary — and its float, its hold times and its risk decisions — between your client and their own payroll. The second asks the employer to press the button at their bank. Neither is wrong. What matters is knowing which one you bought, because it decides who your client calls when a deposit is late.

4. What happens when you hire help?

Most firms discover this limitation at the worst time: they bring on an assistant for the busy season and find the only options are “sees everything” or “sees nothing.” Ask whether access can be limited to specific clients, and — the part worth probing — whether that limit is enforced by the data layer or by hiding menu items. The difference is invisible in a demo and very visible in an audit.

5. Which states, and how deeply?

“All 50 states” and “supports your state” can mean a flat percentage with a state name attached. The useful questions are specific: does it handle an employee who lives in one state and works in another; does it know the counties where the local rate varies; does it generate the quarterly wage file the state unemployment agency actually accepts, or just a report you retype into a portal.

Fewer states done completely is worth more than a map with every state shaded.

6. What still takes a person?

Every payroll platform has manual steps, because several agencies simply do not offer a machine interface. The Social Security Administration’s web service, for one, is closed to new submitters — so somebody uploads the W-2 file.

The question is not whether manual steps exist. It is whether the vendor will tell you where they are before you sign. A list of honest exceptions is a better signal than a page with no exceptions on it.

What to do with the answers

Score them against how you actually bill. If payroll is a courtesy you provide to keep tax clients, convenience wins and the brand matters less. If payroll is a service you are selling, then branding, filing authority and client-level access are not features — they are the product.

Where we stand: PayrollPro was built for the second case — the firm’s brand and domain, filings under the firm’s own IRS authorisation, and payment files the employer’s bank originates. That design has trade-offs, and we list them.