Skip to content
Start free
All industries

Lending · Application evidence

An application is more
than its form fields.

Bring borrower records, business relationships and supporting documents into the applications your lending teams use to review a case.

Discuss your lending workflow Build a sample application

Give every piece of evidence a source.

Resolve a document passage or a declared business relationship back to the application it supports. The reviewer can then inspect the record behind the result.

From application to review packetIllustrative business-loan application
Application fileAPP-17
01 / Application fields
Applicant
CU-92
Business
BIZ-18
Purpose
Working capital
Source
applications / APP-17
02 / Declared relationship
CU-92Applicant
Director of
BIZ-18Business

Source: declaration REL-06. The recorded link is available for inspection.

03 / Document passage
Business statementDOC-31 · version 2 · passage 4
“Prepared for BIZ-18. Statement period: April–June.”

Illustrative extracted text. Resolve DOC-31 to the original source before using the passage.

Application assembles

A packet
for review.

  1. 01Field values and their source IDs
  2. 02Declared applicant relationships
  3. 03Document passages and versions
Reviewer interprets
the evidence.

Eligibility rules and the lending decision belong to your application and review process.

Illustrative records and document text. The database retrieves fields, relationships and passages; it does not verify the applicant’s declarations.

5 use cases / Lending

The right modalities for your workflow.

Start with the combination that fits your question. These are recommended starting points; the best fit depends on your data and query patterns.

Lending: use cases, recommended query modalities and why each combination fits.
Use caseRecommended modalitiesWhy this combination fits
Application pipeline tracking

Track applications, outstanding tasks and review status.
SQL

SQL joins application and task records, filters by stage and groups turnaround times for operational reporting.
Borrower and guarantor context

Explore the people, businesses and assets connected to an application.
SQL Graph

SQL retrieves application fields. Graph follows borrower, guarantor and asset relationships for the reviewer's assessment.
Underwriting evidence workspace

Connect application records to related entities and source documents.
SQL Graph FTS

SQL organises application data, Graph links the supporting entities, and FTS finds evidence within the associated documents.
Document and clause lookup

Find application terms, conditions and verification references.
SQL FTS

SQL provides application IDs and document versions. FTS locates matching clauses and reference terms for the reviewer.
Lending policy assistant

Retrieve source passages for an internal policy question.
SQL FTS Vector

FTS matches lending terminology and Vector finds semantically related guidance. SQL supplies product context and source metadata.

Combine query results in your application using shared record IDs. Keep text indexes and embeddings updated as the source data changes.

Different evidence. A query for each.

Resolve model results by their source IDs rather than treating a search match as a verified fact.

SQL

Structured facts

Filter application fields, join borrower records and inspect document metadata.

SQL reference
Graph

Declared relationships

Follow recorded links between applicants, businesses and related application records.

Graph quickstart
Full-text

Specific wording

Find exact terms and phrases in the text your ingestion pipeline indexes.

Full-text reference
Vector

Related passages

Use supplied embeddings to retrieve text by similarity, then read the source.

Vector schema

Start with one complete review packet.

Use sample records to test the path from ingestion to reviewer hand-off.

  1. 01

    Model the references.

    Give applications, borrowers, businesses and documents stable IDs. Record the source and version of extracted fields.

    Schema reference
  2. 02

    Keep indexing explicit.

    Write passages and embeddings through their separate endpoints. Have the ingestion pipeline track updated documents and stale results.

    Text indexing
  3. 03

    Evaluate the review path.

    Test a missing document, an updated version and a restricted identity. Keep credentials server-side and retain the reviewer's source references.

    Authentication reference

Your application owns eligibility rules and lending decisions. OriginChainDB stores and queries the records that support that process.

Review the design