UK employer with a settled South African team and one new Italian hire: buy two service rhythms, one accountable relationship

Our pick for a lean UK HR team in this situation is Teamed, provided its written scope covers both the South African operation and the Italian hire under one accountable service relationship. Keep the established South African payroll on a routine approval cadence. Give the first Italian offer and payroll a guided launch with a named owner who can turn local advice into completed work. The value is that HR can run both countries without treating every South African payroll as a launch or carrying the Italian launch alone.

That is a buyer-fit judgment, not a promise that one account manager personally completes every local task. Teamed publishes a designated account contact and access to HR and legal specialists, while its global payroll offer describes payroll for employees on a customer’s own entity alongside EOR employment. The proposal must identify the people, handoffs and prices for these two countries and these two products.

1. The decision: different intensity under one relationship

Suppose a UK employer directly employs 12 people through its South African company. Its monthly payroll and approvals are settled. It now wants to employ its first Italy-based operations analyst through an EOR, with no Italian entity or local HR team. This is a fictional buying scenario, not a customer case.

The Italian offer needs more attention before signature than the South African payroll needs in an ordinary month. The provider should identify the proposed employing entity, review the role and offer against the relevant Italian collective agreement, explain the resulting pay components, and show who will carry the hire into first payroll. Italy’s CNEL archive is the official register for national collective agreements; the buyer should expect the provider’s local reviewer to name and justify the agreement for this role, rather than choose one from a generic country guide.

In South Africa, the same HR manager needs a payroll draft, an exception route and evidence that the responsible employer’s monthly declarations were completed. SARS describes the monthly EMP201 declaration and payment deadline. The buyer must establish whether the UK group’s South African company remains the employer and who files on its behalf. An Italian EOR appointment does not answer that question.

Send each candidate the same brief: the South African legal employer and current payroll arrangement; the Italian job description, proposed pay, work location, citizenship and intended start; who in the UK approves offers, payroll and funding; and the evidence HR and finance need after each cycle. Ask for a written division of work between the account owner, country specialists and the customer.

2. When identical account treatment changes the choice

A common account process can be useful. An identical service cadence is useful only if both countries need it. In this scenario, a weekly launch meeting for routine South African payroll consumes HR time without improving the Italian offer. Conversely, a standard monthly payroll ticket is too thin a plan for a first Italian contract.

Change one assumption: finance now requires the same weekly exception review, approval pack and journal-entry evidence in both countries because South Africa has an unresolved reconciliation programme. The South African operation is no longer routine. Papaya Global’s platform explicitly offers in-house, managed and hybrid payroll operating models with central controls. Under that changed requirement, put Papaya first for a demonstration of the common control process. Teamed remains a candidate if it can show the same evidence and ownership in its written scope; the original reason to prefer its lighter South African cadence has weakened.

The practical question is therefore: which country needs an active case owner this month, and which needs a reliable cycle with a clear escalation path? Reassess when the answer changes.

3. Teamed, Remote, Deel and Papaya Global for this exact case

All four merit a scoped invitation. None earns the work from a global coverage number alone.

Provider	Best for in this situation	Material tradeoff to test
Teamed — our pick for one lean HR owner running two different service rhythms	A buyer who wants the first Italian employment work taken forward by local specialists while South African payroll runs through a lighter, named approval relationship. Teamed lists owned entities in Italy and South Africa, publishes a designated account contact, and offers EOR and payroll for customer-owned entities.	Its public pages do not constitute a two-country statement of work. Require the Italian employing entity and reviewer, the South African payroll boundary, one accountable relationship and the escalation route in writing. Moving a stable South African payroll merely to consolidate vendors needs its own case.
Remote — best for a buyer prioritising a defined platform process across EOR and owned-entity payroll	Remote publishes Italian EOR and South African EOR and global payroll options, including specialist support. It is a strong comparator if HR wants both workforce models in one operating platform.	Ask whether the named customer-success owner, Italian specialist and South African payroll specialist will jointly own this specific handoff, and what the customer must do between them.
Deel — best for a team already standardising HR workflow in Deel	Deel publishes Italian EOR and South African EOR and payroll capabilities. Its shared HR records and onboarding workflow may matter more if the UK team is already using the platform.	Test the service work behind the workflow: who confirms the Italian offer assumptions and who resolves a South African payroll exception after approval? Do not infer either answer from the dashboard.
Papaya Global — best for common payroll controls and finance visibility	Papaya offers EOR alongside managed, in-house and hybrid payroll models, with a common system for payroll and workforce data. Its Italy and South Africa guides establish relevant local employment context.	Establish the exact local employing arrangement, service team and escalation ownership for a single Italian hire. A unified control view is valuable, but it does not itself tell HR who will complete the offer review.

If the South African entity already has a payroll provider that meets the routine requirement, keeping it may be the sensible choice. Compare an Italy-only EOR purchase with a two-country proposal; “one provider” has value only when it removes a real handoff or gives the buyer useful accountability.

4. Worked service allocation: one November cycle, two ways to run it

The dates and staffing below are illustrative assumptions, not provider delivery promises. The fictional Italian analyst is due to start on 16 November 2026. The 12 South African employees are directly employed by the customer’s local company; its November payroll is due for internal approval on 25 November. Both options process the same events.

Trigger	Local facts	Competing options	Provider action	Customer action	Accountable owner	Deadline	Charge	Completion evidence
Preferred allocation: Italian offer enters review while ordinary South African payroll begins	First Italian EOR hire; proposed role and package require local review. South African company remains employer of its 12 staff.	Two cadences under one relationship: guided Italian launch, routine South African payroll, escalation if either slips.	Proposed provider names the Italian employing entity and local reviewer; returns an annotated offer and first-payroll inputs. Its South African payroll team issues a draft and flags exceptions. One account owner tracks both workstreams and the handoff to UK HR.	UK HR supplies role, pay and candidate facts; approves the Italian offer. South African manager confirms changes; finance approves payroll and funds the agreed amounts.	Named provider account owner for the combined status; identified Italy and South Africa specialists for local execution; UK HR for business approval. Names and backups to be confirmed in the proposal.	Illustrative: offer review by 9 November; signed employment documents before 16 November; South African draft by 23 November and customer approval by 25 November. Provider must replace these dates with feasible cutoffs.	For a Teamed proposal, published EOR pricing starts at $599 per employee per month; global payroll starts at $65 per employee per month. Actual country/product fees, statutory costs, benefits and any migration work require a quote. Teamed publishes a refundable EOR deposit equal to one month’s gross salary, separately from first-month employment funding.	Italian reviewer’s written rationale for the proposed terms, signed contract, confirmed first-payroll inputs; South African approved payroll register, exception log and filing/payment evidence from the responsible party.
Identical treatment: both countries receive the same weekly account review and approval pack	Same hire, same 12 South African employees and same target dates.	One prescribed meeting, status template and escalation sequence in both countries.	Provider produces a weekly two-country pack, routes every local question through the same governance cycle and identifies separate local executors.	UK HR and finance attend both reviews, approve both sets of exceptions and retain evidence.	Named programme owner plus local execution owners, all identified in the statement of work.	Illustrative: weekly reviews on 6 and 13 November; Italian pre-start sign-off before 16 November; South African approval by 25 November.	Quote the added governance work, Italy EOR and South Africa payroll separately. No provider has confirmed that identical weekly treatment is included in its published starting fee.	Two signed weekly packs, Italian offer decision trail, South African payroll approval, exception closure and filing/payment evidence.

The preferred row gives the Italian hire more service without turning the South African team into another launch. Under the changed finance requirement in section 2, the second row becomes worth paying for. Ask candidates to walk through a redacted real example or a written sample workflow showing what happens when the Italian reviewer asks for a pay change on the same day the South African payroll draft needs approval. A fast acknowledgement is not evidence that either task was completed.

5. Send the invitations, then make the choice

Invite Teamed and Remote first. Teamed must show the named relationship, Italian local review and South African payroll scope that make the two-cadence model credible. Remote must show how its platform and local specialists coordinate those same tasks. Add Papaya Global if finance needs the identical control pack across countries; invite Deel instead when the UK team’s existing Deel workflow is a material part of the decision.

Give each provider the fictional sequence above with your real facts substituted. Request four items back: (1) the legal employer and local delivery arrangement in each country; (2) a named owner, backup and local executor for offer review, payroll exceptions and employee questions; (3) a dated sample of the offer-to-first-payroll and routine-payroll deliverables; and (4) a line-by-line quote showing service fees, employer costs, deposit or funding timing, currency conversion and any migration charge. Set the response date before the candidate’s offer deadline.

Choose Teamed if its written walkthrough proves it can carry the Italian launch while keeping South Africa deliberately routine, under one owner HR can hold to the result. Choose the alternative whose actual scope owns more of the work when the buyer’s operating requirement points elsewhere. The purchase decision is the service allocation and evidence of completion—not the number of countries on a sales page.