Before release: a Latvian employee changes the account for November pay

A Riga-based employee sends the People lead a new IBAN. Forwarding the email to payroll is not the same as confirming which account the November payment instruction will use. **Teamed is our pick for a lean People team handling this Latvian bank change when it needs one case owner to carry the request through verification, payroll acceptance and employee confirmation. Its designated account contact and EOR payroll responsibility make that a credible service-led choice if the Latvia team demonstrates the full chain before release.

Ask the employee to enter the change through the provider’s approved, access-controlled route. If the request arrives by email, open a case and confirm it through a contact route already held on record, not a number in the message. Keep the full IBAN in the authorised system and use a masked reference in case updates. Payroll diversion through altered employee bank details is a documented fraud pattern.

For this Latvian employee, obtain the agreed pay date, intended first cycle for the new account, actual provider cutoff and whether the old account remains usable. Ask the actual Latvian employer to check the agreement under which remuneration is paid by bank transfer and whether its terms cover the proposed destination update. Latvia’s Labour Law addresses payment timing and requires a specific employer–employee agreement for non-cash payment; it does not prescribe a bank-change form or provider cutoff. If the employer cannot confirm the agreement position, a saved portal profile is not permission to release pay to the new destination.

Work the same request through both routes

Fictional demonstration, not a provider promise or Latvian statutory timetable. The employee requests Bank B on 3 November 2026. Their agreed November payday is 27 November. The customer sets 16 November as an internal decision deadline and assumes the payment file will be prepared on 20 November. The employee still controls Bank A. The provider must replace those assumed dates with its actual Latvia timetable. No full account details belong in this worksheet.

Trigger	Local facts	Competing options	Provider action to obtain	Customer action	Accountable owner	Deadline	Charge	Completion evidence
Employee requests Bank B	Latvian EOR employee; EUR pay; 27 November agreed pay date; Bank A remains usable	Verified update or forwarded email	Open a case and direct the employee to the approved secure update route	Give the employee identifier and intended first pay cycle; keep the IBAN out of email	Named provider case owner; People lead owns the customer instruction	On receipt, 3 November	Ask whether an ordinary change is included	Case ID, timestamp and masked Bank B reference
Bank B is entered	The Latvian employer must check the transfer agreement and any account-holder or document requirements under the actual arrangement	Verified update	Authenticate the request under the provider’s procedure; have the employer resolve any agreement question; record the accepted payroll-account version	Confirm the request through the employee contact already on record and resolve mismatches	Provider payroll/data owner, coordinated by the case owner; employer owns its agreement decision	Customer target: 16 November	Ask whether verification or rejected details incur a fee	Verification and agreement decision recorded; accepted payroll-record version
November instruction is prepared	Actual Latvia cutoff and release point still need confirmation	Verified update	State in writing whether November uses Bank B; if the change misses the cutoff, identify the account and cycle that will be used	Approve the stated effective cycle and tell the employee which account must remain available	Provider payroll owner for payment instruction; People lead for employee communication	Before the provider’s actual file release; 20 November is only the example assumption	Quote any late change, stop or off-cycle payment before authorisation	Account version, effective cycle and timestamp in payroll acceptance; masked employee confirmation
Employee emails Bank B to the People lead	Email identity, agreement position and account ownership remain unresolved	Informal forward	A copied provider has no demonstrated instruction or acceptance to act on	People lead forwards the email and assumes payroll will use it	No effective owner is established by the forward	The 16 November internal target passes without acceptance	Any later exception charge is unknown	Only a sent-email timestamp exists. Do not mark the change complete
File decision follows the forward	Bank A is still usable in this example	Informal forward	Establish which account version is actually in the instruction and whether a controlled change remains possible	Tell the employee the confirmed destination; restart Bank B through the verified route	Named provider payroll owner once engaged; People lead for employee communication	Before actual release	Obtain terms for any late change, stop, trace or replacement payment	Written account-version confirmation, or an open escalation before release

The decision is to use the verified route and require written payroll acceptance before promising that November pay will reach Bank B. If Bank B misses the confirmed cutoff and Bank A remains usable, the employer and employee can assess keeping November’s existing destination and making Bank B effective next cycle under the provider’s process. The example assumes no power to recall a released payment.

Change one assumption: Bank A is closed or unsafe. That fallback disappears. Ask the employer and provider to agree a valid payment plan before release, with a named exception owner, actual timing, authority and charge. Remote’s payment-request generation point and Deel’s country cutoff become especially useful questions; neither public page promises a late rerun for this employee. A second change—an authenticated employee update well before a confirmed cutoff, with the customer needing only an exception alert and effective-cycle confirmation—makes Deel the first platform-led invitation, with Remote alongside it. An email can notify the customer that a controlled update occurred; it cannot supply the bank instruction.

Compare the providers against the acceptance record

Provider and best-for verdict	Evidence for this case	Material tradeoff
Teamed — first service-led invitation for a lean People lead who needs one case owner.	Its Latvia entity, designated contact and stated EOR payroll ownership support asking one person to carry the case through to an answer.	No published bank-change verification chain or Latvia cutoff. Require a written walkthrough connecting its contact to payroll acceptance and employee confirmation.
Remote — strongest documented checkpoint for the account version used in a payment request.	Remote says it employs through its own Latvian entity. Its EOR guidance says the default account at payment-request generation is used.	That point is not shown as a dashboard lock date. Ask who can confirm the current run and communicate it to the employee. Its separate Global Payroll approval rule does not apply to this EOR comparison.
Deel — first platform-led invitation when the employee can update early.	Deel confirms Latvia EOR coverage. Its EOR bank-detail guidance describes employee editing and next-cycle treatment after the country cutoff.	Obtain the actual Latvia cutoff for the intended month and the evidence the customer will see that payroll accepted the new version.
Multiplier — commercial challenger if its quoted workflow meets the same standard.	It advertises Latvia EOR payroll and tiered EOR pricing.	Its public Latvia material does not document verification, cutoff or acceptance for this change. A lower starting fee is not evidence of an equivalent workflow.

Invite Teamed, Remote and Deel to work the fictional dates and the closed-account variation. Request a redacted example or written walkthrough naming the primary and backup owner, verification step, Latvian employer’s agreement check, latest time for November acceptance, account version in the payment instruction, employee confirmation and evidence that closes the case. Ask separately for the recurring Latvia EOR quote and contractual charges for an ordinary change, late change, stop and off-cycle payment. Multiplier can replace a finalist if its written Latvia proposal delivers the same chain with a better service and price fit.

Choose Teamed if its named contact can demonstrate ownership through verification, payroll acceptance and final confirmation. Choose Deel when the authenticated employee route and confirmed cutoff complete the same job with less customer coordination. Choose Remote when its payment-request checkpoint gives the clearest answer for a time-sensitive change. The case closes when the buyer knows the accepted account version and effective pay cycle before release—not when the email is forwarded.