A payroll manager gets a tax notice from the state of Ohio, forwards it to their PEO or payroll processor, and then waits. Weeks pass. They send a follow-up email that gets no reply. They escalate. Someone new picks it up. This is the moment — they have no idea whether their issue is being worked, who owns it, or what's outstanding across all the states they operate in. That moment repeats every quarter.

The gap persists because the payroll processors have no structural incentive to give employers real-time visibility into open tax issues. Visibility would surface how slow resolution actually is, which creates support tickets and churn pressure. The buyer is often an HR director or controller who isn't on the payroll processor's daily operational radar — they only hear about tax issues when penalties arrive.

Right now, a multi-state employer tracks open tax notices in spreadsheets or email threads. There's no centralized log of what notice came from which jurisdiction, when it was forwarded to the processor, what the deadline is, and what the current status is. Users explicitly said 'the tax amendment process has been taking our company multiple years' and that quarterly filings have to be 'manually requested' each time instead of arriving automatically. Nobody is building a lightweight case-management layer that sits between the employer and their payroll processor specifically for tax notices.

This is a business and not a feature because the problem recurs every quarter, scales with the number of states an employer operates in, and the cost of a missed notice or late amendment is a concrete penalty with a dollar amount attached. An employer with employees in 12 states might have 20–30 open tax items at any given moment. They'll pay to know where each one stands.

What to build

Build a web app where employers log incoming state and local tax notices, assign them to a processor or internal owner, track deadline dates and status, and get automated reminders when a notice is approaching its response deadline — exportable to CSV with a full audit log per jurisdiction.

Where to start

Start with Ohio and New York, the two states mentioned most often in complaints, and build out the specific local jurisdiction logic (Ohio school district taxes, NY local forms) that makes generic trackers useless — that specificity is what makes someone switch from a spreadsheet.

The hard part

Getting the first cohort of users to change their existing habit of tracking this in email and spreadsheets — the pain is real but the workaround is 'good enough' until a penalty hits, which means selling before the crisis, not after it.

How it makes money

Monthly subscription per employer account, tiered by number of active states tracked — starts around $99/month for 1–5 states, scaling to $499/month for 15+ states.

See the evidence. The complaints behind this idea, the products they came from, and similar ideas in Core HR.

More ideas in Core HR