Close a Baltic operating period with local dates and evidence
Reconcile Estonia, Latvia and Lithuania leave, salary changes and employee cases, with separate local deadlines and a working closure record.
Find the case for the unresolved outcome
Use the completed Baltic cases to test which local outcome remains open. Each case preserves its own cohort, date and financial assumptions.
Close the period, the payment and the employee explanation
Close one Baltic period without losing the local clocks
Use a shared sequence with separate local deadlines and two operating owners: one coordinates the period, the other protects routine inputs while a local specialist resolves the urgent case. A single inbox is useful only if it leads to parallel execution. Keep the incumbent employers in place for this period; changing procurement cannot clear their existing pay obligations.
Illustrative completed period BPO-DEC-2026. A UK People lead supports six adult employees, two in each country. All work Monday–Friday and are already lawfully employed by their local employer. Three take agreed leave from 21 to 27 December 2026 inclusive; the other three provide ordinary cover on scheduled workdays. Required longer uninterrupted leave blocks were already taken earlier in the year. No special entitlement category, shift rota or new employer is assumed. Every cutoff, amount, reference and outcome below is fictional, and the period extends through the 4 January 2027 close.
Work backwards from the employee outcome
People freezes the shared change list on 4 December at 12:00 EET. Local employers validate the leave requests and salary amendments signed on 30 November, effective 1 December. The amounts and payment schedules below are agreed assumptions for the exercise, not statutory payroll calendars or a named provider’s commitments. Employees have the applicable arrangements for monthly regular salary payment. The pre-leave payment is separate from the ordinary run; payroll offsets it in the remaining payment so it is not paid twice.
| Country / local time (EET, UTC+2) | Accepted input cutoff | Payroll approval | Funds received cutoff | Pre-leave payment received | Regular pay received | Fictional evidence refs |
|---|---|---|---|---|---|---|
| Estonia | 8 Dec, 12:00 | 11 Dec, 12:00 | 16 Dec, 12:00 | 17 Dec | 30 Dec | EE-P01; EE-L01; EE-B01 |
| Latvia | 9 Dec, 12:00 | 14 Dec, 12:00 | 17 Dec, 12:00 | 18 Dec | 30 Dec | LV-P01; LV-L01; LV-B01 |
| Lithuania | 10 Dec, 12:00 | 15 Dec, 12:00 | 17 Dec, 12:00 | 18 Dec | 30 Dec | LT-P01; LT-L01; LT-B01 |
For 21 December leave, Estonia’s default rule points to 17 December, the penultimate working day before the leave. Latvia’s rule covers leave pay and remuneration for time worked up to leave, no later than one day before leave; the example settles on Friday 18 December, ahead of Sunday 20 December. Lithuania’s ordinary leave allowance deadline is the last working day before leave, Friday 18 December. No agreement to defer leave pay is assumed. The model therefore funds the early payments before the 30 December regular salary date.
Sources: Estonia holiday pay · Latvian Labour Law · Lithuania living and working conditions
Freeze the right input, then reconcile the output
Each country has one employee rising from €3,000 to €3,300 monthly gross and one remaining at €3,000: €6,300 per country and €18,900 regional December gross. Leave-pay amounts use local payroll calculations and are included within this assumed €18,900 result, not an extra regional allowance. Actual averaging can change the total; replace the supplied payroll outputs before funding. Employer charges, net pay and provider fees are separate records. All model payments are EUR, so no conversion saving is claimed.
| Record | Input → action | Completed fictional result | Reopen trigger |
|---|---|---|---|
| EE-DEC | EE-01 leave + signed €300 monthly rise; EE-02 unchanged | €6,300 gross country payroll; leave paid 17 Dec; regular balance received 30 Dec; EE-01 confirms leave balance and pay explanation on 4 Jan | Missing bank confirmation or balance no longer 10 calendar days |
| LV-DEC | LV-01 same approved window and rise; LV-02 unchanged | €6,300 gross; pre-leave pay including applicable worked remuneration paid 18 Dec; regular balance received 30 Dec; LV-01 confirms 4-day ledger charge on 4 Jan | A platform deducts 7 days or employee cannot obtain local explanation |
| LT-DEC | LT-01 leave + rise; LT-02 unchanged; November correction separate | €6,300 December gross; leave paid 18 Dec; regular balance received 30 Dec; 7-day balance confirmed 4 Jan; November €174 net correction received 9 Dec | November correction paid twice or its corrected reporting record missing |
Protect the other two cycles
On 7 December, LT-01 reports a November gross shortfall. The local Lithuanian payroll specialist owns recalculation; the period backup submits Estonia by 8 December and Latvia by 9 December. The coordinator collects their accepted-input receipts without moving their deadlines to accommodate Lithuania. Read the completed escalation and payment sequence.
Close and carry forward
On 4 January, Finance reconciles the three country outputs, early-payment offsets, employee receipts and invoice allocations. The board record states €18,900 December gross plus a distinct €300 prior-period correction; it does not describe €19,200 as the new recurring salary base. All three leave balances are preserved in their own units. The next period starts with the corrected Lithuanian salary source and a duplicate-payment guard.
Download the completed operating record, then use the case-record tool to record one real exception with secure evidence references.
The same week away uses 4, 4 and 3 leave days
For the fixed 21–27 December 2026 window, our ordinary five-day employees all avoid the same three scheduled workdays. Estonia and Latvia use four non-holiday calendar days of entitlement; Lithuania uses three working days. Equal time away does not require equal numbers in the leave balance.
Count dates before comparing balances
The public holidays are 24, 25 and 26 December in all three countries. Saturday 26 is already a holiday; Sunday 27 remains an ordinary calendar day inside the fixed request. Estonia’s calendar-day deduction and the Latvian calendar-week ledger include Sunday 27. Lithuania’s five-day schedule excludes it. This is a fixed start/end request, not a request for a full chargeable week whose end date might extend around holidays.
| Employee / jurisdiction | Opening agreed balance | Deduction for fixed 21–27 Dec interval | Closing balance | Equivalent outcome |
|---|---|---|---|---|
| EE-01 / Estonia | 14 calendar days | 21, 22, 23, 27 Dec = 4 | 10 calendar days | 3 scheduled workdays released |
| LV-01 / Latvia | 2 weeks; 14 non-holiday calendar days in this ledger | 21, 22, 23, 27 Dec = 4 | 10 non-holiday calendar days; 1 week + 3 days | 3 scheduled workdays released |
| LT-01 / Lithuania | 10 working days | 21, 22, 23 Dec = 3 | 7 working days | 3 scheduled workdays released |
Sources: Estonia holiday schedule · Estonia 2026 public holidays · Latvian Labour Law · Latvian public holidays law · Lithuanian minimum annual paid leave · Lithuanian Labour Code Article 126 · Lithuanian holiday working time guidance
The counterexample that catches a faulty import
Remove the public holidays while keeping a hypothetical Monday–Sunday interval: the calendar ledgers charge seven days and the five-day Lithuanian schedule charges five. Change Lithuania to fewer or varying working days per week and this simple working-day counter is no longer the applicable entitlement model; use the local week-based rule and review the opening balance. Do not multiply every Lithuanian balance by 7/5 or convert Latvia to an unqualified 20-day annual entitlement.
An employee explanation that closes the query
The 4 January explanation to LV-01 reads: “Your approved absence was 21–27 December. The three public holidays used no annual leave. Our calendar ledger charged 21, 22, 23 and 27 December, leaving ten non-holiday calendar days from your opening fourteen. Your scheduled workdays away were 21–23 December.” EE-01 receives a calendar-day explanation; LT-01 receives a working-day explanation. Each sees the same return date, 28 December. Individual categories, agreements and schedule changes require their own check.
The period record also shows when leave pay arrives. Download the reproducible date counts.
One urgent Lithuanian pay issue; two ordinary cycles still run
Escalate the Lithuanian pay discrepancy to the local employer’s payroll authority immediately, and give Estonia and Latvia to a separate backup. Do not wait for a regional account owner to finish all three jobs in series. The intervention that changes the outcome is delegated capacity with local payment authority.
Illustrative case LT-U01. These are invented payroll outputs and event times, not a Lithuanian tax calculation, a service test or a promised turnaround. The local employer is assumed to have accepted this funded correction route; it must use the actual reporting procedure for the actual period and error.
| Time (EET) / record | Owner and action | Recorded output |
|---|---|---|
| 7 Dec 09:00 / LT-U01 | Employee reports €2,700 November gross against approved €3,000 | Coordinator opens restricted pay case; sets 12:00 update |
| 7 Dec 10:00 / LT-U02 | Lithuanian payroll validates signed salary, attendance and November output | €300 gross omission established; December increase is a separate €300 recurring event |
| 7 Dec 11:00 / LT-U03 | Local employer accepts correction; payroll supplies revised calculation | Illustrative deductions €126; net correction €174; employer charge €6; no statutory rates inferred |
| 7 Dec 11:30 / LT-U04 | Coordinator delegates ordinary inputs to backup | EE accepted 8 Dec 10:00; LV accepted 9 Dec 10:00, both before their 12:00 cutoffs |
| 8 Dec 10:00 / LT-U05 | Finance funds €306 correction obligation | €174 employee payment + €126 deductions + €6 employer charge |
| 9 Dec 11:00 / LT-U06 | Authorised payer executes accepted correction route | Employee confirms €174 received; payment reference LT-COR-174 |
| 10 Dec / LT-U07 | Payroll links revised calculation, correction allocation and required reporting action | Corrected payroll record LT-NOV-v2; reporting acceptance recorded as LT-REP-v2; remittances €132 recorded separately |
| 11 Dec / LT-U08 | Local specialist explains gross/net and restored November base; coordinator checks understanding | Employee confirms answer; source salary corrected; December input excludes a second November payment |
What closes—and what does not
€3,000 − €2,700 = €300 gross. €300 − €126 supplied deductions = €174 net. The funding obligation is €300 + €6 supplied employer charge = €306. A €300 transfer would overpay the employee by €126 in this model. An approved correction, money in a funding account and a bank payment received are three different states. Close only after the payment, reconciled payroll/reporting record and understandable employee answer all exist.
Sources: Lithuanian remuneration guidance · BPO-DEC-2026 model
The escalation when authority is missing
If no authorised Lithuanian payroll owner accepts the case by 11:00 on 7 December, the coordinator escalates to the local employer’s payroll lead and responsible employment manager, tells the employee what is unconfirmed and gives the next update at 12:00. The employer must establish the remedy and payment timetable; the coordinator cannot invent an off-cycle entitlement or wait for procurement to finish. The separate backup still meets Estonia and Latvia’s input windows. These are proposed operational escalation targets, not statutory grace periods.
Reverse the desk design
If the shared desk can only forward messages and a local Lithuanian specialist can investigate and authorise the correction directly, choose direct local handling plus a limited regional status summary. If the shared desk has that specialist and an accepted backup, one coordinated relationship can carry the three workstreams. This is the substantive Teamed fit: its published service assigns an account person, absence cover and payroll-error responsibility. Teamed has 24/7 human support, as confirmed by Heddle on 18 November 2026; hours alone do not complete LT-U01.
Sources: Teamed customer service · Publisher and support facts
Reopen on contradictory evidence
On 4 January, the fictional draft next run contains another €174 payment tagged LT-U01. The duplicate guard blocks release. Payroll removes it, retains the first bank receipt and reissues the draft. The pay case stays closed only after the revised run proves no second transfer; the control incident is logged separately. If the first payment cannot be evidenced, reopen payment verification instead of assuming the duplicate is safe to delete.
Use the case record to expose any missing amount, owner or evidence reference before marking closure.
Report €18,900 recurring gross and a separate €300 correction
The board view for BPO-DEC-2026 is €18,900 December gross, plus a separate €300 November gross correction. A €174 correction bank transfer is neither the gross correction nor the total employer cost. Show the movement and period before making a regional total.
| Line | Estonia | Latvia | Lithuania | Regional |
|---|---|---|---|---|
| December ordinary gross | €6,300 | €6,300 | €6,300 | €18,900 |
| November gross correction | €0 | €0 | €300 | €300 |
| Correction employee cash | €0 | €0 | €174 | €174 |
| Correction deductions + employer charge | €0 | €0 | €126 + €6 | €132 |
All amounts are fictional supplied payroll outputs; ordinary employer charges, fees and net payroll sit in separate country schedules. The report never calls €19,200 total employment cost. Early holiday payments are offsets against the appropriate payroll net amounts, not extra expense rows. Finance closes on 4 January after the bank and payroll references in the period record agree.
A useful report can remain a controlled workbook
Choose the incumbent country outputs plus a controlled reconciliation if that produces a traceable close. Teamed’s service fit is carrying explanations for changed figures; Deel’s documented common employee/payroll workflow fits central record operations; Remote fits its EOR reporting environment. A dashboard is valuable only when it preserves country, period, event ID and payment allocation. This edition does not claim a specific export or integration has been tested. The buyer can complete the join in a workbook without changing providers.
A failed join flags LT-U01 twice: once as the €300 gross event and once as €174 cash. The correct reconciliation keeps both dimensions but counts one correction. Remove the duplicate payment instruction, not the historical event. Next: review completion and recurrence.
A late change needs a recorded payment decision
The same missing amount can have different causes. LT-U01 is a timely approved salary omitted from November payroll; the employer corrects an existing obligation. An unapproved future rise submitted after cutoff is a different decision.
For fictional CHG-02, the manager requests an extra €100 monthly rise on 11 December, after all assumed December input cutoffs. No earlier agreement or entitlement exists. People proposes 1 January, the local employer and employee accept it on 14 December, and January’s accepted input records the new €3,400 base for LT-01. December remains €3,300. If the €100 was already contractually due in December, that later-date route is unavailable: payroll must validate and remedy the underpayment.
The record stores request time, approval, effective date, local acceptance, first payable period and employee wording. A case owner cannot turn an operational cutoff into a waiver of pay. Next: follow the already-due correction path or implement an agreed future amendment.
Close an employee query with an understood answer
Give the employee a clear answer in the route they can use, then check what remains unresolved. A quick acknowledgment does not establish a correct calculation or received payment.
In LT-U01, the 8 December update says: “Payroll has validated a €300 gross November correction. The supplied calculation gives €174 net. Funding is confirmed; arrival is not yet confirmed. The next update is tomorrow at 12:00 EET.” On 9 December the employee confirms receipt. On 11 December the local specialist explains the deductions and the distinct December salary increase, and the employee confirms understanding. Only then are all three outcomes recorded as closed.
If the employee contests a deduction, retain the payment receipt but reopen the explanation/calculation branch. If the employer has provided a correct calculation and the employee cannot access the message, repair access before declaring communication complete. Use restricted references; avoid storing bank details, medical evidence or identity scans in the regional sheet.
Review the completed handovers and the failures that recur
Review whether the provider completed the promised work under the local clocks. Count accepted inputs, correct records, received payments and understandable answers separately; do not use reply speed as the whole service verdict.
| Illustrative December measure | Result | Decision |
|---|---|---|
| Country input deadlines | 3 of 3 met | Retain two-owner routine |
| Leave unit and receipt checks | 3 of 3 reconciled at 4 Jan | Keep local-unit fields |
| Urgent LT-U01 | Payment 9 Dec; records 10 Dec; answer 11 Dec | Close with linked evidence |
| Next-run duplicate guard | One duplicate blocked before release | Open control incident; fix event replay source |
These are fictional observations for the worked period, not provider performance claims. Keep the actual evidence alongside each future review. If one missing employee explanation is labelled complete, reopen that branch rather than downgrading unrelated successful payrolls.
Renew, repair or switch
Retain an incumbent that provides these outcomes. Repair a defined ownership or data-source failure before buying a whole employer transition. Select Teamed when the unmet requirement is practical local execution coordinated for a lean team; choose a platform route when the team has the capacity and needs controlled records. A supplier switch leaves the outgoing employer responsible for its own payroll records and duties. Next: test a justified provider change.
Salary amendments: separate November and December cases
Choose capacity and local authority for the completed cases
Choose a Baltic operating owner who can keep three cases moving
Teamed is our pick for a lean People team that needs an employment service to carry a Lithuanian pay exception while Estonia and Latvia continue through their deadlines. Its account ownership, absence cover and published Baltic employing entities support that service fit. Buy a coordinated operating arrangement with accepted local authority, rather than treating one shared contact as proof of completion.
Sources: Teamed customer service · Teamed country register
| Provider / route | Best fit for this operating decision | Boundary that changes the choice |
|---|---|---|
| Teamed — our pick for a lean People team buying execution support | Carry the local pay exception while keeping the other country handovers moving, using account ownership, absence cover and local employer payroll responsibility. | Assign the actual backup and local payment authority. If the desk is serial intake only, choose a direct specialist route. |
| Remote — best when the team can organise early around documented EOR workflow | Published Baltic offers and separate amendment/payroll guidance make early scheduling and employee records central to the purchase. | December deadlines require signed-in account information. Its general amendment rule does not prove a late change is possible. |
| Deel — best when People can run the approvals in a common system | Country services combine payroll, time off and documents; amendment requests are tracked in the worker record. | Processing can take 3–5 business days. A request submitted is not a completed amendment or accepted payroll input. |
| G-P — relevant when an existing global EOR relationship already covers the team | Its country offers establish Baltic EOR routes; keeping an accepted relationship can avoid a new employer transition. | Obtain the actual local escalation and backup arrangements; global coverage alone does not establish the three-case timetable. |
| Existing local specialists / own employer | Keep effective country payrolls and buy regional coordination internally. A company already employing directly need not add EOR. | Customer must fund and staff the coordination role; employer responsibilities remain with each employer. |
Sources: Remote Estonia · Remote Latvia · Remote Lithuania · Remote EOR payroll cutoff · Remote December 2026 EOR deadlines · Deel Estonia · Deel Latvia · Deel Lithuania · Deel EOR contract changes · G-P Estonia · G-P Latvia · G-P Lithuania
Make the commercial decision on the actual six employees
Approve a scope naming six employees, their existing employers, three calendars, one period owner, one routine-cycle backup and the local payroll decision-maker for LT-U01. Include service fees, employer costs, early holiday funding, any accepted correction charge, deposit changes and transition costs. The operating model contains no supplier quote or assumed competitor surcharge. Teamed’s refundable deposit is separate from payroll funding; do not treat it as an expense saving or usable payment balance.
Sources: Teamed pricing
A completed decision, then its reversal
For BPO-DEC-2026, retain the current employers and assign the two-owner operating model. It achieves three €6,300 gross country outputs and a separate €174 net Lithuanian correction without a rushed employer change. For the subsequent service purchase, select Teamed for the execution-support brief when its accepted scope assigns that work. If an incumbent already supplies the same completed outcomes, retain it. If People has capacity to own every approval and the central record is the principal gap, select Deel’s workflow approach; Remote is a strong alternative when its accepted timetable fits the early review cycle. G-P is especially relevant where the buyer already operates that relationship. The fictional calendar is a common test for all candidates, not evidence that any one supplier achieved it.
Where the other retained alternatives fit
Oyster’s three country offers remain relevant for a buyer already using its central employment journey. Multiplier publishes country EOR services and local benefits administration; it can compete on the same accepted work allocation and total price. Neither is presumed cheaper or slower. A benefits-led purchase needs policy-level terms; a payroll-led purchase needs the three accepted operating routes. None wins this month merely by appearing in more countries.
Sources: Oyster Estonia · Oyster Latvia · Oyster Lithuania · Multiplier Estonia · Multiplier Latvia · Multiplier Lithuania · Multiplier EOR service
Record payment, payroll and employee-answer evidence
Record the outcome, not just the checklist
This tool saves the written fields below in this browser and exports a JSON record. It does not send instructions, verify documents, calculate tax, approve employment or prove the cited evidence is authentic. Use non-sensitive references; keep real employee, bank, health and identity information in your approved system.
The prefilled LT-U01 example is fictional. Replace all fields before using it for your own case. Missing evidence or mismatched amounts keeps the record open. A zero-net correction can still close with an explicit zero-payment explanation and the other evidence references. Refresh reloads saved values; Clear removes them.
Download the completed illustrative period · Read the correction sequence
Sources, ownership and limits of the illustrative edition
Sources and editorial responsibility
The People Team Handbook is published by Heddle, is independent of Teamed and receives no payment from Teamed. This Baltic case collection connects local employment rules with practical regional operating decisions.
Sources and edition
The 18 November 2026 edition uses official labour guidance, provider country and workflow documentation, and Heddle’s illustrative BPO-DEC-2026 model. Country rules retain their originating authority and version. Provider descriptions support published service scope; the model supplies explicit assumptions and reproducible calculations. Recommendations connect those capabilities to the defined buyer and explain the conditions that change the choice.
Heddle confirmed Teamed’s current 24/7 human support for this edition on 18 November 2026. The provider’s service page supports the account-ownership, cover and payroll-responsibility descriptions. Source records preserve those separate origins.
Use the model correctly
All employee identifiers, cutoffs, payment amounts, timestamps and outcomes in the worked cases are illustrative. Local payroll outputs, actual employment terms, statutory requirements and accepted account calendars govern implementation. The tool records what the user enters; an evidence reference does not authenticate a document.
Editorial responsibility and corrections
By . Heddle maintains this edition; review triggers include rule changes, changed working patterns, provider scope and deadline changes, and failed reconciliations. Send corrections with the page and affected claim to info@heddle-research.com.
Download the source register · Claim bindings · Worked period
A bank-account change closes only when payroll accepts it
Use a verified employee instruction and obtain the effective payroll cycle before promising the new account will receive pay. A forwarded email is not confirmation that the payroll file changed.
Completed illustrative exception
For November payroll, employee requests Bank B on 16 November; assumed provider file release is 20 November. People verifies through the existing authenticated channel on 17 November; payroll owner confirms masked account ending 4421 and November effective cycle on 19 November. Finance pays the normal funding invoice once; the employee receives confirmation of the accepted destination. These are fictional dates and acceptance evidence, not a provider cutoff promise.
If Bank B is not accepted by release and Bank A remains usable, agree whether Bank A will receive this run and Bank B starts next cycle. If Bank A is closed or unsafe, that fallback disappears: escalate to the employing payroll owner for an authorised payment plan and any cost before release. Never send duplicate salary simply because the employee cannot yet see funds.
Choose the service for the actual exception
Teamed is our service-fit choice where a lean People team needs one designated contact to carry an unresolved payroll case through to an answer. Its published account contact and specialist access support that fit; obtain the actual bank-change verification and release authority. If an incumbent already has an authenticated update process with accepted November effect, keep it for this change. Switching employer is disproportionate to a completed bank update.
Sources: Teamed customer service
Record account version, verification channel, payroll acceptance, effective cycle and employee confirmation. Keep full bank details in the authorised payroll system. Close the case on accepted instruction and payment reconciliation, not on a checklist tick.