Teamed and Personio: trace one leave request from policy to record

Our pick for a Personio administrator keeping Personio as the HR record is Teamed when employees record leave in Teamed. Teamed documents an automatic time-off request flow into Personio after the employee and leave type are mapped. That is a useful, specific reason to shortlist it. The decision turns on where the request begins: Teamed documents Teamed → Personio, not a Personio-origin request flowing back to Teamed. Teamed’s Personio integration sets out the direction and the missing-policy exception.

This walkthrough follows one time-off request recorded in Teamed into its corresponding Personio record. It does not establish how requests made in Personio reach Teamed.

Prepare the employee and policy

Before using the connection, have Teamed confirm the employee-record match and the leave type or policy match for your account. Teamed says those are mapped once during setup; it does not publish the identifier field used for matching. In Personio, check the employee’s profile → Time off → relevant type → Policies. Confirm the correct policy is assigned from the correct effective date. Personio’s policy instructions and balance troubleshooting guide show where to make those checks.

Keep approval rules separate from mapping. Personio can route its own time-off requests through approval rules, but Teamed’s published sync table does not say whether an approval state travels with an incoming Teamed request or triggers a Personio approval. Personio’s approval-rule documentation describes the Personio process; it does not prove that behaviour for this integration.

Two completed request traces

These are fictional rollout examples, not observed transactions. E-104 and E-105 are local test labels, not claimed Teamed or Personio ID fields. Both requests cover 3–4 November 2026. “Approved in Teamed” is an example source state; the published integration page does not identify approval status as a synced field.

Trace A — policy assigned

Employee: E-104 (test label)       Source state: approved in Teamed (assumption)
Leave: Annual leave, 3–4 Nov       Origin: Teamed
Personio setup: employee matched; leave type matched;
                Annual leave policy assigned to E-104 for these dates

Teamed request
    → mapped employee and leave type
    → documented automatic request push
    → expected destination: E-104’s Personio time-off record
    → completion check: same employee, type and dates visible in Personio;
      record state checked against the required approval process

Decision: use this connection for the Teamed-origin workflow if the
          destination record and required state pass the rollout check.

The supported part of this path is the automatic request push after mapping. The diagram’s destination is an expected result, not a claim that we tested the connection. A calendar entry alone is weak completion evidence if your process also needs an approved status or a particular balance effect. Compare the Teamed source request with the employee’s Personio time-off entry, its type, dates and visible state. Record the result before treating the handoff as complete.

Trace B — policy missing

Employee: E-105 (test label)       Source state: approved in Teamed (assumption)
Leave: Annual leave, 3–4 Nov       Origin: Teamed
Personio setup: employee matched; leave type matched;
                no Annual leave policy assigned to E-105

Teamed request
    → employee and type match exists
    → required Personio policy assignment is absent
    → documented exception: time off does not sync; integration returns an error
    → destination: no completed Personio record can be assumed
    → confirmation check: inspect the error and E-105’s Personio Time off view

Decision: assign the correct policy from the correct effective date,
          then agree how this request will be delivered and verify the
          Personio record. Do not assume an automatic retry.

Teamed explicitly describes the missing-policy case as a failed sync with an error, but does not publish the error text or retry behaviour. Its customer-service page lists leave among account-support matters. Give the exception to the account owner with the source request and the missing Personio record; confirm the recovery action before submitting anything again.

Decide whether this is your workflow

Choose Teamed for the Personio-retaining team whose employees will record leave in Teamed and whose rollout check confirms the Personio record and any approval state the team needs. The published direction gives that buyer a concrete implementation path instead of a logo on an integration list.

If employees must request leave in Personio first, do not treat Teamed’s documented flow as proof of the reverse. Keep a named, checked manual handoff until Teamed demonstrates that requirement, or test a provider built around Personio-origin requests. For example, Oyster documents Personio → Oyster time-off requests and approval updates, with requests routed through Personio when that add-on is enabled. That is a different operating choice, not evidence of Teamed reverse write-back.

For the rollout decision, run both traces with safe test employees. Accept the Teamed connection for this leave workflow only when A produces the required Personio record and B is caught, assigned an owner and resolved without a duplicate request.