ATS integration checklist for job boards and payroll
Scope ATS access, job-board updates, candidate matching, approved hours, payroll reconciliation and exception handling before committing to an integration.
Recruitment teams often need to improve the handoffs around an applicant tracking system before deciding whether to replace it. A vacancy can exist in the ATS while job-board updates are delayed, applicants are duplicated or approved hours still need to be copied into payroll. Start with one handoff and define what a reliable result looks like.
This checklist helps UK staffing operators scope an integration with an existing ATS. It separates discovery questions from promises about a particular product or subscription. Supported interfaces, vendor agreements and the agency's pay rules determine the final scope.
Confirm the exact product and access first
Record the ATS product, edition, account owner and available integration routes. Ask which API or export permissions are already included and which need a separate agreement. Identify the test environment, technical contact and who can approve changes.
For example, Bullhorn's current API usage guidance says API access and limits depend on the edition and integration arrangement. Do not assume that a successful demonstration against one account proves another account has the same access. Confirm the position with the vendor before quoting implementation or promising a delivery date.
Write down the system of record
Agree where each record is owned: vacancies, applicants, candidates, placements, clients, timesheets and payroll outcomes. Define which system can change each field and what happens when two systems disagree. A field mapping should include the source identifier, destination identifier, required format and exception owner.
This is also the point to agree which candidate information may move between systems, who needs access and how deletion or correction requests are handled. Bring the agency's data-protection requirements to discovery; the integration design does not replace a legal assessment or the agency's own responsibilities.
Scope the job-board handoff
Choose one approved vacancy and one supported board. Describe the trigger for publishing, the fields sent, the acknowledgement expected and the action for a rejection. Include changes to salary, location and closing date, plus withdrawal of the vacancy.
Then test an application returning to the ATS. Agree how the integration matches an existing candidate, handles a duplicate application and records the source. A successful vacancy export is only half the journey. Keep a visible record of rejected updates so consultants know when a board has not received a change.
Separate payroll rules from data transport
For timesheet-to-payroll work, map placement identifiers, approved hours, pay codes, amendments and approval status. Agree the payroll cut-off and what should happen to a correction received afterwards. Identify who resolves unmatched placements or missing approvals before anything is treated as ready to pay.
Illustrative acceptance check: the same approved timesheet is sent twice after a connection failure. The expected result is one accepted payroll item or an explicit duplicate response, with an audit trail. This example defines behaviour to test; it is not a claim about a delivered client project.
Reconcile counts and totals between the source and destination. A transport-level success response is useful evidence, but the payroll team still needs to confirm that the agreed records were accepted correctly.
Plan failure handling and ownership
Ask what happens when a provider is unavailable, credentials expire or a request is rate-limited. Temporary failures may justify a bounded retry; rejected business data usually needs correction or human review. Keep enough context for the responsible team to find the failed record without exposing unnecessary candidate data.
Microsoft's workflow error-handling guidance describes failure branches, grouped error handling, retries and logging. Those principles are useful when reviewing a proposal even if Power Automate is not the chosen platform. Decide the retry limits and escalation path, rather than relying on a promise that the integration will run automatically.
Ask for a scoped first release
A useful discovery output is a workflow map, access assumptions, field mapping, acceptance checks, exception ownership and an estimate for the first handoff. Separate implementation, vendor charges, subscription costs and ongoing support in the commercial proposal.
Keep ATS replacement as a separate decision. If the current platform supports the required process, an integration may be the smaller change. If the constraints make that impractical, document them before evaluating a migration. Review our recruitment ATS integration approach, or use the Bullhorn to Omni ATS migration guide when replacement is the buying decision.
Reviewed 20 November 2026. Product access and vendor terms should be reconfirmed for the specific account.
Recruitment ATS integration
Connect applicant tracking software to candidate portals, compliance, timesheets, payroll, and reporting.
