Glossary
Payroll cut-off
The calendar deadline by which all variable inputs (hours, expenses, joiners, leavers, bonuses, contract changes) must be finalised so payroll can process the run on time. Most cycles operate two cut-offs in parallel: an internal manager cut-off and a provider or EOR cut-off, set by banking, statutory filing, and payroll-engine constraints.
Payroll cut-off is the calendar deadline by which all variable inputs must be finalised so the run can process on time.
For global payroll teams, the practical question isn't where to mark the date. It's which constraint actually sets it: the banking-clear window, the statutory filing deadline, or the payroll engine's processing window.
UK BACS runs on a three-day clearing cycle with a 10:30am input deadline for credit on T+3. US ACH runs T+1 or T+2 depending on the bank. SEPA standard is T+1, with SEPA Instant available same-day but capped at €100,000 per transaction.
Each window pulls the cut-off back from pay date by a different number of days. Adding the internal-approval lead time on top usually puts the working deadline a full week before the visible pay date.
Two cut-offs that run in parallel: internal and provider
Every payroll cycle carries two deadlines, not one. The internal cut-off is when line managers and HR submit changes. The provider cut-off is when payroll has the file built and ready to lodge with the bank.
| Deadline | Owner | Typical timing | What it gates |
|---|---|---|---|
| Internal cut-off | Line manager and HR | 5-10 business days before pay date | Hours, expenses, joiners, leavers, bonuses |
| HRIS to payroll sync | Payroll team | 24-48 hours after internal cut-off | Master-data refresh, validation |
| Provider cut-off | Payroll provider or EOR | 3-5 business days before pay date | File submission, bank lodgement |
| Funding cut-off | Treasury | 2-3 business days before pay date | Provider account funded for clearing |
| Statutory filing | Payroll provider | On or before pay date | RTI FPS (UK), 941 deposit (US) |
The internal cut-off is the one that usually slips. Most line managers don't see the cycle calendar and treat the visible pay date as the deadline.
Anything submitted late goes off-cycle
A change that misses the internal cut-off has two routes. Either the payroll team carries it to the next regular cycle, or they process it as an off-cycle run.
The off-cycle route adds a per-run fee and a separate statutory filing. See the off-cycle payroll entry for the full mechanics; the cut-off and the off-cycle are paired concepts.
What sets the deadline: banking, statutory filing, payroll engine
Three constraint windows pull the cut-off back from pay date. The latest of the three sets the binding deadline.
Banking clear window
UK BACS runs a three-day cycle. The file is submitted on day one, processed on day two, and credited to the employee account on day three.
The Pay.UK timetable sets a 10:30am input deadline on day one for credit on T+3. Faster Payments offers same-day clearing but caps each transaction at £1m, which prices most batched payroll out of the channel. US ACH credit clears T+1 or T+2 depending on the originating bank's standard. SEPA standard is T+1; SEPA Instant clears in seconds but caps each transaction at €100,000.
Statutory filing window
HMRC PAYE Manual PAYE5010 requires a Full Payment Submission filed on or before the actual payment date. Filing after the date triggers a £100 fixed penalty above a three-day grace window, escalating for repeat offences in the same tax year.
US employers on the semi-weekly deposit schedule (IRS Publication 15) deposit federal taxes for a Wednesday-to-Friday payroll by the following Wednesday, and Saturday-to-Tuesday payrolls by the following Friday. The deposit deadline is independent of the payroll cut-off and adds its own diary lock.
Payroll engine window
The payroll engine needs time to compute gross-to-net, recalculate year-to-date positions, generate payslips, and build the bank file. Most cloud payroll engines need 24 to 48 hours from data lock to validated output, more for complex multi-country runs.
For shadow-payroll or cross-border setups, expect 72 hours minimum. The engine window is the constraint most often underestimated when finance teams pressure-test a new cycle calendar.
Real cut-off windows by country and payroll cadence
The constraint stack varies by country and by cycle frequency. Monthly cycles have more slack than fortnightly; weekly cycles run on tighter rails than either.
| Country | Clearing system | Standard window | Same-day option | Statutory filing |
|---|---|---|---|---|
| UK | BACS | T+3, 10:30am input deadline | Faster Payments, £1m cap | FPS on or before payday |
| US | ACH | T+1 or T+2 | Same Day ACH, $1m cap | 941 semi-weekly deposit |
| France | SEPA | T+1 | SEPA Instant, €100k cap | DSN before 5th or 15th |
| Germany | SEPA | T+1 | SEPA Instant, €100k cap | LStA by 10th of next month |
| Netherlands | SEPA | T+1 | SEPA Instant, €100k cap | Loonaangifte monthly |
| Singapore | GIRO / FAST | T+1 (GIRO) | FAST, S$200k cap | CPF by 14th of next month |
Same-day rails exist almost everywhere, but the per-transaction cap usually rules them out for batched payroll. A 200-employee UK monthly run rarely fits inside the £1m Faster Payments ceiling, so the cycle stays on BACS T+3.
EOR cycle cadence in practice
EOR providers publish their own cut-off windows on top of the underlying banking system. The cadence determines the slack.
| Cycle | Typical EOR cut-off | Internal cut-off | End-to-end lead time |
|---|---|---|---|
| Monthly | 5-7 business days before pay date | 10 business days before | 2 calendar weeks |
| Fortnightly | 3-5 business days before | 5-7 business days before | 7-10 calendar days |
| Weekly | 2-3 business days before | 3-4 business days before | 3-5 calendar days |
For buyer comparison on transparent cycle calendars, see our Deel review for one provider's published submission windows. The UK HMRC payroll submissions entry covers the wider FPS, EPS, and supplementary submission timetable.
What goes wrong when the cut-off slips
Three failure modes account for most missed-cut-off incidents. Each lands a different cost.
Late line-manager submission
The most common failure. A bonus, joiner, or contract change lands after the internal cut-off and gets carried to the next cycle or processed off-cycle.
The off-cycle route triggers the per-run fee, the separate statutory filing, and 2 to 4 hours of payroll-team time. Across a year of mid-cycle approvals, the cumulative cost rivals an extra full cycle.
Late FX or funding
Multi-country payrolls run on multiple currency rails. If the funding currency differs from the payment currency, the FX rate is locked at file submission.
A delayed wire from treasury can push the funding past the provider cut-off, which delays clearing and lands the payment after pay date. In several countries this triggers a statutory late-payment penalty even when the file itself was on time.
Public-holiday and year-end compression
Bank holidays in the clearing country shorten the window. A UK monthly cycle paying on the last working day of December compresses around Christmas and Boxing Day; the cut-off moves forward by two clearing days.
Year-end overlap with the finance close adds further pressure. Payroll cut-off, statutory year-end filing, and finance month-end all collide in the same week, which is why most providers move year-end deadlines forward by 5-7 business days.
Whichapp view
The deadline that matters is the internal cut-off, not the provider cut-off. Line managers approve hours, expenses, and contract changes on the same calendar everyone else works to, so the published date on the cycle slide needs to be the manager deadline (T-10) rather than the provider deadline (T-5).
For provider comparison on transparent cycle calendars, see the best global payroll providers shortlist. Bonuses and corrections that miss the cut-off pair with the gross-up mechanics if the headline figure was promised net.
How to compress cut-off for teams across multiple time zones
Global teams spanning more than four time zones can't run a single cut-off date. The submission window has to account for the latest manager-side closing-of-business in the slowest zone.
Set the internal cut-off in UTC, not local
A manager in Singapore submitting on Friday 5pm SGT is 6am London time. A London team treating Friday 5pm UK time as the cut-off misses the Asia-Pacific submissions by a full working day.
Setting the internal cut-off in UTC with explicit conversion in the cycle calendar removes the ambiguity. The cycle slide carries the UTC time and a per-zone table; managers see their local deadline without ambiguity.
Stagger the cut-off by region, not by employee
Some payroll teams try to give Asia-Pacific staff an extra day. That breaks reconciliation. The better pattern is a regional sub-cut-off for managers, all rolling into a single provider cut-off for the file build.
The provider sees one consolidated file; the regional managers each get their own local deadline. See the employer contributions entry for how regional cut-off variance affects the contribution-line build, especially in mid-month bonus events.
Build in one buffer day for FX and validation
For multi-currency runs, treat the file-build deadline as one business day before the provider cut-off rather than the same day. The buffer absorbs FX-rate variance, validation errors, and any last-minute correction. It costs one day of slack and prevents most missed-payday escalations.
See our ranked shortlist of providers, scored for multi-country coverage, reporting depth, and operational fit. Updated for 2026.
View the shortlist →Payroll cut-off FAQs
What is the difference between internal and provider payroll cut-off?
The internal cut-off is the deadline for line managers and HR to submit changes: hours, expenses, joiners, leavers, bonuses, contract changes. It typically sits 5-10 business days before pay date.
The provider cut-off is the deadline for the payroll provider or EOR to submit the bank file, typically 3-5 business days before pay date. Most cycles operate both deadlines in parallel.
Why is the UK payroll cut-off three days before pay date?
Because UK BACS runs a three-day clearing cycle. The Pay.UK timetable sets a 10:30am input deadline for credit on T+3, so a payday Friday needs the bank file lodged by 10:30am Tuesday.
Faster Payments offers same-day clearing but caps each transaction at £1m, which prices most batched payrolls out of the channel. BACS remains the standard rail.
Does HMRC RTI affect the payroll cut-off?
Yes. HMRC PAYE Manual PAYE5010 requires a Full Payment Submission filed on or before the actual payment date. The filing pulls the practical cut-off forward because the file has to be complete and validated before pay date.
Filing more than three days late attracts a £100 fixed penalty per missed submission, with escalation for repeat offences in the same tax year. See UK HMRC payroll submissions for the wider FPS and EPS cycle.
What happens if an employee change misses the payroll cut-off?
Two options. The payroll team carries the change to the next regular cycle, or they process an off-cycle run for that specific employee.
Off-cycle adds a per-run fee (typically $50 to $300 per employee), a separate statutory filing, and 2 to 4 hours of payroll-team time. Most teams default to next-cycle carryover unless the change is a termination or starter with a statutory deadline. The PILON case in the notice pay in lieu entry is the classic forced-off-cycle trigger.
How do public holidays affect payroll cut-off?
Bank holidays in the clearing country shorten the window. A UK monthly cycle paying on the last working day of December usually moves the cut-off forward by two clearing days because of Christmas and Boxing Day.
The same compression applies at Easter, in early-May bank-holiday weeks, and around national days. Most providers publish a year-end calendar that flags every cycle affected.