Academic Jobs - Home of Higher Ed Logo

ATS Integration in Universities: Connecting Hiring to HRIS, Onboarding and Identity

10 min read0 views

At a glance

University hiring rarely stalls in the interview room. It stalls in the gap between the applicant tracking system and the HRIS, where offers become payroll records and logins. Here is what integration actually moves, where it fails, and what standards now make it easier.

A train station with a sign for the australian institution of management
Photo by International Student Navigator Australia on Unsplash

The handoff nobody owns

The question I hear most from university partners this year is some version of: why does everything go quiet after the offer? A search committee finishes its work, the preferred candidate accepts, and then three weeks pass in which nothing visible happens. No contract, no email address, no way to log in. From the outside it looks like indifference. From the inside it usually looks like a diagram with a gap in it.

The gap sits between the applicant tracking system (ATS) — the software that holds the vacancy, the applications and the interview notes — and the human resource information system (HRIS), which is where a candidate becomes an employee with a position number, a pay grade and, eventually, a login. In most institutions those two systems were bought years apart, by different offices, for different reasons. They have never had a proper conversation.

The California State University system publishes a plain example of how this plays out. Its Workday recruiting FAQ explains that a new hire's Net ID is generated at the midpoint of the hiring process and has to be created outside Workday, because the person needs that ID to sign in and complete their onboarding tasks. Nothing about that is negligent. It is simply an architecture that assumes someone will bridge the space by hand.

What ATS–HRIS integration actually moves

Strip the acronyms back and the flow is straightforward. A department gets approval for a post. The requisition is created in the HRIS or enterprise resource planning (ERP) platform — Workday, Oracle PeopleSoft, Ellucian Banner and Colleague are the names most campus HR teams work with. That requisition becomes a live vacancy in the ATS, where candidates apply and the committee records its decisions.

Then the candidate accepts, and the interesting part begins. Integration means the accepted offer writes itself back into the HRIS as a hire record without an administrator retyping the name, date of birth, position and start date. From that record, three further connections usually follow: payroll and benefits enrolment, onboarding task assignment, and identity provisioning into Microsoft Entra ID, Okta, Active Directory or Google Workspace so the person has an account on day one.

Vendors sell these connections as connectors. PeopleAdmin's connector for its higher education platform, for instance, is marketed as real-time bi-directional data flow between its ATS and Banner, Colleague, Workday and PeopleSoft. Aquera reads Ellucian Banner through the vendor's Ethos Integration layer and pushes identities into whatever directory a campus runs. The technical vocabulary differs — REST APIs, SCIM, flat-file drops, scheduled batch jobs — but the promise is the same: enter the data once, and let the systems agree.

Two standards matter for the plumbing. SCIM, the System for Cross-domain Identity Management, is the format most identity providers use to create and deactivate accounts. Microsoft's documentation describes an API-driven inbound provisioning model in which a source system posts user records to a bulk upload endpoint using SCIM structures, and attribute mapping is handled centrally rather than in custom code. That matters for campuses because it means a student information system or an HR platform can feed identities into the directory without a bespoke script per institution.

PeopleAdmin's own research, published on its blog, found 64 per cent of administrators worried about technology silos and 88 per cent saying the absence of a unified ecosystem kept them from realising their platform's potential. Treat vendor surveys with the caution they deserve. Still, the direction of travel on campus is not in dispute.

a black and white sign with a red shield on it

Photo by Xiangkun ZHU on Unsplash

The day-one problem is an identity problem

Ask new starters what went wrong and they rarely describe the interview. They describe the first fortnight. A UC Berkeley human resources review of new employee feedback collected comments such as one from a faculty member who was told their payroll status took well over a month to straighten out, and another who calculated that without a personal email account carried over from a previous employer, they would have gone nearly five weeks without email. Someone else noted that it took two weeks to be processed into the system, during which nothing could be done without a photo ID.

These are not edge cases in large institutions. They are the predictable output of a chain in which each link waits for the previous one, and no single person is accountable for the end-to-end result.

Where identity work has been automated, the numbers move. Seminole State College of Florida, a four-campus public college, replaced a mix of scripts and spreadsheet tracking with a SailPoint deployment built on out-of-the-box connectors to PeopleSoft, Active Directory and Entra ID. Before the change, provisioning at semester peaks stretched to between 24 and 48 hours. The college went live in six months. Vendor case studies are marketing, but the underlying arithmetic is not: a manual chain slows precisely when volumes spike, which on a campus is the start of term.

Other suppliers make bigger claims. Unifyed, working with QuickLaunch, says automated identity lifecycle management tied to student and HR data can cut onboarding time by up to 80 per cent and reduce account-setup support tickets by up to 70 per cent. Those figures come from the companies selling the software, so they belong in a business case as a hypothesis to test, not as a given.

Standards are arriving, slowly and unevenly

The most useful development of the past two years is not a product. It is an agreement about what data should look like when it leaves one system and arrives at another. 1EdTech, the nonprofit formerly known as IMS Global, publishes Edu-API, a specification for exchanging core academic enterprise data — people, organisations, courses, enrolments, outcomes — between student information systems and the applications around them. It builds on the older Learning Information Services model and, deliberately, avoids tying itself to a single transport technology.

The certification record is beginning to fill in. Sweden's national student system, Ladok, announced in mid-2025 that it had become the first certified producer under Edu-API. Oracle's PeopleSoft Campus Solutions became the first student information system certified against the standard, and its product documentation now describes provisioning of persons, class information, academic periods and enrolments using REST and JSON. Greek institutions working through the UniversiS platform have gone the same route. The specification itself is still at Candidate Final Public status on the road to a first full version, which tells you how early this remains.

Employment data has a parallel track. The HR Open Standards Consortium, founded in 1999 as the HR-XML Consortium, publishes free HR-JSON and HR-XML specifications covering recruiting, screening, interviewing and payroll. Its recruiting standard defines the candidate record, the position opening and the search document — the structures an ATS needs when it talks to a job board or a resume bank. Australia's SEEK built its public API schema on those conventions, which is one reason a posting can move between systems without a translator.

For a hiring team, the practical consequence is simple. When you write a systems requirement, ask whether the vendor supports Edu-API or HR-JSON natively, and ask for the conformance certificate rather than a verbal assurance. Institutional customisation is where integration projects go to die.

black and white i am a good man text

Photo by Arno Senoner on Unsplash

The clock, and where integration actually touches it

Time to fill is the measure most HR divisions now report upward. Benchmark compilations for 2025 put education at around 52 days on average, against a best-in-class figure near 38 days. An earlier NEOED survey of education HR professionals found 55 per cent estimating two to six months to fill a post, against a private-sector average then reported at 37 days.

The University of Central Florida is a useful case because its board of trustees wrote the reasoning down. Having moved to Workday, the university adopted a time-to-fill benchmark of 45 to 50 calendar days, switched from business days to calendar days for consistency, and noted that faculty hires can span months because of their structure. It also acknowledged that a lack of integrated systems and unclear ownership had left colleges to work it out alone.

Now compare the Australian rhythm. In submissions to a parliamentary inquiry on labour market testing, UNSW Canberra set out a 22-week timeline for Level A to D academic appointments and 31 weeks for Level E professorships, with advertising alone running four to twelve weeks. ANU described processes that often take up to 20 weeks to select and secure a candidate, before visa nomination adds more. Read those two documents side by side and the lesson for anyone planning an international campaign is that integration affects specific weeks, not the whole calendar: the front end where a position is created and approved, and the back end where an offer converts into a contract, a visa and a payroll record. Committees and teaching schedules dominate the middle. Software cannot shorten a panel's deliberations, but it can stop a fortnight disappearing between the acceptance email and the contract.

What to fix before the next recruitment round

Most of the remedies are unglamorous and cheap relative to a failed search. They start with naming the ten or twelve fields that must survive the journey from application to payroll without human retyping: legal name, preferred name, date of birth, position number, department code, start date, contract type, salary, work location and visa status. Every one of those fields has an owner in some system. Very few institutions have written down which system is authoritative for each.

Then there is the rehire and multi-role problem, which catches almost every campus. A doctoral student who has worked as a casual tutor, then as a research assistant, then applies for a lectureship, will often exist in three records and arrive in the directory as a fourth. Systems that match on name and date of birth make duplicates; systems with a proper person identifier do not. Identity platforms built for higher education handle this by resolving multiple roles to one person, but only if the source system carries an identifier that survives the transition.

Finally, there is the candidate-facing side, which is where the reputation of the whole process is made. A portal that requires a new account for every application, or an onboarding checklist that cannot be opened until an ID exists, tells a prospective lecturer something about how the institution treats people. The institutions that get this right tend to have one administrator who owns the candidate's experience week to week, and who is empowered to chase IT, payroll and the department without asking permission.

That is also where a specialist jobs portal earns its place. AcademicJobs.com connects with the applicant tracking systems institutions already run, so a vacancy posted internally can appear to a global academic audience and applications can return to the same system the committee works in, without an administrator copying files between them. The value is not the listing. It is that the candidate record never leaves the system of record.

If you take one step this month, make it this: pick a single appointment already in progress and trace it, field by field, from the moment the offer was accepted to the moment the new starter could open their email. Write down every point where a human retyped something or waited for another office. That list is your integration business case, and it will be more persuasive to a vice-chancellor than any vendor demonstration.

  • higher-education-recruitment
  • onboarding
  • university-hr-technology
  • ats-integration
  • identity-management
Portrait of Prof. Sophie Martinez
About the author

Prof. Sophie MartinezView author

Academic Jobs In House Author

Sophie Martinez manages client relationships at AcademicJobs, serving as the primary liaison between the platform and its university partners. With a background in higher education administration, she brings a deep unde…

Discussion

Sort by:

Be the first to comment on this article!

You

You’ll be asked to sign in before your comment is posted.

Frequently Asked Questions

🔗What does ATS integration mean for a university?

Applicant tracking system (ATS) integration is the set of connections that let the software holding vacancies and applications exchange data with the other systems a campus runs. In practice that means an accepted offer creating a hire record in the human resource information system (HRIS) without retyping, and that record triggering payroll set-up, onboarding tasks and an identity account in Microsoft Entra ID, Okta or Active Directory. Without integration, an administrator moves the same information by hand between systems that were bought separately.

🏛️How does an ATS connect to Workday, Banner or PeopleSoft?

Usually through vendor connectors, APIs or scheduled file transfers. PeopleAdmin, for example, markets a connector providing bi-directional data flow between its platform and Ellucian Banner and Colleague, Workday and Oracle PeopleSoft. Third-party tools such as Aquera read Ellucian Banner through its Ethos Integration layer and write identities into whichever directory a campus uses. The important question for a hiring team is not whether a connector exists but which system is authoritative for each data field.

🪪What is SCIM and why does it matter for onboarding?

SCIM stands for System for Cross-domain Identity Management. It is the schema identity providers use to create, update and disable user accounts across systems. Microsoft's documentation on API-driven inbound provisioning describes how a source system such as an HR platform or student information system can post records to a bulk upload endpoint using SCIM structures, with attribute mappings managed centrally. For a campus, that removes the need for a custom script for every new application.

⏱️Why do new staff often wait days or weeks for IT access?

Because the account creation step sits at the end of a chain. A hire record must exist in the HRIS before identity provisioning can run, and provisioning rules often depend on attributes that only payroll or the department can supply. UC Berkeley's review of new employee feedback recorded people waiting weeks for email and system access, and one faculty member describing it as taking two weeks simply to be processed into the system. Automating the chain, as Seminole State College did with SailPoint and PeopleSoft, shortens it, but only when the attributes are complete at the point of hire.

📋What is Edu-API and why are universities asking vendors about it?

Edu-API is a 1EdTech specification for exchanging core academic enterprise data — people, organisations, courses, enrolments and outcomes — between student information systems and the applications around them. It builds on the older Learning Information Services model and uses REST with JSON payloads. Oracle's PeopleSoft Campus Solutions became the first student information system certified against it, and Sweden's Ladok became the first certified producer. Asking vendors for a conformance certificate rather than a verbal assurance is now a reasonable procurement expectation.

📈Does better integration actually reduce time to hire?

It reduces specific portions of it. Benchmark compilations for 2025 put education at about 52 days average time to fill, with best-in-class near 38 days. The University of Central Florida adopted a 45 to 50 calendar day benchmark after moving to Workday and standardising its hiring steps. Integration acts at the edges — creating and approving the position, and converting an accepted offer into a contract, payroll record and login. It cannot compress a search committee's schedule or a candidate's notice period.

🧾Which fields must survive the ATS to HRIS handoff?

At minimum: legal name, preferred name, date of birth, position number, department or cost centre code, start date, contract type, salary, work location and visa or right-to-work status. Institutions that have mapped these fields and named an authoritative system for each tend to avoid the duplicates and payroll corrections that follow a manual handoff. The exercise is short, and it usually reveals two or three fields that no one has ever owned.

👥How should integration handle rehires and people with several campus roles?

With a person identifier rather than a name match. A doctoral student who has worked as a casual tutor and a research assistant before applying for a lectureship will often exist in several records, and name-and-date-of-birth matching creates duplicates rather than resolving them. Higher education identity platforms are built to resolve multiple roles to one person, but only when the source system passes an identifier that persists across the transition.

🛠️What is the first step for an institution starting this work?

Trace one live appointment from the moment the offer was accepted to the moment the new starter could open their email. Note every point where somebody retyped data or waited on another office. That record becomes the integration business case, and it is more persuasive to a vice-chancellor than a vendor demonstration because it carries real dates and real names of processes that failed. Only then decide whether the fix is configuration, a connector or a change in who owns the process.

🌍Where does AcademicJobs.com fit into a university's ATS?

AcademicJobs.com connects with the applicant tracking systems institutions already run, so a vacancy can reach a global academic audience and applications can return to the same system the search committee works in. The point is that the candidate record stays in the system of record rather than being copied between platforms, which keeps the audit trail intact for later reporting and compliance.

ATS Integration for Universities: HRIS, Onboarding,… #29691