Executive Summary: Court records equipment finance teams pull during pre-funding diligence answer a question UCC searches cannot: is this lessee already losing in court, and could a judgment strip the collateral you plan to recover. A money judgment, once filed, can attach to a debtor's property as a lien, which changes recovery math the moment a deal goes bad.[1] Most of that litigation sits in state courts, not federal ones, since the large majority of cases are handled at the state level.[2] This guide turns court records equipment finance review into a repeatable pre-funding step that sits alongside the UCC lien check.
Why do court records matter for equipment finance underwriting?
What does litigation exposure say about a lessee?
A lessee fighting multiple breach-of-contract or collection suits is signaling cash pressure and counterparty disputes before any of it reaches a credit bureau. Court records show the underwriter whether the business is a defendant in active matters, whether judgments have already been entered, and what dollar amounts are attached where the court system publishes them. A court file is a docket sheet plus the documents filed in the case, and what reaches an underwriter depends on what each court makes electronically accessible.[5]
How does a judgment threaten the collateral?
Equipment finance recovery depends on a clean path to the asset. When a judgment creditor records its judgment, that interest can attach to the debtor's property and compete with your claim. A judgment lien is a court-derived security interest, so litigation that looks like a paperwork nuisance can sit ahead of your recovery position if it ripens into a recorded lien.[1]
What should an equipment lender search before funding?
What signals belong in the file?
The useful signals are not the existence of a single old case. They are the pattern: several active matters, a defendant role in collection suits, recent filing dates, and judgment amounts that rival the deal size. Each of those moves a file from automated approval toward manual review. A lessee with three open collection suits and a six-figure judgment entered last quarter is a very different risk than a business with one settled dispute from years ago, even when both show the same clean bank statements at intake. The court record is what separates the two.
How should this run alongside the UCC check?
Court records and UCC filings answer different halves of the same recovery question. The UCC search shows who has already noticed a secured claim on the assets. The court search shows who is suing for money that could become a new lien. Run both at the same pre-funding hold point, before final approval, so either signal can still change the decision. See the pre-funding UCC lien search underwriter workflow for the lien half of this pairing.
How does Cobalt return court records in the workflow?
What does the API call look like?
Cobalt's Court Records API is a callback-only endpoint. You send the business name, the jurisdiction, and a callback URL, and the result is POSTed back when the court search completes, typically within 30 to 120 seconds.
curl --location 'https://apigateway.cobaltintelligence.com/courtCases?businessName=Acme%20Equipment%20LLC&jurisdiction=newYork&callbackUrl=https%3A%2F%2Fyour-app.com%2Fcobalt-callback' \
--header 'x-api-key: YOUR_API_KEY' \
--header 'Accept: application/json'What does the response include?
The documented return fields are judgment details such as type and status, case information such as case number and court division, filing dates, parties involved including plaintiff and defendant names, and judgment amounts where the court makes them available. Amounts are not always present, so the workflow should treat a missing amount as unknown rather than as zero.
What is the honest coverage scope?
Which jurisdictions does the API cover?
Coverage is New York State and Miami-Dade County, Florida only. This is deliberate and limited. New York is a major center for alternative lending and equipment finance, and Miami-Dade is a hub for South Florida small-business lending, so the two venues are disproportionately relevant to this borrower base. The API is not a nationwide litigation screen and does not query PACER or federal courts.[3]
What happens for everywhere else?
For a lessee outside those two venues, the API returns no court coverage, and the workflow must route the file to a fallback path rather than treat the gap as a clean result. A Florida deal outside Miami-Dade, for instance, runs through the broader Florida state courts system, where records are held by county clerks of court.[6]
| Lessee venue | Cobalt court API | Workflow action |
|---|---|---|
| New York State | Supported (`jurisdiction=newYork`) | Parse parties, dates, judgment data |
| Miami-Dade County, FL | Supported (`jurisdiction=miamiDade`) | Parse parties, dates, judgment data |
| Any other state or county | Not covered | Route to state-portal or vendor fallback |
The rule that protects an equipment portfolio is simple: an unsupported jurisdiction is never a clean jurisdiction. Missing coverage routes to a fallback search, not to automatic approval.
How should court signals feed underwriting decisions?
What routing rules turn cases into actions?
Cobalt is a data source, not a decisioning engine, so the lender owns the thresholds. A practical first pass: no covered cases continues the file, one resolved old matter continues with a note, multiple active defendant matters move to manual review, and a recent judgment near the deal size triggers a funding hold until the lessee explains it.
What should the exception queue show?
The queue should display case numbers, party names, filing dates, judgment status, and the rule that fired. An underwriter should not have to reopen a court portal to understand why the file paused.
How should teams handle the seven-year and compliance limits?
Does the FCRA limit how old records can be used?
When public-record data informs a credit decision through a consumer reporting agency, the FCRA bars reporting most civil judgments that predate the report by more than seven years or the governing statute of limitations, whichever is longer.[4] Counsel should set how stale judgments are treated in policy. Court records review also pairs with sanctions and AML diligence covered in BSA/AML for alternative lenders and OFAC's role.
What does the court search not prove?
A court search does not prove current solvency, does not capture every venue, and may miss older or non-electronic case types depending on what the court system publishes. It is one independent control, not the whole picture.
How can an equipment lender get started?
The fastest way to test the fit is to run a few known lessees in New York or Miami-Dade against the Court Records API and compare the structured output to what your team finds by hand. You can book a Cobalt demo to walk through the callback flow, the return fields, and how to wire the fallback path for venues outside the two covered jurisdictions.
.jpg){kind=small}
.png)