Skip to content

Staffing & ERP integration

Bullhorn COI compliance integration

Stop starting placements under a lapsed or missing certificate. Pikorua Security reads client companies, job orders and placements through Bullhorn's REST API, verifies the certificates your contracts require from clients, supplier agencies and independent contractors, and writes compliance status and expiration dates into ClientCorporation custom fields that recruiters see before a start is confirmed.

Bullhorn logo

Bullhorn, Columbus light industrial branch

Placement #88412

Start at risk

Start flagged: client COI deficient

Client general liability expired 10/10/2026. Account manager notified four days before the start.

ClientCorporation
Tri-State Packaging Corp.
Job order
Forklift Operator, 2nd shift
Start date
10/20/2026
COI status (customText7)
Deficient
COI expiration (customDate2)
10/10/2026

Written by Pikorua Security Oct 16, 2026, 06:00 AM ET

Setup time
45 minutes
Connection
Bullhorn REST API + OAuth 2.0
Fields synced
7 fields, 5 trigger events
Included on
Professional and Enterprise

Sync fields

What Pikorua Security reads from and writes to Bullhorn.

Filter by direction. Pikorua Security writes compliance fields only; amounts, approvals and banking details stay with your team.
Fields Pikorua Security syncs with Bullhorn
FieldDirectionWhat happens
ClientCorporationBullhorn to Pikorua SecurityClient name, address, status and owner, matched to Pikorua Security counterparties.
JobOrderBullhorn to Pikorua SecurityJob title, worksite address and start date, so worksite-specific requirements (a refinery, a hospital) are applied.
PlacementBullhorn to Pikorua SecurityStart and end dates, candidate and client, read from Bullhorn's event subscription queue so new starts are checked within minutes.
ClientCorporation custom text: COI statusPikorua Security to BullhornCompliant, Deficient, Expiring or Missing, in a custom field you choose and can add to list views.
ClientCorporation custom date: COI expirationPikorua Security to BullhornEarliest expiration among the required coverages, so a saved search shows clients going stale in the next 30 days.
Certificate file attachmentPikorua Security to BullhornThe verified certificate and endorsement pages, attached to the ClientCorporation record.
Placement notePikorua Security to BullhornA note on the Placement when the start date falls in a period without verified coverage, visible to the recruiter and onboarding team.

Trigger events

When the certificate changes, Bullhorn changes with it.

Each trigger is a rule you can switch on, off or to notify-only per project, property or vendor tier.
How payment and access gates work
  1. Hold

    Placement created for a client or supplier with expired coverage

    Then: A note is added to the Placement and the account manager is emailed before the start date; the client's COI status reads Deficient.

  2. Hold

    Client's general liability lacks the additional insured endorsement your contract requires

    Then: COI status set to Deficient with the missing form named, and the client's risk contact receives a request with a zero-login upload link.

  3. Hold

    Alternate employer endorsement (WC 00 03 01) missing on a supplier agency's policy

    Then: Supplier flagged Deficient so recruiters stop routing new orders to it until the endorsement is verified.

  4. Warn

    Coverage expiring in 30 days

    Then: Expiration field updated so the saved search picks the client up, and the broker is chased on the 60/30/15/0 day cadence.

  5. Release

    Renewal verified

    Then: COI status returns to Compliant and the placement note is marked resolved.

Setup

Live in 45 minutes.

5 steps, done by your Bullhorn administrator and a Pikorua Security Admin together. Nothing to install on your servers.

Bullhorn logoBullhorn REST API + OAuth 2.0
  1. 1

    Choose the fields

    Pick two unused ClientCorporation custom fields, one text and one date, and label them COI status and COI expiration in Bullhorn's field mappings.

  2. 2

    Authorize Pikorua Security

    A Bullhorn administrator signs in through Bullhorn's OAuth 2.0 authorization page from Pikorua Security's Integrations screen, as an API user with access to client, job and placement records.

  3. 3

    Match clients and suppliers

    Pikorua Security imports ClientCorporation records and proposes matches to counterparties already in Pikorua Security.

  4. 4

    Set requirement templates

    Assign requirements by client type, such as light industrial, healthcare or office, and by any client contract with its own insurance exhibit.

  5. 5

    Start the event subscription

    Pikorua Security subscribes to Placement and ClientCorporation events and checks new placements as they arrive.

Where insurance risk sits in a staffing book

In staffing, the certificate question runs in more than one direction. Client contracts often require the agency to carry workers compensation with an alternate employer endorsement and to name the client as additional insured. Many agencies in turn require clients to carry general liability for the worksites where temporary workers report, and they rely on supplier agencies and independent contractors whose coverage must be verified before anyone starts. Bullhorn holds the commercial relationships. It does not read certificates.

Pikorua Security does, and it writes the answer into Bullhorn where recruiters and account managers already work: the ClientCorporation record, a saved search, and a note on the Placement.

Placements are the moment that matters

A lapsed client policy matters most on the day a worker starts. Pikorua Security reads Placement events from Bullhorn's event subscription queue every few minutes and checks each new start against the current verdict for the client and any supplier involved. If something is missing, the account manager hears about it while there is still time to fix it, not after an injury report.

Bullhorn access tokens are short-lived, so the connector refreshes them continuously and logs every call. Writes are limited to the custom fields, notes and file attachments you approve.

FAQ

Bullhorn connector questions.

Pikorua Security is compliance software. It verifies certificates and endorsements against your contract requirements; it does not sell insurance or give legal advice.

Which Bullhorn records does Pikorua Security change?
Only the two ClientCorporation custom fields you choose, notes on Placements, and certificate file attachments. It never edits candidates, pay rates, bill rates or job order details.
Does it see candidate personal data?
Pikorua Security reads the candidate ID and name on a Placement to label the note. It does not read Social Security numbers, pay data or documents attached to candidates.
How fast are new placements checked?
Within a few minutes. Bullhorn delivers changes through an event subscription queue that Pikorua Security reads on a short interval, so there is no inbound webhook to configure on your side.
Can it block a placement from starting?
Bullhorn has no insurance hold on placements, so Pikorua Security flags rather than blocks. Many agencies add the COI status field to their start checklist so a Deficient client cannot be marked ready to start.

14-day free production trial

Connect Bullhorn during your 14-day trial.

Upload your current certificates, authorize Bullhorn, and see which vendors would be on hold today before you switch a single rule on.