saascode
hr, payroll & talent·run 220 · Jun 2026

Boxtwelve

A pre-filing review workspace that checks qualified-tip, overtime, contribution and occupation-code mappings and prepares employee explanations for accountable payroll approval.

Genesis score6.08/10
Make Boxtwelve real.0/500
500 more votes and Boxtwelve is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The case

The supplied research confirms new mandatory 2026 wage-statement reporting fields for qualified overtime, qualified tips, certain contributions and tipped-occupation information, with the filing cycle continuing into early 2027. Payroll platforms may add native support, but organizations on legacy or partially updated systems still need to verify how source earnings and employee records map into the new output. Boxtwelve proposes a narrow upload-and-review tool for that transition.

A structural check cannot establish tax eligibility. Source earning, earning-code classification, employee occupation, payroll-system mapping, generated wage-statement field, exception candidate, payroll determination, correction approval, regenerated output, employee notice, filing transmission, agency acceptance and later correction remain separate. The product should identify missing, duplicate or inconsistent mappings and show the exact source rows; it must not decide whether wages legally qualify or sign on behalf of the employer.

The opportunity is intentionally small and time-bound. Employee communication adds useful polish, but the durable path would require broader payroll control coverage. Two referenced interfaces remain unverified, so the first product should accept controlled exports rather than promise universal connectivity.

Who pays — and why

A payroll or HR operations leader at a mid-market employer preparing 2026 wage statements on a system whose new-field mappings still require independent review.

What it unlocks
A row-level mapping review that preserves earning source, payroll code, proposed reporting field, employee record and rule version
An exception queue for missing, duplicated, contradictory and out-of-period values with an accountable payroll disposition
A reviewed correction worksheet and plain-language employee notice tied to the exact regenerated output rather than a generic template
How Genesis scored it
6.08across seven criteria
tension 6temporal 8blindspot 5buyer 5leverage 7convergence 5why-not 6
8
Temporal window

Finalized 2026 wage-statement requirements and the filing cycle create a specific near-term window.

7
Asymmetric leverage

Deterministic validation can scale across files once schemas are mapped, with review remaining employer-specific.

5
Convergence

One cross-reference and no inbound connections provide limited supplied convergence.

Why it scored well

The input supplies a concrete mandatory reporting change, a filing clock and a narrow file-in-to-reviewed-output mechanism that can ship quickly.

What's holding it back

Buyer evidence is incomplete, both cited interfaces are unverified, native payroll vendors are already updating and the concept is deliberately a transitional wedge with limited standalone moat.

Signals detected4 sources crossed
SignalSupplied official-form research

SignalSupplied payroll guidance research

SignalSupplied competitor research

SignalSupplied market scan

Direction briefboxtwelve.md
boxtwelve.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.