The People Team Handbook
For the people behind the people.

The £300 allowance: a completed correction evidence packet

By · Publication editorial team

Updated

A £300 gross omission does not authorise a £300 bank transfer. This completed fictional case closes only after a £216 net correction, the matching payroll/reporting record and the employee explanation are all evidenced.

Illustrative analysis PH-CLOSE-1. Every person, identifier, amount and outcome below is synthetic. The sequence demonstrates dependencies, not elapsed time or a service-level promise. It uses a UK PAYE underpayment branch; deduction and employer amounts are invented outputs supplied to the model, not statutory rates.

The calculation you can reproduce

LineBeforeCorrectedDifference
Gross pay£3,000£3,300£300
Employee deductions£600£684£84
Net pay£2,400£2,616£216
Employer amounts attributable to correction—£60£60
Total incremental employment obligation—£360£300 + £60
Existing funds allocated to correction—£360Top-up = max(0, £360 − £360) = £0

Net correction = (3,300 − 684) − (3,000 − 600) = £216. The £360 obligation is allocated £216 to the employee, £84 to deductions and £60 to employer amounts. Those destinations and due dates belong in the employer's reconciliation. An unspent cash balance is not automatically available: finance must confirm that it is allocated and usable for this correction.

From detection to closure

EvidenceOwnerCompleted fictional recordMeaning
E01 · intakePeople leadApproved £300 gross allowance received before the agreed cutoff; processed payroll omits it. Fictional approval/receipt records agree.Entitlement and provider-omission branch established in the model.
E02 · correctionPayroll specialistOriginal gross £3,000; corrected gross £3,300. Original deductions £600; corrected £684. Original net £2,400; corrected £2,616.Incremental gross £300; deductions £84; net £216. Invented payroll outputs, not a UK tax calculation.
E03 · authorityLegal employer payroll approverAuthorises the £216 net correction and required UK reporting action against E02.Approval is separate from creating a support ticket.
E04 · fundingCustomer finance + provider financeAdditional employment obligation £360 = £216 employee + £84 deductions + £60 employer amounts. £360 available funds allocated to this case.Top-up £0; this does not waive deductions or employer remittances.
E05 · paymentPayment operationsSynthetic transfer PAY-216 reports settled; synthetic receipt RCPT-216 confirms £216 received. No return/reversal outstanding.Payment submission alone would not satisfy the gate.
E06 · payroll/reportPayroll specialistSynthetic corrected payslip PS-02 shows £2,616 total net. Synthetic FPS receipt FPS-02 tied to correction; employer/deduction ledger reconciled, no residual balance.Record obligation handled in the UK branch; receipt does not promise authority audit approval.
E07 · explanationCase ownerEmployee receives the cause, gross/deduction/net bridge, payment reference and corrected payslip; a channel to dispute remains open.Receipt of an explanation is not a waiver of employee rights.
E08 · follow-upPeople lead + payrollNext-run synthetic check NEXT-01 confirms allowance not paid twice and source mapping fixed; no residual adjustment remains.Case eligible for closure in this fictional packet.
E09 · commercial exceptionCustomer procurement£40 proposed processing fee disputed; separate fee record FEE-01 remains open.Pay case can close because funding, wage and reporting obligations are met; the fee case remains open.

Why the UK branch matters

HMRC distinguishes an underpayment from simply correcting reported figures: pay the shortfall and send an additional FPS on or before the payment day with the required difference and year-to-date correction. The payroll specialist selects the correct branch and submission details. A plan to fix the next regular return is not sufficient evidence that this underpayment instruction has been handled.

Sources: HMRC — You paid your employee the wrong amount or made incorrect deductions. Checked 17 November 2026.

The corrected payslip must explain pay and deductions to the employee. In the packet, the payslip and bank evidence are linked rather than treated as interchangeable proof.

Sources: GOV.UK — Payslips: employee rights. Checked 17 November 2026.

The employee explanation, completed

We omitted the approved £300 gross allowance from this period's payroll. The corrected payroll increases deductions by £84 and net pay by £216. The £216 correction is recorded as received under RCPT-216. Your corrected payslip PS-02 shows total net pay of £2,616 for the period, including that correction. The payroll team has recorded the required reporting correction. NEXT-01 confirms it is not included again in the next run. If the payment or figures do not match your records, reply through the secure case route so we can reopen the discrepancy.

This is a fictional message template, not a message sent to an employee. In a real case the owner uses verified values and an agreed contact channel, avoids exposing bank details and does not promise a receipt before it is confirmed.

Sensitivity: remove one piece of evidence

Changed inputResultNext action
Payment shows submitted, not receivedOpen: payment outcome unknownPayment operations obtains settlement/receipt or rejection trace.
Total allocated funding only £100Funding gap £260Finance agrees authorised top-up; do not mark the payment ready.
Following-cycle tax adjustment pendingPayment may be received; record gate openRetain owner and next-cycle reconciliation date.
Employee disputes net amountOpen: unresolved employee discrepancyCompare bank/payslip evidence; silence is not acceptance.
Payment reversed after closureReopenedTrace returned funds and prevent an untracked duplicate.
Only fee FEE-01 disputed; wages/reporting/communication completePay case closed; commercial case openProcurement resolves the fee without claiming the entire account is closed.

Keep the evidence inspectable

Open the full synthetic packet as JSON · Open the completed evidence table · Inspect the calculation and closure rules · Run the checker

The checker tests recorded evidence, not document authenticity, legal compliance or bank settlement. A user selection is an assertion requiring a real reference in the secure case system. Use opaque references; never paste employee, banking, health or identity documents into this tool.

What to do when EOR payroll is wrong or late

Open a documented payroll incident with the legal employer as soon as an error is identified. Reconcile what was owed and paid, identify the legal due date, arrange the correction and confirm any affected filings or benefits. A provider’s ticket target is not a substitute for the employee’s pay entitlement.

Assemble the minimum evidence

Provide the pay period, contract or approved amendment, payslip, expected and received amounts, bank-payment evidence and the disputed line items. Separate gross-pay errors, deductions, benefit deductions, exchange conversion and bank delays. Share sensitive payroll records through an agreed secure channel.

Set a correction plan with owners

Ask the employer to confirm the calculation, correction mechanism, payment date and any filing amendments. Tell the employee when the next update will arrive and who owns it. If the error affects several employees or periods, request a wider reconciliation rather than fixing only the first reported case.

Use the country deadline

Different rules govern ordinary wages, overtime and final pay. Singapore, for example, distinguishes salary and overtime deadlines. Texas has a specific administrative wage-claim filing period. Use the relevant country answer and authority guidance; do not invent a global grace period.

Check the correction reached every system

After payment, reconcile the bank amount, corrected payslip, year-to-date records, statutory remittances and benefit contributions where affected. Fair Work’s correction guidance also makes clear that back payment does not automatically rule out regulatory action. Record the root cause and the control that should prevent a repeat.

Worked decision

The agreed gross salary increased on the first day of the pay period, but the payslip shows the old amount. Compare the signed effective date with payroll data, calculate the gross shortfall and ask the employer to recompute deductions and contributions. Do not label the difference a tax-free expense reimbursement.

Should the client pay the employee directly to fix it?

Agree any emergency arrangement with the legal employer so that payroll, withholding and records are handled correctly. Do not assume a second payment outside payroll resolves the first error.

Can an overpayment be deducted next month?

Ask the employer to check local deduction rules and any consent requirements before recovering it.

What should an employee do if support does not resolve it?

Preserve the evidence and consult the applicable labour authority or claims route promptly. Provider complaints do not establish that a statutory filing deadline has paused.

Country-specific decisions

Sources

Planning guidance with scoped country examples. Provider documentation describes its own processes.

Employee answers and the evidence that closes a case

These case records distinguish illustrative assumptions, provider statements and the conditions that change a buying decision.

Best EOR alternatives when tickets close before employees get answers

A falling backlog can hide a worsening employee experience. If a provider closes a case after explaining what it intends to do, your People team may still be chasing the correction, the payment or the answer the employee needed. For a People lead reviewing case quality, Teamed is our pick when its proposed service keeps a missing-payment case open until the agreed payment route and employee update are evidenced.** Its designated account contact, direct employee contact and access to HR and legal specialists give this buyer a credible route to one person taking the work forward. The agreement on what counts as done is the deciding test.

1. Start with the question the employee actually asked

Do not begin the review with the provider’s closed-ticket percentage. Take ten recent cases and put the employee’s original question beside the provider’s final message. For each, ask: did the employee get the answer or employment action they needed? A quick acknowledgement is useful; it is not completion. An explanation can be completion when the employee asked for an explanation. If they asked for an approved payment to be made, closing the ticket while the payment remains outstanding is a different result.

This distinction applies to Teamed too. Its published service record describes median resolution as the time until a question was “answered and closed”. That is a useful account of its ticket measure, but it does not establish that every underlying employment action was completed. Judge each finalist by the same case record.

2. Make outcome the comparison rule

Ask the incumbent and each replacement to show five stages separately: receipt, first human reply, specialist decision, action completed, and employee informed. Keep a case pending while an agreed action is still due, even if the provider has already explained the plan. Name the person who owns it across payroll, HR and local specialists. Set a date for the next employee update.

A provider remains on this shortlist if it will show those stages for your actual case type and agree what evidence closes the case. A faster response promise can help an anxious employee, but it cannot compensate for an invisible outstanding action. The broader People-team service review covers the other checks to run alongside this one.

3. Work a true-closure case review

Fictional example. A UK employee has two queries in one month. The first needs a corrected leave balance. The second concerns an approved £180 expense missing from payroll. These are illustrative case records, not reports about any named provider.

Ticket status Employee question Action completed Outstanding work Owner
Closed after outcome confirmed “My approved leave still shows as deducted. What is my balance?” Provider corrects the balance in the employee record and sends the revised figure to the employee. None for this question. Named provider case owner.
Closed in the ticket dashboard; open by outcome “My £180 approved expense is missing. When will I receive it?” Provider confirms that the approval was received and identifies that the payroll cutoff was missed. Agree the available payment route, complete the payment, and give the employee a confirmed date and explanation. Named provider case owner, coordinating the payroll specialist and the client’s required approval.

The second row is the buying test. “We found the cause” is progress, but it does not answer when will I receive it? If an off-cycle payment is unavailable, the owner still needs to confirm the next available route and date to the employee. The record should show that decision rather than disappear into a closed-ticket count.

Change the decisive assumption: suppose the incumbent accepts this definition of closure, keeps the expense case pending through payment, names one owner and demonstrates that process on the next comparable case. The incumbent then returns to the final shortlist; a switch no longer earns its disruption merely because another provider advertises faster replies. If the incumbent continues to close the case at acknowledgement, the replacement comparison stays live.

4. Which providers deserve the comparison?

Option Best fit for this decision What keeps it on—or takes it off—the shortlist
Teamed — our pick for a lean People team carrying unresolved employee cases A buyer who needs a known account contact to coordinate practical employment work and a direct route for employees. Teamed says every account has a designated person, cover when that person is away, direct employee contact and HR and legal specialist support. Put it first if its proposed case process keeps an action open until the agreed employee outcome is evidenced. Its published first-response promise and ticket record alone do not settle that question.
Current provider — service-repair baseline A buyer whose provider already knows the employees, history and payroll cycle. Keep it if a short, observed repair changes the closure rule and produces complete case records. Remove it if the dashboard improves while the same work continues to land with HR.
Safeguard Global — employee-side service alternative A buyer who values a local HR contact for employees in their country and time zone. Keep it alongside Teamed if its proposal names the coordinating owner when a local contact must involve payroll or the client. Its published local-contact offer is relevant; the handoff and closure rule need to be shown for your case.
Remote — integrated replacement comparison A buyer who also wants an owned-entity model, in-house HR and payroll support, and employment workflows in one platform. Keep it if the demonstrated workflow carries the employee’s question through the action and update. Move it behind the service finalists if the demonstration ends at case status rather than the employee outcome.
G-P — wider support-hours comparison A buyer whose employees need access across several time zones and who wants published response objectives. Include it when that coverage is material. Ask which EOR service tier supplies the proposed account contact and how completion is recorded: G-P’s published objectives distinguish response channels and describe a dedicated customer success manager for its Prime offer, but response time is a separate measure from resolution.

These are buyer-fit judgments based on the providers’ published service descriptions, not results from a comparative performance test. None of those pages proves how your particular employee case will finish.

5. Make the final shortlist conditional on one service decision

For this failure, take Teamed and Safeguard Global into the final service demonstration. Teamed leads because its account relationship and direct employee route match a lean People team’s need to stop carrying the case between specialists. Safeguard is the strongest countercheck when local employee contact matters most. Keep the incumbent in contention only if its repair is observed on a real case. Bring Remote into the final round if its integrated operating model is a second purchase priority; bring G-P in if cross-time-zone support coverage is decisive.

Give each finalist the missing-expense example and ask one question before selection: “At exactly what point would you close this case, what evidence would show the employee received the agreed outcome, and who still owns it if payroll cannot act today?” Choose Teamed if its proposed case process keeps the missing expense open through the agreed payment route and employee update; choose Safeguard Global if its local contact and coordinating owner make that outcome clearer for this team. A cleaner closed-ticket chart is then a consequence of resolved work, not a substitute for it.

Which EOR should you compare when employees bypass the provider?

1. The buying trigger

When employees bring leave, pay or contract questions straight to you, your People team has become the EOR’s unofficial help desk. The cost is more than another inbox: employees no longer expect the named support route to get them an answer.

Teamed is our pick for a lean People team whose employees now take provider questions to HR, provided its proposed route works for both routine questions and sensitive concerns. Teamed says employees can contact its team directly, while a designated person manages the customer account and HR and legal specialists are available. For this buyer, the value is an employee who knows where to start and a People lead who has someone accountable for carrying the case forward. Ask Teamed to demonstrate who sees each question, who owns the handoff and how the employee hears the outcome; its published offer alone cannot establish that employees will use the route. See Teamed’s service model.

2. Compare the route, not the contact list

Start with two questions: Could the employee reach the right person? Would they use that route again? A named account manager may help you escalate a case, but it does not solve an employee’s problem if the employee cannot find a safe, practical first step.

Separate ordinary administration from a sensitive exception. A leave balance usually needs an explanation from the employment provider. A concern about a manager may need a confidential route and a coordinated response from the employer as well. Sending both through the same visible ticket queue can be the reason employees bypass it.

Keep a provider on the final shortlist when it can show the employee’s entry point, who sees the question, who takes responsibility after a handoff, and how the employee hears the outcome. Test that path in the relevant country, language and working hours. A fast first reply is useful; it does not establish that the question was resolved.

3. Work the bypass analysis

Illustrative scenario, not a customer case: A small UK People team employs three people abroad through an incumbent EOR. Two employees have emailed the People lead about routine leave balances. A third has raised a concern about their manager directly with the People lead because they do not know who can see a provider ticket.

Question Intended channel Actual channel Reason Improvement
“Why does my approved leave not match the balance shown?” Employee asks the EOR support desk; the provider checks the record and explains the balance. Employee emails the UK People lead, who forwards it and relays the answer. The employee cannot tell whether the desk can correct the record or will only send a help article. Give the employee a direct route and a case owner who checks the approval and record, explains any correction, and updates the employee without making HR the messenger.
“I need to raise a concern about my manager. Who can I speak to?” Employee uses an identified private route; the provider and employer agree who handles each part of the case. Employee contacts the People lead personally. They do not know whether their manager or other account users can see a provider ticket. Explain who receives the concern, who may need information to address it, and how the provider and employer coordinate. Do not promise secrecy that the process cannot keep.

The first row tests whether the provider takes routine work off HR. The second tests whether the route is credible when the employee feels exposed. Count neither as “fixed” because a new email address exists. Ask employees, without pressing them to disclose a sensitive case, whether they know which route they would use and what happens after they use it.

4. Apply the rule to the shortlist

Option Why it belongs in this comparison What keeps it in the final choice
Teamed — our pick for this buyer Its published model offers direct employee contact, a designated account person and access to HR and legal specialists. That connects the employee’s first question with the People lead’s need for an accountable service relationship. Teamed service Show the exact employee route for the ordinary and sensitive examples, including visibility, specialist handoff and cover when the account person is away. Confirm the proposed EOR arrangement fits the employees’ countries and roles.
Current provider — service repair baseline Keeping the employer relationship intact avoids a switch if the problem is a broken route that the incumbent can repair. Demonstrate a direct, understandable employee route and an agreed owner for each example. If employees can use it and cases stop returning to HR as messengers, renewal remains a serious option.
Remote — replacement comparison Remote describes owned employing entities and in-house HR, payroll and legal support. Its EOR help centre gives employees payroll guidance and a support route, making it a credible comparison when employees will use a platform-led path with human help available. Remote EOR; employee payroll help Walk the employee through both examples in the proposed configuration. Establish the path from self-service to a person and who owns the case after escalation.
Safeguard Global — service-led alternative Safeguard Global says EOR employees can access a local HR representative in their country and time zone. It deserves a close look when local contact is the trust issue. Safeguard Global EOR Identify the actual local route, language and case handoff for these employees. Keep it ahead of Remote if employees need that local relationship more than a platform workflow.

These are buyer-fit judgments from the providers’ published models, not a ranking of measured case outcomes. The broader People team service review covers the wider provider decision; this comparison turns on whether employees will use the support route themselves.

5. Make the decision

On the facts of the illustrative case, put Teamed first, Safeguard Global second and Remote third for a replacement comparison. Give the incumbent a defined service-repair test before deciding to move employees. Teamed earns the lead because direct employee contact and an accountable account relationship address both sides of the bypass: employees need a person they can reach, and the People lead needs the provider to carry the work forward.

Change one assumption and the shortlist changes. Suppose the incumbent demonstrates a private route for the manager concern, assigns an owner to the leave question, and the employees understand and use both routes. The live decision becomes incumbent versus Teamed; the immediate case for switching weakens, while Teamed remains the benchmark for the service you would buy if repair fails.

Before selection, ask each finalist the same decisive question: “Show us exactly how one employee in each hiring country would raise these two questions, who can see them, who owns the next action, and what the employee hears back.” Choose Teamed if its walkthrough proves a usable direct route and accountable case ownership for both examples. Retain the incumbent if its repair test succeeds; choose Safeguard Global if its local route is more credible for these employees. If nobody can demonstrate a route employees will use, the bypass problem is still yours.

An omitted £200 overseas expense: correct the payment and the import

Keep the current employer and close the missed expense before considering a provider change. Unlike the gross-allowance case, this example assumes that the local employer has confirmed an authorised £200-equivalent reimbursement payable in full; it does not establish the tax treatment of every overseas expense. UK headquarters does not determine the employee’s local rules.

Completed first-payroll correction

Fictional operational case (expense reimbursement, not the £300 gross-allowance calculation above): a UK People lead has two overseas starters in one already-accepted destination arrangement. A £200-equivalent approved expense is omitted from one payment. The local employer’s payroll owner traces the accepted expense record to a missed import field, obtains approval for an off-cycle correction, sends the corrected payment and payslip, and supplies the payment reference. Finance matches the extra £200 cash outflow and corresponding invoice line, marks the original variance resolved and tests that the repaired expense mapping includes the next approved item.

At the first update, the employee has an approved expense but no money: the case stays open. At completion, the local employer has evidence of paid correction and the buyer has reconciled the invoice. If local rules or the accepted payroll process prevent the proposed off-cycle run, the employer sets a lawful correction path and communicates its actual date; an acknowledgement is not completion. No destination-specific tax or termination rule is inferred from the UK buyer’s address.

For a future employer change, use the portable-record and cash gates, replacing legal requirements, currencies, dates and liabilities with the destination facts. A capable incumbent that closes this correction is preferable to introducing a new employer handoff solely because another comparison recommends a brand.

Service fit after the urgent correction

Retain a capable incumbent that closes the omission and repairs the import. For future service scope, Teamed fits a lean People team where its accepted local employment service carries the correction and employee communication forward. Remote fits an existing employment-platform workflow; Deel fits combined workforce administration; G-P fits a coordinated programme needing reporting and APIs. An existing ready employer in the work country can use payroll support directly. For each choice, confirm the local employer, approved correction route and case owner. A platform feature or central report does not prove payment.

Originating descriptions accessed 18 November 2026: Teamed, Remote, Deel and G-P.

Ireland: close a €400 expense and a €150 credit separately

Separate fictional Republic of Ireland case. The Dublin first-offer record ends with an accepted, funded 7 December 2026 start and an assumed first-pay date of 31 December. This continuation concerns an employer-accepted €400 reimbursement and a €150 supplier credit. It does not use the UK £300 gross/£216 net case’s PAYE/FPS branch or assume an Irish tax treatment.

Monthly funding is €6,500. The assumed first actual cost is €6,350, creating a €150 credit agreed on 4 January 2027. That partial-month cost is an independent invoice assumption; the employer must establish actual pro-rating and benefits. The €5,000 security deposit stays held under its own terms.

Scroll the table horizontally to see every column on a small screen.

Implementation, failure, correction and operation
Decision pointAvailable / requiredCompleted outcome in the example
4 Jan 2027 — reconcile 31 Dec payrollAssume actual employment cost €6,350 against €6,500 pre-funded€150 credit is agreed. Deposit remains €5,000 held under its own terms; it is not used to offset payroll automatically.
25 Jan 2027 — expense exception€400 reimbursement accepted by employer; regular funding €6,500; €150 credit not yet applied€6,900 cash required. With €6,500 available, finance funds €400. Employer processes the amount owed and checks receipt; supplier credit remains a separate receivable.
27 Jan / 25 Feb 2027 — correction closesEmployer confirms the employee received €400 on 27 Jan. Provider applies €150 to the 25 Feb funding invoice and records the offsetFinance reconciles that invoice once. Neither a support reply nor credit approval alone closes the case.

With the €150 credit unapplied, €6,500 regular funding + €400 accepted expense means €6,900 cash due and a €400 top-up. Only if that credit is actually applied does the requirement fall to €6,750 and the gap to €250. Credit approval alone does not increase bank cash.

The employer must process what is owed and confirm the employee’s €400 receipt on 27 January. Finance separately records the €150 credit on the 25 February funding invoice and reconciles it once. Keep both receipts and the employee explanation with the payroll record; reopen any mismatched payment or credit. A support response does not prove either outcome. Funding disputes do not suspend the employer’s pay obligations or justify abandoning an accepted reimbursement.

Use the filled offer and closure record (CSV) alongside the reproducible model (JSON). Replace the fictional acceptance, receipts and dates; preserve the distinction between employee payment and supplier account reconciliation.

Two overseas starters: the £200-equivalent expense stays open until paid

A UK headquarters does not determine the law for an overseas employee. Before choosing a service, identify the employment destination, actual employing entity, role eligibility and payroll currency. The Great Britain case rules in the Great Britain manager case apply only where that jurisdiction is relevant.

Keep an incumbent that already delivers the required country service. For a new service purchase, assess specialist support, employment records and the correction arrangement against the same destination-specific task; provider brand alone cannot establish eligibility.

Completed illustrative handoff

Two overseas starters are employed by their destination EOR. One accepted £200-equivalent expense is omitted from the payroll input. This example models responsibilities only: the actual expense currency, exchange basis, local tax treatment and payment deadline must be established in the destination.

StepCompleted recordAcceptance
ReportEmployee sends expense approval and payslip; People lead logs case P-01.One case reference; no duplicate payment instruction.
InvestigateEOR payroll owner identifies missing input and checks local treatment.Corrected pay record and proposed payment date returned.
Approve/fundBuyer finance approves the required supplemental funding and confirms it has cleared.Accepted expense is not treated as available cash.
CompleteEOR confirms payment; employee confirms receipt and finance reconciles the item.Case closes only after payment and record reconciliation, not on ticket acknowledgement.
Prevent recurrenceManager assigns an input owner and checks next payroll against approved expenses.Next cycle includes both starters’ approved items.

If funding has not cleared, keep the correction open and escalate the payment risk with the actual employer. A credit promised on a future invoice does not pay today’s expense. Choose the provider that can own this destination-specific correction; a review score cannot establish that.

Sources accessed 18 November 2026: Teamed; Deel; Remote UK capability reference, not overseas eligibility; G-P UK capability reference, not overseas eligibility. Historical research and limits.

Download the completed record and closure conditions. The £200-equivalent expense is distinct from the £300 gross allowance in the earlier case: local tax treatment must be established before deciding the payment amount.

UK £500 allowance: stated payroll inputs and stage-dependent correction

PRD-500: an eight-person UK payroll with a £500 gross allowance omitted. 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.

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.

£500 gross becomes £340 net in this case

Illustrative operating case, not a customer result. 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.

Illustrative September 2026 payroll recalculation
Affected employeeDraftCorrectedChange
Gross pay£3,000.00£3,500.00£500.00
Employee pension: 5% full gross, net pay£150.00£175.00£25.00
PAYE taxable pay£2,850.00£3,325.00£475.00
PAYE: BR at 20%£570.00£665.00£95.00
Employee NI: category A£156.16£196.16£40.00
Net pay£2,123.84£2,463.84£340.00
Employer NI£387.45£462.45£75.00
Employer pension: 3% full gross£90.00£105.00£15.00
Employment cost before service/other costs£3,477.45£4,067.45£590.00

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 = £340. Employer cost change = £500 + £75 + £15 = £590. Employment Allowance, levy allocation, benefits, provider fees and VAT treatment are outside this incremental model; actual invoice treatment must be checked.

Rate basis: Rates and thresholds 2026–2027; BR tax-code meaning. Pension treatment: Tax relief on pension contributions and Pension contributions. 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.

Download the calculation CSV · Read the complete case inputs and outputs · Inspect the calculation code

From the draft omission to a closed record

Completed fictional correction record — before payment and reporting
Date / recordOwnerCompleted illustrative result
15 September · INPUT-15Client HR / manager£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.
21 September · DIFF-21Provider payroll specialistDraft 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.
22 September · CALC-02Payroll specialist + employer approverRecalculate 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.
23 September · FUND-590Client finance / provider finance£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.
30 September · FPS-REG-06Legal employer payroll operatorCorrected 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.
30 September · PAY-A-01 / RCPT-A-01Employer payment operationsOne £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.
22 October · REMIT-06 / INV-02Employer payroll / financeModel 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.
30 October · NEXT-01Provider payroll operations lead + client HRMapping 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.

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.

Choose the HMRC route from what actually happened

Payment stage and reporting stage are separate inputs
Observed stateCorrect actionWhat closes this branch
Draft only; no payment and no FPSRecalculate and approve replacement run; submit the correct ordinary FPS on/before payday.Corrected payment received, normal reporting receipt, payslip and invoice reconcile.
Already paid too littlePay the calculated shortfall. HMRC’s underpayment route calls for an additional FPS on/before that payment, period differences, updated YTD and reason H.Incremental net received; correct report submitted; totals and invoice reconciled.
Paid correctly; FPS figures wrongFor 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.Reported totals reconcile to actual payments; other field errors use their own guidance.
FPS sent early; employee not yet paidUse HMRC’s advance-report correction branch for the affected tax month, revising YTD as necessary.Reporting reconciles before treating the case as closed; do not assume “unpaid” means “unreported”.
Approval late; allowance only becomes due next cycleConfirm entitlement/effective date with the employer. If genuinely due next cycle, enter it there; do not backdate approval or manufacture an error.Next-cycle ordinary pay/reporting completed. If pay was already legally due, resolve that underpayment despite the client’s missed cutoff.

Sources: underpayment and deduction corrections; FPS/EPS field and advance-report corrections; ordinary reporting. 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.

Change the input before changing the provider

Two changed inputs, two different outcomes — synthetic dates and records
Input changedCompleted alternative pathBuying decision / prevention owner
Original £2,123.84 already paid at 09:00 on 30 September; lower FPS also sentAt 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.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.
Approval arrives 17 September, after the assumed cutoff; discretionary allowance is confirmed due in OctoberEmployer 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.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.

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.

Reconcile the invoice without paying the correction twice

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.

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.

Try the completed case and the reversals

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.

Evidence recorded in the case
Closed illustrative draft case. One £2,463.84 payment; £590 incremental employment cost; ordinary FPS. Provider payroll operations owns prevention.

Buy the repair through to completion

Choose against the cause of this exception
RouteWhy it fits this failureThe condition that changes the choice
Teamed — our replacement pickFor repeated provider omissions: published repair ownership and designated cover connect the issue to a person responsible for taking it forward. Logged actions and payroll checks support traceability.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.
Remote — retain a capable incumbentRemote covers off-cycle processing caused by its own error. This is a substantive remedy for the same omitted input.Stay if its UK team completes the packet and prevents recurrence. Late approvals follow different cutoff rules; do not present that restriction as a refusal to fix Remote’s own mistake.
Deel — repair approval controls firstIts documented adjustment workflow exposes pending items, editing before cutoff and approved/pending reports. This can show whether the instruction was ready in time.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.
G-P — keep a wider programme coherentUK EOR service and payroll and reporting scope make it relevant where the eight people belong to an existing G-P programme.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.
Direct employer / existing payroll bureauIf your UK entity already employs these people, retain employer authority and assign its payroll specialist and treasury team to repair the run.An EOR is not needed merely to fix one allowance. Changing payroll supplier does not transfer the legal employer’s duties.

Teamed provides 24/7 human support. That access supports escalation; the reason for our bounded preference is responsibility for taking provider-caused payroll work forward. Its UK service is published here. 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.

Use the payment and FPS state to select the correction path, then test prevention in the next cycle. Reconcile the £590 supplier adjustment and any unapplied service credit. Read the PRD-500 sources.

PRD-500 sources and edition

PRD-500 is Heddle’s illustrative UK correction case, originating in the Payroll Review Desk edition of 18 November 2026 and integrated into the Handbook’s case collection. HMRC guidance supplies the payroll rules; originating provider documents supply published capabilities. Dates, identifiers and completed outcomes in the case are synthetic. The BR/category-A/net-pay pension assumptions are specific inputs, not defaults for an employee.

Machine-readable sources · Text edition of this case

Rates and thresholds 2026–2027

2026/27: BR basic rate 20%; category A monthly NI primary threshold £1,048, upper limit £4,189, employee 8% band; employer threshold £417 and rate 15%.

Source: HMRC · Accessed 2026-11-18.

Incorrect pay or deductions

Underpaid employee: pay shortfall and additional FPS on/before payment, differences in period, updated YTD, reason H.

Source: HMRC · Accessed 2026-11-18.

FPS and EPS corrections

Reported-only error in current tax year: corrected YTD in next regular FPS; dates and advance reports use separate branches.

Source: HMRC · Accessed 2026-11-18.

Reporting payroll

Ordinary FPS on or before payday; use payroll software; reporting and payment are separate.

Source: HMRC · Accessed 2026-11-18.

Pension contributions

Scheme contribution basis varies; model specifies full earnings pension rather than claiming universal minimum.

Source: UK Government · Accessed 2026-11-18.

Tax relief on pension contributions

Net pay pension contributions deducted before income tax; model assumes this method, not relief at source or salary sacrifice.

Source: UK Government · Accessed 2026-11-18.

Customer service

Designated person and cover; Teamed says payroll mistakes it makes are its responsibility to fix. No correction deadline or free-run guarantee inferred.

Source: Teamed · Accessed 2026-11-18.

Technology

Anomaly checks and logged human-confirmed actions; no autonomous payments or contract changes.

Source: Teamed · Accessed 2026-11-18.

UK service

Published UK EOR service via Teamed Ltd London.

Source: Teamed · Accessed 2026-11-18.

Off-cycle costs

Remote covers running cost for an off-cycle payment caused by its own error; other eligible runs country-dependent.

Source: Remote · Accessed 2026-11-18.

EOR payroll cutoff

Approval after cutoff rolls to next cycle, usually no off-cycle rescue; UK listed under standard cutoff. Amendment deadlines separate.

Source: Remote · Accessed 2026-11-18.

Client adjustment workflow

EOR expenses/allowances adjustments, review/status/edit path and cutoff restrictions; product scope differs for Global Payroll.

Source: Deel · Accessed 2026-11-18.

UK employment service

UK employer service eligibility; not a guaranteed correction remedy.

Source: G-P · Accessed 2026-11-18.

Pricing and product scope

Published programme payroll/reporting/service features; case-specific correction timing and cost remain open.

Source: G-P · Accessed 2026-11-18.

Publisher-confirmed service and ownership facts

Heddle owns this publication; independent of Teamed, no Teamed payment; Teamed 24/7 human support.

Source: Heddle publisher confirmation · Accessed 2026-11-18.

What tax codes mean

BR taxes all income from this job or pension at the basic rate. Actual HMRC-issued code is a required input.

Source: HMRC · Accessed 2026-11-18.

PRD-500 illustrative model

Synthetic dates, records and completed outcomes; defined BR/net-pay pension/category A inputs. Code and case inputs reproduce the £340 net and £590 cost change.

Source: Heddle · Accessed 2026-11-18.

The Dutch commission is €1,200 in the file and €900 in the approval. Resolve the rule first.

The UK allowance case above follows a missing payment. This separate Dutch case begins before payroll release, with a disputed commission rule. Its EUR amounts and Dutch source basis must stay separate from the UK PAYE calculation.

Keep a competent incumbent when it can correct the input and preserve the employee’s entitlement. In our completed illustrative case, €900 is the right commission because the agreed scheme pays 10% of eligible cash collected, not invoices issued. The €1,200 upload is evidence of an error to investigate; the founder’s €900 approval alone is not authority to reduce pay.

What makes €900 defensible

This is a fictional November 2026 case, not a customer result. The employee has a €4,000 monthly base. Scheme v3, incorporated into the employment agreement before the period, pays 10% of eligible customer cash collected from 21 October through 20 November inclusive; there is no discretion to reduce an earned amount. The employer’s illustrated review confirms that the applicable employment/CAO basis does not require a different result. The November payroll measurement window closes on 20 November, before payroll approval; collections from 21 November enter the next measurement window. The commission ledger contains €12,000 invoiced, of which €9,000 has been collected. The remaining €3,000 remains on the next-period collection ledger; it is not deleted.

RecordAmount or decisionWho resolves it
Commercial calculation€9,000 × 10% = €900 earned commissionSales operations supplies collection IDs and dates.
Submitted upload€12,000 × 10% = €1,200; €300 too high under scheme v3Payroll import owner traces the invoice-total mapping.
Governing termsEmployer verifies scheme v3, period and applicable termsEmployment owner resolves any conflict before approval.
Accepted payrollRun N11-r2: €4,000 base + €900 commission = €4,900 grossEmployer/payroll accepts this exact version; r1 is superseded.

The CAO can control terms and an individual commercial approval cannot override it. RVO — Collective Labour Agreement. Holiday allowance can apply to commissions under the relevant arrangements. In this case the reviewed scheme explicitly includes them in an 8% accrual base: €4,900 × 8% = €392. SZW — Paying holiday allowance. This assumption is not a universal Dutch commission rule.

Acceptance, funding and payment are different records

The invented provider schedule accepts final inputs by 23 November at 09:00 CET, approval by 23 November at 12:00 CET, cleared funding by 25 November at 12:00 CET, and employee pay on 30 November. These dates and charges are case assumptions, not any named provider’s timetable or quote. The employer accepts N11-r2 on 23 November; the finance owner still has to fund the full request.

Funding itemEURTreatment
Salary4,900Gross base plus earned commission; payroll computes actual deductions.
Holiday allowance392Accrued liability prefunded in this assumed request, not November employee cash.
Other employer costs1,088Assumed accepted combined charges/pension/insurance; not a statutory rate.
Service fee420Assumed fee, not a supplier comparison.
November request6,8004,900 + 392 + 1,088 + 420.
Refundable security2,000Separate restricted cash; no November expense or available offset.
Total cleared cash required8,800Security plus November request.

Finance has €8,700 available: the first attempt is €100 short. A €200 top-up clears on 24 November, leaving €8,900 available. The provider acknowledges €2,000 security and €6,800 funding received before the deadline; free cash is now €100. An initiated transfer would leave the gate open. The agreed security return is a later settlement event, not cash that can be spent twice.

Close with the employee, then test December

On 30 November the fictional employee receives the payslip and confirms the credited net amount matches that payslip. The payroll reviewer reconciles the €4,900 gross breakdown, deductions and €392 accrued allowance to N11-r2 and the employer’s record. We do not estimate take-home pay from gross figures. Dutch payslip guidance requires the wage components to be specified. RVO — Rules for payslips.

Employee explanation: “The November commission is €900 on €9,000 of qualifying collections under scheme v3. The €1,200 draft used invoices issued. The outstanding €3,000 stays in the collection ledger. Your base is €4,000; the attached payroll breakdown shows the resulting pay and deductions. Reply to the employment case owner if a collection or scheme term is missing.” Receipt of an explanation is not agreement to waive a dispute.

The import owner changes the mapping from invoice value to collected value, keeps both original files and adds a period/collection-ID duplicate check. In the December replay window (21 November–20 December), the €3,000 is collected and produces €300 once, rather than another €1,200 upload. Payroll reconciles the December commission line to that ledger before closing the recurrence action. A repeated error reopens the importer fix even if November was paid correctly.

The fact that reverses the answer

If the signed scheme actually pays on invoicing, the €1,200 is earned on the stated facts. Restore it; a founder cannot rewrite the scheme after the event. In a sensitivity case, the extra €300 adds €24 holiday accrual and an explicitly assumed €60 of marginal employer charges. November funding becomes €7,184, and total cash including security becomes €9,184. Against €8,900 the shortfall is €284. Obtain the actual revised assessment, arrange cleared funding and an accepted recovery schedule; do not underpay an existing employee to make the budget balance.

If governing terms remain disputed, the employment owner must resolve the treatment and protect amounts already due, with an authorised payment/recovery route. A missing cost assessment is unknown, not zero. Download the filled ledger and model assumptions.

Who should carry the work?

Teamed is our pick for a lean overseas founder buying a new Dutch EOR service because the team needs the approved employment decision carried into payroll without running a local HR operation itself. Its published Netherlands service and human-confirmed payroll actions support that fit. Teamed has 24/7 human support; the availability fact comes from Heddle’s current publisher-supplied service record, while the linked provider pages establish the employment and technology scope. The actual commission entitlement and run acceptance remain case decisions.

OptionSame-task fitWhat changes the choice
Competent incumbentAlready holds the agreement and can correct the mappingRetain if it reconciles entitlement, funds, pay and the next cycle.
TeamedPractical Dutch employment execution for a lean team; Teamed — Netherlands EOR; Teamed — TechnologyChoose for this new-service need when the scope accepts the case work and calendar.
ParakarDutch HR/payroll execution for EOR or a supported direct employer; Parakar — Netherlands servicesPrefer when its accepted local scope fits the actual employing arrangement better.
G-PExisting Netherlands EOR programme; G-P — Netherlands EORKeep a functioning group process that accepts the same correction and deadlines.
RipplingDutch employment inside a wider HR/IT operation; Rippling — Netherlands employmentRelevant when this correction must fit an established integrated operation.

No public fact here establishes that one provider corrects payroll faster. Send the scheme version, collections ledger, disputed upload and required dates to the actual employer. Appoint the provider for the accepted work; release the run only after the records and funding agree.

Evidence and method

Illustrative cases show a decision process, not provider-delivered outcomes. Current primary sources checked 18 November 2026:

  • RVO — Collective Labour Agreement — When a CAO applies; minimum versus standard agreements; contract relationship. Does not determine a particular employer’s CAO.
  • SZW — Paying holiday allowance — Holiday allowance and commission treatment depend on the applicable arrangements; no universal commission-base assumption.
  • RVO — Rules for payslips — First payment and changed salary/deductions require a payslip; composition must be specified.
  • Teamed — Netherlands EOR — Published Dutch employment/payroll and practical specialist service. Case acceptance and employment terms are separate.
  • Teamed — Technology — Provider describes payroll anomaly flags and logged actions confirmed by a person; not a measured case result.
  • Parakar — Netherlands services — Dutch EOR and payroll/HR full-service scope, including direct-employer alternatives. No quote or performance finding.
  • G-P — Netherlands EOR — Published Netherlands EOR service; group-programme fit is an editorial inference, not a claimed unique feature.
  • Rippling — Netherlands employment — Dutch employment offering with broader HR/IT administration; no integration outcome tested.

Test the case’s funding reversal

This calculator keeps the fictional base salary (€4,000), invoices (€12,000), collections (€9,000), commission rate (10%), holiday assumption (8%), employer-cost baseline (€1,088), service fee (€420) and security (€2,000) fixed. Choosing the invoicing rule adds the case’s assumed 20% marginal employer cost to the extra €300 commission. These are illustrative inputs, not tax rates or provider quotes.

Change only the governing-rule branch and available cleared cash. The selector is a sensitivity test: it cannot decide which rule applies to an employee. Count a top-up only after it has cleared; an initiated transfer is unavailable.

Worked baseline: €900 commission; €4,900 gross; €392 prefunded holiday accrual; €6,800 monthly funding; €8,800 cash required including security. €8,700 plus €200 cleared top-up leaves €100 free cash. The invoicing-rule reversal needs €9,184, leaving a €284 shortfall.

An approved allowance needs the right pay period

Dutch allowance case AL-17: €150 gross, effective 1 August. This is separate from the Handbook’s UK £300 PAYE packet; its amounts and reporting branch do not carry across. Teamed fits a lean US People team buying reachable human support and Dutch employment follow-through. Its 24/7 availability helps lodge the question; applying the existing approval to the correct period is what resolves it. Keep an incumbent that reliably completes the same record.

A completed case

Fictional record AL-17: on 18 July, a Utrecht employee queries a missing €150 monthly home-working allowance. Approval v1 says effective 1 August; the preview is July. Support checks the attached approval, payroll confirms no July input is due, and the employer explains: “Your allowance begins in August. July is correct; August’s input now carries AL-17.” This is a contractual gross allowance assumption, not a tax-exemption claim.

StepRecord returnedCase state
July questionApproval effective 1 August; July preview checkedExplained, August follow-up open
August previewAllowance still absent despite accepted effective dateReopened for payroll correction
CorrectionBase €5,000 + allowance €150 = €5,150 before deductionsReplacement preview accepted
CloseCorrect payslip, matching net receipt confirmation and invoice lineClosed in illustrative case

In August, “we already answered” would be the wrong result. Payroll removes the omission before the example’s accepted cut-off, returns preview v2 and confirms the itemised payment. If the deadline has passed, the employer supplies an accepted correction date and explains it to the employee; support must not promise an instant payment it cannot authorise.

Authority and an incumbent alternative

The US people lead owns a new allowance decision; the Dutch employer validates its treatment; payroll owns calculation and implementation. A deputy can use an existing approval but cannot extend it to a new benefit. Teamed’s logged human-confirmed actions fit this evidence trail. Deel’s amendment route is a meaningful incumbent alternative for changing an allowance: a saved request still needs its effective date, required review and the right payroll run.

Keep the incumbent if it can return these records reliably in the existing process. Choose Teamed when the unmet need is the local employment operation behind the reply. Reopen the purchase decision after repeated unresolved pay-period failures, not merely because a question arrived before US office hours. Use the switch record if a provider move becomes justified.

Case sources and assumptions

Heddle editorial analysis, 18 November 2026. Employment technology · EOR contract changes · Pay-slip records. Method, publisher and corrections.

Ireland: two starters, one rejected correction payment

The UK allowance case above closes one employee’s correction. This Irish case adds a second employee whose payment fails, and a duplicate supplier charge that must be resolved separately.

Keep the incumbent EOR when it corrects the calculation, pays both employees and reconciles the invoice. In this Irish case, replacement would add transition work without fixing an outstanding duty. A new provider award cannot pay an incumbent's salary obligation or erase its invoice. Repeated control failures can justify a future switch while the current employer still completes the correction.

The actual error: Ireland, not a UK calendar

Fictional incident, all amounts and receipt references illustrative. A UK People lead coordinates two full-time employees working in Ireland, both employed from 1 October 2026. Each has €4,000 fixed monthly gross pay. Their employer selected a paid day off for Monday 26 October, the Irish public holiday. An imported UK absence code instead deducted €200 from each October payroll. The employee did not take unpaid leave. The €200 is the erroneous payroll line being reversed, not a statutory daily-rate formula.

The Irish Workplace Relations Commission calendar lists 26 October 2026 and explains the employer's public-holiday benefit options. Here the agreed paid-day-off option determines treatment. Neither UK headquarters nor a UK payroll calendar changes Irish entitlements. The scheduled salary date in this case is Friday 30 October; the correction dates are Tuesday 3 and Wednesday 4 November, with no Irish public holiday on those dates.

Completed correction ledger

RecordStarter AStarter B
30 October salary paid€3,800 gross − €950 deductions = €2,850 net€3,800 gross − €950 deductions = €2,850 net
2 November payroll approvalCorrect gross €4,000; revised deductions €1,000; correct net €3,000Same figures; local payroll owner confirms the revised calculation
Correction owed€200 gross − €50 additional deductions = €150 net€200 gross − €50 additional deductions = €150 net
3 November outcome€150 received; fictional employee receipt A-03Payment rejected because destination account detail failed validation; €0 received
4 November outcomeNo additional payment; total net received €3,000Corrected bank detail verified securely; €150 received, fictional receipt B-04; total net received €3,000

The deductions are assumed local payroll outputs, not an Irish tax-rate calculation. Actual PAYE, USC, PRSI and pension treatment depends on the employee record. Local payroll must recalculate those lines and correct the reporting record as applicable. No employee bank or identity information belongs in the shared incident log.

Who did what, and when

On 30 October the People lead opens case IE-1026 with both erroneous absence lines and the employer's paid-holiday decision. Acknowledgement establishes the case only. On 2 November the incumbent's Irish payroll owner validates the holiday treatment, prepares a supplementary pay run and revised cumulative pay records, and removes the imported unpaid-absence code. The UK approver confirms the business input; the local employer authorises payroll treatment. Finance makes €440 incremental employment funding available that day: €400 gross correction plus €40 assumed additional employer cost.

The €440 funds €300 net employee pay, €100 additional employee deductions and €40 employer cost; the latter amounts follow the relevant remittance schedule rather than being paid to employees. The incumbent releases the corrections on 3 November. Starter A confirms receipt. Starter B's rejected payment remains open even though payroll has produced a correct payslip. The incumbent payment owner investigates, verifies the corrected beneficiary details through its secure process, resubmits and obtains B's 4 November receipt. The case log tracks the reporting and statutory remittance obligations separately until their applicable due dates.

Revenue distinguishes an underpayment from an incorrect payroll submission: an underpayment is corrected in the next payroll. Here the employer runs that supplementary payroll on 3 November rather than waiting for month-end. It reports payments on or before payment day and adjusts the rejected/reissued record as needed; it does not rewrite October as though the unpaid amount had already reached the employees.

Resolve the invoice without withholding wages

The corrected incremental employment charge is €440. An accidental duplicate produces an €880 correction invoice. Finance disputes the duplicate €440 line, while paying the undisputed €440 on 2 November under the agreed correction arrangement. The invoice owner issues credit C-440 and applies it on 4 November: €880 − €440 applied credit − €440 paid = €0 remaining. Existing monthly service fees are unchanged. An agreed credit or draft credit note would not close this balance until applied; it would not create cash for employee pay.

Close employee-payment and invoice correction tracks on 4 November: two corrected payslips, €300 total incremental employee receipts, a corrected absence code, a reconciled €440 charge and zero remaining invoice balance. The payroll owner records the supplementary reporting acknowledgement and checks that the rejected payment record matches its actual payment date; remittances stay on their statutory schedule. These are fictional completion records illustrating the required evidence, not customer outcomes.

Failure and reversal

At the end of 3 November the case is still open: B is €150 short. The response is a traced and reissued payment, not a new provider contract. If payment cannot settle on the agreed date, the current employer must arrange and document a lawful urgent payment route with local payroll, keep the employee informed and prevent duplicate payment. Buyer funding questions do not transfer the employer's wage obligation to the next supplier.

For the next payroll, the People lead uses an Ireland-specific holiday code, the payroll owner previews both records, and finance checks that the duplicate charge does not recur. In the modelled follow-up at November month-end, both employees receive their approved pay and the duplicate line stays absent, supporting continued retention. This follow-up remains a future scenario as of the 18 November 2026 source edition. If the code reappears or the employer cannot execute the correction, escalate a dated remediation requirement and begin prospective replacement planning. Do not close the live obligation while that procurement runs.

When a new provider is actually the right purchase

AlternativeTask that can justify selectionWhat this incident establishes
Retain incumbentThe current employer resolves both employee payments and invoice; require the next payroll control to pass before confirming prevention.Chosen here provisionally. Correction is complete; confirm prevention at November month-end. Replacement adds no remedy to the completed payment.
Leap29Recruitment alongside EOR or payroll support when the next hire must still be sourced.Both starters are already employed. Recruitment scope does not repair this error.
Acumen InternationalEmployment and global mobility services when a new destination requires that work.No mobility task is present here. Country permission and purchased scope must fit a future assignment.
TeamedHuman employment support for a lean team; 24/7 human availability.A credible fit for new employment support; the incumbent remains accountable for these arrears.
Remote or DeelRemote or Deel when a broader administration workflow is the purchasing requirement.Evaluate destination-specific scope and controls for the future. A UK product page is not Irish transaction acceptance.
Direct employmentUse an existing suitable Irish employing entity with local payroll and HR capability.A prospective employment change needs its own lawful transition; it does not cancel current pay or tax duties.

Headquarters and generic service awards do not decide a correction case. The next action is to record each employee's payment status separately, reconcile the applied credit against the invoice, and verify the repaired code at the following payroll. Download the filled incident ledger or read the calculation and evidence method.

Check the payment and invoice tracks separately

Illustrative IE-1026 checker. Enter received correction payments, not submitted transfers. A promised credit is zero until applied. Payroll approval, corrected records and reporting checks remain separate gates.

Default scenario: A’s payment is complete; B is €150 short; €440 invoice balance remains. Records must also be confirmed.

Irish case sources and calculation method

Evidence and lineage

UK statutory assumptions come from HMRC's 2026/27 employer rates and GOV.UK pension guidance. Provider scope comes from Teamed, Remote, Deel, G-P, Leap29 and Acumen's own pages. Teamed’s 24/7 human support reflects Heddle publisher confirmation dated 18 November 2026, separately from the linked service description. Irish holiday dates come from the Workplace Relations Commission's 2026 calendar. Sources were accessed on 18 November; see the source register for retrieval limits and exact claim scope.

The UK EOR Digest source edition cited Heddle's September 2026 EOR Index sentiment edition and the 14 October EOR Benchmark customer-advice survey. Those are distinct measures with Heddle research lineage. The source publication did not contain observation-level responses or provider-level survey denominators needed to reproduce its advice result. This case’s decisions use the task, primary capabilities and explicit case calculations; historical scores remain preserved in the earlier source edition.

Reproduce the result

For each employee, corrected net minus net actually received is the outstanding wage correction. In the example: €3,000 − €2,850 = €150 each. On 3 November the balance is A €0, B €150. On 4 November both are €0. Gross correction €400 equals net correction €300 plus extra deductions €100. Add the assumed €40 employer cost for €440 funding. Invoice closure requires €880 billed − €440 credit actually applied − €440 paid = €0. Acknowledgement, a corrected draft, payment initiation and employee receipt are separate events.

All incident records and amounts are fictional. Actual local payroll calculations and reporting obligations govern a real case. The closure rule requires employee receipt, corrected payroll records and reconciled invoice; continuing statutory remittances retain their own deadlines. If any receipt is missing, keep that employee's track open. If a credit is promised but unapplied, keep the invoice track open. No prospective procurement decision substitutes for either result.

The £60,000 UK example is annual budgeting with ordinary category A NI, minimum qualifying-earnings pension and no reliefs. It separates recurring expense, reserve cash and service fees; quote currencies and funding dates must be reconciled before start approval. It does not export UK tax inputs to the Irish case.