Surfaces · Wages.software
Each surface has one job and a visible stopping point.
The branded desks and views below are design descriptions, not deployed screens. Read their field lists as a manual screen study. The underlying calculation contracts and the public reference pages have separate, narrower status.
Operator surfaces
The calculation desk, rules register, and reconciliation view answer different questions.
The calculation desk is for an authorized finance operator to assemble one scoped request and inspect its result. It shows the earnings and deduction lines supplied by the caller, the authority-specific bases derived from them, the ruleset version, exact-cent outputs, and any refusal. It is not a timesheet, an HR record, or a ledger. The branded operator desk is planned; the underlying calculation modules exist at different levels of reachability described elsewhere on this site.
The rules register is the future place for provenance: authority, effective window, source artifact, signature, version, and review state. In this design discussion, a table cannot be treated as applicable merely because it is newest. Dates may overlap, a source may be replaced, and historical calculations must remain reproducible. The register therefore needs an explicit activation decision and an audit trail before it can be described as operational.
The reconciliation view places totals beside one another without manufacturing agreement. It should identify the exact lines that differ across check detail, quarter totals, W-2/W-3 figures, and Form 941 figures. A mismatch is a work item for an authorized operator. It is never silently written into an adjustment line.
Narrow intake and handoff
Employee validation and export seams remain smaller than a payroll platform.
An employee-facing validation surface may check the shape of a W-4, address change, or bank instruction and return masked feedback. It does not become the system of record merely because a browser displayed it. Any future persistence, approval, retention, or downstream delivery would need its own product boundary and evidence. Today the marketing site accepts none of that information.
Export surfaces are equally constrained. A structural NACHA check can show that a batch has required record shapes and balanced control totals while still withholding the raw file. A reporting projection can prepare values for review while remaining distinct from filing. The handoff should carry a result, provenance, and refusal history to an authorized external operator or system; it should never claim that the receiving institution accepted the data.
Public pages form a separate surface. They explain the model, status, and limits, and they offer a mailto link for an early-access conversation. They expose no employee search, finance route, demo tenant, or synthetic interface that could be mistaken for a working payroll console.
A screen-by-screen walkthrough
The desk presents one case; the library governs reusable rules; the comparison room investigates disagreement.
Imagine a synthetic operator opening the calculation desk for a single historical pay period. The first panel is an intake summary, not a spreadsheet clone: opaque worker reference, period boundaries, earning categories, deduction elections, filing attributes, and the authority list requested. A second panel previews the independently derived bases. A third identifies the exact ruleset version selected for each authority. The result panel then places returned cents beside reasons and refusals. Nothing on that screen says paid, deposited, filed, or approved.
The rules library has a different rhythm. Its useful objects are source artifact, issuing authority, effective-from and effective-through dates, digest, signature, reviewer, and activation state. A librarian can compare a candidate version with the previously active version and identify overlapping windows before an operator selects it. Historical versions remain readable so an older calculation does not silently inherit today’s brackets. Publishing belongs to an explicit review action; uploading a newer filename is insufficient.
The reconciliation room starts from artifacts rather than from employee setup. It lays check-detail totals, quarter aggregates, annual wage statements, transmittal totals, and return lines beside one another. Expandable difference groups show which authority and box diverged and by how many cents. The workspace creates no balancing entry. It gives an investigator a bounded list of disagreements to trace back to source data, table provenance, or classification.
The handoff view is smaller still. It packages normalized inputs, versions, outputs, and refusal history for an authorized receiving system without pretending the receiver acted. Export status can mean prepared or withheld; it cannot mean a bank accepted a batch or an agency accepted a filing. These deliberately different visual grammars keep a reader from mistaking browsing a rule, calculating a number, comparing evidence, and completing an external operation for the same action.
Review a paper screen by asking which question its fields can answer.
Use three sheets of paper for a fictional finance review. Label them Case, Rule and Comparison. These are human design aids, not screenshots of a deployed Wages workspace. On Case, put an invented period, an opaque reference and two earning lines. On Rule, put the source name, version and effective window supplied for the exercise. On Comparison, put two totals that differ. Keeping the sheets apart makes it easier to notice when a screen borrows authority from a field that belongs somewhere else.
Suppose the Case sheet includes a green badge labelled paid because its arithmetic completed. Cross out the badge. A returned calculation does not support that status. Suppose Rule says current because someone uploaded the most recent-looking document. Replace that label with the actual effective dates and the open review question. Suppose Comparison says corrected because a difference was found. Write difference identified instead. Each edit narrows the wording to the evidence on that sheet without claiming that a new software control performed the review.
An entry point needs an honest exit label.
The same exercise applies to an employee-change design. A draft screen that displays a masked account ending has shown a representation of an input. It has not proved that an instruction was saved, approved or delivered. The existing validation modules return decisions and masked values; the published boundary explicitly distinguishes those returns from persistence. A designer can write acceptable shape as a proposed feedback label while leaving saved instruction off the sketch. The public website takes no such input and creates no employee record.
For a bank-output sketch, separate structural review from a downloadable or transmitted file. The named NACHA preview withholds the raw payload. A proof summary therefore needs language about what was checked and withheld, with no visual implication of a completed transfer. A disabled-looking bank icon would not be sufficient if the surrounding sentence still said deposit scheduled. A reader should understand the stopping point from the words alone. This is a screen-copy review method, not an assertion that a handoff console is operating.
Request the smallest surface that resolves the actual uncertainty.
Someone evaluating Wages may ask for a dashboard because they need an answer quickly. First identify that answer. A disagreement about deduction treatment calls for the independent bases and supplied classification. A question about which source applied calls for provenance. An annual mismatch calls for comparable artifacts. A dashboard that mixes all three can make the page look complete while leaving each question unanswerable. Ask for the minimum fields that make one decision inspectable, and name the operational action that remains outside that view.
The five public companion guides serve a different purpose again: they help a reader understand and question the product without entering staff data. The existing taxable-basis explorer illustrates subtraction through links; it is not the shipped calculation engine or a payroll account. A guide, a manual screen sketch and a registered compute route are three different surfaces. Their labels should remain distinct even when they describe the same arithmetic. No reading action on this site grants finance access, accepts a filing or enables a payment rail.
None of these screen descriptions offers an AI assistant or a live purchase flow. There is no checkout on the public site, and the described bank preview does not disburse money. Treat a sketch as a way to question labels and responsibilities; it supplies neither a working finance session nor permission to use an unavailable action.
Before accepting a sketch, ask another adult reviewer to explain its labels without hearing the presentation. If they read prepared as transmitted, the wording needs another pass. If they believe an example reference opens an employee record, remove that implication. The result of this manual readback is a list of labels to clarify, not an access review performed by Wages. This gives a design discussion a practical stopping rule: the proposed screen must explain the limited decision before it can support a conversation about an operational workflow.
Where to go next
The rest of this site.
Every page here is its own argument rather than a restatement of the home page. If you would rather ask a person, the address below reaches one.