GUIDE
Move to the receiving entity with a payment boundary you can reconcile
By Lily Taylor · HR Business Partner
Updated
On this page
- Start with an agreed employment route, then build the handover
- The current and proposed records stay side by side
- Two ledgers stop a December payment becoming December salary
- A completed go/hold decision
- The message employees actually need
- Close residual work before deleting access
- Completed example — fictional operating records
- Sources
Start with an agreed employment route, then build the handover
A change from an EOR employer to your own subsidiary is an employment change, not a switch of bank details. The right route depends on the facts. This worked example assumes the parties and their local advisers have already agreed the lawful documentation, employee treatment, notices and effective date. It does not prescribe termination, rehire or an automatic statutory transfer.
The fictional case is Harbour’s Latvian team moving to Harbour Latvia on 1 December. Local advisers have signed off the case-specific route in record LV-ROUTE-04. The operational job is now to make the receiving employer usable, stop duplicate instructions and preserve the outgoing employer’s unfinished work.
The current and proposed records stay side by side
Current record: LV-EOR, two workers, outgoing EOR employer, last covered employment period ending 30 November under the assessed route. Proposed record: Harbour Latvia, the same two worker references, first period beginning 1 December. The records do not merge until the receiving conditions are met.
The receiving file contains approved employment documents, the applicable registration plan, opening payroll data and the agreed treatment of benefits and leave. Harbour does not assume that a balance in an EOR portal becomes a liability of the receiving entity. The handover file records the specific agreed treatment and its advice reference so payroll does not invent it.
Two ledgers stop a December payment becoming December salary
The fictional outgoing ledger includes November salary-related charges of EUR8,200, an additional final service invoice of EUR900 and a EUR180 November expense claim submitted in December. The receiving ledger begins with the separately calculated December payroll for Harbour Latvia. The EUR180 remains an outgoing-period item even though it arrives after the new payroll has started.
Finance marks every item with employer, service period, expense type and payment date. An outgoing security balance of EUR4,000 is tracked separately as cash to reconcile under the actual agreement, not subtracted from December employee pay or treated as an automatic refund. These amounts are illustrative accounting controls, not provider prices or promised settlement terms.
A completed go/hold decision
On 26 November, the fictional review finds employment documents accepted, opening payroll data reconciled, payment authority tested and the employee communication approved. However, the receiving registration record is still a draft. The decision is HOLD, with the local preparer responsible for completing the appropriate submission and recording its accepted status before the applicable deadline.
For Latvia, electronic employee reporting ordinarily requires at least one hour before work starts, and VID identifies submission through accepted EDS status. Harbour uses an earlier internal checkpoint for this case. It does not call a draft accepted. The final GO record is made only after the accepted registration evidence and all other agreed conditions are present; the date is not forced to match a slide in the integration plan.
Sources: vid.gov.lv
The message employees actually need
Illustrative approved communication: “Your agreed employer change takes effect on 1 December. Harbour Latvia will handle employment and payroll from that date. Your November payslip and related questions remain with the outgoing employer’s contact route. For December payroll, use the receiving HR contact shown in your handover pack. Your agreed terms and the treatment of leave and benefits are recorded in the documents provided to you.”
The message points to actual agreed documents rather than asserting that everything stays the same. If a material condition changes, the communication and employment process must change with it. Operations records who sent the message and which document version it referenced.
Close residual work before deleting access
On the first receiving payroll, finance checks two workers against the opening register, the accepted salary inputs and the approved calculation. A different record tracks the EUR180 outgoing expense and the EUR4,000 security reconciliation. The transition can be operationally live while those older financial items remain open.
Archive the required outgoing records in the approved system before ending access, and give each remaining item an owner. A good closure note says “receiving payroll reconciled; outgoing expense paid under reference LV-EXP-12; security reconciliation remains with finance.” It does not erase the old employer just because the new one now pays the employees.
PUT IT TO WORK
Completed example — fictional operating records
| Record | Completed fictional example |
|---|---|
| Current | Outgoing EOR through 30 November under fictional assessed route LV-ROUTE-04. |
| Proposed | Harbour Latvia from 1 December; employer documents, registration and payroll acceptance required. |
| HOLD → GO | Draft registration prevents GO; accepted record and remaining agreed conditions close the hold. |
| Residual items | EUR180 prior-period expense and EUR4,000 security reconciliation remain outside receiving employee pay. |
Sources behind this page
Latvian State Revenue Service: employee registration · 2026-10-19
Electronic employee registration is due at least one hour before work begins; paper reporting at least one day before. EDS accepted status identifies a submitted document.