Run an EOR and your own entity without losing the employer boundary

One region, three operating routes

Harbour Instruments is a fictional group with eight employees: three employed by its Estonian subsidiary, two by an EOR in Latvia and three by its Lithuanian subsidiary. Estonia uses an external payroll bureau; Lithuania has an internal preparer. The regional operations lead supervises all eight, but that does not make the regional team the legal employer of all eight.

The operating map below keeps the current employer visible. It deliberately uses an unnamed EOR and bureau: the records illustrate a purchased service and internal decisions, not a claim about a particular supplier’s contract. No route change is planned this month.

The completed employer and instruction map

EE-OWN: Harbour Estonia is the employer. Its manager approves the employment decision, the bureau prepares payroll, the Estonian controller approves the calculation and treasury releases payment. Employee pay questions go to the local HR coordinator, who obtains the bureau’s explanation.

LV-EOR: the EOR’s Latvian entity is the employer. Harbour’s manager requests a change through the agreed EOR route; the EOR accepts the employment instruction and prepares the payroll. Harbour’s controller reviews the funding request. The EOR handles the employment/payroll question through its contracted contact route.

LT-OWN: Harbour Lithuania is the employer. Its HR administrator prepares employment changes, the internal payroll specialist calculates them, and the Lithuanian director approves release. A finance deputy has documented authority during the director’s absence. The employer record identifies that deputy, not simply the regional operations lead.

A salary change that stops in the right place

The Latvian manager emails a proposed gross monthly salary change from EUR3,000 to EUR3,200, effective next month. In the fictional case, the business approves the budget but the EOR has not yet accepted the employment change. The controller therefore records “budget approved; employment acceptance pending” and does not alter the current payroll funding file.

The EOR later returns an accepted instruction reference LV-CHANGE-07 with the effective period. Finance checks that reference against the next funding request. The current month stays EUR3,000; the next period carries EUR3,200 in the underlying salary input. These illustrative gross salaries are not net-pay estimates or total employer costs. The EUR200 change is not copied into Estonia or Lithuania simply because the same manager oversees those employees.

Show three cash routes, not one unexplained Baltic total

Harbour’s fictional close contains EE-OWN EUR12,400 total payroll funding, LV-EOR EUR9,100 EOR invoice and LT-OWN EUR11,800 total payroll funding. The EUR33,300 aggregate is a cash planning figure, not a like-for-like salary comparison. The Latvian invoice includes a service component; the other routes may have separate supplier invoices.

Finance keeps each underlying schedule and separates salary-related amounts, employer charges, supplier fees and any security cash. In this example all three payments are EUR-to-EUR, so the close records no currency-conversion saving. If a group funds a future route in sterling, it should add the conversion basis and provider markup as separate fields rather than compare a sterling bank debit with a euro salary total.

Resolve a payslip question without changing the employer

A Lithuanian employee queries a EUR150 difference. The HR coordinator checks the employee reference and period, then the payroll specialist identifies a duplicated voluntary-benefit input in this fictional test. The specialist prepares the correction; the Lithuanian director authorises it through the applicable process; the coordinator explains the correction and timing to the employee.

The regional lead sees the status and the correction reference, not the employee’s sensitive case file. The Latvian EOR is not assigned this Lithuanian investigation. One regional inbox can coordinate visibility, but it must not blur which organisation prepares, approves or communicates each action.

The absence test that makes the map usable

Run the same salary-change record with the usual approver away. In Harbour’s Estonia test, the deputy has access to the calculation but no payment authority. That is a failed test, even though the payroll bureau completed its work. Treasury adds the approved deputy arrangement before the funding day and records the retest result.

The finished monthly record has three employer rows, three funding routes and explicit open exceptions. A provider purchase becomes relevant when one of those work packages lacks capacity. It does not require all three countries to use the same employment model.