saascode
hr, payroll & talent·run 319 · Aug 2026

Retrolot

A payroll evidence ledger that versions calculation rules, rates, classifications and jurisdiction inputs per pay line, then identifies bounded recall candidates for authorized review.

Genesis score6.72/10
Make Retrolot real.0/500
500 more votes and Retrolot 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

Payroll teams can recompute a known period, yet may struggle to identify every paycheck affected when a rule, rate or classification is later found wrong. The supplied research confirms an open-source calculation substrate and a unified read layer across many payroll providers, while finding no reviewed standalone product focused on recall by rule version. That supports a traceability gap, not proof that existing payroll systems cannot answer the question in every deployment.

A rule change does not automatically authorize a correction. Effective dates, jurisdiction, worker classification, collective agreements, tax treatment, payroll provider behavior and limitation periods require qualified review. A calculated difference is not an approved wage obligation, posted payroll adjustment, tax amendment, employee notice or payment. Payroll records contain highly sensitive identity and compensation data and need strict tenant isolation, access, retention and correction history.

Source rule, interpreted rule version, rate table, worker fact, classification decision, pay input, calculated pay line, issued paycheck, recall candidate, reviewer finding, approved correction, provider acknowledgment, tax filing, employee notice and settled payment are separate. Retrolot should make affected records discoverable and reproducible while leaving legal interpretation, payroll approval, filing and money movement with authorized professionals.

Who pays — and why

A payroll operations, compliance or finance team responsible for multi-jurisdiction payroll and retroactive corrections across one or more payroll providers.

What it unlocks
An append-only lineage from every pay line to source rule, interpretation, rate table, classification, jurisdiction and input version
Rule-scoped recall candidates with reproducible recalculation, uncertainty and reviewer disposition
An authorized remediation packet that remains separate from payroll posting, filing, notice and payment
How Genesis scored it
6.72across seven criteria
tension 6temporal 8blindspot 5buyer 8leverage 6convergence 5why-not 8
8
Temporal window

Recent calculation infrastructure and supplied wage-recovery signals create a current operational window.

8
Buyer persona

Payroll and compliance teams own retroactive correction work with direct employee and filing consequences.

5
Convergence

Wage-recovery pressure, payroll APIs and rule engines converge around traceability, supported by several related ideas.

Why it scored well

The input identifies a concrete payroll-compliance buyer, confirms calculation and provider-access substrates and finds a plausible gap in identifying affected periods by rule version.

What's holding it back

Legal and payroll authority are complex, provider history may be incomplete, existing vendors can add lineage, the supplied compliance-cost figure is secondary and the proposed non-backfillable moat is not demonstrated.

Signals detected4 sources crossed
SignalSupplied repository research

SignalSupplied provider research

SignalSupplied competitor research

SignalSupplied enforcement research

Direction briefretrolot.md
retrolot.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.