Fill the fields the law needs from Bullhorn: salary range, benefits, closing date, employment type, agency status
As of 6 November 2026, 14 US states plus DC require a pay range in the posting, seven of them also require a benefits description, and Colorado requires a dated application deadline. On a Bullhorn career site those lines come from four job order fields (salary range, benefits text, closing date, employment type) and one board setting, the agency's name and status. These rules come from Jan Jedlinski's research of 6 November 2026, and the fields sit on the Bullhorn job order, which our Bullhorn integration reads.
Benjamin BartakovicsCo-Founder & CPO7 min read
Ask AI
Rules as of 6 November 2026Based on our own research. Not legal advice and not legally binding.

In short
- As of 6 November 2026, 14 US states plus DC put the pay range in the posting, so a job order with no range cannot feed a compliant post.
- Seven of those states also require a general benefits description, and Colorado requires an estimated closing date, where "open until filled" does not comply.
- In Great Britain, every agency ad must carry the agency's full name and say whether each job is temporary or permanent.
- For each field, decide what the board does when the job order leaves it empty: refuse to publish, use a default, or ask the recruiter.
- The pay a posting shows is what the candidate earns, so the board should read the pay rate and never the client bill rate.
On this page
- Why do these fields fail on a Bullhorn career site?
- Decide what happens when a field is empty
- Make the board read the candidate's pay, never the bill rate
- Write the benefits line once per client or per job
- Set the closing date and the posting date
- Map employment type to a temporary or permanent label
- Add the agency name and status line
- Keep each posting as published
- What should I ask my web vendor or developer for?
Each state's rule is in the tracker, and every field a compliant post carries is in the 23-field checklist.
Why do these fields fail on a Bullhorn career site?
The report reads the Bullhorn fields behind these lines as optional at the job order level, so a board that publishes straight from the job order publishes whatever the recruiter left out. Bullhorn's pages do not say so, and the report also lists these as the items most often missing from a Bullhorn career site template.
Bullhorn documents one gap itself: its help page lists "Compensation and salary fields" among the fields LinkedIn Apply Connect does not transmit. So the career site is where pay transparency laws, which make pay visible to candidates, get their range.
The costliest mistake sits beside these fields: a template reading the client bill rate shows your price as the wage (Step 2).
For your developer: the job order is the source, the template is the gate
Have the template read the board's job model, filled from the job order, and run every publish through the Step 1 check. The Bullhorn field names here (payRate, clientBillRate, salary, dateEnd) are guidance to check against Bullhorn's REST API reference for the JobOrder entity and your own account, which may use custom fields.
Step 1: Decide what happens when a field is empty
Pick one rule per field: refuse, default or ask.
| Field | What the law needs | Rule when the job order leaves it empty |
|---|---|---|
| Pay range | Both ends of the range | Refuse to publish and ask the recruiter |
| Benefits | A general description | Default to the line written for that client |
| Closing date | An estimated date on Colorado jobs | Ask the recruiter; refuse for Colorado |
| Employment type | Temporary or permanent | Refuse to publish |
| Agency name and status | On every ad in Great Britain | Default from the board's settings |
Asking also helps in Illinois. Its law names the third party, anyone who posts for the employer: a recruiter, a staffing agency, a job board. The rule applies when it posts for an Illinois employer with 15 or more employees.
The third party is then liable for a missing pay scale and benefits "unless the third party can show that the employer did not provide" them (820 ILCS 112/10). The report advises a dated record of the pay data the client supplied; log your request in it.
For your developer: one publish check
Run it on publish and on every change (sample only):
function publishCheck(job) {
const missing = [];
const hasRange = job.payMin != null && job.payMax != null;
if (!hasRange && job.payFixed == null) missing.push("pay");
if (job.payFixed != null && !job.fixedPayAllowed) missing.push("pay range");
if (!job.employmentLabel) missing.push("employment type");
if (job.reachesColorado && !job.closingDate) missing.push("closing date");
return missing.length ? { publish: false, askRecruiter: missing } : { publish: true };
}Step 2: Make the board read the candidate's pay, never the bill rate
A pay range is the lowest and highest pay the employer in good faith expects to pay: what the candidate earns. A template that reads the client bill rate publishes your price as the wage.
The report says Colorado, Washington, Illinois, New York, Minnesota, Maryland and British Columbia all reject "$X and up", "up to $Y", "DOE" (depending on experience) and "competitive".
Washington's guide, which we checked, rejects the open-ended forms. Washington and New York guidance accept one fixed figure where only one amount is offered; the report says the same holds everywhere, which we did not check.
For your developer: the pay fields
Read the candidate pay field (payRate on a temp job, salary on a permanent one) and never clientBillRate. Show a single figure only for states that allow one; otherwise fail the check. Our JobPosting tutorial writes the salary into the data Google reads.
Step 3: Write the benefits line once per client or per job
Write one benefits line per client, because seven states require a benefits description in the posting: Colorado, Connecticut, Illinois, Maryland, Minnesota, New Jersey and Washington. Here that means a general description of the benefits that come with the job, such as health insurance or paid leave, not a full plan.
Decide whose package it describes: yours on a temp job where you employ the worker, the client's on a direct hire. Illinois accepts a reference to a current benefits description in a public place on the employer's website. Delaware's law, pending until 26 September 2027, adds benefits for employers with more than 25 employees.
For your developer: job text, then client default
Read the job's own benefits text first, then the client's stored line, then the agency's own line.
Step 4: Set the closing date and the posting date
In Colorado, any employer with one or more employees in the state must put an estimated closing date on the posting (C.R.S. §8-5-201). The state's guidance says "open until filled" is not compliant. The INFO #9A guidance of the Colorado Department of Labor and Employment lets a position always open for recruitment say applications are "accepted on an ongoing basis". Our research could not confirm that a temp pool counts, so date pool ads. Agree with recruiters who sets the date and who extends it.
Google's JobPosting documentation, checked 6 November 2026, lists the posting date (datePosted) as required. It says the closing date (validThrough) "is required for job postings that have an expiration date", and "We don't allow expired job postings".
For your developer: two dates, two sources
An end date on the job order, such as dateEnd, may hold the assignment end rather than the closing date; confirm before you use it. Store the posting date at first publish.

Step 5: Map employment type to a temporary or permanent label
Give every job a visible temporary or permanent label: Great Britain requires one on every agency ad. The rule is regulation 27 of the Conduct Regulations, the UK rules for employment agencies and employment businesses. It covers every ad from an employment agency (the UK term for a perm recruiter) or employment business (the UK term for a temp agency). Each ad must say "whether it is for temporary or permanent work" (SI 2003/3319 reg 27). The regulations say an advertisement "includes every form of advertising by whatever means", which the report reads as covering a career-site job page. The Fair Work Agency has been the regulator since 7 April 2026.
For your developer: one mapping table
Map each employment type value to a visible label and to Google's employmentType, which has TEMPORARY but no permanent value, so a permanent job maps to FULL_TIME or PART_TIME. An unmapped value fails the publish check.
Step 6: Add the agency name and status line
Regulation 27 requires the agency's full name on every ad in Great Britain. In New York, a licensed employment agency's ads carry its name and address, the word "agency" and its licence number (GBL §187). Covered Ontario postings add a vacancy statement and any AI disclosure; the Ontario page has the rule.
For your developer: settings, not job order fields
Keep the legal name, status wording and licence number in the board's settings, and add the Ontario statements by job location.
Step 7: Keep each posting as published
You can prove a posting was right on the day only if you kept it, so ask for an archive of each posting as published, dated, with its job order. Test it on one closed job: the archive should show the page candidates saw.
What should I ask my web vendor or developer for?
Send the seven steps as one request once your recruiters agree the Step 1 rules, then check the JobPosting fields Google reads on two live jobs.
We build a job board for staffing agencies that syncs with Bullhorn in both directions, so we have a stake in how these fields reach the page.