> ## 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. # Employment Hero > Sync Employment Hero employees, teams, leave and work hours into Pike, and send approved hours for hourly employees to Employment Hero Payroll as timesheets. The Employment Hero integration syncs employees, teams, approved leave and work hours from Employment Hero into Pike [members](https://usepike.com/docs/members/overview.md), teams, [time off](https://usepike.com/docs/members/time-off.md) and capacity. It can also send approved Pike hours for hourly employees to Employment Hero as timesheet entries, which are paid in the next Employment Hero Payroll pay run. Capacity, billing and hourly pay use the same approved hours. ## At a glance | | | | - | - | | **Direction** | Employment Hero to Pike for employees, teams, managers, leave and work hours. Pike to Employment Hero for timesheet entries, when **Send hours to payroll** is on | | **Who sets it up** | Workspace admins, with an Employment Hero admin who authorizes the Pike app | | **Plan** | All plans | | **Sync** | Every 3 hours. On the Enterprise plan, changes sync in real time. | | **Source of truth** | Employment Hero for person fields, leave, work hours and pay details. Pike for allocations, projects, time, pay lines and cost profiles | ## Before you start You need: * The workspace admin role in Pike. * An Employment Hero user with the admin or owner role in the organisation you want to connect. The admin signs in during setup and authorizes Pike. Pike asks for read access to employees, teams, leave requests and pay details, and write access to timesheet entries. * An Employment Hero subscription that includes API access. * Pike time off types for the Employment Hero leave categories you use. You map each leave category during setup. See [Time off](https://usepike.com/docs/members/time-off.md). * Work types in Employment Hero for the hours Pike sends, such as ordinary hours and overtime, if you plan to turn on **Send hours to payroll**. ## Connect Employment Hero **1. Open the integration** Go to **Workspace settings → Integrations → Employment Hero** and click **Add integration**. **2. Authorize Pike** Sign in to Employment Hero as an admin, choose the organisation to connect, and approve access for Pike. You return to Pike with the integration connected and the organisation name shown. **3. Map time off types** Under **Time off types**, choose a Pike time off type for each Employment Hero leave category. Pike suggests a mapping from the category names. **4. Map pay codes** Under **Pay codes**, choose an Employment Hero work type for each pay line Pike sends: **Normal hours**, **Overtime 1** and **Overtime 2**. **5. Choose what syncs** In the **What syncs with Employment Hero** card, turn **Read** and **Send** on or off for each entity, and choose whether to turn on **Invite new employees**. **6. Import** Click **Import data**. Teams import first, then employees, then work hours and leave. The integration page shows **Connected**, the Employment Hero organisation name, **Last synced** and **Next sync**. ## What syncs | Employment Hero | Pike | Direction | | - | - | - | | Employees | Members | Employment Hero to Pike | | Teams | Teams | Employment Hero to Pike | | Job titles | Positions | Employment Hero to Pike | | Primary managers | Managers | Employment Hero to Pike, matched by email | | Work hours on pay details | Capacity per week | Employment Hero to Pike | | Approved leave requests | Time off | Employment Hero to Pike | | Salary versions and pay rate | Member cost profiles | Employment Hero to Pike, when **Sync compensation to cost profiles** is on | | Timesheet entries | Pay lines from a closed Pike pay period | Pike to Employment Hero, when **Send hours to payroll** is on | ### Employees | Employment Hero field | Pike field | Notes | | - | - | - | | First name, last name | Member name | The known-as name is used when one is set | | Company email | Member email | Also used to match existing members | | Job title | Position | A position is created when no Pike position has the same name | | Team | Team | A team is created when no Pike team has the same name | | Primary manager | Manager | When the manager's email matches a Pike member | | Employment type | Employment type | Salaried or hourly, from the employee's pay details | | Work hours | Capacity per week | Spread over the employee's working days. See [Work schedule](https://usepike.com/docs/members/working-time.md#work-schedule) | | Status, termination date | Member status | A terminated employee becomes a deactivated member. History is kept | | Start date | Contract start | | | Employee ID | Employment Hero ID | Shown on the member as the Employment Hero marker | ### Time off | Employment Hero field | Pike field | Notes | | - | - | - | | Employee | Member | | | Leave category | Time off type | Through your type mapping | | Start and end date | Dates | | | Hours | Hours per day | A part-day request removes only its hours from capacity | | Status | Not stored | Only approved leave requests import | Default type mapping: annual leave to Vacation, personal or sick leave to Sick, parental leave to Parental, time off in lieu to Time off in lieu, leave without pay to Unpaid leave, and every other category 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. ### Compensation **Sync compensation to cost profiles** is off by default. Only admins and finance users can turn it on. | Employment Hero field | Pike field | Notes | | - | - | - | | Salary or hourly rate | Cost profile salary | | | Salary period | Cost profile pay period | Hour or year | | Effective date | Cost profile start date | Each salary version adds a new row | See [Cost profile](https://usepike.com/docs/members/cost-profile.md). ### Send hours to payroll **Send hours to payroll** is off by default. When on, closing a [pay period](https://usepike.com/docs/members/payroll.md) in Pike posts approved hours for each hourly employee to Employment Hero as timesheet entries, one per employee and day, with the work type from your **Pay codes** mapping. | Pike pay line | Sent to Employment Hero as | | - | - | | Normal hours | Timesheet entry with the ordinary hours work type | | Overtime 1 | Timesheet entry with the first overtime work type | | Overtime 2 | Timesheet entry with the second overtime work type | The [working time policy](https://usepike.com/docs/members/working-time.md) sets the split between normal hours and overtime. The entries are paid in the next Employment Hero Payroll pay run for the employee's pay schedule. Salaried employees' hours are not sent, and leave is not sent because it comes from Employment Hero. ## Matching and duplicates On the first import, Pike matches before it creates: * An employee matches a Pike member with the same company email. A match links the two, and Employment Hero values replace the Pike values for the fields in the mapping. * A team matches a Pike team with the same name. A job title matches a Pike position with the same name. * Leave always imports as new time off. Time off already entered in Pike for the same member and dates stays, and the Employment Hero request is listed in **Sync issues** as an overlap. An employee 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 employee 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 | Employment Hero owns | Pike owns | | - | - | - | | Members | Name, company email, position, team, manager, status, dates, work hours | Role, rates, working time policy, project access, allocations | | Time off | Dates, hours and category of leave from Employment Hero | Time off requested in Pike | | Cost profiles | Salary rows, when compensation sync is on | Cost profiles, when compensation sync is off | | Hours to payroll | The pay run and everything calculated in it | Approved time, overtime split and pay lines | Edit Employment Hero-owned fields in Employment Hero. Pike shows them as read-only with the Employment Hero marker. ## Sync schedule Pike syncs Employment Hero every 3 hours. On the Enterprise plan, changes sync in real time. Closing a pay period sends its timesheet entries straight away on every plan, and so do **Import data**, **Sync now** and **Refresh** on a member. See [How sync works](https://usepike.com/docs/integrations/how-sync-works.md). ## Sync settings While Employment Hero is connected, the **What syncs with Employment Hero** card is below the top button row on the integration page. Toggles save immediately. | Entity | Read | Send | | - | - | - | | Employees | Yes | Not available | | Time off | Yes | Not available | | Compensation | Off by default, admins and finance users only | Not available | | Hours to payroll | Not available | Yes, off by default | New connections start with **Read** on for employees and time off, **Invite new employees** off, compensation off, and **Send hours to payroll** off. ## How it works ```mermaid theme={"system"} sequenceDiagram participant HR as HR in Employment Hero participant EH as Employment Hero participant Pike participant Admin as Payroll admin in Pike HR->>EH: Approve annual leave for Friday EH->>Pike: Approved leave, on the next sync or in real time Pike->>Pike: Remove 7.6 hours from Friday capacity Admin->>Pike: Approve timesheets and close the pay period Pike->>EH: Timesheet entries for hourly employees, straight away EH-->>Pike: Entries accepted Pike-->>Admin: Pay period shows Sent to Employment Hero ``` ## Use it in Pike ### Plan around approved leave Open **Members → Allocations** to see each person's capacity for the week. Approved Employment Hero leave shows on the day with its 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 employee is added in Employment Hero, they appear in Pike with their team, position, manager and work hours on the next sync. Turn on **Invite new employees**, or click **Invite** under **Unmatched employees**, and the person can log time on their first day. ### Offboard a leaver When an employee is terminated in Employment Hero, the member is deactivated in Pike. Their logged time, allocations and history stay on every project, and they stop counting toward capacity from the termination date. ### Pay hourly staff from approved hours Go to **Members → Payroll**, resolve any flags, and click **Close period**. Approved hours for hourly employees post to Employment Hero as timesheet entries, so the pay run uses the same hours you bill from and nobody re-keys timesheets. ## Deletes and removed records An integration never deletes Pike data. An employee deleted in Employment Hero is marked **Removed in Employment Hero** on the member, stays in Pike with their history, and stops syncing. A leave request canceled in Employment Hero after approval is removed from Pike capacity on the next sync, and the change appears in the member's time off history. Timesheet entries already sent stay in Employment Hero. A correction to a closed period goes in the next period as an adjustment. ## Troubleshooting | Symptom | Fix | | - | - | | An employee is missing in Pike | Check that **Read** is on for employees and that the employee has a company email in Employment Hero. Then click **Sync now**. | | An employee shows under **Unmatched employees** | The company email in Employment Hero differs from the member's email in Pike. Click **Link to member**, or correct the email in Employment Hero. | | Approved leave is missing | Check that **Read** is on for time off and that the leave request is approved in Employment Hero. Then click **Refresh** on the member. | | Time off shows the wrong type | The leave category 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 a duplicate timesheet entry | Employment Hero already has a timesheet entry for that employee and date. Remove the entry in Employment Hero, then click **Retry**. | | A pay line is held back on the payroll page | The pay line has no work type. Map it under **Pay codes**, then close the period again or click **Retry**. | | **Sync issues** lists an authentication error | The Employment Hero admin who authorized Pike lost access, or the app was removed. Reconnect with a current Employment Hero admin. | ## Limits * Salaried employees' hours are not sent. * Pike does not run payroll or calculate tax, superannuation, pension or leave accruals. * Only approved time in a closed pay period is sent. * Pike does not create or change employees, teams or leave in Employment Hero. * Pending, declined or canceled leave requests do not sync. * Compensation sync is off until an admin or finance user turns it on. * One Pike workspace connects to one Employment Hero organisation. ## Disconnect Go to **Workspace settings → Integrations → Employment Hero** and click **Disconnect**. Syncing stops, no more timesheet entries are sent, and every member, team, position and time off entry stays in Pike with its history. Reconnecting the same Employment Hero organisation relinks the members. ## Related * [How sync works](https://usepike.com/docs/integrations/how-sync-works.md): The schedule, real-time sync and sync issues. * [Pay periods and payroll](https://usepike.com/docs/members/payroll.md): Period close, pay lines and pay codes. * [Time off](https://usepike.com/docs/members/time-off.md): Time off types and how they count toward capacity. * [Humaans](https://usepike.com/docs/integrations/humaans.md): People, time away and working patterns. * [Personio](https://usepike.com/docs/integrations/personio.md): Employees, absences and work schedules. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.