A payroll manager in Manchester changes one tax code in month nine. The code moves down. The next payslip shows income tax several hundred pounds higher, and the employee is on the phone by lunchtime asking who broke payroll.
Nobody broke payroll. The UK operates PAYE cumulatively, so the new code was applied against the employee’s year-to-date position, not month nine in isolation. Eight months of under-withholding arrived in one period, exactly as designed.
Run the identical change in the Netherlands, or in Ohio. Nothing reaches backwards. The new instruction takes effect from the period you entered it and the closed periods stay closed.
Same input, same intent, different arithmetic, because the two countries do not agree what a pay period is for tax purposes. Load every rate table for sixty countries and you can still produce wrong net pay.
The UK keeps two different memories on the same payslip
What is the cumulative basis?
Each period’s tax is calculated on the year’s running totals rather than on that period alone. HMRC’s PAYE manual puts it plainly: the employer “takes into account any previous pay and tax for the year.” What you deduct is the difference between tax due to date and tax already deducted. The result can be negative, so a cumulative code can issue a refund inside a live payroll run, a concept many non-UK systems have no field for.
Week 1/Month 1 switches that memory off. Same code number, but as HMRC puts it, “it ignores previous pay and tax. In effect all payments are taxed as though it was week 1 or month 1.” You apply it on an emergency code such as 1257L W1/M1 for a starter with no P45, which is why one employee on one salary can show two different tax deductions depending on a suffix your engine either honours or quietly drops on import.
Then National Insurance sits on that same payslip and behaves the opposite way, assessed on each earnings period on its own. For 2026/27 the monthly primary threshold is £1,048, the upper earnings limit £4,189, the employee main rate 8 percent with 2 percent above the UEL, and the employer rate 15 percent above a secondary threshold of £417. Pay a £12,000 bonus in one month and NI lands at that month’s banding, permanently. The income tax on that bonus keeps self-correcting until April. The NI does not.
Two memories, one payslip. An engine with a single state model gets one of them wrong.
India asks you to withhold against a forecast
Section 192 of the Income-tax Act 1961 requires the employer to deduct TDS on salary at the average rate of income tax computed on the estimated income for that financial year. The year runs April to March. So in April, with eleven months of unknowns ahead, the engine builds a full-year projection: annual salary, Section 10 exemptions such as HRA, the standard deduction, Chapter VI-A deductions, a comparison of old and new regimes, and the employee’s investment declaration on Form 12BB. Then it spreads the projected liability across the remaining months.
Every input change therefore re-shapes the future rather than adjusting the past. An employee declaring an extra 80C investment in December gets no one-off December credit. The engine reprojects the year, recomputes annual liability, subtracts TDS already deducted from April through November, and redistributes the remainder across the four months left. One form moves four payslips.
It is why Indian payroll gets caught at the filing, not the payslip. Form 24Q goes in quarterly, and Annexure II in the Q4 return carries the full annual salary and deduction detail. A projection nobody ever trued up shows up there, not in month six.
Germany computes an annual tax and hands you a twelfth of it
German Lohnsteuer starts with tax class, I through VI, retrieved from ELStAM, the electronic wage tax deduction database. A married couple on classes III and V versus class IV with the Faktorverfahren withholds materially different amounts on identical household gross.
The calculation is annual in shape. Under § 39b EStG the engine projects period pay to an annual figure, computes the Jahreslohnsteuer, then apportions: one twelfth for a monthly period, 7/360 for weekly, 1/360 for daily. The statute even legislates the crumbs: fractions of a cent are disregarded. Rounding in Germany is not an implementation choice. It is statutory text.
Social insurance runs on its own ceilings, and there are two of them. In 2026 the Beitragsbemessungsgrenze for pension and unemployment insurance is €8,450 a month, €101,400 a year, while health and long-term care cap at €5,812.50 a month, €69,750 a year. Rates this year: pension 18.6 percent, unemployment 2.6 percent, health 14.6 percent plus a fund-specific Zusatzbeitrag the ministry set at an average of 2.9 percent for 2026, long-term care 3.6 percent. One unchanged salary crosses one ceiling in March and the other in September. It closes out in the Lohnsteuerbescheinigung, transmitted electronically by the last day of February with the 11-digit Steuer-ID. If monthly rounding drifted, that file is where it surfaces.
The US is per-period, with a stack underneath
Federal withholding has no year-to-date memory in the British sense. Publication 15-T offers methods driven by the employee’s Form W-4: percentage method tables for automated systems via Worksheet 1A, then wage bracket and percentage method tables for manual systems, each split between W-4s from 2020 or later and pre-2020 allowance-based forms. The Step 2 checkbox sends you to a different column entirely.
Worksheet 1A annualises: take the period wage, multiply by the number of pay periods, apply the annual tables, divide back down. Structurally that resembles Germany, with one decisive difference. It annualises this period as though it repeated all year. It never looks at what the previous eleven actually were.
Then the stack. Federal, plus state, plus local in a meaningful number of jurisdictions. Some state pairs have reciprocity, where, as PayrollOrg puts it, “the employer will only need to withhold for the state of residence, not the work state.” Where no agreement exists, both states may have to be considered, and New York among others applies a convenience-of-the-employer test that turns on days actually worked in state. That is not a rate lookup. It is a per-employee, per-day sourcing decision that resolves before withholding starts.
Brazil writes the order of operations into law, and the Netherlands hides it in a table
Brazil sequences it explicitly. INSS comes off first, progressive by band: for 2026, 7.5 percent up to R$1,621.00, 9 percent to R$2,902.84, 12 percent to R$4,354.27 and 14 percent to the ceiling of R$8,475.55, applied band by band so the effective rate always sits below the nominal top band. Only then do you build the IRRF base: gross less INSS, less R$189.59 per dependant, or the simplified deduction of R$607.20 where that helps more. The monthly table still exempts a base up to R$2,428.80, with brackets at 7.5, 15, 22.5 and 27.5 percent. Then Lei 15.270/2025 adds a fourth step from January 2026: a redutor zeroing the withholding up to R$5,000 a month and tapering to nothing by R$7,350, at R$978.62 less 0.133145 times taxable income. After the table, not inside it.
Reverse those two steps and you overwithhold income tax on the whole population. Every number is individually correct and every payslip is wrong. Then add the 13th salary, in two instalments, the first by 30 November with no deductions, the second by 20 December carrying INSS and IRRF computed on the 13th alone, not added to December’s regular pay. A second gross-to-net for the same person in the same month.
The Netherlands relocates the difficulty. Withholding depends on which table applies, white or green, and on whether the employee has asked in writing for the loonheffingskorting, the payroll tax credit only one withholding agent may apply at a time. Non-recurring payments go somewhere else again: the tabel bijzondere beloningen sets a percentage from the employee’s prior-year annual wage, and that published percentage already includes a verrekeningspercentage reflecting the phase-out of the employment credit. The bonus rate is not a bracket rate. It is a blended rate driven by last year’s income.
Japan carries the logic to its end: monthly withholding is provisional, and the real calculation is the nenmatsu chosei year-end adjustment at the last salary payment.
Why this decides your retro pay process and your engine
Retro pay in a cumulative country is an input, not a correction. Drop an April-effective increase into a UK November run and the calculation absorbs it: year-to-date taxable pay rises, tax due to date rises, tax already deducted comes off, the difference falls out in November. Nobody reopens April. NI is less obliging, and where arrears relate to earlier earnings periods you may have to recompute it period by period against those periods’ thresholds.
In a non-cumulative country the same retro pay is a genuine amendment. Either you treat it as current-period supplemental earnings, or you reopen closed periods and refile. Different files, different deadlines, different exposure. One business event, two incompatible handling paths, same close.
Which is why configuration on a rate table alone never holds. A rate table cannot express “recompute year to date and net off what was already withheld,” or “project the year, subtract eight months of actuals, spread the remainder across four,” or “INSS first, then dependants, then the table.” Those are code paths.
Rounding is where it gets expensive. Round German Lohnsteuer at the annual step instead of after apportionment and you are a cent out per employee per period. Across four thousand employees that is a €480 annual variance and a statutory file that will not reconcile. No employee ever queries it. The authority’s validator always does.
Which lands on the architecture question: one engine implementing each country’s logic natively, or local engines stitched together behind a shared portal. The stitched model can be accurate in every country and still leave you exposed: variance checks, approval gates and audit trail sit above the calculation rather than inside it, and every engine holds a private definition of a period. HR Blizz went the other way, with one native gross-to-net engine calculating in every country itself, generating statutory filings inside the run, India’s Form 24Q and New Zealand payday filing among them.
Three things to check on Monday
Pull one payslip per country from your last close and test the engine, not the output.
1. Recompute period four’s income tax using only period four’s data. If that matches the UK payslip, someone put your population on Week 1/Month 1 and did not tell you.
2. Ask your provider at which step the figure is rounded, and to what precision, separately for tax and each social contribution. If the answer runs longer than a sentence per country, the real answer is “wherever the code happened to land.”
3. Enter a backdated April increase in a test run for one cumulative country and one non-cumulative country. If the engine behaves identically in both, one of them is wrong.
Then find the last one-cent variance somebody wrote off as immaterial and check which statutory file it was sitting in. If you want to see what one native gross-to-net engine does across your real country footprint, ask the HR Blizz team to walk one of your countries end to end.
The country rules above are general information, not tax advice.
FAQ
Q: What does cumulative PAYE mean in UK payroll?
Cumulative PAYE means income tax is calculated each period on the employee’s year-to-date pay and tax rather than on that period alone. HMRC’s PAYE manual states the employer “takes into account any previous pay and tax for the year,” so a mid-year tax code change adjusts the whole year in one payslip and can even produce a refund inside a live run.
Q: Why is UK National Insurance calculated differently from income tax?
Class 1 National Insurance is assessed on each earnings period separately, so it is non-cumulative, while PAYE income tax is normally cumulative. For 2026/27 the monthly primary threshold is £1,048 with an upper earnings limit of £4,189, employee rates of 8 percent and 2 percent above the UEL. A one-off bonus is charged NI at that period’s banding and later periods do not correct it.
Q: How is TDS on salary calculated in India?
Under Section 192 of the Income-tax Act 1961, the employer estimates the employee’s total income for the April-to-March financial year, applies exemptions, the standard deduction and declared investments from Form 12BB, computes the annual liability under the chosen regime and spreads it across the remaining months. A declaration submitted in month nine causes the engine to reproject the year and redistribute the balance across the remaining payslips.
Q: Why does payroll rounding matter for statutory filings?
Because some countries legislate it. German § 39b EStG specifies how the annual wage tax is apportioned to the pay period and that fractions of a cent are disregarded. Rounding at the wrong step produces a one-cent per employee per period difference that no employee notices but that will fail reconciliation against annual statutory returns such as the Lohnsteuerbescheinigung.