Executive Summary: A judgment records a court outcome; a current payoff balance requires evidence about the obligation now. New York Courts describes entry of judgment, while the New York County Clerk separately maintains satisfaction records.[1][2] Preserve the court amount as a dated source fact and reconcile later evidence before treating it as current borrower exposure.
What does the amount in a court record actually describe?
Identify the document and procedural event before interpreting the number. An amount requested in a complaint, an entered judgment amount and a later statement of an obligation are not interchangeable labels.
New York Courts explains that a decision must be entered as a judgment through the clerk's signing and filing process.[3] A search summary or case caption alone does not establish every part of that process or the current amount owed.
What should the credit reviewer record first?
Record the source document, date, jurisdiction, case reference, parties and the precise meaning of the amount. Use a label such as “Amount stated in entered judgment” only when the retained source supports it.
Do not populate a generic “Current debt” field merely because a court-related number is available. If the record does not establish a current balance, keep that fact unknown and open the evidence task needed for the lending decision.
Is using the full amount a conservative assumption?
A lender may choose a temporary assumption under its policy, but the file should identify it as an assumption. “Assumed exposure pending reconciliation” is different from “Verified current payoff balance.”
Keep the source amount and the policy assumption in separate fields. That allows the reviewer to change the assumption when new evidence arrives without rewriting the underlying judgment record.
Which later records can change the interpretation?
Look for evidence relevant to payment, satisfaction, amendments, other court action or the current obligation. The exact records needed depend on the case and the lending question. Do not infer a complete payment history from a single docket entry.
The New York County Clerk describes filing a satisfaction of judgment and obtaining proof that a judgment has been satisfied.[4] That separate process illustrates why an earlier judgment amount should remain tied to its original date and document.
Does no visible satisfaction mean nothing was paid?
Do not make that inference from an incomplete record search. Identify what sources were checked and what they establish. If the current balance matters to underwriting, request the supporting evidence appropriate to that question rather than treating missing information as a verified amount.
Equally, a borrower statement that an obligation was paid should retain its provenance until the required corroboration is obtained. Do not label borrower-supplied information as a court-record fact.
Should the analyst calculate the payoff independently?
Avoid inventing a payoff from a judgment amount and a generic interest assumption. The relevant legal terms, payments, costs and later events may require specialist interpretation. Route that question to the responsible legal or credit owner and obtain an appropriately supported current figure.
This article concerns evidence handling in a business-lending file. It does not supply a legal payoff formula, collection deadline or lien-priority determination.
What can Cobalt's court response contribute?
Cobalt documents court-search routes for New York and Miami-Dade, with a required business name, jurisdiction and callback URL.[5] The response can help identify source records for review within those documented jurisdictions.
It does not document a dedicated current payoff-balance service. Do not promise that a court API result automatically supplies the borrower's current obligation or a legally complete exposure calculation.
Which New York details are available?
The current New York example includes a more detailed first result with source and document references, while later results contain top-level information.[6] Obtain the relevant source document before interpreting an amount that is not established by the returned fields.
The amount discussed in this article comes from the appropriate court or obligation evidence. It is not an invented Cobalt currentBalance field.
Does the Miami-Dade response have the same shape?
The documented Miami-Dade example uses case-information, status, filing-date and case-number fields.[7] Confirm the actual jurisdiction-specific response and available source route rather than assuming the New York document fields exist everywhere.
Our civil court docket guide provides broader review context. The additional control here is keeping the court amount separate from any current-balance conclusion.
How should the lending file represent the unresolved balance?
Create separate fields for the dated source fact, later supporting evidence and current underwriting disposition. A blank current balance is preferable to a fabricated zero or an unqualified copy of the earlier amount.
A practical checklist includes:
• Available API evidence. The documented court response supplies case and document information; it does not define a current-payoff-balance field.[8]
• Correct party. Establish that the source record concerns the intended applicant and identify its role in the case.
• Procedural source. Identify the document or event supporting the amount, rather than relying only on a case label.
• Recorded amount. Preserve the value, currency, source date and document reference exactly as supported.
• Later evidence. Attach relevant satisfaction, payment or other records with their own dates and provenance.
• Current-balance status. Mark verified, assumed under policy or unresolved, with a clear supporting basis.
• Decision owner. Identify who may accept the evidence and what lending action it supports.
New York Courts' records guidance provides a route to search Supreme Court cases and e-filed documents as a guest through NYSCEF.[9] Use the appropriate current source process for the case rather than treating an API summary as the entire record.
What should the analyst-facing summary say?
Use wording that preserves uncertainty. For example: “Entered judgment amount recorded; current obligation not yet reconciled.” If the team uses a temporary exposure assumption, show that label and the applicable policy next to it.
Avoid “Paid” or “Outstanding” when the available evidence only establishes an earlier entry. The summary should tell the next reviewer what is known and which specific question remains open.
What could an implementation check look like?
The integration should not turn an earlier amount into a current one by default. Require an explicit evidence basis before populating the verified-current-balance field.
The following is an illustrative customer-side record. It is not a Cobalt payload and contains no real borrower facts.
{
"case_reference": "synthetic-case-reference",
"source_amount_type": "entered_judgment",
"source_amount_reference": "retained-court-document",
"current_balance": null,
"current_balance_status": "unresolved",
"next_action": "obtain_current_obligation_evidence",
"decision_scope": "credit_review_pending"
}What should null mean here?
It means a current balance has not been established in this record. Do not export it as zero or omit the unresolved label from a credit memo. Downstream calculations should handle unknown exposure explicitly under the lender's policy.
If a reviewer uses an assumption, store it separately with the reason and authority. A policy estimate should not be presented as if a court or creditor supplied that number.
How should a later verified figure be added?
Attach the source, effective date, relevant terms and reviewer disposition. Preserve the earlier court amount as history. Record what evidence supports the current figure and any limitations on using it for the particular decision.
If sources conflict, retain the conflict and identify the responsible owner for resolving it. Do not average numbers from different documents merely to produce a single answer.
What does a worked review look like?
Consider a hypothetical application where an analyst finds an entered judgment stating an amount. The borrower says payments were made afterward and provides supporting material. This scenario is illustrative and does not describe a Cobalt customer or an actual court case.
The reviewer first confirms the applicant's association with the case and the source of the entered amount. Next, the team identifies which later records are required to establish the current obligation for underwriting. The borrower-supplied material remains labeled as such while the required verification proceeds.
What if a satisfaction is found?
Retain the exact source record and have the responsible reviewer assess what it establishes for the case and decision. The County Clerk's guidance describes checking its records for satisfaction and obtaining certified proof when needed.[10]
Do not erase the judgment history. Add the later evidence and the resulting disposition so the file explains both the earlier event and the current assessment.
What if the evidence remains incomplete?
Keep the current balance unresolved. A policy owner may decide how the lender treats that uncertainty for the current stage, but the source record should not be altered to make the uncertainty disappear.
The pre-funding business-verification framework provides context for keeping an outstanding evidence condition separate from other completed checks. A court-record search can be complete while the balance question remains open.
Keep the court's dated fact, the borrower's later evidence and the lender's current assumption distinguishable.
How should the reviewer handle several related records?
Do not add every visible amount automatically. Determine whether the entries describe separate obligations, later events in the same case, or records that require more context. Preserve the case and document relationships used in that determination.
Middesk's legal-record documentation describes judgment-related docket entries with dates, text and monetary amounts.[11] That illustrates another provider's record model; it does not make every amount in such a model a separate current debt.
What should a reconciliation note contain?
Identify which records were compared, what each amount represents, which values remain historical and which figure, if any, is accepted for the current decision. Cite the supporting source for the accepted figure and name the reviewer.
If the decision depends on legal interpretation, state the question and route it to the appropriate specialist. A data mapping should not silently decide that two similar-looking amounts represent the same obligation or that a later docket label supersedes an earlier one.
What if a case status says closed?
Use that status within its source meaning. It does not independently establish the current payment balance. Obtain the evidence relevant to the obligation rather than treating a broad case status as a payoff statement.
Keep the procedural and financial questions separate in the task list so one completed check cannot inadvertently close the other.
How should the team test this control?
Use synthetic fixtures for an entered amount without later evidence, a borrower payment claim, a source satisfaction record, conflicting figures, several related entries and a case associated with a similarly named business.
Which failures should the test catch?
It should fail if an unknown balance becomes zero, if a historical amount is labeled current without support, if a complaint amount becomes an entered judgment, or if a closed case is automatically marked paid.
Also test the source-delivery boundary. Cobalt's court endpoint documents an initial callback acknowledgment rather than immediate final case results.[12] The initial response must not create either a completed court review or an empty clean-result record.
What should operations review after rollout?
Inspect the reasons current balances remain unresolved and how cases eventually close. Distinguish identity problems, missing documents, source conflicts and pending specialist decisions. These are different work queues, not one generic “court issue.”
Ask another reviewer to reconstruct a sample decision from its retained evidence. The accepted figure should be traceable without relying on undocumented memory or an unlabeled spreadsheet calculation.
What should you confirm in a Cobalt evaluation?
Bring the court-evidence question your credit team needs answered. Ask to inspect the actual jurisdiction-specific fields, document references and callback flow, then identify the separate evidence required for a current obligation assessment.
Cobalt's documented court coverage is limited to the named New York and Miami-Dade routes.[13] Confirm suitability for the intended cases and do not generalize the result to nationwide or federal coverage.
Schedule a Cobalt demo with a permitted example of the review package you need. The objective is a traceable court-record workflow that preserves the distinction between an earlier judgment amount and the current balance the lending decision may require.
.jpg){kind=small}
.png)