Executive Summary: A court records BSA AML investigation gives a lender a documented way to add litigation and judgment history to its anti-money-laundering diligence and adverse-information review. Federal credit-reporting rules limit how far back civil suits and judgments can travel into a decision, and they require furnishers and users of that data to maintain reasonable accuracy and integrity controls.[1][2] This guide turns court-record review into a usable part of BSA/AML diligence: what litigation data adds, where Cobalt's court coverage actually fits, and how to keep the workflow honest about its limits.
Why does court records BSA AML investigation matter for lenders?
What does litigation data add to an AML file?
A money-laundering and adverse-information review asks whether a business or its principals carry red flags that automated identity and sanctions checks miss. Judgments, fraud suits, and repeated litigation are part of that picture. A judgment in particular is a court money order that, once filed, can attach as a security interest to the debtor's property.[6] That makes it both a repayment-risk signal and an adverse-information signal, the same lien-priority concern that drives the workflow in our pre-funding UCC lien search guide.
Court records do not replace sanctions screening or transaction monitoring. They sit beside them, adding a documented litigation layer to the negative-news and adverse-media portion of a diligence file.
Why is self-reported history not enough?
A borrower has little incentive to volunteer a fraud judgment or a pattern of contract suits. Court records give the lender an independent control that does not depend on what the applicant chooses to disclose. The public docket is the same whether or not the business mentions it on an application.
The practical question is not whether the applicant says it has a clean legal history. The question is whether the public record supports that claim before money moves.
What court data supports an AML and adverse-information review?
Which fields carry the most signal?
Cobalt's Court Records API returns judgment details such as type and status, case information including case number and court division, filing dates, the plaintiff and defendant names, and judgment amounts where the record makes them available. Amounts are not always present, so the workflow should treat a missing amount as unknown, not as zero.
How does this connect to negative-news review?
Adverse-media and negative-news screening often surface a name without a verifiable source. A matched court record turns a rumor into a documented event with a case number and a filing date, the same case-file elements that define a court record in the first place.[4] That is the difference between an analyst note and an evidence-backed finding a compliance reviewer can defend.
| Court signal | AML / adverse-information use | What it does not prove |
|---|---|---|
| Fraud or misrepresentation judgment | Strong adverse-information flag for enhanced review | Guilt in any pending or unrelated matter |
| Repeated contract or collection suits | Pattern signal for financial distress | Current outstanding balance |
| Recent judgment with a named principal | Links a person to a documented court event | That the principal controls the applicant entity |
How does Cobalt return court data in this workflow?
What does the API call look like?
The Court Records API is asynchronous. Every request requires a `businessName`, a `jurisdiction`, and a `callbackUrl`, and results are posted to the callback endpoint when the search completes, typically within 30 to 120 seconds. There is no synchronous result body.
curl --location 'https://apigateway.cobaltintelligence.com/courtCases?businessName=Acme%20Corp&jurisdiction=newYork&callbackUrl=https%3A%2F%2Fyour-endpoint.example.com%2Fcobalt-callback' \
--header 'x-api-key: YOUR_API_KEY' \
--header 'Accept: application/json'What should compliance store?
Store the raw callback payload, the parsed findings, and the reviewer's disposition. The raw record proves what was searched and when. The parsed fields drive routing. The disposition note tells a future examiner why the file was cleared, escalated, or held. That chain is what an AML program needs to show that a control actually ran.
How should a lender turn court findings into AML actions?
What routing rules make the signal useful?
Keep the first policy pass simple. No matched records in supported coverage means the file continues through standard diligence. A single old civil matter means continue with a note. A fraud or misrepresentation judgment, or a dense pattern of recent suits, should trigger enhanced review of the business and its principals before the relationship opens.
What should the exception queue show?
The exception queue should display the case number, the parties, the filing date, the judgment type, and the exact rule that fired. A reviewer should not have to reopen a court website to understand why the file paused. Clear queue records are also what make a control auditable later.
How does this fit broader BSA/AML obligations?
Where does court review sit next to sanctions screening?
Court review is one input, not the whole program. Sanctions screening against the Treasury list is a separate, mandatory control. For the relationship between court-record diligence and sanctions obligations, see BSA/AML for Alternative Lenders: OFAC's Role. Court data adds litigation context; OFAC screening answers a different and non-negotiable question.
What FCRA limits apply?
If court-derived public records inform a credit decision, federal rules govern their use. The FCRA bars reporting most civil suits and judgments that predate a report by more than seven years or the governing statute-of-limitations period, whichever is longer.[1] Users and furnishers must also keep reasonable written policies on the accuracy and integrity of that information.[3] Counsel should set the final use policy.
How should the workflow handle coverage limits?
What does Cobalt court coverage include?
Cobalt's Court Records API covers New York State and Miami-Dade County, Florida only, where Florida court records are accessed through the county clerks of court.[7] Both are concentrated centers for alternative and small-business lending, which makes the coverage limited but targeted. It is not nationwide and is not a substitute for comprehensive litigation screening. State courts handle the vast majority of cases across thousands of separate venues, which is exactly why no single feed covers everything.[5]
Why must fallback logic be explicit?
For any business outside New York or Miami-Dade, the workflow must route to a fallback litigation search or manual review, not silently clear the file. Treating missing coverage as a clean result creates a hidden gap in the AML program. The honest workflow states one of three outcomes: clean supported search, adverse supported search, or unsupported jurisdiction requiring fallback.
How can a lender add court data to its AML review?
The fastest way to evaluate fit is to test the Court Records API against businesses you already underwrite in New York or Miami-Dade and compare the findings to your current adverse-information process. You can walk through the data and the supported coverage with the team on a Cobalt Intelligence demo.
.jpg){kind=small}
.png)