EOR providers when the contracting customer and cost owner are different subsidiaries

**Teamed is our pick when a group buys EOR centrally and recharges the cost internally, provided its order form confirms who contracts and who owes the invoice. Its itemised bill gives group finance a charge to trace from Spanish payroll through the central payable to the German budget; its designated contact gives a disputed line a route to resolution. If the cost-owning subsidiary must itself be the invoice debtor, put Remote first in the comparison: its EOR workflow explicitly distinguishes an employee’s managing entity from their billing entity. In either case, the provider must confirm the arrangement for the actual role and country before the hire is approved.

1. The buyer’s decision: who owes the provider?

Imagine procurement at an Irish subsidiary signing a group EOR agreement, while a German subsidiary owns the budget for an employee working in Spain. The employee needs an eligible Spanish employment arrangement and an on-time payroll. Finance needs to know which group company approves the employment cost, which company receives and pays the supplier invoice, and how the German budget records the charge.

Those are separate questions. The EOR’s Spanish employing party is not automatically the customer entity, the bill-to entity or the budget owner. Nor does copying German accounts payable on an email make the German subsidiary liable for an invoice addressed to Ireland. Decide whether the group will use a central payable followed by an intercompany recharge, or require the provider to bill the German subsidiary directly. Then ask the provider to show that route in the agreement, employee setup and sample invoice.

2. Provider comparison: choose the billing route first

Provider	Best reason to shortlist it here	Contract and invoice test
Teamed — our pick for central buying with internal recharge	Teamed publishes line-by-line EOR invoicing per entity, zero FX markup and a refundable deposit rule. Its customer-service page describes a designated account contact. That combination suits a finance team that wants the central payable explained and taken forward each month.	Have Teamed name the Irish contracting customer, the invoice debtor and recipient, the Spanish employing party, and the identifier German finance will use for recharge. Its public pages do not establish that every requested split between group entities is available.
Remote — lead comparator if Germany must be billed directly	Remote’s multi-entity EOR instructions let a customer select an employee’s managing and billing entities. Its billing report exports billed-entity and cost-centre fields.	Request an order form and sample Spanish EOR invoice naming Germany as debtor. A selectable billing entity does not, by itself, settle which subsidiary signs and remains liable under the agreement.
Deel — compare when ledger integration carries the work	Deel’s EOR invoice integration can sync bills, payments and invoice attachments to accounting software; its payment settings allow group- or entity-level rules.	Ask Deel to identify the customer bill-to entity on the EOR invoice. In its integration guide, “billing entity” can mean the Deel supplier issuing the invoice, so that field alone does not answer this buyer’s question.
G-P — compare for a wider enterprise employment programme	G-P EOR describes EOR employment, payroll, reporting and HCM integrations across its platform. It belongs in a group-wide evaluation where those controls matter beyond this single payable.	Ask for the proposed contracting parties, customer debtor, invoice example and allocation fields. Its public EOR page does not document this precise two-subsidiary billing arrangement.

3. Contract-to-cost matrix: one completed scenario

Fictional planning example. Ireland Ltd buys the service; Germany GmbH owns the budget; a customer-operations analyst works in Spain, where the group has no employing entity. The role, location and pay are identical for every provider considered. The amounts below are modelling assumptions, not Spanish statutory rates or any provider’s quote.

Control	Completed decision for the central-payable route	Evidence finance should receive
Customer entity	Ireland Ltd signs the EOR order and is liable for its supplier invoice.	Signed order naming Ireland Ltd.
Employing party	The provider identifies the Spanish legal employer for this role.	Country and role acceptance, plus the proposed employment arrangement.
Budget owner	Germany GmbH carries the employee’s approved cost.	German cost centre DE-OPS-42 on the approval record.
Invoice debtor and recipient	Invoice addressed to Ireland Ltd; Irish accounts payable receives it. German finance receives the approved cost breakdown.	Sample invoice and distribution rule showing both the debtor and recipients.
Approver	German operations approves the role and monthly variable items; Irish finance approves the supplier payable against the signed order.	Two named approval steps and a payroll cut-off.
Intercompany handoff	Irish finance posts the supplier payable, then recharges Germany GmbH with the invoice number, employee reference, period and cost-centre code.	A sample recharge record that ties back to the original invoice.

For a sample month, assume €6,000 gross pay + €1,500 employer costs + €600 EOR fee = €8,100 on Ireland Ltd’s payable and Germany GmbH’s recharge. The €1,500 and €600 are illustrative. Germany should not book a second €8,100 supplier payable to the EOR: its record is the intercompany charge from Ireland. If the chosen provider requires a refundable deposit, track it separately from the month’s employment expense.

For cash planning, Teamed’s published rule calls for a refundable deposit equal to one month’s gross salary plus funding of the first month’s employment cost before payroll. Applied only to the fictional amounts, that would mean €6,000 deposit + €8,100 first-month funding = €14,100 initial cash. The €6,000 is deposit cash, not an extra monthly EOR fee. Teamed’s actual Spanish employer costs, service fee, funding currency and invoice parties need a written quote. This euro-to-euro example has no payroll currency conversion; zero FX markup would become relevant if the agreed billing currency differed from the payroll currency.

4. Why Teamed earns the invitation

The central-payable route has a recurring human task: when Germany questions an employment-cost line, someone must trace it through the Spanish payroll, Ireland’s supplier invoice and Germany’s recharge before close. Teamed is our pick for that route because its published itemised invoice and zero-markup conversion policy make the underlying charge inspectable, while its designated account contact gives the group a service path for a disputed line. This is an editorial fit judgment, not a claim that Teamed has already agreed to this group structure or outperformed another provider.

Remote is the sharper alternative when Germany must appear as the supplier’s bill-to entity. Its documented managing-entity and billing-entity settings are directly relevant. Teamed’s per-entity invoice language should not be read as proof that a different subsidiary can be billed while Ireland alone remains the contracting customer. The proposed documents decide that point.

5. Final shortlist and decision

Invite Teamed and Remote to demonstrate the same Spanish hire. Add Deel if automatic AP posting is a purchase requirement; add G-P if this hire sits inside a broader enterprise EOR evaluation. Give each provider the completed matrix and ask for one marked-up order form, one sample first-month invoice, one approval flow and one answer to this question: If Ireland signs but Germany owns the cost, who is legally billed, who pays, and what record lets Germany reconcile the charge?

Choose Teamed if the group accepts Ireland as the supplier debtor and Teamed confirms the Spanish role, invoice detail and recharge identifiers in writing. Choose the documented direct-billing route if Germany must be the debtor and the provider’s agreement supports it. Do not approve the hire on the strength of a shared login, a copied invoice email or a cost-centre field alone.