WorkPayContracts2026

How to Read a Payslip or Employment Contract Without Missing the Terms

The contract is the promise and the payslip is the performance, and the seam is where they disagree — and the deductions on a payslip are ordered, not parallel, so the sequence is the mechanism the single net figure conceals. Here is the gross-to-net waterfall, the promise-versus-performance split, the written-particulars rule, the deduction-lawfulness tells, and the hours-and-rate arithmetic check. The page is about reading the documents, not about whether your employer is honest; most payroll is accurate, and the discipline is the check, not the suspicion.

General information only — not legal advice, not financial or tax advice, and not a description of any specific jurisdictions employment, pay, or tax rules. This page explains the shape of reading a payslip and a contract — the gross-to-net waterfall, the promise-versus-performance match, the written-particulars rule, the deduction-lawfulness tells — in broad terms. The payslip entitlement and its threshold, the written-particulars list, the lawful-deduction rules, the minimum-wage treatment, who counts as a worker versus an employee, the tax and social-insurance computation, and the grievance and tribunal routes vary by jurisdiction and change over time; they belong to your employer or payroll, the national labour authority or regulator, the tax authority, a union, and a solicitor — not a guide page. And the two load-bearing limits: checking is not refusing — a checked payslip may still be entirely correct, and stopping work over a query is a different failure from querying a line; and a verbal promise that is not in writing is usually not a term you can rely on, because the document is what the procedure and the tribunal read.

A narrow plain blank paper strip lying diagonally across a larger plain blank folded paper sheet, on a clean light surface — The narrow blank strip lying diagonally across the larger blank folded sheet is the promise and the performance made physical: the contract is the wider document that says what you were hired on, and the payslip is the narrow strip that shows what was actually paid — and the discipline is to lay the narrow one across the wide one and check that they agree. Both stay blank on purpose — the lesson is the match between the two documents, not the words in either, because the seam where a wage goes wrong is almost always the seam where the promise and the performance disagree.

Updated September 2026By the AI Help Guide editorial team11 min read

The Number You Stop Questioning

The Most Common Loss Is Not a Stolen Wage — It Is a Quiet One You Never Checked

The mental image of a wage problem is a dramatic one: a withheld paycheck, a fired employee, a tribunal. The image is real, but it is not the largest loss, because the biggest hole in any payroll is the small, silent, repeated error — the overtime rate applied at the wrong multiplier, the deduction taken from the wrong base, the shift premium omitted, the salary-review promise that never reached the written particulars, the student-loan or pension contribution computed on a figure that has since changed. Each is small; each recurs every pay period; and each is invisible, because the payslip shows you a single net figure and the eye stops at the number that lands in the account. The most common loss is not a stolen wage. It is a quiet one you never checked, accepted because the document looked authoritative and the arithmetic looked finished.

This page is the pay half of the employment-and-work trio; its companions, the raise-a-grievance guide and the leave-a-job guide, deal with the dispute and the exit. The promise-versus-performance split below is the two-documents-that-should-match discipline our read-a-hospital-bill guide built for an EOB and a bill, transplanted to employment: 89 reconciled the insurers statement against the providers demand line by line; 91 reconciles the contracts promise against the payslips performance, and the tell is the same — a figure that does not match the document that authorises it. And it ends where 89 did not have to: with the gross-to-net waterfall, the sequential-deduction mechanism a medical bill never had, because a bills columns sit side by side while a payslips deductions come off in an order that changes the base each one is computed on — so the single net figure conceals not just the deductions but the sequence, and the sequence is where the error hides.

The gross-to-net waterfall — the deductions are ordered, and the order is the mechanism

Gross pay — the starting figureHours worked times your rate, plus any overtime, shift premium, bonus, or allowance that the contract authorises for this period. This is the top of the waterfall and the figure every later step is computed against.

Base for step 2: the full gross.

The deductions that reduce the taxable baseIn many systems, certain contributions — pension and some others — come off before tax is computed, so they reduce the figure the tax is calculated on. This is the step whose position in the order most changes the outcome, and the one a reader who only looks at the net cannot see.

Base for step 3: gross less these pre-tax deductions.

Tax and social insurance on what remainsIncome tax and the social-insurance or national-contributions equivalent are computed on the reduced base from step 2, not on the full gross — which is why a pension increase can change your tax as well as your savings, and why reading these figures off the wrong base is a common error.

Base for step 4: the post-tax-and-insurance remainder.

The other statutory and agreed deductionsStudent-loan or graduate-loan equivalents, court-ordered attachments, and any deduction your contract or a written agreement authorises — taken in the sequence the rule sets, each on the base that remains after the one before.

Base for step 5: the remainder after these.

Net pay — the figure that landsWhat reaches your account. This is the only number most readers see, and it is the output of the waterfall, not the input — so checking only the net tells you nothing about whether the sequence above it was right.

The result, not the starting point.

Why the order matters: the deductions are sequential, not parallel — each one is computed on the base that remains after the one before it, so a deduction taken in the wrong place in the waterfall changes the amount of everything downstream. A medical bills columns sit side by side (charged, allowed, plan-paid, patient-responsibility) and the check is the match between them; a payslips deductions stack in an order and the check is the sequence. This is why reading only the net is reading only the output: the error hides in the step where the base changed, and the base changes at every step.

The waterfalls logic is the read-a-hospital-bills arithmetic logic, deepened by one dimension the bill did not have: a bills columns are parallel and the check is the match, but a payslips deductions are ordered and the check is the sequence. The most common failure is the reader who looks only at the net — the single figure that lands — and therefore cannot see that a pension contribution was taken after tax rather than before, or that a loan deduction was computed on the full gross rather than the post-tax remainder, or that a shift premium was omitted from step 1 and so never entered the base at all. The discipline is to read the waterfall from the top: check gross first, then follow each deduction in order and ask what base it was computed on, because the net is the output and the output cannot tell you whether the sequence was right. And the reciprocal limit, stated in the same breath: checking is not refusing — most payrolls compute the waterfall correctly, and a checked payslip may still be entirely right.

The contract — the promise, and what you were hired on

The rate, the hours, the frequency, the overtime and premium terms
The pension arrangement and the contribution levels
The holiday entitlement and the accrual basis
The deductions the employer is authorised to make
The written particulars the rule says must be given to you
This is the document that authorises every figure downstream

The seam is the whole method: the contract is the promise and the payslip is the performance, and the error almost always lives where they disagree — a rate that does not match the contract, a deduction the contract does not authorise, a premium the contract promises and the payslip omits, a term that was promised verbally and never reached the written particulars. Lay the narrow strip across the wide sheet and check them line by line, exactly as the bill guide reconciled the EOB against the bill: the promise is the reference, the performance is the demand, and the match is the check.

The payslip — the performance, and what was actually paid

The gross, the deductions in order, the net
The period, the pay date, the employer and employee identifiers
The year-to-date figures, which catch a drift the period misses
Every figure here should be authorised by the contract or by law
A figure with no authorising term is the tell to query
This is the document that performs the promise, and can fail it

The two bands and the seam between them are the pages entire method compressed into one distinction, and its power is that it requires no payroll expertise — you do not need to understand the tax computation to know that a figure on the payslip which the contract does not authorise is a figure to query, and that a term in the contract which the payslip does not perform is a term to chase. The failure mode the split prevents is the well-meaning one: a reader who checks the payslip against itself (does the arithmetic add up?) rather than against the contract (is this figure authorised?), and so confirms a internally-consistent error — a wrong rate applied perfectly, every period. The discipline is to reconcile the two documents, pay attention to the year-to-date figures that catch a slow drift, and treat any unauthorised figure as the tell — because the promise is the reference and the performance is what you can check it against, and the seam where a wage goes wrong is almost always the seam where the two disagree.

The written-particulars rule — the file is the only thing, applied to employment. My manager said not to worry about that, we will sort it — so it is a term of my job. In many jurisdictions certain core terms must be set out in writing and given to you, and a term that is not written down is a term you will struggle to enforce, because the document is what the procedure and the tribunal read. This is the pages behavioural payload and the employment-specific form of the hold-the-thread guides central mechanic: 84 showed that a verbal promise is not a decision and the file is the only thing that exists; 91 shows that a verbal promise is not a term and the written particulars are the only thing the procedure reads. An oral assurance — the salary review that was promised in a corridor, the flexible hours agreed over coffee, the bonus "we will sort" — is not a term until it reaches the document, and the discipline is to ask for the promise in writing, confirm it by email so it reaches the record, and treat the written particulars as the authoritative account of what you were hired on.

And the reciprocal caveat, because the naive version causes real harm: the written particulars are not the whole contract. In many systems terms can also arise from the law, from a collective agreement, from an implied term, or from a documented custom, and the written statement is a floor rather than a ceiling — so a term absent from the written particulars is not automatically nonexistent, and a term present in them is not automatically enforceable if the law overrides it. The rule is jurisdiction-specific and belongs to your employer, the labour authority, a union, and a solicitor. The durable discipline is narrower and safer than either extreme: get the promise in writing, because the document is what the procedure reads, and ask before you assume in either direction.

The hours-and-rate arithmetic check — the one calculation every reader can do. Whatever else on a payslip requires the tax authority to interpret, the top of the waterfall is plain arithmetic, and it is the check that catches the most common quiet error — the wrong multiplier on overtime, the omitted premium, the hours mis-keyed.

hours worked × your rate + overtime hours × the contract overtime rate + any shift premium or allowance = gross pay

If the gross figure on the payslip does not match the hours you recorded times the rates your contract states, the error is at step 1 of the waterfall — and because every later step is computed on the gross, a step-1 error propagates silently through tax, insurance, pension, and net. The discipline is to keep your own hours record (the chronology the grievance guide builds, applied to time) and to check the multiplication before you check anything else, because it is the one line of the payslip that needs no expert to verify.

The overtime and premium rates, the minimum-wage treatment, and what counts as working time are set by your contract and by the law, and both are jurisdiction-specific — confirm them with your employer, the labour authority, a union, or a solicitor. The page teaches the arithmetic check, not the rate.

The deduction-lawfulness tells — what to query, framed as questions rather than accusations

a deduction your contract does not authorise a deduction taken without the prior written agreement the rule requires a rate that does not match the contract hours that do not match your own record a premium the contract promises and the payslip omits a deduction computed on the wrong base in the waterfall a year-to-date figure that drifts from the period figures a recovery of an overpayment taken in one lump a deduction for a shortage or loss without a contractual term a benefit-in-kind charge that does not match the scheme

The tells are the questions that a promise-versus-performance reconciliation surfaces, and the discipline is to read them as queries to payroll rather than as accusations to your manager — because an unauthorised deduction is often a configuration error in the payroll system that corrects next period, and a missing premium is often a timesheet that did not post. No single tell is a verdict; the pattern across the waterfall and the two documents is the signal, and the signal is the same one the bill and record-correction guides taught: read the mechanism, not the net. And the reciprocal limit again: checking is not refusing — a queried deduction may turn out to be lawful and authorised, and the discipline is to query the line, not to withhold your work or your trust over it.

The Payslip Anatomy

Each Column, Its Vector, and Its Check

A payslip is a small set of columns, and each one is a seam the hurried reader can miss — and each has a check that, read against the contract and the waterfall, reveals the error. The anatomy below walks the columns in the order the waterfall steps down, and for each names what the column can do and what to check. No single row is a verdict; the pattern across rows is the signal.

The period and the pay date

The vector

A contract that refers to procedures you have never seen, so the process you will be governed by is invisible until it is used.

The check

Ask for the disciplinary and grievance procedure documents now, while nothing is wrong; they are the map the grievance guide walks, and reading them cold is far easier than reading them in a hearing.

Clause	What it can hide	The tell	What to check
Dates	Understated continuous service	Start date does not match your record	Confirm the continuous-employment date
Pay / deductions	Omitted premium rates	The contract is silent on a figure the payslip uses	Get the rates in writing
Hours / mobility	A looser clause than the arrangement	The flexible deal is not in the clause	Read the clause against the reality
Holiday / sickness	A term below the statutory floor	The payslip computes on the wrong basis	Confirm which applies with the authority
Pension	A level that does not match the deduction	Contract and payslip disagree	Match the level to the deduction
Procedures	A process you have never seen	The contract refers to unseen documents	Ask for them now, while nothing is wrong

The contract anatomy is the same claims-vs-mechanism habit applied to the promise end of the seam: a clause is not evidence of your terms, it is the text that the payslip performs and the procedure applies, and the gaps — the silent premium rate, the loose mobility clause, the referred-but-unseen procedure — are the seams where a dispute later starts. The discipline is to read the contract as the reference document rather than as a formality to sign: confirm the dates, get the premium rates in writing, read the hours and mobility clauses against the reality you agreed, match the pension level to the deduction, and ask for the disciplinary and grievance procedures now, while nothing is wrong — because reading the map cold is infinitely easier than reading it in a hearing, and the grievance guide you will one day need begins with a document you should already have in your file.

A worked example: the two payslips, and the one that was reconciled to the contract

Concretely, the gross-to-net waterfall, the promise-versus-performance seam, the written-particulars rule, the hours-and-rate check, the deduction-lawfulness tells, and the two anatomies meeting two workers with the same quiet error. A warehouse operative and an office manager each receive a payslip that looks fine, and each has, for several months, been paid on a rate that does not match the contract.

Payslip one is accepted at the net and the drift compounds. The operative reads the net figure, sees it lands, and stops. The contract states an overtime multiplier; the payroll system was configured with a different one, and the gross at step 1 of the waterfall has been computed on the wrong rate for four months. Because the error is at the top, every later step — tax, social insurance, the pension base — is internally consistent and quietly wrong, and the year-to-date column would have shown the drift, but the year-to-date column was never read. Separately, the manager once said in a corridor that the weekend premium "would be sorted"; it never reached the written particulars, so there is no term to perform and no document for the procedure to read. The loss is not a stolen wage; it is a quiet one, repeated every period, concealed by a net figure that looked finished and a promise that never reached the document.

Payslip two is reconciled to the contract and the error is caught at step 1. The same kind of slip, the same manager, the same corridor promise — but this worker does the arithmetic first: hours record times contract rates, and the gross does not match. The error is at the top of the waterfall, so the query goes to payroll about the rate, not about the net, and the configuration is corrected and the arrears computed. Then the waterfall is read in order — the pension contribution confirmed as taken before tax where the rule says it should be, the loan deduction confirmed as authorised by a term, the year-to-date figures checked against the sum of the periods so a slow drift cannot hide. And the corridor promise is chased in writing: an email confirming the weekend premium, which reaches the record and becomes a term the payslip can be checked against, rather than a memory the procedure cannot read.

The lesson is the whole page. Both workers had the same quiet error and the same unwritten promise; the difference was not the employer but the reconciliation. Payslip one read the net and stopped, so a step-1 error propagated silently through every later figure and an oral promise never became a term; payslip two did the gross arithmetic first, read the waterfall in order, checked the year-to-date for drift, and got the promise into writing — and the error was caught at the top, where it was cheap to fix, rather than at the net, where it had already compounded. The promise-versus-performance seam is where a wage goes wrong, the waterfall is the mechanism the net conceals, and the written particulars are the only thing the procedure reads. Checking is not refusing: payslip twos query was a question to payroll, not a withdrawal of work, and the payslip it queried was, in the end, mostly right — which is exactly the point. The most common loss is the quiet one you never checked, and the discipline is to lay the narrow strip across the wide sheet and read the sequence.

The Check

A Sensible Default

Hold the thesis: the contract is the promise and the payslip is the performance, and the error lives where they disagree — reconcile the two documents, do not check the payslip against itself.
Read the gross-to-net waterfall in order: the deductions are sequential, each computed on the base the one before left, so the net is the output and the sequence is where the error hides.
Do the hours-and-rate arithmetic first: hours record times contract rates equals gross; a step-1 error propagates silently into tax, insurance, pension, and net.
Query the deduction-lawfulness tells as questions to payroll, not accusations to your manager: every deduction needs a contract term, a legal basis, or your written agreement.
Obey the written-particulars rule: get the promise in writing and confirm it by email so it reaches the record — a verbal assurance is usually not a term the procedure can read — but remember the written statement is a floor, not a ceiling.
Read the year-to-date figures, not only the net: they are the only place a slow multi-period drift becomes visible.
Respect the non-adversarial limit: checking is not refusing — most payroll is right, a queried deduction may be lawful, and stopping work over a query is a different failure from querying a line.
Route the specifics out: the payslip entitlement, the written-particulars list, the lawful-deduction rules, the minimum-wage treatment, and the tax computation are jurisdiction-specific and belong to your employer, the labour authority, the tax authority, a union, and a solicitor — not this page.

The honest takeaway is that the most common wage loss is not a dramatic theft but a quiet, repeated, internally-consistent error that a single net figure conceals — so the discipline is the reconciliation: do the gross arithmetic first, read the waterfall in order because the deductions are sequential rather than parallel, ask what authorises every deduction, read the year-to-date for drift, get the verbal promise into writing, and lay the narrow strip across the wide sheet to check that the performance matches the promise. For the two-documents-reconciled discipline this page transplants, see our read-a-hospital-bill guide; for the field-decoder habit it applies, see our spec-sheet, read-a-listing, manifesto-reading, official-letter, and record-correction guides; for the written-particulars rule it inherits, see our hold-the-thread guide; for the procedure the contract refers you should ask for now, see our raise-a-grievance guide; for the pension portability and the final-pay check that follow a payslip, see our leave-a-job guide; and for the actual payslip entitlement, written-particulars list, lawful-deduction rules, minimum-wage treatment, and tax computation for your place, see your employer or payroll, the national labour authority, the tax authority, a union, and a solicitor — the authorities this page keeps routing you to, because the shape of the waterfall is durable, the specifics are not ours to assert, and the quiet error is the loss the page exists to catch.

A small staircase of four unmarked wooden blocks descending in height from largest to smallest beside a single plain blank paper sheet, on a clean light surface — The small staircase of four unmarked blocks descending from largest to smallest, beside a single blank sheet, is the gross-to-net waterfall made physical: each step is a deduction coming off the base the step before left, and the blank sheet is the single net figure that shows you only the bottom of the staircase. The blocks stay unmarked and descending on purpose — the lesson is that the deductions are ordered rather than parallel, so the sequence is the mechanism the net conceals, and the error hides at the step where the base changed.

Common Questions

Frequently Asked Questions

How do I check my payslip is right?

By reconciling it to your contract line by line and reading the waterfall in order. Start at gross pay and check the arithmetic — hours times rate, plus any overtime or shift premium, should give the gross figure. Then follow the deductions in sequence, because each one reduces the base the next is calculated on, and check that every deduction is authorised by your contract or by law. An unauthorised deduction, a rate that does not match the contract, or hours that do not match your record are the tells. The payslip entitlement, the lawful-deduction rules, and the minimum-wage treatment are jurisdiction-specific and belong to your employer, the labour authority, a union, or a solicitor.

What is the gross-to-net waterfall?

It is the order in which the deductions come off your pay, and it matters because the deductions are sequential, not parallel — each one is calculated on the base that remains after the one before it, so the sequence changes the amount. Gross pay, then the deductions that reduce the taxable base, then tax and social insurance on what remains, then pension and any voluntary schemes, then the net figure you receive. A payslip shows you only the net; the waterfall is the mechanism it conceals, and reading it in order is how you spot a deduction taken from the wrong base.

My employer promised something verbally that is not in my contract. Is it a term?

Usually not in a way you can rely on, and this is the written-particulars rule. In many jurisdictions certain core terms must be set out in writing and given to you, and a term that is not written down is a term you will struggle to enforce, because the document is what the procedure and the tribunal read. An oral assurance — do not worry about that, we will sort it — is not a term until it is in writing. The discipline is to ask for the promise in writing, confirm it by email so it reaches the record, and treat the written particulars as the authoritative account of what you were hired on.

Can my employer deduct anything it likes from my pay?

No, and the limit is the tell. In most systems an employer may deduct only what your contract authorises, what the law permits, or what you have agreed in writing — and a deduction outside those is the unauthorised-deduction tell to query with payroll and, if it stands, to raise through the procedure. But the rule is jurisdiction-specific: what may be deducted, for what, and with what notice varies, and some deductions are lawful only with prior written agreement. The discipline is to check each deduction against your contract and the law, not to assume either that all deductions are lawful or that none are.

The net figure looks wrong. Should I stop working until it is fixed?

No, and this is the non-adversarial limit the page stands on. Checking is not refusing: a queried figure may turn out to be lawful and correct, and withdrawing your work over a pay query is a different failure from raising one — in many jurisdictions it can itself be a disciplinary matter. The discipline is to query the line with payroll in writing, quoting the contract term and the period, keep your own dated copy, and if the error stands, raise it through the grievance procedure our grievance guide explains — not to stop. The most common loss is the quiet error nobody checked, and the remedy is the check, not the strike.

I am paid in cash, or under a zero-hours or gig arrangement. Does any of this apply?

The discipline applies more, not less, and the route-out is sharper, because these arrangements are where the written-particulars gap and the hours-and-rate error are hardest to check and where the legal classification — worker, employee, self-employed, or something between — most affects what you are owed. The arithmetic check still works: keep your own record of hours and rates and reconcile what you were paid against what was agreed. But the rights that attach to your arrangement are jurisdiction-specific and often contested, and the classification question — which determines whether the payslip, minimum-wage, and deduction rules apply to you at all — belongs to the labour authority, a union, and a solicitor, not to a guide page. The discipline is the same; the authority you route the classification to is the one that matters most here.

My payslip has no detail at all — just a net figure. Is that allowed?

In many systems a payslip must show certain items — the gross and net, and the amounts and purposes of the deductions — and a bare net figure would not meet that standard, but the exact list is jurisdiction-specific and belongs to the labour authority and your employer, not to a guide page. The practical discipline does not depend on the rule: if the payslip will not show you the waterfall, ask payroll for the breakdown in writing, because you cannot reconcile the performance to the promise without seeing the steps. A refusal to provide the breakdown is itself information — it is the tell that the reconciliation will have to happen through the procedure rather than through payroll, and that is the route our grievance guide walks.

Ask our AI. Holding a payslip you cannot reconcile? Tap the chat icon and tell us the contract terms, the hours, and the figures, and it can walk the waterfall with you, do the gross arithmetic first, and flag the deduction-lawfulness tells as questions for payroll — and it will always route the payslip entitlement, the written-particulars list, the lawful-deduction rules, the minimum-wage treatment, and the tax computation to your employer, the labour authority, the tax authority, a union, and a solicitor, never asserting a rate or a rule itself, because the shape of the waterfall is durable and the specifics are not ours to assert. It will not tell you your employer is wrong; it will tell you to lay the narrow strip across the wide sheet and read the sequence.

More work & pay guides like this

We treat the most common wage loss as a quiet, repeated, internally-consistent error that a single net figure conceals, and the defence as the reconciliation: do the gross arithmetic first, read the waterfall in order because the deductions are sequential rather than parallel, ask what authorises every deduction, and check that the performance matches the promise — because checking is not refusing.

Explore All Guides