> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# What is Lender?

> Meet Lender — Lerian's credit journey engine for consumer credit (CDC), business lending (PJ), and cards.

export const GPortfolio = ({children}) => <Tooltip headline="Portfolio" tip="A grouping of accounts belonging to the same customer, business unit, or purpose — tying together checking, savings, and investment accounts for a unified view." cta="See glossary" href="/en/glossary">
    {children}
  </Tooltip>;

export const GAuditTrail = ({children}) => <Tooltip headline="Audit trail" tip="A chronological, immutable record of every action and transaction in the system — essential for regulatory compliance and dispute resolution." cta="See glossary" href="/en/glossary">
    {children}
  </Tooltip>;

export const GDoubleEntry = ({children}) => <Tooltip headline="Double-entry accounting" tip="Every financial movement is recorded as at least two operations: a debit from one account and a credit to another, ensuring the system always balances." cta="See glossary" href="/en/glossary">
    {children}
  </Tooltip>;

export const GLedger = ({children}) => <Tooltip headline="Ledger" tip="The core financial book that records all transactions, balances, and operations for an organization — the single source of truth for a business unit's finances." cta="See glossary" href="/en/glossary">
    {children}
  </Tooltip>;

**Lender** is Lerian's credit journey engine. It gives financial institutions one product to run the full lifecycle of a credit operation — from defining the loan product, through origination and disbursement, to servicing, repayment, and audit-ready history. Lender spans three credit journeys: **consumer credit (CDC)**, **business lending (PJ)**, and **cards**.

Lender is available to licensed customers; its repository is maintained internally.

## What a credit journey engine is

***

A credit operation is not a single event — it is a journey that spans months or years and touches many teams. A credit journey engine manages that journey end to end:

* **Product definition**: Loan products with versioned terms, charges, and rate configurations, so every contract traces back to the exact product version it was originated under.
* **Origination**: Application intake, approval or rejection decisions, disbursement, schedule preview, and the regulatory disclosures the jurisdiction requires.
* **Servicing**: Active contract schedules, repayment recording, prepayment, rescheduling, and corrections — with reversals and replays that keep history consistent.
* **Portfolio visibility**: Dashboards over the active book, including delinquency views.
* **Audit**: An immutable <GAuditTrail>audit trail</GAuditTrail> of every lifecycle event, preserved for compliance.

Most institutions assemble this from separate systems — a product catalog here, an origination tool there, servicing in the core, spreadsheets in between. Lender's premise is that the journey belongs in one engine, with one consistent history.

## The five domains that ship today

***

Under the hood, Lender is organized into five bounded domains. Every credit journey — whatever the product — flows through them:

| Domain                | What it owns                                                                                                                                                             |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Products**          | Loan products, immutable product versions, activation, charge templates, floating-rate tables, and the accounting profile that says how the product books to the ledger. |
| **Origination**       | The loan application lifecycle — submit, approve, reject, withdraw, disburse — plus schedule preview and decision records.                                               |
| **Servicing**         | The active loan account: schedules, repayments, prepayments, reschedules, and corrections applied through reversals and replays.                                         |
| **Accounting**        | Accounting profiles, posting rules, posting intents, accrual runs, and journal references that tie every financial event to the ledger.                                  |
| **Portfolio & audit** | Portfolio and delinquency dashboards, and the immutable audit trail behind them.                                                                                         |

Start with [Core concepts](/en/lender/core-concepts) for the vocabulary, then follow the guides for each domain.

## Jurisdiction-aware, Brazil first

***

Credit rules differ by jurisdiction, so Lender is built jurisdiction-aware from the start: a generic baseline for any market, and a deep Brazilian profile layered on top. The three credit journeys map onto that model:

| Journey   | Scope                                                                                                                  |
| --------- | ---------------------------------------------------------------------------------------------------------------------- |
| **CDC**   | Consumer credit operations — fixed-schedule lending to individuals, with the disclosures consumer regulation requires. |
| **PJ**    | Business lending — credit extended to companies, from origination through servicing.                                   |
| **Cards** | Card-based credit journeys.                                                                                            |

The deepest journey shipped today is **consignado privado** — payroll-deducted lending in Brazil, with active origination (contratação ativa), CCB generation and signing, and averbação lifecycle tracking. See [Consignado privado](/en/lender/consignado-privado).

For everything the Brazilian profile adds — CET disclosure, IOF preview, capitalization consent, PDD staging, and more — see the [Brazil regulatory pack](/en/lender/brazil-regulatory-pack).

## How Lender composes with the platform

***

Lender is a Lerian primitive: it runs on the platform rather than beside it.

* **Ledger**: Every financial event a credit journey produces — disbursement, repayment, accrual, reversal — books to the <GDoubleEntry>double-entry</GDoubleEntry> <GLedger>ledger</GLedger> through configurable accounting profiles and posting rules. The ledger stays the source of truth for balances; Lender stays the source of truth for the credit journey.
* **Multi-tenancy**: Like every Lerian product, Lender is built for full tenant isolation from the ground up.
* **Events**: Lifecycle events are published on the platform's streaming backbone, so downstream products and your own services can react to the credit journey as it unfolds.
* **Observability**: Structured logs, traces, and metrics on the same observability stack as the rest of the platform.

See [Lender in the platform](/en/lender/lender-in-the-platform) for the posting path, the event catalog, and tenant isolation.

## Next steps

***

<Card title="Core concepts" icon="book" href="/en/lender/core-concepts" horizontal>
  Learn the vocabulary: loan products, accounting profiles, applications, loan accounts, accrual runs, and the Brazil terms.
</Card>

<Card title="Lender in the platform" icon="sitemap" href="/en/lender/lender-in-the-platform" horizontal>
  See how Lender posts to the <GLedger>ledger</GLedger>, emits events, and isolates tenants.
</Card>

<Card title="Originate a loan" icon="file-signature" href="/en/lender/originate-a-loan" horizontal>
  Walk an application from intake through preview, approval, and disbursement.
</Card>

<Card title="Consignado privado" icon="brazilian-real-sign" href="/en/lender/consignado-privado" horizontal>
  Explore the flagship Brazilian journey: contratação ativa, CCB, and averbação.
</Card>

If you want to talk about credit journeys on the Lerian platform, [contact us](https://lerian.studio/contact).