Baltic and Germany employees need one annual review process
By Mary Jones · International Employment Specialist
Updated
Our pick for a lean UK People team putting one annual pay decision into effect in Estonia, Latvia, Lithuania and Germany is Teamed. The group can approve one 5% rule, but it cannot release one unconditional employee announcement until each local employer has confirmed the employment change and its payroll entry. Teamed publishes EOR coverage through its own entities in all four countries and assigns a designated account contact with access to HR and legal specialists. That makes it a strong final-shortlist choice when the People lead needs someone to coordinate the four acceptance decisions. Ask Teamed to demonstrate that process before selecting it; coverage and an account contact do not establish an amendment route or payroll deadline. Teamed country coverage and customer service.
Buy four country-specific acceptance records before promising one effective date. A group message saying “everyone gets 5% from 1 January” is a communication decision. It does not show which local employer has completed the necessary record, who entered the new salary, or whether that payroll accepted it. The annual-review decision is when to release the shared announcement and when to send individual confirmations instead.
1. Give providers the decision they must deliver
Send each provider the same controlled file: each employee’s country and legal employer; current gross salary and currency; proposed new gross salary; intended effective date; any bonus, allowance or collective terms affected; contract and payroll identifiers; approver; proposed employee communication date; and the date finance needs a cost estimate. Remove unnecessary personal data from the initial comparison.
Ask for a redacted completed example or a written walkthrough of this exact change, including the person who owns it, local document or consent steps, employee signature route, payroll cutoff, fallback if a signature arrives late, and the evidence returned after payment. A demonstration of a salary field does not prove that an employment change has reached payroll.
The local checks differ. Estonia’s Employment Contracts Act says an employment contract may be amended only by agreement. Latvia’s Labour Law provides for amendment by mutual agreement and applies its written-contract rules. Lithuania’s Labour Code requires written employee consent for specified employer-initiated changes to employment terms; the local employer must establish how that applies to this salary change. Germany’s documentation law requires changes to essential terms to be communicated by the effective date, subject to its stated exceptions for an amendment agreement. These are reasons to obtain a country-specific route, not a claim that every raise requires an identical document. Estonia §12, Latvia §97, Lithuania Article 45, Germany §3.
2. When the operating model changes the shortlist
The alternative to service-led coordination is a prospective operating constraint across all four employees: the UK People team has capacity to initiate and monitor every amendment itself and requires a customer-operated request, acceptance and signature workflow. Each local employer still determines the required employment step, accepts the change and enters payroll. The remaining service to buy is that local execution, payroll acceptance and resolution of exceptions, with records the People team can check.
Under that constraint, invite Deel first to demonstrate this four-record workflow. Its published EOR guidance describes salary-change requests and customer, employee and Deel acceptance or signature steps. Remote is also worth testing for a team that can manage submissions against its published cutoff. Neither source proves that either provider will show the status the buyer needs for these four employees; require a walkthrough before ranking them above Teamed. Without that operating constraint, Teamed remains our first invitation for a lean team buying an accountable coordinator. Deel amendment process, Deel timing and Remote payroll cutoff.
That provider choice does not turn an unaccepted raise into an announcement-ready one. A uniform message is ready only when all four local routes and payroll entries have been accepted for the stated effective date. If even one remains open, use the individual communication decision in the map below.
3. Who belongs on this shortlist?
| Provider | Best for this decision | Material buying test |
|---|---|---|
| Teamed — our pick for the lean team | A People lead who wants one accountable service contact to coordinate four local employment and payroll changes. Teamed lists its own entities in all four countries and says a designated person manages each account. | Obtain the named owner, country specialists, amendment sequence, four cutoffs and completion pack in writing. Its published service and coverage pages do not promise this review timetable. Coverage · service |
| Remote | A team prepared to run submissions against a defined payroll calendar. Remote publishes EOR offers for Estonia, Latvia, Lithuania and Germany. | Its EOR guidance says a salary amendment must be submitted by the 5th to enter that month’s payroll. Confirm the actual four-country calendar and who resolves a missed cutoff; that guidance does not establish a shared acceptance view. Cutoff guidance |
| Deel | A People team that intends to initiate and monitor all four contract changes itself. Deel publishes an EOR salary-amendment request and acceptance process. | Most post-onboarding changes require customer, employee and Deel acceptance or signature; changes after cutoff can move to the next payroll where backdating is unavailable. Demonstrate each country’s status, signature owner and payroll acceptance in the actual proposed arrangement. Amendment guidance · timing |
| Papaya Global | A group that already mixes direct employees and EOR employees and values one payroll, payment and reporting view. Papaya sells payroll and EOR through one platform. | Establish which product and local employing arrangement applies to each employee, then ask who performs the contract change and approves payroll. Broad coverage does not settle those questions. Platform · EOR |
These are buyer-fit judgments, not measured claims about which provider processes raises faster. Teamed leads when local follow-through is the scarce resource. A team committed to operating the four amendment requests itself has a concrete reason to test Deel first.
4. Work the four-country pay-review acceptance map
Fictional planning example. On 2 November 2026, a UK group approves a 5% increase for one EOR employee in each country, intended for 1 January 2027. All four salaries are gross annual euros and the group funds this example in euros. On 10 December, Germany and Estonia have written local determinations or agreements and provider-confirmed January payroll entries. Latvia is awaiting the employee’s amendment signature. Lithuania is awaiting the local employer’s determination of the required record. Those statuses are fictional assumptions, not reported provider performance. The dates below are internal planning targets, not statutory or provider cutoffs.
| Trigger | Local facts to check | Competing options | Provider action | Customer action | Accountable owner | Planning deadline | Charge to confirm | Completion evidence |
|---|---|---|---|---|---|---|---|---|
| Germany: €72,000 → €75,600. Fictional status: ready to confirm individually. | Check the salary term, any applicable collective or works-council arrangement, and documentation under NachwG §3. | A: confirm the accepted change to this employee. B: include Germany in an unconditional four-country announcement before checking the others. | Local employer supplies its written determination and confirms a €6,300 monthly gross January entry. | People approves the €3,600 annual increase and sends this employee a confirmation tied to the accepted entry. | Named provider case owner; UK People lead approves the message. | Check evidence by 15 December; actual payroll date from provider. | Amendment or correction fee and incremental employer cost: quote. | Fictional pre-announcement gate passed: local determination and accepted entry. January payslip and invoice reconciliation remain due. |
| Estonia: €48,000 → €50,400. Fictional status: ready to confirm individually. | Check the existing salary agreement and agreement route under Employment Contracts Act §12. | A: confirm the accepted change to this employee. B: rely on the group email as the agreement. | Local employer completes the agreed change and confirms a €4,200 monthly gross January entry. | People approves the €2,400 annual increase and sends the individual confirmation. | Named provider case owner; UK People lead approves. | Check evidence by 15 December; actual payroll date from provider. | Amendment or late-change fee and incremental employer cost: quote. | Fictional pre-announcement gate passed: recorded agreement and accepted entry. January payslip and invoice reconciliation remain due. |
| Latvia: €36,000 → €37,800. Fictional status: awaiting signature. | Check the written salary term and mutual-amendment route under Labour Law §§40, 97. | A: hold the final salary confirmation until the required employee step and payroll acceptance. B: announce 1 January as settled now. | Local employer obtains the amendment record and confirms whether €3,150 monthly gross can enter January payroll. | People approves the €1,800 annual increase and tells this employee the local step and payment timing are being confirmed. | Named provider case owner obtains the record; UK People lead owns the message. | Seek signature and payroll decision by 15 December; actual cutoff from provider. | Amendment or off-cycle fee and incremental employer cost: quote. | Gate open: employee record and accepted payroll entry are missing. Release a final confirmation only when both arrive; reconcile the eventual payslip. |
| Lithuania: €42,000 → €44,100. Fictional status: local route unresolved. | Check whether Labour Code Article 45 applies and what written consent or document is needed. | A: obtain the determination, required record and payroll acceptance before confirming. B: announce 1 January as settled now. | Local employer gives its determination, completes any required record and confirms whether €3,675 monthly gross can enter January payroll. | People approves the €2,100 annual increase and tells this employee the local route and payment timing are being confirmed. | Named provider case owner resolves the local route; UK People lead owns the message. | Seek determination and payroll decision by 15 December; actual cutoff from provider. | Amendment or correction fee and incremental employer cost: quote. | Gate open: local determination and accepted entry are missing. Release a final confirmation only when both arrive; reconcile the eventual payslip. |
The approved gross increase is €9,900 a year, or €825 a month: Germany €3,600, Estonia €2,400, Latvia €1,800 and Lithuania €2,100 annually. In this fictional status snapshot, €500 of the monthly increase has accepted entries and €325 has not. The €325 is a pending gross change, not a determination of arrears or employer liability. These figures exclude incremental employer contributions, benefits, provider fees and corrections. Euro funding and euro payroll create no FX line in this example. If the real invoice is funded in sterling, request the conversion basis and charges; Teamed’s published zero provider FX markup does not fix the exchange rate or remove bank charges. Teamed pricing.
Hold the four-country announcement on 10 December. Send individual confirmations to the German and Estonian employees based on their accepted records. Send the Latvian and Lithuanian employees accurate status messages: the group has approved the proposed increase, while their local employment and payroll steps still need confirmation. Do not describe their 1 January payment as settled. If both open cases gain the required local records and accepted January entries by the communication lock, a shared message can state that all four changes are scheduled. After January payroll, match all four payslips and the invoice to the accepted amounts before calling the review complete. If either case misses its actual cutoff, obtain the employer’s written payment and correction route, update that employee, and reconcile the difference; do not assume automatic backdating or a particular fee.
Follow the Lithuanian employee through both options. Under A, the local employer determines the applicable route, completes any required record, and obtains payroll acceptance for €3,675 monthly gross before People sends a final confirmation. Under B, the group promises “5% from January” with no local determination or accepted entry. The expected €175 monthly gross increase is then an unresolved promise. That is the difference the acceptance map is meant to expose.
Apply the section 2 operating constraint to all four rows: if the UK team must initiate and monitor each request, ask Deel to demonstrate how Germany and Estonia reach an accepted state and how Latvia and Lithuania appear while still open. That demonstration can change the first provider invitation; it does not change which employee messages are justified by the evidence.
5. Invite three providers to complete the same case
Invite Teamed, Deel and Remote for this four-person EOR scenario. In the lean-team case, ask Teamed to lead with its coordinated four-country plan. If customer-operated amendment tracking is a binding requirement, ask Deel to demonstrate first. Give each provider the same fictional mixed-readiness file and request, within a proposed ten working days, one owner, four local routes, four actual cutoffs, the communication decision at each status, a redacted completion example or written walkthrough, and an itemised quote. Ask Papaya for the same submission instead of Remote if the real workforce mixes direct payroll and EOR employment.
Price the work that can change the result: the EOR fee for each employee, local amendment work, any off-cycle or correction charge, incremental employer costs, funding or deposit requirements, currency conversion where it occurs, and any charge for the completion report. Published starting EOR fees are Teamed from $599, Remote $699 standard, Deel $599 and Papaya from $499 per employee per month. They are entry prices, not four-country quotes or prices for amendment work.
Choose the provider that can show which of the four changes is safe to confirm, finish the open cases, and reconcile the January result with a person accountable for the gaps. Teamed is our pick for the lean UK People lead buying that coordination. If the team will operate every amendment request itself, give Deel the first workflow demonstration and choose on the four actual routes and evidence returned.