Method

How the numbers are checked

NetPay Pro is a static calculator site. This page describes what it computes, where each parameter comes from, and what it deliberately leaves out.

What kind of site this is

The site is static: HTML, CSS and JavaScript served from a content delivery network. There is no application server, no database, no user account and no upload. Every calculation runs in the reader's browser, and the salary typed into a calculator is never sent anywhere.

That architecture is also a limit. The site cannot see a Form W-4, other income or itemised deductions, so it can only compute from the parameters published for the tax year. It is a calculator and a reference, not a preparer.

Where each parameter comes from

  • Federal brackets and standard deduction — IRS Publication 15 (2026), Circular E, and the 2026 inflation-adjustment release IR-2025-103. The head-of-household and married-filing-separately schedules come from Revenue Procedure 2025-32.
  • Social Security and Medicare — the contribution and benefit base published by the Social Security Administration, the rates in Publication 15, and the Additional Medicare Tax threshold from Form 8959.
  • State income tax — either the state's published schedule or statute, linked on the state page, or a single editable planning rate where no schedule has been verified. The page always says which of the two applies.
  • State payroll programmes — disability, family leave, UI and similar lines, from the agency that administers each one.

The order the calculator applies them

Every calculator here runs one sequence, and the sequence is part of the answer:

  1. Social Security, Medicare and any state payroll programme are charged on gross pay. A 401(k) deferral does not reduce them.
  2. The deferral is then capped three ways: the year's elective deferral limit, gross pay itself, and what remains after the payroll lines already taken. The third cap is why a deferral set to the whole salary cannot produce a negative take-home figure in a state that charges a disability premium on that salary.
  3. Federal income tax is computed on gross minus the deferral minus the standard deduction, then reduced by the child credit, which is itself limited to the tax actually owed.
  4. State tax starts from the same deferral-reduced base, with one exception: Pennsylvania taxes the first dollar of wages and does not recognise the deferral at all.
  5. Local tax and the remaining payroll lines come last, which is why they appear below the state line in every breakdown table.

Two consequences follow from that order, and both are visible in the figures: a deferral is worth its marginal rate rather than its face value, and a payroll premium is charged whether or not the reduced pay reaches a bank account.

How a figure is verified

  1. The number is read from the primary source, not from a secondary summary.
  2. It is entered in data/tax-params.json with the URL that supports it and the field it covers.
  3. The page is generated from that file. No figure is typed into the HTML by hand.
  4. A release check compares the rendered page against the data file and fails if they disagree. A second check fails if any content page links to no primary source at all.

What the parameter file records

data/tax-params.json is the only place a tax figure exists. Each entry carries four things: the value, a label a reader can understand, the URL of the document that states it, and the date that document was read. A number without a source URL is not accepted by the build, and a page cannot ship while one of its figures is unsourced.

The pages are generated from that file rather than written around it. Changing the 2026 standard deduction in the data file changes it in the tables, in the worked examples and in the structured data on every page that quotes it. An error is therefore usually a data error: the prose sits downstream of the parameter, not the other way round.

What agreement between engines proves, and what it does not

The browser bundle and the build engine are separate implementations. Every build compares them across 5,120 combinations — sixteen states, four filing statuses, ten incomes, four deferral rates and two household sizes. A third implementation, written for auditing rather than for production, recomputes 4,016 cases.

All three read the same parameter file. Agreement therefore proves that the model is implemented consistently, and that no page can disagree with the calculator beside it. It does not prove that the model describes the law. That claim rests on the source URL attached to each parameter, and on a person reading the statute — the part a test cannot do.

Confidence grades

State pages carry one of three labels, and the label is not decoration. Of the 51 jurisdictions the site tracks, sixteen carry an encoded schedule — four of them a statutory zero — and the remaining thirty-five use a single editable planning rate:

  • Exact brackets — the state's published schedule or statute is encoded and computed.
  • No wage tax — a statutory zero, written into the state's own law.
  • Estimate — a single editable rate used as a planning starting point. It is not a published schedule, it does not vary by filing status, and the page says so and dates it accordingly.

What is not modelled

On the state paycheck calculators, which compute one salary for one person: itemised deductions; credits other than the child tax credit; a second job and the withholding gap it opens; self-employment income; health premiums, HSA and dependent-care accounts; local income taxes at any rate other than the typical one pre-filled on the Ohio, Pennsylvania and Michigan pages; and a mid-year move between two states. The advanced calculator carries several of those — pre-tax accounts, a second job, a bonus, 1099 income, the care credit, three state child credits and a move across a state line — and names on its own page what it still leaves out.

What no page here computes: state child credits beyond California, New York and New Jersey; local wage taxes that survive a reciprocal agreement, such as Philadelphia's; the underpayment penalty; and the part-year proration of state credits. A rule that is not implemented is never printed as zero. It is written out in the section that would have carried it, because a blank in a table reads as nothing owed — which is a number, and a wrong one.

When pages are re-checked

Every state page shows the date its figures were last checked, taken from the data file rather than typed into the page. The 2026 federal figures were checked against IRS and SSA publications on 10 November 2026. A new tax year or a published revenue procedure triggers a re-check before the site claims the new year.

Corrections

Corrections are published, not silent. The change log records what changed and why, including the cases where an earlier claim on this site was wrong. The contact page explains how to report one.