OffenderSearch
FCRA 613 compliance · for consumer reporting agencies

FCRA 613 compliance: verify every database hit at its source court

Section 613 asks a CRA that reports public records for employment to keep them complete and up to date. Our FCRA order re-checks every criminal hit live with the court that holds it and withholds anything the court no longer shows. The data API does the same for a hit from any database.

Request FCRA accessRead the docs$4.95 an order · no court fees

Updated November 22, 2026 · API changelog

A criminal search on an FCRA order
// GET /v1/fcra/orders/{id}: the criminal search (excerpt, values illustrative)
{
  "type": "criminal",
  "status": "complete",
  "result": "records_found",
  "recordCount": 1,
  "withheld": {
    "not_current_at_source": 1,      // the court no longer shows it
    "obsolete_non_conviction": 1     // the seven-year rule removed it
  },
  "incompleteReasons": []
}
// the furnished record carries the moment its court confirmed it:
// "verifiedAt": "2026-11-21T15:04:12Z"
Not legal advice. The statute is quoted below; your program’s procedures are your counsel’s call.

What FCRA section 613 says (15 U.S.C. § 1681k)

The section is short. It applies to a CRA that furnishes a consumer report for employment and reports public-record items likely to have an adverse effect on the consumer’s ability to get the job.

15 U.S.C. § 1681k(a), public record information for employment purposesA consumer reporting agency which furnishes a consumer report for employment purposes and which for that purpose compiles and reports items of information on consumers which are matters of public record and are likely to have an adverse effect upon a consumer’s ability to obtain employment shall—(1) at the time such public record information is reported to the user of such consumer report, notify the consumer of the fact that public record information is being reported by the consumer reporting agency, together with the name and address of the person to whom such information is being reported; or(2) maintain strict procedures designed to insure that whenever public record information which is likely to have an adverse effect on a consumer’s ability to obtain employment is reported it is complete and up to date. For purposes of this paragraph, items of public record relating to arrests, indictments, convictions, suits, tax liens, and outstanding judgments shall be considered up to date if the current public record status of the item at the time of the report is reported.15 U.S.C. § 1681k at Cornell LII ›

Two words carry the weight for a criminal record: complete (every charge and its outcome, not a fragment) and up to date (the current status at the court, at the time of the report). A dismissal, a reduction, a sealing order or an expungement changes the current status; a database copy made before it does not.

Section 613 sits next to the general accuracy duty in § 1681e(b), the time limits in § 1681c and the dispute duty in § 1681i. How our order handles each is on the FCRA-compliant background check data page.

This page describes the statute and common industry practice. It is not legal advice.

613 notice or 613 strict procedures: the two options

The statute offers a choice. What each one asks of the CRA, and what it leaves the consumer with.

§ 1681k(a)(1): the 613 notice§ 1681k(a)(2): strict procedures
What the CRA doesTells the consumer, when the record is reported, that it is being reported and to whomKeeps procedures designed to make sure the record is complete and up to date when reported
WhenAt the time the information goes to the employerBefore the information goes to the employer
What it relies onThe consumer spotting an error and disputing itThe CRA catching a stale or partial record first
Common practice for criminal hitsA letter or email per report with adverse public recordsConfirm each database hit at the court that holds it before it is reported
In our FCRA orderYour notice process; the consumer portal shows the consumer what was furnishedEvery criminal hit re-checked live; anything not confirmed is withheld

The two are not exclusive, and some CRAs do both. The consumer-facing side of an order, what the consumer sees and how they dispute it, is on the FCRA consumer portal and FCRA dispute API pages.

FCRA 613 strict procedures for database hits: what CRAs commonly do

A description of industry practice, not a statement of what the law requires.

A multi-jurisdictional criminal database is a copy, and a copy has an age. The common practice is to treat a database result as a pointer: a possible record in a named county, which is then confirmed at that county’s court before anything adverse is reported. Where the court cannot be reached, the hit is held rather than reported.

For most of the industry’s history that confirmation was a courthouse researcher, sent per hit and per county, with turnaround commonly quoted in business days and a court access fee on top. The court runner alternative page compares that model with a live check by API.

  • Find candidates. A database or county search by name and full date of birth.
  • Match the identity. Report only on a full date-of-birth match; a name alone is not an identification (date of birth).
  • Confirm at the source. Ask the court that holds the record for its current status.
  • Apply the time rules. Seven-year and state limits, charge by charge, on the current copy.
  • Keep the evidence. Which court, which page, when it was checked.
  • Hold what cannot be confirmed. An unconfirmed hit is not reported.

How an FCRA order handles section 613: confirm, withhold or mark incomplete

Every criminal hit in an order is re-checked live with its source before the report is built. There are three outcomes, and only one of them reaches the report.

Live re-check outcomeWhat the order doesCode
The court confirms the record (same case, still a full date-of-birth match)The time rules run again on the fresh copy, then the record is furnishedverifiedAt
The court answered without the recordWithheld; its content is never returnednot_current_at_source
The court shows it sealed, expunged or not public (liveScope: "matches")Withheldsealed_or_expunged
The court did not answer, or the check ran out of timeWithheld; the search is incomplete, never clearverification_unavailable

A record is never furnished from a stored copy: it is always confirmed live first. The withheld counts sit on the search by reason code, beside the other controls (obsolete_non_conviction, time_limited, insufficient_identifiers, disputed_suppressed), so your adjudicators see how many items were held back and why without seeing their content. The reason codes are in FCRA controls.

Every order also carries its search plan: the counties around each address, the states, the sources behind each, and the counties with no county-level source. A policy can set requireCountyCoverage so that a county gap makes the search incomplete instead of a disclosed gap (search scope).

liveScope sets where the order checks live. The default, relevant, checks every live-capable source in the subject’s address-history states and the use location, plus the source of every exact date-of-birth candidate. matches confirms each possible record with the agency that keeps it and holds it until it does, for up to five business days.

$4.95 an order, sex offender and criminal court search included, with no court fees or extra charges. The criminal search inside the order, with its seven-year and state rules, is on the FCRA criminal background check API page; the endpoints are on the FCRA Orders API page.

Database hit verification at the source court, by API

Hold a hit from any database, yours or a vendor’s? Send the subject with a live block naming the jurisdiction. The answer says whether that court still shows it.

POST /v1/criminal/searchsandbox scenario “Felony conviction, verified live” · query {"firstName":"Felony","lastName":"Record","dob":"1975-06-15","live.jurisdictions":"US-DOC","live.evidence":"pdf"}
200 OK · the sandbox's answer, captured from its code
{
  "status": "complete",
  "counts": {
    "records": 1,
    "recordsReturned": 1,
    "sourcesQueried": 1,
    "sourcesComplete": 1,
    "sourcesIncomplete": 0,
    "candidatesCapped": false,
    "exclusionsIncluded": false,
    "sourcesOnFile": 1934,
    "sourcesPending": 197
  },
  "warnings": [],
  "page": 1,
  "perPage": 50,
  "totalPages": 1,
  "sourceStatus": [
    {
      "code": "US-DOC",
      "source": "US-DOC",
      "ok": true,
      "incomplete": false,
      "incompleteReason": null,
Read sourceStatus first: who was asked and who answered. A system that answered with no matching record is a defensible “not held there”; a stored record the live check did not return is flagged for review.Run it yourself with a test key ›
Question your reviewer asksField that answers it
Did the court answer during this request?sourceStatus[].ok, sourceStatus[].live
Was this record confirmed live?sources[].live, sources[].lastCheckedAt
Where is the court’s own page for it?sources[].recordUrl
Did the court confirm the date of birth?dobVerification
Is the court still listing it?lifecycle.droppedOut
What did the live checks cost?usage.liveChecks, usage.liveChargeUsd

$0.15 a call, $0.02 per system that answered, never more than $2.00 of live checks on one search. The data API is not a consumer report; the full mechanics are on the criminal record verification API page, and county-by-county searching is on the county criminal search API page.

FCRA 613 compliance evidence for the file

Strict procedures are easier to show than to describe. These are the artefacts each step leaves behind.

ArtefactWhat it showsWhere
Check time on each recordThe court and the moment its status was confirmedverifiedAt
Withheld counts by reasonHow many hits were held back, and whywithheld
Search planWhich counties and states were searched, and the county gapssearch scope
Signed report receiptThe report has not changed since it was issued; anyone can check it/verify
Verification PDF (data API)The search criteria, each record and a source citation, $0.02 a documentverification reports
Dispute trailReinvestigation, outcome and any revised reportdisputes

The full artefact list, with what each signs, is in FCRA evidence, signed PDF and receipts.

FCRA 613 and courts with no online records

Live coverage is jurisdiction by jurisdiction. Where a court cannot be asked, the product says so instead of reporting an unconfirmed hit.

  • A hit held by a court with no online index cannot be confirmed by the API. In an order it is withheld as verification_unavailable and the search is incomplete; on the data API the county is listed in countiesWithoutSource. If you intend to report it, a courthouse researcher still has to confirm it.
  • A sealed or unpublished case is not returned. A live check asks a court about what it lists.
  • No promise of a county the court has not put online. The current list is in the criminal coverage reference, by state on the criminal records by state pages.
  • No legal advice. Whether your procedures meet § 1681k is your counsel’s judgment; this page describes the product and common practice.

FCRA 613 compliance checklist for a criminal search program

Questions compliance teams commonly ask of their own pipeline and their vendors. Not legal advice.

Which option are we using?

The 613 notice, strict procedures, or both, written down per product and per client.

FCRA Partner Access ›

Is every hit confirmed at its source?

Before it is reported, with the court’s current status and the time of the check kept on file.

Criminal record verification API ›

What happens to a hit we cannot confirm?

Held, never reported unconfirmed; routed to a researcher where the court is offline.

Court runner alternative ›

Is the identity match strong enough?

Full date of birth, not a name or a birth year alone.

criminal matching ›

Are the time rules applied per charge?

Seven-year and state limits measured on the current copy.

FCRA criminal background check API ›

Can we show it later?

Search plan, withheld counts, check times and a signed receipt per report.

FCRA evidence ›

FCRA 613 compliance questions

The statute, the 613 notice and how the order behaves. Not legal advice.

Does section 613 require us to verify every database hit at the court?

The statute gives a CRA two options for adverse public-record information reported for employment: notify the consumer at the time of reporting, or keep strict procedures designed to make sure the information is complete and up to date. It does not name a verification step. Many screening companies treat a database hit as a lead and confirm it at the source court before reporting it, because a database copy can be older than the court’s current record. Which approach fits your program is a question for your counsel. This page is not legal advice.

What counts as “up to date” for a criminal record under § 1681k?

The statute says items of public record relating to arrests, indictments, convictions, suits, tax liens and outstanding judgments are considered up to date if the current public record status of the item at the time of the report is reported. That is why the check time matters: a live check records the court’s status at the moment of the request.

What is a 613 notice?

It is the first option in § 1681k(a)(1): at the time adverse public-record information is reported for employment, the CRA notifies the consumer that it is being reported, with the name and address of the person receiving it. Some CRAs send the notice as well as running strict procedures.

What happens in an FCRA order when the court no longer shows a record?

The record is withheld with the reason not_current_at_source and counted in withheld; its content is never returned. A record whose court did not answer is withheld as verification_unavailable and the search is marked incomplete, never clear. Only a record the court confirmed is furnished, with verifiedAt.

How long does the re-check take?

Most live checks run as a background job inside the order. 90% of criminal checks done in under 30 minutes. With liveScope: "matches", a possible record is held until the agency that keeps it confirms it, for up to five business days, and is withheld as verification_unavailable if it does not.

Can we use this to verify hits from another provider’s database?

Yes, on the data API. Send the subject with a live block naming the jurisdiction that holds the hit; the answer says whether that court still shows it, with the court’s link and the check time. $0.15 a call plus $0.02 per system that answered.

What about counties whose court has no online records?

A live check can only ask a court that publishes online. A hit held by such a court cannot be confirmed by the API: in an order it is withheld as verification_unavailable rather than reported unconfirmed. On the data API the county is listed in countiesWithoutSource. Those hits still need a courthouse researcher if you intend to report them.

Learn the API by example

Runnable guides that use this endpoint as the worked example.

FCRA adverse action with an API ›Adverse items, the pre-adverse notice, the waiting period and the post-adverse notice, endpoint by endpoint.
Background check API for HR and ATS ›The FCRA order from the offer stage to the result on the candidate record.
Criminal records by name and date of birth ›Why the date of birth decides whether a hit is an identification or a lead.
No-match and multiple-match results ›The three shapes of "nothing", possibles, and a decision table per matchState.
Background check API response explained ›Every field of a real sandbox response, group by group.
Court records API tutorial ›Cases, charges and dispositions, and how to read a case that holds both a conviction and a dismissal.

All guides: Learn APIs by example · reference: developer docs · packages: SDKs and CLI.

Related FCRA and verification API pages

The rest of the developer surface, one anchor per page.

Background check API ›Criminal records and 58 US sex offender registries on one key, per call.
Criminal records API ›Court cases, jail bookings, prison custody and warrants as JSON.
Sex offender API ›One POST across 58 US registries, scored and cited.
Free background check API ›25 free calls on real data, no card, plus the free sandbox.
Employment screening API ›The public-records stage of a hiring pipeline, and the FCRA path for the decision.
Tenant screening API ›The registry and criminal layer behind a rental application.
Inmate search API ›State prison and county jail custody records.
Background check API pricing ›Costs from 100 to 100,000 searches a month.
Public API for testing ›A free sandbox with documented test people in the production shape.
SDKs: Python, Node, CLI ›Client status and the method surface, one per endpoint.
Postman collection ›Every endpoint with sandbox bodies pre-filled.
MCP server ›Registry and criminal lookups as tools for Claude, Cursor and agents.

Run an FCRA 613 source-court check in the sandbox

Every test account is an enabled FCRA partner. Place an order with an os_test_ key and read withheld and verifiedAt. Nothing is billed.