Skip to main content

Paylocity Integration: Understanding Status Mapping

This article explains how Yardstik statuses map to Paylocity statuses for both Reports (Order-level) and Report Screenings (Service-level).

Updated this week

Reports

Each Yardstik Report status maps to a Paylocity Screening Order status:

Yardstik Status

Paylocity Status

created

WaitingOnCandidate

info_requested, exception

Hold

queued, processing, pending, approved_to_process, pending_approval, ys_qa_review

InProgress

consider

CompleteNeedsReview

clear, proceed

Complete

pre_adverse

PreAdverseActionSent

dispute

Dispute

final_adverse

AdverseActionSent

canceled

Cancelled

expired

InvitationExpired


Report Screenings

Each Yardstik Report Screening status maps to a Paylocity Service status:

Yardstik Status

Paylocity Service Status

created, info_requested

Pending

exception

Suspended

queued, pending, ys_qa_review, processing, pending_approval

InProgress

consider

NeedsReview

clear, proceed, pre_adverse

Completed

dispute

Disputed

final_adverse

NotEligible

canceled

Cancelled

expired

Expired

Did this answer your question?