Payroll Cut-off Dates

Payroll cut-off dates are the deadlines by which changes - bonuses, expenses, time off, salary changes, terminations - must be submitted to be included in the upcoming payroll cycle. Submissions after the cut-off may require off-cycle processing, which can delay payments and incur additional fees.

• EOR employees run on a single global payroll cycle.

• Cut-off: the 5th of each month at 12:00 CET. If the 5th falls on a weekend or public holiday, the cut-off moves to the previous working day.

• This applies across all billing entities and countries.

• You can submit changes as soon as the previous cycle's cut-off passes (the To Review phase).

• Payroll employees run on entity-specific cycles, set per entity in consultation with Lano and the local payroll provider, and shaped by local law and payroll frequency:

• Monthly payroll: cut-off usually 9 business days before the net pay date, at 9:00 CET.

• Semi-monthly: first-half cut-off usually 7 business days before that pay date; second-half cut-off on the 20th.

• Bi-weekly: typically 3–4 business days before the pay date.

• Some entities also have a late cut-off - a short extension window in which changes may still be accepted, subject to Lano approval and possible fees. Your Platform Experience Manager can confirm whether your entity has one, and when your exact dates fall.

Cut-off Deadlines & What Happens:

• Before the normal cut-off: Included in this month's payroll. No action needed.

• Between normal and late cut-off (where applicable): May still be included, subject to approval; fees may apply.

• After all cut-offs: Moves to next month's payroll by default.

• After cut-off, but it must be paid this month: Ask us about an off-cycle run - see below.

Contact your Platform Experience Manager or help@lano.io as soon as possible and ask about an off-cycle adjustment. Be aware that off-cycles are subject to approval, usually carry an additional fee, and are not available in every country - in some locations the only option is the next regular cycle. The earlier you flag it, the more options exist.

1. Submit changes as soon as you know about them - the submission window opens right after the previous cycle closes; there's no need to batch for the deadline.

2. If a month has no changes, tell us - a one-line "no changes" confirmation lets payroll run early on standing data.

3. Put the effective date on every change. A salary increase "from 1 September" submitted in August is processed forward correctly; the same change submitted without a date generates a query.