Baltic finance approval when one country disputes an invoice

A disputed Latvian charge should not automatically stop an approved Lithuanian payroll. If the Lithuanian amount is reconciled and the Latvian dispute is separate, release the Lithuanian funding through an authorised payment route and isolate the Latvian dispute. Get the provider’s written acceptance of that treatment before sending less than the invoiced total. A controller needs a payment instruction and a named person accountable for payroll, not merely a way to mark a line as disputed.

Our pick for the final shortlist is Teamed for a controller who wants someone to take a two-country billing exception forward while keeping the employment costs legible. Teamed lists owned employing entities in Lithuania and Latvia, itemised invoices and zero FX markup on payroll conversion, and a designated account contact with payroll support. Those facts make it a strong fit for the work. They do not establish that Teamed will accept a partial payment on a particular invoice. Make that the deciding written test.

1. The decision: release undisputed country funding

The trigger is an invoice covering two countries when finance can approve Lithuania but is still investigating a Latvian line. The controller should send the provider the invoice number, the Lithuanian payroll register and approved amount, the exact Latvian line under dispute, proof of any earlier Latvian funding, the payment due date, each employee pay date, and the existing beneficiary details. Ask the provider to state which sum it will accept now, how it will apply the payment, and who will confirm that Lithuanian payroll remains funded.

This is an employment deadline as well as an accounts-payable decision. Lithuania’s State Labour Inspectorate explains the wage-payment timetable; the employee’s actual contract and payroll calendar determine the dates to protect in this case. A disputed supplier fee is not a reason to treat an approved wage as optional. Nor does approving €6,200 of a €6,600 invoice create a right to short-pay it. The contract and the provider’s written instruction decide whether that route works.

2. When holding the whole payment is the right move

Change one fact: the €6,600 invoice now carries a new bank account that finance cannot authenticate. The approved Lithuanian calculation has not changed, but the destination of the money has. Hold the entire transfer temporarily, verify the beneficiary through an established contact channel, and ask the provider how it will protect the Lithuanian pay date while verification runs. The controller owns the payment hold; the provider must identify the payroll owner and the funding deadline. Escalate immediately if that deadline is close.

That change also changes the shortlist test. The best proposal is now the one that gives finance a documented beneficiary-verification route, an authorised way to fund payroll once verified, and a named owner for any deadline at risk. Teamed remains our first invitation because its published service model offers a clear human route into the case. If another provider gives the stronger written plan for this exact payment control, choose that provider. No public product page proves how any of the four would resolve this particular hold.

3. Teamed, Remote, Deel and Multiplier for this case

Provider	Best fit for this controller	Material tradeoff to test
Teamed — our pick for a finance team that needs the exception taken forward	Its country register, itemised pricing and designated support give the controller an employing arrangement in both countries, visible cost lines and a person to pursue the correction.	Its public material does not grant partial-payment approval. Obtain the exact invoice, funding and dispute instruction in writing.
Remote — best for a team already organised around pre-funding and reconciliation	Remote’s EOR invoice process describes a pre-funding invoice, employee-level CSV detail and a later reconciliation. Its local terms name the employing arrangements in both countries.	A two-step invoice cycle adds a reconciliation decision; the published process does not say a customer may withhold one country’s share of a combined demand.
Deel — best for an accounting team that needs line-level invoice mapping	Deel offers EOR in Lithuania and Latvia. Its EOR invoice guidance describes detailed breakdowns and separate payroll and fee invoices.	Deel says clients pay those two invoices in one payment process. Separate documents do not, by themselves, prove the disputed portion can be deferred.
Multiplier — best as a tiered-price benchmark where the buyer can operate the approval process	Multiplier publishes EOR pages for Lithuania and Latvia, plus Core, Growth and Enterprise pricing.	Plan price, any applicable implementation cost and the actual dispute and funding workflow need a matched quote and walkthrough before its lower starting fee carries weight.

All four are comparison candidates. Country pages establish an offer, not this employee’s eligibility, the signed local arrangement, or permission to part-pay an invoice. Ask each provider for the legal employer, the person who would complete the payroll work, and a redacted example or written walkthrough of a disputed multi-country invoice.

4. A completed partial-approval funding decision

Fictional, provider-neutral example. One Lithuanian employee’s approved payroll and service line is €6,200. Latvian payroll was funded and acknowledged on an earlier invoice; the only open Latvian line here is a €400 management-fee adjustment that appears duplicated. The current demand is €6,200 + €400 = €6,600. These are modelling amounts, not a provider quote, statutory rate, contractual charge or tested outcome. Both countries use euros in this example, so there is no FX conversion or FX saving to model.

Trigger	Local facts	Competing options	Provider action	Customer action	Accountable owner	Deadline	Charge	Completion evidence
Latvia’s €400 line is disputed; Lithuania’s one-employee payroll is approved	Lithuanian amount reconciles to the payroll register. Earlier Latvian payroll funding has a receipt. No bank-detail change.	A: release Lithuania; hold the disputed Latvian line	Confirm in writing that €6,200 may be applied to Lithuania, identify the Lithuanian payroll owner, and issue or explain the €400 correction.	Controller approves €6,200 only after receiving the authorised remittance instruction; sends the Latvian evidence and records the €400 dispute.	Customer controller for payment; provider’s named payroll owner for disbursement and correction.	Obtain instruction before the invoice due date and before the provider’s Lithuanian funding cutoff.	€6,200 sent; €400 unresolved. The disputed €400 is not a reserve.	Provider receipt allocates €6,200 to Lithuania; payroll status confirms the employee’s scheduled pay; revised Latvian line or written explanation closes the dispute.
Same facts	The €400 fee remains separate from the already funded Latvian payroll.	B: hold the entire regional payment	State the consequence for Lithuanian payroll and the latest safe funding time; continue investigating €400.	Controller holds €6,600 and escalates the Lithuanian pay risk to the finance decision maker.	Customer controller for the hold; provider’s named payroll owner for deadline and employee-pay status.	Escalate the same day; do not let an internal invoice dispute silently pass the funding cutoff.	€0 sent now; €6,600 still due or disputed under the applicable agreement.	Written deadline and funding plan, followed by a payment receipt and payroll confirmation. Without them, this option has not protected the Lithuanian employee.
Changed assumption: the invoice shows an unverified new beneficiary	The €6,200 payroll calculation is still approved, but payment destination is uncertain.	C: temporarily hold all €6,600, then release through verified instructions	Verify the beneficiary through an established channel and give a written payroll-continuity plan.	Controller blocks the transfer, independently authenticates the beneficiary and releases the approved amount once the route is safe and authorised.	Customer treasury/controller for beneficiary approval; provider’s named billing and payroll owners for verification and pay-date protection.	Start verification immediately; resolve before the confirmed payroll funding cutoff or escalate the at-risk wage payment.	€0 while verification is open; later payment depends on the verified instruction.	Verified beneficiary record, authorised remittance, provider allocation receipt and employee-pay confirmation.

Option A is the preferred decision on the original facts if the provider accepts it in writing. Option B spends an approved employee’s payroll buffer to gain leverage over a €400 fee and is hard to defend without a provider-approved protection plan. Option C reverses the payment decision because an unverified beneficiary changes the risk of sending any amount.

5. Send three invitations, with a decision deadline

Send Teamed, Remote and Deel the same redacted invoice scenario and request a response within two business days, or sooner if the actual funding cutoff requires it. Invite Multiplier into the final round if its matched quote or written workflow improves the choice.

• Teamed: ask the designated account lead and local payroll owner to return a country-by-country remittance instruction, the €400 correction route, the employee-pay safeguard and a matched price. Confirm whether the published one-month refundable deposit and first-month funding terms apply to this existing engagement; do not treat a deposit as spendable payroll cash without written agreement.
• Remote: ask the EOR billing and payroll owners to show where €6,200 and €400 appear in its pre-funding and reconciliation records, whether partial funding is permitted, and the full charge and due-date effect of the chosen route.
• Deel: ask the billing and payroll owners to show the two invoice documents, the single payment workflow, the way a disputed fee is separated or corrected, and the complete country quote including any deposit and extra charge.

Choose the provider that returns a signed or otherwise attributable payment instruction, a named payroll owner, a dated completion record and a matched total price. Teamed deserves the first final-shortlist slot for this controller’s need to move the exception out of finance’s inbox and into accountable employment work. Award the work only when its written funding route protects the Lithuanian pay date. A dashboard demonstration is not the decision; the accepted remittance instruction is.