# UK £500 allowance: PRD-500

The People Team Handbook · Heddle · Revised 18 November 2026

Canonical: https://thepeopleteamhandbook.xyz/articles/payroll-correction-closure-case/#uk-500-allowance

<div id="payroll-review-case"><p><strong>PRD-500: an eight-person UK payroll with a £500 gross allowance omitted.</strong> This second illustrative case uses stated BR tax-code, category-A NI and pension inputs. Keep it separate from PH-CLOSE-1 above, whose £300 example deliberately supplies invented payroll outputs. Here the £500 change produces £340 extra employee cash and £590 extra employment cost.</p><p>For the urgent case, keep the current legal employer responsible for correction. The future supplier decision turns on whether approved inputs repeatedly disappear or client approvals arrive late.</p>
<section id="payroll-review-calculation"><h3>£500 gross becomes £340 net in this case</h3><p><strong>Illustrative operating case, not a customer result.</strong> Employee A is a non-director aged 30 in England, monthly paid, NI category A, with an HMRC-issued BR tax code. The pension scheme uses net pay, with employee 5% and employer 3% on all gross earnings including the allowance. No student/postgraduate loan, attachment, salary sacrifice, benefits adjustment or other deduction applies. All amounts are GBP; no conversion occurs. These inputs are not defaults for a real employee.</p><div class="payroll-review-table-scroll" tabindex="0" role="region" aria-label="Illustrative September 2026 payroll recalculation"><table><caption>Illustrative September 2026 payroll recalculation</caption><thead><tr><th scope="col">Affected employee</th><th scope="col">Draft</th><th scope="col">Corrected</th><th scope="col">Change</th></tr></thead><tbody><tr><th scope="row">Gross pay</th><td>£3,000.00</td><td>£3,500.00</td><td>£500.00</td></tr><tr><th scope="row">Employee pension: 5% full gross, net pay</th><td>£150.00</td><td>£175.00</td><td>£25.00</td></tr><tr><th scope="row">PAYE taxable pay</th><td>£2,850.00</td><td>£3,325.00</td><td>£475.00</td></tr><tr><th scope="row">PAYE: BR at 20%</th><td>£570.00</td><td>£665.00</td><td>£95.00</td></tr><tr><th scope="row">Employee NI: category A</th><td>£156.16</td><td>£196.16</td><td>£40.00</td></tr><tr><th scope="row">Net pay</th><td>£2,123.84</td><td>£2,463.84</td><td>£340.00</td></tr><tr><th scope="row">Employer NI</th><td>£387.45</td><td>£462.45</td><td>£75.00</td></tr><tr><th scope="row">Employer pension: 3% full gross</th><td>£90.00</td><td>£105.00</td><td>£15.00</td></tr><tr><th scope="row">Employment cost before service/other costs</th><td>£3,477.45</td><td>£4,067.45</td><td>£590.00</td></tr></tbody></table></div><p>Employee NI = (gross − £1,048) × 8% here, with both totals below the £4,189 monthly upper limit. Employer NI = (gross − £417) × 15%. Net = gross − employee pension − PAYE − employee NI. Thus £500 − £25 − £95 − £40 = <strong>£340</strong>. Employer cost change = £500 + £75 + £15 = <strong>£590</strong>. Employment Allowance, levy allocation, benefits, provider fees and VAT treatment are outside this incremental model; actual invoice treatment must be checked.</p><p>Rate basis: <a href="https://www.gov.uk/guidance/rates-and-thresholds-for-employers-2026-to-2027">Rates and thresholds 2026–2027</a>; <a href="https://www.gov.uk/tax-codes/what-your-tax-code-means">BR tax-code meaning</a>. Pension treatment: <a href="https://www.gov.uk/tax-on-your-private-pension/pension-tax-relief">Tax relief on pension contributions</a> and <a href="https://www.gov.uk/workplace-pensions/what-you-your-employer-and-the-government-pay">Pension contributions</a>. Replace the model with the legal employer’s payroll calculation when applying it: a tax-code change, loan, different pension basis or threshold crossing changes net pay. For example, changing the base gross to £4,100 and corrected gross to £4,600, with all other inputs unchanged, gives £364.66 extra net because part of the change crosses the NI upper limit.</p><p><a href="/assets/cases/payroll-review/assets/payroll-case.csv" download>Download the calculation CSV</a> · <a href="/assets/cases/payroll-review/assets/payroll-case.json">Read the complete case inputs and outputs</a> · <a href="/assets/cases/payroll-review/assets/payroll-model.mjs">Inspect the calculation code</a></p></section>
<section id="payroll-review-closure"><h3>From the draft omission to a closed record</h3><div class="payroll-review-table-scroll" tabindex="0" role="region" aria-label="Completed fictional correction record — before payment and reporting"><table><caption>Completed fictional correction record — before payment and reporting</caption><thead><tr><th scope="col">Date / record</th><th scope="col">Owner</th><th scope="col">Completed illustrative result</th></tr></thead><tbody><tr><th scope="row">15 September · INPUT-15</th><td>Client HR / manager</td><td>£500 taxable, pensionable one-off allowance approved and received at 14:00 UK time. Receipt includes all eight employees. Agreed cutoff is 16 September, 17:00 UK time. These are case assumptions, not any provider’s calendar.</td></tr><tr><th scope="row">21 September · DIFF-21</th><td>Provider payroll specialist</td><td>Draft omits the approved allowance for employee A. Remaining seven records match approved inputs. Intake logs show provider mapping lost this item; provider omission established. No bank file released; no FPS sent.</td></tr><tr><th scope="row">22 September · CALC-02</th><td>Payroll specialist + employer approver</td><td>Recalculate as below. Approver accepts revised £2,463.84 net for A; cohort gross moves £24,000 → £24,500. All seven other employees unchanged. Superseded draft and bank file are marked void.</td></tr><tr><th scope="row">23 September · FUND-590</th><td>Client finance / provider finance</td><td>£590 incremental employment cost approved and allocated from funded payroll cash. No separate emergency transfer requested. Funds are available to the paying employer, not merely present in a client bank account.</td></tr><tr><th scope="row">30 September · FPS-REG-06</th><td>Legal employer payroll operator</td><td>Corrected ordinary FPS sent before payday payment; recorded submission accepted. Taxable pay in period £3,325; taxable YTD £17,575 and PAYE YTD £3,515, assuming five prior months at the original figures. No earlier report existed to correct.</td></tr><tr><th scope="row">30 September · PAY-A-01 / RCPT-A-01</th><td>Employer payment operations</td><td>One £2,463.84 net payment settled; employee confirms receipt. Rejected or reversed payments: none. Revised payslip PS-A-02 delivered. No separate £500 or £340 transfer is made in this before-release branch.</td></tr><tr><th scope="row">22 October · REMIT-06 / INV-02</th><td>Employer payroll / finance</td><td>Model HMRC remittance includes incremental £210 (PAYE £95 + employee NI £40 + employer NI £75); pension remittance includes £40 (£25 + £15). Finance matches the incremental £590 bill to these obligations and £340 extra employee cash. No correction service charge in this assumed agreement.</td></tr><tr><th scope="row">30 October · NEXT-01</th><td>Provider payroll operations lead + client HR</td><td>Mapping control now compares every approved adjustment ID with payroll output. Next run confirms one-off allowance is not paid again. Employee explanation and finance reconciliation complete; no residual exception. Case closed in the model.</td></tr></tbody></table></div><p>The employee message in this fictional packet reads: “The approved £500 gross allowance was missing from the draft. Your corrected payslip shows £3,500 gross, £175 pension, £665 PAYE and £196.16 NI: £2,463.84 net. Your receipt confirms that amount. The allowance is one-off and will not repeat next month. If the figures or payment differ from your records, reply through the secure payroll case so we can reopen it.” Employee confirmation does not waive rights.</p></section>
<section id="payroll-review-reporting"><h3>Choose the HMRC route from what actually happened</h3><div class="payroll-review-table-scroll" tabindex="0" role="region" aria-label="Payment stage and reporting stage are separate inputs"><table><caption>Payment stage and reporting stage are separate inputs</caption><thead><tr><th scope="col">Observed state</th><th scope="col">Correct action</th><th scope="col">What closes this branch</th></tr></thead><tbody><tr><th scope="row">Draft only; no payment and no FPS</th><td>Recalculate and approve replacement run; submit the correct ordinary FPS on/before payday.</td><td>Corrected payment received, normal reporting receipt, payslip and invoice reconcile.</td></tr><tr><th scope="row">Already paid too little</th><td>Pay the calculated shortfall. HMRC’s underpayment route calls for an additional FPS on/before that payment, period differences, updated YTD and reason H.</td><td>Incremental net received; correct report submitted; totals and invoice reconciled.</td></tr><tr><th scope="row">Paid correctly; FPS figures wrong</th><td>For current-tax-year wrong pay/deductions, HMRC directs corrected YTD in the next regular FPS. Do not make another wage payment for a reporting-only error.</td><td>Reported totals reconcile to actual payments; other field errors use their own guidance.</td></tr><tr><th scope="row">FPS sent early; employee not yet paid</th><td>Use HMRC’s advance-report correction branch for the affected tax month, revising YTD as necessary.</td><td>Reporting reconciles before treating the case as closed; do not assume “unpaid” means “unreported”.</td></tr><tr><th scope="row">Approval late; allowance only becomes due next cycle</th><td>Confirm entitlement/effective date with the employer. If genuinely due next cycle, enter it there; do not backdate approval or manufacture an error.</td><td>Next-cycle ordinary pay/reporting completed. If pay was already legally due, resolve that underpayment despite the client’s missed cutoff.</td></tr></tbody></table></div><p>Sources: <a href="https://www.gov.uk/payroll-errors/correcting-pay-or-deductions">underpayment and deduction corrections</a>; <a href="https://www.gov.uk/payroll-errors/correcting-your-fps-or-eps">FPS/EPS field and advance-report corrections</a>; <a href="https://www.gov.uk/running-payroll/reporting-to-hmrc">ordinary reporting</a>. The employer’s payroll operator selects the fields in its software and retains the submission result. A submission receipt is not an HMRC audit clearance.</p></section>
<section id="payroll-review-reversals"><h3>Change the input before changing the provider</h3><div class="payroll-review-table-scroll" tabindex="0" role="region" aria-label="Two changed inputs, two different outcomes — synthetic dates and records"><table><caption>Two changed inputs, two different outcomes — synthetic dates and records</caption><thead><tr><th scope="col">Input changed</th><th scope="col">Completed alternative path</th><th scope="col">Buying decision / prevention owner</th></tr></thead><tbody><tr><th scope="row">Original £2,123.84 already paid at 09:00 on 30 September; lower FPS also sent</th><td>At 10:00 detect omission. Employer recalculates the same monthly earnings period and approves £340 net. Additional FPS before the 14:00 top-up records £475 taxable pay difference, £95 PAYE difference, updated taxable YTD £17,575 / PAYE £3,515 and reason H; payroll software supplies all relevant NI fields. PAY-A-02 settles £340 at 15:00, confirmed by RCPT-A-02. Employee total is £2,463.84.</td><td>Provider omission still supports the replacement case if recurring. Finance records the same £590 incremental cost once, not £590 plus the £340 transfer. Provider operations owns prevention; a fee is reconciled separately under agreed terms.</td></tr><tr><th scope="row">Approval arrives 17 September, after the assumed cutoff; discretionary allowance is confirmed due in October</th><td>Employer confirms October entitlement; HR informs employee on 18 September. No September underpayment or corrected FPS is created. October inputs include £500 once; 30 October ordinary payroll pays £2,463.84 under the same unchanged model assumptions and reports the October amounts. Employee confirms receipt; invoice adds £590 once.</td><td>Retain the incumbent and fix approval timing. Client HR owns a 14 September reminder, delegated approver and cutoff exception list. Provider confirms acceptance and due cycle. If entitlement had already been September, the employer must remedy the overdue pay instead.</td></tr></tbody></table></div><p>If the extra payment returns, reopen payment operations and trace the return before authorising a replacement. If reporting is still pending, record “paid; reporting open”. If only a service fee is disputed, keep that commercial item open separately; do not claim the whole account reconciles. A £40 proposed fee with a £40 credit merely promised leaves £40 unresolved until the credit is actually applied.</p></section>
<section id="payroll-review-invoice"><h3>Reconcile the invoice without paying the correction twice</h3><p>The before-release case’s original employment-cost line is £3,477.45 for A. Its replacement is £4,067.45, a £590 increase. Finance either replaces the original line or records a £590 adjustment against it; it does not add another full £4,067.45. In the already-paid branch, £340 is the employee destination within that £590 obligation. The remaining £250 funds tax, NI and pension destinations. The seven other employee lines and agreed service fees must reconcile independently.</p><p>Before closing, match input ID → corrected payroll version → employer approval → available funding → bank receipt → payslip/FPS → remittances → invoice adjustment → employee explanation → next-cycle prevention. Missing proof keeps its stage open. A provider change is not a reason to leave the old employer’s statutory records or employee underpayment unresolved.</p></section>
<section id="payroll-review-checker"><h3>Try the completed case and the reversals</h3><p>This checker reproduces the fixed illustrative case and tests your selected evidence states. It does not calculate a real employee’s tax, verify documents or send payments. Nothing is saved or uploaded; changing a selection only changes this page.</p><p>Use the interactive checker in the canonical case; selections are not saved.</p></section>
<section id="payroll-review-choice"><h3>Buy the repair through to completion</h3><div class="payroll-review-table-scroll" tabindex="0" role="region" aria-label="Choose against the cause of this exception"><table><caption>Choose against the cause of this exception</caption><thead><tr><th scope="col">Route</th><th scope="col">Why it fits this failure</th><th scope="col">The condition that changes the choice</th></tr></thead><tbody><tr><th scope="row">Teamed — our replacement pick</th><td>For repeated provider omissions: <a href="https://www.teamed.global/customer-service">published repair ownership and designated cover</a> connect the issue to a person responsible for taking it forward. <a href="https://www.teamed.global/technology">Logged actions and payroll checks</a> support traceability.</td><td>Agree the UK correction owner, payroll/reporting authority, funding deadline, employee update and closure evidence. Support access is not a settlement deadline; charges and remedies need explicit terms.</td></tr><tr><th scope="row">Remote — retain a capable incumbent</th><td><a href="https://support.remote.com/eor/employee-payroll/does-an-off-cycle-payroll-run-always-incur-a-cost">Remote covers off-cycle processing caused by its own error</a>. This is a substantive remedy for the same omitted input.</td><td>Stay if its UK team completes the packet and prevents recurrence. <a href="https://support.remote.com/eor/employee-payroll/what-is-the-payroll-cutoff">Late approvals follow different cutoff rules</a>; do not present that restriction as a refusal to fix Remote’s own mistake.</td></tr><tr><th scope="row">Deel — repair approval controls first</th><td><a href="https://help.letsdeel.com/hc/en-gb/articles/4407745487761-How-Clients-Can-Add-Expenses-and-Manage-Adjustments-for-Their-Workers">Its documented adjustment workflow</a> exposes pending items, editing before cutoff and approved/pending reports. This can show whether the instruction was ready in time.</td><td>Retain Deel if the evidence identifies late client approval and controls solve it. EOR and direct-payroll settings differ. A report of an approved item is not proof of payment.</td></tr><tr><th scope="row">G-P — keep a wider programme coherent</th><td><a href="https://www.globalization-partners.com/globalpedia/united-kingdom/">UK EOR service</a> and <a href="https://www.globalization-partners.com/pricing/">payroll and reporting scope</a> make it relevant where the eight people belong to an existing G-P programme.</td><td>Use the same closure packet to agree the UK repair owner. The reviewed product scope does not settle a case-specific correction deadline or charge; unknown is not unavailable.</td></tr><tr><th scope="row">Direct employer / existing payroll bureau</th><td>If your UK entity already employs these people, retain employer authority and assign its payroll specialist and treasury team to repair the run.</td><td>An EOR is not needed merely to fix one allowance. Changing payroll supplier does not transfer the legal employer’s duties.</td></tr></tbody></table></div><p>Teamed provides <strong>24/7 human support</strong>. That access supports escalation; the reason for our bounded preference is responsibility for taking provider-caused payroll work forward. Its UK service is <a href="https://www.teamed.global/country-hiring-guides/united-kingdom">published here</a>. No provider’s marketing establishes the bank’s settlement time. Use this case to agree the correction path and keep the incumbent responsible until any lawful, funded transfer is complete.</p></section>
<p>Use the payment and FPS state to select the correction path, then test prevention in the next cycle. <a href="https://eor-truth.com/guides/check-eor-fx-invoice/#uk-payroll-correction-590">Reconcile the £590 supplier adjustment and any unapplied service credit</a>. <a href="https://thepeopleteamhandbook.xyz/articles/payroll-correction-closure-case/#prd-500-sources">Read the PRD-500 sources</a>.</p></div>