A friendly, plain-English tour of your payroll file — what every number means, and why a flagged row is never late, never a fine — and what happens if a missing class code isn't fixed within 24 hours.
From the moment a payroll file reaches us to a fully explained premium.
When a payroll file reaches us — uploaded by you, sent by your payroll company, or delivered automatically by a connector — it goes on a short, friendly journey:
Everything on the page, explained — no black boxes.
At the top of every file are the overview cards: Class Codes Reported, Employees Reported, Valid Rows, Total Payroll Reported, and Premium Reported. Tap More on Total Payroll to see Auditable vs Gross, and Subject vs Excluded wages.
You'll always find two things in the header. Notification Proof shows a timestamped record of every notification we sent about this file — and if nothing was ever sent, it says so honestly. Download original CSV hands you back the exact file that arrived.
What makes a row wait — and everything that doesn't.
A row turns red only when we genuinely can't price it — for example:
Everything else is green (priced) or slate (a $0-payroll period — tracked so you can confirm it was intentional).
This is the part people worry about, so let's be direct.
Red rows collect in the Quarantine tab, and a calm red banner appears at the top of the file. Here's what it says — and, just as importantly, what it does not mean.
Your file arrived — you reported on time. The period shows as received.
Nothing punitive happens. There is no interest, no fee, nothing.
Premium for a red row is not collected while it waits for your fix — your debit waits for it too.
A missing or invalid class code not fixed within 24 hours of our email is priced at your policy's highest-rate class, as our terms of service state.
“Fix a missing class code within 24 hours — otherwise it is charged at your policy's highest-rate class.”
When a red row happens, the reason is spelled out plainly — no codes to decipher:
So the honest consequence of leaving a class code unfixed: 24 hours after our email, that row is priced at the highest-rate class on your policy and included in your debit. A correction you send afterwards applies from then on. Anything else still unresolved when the policy ends is compiled into a report for your carrier's renewal audit.
Why some rows are calmly set aside — with nothing to fix.
If your roster marks an officer as excluded from coverage, or a row belongs to a subcontractor, that person was never going to be billed. Their rows are set aside at $0 in their own calm, informational tabs — Officers Excluded, Subcontractors — with no red, no action needed, and nothing to fix.
The one and only time a fix costs anything — and you see the number first.
Every notice is branded for your program — and provable on-screen.
Every notice we send is recorded in the file's Notification Proof panel — a timestamped, immutable record that serves as legal proof of notice. If nothing was sent, it tells you that too.
Nothing is silently dropped, and nothing is retroactively charged.
When a policy term ends, any records still unresolved are compiled into an unresolved-records report for the carrier's renewal audit. That's the whole story — nothing is silently dropped, and nothing is charged after the fact.