> ## Documentation Index > Fetch the complete documentation index at: https://usepike.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # PayFit > Sync PayFit collaborators, contracts and approved absences into Pike members and capacity, for companies in France, the UK, Spain and Germany. The PayFit integration syncs collaborators and their contracts from PayFit into Pike [members](https://usepike.com/docs/members/overview.md), and approved absences into Pike [time off](https://usepike.com/docs/members/time-off.md). Your HR and payroll team works in PayFit. Resource managers plan allocations around the absences PayFit approves, and a contract that ends in PayFit deactivates the member in Pike. ## At a glance | | | | - | - | | **Direction** | PayFit to Pike for collaborators, contracts and approved absences | | **Who sets it up** | Workspace admins, by signing in to a PayFit admin account and authorizing Pike | | **Plan** | All plans | | **Sync** | Every 3 hours. On the Enterprise plan, changes sync in real time. | | **Source of truth** | PayFit for person fields, contract dates and absences. Pike for capacity, allocations, projects, time and cost profiles | ## Before you start You need: * The workspace admin role in Pike. * A PayFit admin account for the company you want to connect. Pike asks for read access to collaborators, contracts and absences. * One PayFit company per Pike workspace. If your business runs several PayFit companies, for example one in France and one in Spain, connect the company whose people you plan in this workspace. * Pike time off types for the PayFit absence types you use. PayFit absence types depend on the company's country, for example congés payés (paid leave) in France. You map each type during setup. See [Time off](https://usepike.com/docs/members/time-off.md). * Weekly capacity and teams set in Pike. Pike does not read them from PayFit. See [Working time](https://usepike.com/docs/members/working-time.md#work-schedule). ## Connect PayFit **1. Open the integration** Go to **Workspace settings → Integrations → PayFit** and click **Add integration**. **2. Authorize Pike** Sign in to your PayFit admin account, choose the company to connect, and approve the access Pike asks for. You return to Pike with the PayFit company name shown. **3. Map absence types** Under **Time off types**, choose a Pike time off type for each PayFit absence type. Pike suggests a mapping from the type names. **4. Choose what syncs** In the **What syncs with PayFit** card, turn **Read** on or off for each entity, and choose whether to turn on **Invite new employees**. **5. Import** Click **Import data**. Collaborators import first, then contracts, then absences. The integration page shows **Connected**, the PayFit company name, **Last synced** and **Next sync**. ## What syncs | PayFit | Pike | Direction | | - | - | - | | Collaborators | Members | PayFit to Pike | | Contracts | Hire date and member status | PayFit to Pike | | Approved absences | Time off | PayFit to Pike | ### Collaborators | PayFit field | Pike field | Notes | | - | - | - | | First name, last name | Member name | | | Email | Member email | The email on the collaborator's contract. Also used to match existing members | | Collaborator ID | PayFit ID | Shown on the member as the PayFit marker | A collaborator with no contract in PayFit does not import. ### Contracts | PayFit field | Pike field | Notes | | - | - | - | | Contract start date | Hire date | From the collaborator's first contract | | Contract end date | Member status | When the last contract ends, the member is deactivated from that date | A collaborator with several contracts syncs as one member. A new contract after a gap reactivates the member from its start date. ### Absences | PayFit field | Pike field | Notes | | - | - | - | | Collaborator | Member | | | Absence type | Time off type | Through your type mapping | | Start date and end date | Dates | | | Start and end of the absence | Hours per day | An absence that starts or ends at midday removes only half of that day's hours | | Status | Not stored | Only absences with the status approved import | Default type mapping: vacation and paid leave to Vacation, sick to Sick, parental to Parental, time off in lieu to Time off in lieu, unpaid to Unpaid leave, and every other type to Vacation. Each type counts toward the member's [norm hours](https://usepike.com/docs/members/working-time.md#norm-hours) as set on the Pike type. ## Matching and duplicates On the first import, Pike matches before it creates: * A collaborator matches a Pike member with the same email. A match links the two, and PayFit values replace the Pike values for the fields in the mapping. * Absences always import as new time off. Time off already entered in Pike for the same member and dates stays, and the PayFit absence is listed in **Sync issues** as an overlap. A collaborator with no matching member appears under **Unmatched employees** on the integration page. Click **Invite** to send a Pike invite, or **Link to member** to link the collaborator to a member with a different email. With **Invite new employees** on, Pike sends the invite automatically with the default role the admin chose. ## Which system wins | Entity | PayFit owns | Pike owns | | - | - | - | | Members | Name, email, hire date, status | Role, teams, position, rates, cost profile, working time, project access, allocations | | Time off | Dates, half days and type of absences from PayFit | Time off requested in Pike | Edit PayFit-owned fields in PayFit. Pike shows them as read-only with the PayFit marker. ## Sync schedule Pike syncs PayFit every 3 hours. On the Enterprise plan, changes sync in real time. **Import data**, **Sync now** and **Refresh** on a member run straight away on every plan. See [How sync works](https://usepike.com/docs/integrations/how-sync-works.md). ## Sync settings While PayFit is connected, the **What syncs with PayFit** card is below the top button row on the integration page. Toggles save immediately. | Entity | Read | Send | | - | - | - | | Collaborators | Yes | Not available | | Contracts | Yes | Not available | | Absences | Yes | Not available | New connections start with **Read** on for every entity and **Invite new employees** off. ## How it works ```mermaid theme={"system"} sequenceDiagram participant Person as Collaborator in PayFit participant Admin as Admin in PayFit participant PayFit participant Pike participant RM as Resource manager in Pike Person->>PayFit: Request paid leave for Monday and Tuesday Admin->>PayFit: Approve the absence PayFit->>Pike: Approved absence, on the next sync or in real time Pike->>Pike: Remove 16 hours from that week's capacity Pike-->>RM: Capacity and allocations show the absence RM->>Pike: Move Monday and Tuesday's allocations to another person ``` ## Use it in Pike ### Plan around approved leave Open **Members → Allocations** to see each person's capacity for the week. Approved PayFit absences show on the day with their type, and the hours are already removed from capacity, so an over-allocated day stands out before the work is due. See [Workspace capacity](https://usepike.com/docs/allocation/workspace-capacity.md). ### Onboard a new hire When a new collaborator gets a contract in PayFit, they appear in Pike on the next sync with their hire date. Turn on **Invite new employees**, or click **Invite** under **Unmatched employees**, then set their team, position and work schedule in Pike so they count toward capacity from their first day. ### Offboard a leaver When a collaborator's contract ends in PayFit, the member is deactivated in Pike from the end date. Their logged time, allocations and history stay on every project, and they stop counting toward capacity from that date. ## Deletes and removed records An integration never deletes Pike data. A collaborator deleted in PayFit is marked **Removed in PayFit** on the member, stays in Pike with their history, and stops syncing. An absence canceled in PayFit after approval is removed from Pike capacity on the next sync, and the change appears in the member's time off history. PayFit records a changed absence as a cancellation and a new absence, so Pike removes the old dates and imports the new ones. ## Troubleshooting | Symptom | Fix | | - | - | | A collaborator is missing in Pike | The collaborator has no contract in PayFit. Add the contract in PayFit, then click **Sync now**. | | A collaborator shows under **Unmatched employees** | The email on the PayFit contract differs from the member's email in Pike. Click **Link to member**, or correct the email in PayFit. | | Approved absence is missing | Check that **Read** is on for absences and that the absence is approved in PayFit. Then click **Refresh** on the member. | | Time off shows the wrong type | The PayFit absence type maps to a different Pike type. Change it under **Time off types**. Existing time off updates on the next sync. | | **Sync issues** lists an overlap | Time off for the same dates already exists in Pike. Delete the Pike entry, then click **Retry**. | | **Sync issues** lists an authentication error | The PayFit admin who authorized Pike lost access to the company. Reconnect with another PayFit admin under **Credentials**. | ## Limits * Pike does not write to PayFit, and does not send hours or variable elements to PayFit payroll. * Pending, declined or canceled absences do not sync. * Teams, positions and weekly capacity are set in Pike, not read from PayFit. * Compensation does not sync. Set cost profiles in Pike. * One Pike workspace connects to one PayFit company. ## Disconnect Go to **Workspace settings → Integrations → PayFit** and click **Disconnect**. Syncing stops and every member and time off entry stays in Pike with its history. Reconnecting the same PayFit company relinks the members. ## Related * [How sync works](https://usepike.com/docs/integrations/how-sync-works.md): The schedule, real-time sync and sync issues. * [Time off](https://usepike.com/docs/members/time-off.md): Time off types and how they count toward capacity. * [Cost profile](https://usepike.com/docs/members/cost-profile.md): Set salary and cost rates for margin. * [Lucca](https://usepike.com/docs/integrations/lucca.md): Users, work cycles, leaves and timesheets. * [Factorial](https://usepike.com/docs/integrations/factorial.md): Employees, contracts, leaves and compensation. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.