CEDX Payroll · Finance
Run 2026-BW16 is open: $1.24M gross across 318 people, $862K net, $318K of tax liability and 38 exceptions standing between now and the August 15 check date. Payroll shows you exactly what blocks the run — and answers questions from the run data, not a model.
Ask payroll is labelled on screen: “deterministic; answers from the run, exception and tax arrays, no model.” What changed vs last run is arithmetic, and the arithmetic is shown.
Runs on demo data. The answer panel cites its own source: “Source: Open run”.
What it is
Ask payroll computes from the run, exception and tax arrays: “What changed vs last run?” returns $1.24M gross, +$24K (+2.1%) vs BW15, headcount 318 (+2), exceptions 38 vs 12 settled last cycle — with the source cited on the answer.
The employee register carries title, department, type, rate, state, a masked bank account and tax-form status per person. 33 are missing bank details — an ACH risk priced before payday, not after a failed deposit.
360 paystubs at $1.65M filtered gross, and 35 of them are on hold with blocked ACH — visible as a count on a card, not discovered in a bank rejection file. 27 more are flagged for review before approve.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/payroll.
01 — Overview
BW16 at $1.24M gross with 54 blocking exceptions, tax deposits of $614K due soon and funding 89% ready. Alerts arrive root-caused: an ACH that will fail on a failed bank re-verify at $4.5K, a first pay incomplete without W-4 or bank at $2.4K, a garnishment riding on an expired form at $1.7K.
02 — Runs
Every run with check date, status, schedule, headcount, gross, net and exception count. BW16 sits in review at $1.24M with 38 exceptions; the off-cycle bonus run paid 42 people $186K gross in July, separate from the biweekly drumbeat.
03 — Paystubs
The stub register shows employee, run, check date, department, hours, gross, net and status. Paid rows sit next to Ready, Flag and the 35 on Hold — the difference between “will be paid” and “needs a person” is a column, not a phone call.
04 — Employees
309 active people with the data payday depends on: rate and type, state, masked bank, tax-form status. The 33 missing-bank and 18 tax-form issues are the same numbers the run's exception count is built from.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Lives in the open run: clears the 54 blocking exceptions, chases the 33 missing bank details and watches the funding-ready percentage climb to 100.
funding 89% · 54 blocks
Owns the $614K deposit queue and the 18 tax-form issues — federal and state, due soon, with the semi-weekly window already open.
$614K due · 18 forms
Reads the run the way the close will: gross by department, tax liability split employer and employee, and what changed against last cycle.
+$24K · +2.1% vs BW15The shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your estate — it is the state of the demo data.
How it runs
The run assembles from the employee register — 309 active people with rates, states and tax status — into a gross of $1.24M across 318 paid this cycle.
Exceptions surface before money moves: failed bank re-verifies, missing W-4s, expired forms on garnishments. 54 of them stop the run; the rest are flagged.
Questions get computed from the run arrays — what changed, who is missing forms, how much the next tax debit is — with the source cited on each answer.
Funding ready climbs to 100, deposits of $614K go out in the semi-weekly window, and 360 stubs move from Ready to Paid.
One record
These captures come from one demo workspace — Northline US Inc. — so the people and amounts here are the same ones the rest of the estate carries.
The HR record the employee register mirrors — titles, departments and onboarding states shared, not re-typed.
CEDX TimeWhere the hours on the paystubs come from — 80-hour rows start life on a time clock, not in a spreadsheet.
CEDX BooksThe ledger the gross-by-department figures post to — and the finished reference page for this estate's evidence standard.
Limits
Finding this out on the third call is worse for you than reading it here, and worse for us.
Start
Open it right now
Your people, your schedules
Payroll with the rest of it
Questions
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/payroll. It runs on demo data.
Exactly what the screen says: answers are computed deterministically from the run, exception and tax arrays. “What changed vs last run?” is arithmetic over those arrays, and the answer cites its source — nothing is generated or paraphrased.
The 54 blocking exceptions on the open run: failed bank re-verifies, missing W-4s, expired tax forms riding on garnishments. Each is priced and root-caused on the overview before the check date, not after a failed deposit.
The build calculates tax liability ($318K employer plus employee) and the deposit schedule ($614K due soon). We are not claiming agency submission — no capture shows a filing receipt, so that claim stays off this page.
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
Live build, demo data, no card. Then count your own blocking exceptions and compare the view.