Sell payroll plans to employers in every state from one subscription website.

Plan comparison tables, a headcount slider that shows the monthly figure before checkout, and clear lines on what each tier includes: number of states, contractor payments, year-end forms, integrations and support level. Add-ons show their own per-employee charge so nothing appears for the first time on an invoice.

Card payments through hosted fields so card data never touches your servers, plus bank debit with a written ACH authorization that follows Nacha rules. Many employers prefer paying by bank, and the site records the authorization text, time and IP address against the account. Larger employers on annual contracts can pay by invoice instead.

Your payroll product reports how many people were paid in each run or month, and the billing engine charges for that count. We set rules for minimums, mid-month hires, terminated employees paid a final check, and contractors billed at a different rate. The invoice shows the count so customers can check it against their own payroll register.

An employer moving from a single-state plan to a multi-state one, or adding time tracking halfway through a cycle, gets a prorated charge or credit calculated automatically. Downgrades can wait until the period ends so nobody loses features they already paid for.

After South Dakota v. Wayfair, a payroll SaaS company can owe sales tax in states where it has no office once sales pass that state's threshold. States also disagree on whether SaaS is taxable at all. We connect a tax engine that decides by the customer's service address and stores exemption certificates.

Customers already billed from spreadsheets, an older billing tool or manual invoices are imported with their plan, start date, payment method token where the processor allows it, and current period. We run the old and new systems side by side for one billing cycle and compare every invoice before switching off the old one. Customers get a short notice explaining what changes on their next invoice, if anything.

Retry schedules timed to when cards and bank accounts usually clear, reminder emails that link straight to an update page, and a grace period before the payroll account is restricted. You decide whether a lapsed account can still run a pay run already scheduled, since stopping payroll harms employees.

Owners and billing admins change plans, update payment methods, add billing contacts and download numbered PDF invoices showing the legal entity, tax lines and employee count for each period. Cancellation is available online through the same kind of path used to sign up, which is what federal enforcement under ROSCA expects of a recurring charge.

A successful checkout creates the company record, the admin user and the plan entitlements in your payroll application through its API. Plan changes and cancellations flow the same way, and webhooks keep both systems in step if one is briefly unavailable.

Employers search for payroll by state, by industry and by problem, such as paying workers in two states or running payroll for a restaurant. We plan landing pages that explain your coverage in each state you support, with structured data on plans and pricing so search engines read your offer correctly, all served from the same fast templates as the checkout.