> ## 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. # Credit > Define loan products and versions, record and decide loan applications, and emit credit instruments in the Lender module. The **Credit** section of the [Lender module](https://docs.lerian.studio/en/products/lender/console/lender-module.md) holds **Products** and **Loan applications**. For the model behind them, see [Define a loan product](https://docs.lerian.studio/en/products/lender/define-a-loan-product.md) and [Originate a loan](https://docs.lerian.studio/en/products/lender/originate-a-loan.md). ## Products *** **Products** lists the credit products your institution offers, each versioned with its terms. Filter by name, status, or type. The list hides archived products unless the status filter asks for them. ### Create a product **New product** opens a wizard. Its steps record the product, its first version, and its activation. These records are permanent. | Step | What you record | | - | - | | **Product identity** | The name, the type, and the jurisdiction. You cannot edit them. | | **Version and rates** | Version 1: the currency and the rate terms, with the change reason. You cannot edit a recorded version. To correct one, record another. | | **Brazilian regulatory extension** | The tax regime and the consumer-protection caps that go with the version. This step appears for a Brazil product. | | **Accounting profile** | The double-entry posting rules of the version. | | **Review and activate** | Pins the version as the product's active version and moves the product to active. You cannot undo or repeat it. | A product that stops before the end shows **Needs setup**. **Continue in the wizard** resumes it. ### Work with a product A product page shows its active version, its rate terms, the version terms (read only), and its versions. * **Record new version** records a version with its own rates and limits. You can also set how long a payoff quote of a contract on the version stays payable, from 1 to 168 hours. Left empty, the deployment default applies. A new version does not carry over the Brazilian regulatory terms of the live version. Declare them again. The form also sets the **CCB issuer**, **Issued by Lender** or **Issued by the institution**, and the product wizard asks for the same in its version step. On a consignado version, the form replaces the late fee, default interest, and tolerance fields with a note. A consignado version takes no late-payment terms. * **Configure accounting profile** binds the double-entry posting rules to a version. A version with no profile, or with missing rules, shows what is missing. * **Archive product** removes the product from the list and stops new contracts on it, after a confirmation. Its existing contracts do not change. **Unarchive product** returns it to the list. * **Promote** makes a version the one that new applications originate on. Contracts and applications already in flight keep the version they were booked on. The new version takes effect when you promote it, once its accounting profile is configured. * **Chart of accounts changes** records a change to the chart of the product's versions from a given day. Recording a change moves no money. **Run sweep** then queues one transfer per contract from the old accounts to the new ones. * **Document templates** holds the CCB templates of the product. **Create draft** adds a template draft. **Publish** makes a version the one that emission uses. Drafts and earlier published versions are kept. ## Loan applications *** **Loan applications** lists credit requests from record to release. Filter by application or borrower, or by status. The search applies to the applications on the page you see. A whole borrower ID and the status filter apply to all of them. ### Record an application **New loan application** records an application against an active product. You give: * The borrower's CPF or CNPJ and the borrower's name. Lender finds the holder with that document in the CRM of the product's institution, or registers one. An existing holder keeps its name. * The way the proposal is requested: by principal, by the net amount the borrower receives, or by the installment amount. * The number of installments, the monthly rate, and the first due date, or the grace days (carência) before it. Give one of the two, not both. The product version sets the window the first due date can fall in. * Whether the borrower is under Simples Nacional. **Quote schedule** computes the schedule on those values and records the offer that the application cites. It changes no application. You cannot edit or delete a recorded application. ### Decide an application Open an application to **Approve**, **Reject**, **Withdraw**, or **Disburse** it. Approval, rejection, and withdrawal are permanent. A rejection or a withdrawal closes the application with the reason you give. Lender sends no payment: your institution pays the borrower through its own channel, and a disbursement records that release and books it in the ledger. The console records the release on today's date. To record a release from an earlier day, call the API with `disbursedAt`, as [Record a release your institution made](https://docs.lerian.studio/en/products/lender/originate-a-loan.md#record-a-release-your-institution-made) describes. ### Credit instruments On an application, **Credit instruments** emits the CCB, lists the instruments already emitted, and downloads one as a PDF. The version of the product sets who issues the CCB: see [Issue the CCB](https://docs.lerian.studio/en/products/lender/issue-the-ccb.md). When Lender issues the CCB, **Emit instrument** appears on an approved application. It renders a new PDF from the active document template of the product. The application's status does not change. If no template is published, emission is refused. When the institution issues the CCB, Lender emits none: the page says so, and the integrator records the signed CCB through the API. On an approved or disbursed application, in both modes, a card shows the signed CCB. Until the integrator records it through the API, the card reads **Signed CCB not recorded yet**. **Download PDF** and **Replace** appear only when Lender holds the PDF. **Replace** sends the new PDF and asks for the reason, when the parties signed, the reference to the signature evidence, and the name and document of each signatory again. The replaced record stays in Lender's history. Disbursement does not wait for the signed CCB. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.