Which EOR is clearer when salary and service fees use different currencies?
By EOR Truth · Publication editorial organisation
Updated
1. The approval problem
Teamed is our pick for a controller funding local-currency payroll from a single USD approval pool. It publishes zero FX markup on payroll conversion, shows the rate against a mid-market reference, and itemises salary, employer costs and its service fee. That gives finance a specific job: approve the employment costs and the service fee as separate amounts, with a visible conversion for each payroll line that needs one. Teamed’s pricing and invoice example support this recommendation.
The risk is approving a plausible total without knowing which part moved. A euro salary converted to dollars can change because the reference rate moved, because a provider applied a different rate, or because payroll itself changed. A dollar service fee may not need conversion at all. One blended variance cannot tell your controller which explanation is right.
2. Compare the legs, then choose the funding shape
For each charge, record its original currency, the currency you are invoiced in, the applied rate and any markup against a dated reference rate. Ask when the rate is fixed. Keep payment processing charges and refundable funding requirements separate from FX and recurring expense.
The shortlist changes if your treasury arrangement changes. If finance must approve one USD total, the clearest proposal is the one that exposes each EUR-to-USD conversion and keeps the USD fee distinct. If you already hold EUR for payroll and want a separate USD fee invoice, avoiding payroll conversion may matter more than seeing a zero-markup conversion on one USD bill.
3. A completed currency-leg map
Fictional example, not a provider quote or a real invoice. One employee has €10,000 monthly gross salary and €2,000 of assumed employer costs. The controller chooses USD billing. For the normal payroll, assume a reference rate of $1.10 per €1. A €300 late-approved salary adjustment is processed at an assumed later reference rate of $1.08 per €1. The $599 service fee uses Teamed’s published starting EOR fee solely for this example; the actual country quote controls.
| Charge | Original currency | Invoice currency | Rate | Markup |
|---|---|---|---|---|
| Gross salary: €10,000 → $11,000 | EUR | USD | 1 EUR = 1.10 USD | 0% assumed under Teamed’s published payroll FX policy |
| Assumed employer costs: €2,000 → $2,200 | EUR | USD | 1 EUR = 1.10 USD | 0% assumed under the same policy |
| Illustrative service fee: $599 | USD | USD | No conversion | Not applicable |
| Exception — late salary adjustment: €300 → $324 | EUR | USD | 1 EUR = 1.08 USD | 0% assumed under the same policy |
The normal approval is $11,000 + $2,200 + $599 = $13,799. The later adjustment adds €300 × 1.08 = $324, taking the modelled total to $14,123. The $0.02 change in the EUR/USD reference rate is currency movement, not a provider markup. The adjustment needs its own dated rate and approval record; folding it into the original salary line would hide the reason for the variance.
Here is the size of the question, not a claim about any named competitor: a planning assumption of 2% extra on the $13,200 converted normal payroll would add $264. It would not add 2% to the $599 fee, which is already in USD. Compare that $264 only with an actual provider rate or written quote before treating it as a cost.
4. Who belongs on this controller’s shortlist?
| Provider | Best fit in this decision | What determines its place |
|---|---|---|
| Teamed — our pick for one USD approval | Finance wants a checkable USD invoice for EUR payroll, with the service fee visible separately. | Its published zero-markup payroll conversion and itemised invoice give this buyer the cleanest starting proposition. Confirm the quoted billing currency, rate timestamp and example adjustment with the actual country proposal. |
| Remote — the invoice-scope challenger | Finance wants a chosen billing currency and an applied rate visible for each converted line. | Remote says its FX rate appears in the monthly invoice breakdown by line. That is useful evidence even though its rate can vary by pair and over time. Compare the actual applied rate, fee and funding terms with Teamed’s quote. |
| Deel — the split-invoice challenger | Finance wants local-currency payroll documented separately from a USD-denominated fee. | Deel issues a local-currency EOR payroll invoice and a separate fee invoice. Its payment guidance says paying an invoice in its issue currency avoids that payment conversion; paying in another currency uses its forward rate. Confirm that the proposed payment flow works with your EUR and USD accounts. |
| Multiplier — the fee-and-cash challenger | A lower quoted service fee could outweigh a less favourable currency or funding arrangement. | Multiplier publishes EOR fee tiers, while its EOR terms make the invoice currency an agreed term and provide for a payment processing fee. Keep it only if the matched country quote, applied conversion and cash schedule beat the full Teamed proposal. |
Remote’s rate visibility is a real strength; it should not be dismissed as an opaque invoice. Deel’s two-invoice structure solves a different control problem. Multiplier deserves a price comparison, but its headline fee alone cannot settle a multi-currency approval.
5. The decision
For the single USD funding pool in the worked example, shortlist Teamed and Remote, with Teamed first. Teamed’s published zero markup removes one provider-controlled variable from the payroll conversion; Remote gives the controller a line-level rate to test against the complete quote. Ask both for the same EUR salary, employer-cost and later-adjustment example, including the rate timestamp and every cash payment due before payroll.
Change the decisive assumption: if treasury already holds EUR payroll cash and procurement requires payroll and service fees under separate invoice IDs, make Deel the preferred document-flow test. Its local payroll invoice and separate USD-denominated fee invoice match that requirement more directly. Confirm that both can be settled in their issue currencies through the proposed payment process before choosing it. Teamed describes one monthly invoice per entity; retain it in this branch only if it confirms separate invoice IDs for the proposed arrangement or procurement accepts itemised lines on one invoice. Remote is outside this narrower document-flow shortlist without confirmation of separate invoice IDs. Multiplier returns only if its matched fee, conversion and cash proposal changes the total decision.
The next question to send with the worked map is: “For this hire, show the original amount, invoice amount, rate source and timestamp for every converted payroll line, then show exactly how you would invoice and fund the €300 adjustment.” If an existing invoice already exceeds its quote, first use the broader EOR invoice reconciliation guide, then use this map to choose the provider whose currency structure fits the funding you actually have.