
Workday connects seamlessly with TeamOhana to make headcount planning and management easier than ever. TeamOhana's integration with Workday automates the maintenance of the hiring plan and ensures that all workforce updates are tracked.
Workday connects seamlessly with TeamOhana to make headcount planning and management easier than ever. TeamOhana's integration with Workday automates the maintenance of the hiring plan and ensures that all workforce updates are tracked.
Workday is a leading provider of enterprise cloud applications for finance and human resources, helping customers adapt and thrive in a changing world. Workday Adaptive Planning is an Enterprise Performance Management (EPM) software commonly used by Finance and FP&A teams.
When new employees are hired and added to Workday, TeamOhana will automatically link them to the headcount they were hired to fill, and will update the hiring plan with no manual intervention required
TeamOhana's integration with Workday enables you to see how your approved hires will fit into your existing org structure with a dynamic org chart
Hourly updates from Workday mean you'll never again need to wonder if your current employee count is accurate
When new employees are hired and added to Workday, TeamOhana will automatically link them to the headcount they were hired to fill, and will update the hiring plan with no manual intervention required
TeamOhana's integration with Workday enables you to see how your approved hires will fit into your existing org structure with a dynamic org chart
Hourly updates from Workday mean you'll never again need to wonder if your current employee count is accurate
Utilize a Dynamic Org Chart with all relevant people data.
Utilize a Dynamic Org Chart with all relevant people data.
Simplify and centralize headcount requests and make better approval decisions with an audit trail for visibility.
The Application Object is used to represent a candidate's journey through a particular Job's recruiting process. If a Candidate applies for multiple Jobs, there will be a separate Application for each Job if the third-party integration allows it.
The Benefit object is used to represent a benefit that an employee has enrolled in.
The Candidate object is used to represent profile information about a given Candidate. Because it is specific to a Candidate, this information stays constant across applications.
The Department object is used to represent a department within a company.
The Group object is used to represent any subset of employees, such as PayGroup or Team. Employees can be in multiple Groups.
The JobInterviewStage object is used to represent a particular recruiting stage for an Application. A given Application typically has the JobInterviewStage object represented in the current_stage field.
The Job object can be used to track any jobs that are currently or will be open/closed for applications.
The Location object is used to represent an address that can be associated with an employee.
The Office object is used to represent an office within a company. A given Job has the Office ID in its offices field.
The TimeOff object is used to represent all employees' Time Off entries.
The TimeOffBalance object is used to represent current balances for an employee's Time Off plan.
The RemoteUser object is used to represent a user with a login to the ATS system.
The sync between TeamOhana and Workday updates once every hour.
Yes we do! All changes made in Workday, whether it's a reporting manager update, a pay raise, or a name change will all be captured in the employee's profile in TeamOhana - no manual updates necessary.
No, TeamOhana works with or without Workday position management. Without position management, TeamOhana creates headcount IDs that map directly to ATS openings and then reconciles with employees in Workday. Using position management adds complexity but can be integrated if required, with TeamOhana pushing to position management which then flows to your ATS.
TeamOhana needs job families and job levels associated with hiring locations and pay zones, but doesn't need job descriptions or complete profile details. During implementation, TeamOhana imports your job architecture from a file export, allowing it to auto-populate compensation information based on selections. The job architecture data is updated periodically rather than in real-time.
TeamOhana automatically matches employees across systems using algorithms and identifiers like email address and name. When an employee is hired through the ATS and appears in Workday, TeamOhana links them to their originating headcount. For unmatched records, TeamOhana flags them for manual reconciliation through a simple interface.
No, TeamOhana doesn't automatically update when changes occur in Workday's job architecture. Instead, organizations send updated job architecture files when ready (typically quarterly or annually). This controlled approach prevents unexpected changes in compensation bands from automatically affecting budget forecasts without review.