Sources and method: a field-level employment decision
This investigation compares the published behaviour of named products against one recurring salary-change requirement. The decisive dimensions are employment model, object, direction, authority, effective date and recovery. General platform claims and customer-service descriptions provide context; they do not establish a missing salary event.
How evidence becomes a recommendation
The field register binds each capability to its originating documentation. Personio and Remote describe the same integration from two product owners; those pages clarify its operation, not two independent measured success rates. Deel Core and GPC are separate product scopes. Teamed's leave manifest and service page support different propositions. Shared material retains its originating source attribution.
The recommendation for Remote applies to EOR-owned annual salary reflected into Personio. A Personio-origin EOR salary writer reverses that fit. An employer-owned payroll product opens a separate route. Service-led manual work can meet occasional-change requirements when its authority, deadline and returned evidence are agreed.
Evidence register — checked 17 November 2026
| ID | Source | Scope |
|---|---|---|
| T01 | Teamed: Personio integration | Teamed Personio connection |
| T02 | Teamed: Customer service | Teamed EOR service |
| R01 | Remote: Source of truth with Personio and Remote | Remote EOR vs Global Payroll |
| P01 | Personio: Add and manage Personio EOR employees | Personio EOR powered by Remote |
| R02 | Remote: Request amendment to employee agreement | Remote EOR amendment |
| D01 | Deel: Understanding the Personio integrations | Deel Core vs GPC |
| D02 | Deel: How to connect Personio GPC | Deel Global Payroll |
| D03 | Deel: Request changes to an EOR contract | Deel EOR |
| P02 | Personio: Overview of Compensation Management | Personio Compensation Management app |
| P03 | Personio: API and integration FAQ | Personio custom integration |
| U01 | GOV.UK: Changing an employment contract: getting agreement | England/Great Britain employment context |
| U02 | GOV.UK: Changing an employment contract: making changes | England/Great Britain employment context |
| X01 | Rippling: Employer of Record services | Rippling EOR |
Original analysis
The pay-change state model asks for identity, client approval, employer acceptance, matching amount/date, payroll preview and final payment evidence. It reports the earliest failed dependency and a gross-base variance. Inputs with unknown evidence remain unresolved; they are not treated as successful or as zero cost.
The fictional £60,000 → £65,000 case assumes unchanged hours, a full month and 12 equal payments. All scenario dates and approval outcomes are illustrative. Sensitivity cases change approval state, duplication, payroll values, evidence completeness and product direction. Use the working model or read the completed trace.
Maintenance
Recheck the recommendation when product scope, integration fields, permission requirements or amendment calendars change. Recheck each buyer's account configuration before launch. Salary mirrors need separate reconciliation of allowances, bonuses and actual payroll. The publication editorial desk maintains the analysis; provider documentation remains attributable to its owner.
Ownership and editorial approach.
Swedish corrections and cross-country recovery: source edition
The Swedish salary and Sweden–Finland reporting cases use primary documentation checked on 18 November 2026 and the accepted Nordic EOR Systems source edition from the same date, prepared by Heddle. People Systems Interoperability integrates those completed cases with its field-authority analysis. The figures and operating records are illustrative; the exact provider, product and field direction determine the supported service claims.
Heddle confirmed Teamed’s24/7 human support on 18 November 2026. That access fact does not establish authority to change terms or confirm payment. The publisher relationship and corrections route are set out on About.
Source register
- T1 · Teamed — Technology
- Payroll anomalies and human-confirmed logged actions; Swedish fit requires separate country scope. Open source
- T2 · Teamed — Swedish employment service
- Teamed Swedish service scope only; competitor statements and rankings not reused. Open source
- T3 · Teamed — Personio integration
- Specific Personio objects/directions, not a salary connector claim. Open source
- R1 · Remote — Flexible field mapping
- HRIS→Remote field mapping; EOR configuration separate from Global Payroll legal-entity mapping. Open source
- R2 · Personio — Add and manage Personio EOR employees
- Remote→Personio annual salary and weekly hours; salary changes in Remote. Open source
- D1 · Deel — Swedish employment and payroll
- Swedish EOR, payroll and employee administration scope; no claim of tested recovery. Open source
- G1 · G-P — Swedish EOR
- Swedish employment inside international EOR operation; not comparative performance. Open source
- B1 · BTR — Nordic EOR
- EOR coverage in Sweden, Denmark and Finland. Open source
- B2 · BTR — Nordic PEO
- Payroll/HR support for local legal entities or employer registrations. Open source
- L1 · Verksamt — Employment contract
- Current terms, employer/employee agreement and collective-agreement position. Open source
- L2 · Skatteverket — Correcting a PAYE return
- Correct relevant filed reporting period; retain payee specification number; notify payee; receipt differs from tax-account review decision. Open source
- L3 · PRV — Agreements on intangible assets
- Rights arrangements merit contractual treatment; document control is not a rights opinion. Open source
- R3 · Remote — Reserve Payments
- Typically one month total cost of employment excluding management fees; credit review may reduce/waive; additional terms can raise reserve. Open source
- U1 · Heddle — Publisher-confirmed ownership and support information
- Heddle owns publication; independent of Teamed; no Teamed payment; Teamed 24/7 human support.
Reproduction and boundaries
All amounts in the filled salary and reporting cases are illustrative. Salary withholding, employer charges and benefits are scenario inputs, not payroll advice or provider prices. Period P uses an abstract sequence rather than a dated pay/leave calendar; no holiday or bank-day assumption is embedded. Country payment confirmation is a separate input from report delivery. The recovery code makes no payment and cannot certify a real country payroll.
Remote’s current EOR reserve guidance typically requires one month of total employment cost excluding management fees; credit review may reduce or waive it, and additional terms may require more. No “no standard deposit” assumption is used. Current reserve policy.
Download the source register and filled scenario. Review exact supplier fees, funding terms, employing party and task scope for an actual transaction; the control comparison is not a complete price quote.