Both parties are accountable, because the hirer controls the role information and the agency must act on it. The safest approach is to assign clear ownership for records, comparators, and communications before placements begin, so no one relies on assumptions when the equal-treatment date arrives.
Why accountability is shared when pay equivalence is disputed
The hirer and agency are accountable together, but for different parts of the process. The hirer owns the role facts that determine pay equivalence, while the agency must rely on, apply, and communicate those facts correctly. When the two disagree, the failure is usually not a single decision but a broken handoff between ownership, verification, and escalation.
That shared accountability matters because pay equivalence depends on evidence, not assumption. If the hirer’s role information is incomplete or inconsistent, the agency can misapply the entitlement. If the agency does not challenge unclear comparators or does not preserve the record of what was agreed, both sides can leave the worker exposed to delay or underpayment.
In practice, the accountability question is less about who is “at fault” and more about who must be able to prove their part of the process. The hirer should be able to show how the role, terms, and comparator were defined, and the agency should be able to show how that information was checked, relayed, and acted on before the equal-treatment date.
What each party owns in the pay-equivalence process
The hirer normally owns the role-side inputs: job content, pay-relevant duties, working conditions, and any changes that affect equivalence. If those details are wrong or stale, the downstream pay calculation is unreliable even if the agency processes it perfectly.
The agency owns the placement-side execution: recording the information, applying it to the worker’s terms, and escalating ambiguity instead of quietly guessing. That means the agency cannot treat the hirer’s input as automatically sufficient if the information is incomplete, contradictory, or not aligned to the placement record.
When the two parties disagree, the safe interpretation is that neither can outsource responsibility entirely. A hirer cannot assume the agency will “sort it out,” and an agency cannot assume the hirer’s description is self-validating. Shared accountability only works when each side has a distinct owner for the same business outcome.
How to prevent disputes before the equal-treatment date
The strongest control is to lock down ownership early, before placements start. That means agreeing who defines the comparator, who approves role changes, who updates records, and who issues worker communications when the evidence changes. Once the equal-treatment date arrives, there is usually little room to reconstruct missing decisions without dispute.
It also helps to make the recordable facts explicit. A clear record should capture the role description, the comparator basis, any agreed pay-equivalence adjustments, and the communication trail between hirer and agency. If the process depends on informal conversations, the dispute will almost always become a record-keeping problem as well as a pay problem.
For recurring placements, treat disagreement as a control weakness, not a one-off misunderstanding. The same ambiguity often reappears when the hirer changes the role, the agency changes account staff, or the worker moves across assignments without a refreshed comparator review.
Risk and Threat Considerations
Pay-equivalence disputes create exposure when one party assumes the other has already verified the facts. The main risk is delayed or incorrect pay treatment, but the deeper issue is loss of evidential control, because missing records make it hard to prove who knew what and when.
Failure mechanism: Role information, comparator data, or communication ownership is left informal, so each party believes the other is maintaining the authoritative record. When the entitlement date arrives, the organisation has no single source of truth and no reliable audit trail for the decision.
Impact: The worker may be underpaid or delayed, the dispute may escalate into a compliance or contractual issue, and both parties may spend time reconstructing decisions that should have been settled before placement. Repeated failures can also damage trust in the hiring process itself.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 sets the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| ISO/IEC 27001:2022 | A.5.2 — Information security roles and responsibilities | Clear ownership is central to resolving disputed pay-equivalence records. |
| A.5.15 — Access control | Controlled access to authoritative records supports accountability and prevents unauthorized changes. | |
| A.5.33 — Protection of records | The question turns on preserving reliable records for comparator and payment decisions. | |
| Recommendation — Assign and document responsibility for role records, comparators, and communications. Restrict who can alter placement and pay-equivalence records. Protect the evidence trail for role facts, approvals, and communications. | ||
| NIST SP 800-53 Rev 5 | AU-3 — Content of Audit Records | Audit detail is needed to prove who supplied and acted on pay-equivalence information. |
| AU-6 — Audit Record Review, Analysis, and Reporting | Reviewing records helps spot unresolved disagreement before entitlement dates pass. | |
| AC-6 — Least Privilege | Limiting who can change authoritative records reduces dispute and accountability drift. | |
| Recommendation — Log the facts, approvals, and changes that drove the pay-equivalence decision. Review placement records for mismatches and unresolved ownership gaps. Limit record changes to the smallest set of authorised staff. | ||
Practitioner Guidance
What to verify: Before any placement starts, verify that there is one named owner for role information, one named owner for pay-equivalence communications, and one agreed process for resolving mismatch. If those names are not written down, accountability will drift to whichever party is most active, not whichever party is most responsible.
Decision rule: If the hirer and agency disagree on comparators or role facts, pause reliance on informal agreement and require written clarification before the equal-treatment date. If the record cannot support the entitlement decision, treat the case as unresolved rather than forcing a weak assumption into production.
Practitioner takeaway: Shared accountability only works when ownership is split by function, not blurred by convenience, so the best defence is a written chain of responsibility for facts, review, and communication.
Related resources from NHI Mgmt Group
- Who is accountable when Oracle and an external governance layer disagree on SoD findings?
- Who is accountable when employee pay or tax documents are left visible on a shared device?
- Who is accountable when two vulnerability databases disagree on a critical issue?
- Who is accountable when a government agency purchases a cloud security platform without mapping its compliance obligations first?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 21, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org