# HES FinTech docs > Documentation for HES LoanBox — an end-to-end loan management platform. > Maintained by HES FinTech. ## LoanBox - [HES LoanBox tech library overview](https://docs.hesfintech.com/) - [Platform overview](https://docs.hesfintech.com/loanbox/platform-overview/) - [Overview](https://docs.hesfintech.com/loanbox/user-and-role-management/) - [HES LoanBox and Keycloak connected](https://docs.hesfintech.com/loanbox/user-and-role-management/hes-loanbox-and-keycloak-connected/) - [Creating users in Keycloak](https://docs.hesfintech.com/loanbox/user-and-role-management/creating-users/) - [Predefined roles in Keycloak](https://docs.hesfintech.com/loanbox/user-and-role-management/predefined-roles-in-keycloak/) - [Assigning a role to a user](https://docs.hesfintech.com/loanbox/user-and-role-management/assigning-a-role-to-a-user/) - [Overview](https://docs.hesfintech.com/loanbox/product-groups-and-products/) - [Creating a product group](https://docs.hesfintech.com/loanbox/product-groups-and-products/creating-a-product-group/) - [Editing a product group](https://docs.hesfintech.com/loanbox/product-groups-and-products/editing-a-product-group/) - [Product group list and filters](https://docs.hesfintech.com/loanbox/product-groups-and-products/product-group-list-and-filters/) - [Creating a product](https://docs.hesfintech.com/loanbox/product-groups-and-products/creating-a-product/) - [Product list and filters](https://docs.hesfintech.com/loanbox/product-groups-and-products/product-list-and-filters/) - [Editing a product](https://docs.hesfintech.com/loanbox/product-groups-and-products/editing-a-product/) - [Overview](https://docs.hesfintech.com/loanbox/customer-onboarding-and-application-process/) - [Application process](https://docs.hesfintech.com/loanbox/customer-onboarding-and-application-process/what-is-customer-onboarding/) - [Submitting an application](https://docs.hesfintech.com/loanbox/customer-onboarding-and-application-process/ways-to-submit-an-application/) - [Submission by channel](https://docs.hesfintech.com/loanbox/customer-onboarding-and-application-process/submission-process-per-channel/) - [Overview](https://docs.hesfintech.com/loanbox/loan-origination-process/) - [How it works](https://docs.hesfintech.com/loanbox/loan-origination-process/what-is-the-loan-origination-process/) - [What determines the process](https://docs.hesfintech.com/loanbox/loan-origination-process/what-determines-the-process/) - [Step-by-step](https://docs.hesfintech.com/loanbox/loan-origination-process/step-by-step-description/) - [Process tasks](https://docs.hesfintech.com/loanbox/loan-origination-process/tasks-during-the-process/) - [Borrower notifications](https://docs.hesfintech.com/loanbox/loan-origination-process/notifications-for-the-borrower/) - [Overview](https://docs.hesfintech.com/loanbox/scoring-and-credit-decisioning/) - [Scoring providers](https://docs.hesfintech.com/loanbox/scoring-and-credit-decisioning/scoring-providers/) - [Connecting GiniMachine to a product group](https://docs.hesfintech.com/loanbox/scoring-and-credit-decisioning/connecting-ginimachine-to-a-product-group/) - [The Scoring result decision table](https://docs.hesfintech.com/loanbox/scoring-and-credit-decisioning/the-scoring-result-decision-table/) - [Reading GiniMachine scoring results](https://docs.hesfintech.com/loanbox/scoring-and-credit-decisioning/reading-ginimachine-scoring-results/) - [Overview](https://docs.hesfintech.com/loanbox/contract-signing/) - [Signing options (product-group level)](https://docs.hesfintech.com/loanbox/contract-signing/signing-options/) - [Signing flow](https://docs.hesfintech.com/loanbox/contract-signing/signing-walkthrough/) - [Deadline expiration](https://docs.hesfintech.com/loanbox/contract-signing/deadline-expiration/) - [New offer mid-signing](https://docs.hesfintech.com/loanbox/contract-signing/new-offer-at-mid-signing/) - [User tasks](https://docs.hesfintech.com/loanbox/contract-signing/user-facing-tasks/) - [Overview](https://docs.hesfintech.com/loanbox/loan-management-and-servicing/) - [Creating a loan / credit line](https://docs.hesfintech.com/loanbox/loan-management-and-servicing/loan-credit-line-created/) - [Activating a loan / credit line](https://docs.hesfintech.com/loanbox/loan-management-and-servicing/loan-credit-line-activated/) - [Interest accrual](https://docs.hesfintech.com/loanbox/loan-management-and-servicing/interest-accrual/) - [Disbursement](https://docs.hesfintech.com/loanbox/loan-management-and-servicing/disbursement-process-and-options/) - [Scheduled payments](https://docs.hesfintech.com/loanbox/loan-management-and-servicing/scheduled-payment-process/) - [Payment allocation](https://docs.hesfintech.com/loanbox/loan-management-and-servicing/payment-allocation/) - [Loan list and filters](https://docs.hesfintech.com/loanbox/loan-management-and-servicing/loan-list-and-filters/) - [Write-off](https://docs.hesfintech.com/loanbox/loan-management-and-servicing/write-off-operation/) - [Register payment](https://docs.hesfintech.com/loanbox/loan-management-and-servicing/register-payment-operation/) - [Waive fees](https://docs.hesfintech.com/loanbox/loan-management-and-servicing/waive-fees-operation/) - [Adjust loan](https://docs.hesfintech.com/loanbox/loan-management-and-servicing/adjust-loan-operation/) - [Overview](https://docs.hesfintech.com/loanbox/collection-process/) - [Overdue loans](https://docs.hesfintech.com/loanbox/collection-process/overdue-loan/) - [Collection flow](https://docs.hesfintech.com/loanbox/collection-process/collection-workflow/) - [Back-office collection tasks](https://docs.hesfintech.com/loanbox/collection-process/collection-task/) - [Overview](https://docs.hesfintech.com/loanbox/collateral-management/) - [Collateral requirements](https://docs.hesfintech.com/loanbox/collateral-management/collateral-requirements/) - [Verification](https://docs.hesfintech.com/loanbox/collateral-management/verification-stage/) - [LTV](https://docs.hesfintech.com/loanbox/collateral-management/ltv/) - [Collateral list, filters and details](https://docs.hesfintech.com/loanbox/collateral-management/collateral-list-filters-and-details/) - [Automatic re-evaluation](https://docs.hesfintech.com/loanbox/collateral-management/automatic-collateral-re-evaluation/) - [Manual re-evaluation](https://docs.hesfintech.com/loanbox/collateral-management/manual-collateral-re-evaluation/) - [Overview](https://docs.hesfintech.com/loanbox/agent-portal/) - [Agent list and filters](https://docs.hesfintech.com/loanbox/agent-portal/agent-list-and-filters/) - [Creating an agent](https://docs.hesfintech.com/loanbox/agent-portal/creating-an-agent/) - [Editing an agent](https://docs.hesfintech.com/loanbox/agent-portal/editing-an-agent/) - [Inviting an agent user](https://docs.hesfintech.com/loanbox/agent-portal/invite-an-agent-user/) - [Re-invite an agent user](https://docs.hesfintech.com/loanbox/agent-portal/re-invite-an-agent-user/) - [The Agent Portal](https://docs.hesfintech.com/loanbox/agent-portal/the-agent-portal/) - [Overview](https://docs.hesfintech.com/loanbox/borrower-portal/) - [Signing in](https://docs.hesfintech.com/loanbox/borrower-portal/signing-in/) - [Modules](https://docs.hesfintech.com/loanbox/borrower-portal/modules/) - [Borrower operations: detailed flows](https://docs.hesfintech.com/loanbox/borrower-portal/borrower-operations-detailed-flows/) - [Borrower operations summary](https://docs.hesfintech.com/loanbox/borrower-portal/borrower-operations-summary/) - [Overview](https://docs.hesfintech.com/loanbox/settings/) - [Interest rate setting](https://docs.hesfintech.com/loanbox/settings/interest-rate-setting/) - [License info setting](https://docs.hesfintech.com/loanbox/settings/license-info-setting/) - [Landing page calculator setting](https://docs.hesfintech.com/loanbox/settings/landing-page-calculator-setting/) - [Scoring model setting](https://docs.hesfintech.com/loanbox/settings/scoring-model-setting/) - [Document templates setting](https://docs.hesfintech.com/loanbox/settings/document-templates-setting/) - [Notifications setting](https://docs.hesfintech.com/loanbox/settings/notifications-setting/) - [Overview](https://docs.hesfintech.com/loanbox/reports-and-analytics/) - [Metabase integration](https://docs.hesfintech.com/loanbox/reports-and-analytics/metabase-integration/) - [Opening a dashboard](https://docs.hesfintech.com/loanbox/reports-and-analytics/opening-a-dashboard/) - [Analytics list](https://docs.hesfintech.com/loanbox/reports-and-analytics/analytics-list/) - [Access to Analytics](https://docs.hesfintech.com/loanbox/reports-and-analytics/access-to-analytics/) - [Dashboards and reports](https://docs.hesfintech.com/loanbox/reports-and-analytics/dashboards-and-reports/) - [Overview](https://docs.hesfintech.com/loanbox/security/) - [Identity and access management](https://docs.hesfintech.com/loanbox/security/identity-and-access-management/) - [Data, application, and API security](https://docs.hesfintech.com/loanbox/security/data-application-and-api-security/) - [Infrastructure and deployment security](https://docs.hesfintech.com/loanbox/security/infrastructure-and-deployment-security/) - [Audit logging and monitoring](https://docs.hesfintech.com/loanbox/security/audit-logging-and-monitoring/) - [Compliance and secure development](https://docs.hesfintech.com/loanbox/security/compliance-and-secure-development/) ## Glossary - [Glossary](https://docs.hesfintech.com/glossary/) ## Glossary terms - **Product group** — A lending program that combines products and defines the overall strategy for issuing and servicing loans ([definition](https://docs.hesfintech.com/glossary/product-group/)) - **Product** — A specific lending offer within a product group with defined conditions ([definition](https://docs.hesfintech.com/glossary/product/)) - **Product name** — A title given to a specific product within the product group ([definition](https://docs.hesfintech.com/glossary/product-name/)) - **Loan type** — Classification of the loan structure: fixed-term or credit line ([definition](https://docs.hesfintech.com/glossary/loan-type/)) - **Calculation type** — Method for generating the payment schedule (annuity, linear, pay-day, bullet, revolving/non-revolving line) ([definition](https://docs.hesfintech.com/glossary/calculation-type/)) - **Interest rate** — The rate at which interest is charged on the principal balance (calculated automatically: prime rate + margin) ([definition](https://docs.hesfintech.com/glossary/interest-rate/)) - **Fixed interest rate** — An interest rate that stays the same for the full term of a loan or credit line, making payments more predictable. ([definition](https://docs.hesfintech.com/glossary/fixed-interest-rate/)) - **Floating interest rate** — An interest rate that moves up or down during the loan/credit line term based on a prime rate. An interest rate calculated as the sum of the prime rate and the margin. ([definition](https://docs.hesfintech.com/glossary/floating-interest-rate/)) - **Prime rate** — A system-wide rate used to calculate floating interest rates ([definition](https://docs.hesfintech.com/glossary/prime-rate/)) - **Daily grace interest rate** — Daily interest rate during the grace period ([definition](https://docs.hesfintech.com/glossary/daily-grace-interest-rate/)) - **Margin** — A fixed markup added to the prime rate when calculating a floating interest rate ([definition](https://docs.hesfintech.com/glossary/margin/)) - **Default interest rate** — A penalty rate applied daily to the overdue principal balance of loans/credit lines. ([definition](https://docs.hesfintech.com/glossary/default-interest-rate/)) - **Term period type** — The unit in which the loan term is measured (days, weeks, months, years) ([definition](https://docs.hesfintech.com/glossary/term-period-type/)) - **Payment frequency** — The frequency at which the borrower makes payments ([definition](https://docs.hesfintech.com/glossary/payment-frequency/)) - **Grace period** — A period after loan disbursement during which a reduced interest rate applies ([definition](https://docs.hesfintech.com/glossary/grace-period/)) - **Scoring** — Automated assessment of the borrower's creditworthiness ([definition](https://docs.hesfintech.com/glossary/scoring/)) - **Verification** — Borrower verification strategy - whether an additional verification step is required ([definition](https://docs.hesfintech.com/glossary/verification/)) - **Underwriting** — The process of making a decision on whether to issue a loan ([definition](https://docs.hesfintech.com/glossary/underwriting/)) - **Establishment fee** — A fixed amount deducted from the loan amount at disbursement for fixed-term loans. A fixed amount added to the drawdown amount for credit lines. ([definition](https://docs.hesfintech.com/glossary/establishment-fee/)) - **Service fee** — A percentage of the loan amount deducted at disbursement for fixed-term loans. A percentage of the drawdown amount added at disbursement for credit lines. ([definition](https://docs.hesfintech.com/glossary/service-fee/)) - **Early repayment fee** — A charge applied when a borrower partially or fully repays a fixed-term loan before maturity, calculated on the principal balance ([definition](https://docs.hesfintech.com/glossary/early-repayment-fee/)) - **Overdue penalty** — A one-time penalty for each missed payment ([definition](https://docs.hesfintech.com/glossary/overdue-penalty/)) - **Amount selection step** — The interval between adjacent amount values ([definition](https://docs.hesfintech.com/glossary/amount-selection-step/)) - **Term selection mode** — Method for the borrower to select the term ([definition](https://docs.hesfintech.com/glossary/term-selection-mode/)) - **Application** — A loan request that progresses through intake toward a confirmed set of loan conditions handed to origination ([definition](https://docs.hesfintech.com/glossary/application/)) - **Loan calculator** — The first form the customer sees under a product group, used to pick the amount, term, and payment frequency ([definition](https://docs.hesfintech.com/glossary/loan-calculator/)) - **KYC** — Identity verification of the customer or of the company's representative ([definition](https://docs.hesfintech.com/glossary/kyc/)) - **Open banking verification** — Verification of the customer's bank account ([definition](https://docs.hesfintech.com/glossary/open-banking-verification/)) - **Lead** — A potential customer record captured by an agent (first name, last name, phone, email, assigned agent). A lead can be turned into an active application via the "Send loan application" action, which sends an invitation to the Borrower Portal ([definition](https://docs.hesfintech.com/glossary/lead/)) - **Origination** — The decisioning phase that runs after intake ([definition](https://docs.hesfintech.com/glossary/origination/)) - **Active application** — An application that has been started but has not yet reached a closed state (approved / declined / canceled / disbursed / error). A customer can have only one active application at a time ([definition](https://docs.hesfintech.com/glossary/active-application/)) - **Loan origination process** — The underwriting and decisioning stage of a loan application. Runs after the borrower has submitted the application and before contract signing. ([definition](https://docs.hesfintech.com/glossary/loan-origination-process/)) - **Borrower type** — Whether the borrower is an individual person or a legal entity (company). Determines which origination flow is used. ([definition](https://docs.hesfintech.com/glossary/borrower-type/)) - **Stop factor** — An automated rule that immediately disqualifies the application (e.g., on a blacklist, or an age limit not met). ([definition](https://docs.hesfintech.com/glossary/stop-factor/)) - **Scoring zone** — The risk band returned by the scoring engine (top / middle). Used together with the underwriting setting to decide whether an underwriter is required. ([definition](https://docs.hesfintech.com/glossary/scoring-zone/)) - **LTV** — Loan-to-value percentage, calculated when the application has collateral. ([definition](https://docs.hesfintech.com/glossary/ltv/)) - **Amortisation schedule** — The list of repayment periods (payment date, principal, interest, and fees) calculated for the approved loan. ([definition](https://docs.hesfintech.com/glossary/amortisation-schedule/)) - **Contract signing** — The loan origination stage during which the borrower signs the loan contract before the loan is activated and disbursed. ([definition](https://docs.hesfintech.com/glossary/contract-signing/)) - **Signing option** — A product group parameter that determines how the borrower signs the contract: E-signature, OTP, or Outside the system. ([definition](https://docs.hesfintech.com/glossary/signing-option/)) - **E-signature** — A signing option where the borrower signs the contract through an embedded electronic-signature provider window (iframe) inside the Borrower Portal. ([definition](https://docs.hesfintech.com/glossary/e-signature/)) - **OTP** — A one-time password sent to the borrower by SMS to confirm signing of the contract; valid for 10 minutes after it is generated. ([definition](https://docs.hesfintech.com/glossary/otp/)) - **Outside the system** — A signing option where the borrower signs the contract offline and a credit officer uploads the signed copy in the Back Office. ([definition](https://docs.hesfintech.com/glossary/outside-the-system/)) - **E-sign service** — The system-wide e-signature provider setting (pandaDoc or pandaDocEmail), used when a product group's Signing option is E-signature. pandaDoc signs in an in-portal iframe; pandaDocEmail sends a signing link by email. ([definition](https://docs.hesfintech.com/glossary/e-sign-service/)) - **Contract template** — The document template attached to a product group, from which the system generates the contract PDF filled with the borrower's data and approved loan terms. ([definition](https://docs.hesfintech.com/glossary/contract-template/)) - **First payment date** — The date of the borrower's first repayment. Before signing starts it must be at least 4 days ahead, unless the product is a credit line or a payday loan. ([definition](https://docs.hesfintech.com/glossary/first-payment-date/)) - **Signatory** — The party who signs the contract: the borrower for an individual, or the authorized representative for a legal entity. ([definition](https://docs.hesfintech.com/glossary/signatory/)) - **Collection strategy** — The recovery approach configured on a product group. Today: Default or None. ([definition](https://docs.hesfintech.com/glossary/collection-strategy/)) - **Collection case** — The recovery file opened for an overdue loan. Tracks all call results and the case status. ([definition](https://docs.hesfintech.com/glossary/collection-case/)) - **Call result** — A single recorded contact attempt with the borrower. Holds outcome, promise-to-pay info, next-reminder date, comment, author, and call date. ([definition](https://docs.hesfintech.com/glossary/call-result/)) - **Promise to pay** — The borrower's commitment to repay by a specific date for a specific amount. ([definition](https://docs.hesfintech.com/glossary/promise-to-pay/)) - **Days in overdue** — Number of calendar days since the loan became overdue, calculated automatically from the overdue date. ([definition](https://docs.hesfintech.com/glossary/days-in-overdue/)) - **Collection Manager** — Back-office role that handles borrower contact during collection. ([definition](https://docs.hesfintech.com/glossary/collection-manager/)) - **Credit Officer** — Back-office role that authorizes write-offs at the end of collection. ([definition](https://docs.hesfintech.com/glossary/credit-officer/)) - **Agent** — A partner organization (broker, dealer, merchant, referral partner) registered in the platform to originate loans on behalf of borrowers. ([definition](https://docs.hesfintech.com/glossary/agent/)) - **Agent user** — An individual person with a login linked to a specific agent organization. ([definition](https://docs.hesfintech.com/glossary/agent-user/)) - **Partner Manager** — A Backoffice role that can manage all agents and all leads across the whole platform. ([definition](https://docs.hesfintech.com/glossary/partner-manager/)) - **Invitation** — The one-time process that creates the login of a new agent user, sets a temporary password, sends an email with credentials, and collects the agent's bank account details if they are still missing. ([definition](https://docs.hesfintech.com/glossary/invitation/)) - **Re-invitation** — A repeat of the invitation that resets the temporary password, sends a fresh email, and cancels any previously running invitation for the same person. ([definition](https://docs.hesfintech.com/glossary/re-invitation/)) - **Task** — A pending step the system is waiting on the agent user to complete (for example, filling missing data on an application). ([definition](https://docs.hesfintech.com/glossary/task/)) - **Collateral** — A physical or financial asset pledged to secure a loan. ([definition](https://docs.hesfintech.com/glossary/collateral/)) - **Valuation period** — The interval, in months, between scheduled re-evaluations of the collateral. ([definition](https://docs.hesfintech.com/glossary/valuation-period/)) - **Re-evaluation event** — An audit record describing a single update of the collateral value, with its new amount, timestamp, and initiator. ([definition](https://docs.hesfintech.com/glossary/re-evaluation-event/)) - **Realm** — An isolated user store inside Keycloak. Each HES LoanBox portal authenticates against its own realm. ([definition](https://docs.hesfintech.com/glossary/realm/)) - **Realm role** — A role that exists within a single realm and can be assigned to users of that realm. All LoanBox-recognised roles are realm roles. ([definition](https://docs.hesfintech.com/glossary/realm-role/)) - **Role** — A named permission that an administrator assigns to a user. HES LoanBox endpoints and process tasks check for specific role names. ([definition](https://docs.hesfintech.com/glossary/role/)) - **Default role** — A role that Keycloak automatically attaches to every new user in a realm. Works for Borrower and Agent. ([definition](https://docs.hesfintech.com/glossary/default-role/)) - **Temporary password** — A password that the user must change the first time they sign in. Used during borrower and agent invitations and when an administrator creates a back-office user. ([definition](https://docs.hesfintech.com/glossary/temporary-password/)) - **Metabase** — A third-party business intelligence tool used to build dashboards and reports. HES LoanBox integrates with it but does not include it. ([definition](https://docs.hesfintech.com/glossary/metabase/)) - **Dashboard** — A page in Metabase that combines one or more charts, tables, or KPIs on a single screen. ([definition](https://docs.hesfintech.com/glossary/dashboard/)) - **Embeddable dashboard** — A dashboard that has been explicitly marked in Metabase as "shareable through an embed link." Only embeddable dashboards appear in HES LoanBox. ([definition](https://docs.hesfintech.com/glossary/embeddable-dashboard/)) - **BackOffice** — The internal HES LoanBox web application used by operations, underwriting, collections, and analytics staff. ([definition](https://docs.hesfintech.com/glossary/backoffice/)) - **Loan Data Manager** — The BackOffice role that grants access to the Analytics area. ([definition](https://docs.hesfintech.com/glossary/loan-data-manager/)) - **Viewing link** — A short-lived, signed URL that HES LoanBox issues each time a dashboard is opened. It expires after about 10 minutes and is replaced automatically on the next view. ([definition](https://docs.hesfintech.com/glossary/viewing-link/)) --- ## Full content ### Overview Source: https://docs.hesfintech.com/loanbox/user-and-role-management/ Overview and definitions HES LoanBox does not manage user credentials, sign-in screens, or password policies on its own. All authentication and identity management is delegated to Keycloak — an external identity and access management product. This document explains how HES LoanBox and Keycloak work together, how a user gets access to HES LoanBox, which roles the platform recognizes, and how an administrator assigns a role to a user. ### HES LoanBox and Keycloak connected Source: https://docs.hesfintech.com/loanbox/user-and-role-management/hes-loanbox-and-keycloak-connected/ HES LoanBox and Keycloak connected HES LoanBox is a back-end platform with several portals: Borrower Portal, BackOffice Portal, Agent Portal, plus a machine-to-machine integration API. None of the portals show a LoanBox-owned login screen — every sign-in is handled by Keycloak. Key characteristics Keycloak is the source of truth for users. A user account, password, phone, email, password reset, account deactivation, and temporary password handling all live in Keycloak. HES LoanBox never stores a password. One realm per portal. Each portal authenticates against its own isolated Keycloak realm. Users from one realm cannot access another portal: Realm Who uses it BorrowerRealm Borrowers using the Borrower Portal BackofficeRealm Internal staff using the BackOffice Portal AgentRealm External partners and agents using the Agent Portal Single sign-on is token-based. After a user signs in to Keycloak, HES LoanBox accepts a short-lived security token on every request and reads the user’s name and roles from it. There are no LoanBox-side login sessions. Roles drive what a user can do. HES LoanBox checks the roles carried in the token at every endpoint and at every step inside business processes. If the role does not permit the action, the action is rejected. The platform creates some users automatically. Borrowers and agents are created in Keycloak by HES LoanBox itself during the application and agent-invitation flows. All other users — back-office staff, integration clients, analytics users, administrators — are created directly in Keycloak by an administrator. Relationship with related concepts A Borrower profile in HES LoanBox is paired with a Keycloak user account. The Keycloak user holds the credentials; HES LoanBox holds the application and loan data. An Agent record in HES LoanBox is paired with a Keycloak user under a specific partner organization. The partner identifier is stored as a Keycloak attribute on the user so the Agent Portal can scope data correctly. A Staff user is a Keycloak user in the Backoffice realm with one or more backoffice roles. The platform does not store a separate staff profile — the role in Keycloak is enough. ### Creating users in Keycloak Source: https://docs.hesfintech.com/loanbox/user-and-role-management/creating-users/ Creating users in Keycloak How a user is created depends on which portal they need to use. Some flows happen automatically inside LoanBox; others are performed by an administrator directly in Keycloak. BackofficeRealm Backoffice users (internal staff such as credit officers, underwriters, verifiers, collection managers, partner managers, analytics users, and administrators) are not created by LoanBox. They are created directly in Keycloak by an administrator. Step 1. Sign in to Keycloak. The administrator opens the Keycloak Administration Console and selects the Backoffice realm. Step 2. Open the user list. Navigate to Users → Add user. Step 3. Fill in the user fields. Provide the basic user information: Username: the login the operator will use on the BackOffice Portal. Email, First name, Last name: used for display and notifications. Email verified / Enabled: typically set so the user can sign in immediately. Step 4. Save the user. Keycloak creates the account. Step 5. Set the initial password. Open the new user’s Credentials tab and set a temporary password. Toggle Temporary on so Keycloak forces the operator to change the password on first sign-in. Step 6. Assign one or more roles. Follow the role-assignment procedure described on the Assigning a role to a user page. Step 7. The operator signs in. The operator opens the BackOffice Portal, signs in via Keycloak, sets a permanent password, and lands on the BackOffice home screen. Result: A backoffice user exists in the Backoffice realm with the assigned roles. The user can access the BackOffice Portal areas that the assigned roles permit. BorrowerRealm Borrower accounts are always created automatically by LoanBox. There are two creation flows; only one is active at a time, controlled by a platform setting (KEYCLOAK_AUTH_BROWSER_FLOW): SMS or email. Step 1. A new applicant appears. A borrower starts a loan application from the Borrower Portal, or an agent invites a borrower from the Agent Portal, or a backoffice operator submits an application on a borrower’s behalf. Step 2. The system checks whether the user already exists. HES LoanBox looks up the phone number (SMS flow) or email address (email flow) in Keycloak. If a user with that username already exists, the existing account is reused and no new account is created. Step 3a. SMS flow — the system creates a passwordless user. A new user is created in the BorrowerRealm with the phone number as the username. Two attributes are stored on the user: phoneNumber and phoneNumberVerified=true. The borrower will sign in later using a one-time code sent via SMS — no password is set. Step 3b. Email flow — the system creates a user with a temporary password. A new user is created in the BorrowerRealm with the email address as both the username and the email. The system generates an 8-character temporary password (at least one lower-case letter, one upper-case letter, one digit, and one special character from !@#$%^&*) and assigns it to the new user. The password is marked temporary — Keycloak forces the borrower to change it the first time they sign in. Step 4. The borrower receives the invitation. HES LoanBox sends the borrower a notification with the link to the Borrower Portal. For the email flow, the temporary password is delivered to the borrower in the same notification. Step 5. The borrower signs in. The borrower opens the Borrower Portal, completes the Keycloak login (one-time SMS code or temporary password followed by setting a permanent one), and is returned to the portal as an authenticated user. Result: A borrower user exists in the BorrowerRealm and carries the Borrower role. The user can access the Borrower Portal only. AgentRealm Agent accounts are created automatically by HES LoanBox when a Partner Manager invites a new agent from the BackOffice Portal. Step 1. Open the invite form. A Partner Manager opens “Invite agent user” in the BackOffice Portal and provides the agent’s username (email) and the partner record the agent belongs to. Step 2. The system checks whether the user already exists. If a user with that username already exists in the AgentRealm, the system updates the existing user’s temporary password instead of creating a new account. Step 3. The system creates the user. When no user exists, a new user is created in the AgentRealm with the email as the username. The partner identifier is stored as a partner_id attribute on the Keycloak user. A temporary password is generated and assigned (same rules as the borrower email flow). The user is enabled. Step 4. The agent receives the invitation. HES LoanBox sends an email to the new agent with the link to the Agent Portal and the temporary password. The password is removed from the system right after the notification is sent. Step 5. The agent signs in and completes onboarding. The agent opens the Agent Portal, signs in, sets a permanent password, and is asked to fill in bank account details if the partner organisation does not already have them. Result: An agent user exists in the AgentRealm with the partner identifier attribute and can access the Agent Portal scoped to their partner. ### Predefined roles in Keycloak Source: https://docs.hesfintech.com/loanbox/user-and-role-management/predefined-roles-in-keycloak/ Predefined roles in Keycloak HES LoanBox is designed to work with a fixed set of role names. Every endpoint, every process task, and every menu permission is wired to one or more of these role names. For the platform to function, predefined roles are listed below. Roles by realm Role Realm Display name Description Borrower BorrowerRealm Borrower Self-service access to own profile, applications, loans, schedules, transactions, and contract signing. Agent AgentRealm Agent (partner user) Lead creation, agent-originated applications and access to loans linked to the agent’s partner organisation. PartnerManager Backoffice Partner manager Management of agent partners and agent users across all partner organisations. Cross-partner visibility. CreditOfficer Backoffice Credit officer Most-permissive backoffice role. Covers loan operations, borrower management, product group and product configuration, document and notification templates, scoring model settings, write-offs, manual disbursements, contract management and loan adjustments. Underwriter Backoffice Underwriter Application evaluation and credit decision (approve / decline), review of scoring errors, view access to loans, applications, borrowers, products and configuration. Verifier Backoffice Verifier Manual verification of borrower data and documents, collateral review, bank account verification data correction, and provision of financial data for legal entity applications. CollectionManager Backoffice Collection manager Overdue case management, calling the borrower, viewing and managing loans in collection, and contract management for collection. LoanDataManager Backoffice Analytics user Access to embedded analytics dashboards (Metabase). Access summary by role The table below lists the user-visible capabilities that each role unlocks. Where the same area is shown for multiple roles, the level of access differs: read-only roles can view but not edit; full-access roles can create, edit, and approve. Role Capabilities Borrower View own loan applications, active loans, repayment schedules, transactions; submit new applications; sign contracts; receive borrower-side tasks (provide bank details, etc.). Agent Create and manage leads; submit applications on behalf of leads; view loans assigned to their partner; fill in their own bank account details. PartnerManager Create, view and edit agents; view and manage agent users. CreditOfficer Full borrower management; full loan operations and recalculation; manage product groups; create, edit, activate, deactivate loan products; manage scoring model settings (add, deploy, activate, validate); manage interest rate settings, landing page settings, document templates, notification templates; verify applications; make a decision on applications when underwriter is unavailable in cross-role contexts; approve bank account changes; upload signed contracts; review loan adjustment requests; write off loans during collection. Underwriter Make a decision on an application (approve / decline); review scoring errors; view borrowers, loans, applications, products, product groups, templates and interest rate settings. Verifier Verify applications; review and update collateral data; edit bank account verification data; provide financial data for legal entity applications; view borrowers, applications and settings. CollectionManager View and operate on loans in collection; call the borrower and record the result; manage transactions; view loans, applications, borrowers, products and templates. LoanDataManager View the list of embedded dashboards; open individual dashboards. Note A user can hold more than one role in the same realm. For example, a senior staff member may hold both CreditOfficer and Underwriter. Permissions are additive. Note The platform never assigns roles itself. Role assignment is always done by an administrator in Keycloak. When HES LoanBox creates a borrower or agent user, it sets up the account but does not attach the Borrower or Agent role. That is part of the realm configuration in Keycloak (typically a default realm role, so every new user receives it automatically). ### Assigning a role to a user Source: https://docs.hesfintech.com/loanbox/user-and-role-management/assigning-a-role-to-a-user/ Assigning a role to a user Role assignment is performed entirely inside Keycloak by an administrator. HES LoanBox does not provide a screen to assign a role. Prerequisites The administrator has access to the Keycloak Administration Console. The administrator has permission to manage users and roles in the target realm. The required role names already exist in the realm (see the Predefined roles in Keycloak page). The user account already exists in the realm. Steps to assign a role Step 1. Open the Keycloak Administration Console. Sign in with administrator credentials. Step 2. Select the realm. Use the realm selector at the top to pick the realm that contains the user — for example Backoffice for an internal staff user, AgentRealm for an agent, or BorrowerRealm for a borrower. Step 3. Open the user. Navigate to Users, search for the user by username or email, and click the user record to open it. Step 4. Open the role-mapping tab. Click the Role mapping tab on the user detail screen. Step 5. Open the role picker. Click Assign role. Keycloak shows the list of roles available in the current realm. Step 6. Pick the realm role(s). Choose one or more roles from the list — for example CreditOfficer, Underwriter. Multiple roles can be selected at once. Step 7. Confirm the assignment. Click Assign. Keycloak attaches the selected roles to the user. The role mapping is effective immediately for any new sign-in. Result: The user now appears in the role-mapping tab with the selected roles. The next time the user signs in, the security token issued by Keycloak will carry the new roles, and HES LoanBox will grant the corresponding access. Removing a role To revoke access, open the user’s Role mapping tab, find the role in the list of assigned roles, and click Unassign. The change applies the next time the user signs in or refreshes the security token. Default roles A realm may be configured so that every new user automatically receives a baseline role. This is the recommended setup for Borrower in the BorrowerRealm and for Agent in the AgentRealm, because HES LoanBox creates these users automatically and does not assign roles itself. With a default role configured, every new borrower or agent user receives the right role at the moment of creation without any further administrator action. For the Backoffice and Integration realms, default roles are not recommended — a new account should never carry permissions until an administrator explicitly grants them. ### Overview Source: https://docs.hesfintech.com/loanbox/product-groups-and-products/ Overview and definitions This document describes two key system objects: product group and product. It covers definitions, differences, creation and editing processes with all parameters and values, and list screens with filters. Creating product groups and products is one of the first steps in working with HES LoanBox. Borrower onboarding cannot begin without them. Product group A product group is a lending program that combines one or more products and defines the overall strategy for issuing and servicing loans. A product group determines: Loan type (fixed-term or credit line). Interest rate type (fixed or floating). Term period type (days, weeks, months, years). Calculation type (annuity, linear, pay-day loan, bullet installment, revolving credit line, non-revolving credit line). Allowed amount and term ranges for all products within the group. Verification, underwriting, scoring, and collection strategy. Disbursement and contract signing options. Borrower application requirements (supporting documents, collateral, additional information). Agent assignments and document templates. Note A product group can be active or inactive. Only active groups are available for loan applications. Product A product is a specific lending offer within a product group. A product defines exact amount and term ranges, interest rates, fees, and grace period conditions. Key characteristics of a product: Always belongs to exactly one product group. Inherits the loan type, term period type, and interest rate type from its product group. Product amount and term ranges must fall within the product group’s ranges. Can be active or inactive independently of the group’s status. For automatic matching during application processing, both the group and the product must be active. Maintains a history of all changes (audit). Comparison of product group and product Aspect Product group Product Purpose Defines the overall lending strategy and parameter boundaries Defines specific conditions of a lending offer Group attribution One or more products Belongs to exactly one group Loan type Set at the group level Inherited from the group Interest rate Sets the base rate (or margin for floating) for the group Sets a rate range within the group’s boundaries Amount and term Defines the allowed boundaries Defines specific ranges within the group’s boundaries Strategies (verification, underwriting, scoring, collection) Configured at the group level Not configured: uses the group’s strategies Fees (overdue penalty, establishment fee, service fee, and others) Not set Set at the product level Grace period Not set Set at the product level (for fixed-term loans only) Document templates Assigned to the group Not assigned - uses the group’s templates Agents Assigned to the group Not assigned: availability is determined by the group When to use which? A product group is created for each distinct lending program. Within a single group, products are created with different pricing conditions—for example, for different amount or term ranges. ### Creating a product group Source: https://docs.hesfintech.com/loanbox/product-groups-and-products/creating-a-product-group/ Creating a product group Process Creating a product group is available to users with the Credit Officer role. Step 1. Opening the creation form The user clicks the button to create a new product group. The system displays the “Create product group” form. Step 2. Filling in parameters The user fills in all required fields of the form (described below in Product group parameters). Step 3. Saving The system validates the data while the fields are being filled in. If all fields are filled in correctly, the “Save” button becomes active. If errors are found, the system displays messages next to the corresponding fields. When a user clicks the “Save” button, the system saves the created product group. Result: The product group is created. By default, it is inactive (the “Active” flag is off). Caution To make the group available for loan applications, the “Active” flag must be enabled during editing. Product group parameters General info Parameter Description Type Required Possible Values Default Notes Active Activity flag for the group. Only active groups are available for loan applications Yes/No No On / Off Off – Loan type Defines the basic structure of the lending product Dropdown Yes See table below – Cannot be changed after the group is created Name Product group name Text Yes Free text – Maximum 50 characters Agents Agents who have access to this product group Multiple selection No List of registered agents – An agent can be assigned to multiple groups Payment calculation type Determines the method for generating the payment schedule Dropdown Yes Depends on loan type; see table below – Cannot be changed after the group is created. Available values are filtered based on the selected loan type Term period type Unit of measurement for the loan term Dropdown Yes Depends on calculation type; see table below – Available values are filtered based on the selected calculation type Interest rate type Determines how the rate is calculated Dropdown Yes Depends on calculation type; see table below – Cannot be changed after the group is created. Available values are filtered based on the selected calculation type Disbursement option Method of disbursing funds to the borrower Dropdown Yes See table below – – Available payment frequency options Payment frequency options for products within the group Multiple selection Yes Depends on loan type; see table below – Hidden if the calculation type is Pay-Day Loan. Available values are filtered based on the loan type First payment date Possibility for the borrower to choose the first payment date Yes/No No On / Off Off Displayed only for fixed-term loans with a calculation type other than Pay-Day Loan Range of available days for the first payment date Range of days available for choosing the first payment date Number Yes (if the “First payment date” parameter is enabled) From 1 to 90 45 Displayed only if the “First payment date” parameter is enabled Drawdown freeze Number of days before drawdowns on a credit line are frozen Number (days) Yes (for credit lines) From 5 to 999 5 Displayed only for the “Credit line” loan type Loan type Value Description Fixed-term loan A loan with a defined repayment schedule and maturity date Credit line Revolving or non-revolving credit facility with a drawdown mechanism Calculation type Fixed-term loan Value Description Pay-day loan Short-term loan (single lump-sum repayment) Annuity installment Equal periodic payments that include both principal and interest Linear principal repayment installment Equal principal payments with decreasing interest Bullet installment Periodic interest payments with the full principal repaid in the final period Credit line Value Description Revolving credit line The limit is restored after repayment Non-revolving credit line Repaid funds cannot be reused Term period type Calculation type Available units Pay-day loan Days Annuity installment Weeks, Months, Years Linear principal repayment installment Weeks, Months, Years Bullet installment Weeks, Months, Years Revolving credit line Months Non-revolving credit line Months Interest rate type Calculation type Available rate types Pay-day loan Fixed Annuity installment Fixed, Floating Linear principal repayment installment Fixed, Floating Bullet installment Fixed, Floating Revolving credit line Fixed, Floating Non-revolving credit line Fixed, Floating Disbursement option Value Description Manual The operator initiates the disbursement manually Automatic The system initiates the disbursement automatically Available payment frequency options Value Description Fixed-term loan Weekly / Fortnightly (every two weeks) / Monthly / Quarterly Credit line Monthly Document signing Parameter Description Type Required Possible Values Default Notes Contract template Contract template used to generate the agreement Dropdown Yes List of uploaded templates of type “Contract template” – – Amendment agreement template Amendment agreement template Dropdown No List of uploaded templates of type “Amendment agreement template” – – Signing option Method of contract signing by the borrower Dropdown Yes See table below – – Signing option Value Description E-signature Electronic signature (PandaDoc) OTP Signing with a one-time password Outside the system Signing outside the system (offline) Decision making Parameter Type Required Possible Values Default Notes Verification Dropdown Yes See table below None If collateral is requested in the application form, the value must be “Manual” Underwriting Dropdown Yes See table below – – Scoring providers Multiple selection Yes See table below – – Internal scoring model Dropdown Yes (if the “Internal” provider is selected) List of available models – Displayed only when the “Internal” provider is selected GiniMachine scoring model Dropdown Yes (if the “GiniMachine” provider is selected) List of available GiniMachine models – Displayed only when the “GiniMachine” provider is selected Credit bureau Dropdown No See table below – Available values depend on the borrower type Verification Value Description Manual The operator verifies the borrower’s data manually None No additional verification Underwriting Value Description Manual The operator makes the decision manually Semi-auto The system generates a recommendation based on the scoring results, the operator confirms Auto The system makes the decision without operator involvement based on the scoring results Scoring providers Value Description Internal Built-in scoring model of the system GiniMachine External scoring service GiniMachine Credit bureau Value Description Equifax Equifax credit bureau (available only for individual borrowers) Application form Configuration of borrower application requirements when submitting a loan application. Parameter Type Required Default Notes Request bank statement Yes/No No Off – Request utility bill Yes/No No Off – Request loan purpose Yes/No No Off – Request financial statement Yes/No No Off – Request profit and loss statement Yes/No No Off – Request balance sheet Yes/No No Off – Request collateral Yes/No No Off When this option is enabled, the verification strategy must be “Manual”. A custom field builder for the collateral form is also displayed Request further info Yes/No No Off When enabled, a custom field builder for the additional information form is displayed Collection Parameter Type Required Possible Values Default Notes Collection strategy Dropdown Yes See table below – – Overdue days before the collection starts Number Yes (if the strategy is not “No collection process needed”) From 0 to 365 0 Displayed only if a collection strategy other than “No collection process needed” is selected Collection strategy Value Description No collection process needed The collection process is not triggered Default collection Standard collection process Loan calculator parameters Parameter Type Required Possible Values Default Notes Minimum loan amount for the group Number Yes From 0.01 to 99,999,999.99 – Cannot be greater than the maximum amount Maximum loan amount for the group Number Yes From 0.01 to 99,999,999.99 – Cannot be less than the minimum amount. Cannot be less than the amount selection step Amount selection step Number Yes From 1 – Cannot exceed the maximum amount Minimum loan term Number Yes From 1 to 999 – Cannot be greater than the maximum term. For credit lines: the minimum term in days cannot be less than the “Drawdown freeze” parameter Maximum loan term Number Yes From 1 to 999 – Cannot be less than the minimum term Term selection mode Toggle Yes See table below Fixed step Displayed only for the “Fixed-term loan” loan type Predefined term options List of values Yes (if selection mode is “Predefined options”) Numbers in the range from Min term to Max term – Displayed only when the “Predefined options” mode is selected Interest rate (for fixed rate) Number (%) Yes From 0 to 999 – Annual rate for instalment loans, daily rate for Pay-Day Loan. Used to calculate preliminary conditions on the calculator Margin (for floating rate) Number (%) Yes (for floating rate) From 0 to 999 – Displayed only when the interest rate type is “Floating”. Used to calculate the floating rate Interest rate (for floating rate) Number (%) – – – Read-only field. Displayed only when the interest rate type is “Floating” Term selection mode Value Description Fixed step Free selection: the borrower selects any value in the range from the minimum to the maximum term Predefined options Predefined options: the borrower selects from a defined set of fixed terms ### Editing a product group Source: https://docs.hesfintech.com/loanbox/product-groups-and-products/editing-a-product-group/ Editing a product group Process Editing a product group is available to users with the Credit Officer role. Step 1. Opening the editing form The user clicks the button to edit a product group. The system displays the “Edit product group” form. Step 2. Filling in parameters The user edits all required fields of the form. Step 3. Saving The system validates the data while the fields are being edited. If all fields are filled in correctly, the “Save” button becomes active. If errors are found, the system displays error messages next to the corresponding fields. When a user clicks the “Save” button, the system saves the updated product group. Result: the product group is updated. ### Product group list and filters Source: https://docs.hesfintech.com/loanbox/product-groups-and-products/product-group-list-and-filters/ Product group list and filters Screen purpose The screen displays a list of all product groups in the system. It is available to users with the Credit Officer, Underwriter and Collection Manager roles. Table columns Column Description Name Product group name (serves as a link to the group card) Status Product group status (Active / Inactive) Filters Filter Description Type Search Search by group name Text field Status Filter by group status (active, inactive) Yes/No Amount Filter by amount (finds products whose amount range includes the specified value) Number Term Filter by term (finds products whose term range includes the specified value) Number Sorting and actions Default sorting: by product name in alphabetical order. Pagination is supported. Available actions: navigate to the product group card (click on a row). ### Creating a product Source: https://docs.hesfintech.com/loanbox/product-groups-and-products/creating-a-product/ Creating a product Process Creating a product is available to users with the Credit Officer role. A product is always created within a specific product group. Step 1. Navigating to creation The user opens the product group card and clicks the “Create product” button. The system opens the product creation form, indicating the parent group. Step 2. Filling in parameters The user fills in all required fields of the form (described below in Product parameters). The set of visible fields depends on the parent product group’s settings (loan type, interest rate type, calculation type). Step 3. Saving The system validates the data while the fields are being filled in, including verifying that the product’s ranges fall within the group’s ranges. If all fields are filled in correctly, the “Save” button becomes active. If errors are found, the system displays messages next to the corresponding fields. When a user clicks the “Save” button, the system saves the created product. Result: the product is created and is active by default (the “Active” flag is on). Product parameters General info Parameter Type Required Possible Values Default Notes Active Yes/No No On / Off On – Product name Text Yes Free text – Maximum 20 characters. Must be unique within the group Payment frequency Dropdown Yes Values from the frequency list configured in the parent product group – Hidden if the group’s calculation type is Pay-Day Loan Product description Text No Free text – Maximum 255 characters Amount Parameter Type Required Possible Values Default Notes Minimum loan amount Number Yes From 0.01 – Cannot be less than the group’s minimum amount. Cannot be greater than the group’s maximum amount. Cannot be greater than the product’s maximum amount Maximum loan amount Number Yes From 0.01 – Cannot be less than the group’s minimum amount. Cannot be greater than the group’s maximum amount. Cannot be less than the product’s minimum amount. Must be strictly greater than the establishment fee Term Parameter Type Required Possible Values Default Notes Minimum loan term Number Yes From 1 – Cannot be less than the group’s minimum term. Cannot be greater than the group’s maximum term. Cannot be greater than the product’s maximum term. The unit of measurement is inherited from the group Maximum loan term Number Yes From 1 – Cannot be less than the group’s minimum term. Cannot be greater than the group’s maximum term. Cannot be less than the product’s minimum term. The unit of measurement is inherited from the group Rates The set of fields depends on the group’s interest rate type: fixed rate and floating rate. Fixed rate Parameter Type Required Possible Values Default Notes Minimum interest rate Number (%) Yes From 0 – Cannot be less than the group’s interest rate. Cannot be greater than the product’s maximum rate. Annual rate for instalment loans, daily rate for Pay-Day Loan Maximum interest rate Number (%) Yes From 0 – Cannot be less than the product’s minimum rate. Annual rate for instalment loans, daily rate for Pay-Day Loan Default interest rate Number (%) Yes From 0 to 999 – Annual default rate for instalment loans, daily rate for Pay-Day Loan. Has only fixed interest rate logic Floating rate Parameter Type Required Possible Values Default Notes Minimum product margin Number (%) Yes From 0 – Cannot be less than the group’s margin. Cannot be greater than the product’s maximum margin. Used to calculate the floating rate Maximum product margin Number (%) Yes From 0 – Cannot be less than the product’s minimum margin Minimum interest rate Number (%) – – – Read-only field Maximum interest rate Number (%) – – – Read-only field Default interest rate Number (%) Yes From 0 to 999 – Has only fixed interest rate logic Fees Parameter Type Required Possible Values Default Notes Overdue penalty Number Yes From 0 to 9,999,999,999,999.99 – – Establishment fee Number Yes From 0 0 Must be strictly less than the product’s maximum amount Service fee Number (%) Yes From 0 to 99.99 – – Early repayment fee Number (%) Yes From 0 to 99.99 0 Displayed only for fixed-term loans (not for credit lines) Grace period Parameter Type Required Possible Values Default Notes Grace period, days Number (days) Yes From 0 to 99,999 0 If the value is 0, there is no grace period Daily grace interest rate Number (%) Yes From 0 to 999 0 – ### Product list and filters Source: https://docs.hesfintech.com/loanbox/product-groups-and-products/product-list-and-filters/ Product list and filters Screen purpose The screen displays a list of all products in the system. It is available to users with the Credit Officer, Underwriter and Collection Manager roles. Table columns Column Description Product name Product name (serves as a link to the product card) Status Product status (Active / Inactive) Filters Filter Description Type Search Search by product name Text field Status Filter by status (active, inactive) Yes/No Amount Filter by amount (finds products whose amount range includes the specified value) Number Term Filter by term (finds products whose term range includes the specified value) Number Sorting and actions Default sorting: by product name in alphabetical order. Pagination is supported. Available actions: navigate to the product card (click on a row). ### Editing a product Source: https://docs.hesfintech.com/loanbox/product-groups-and-products/editing-a-product/ Editing a product Process Product editing is available at any time to users with the Credit Officer role. Any modifications will apply exclusively to newly created loan applications and loans. Existing loans will continue to operate under the product conditions effective at the time of their creation, as HES LoanBox adheres to the product snapshot principle. Step 1. Navigating to editing The user opens the product card and clicks the “Edit” button. The system opens the product editing form indicating the parent group. Step 2. Editing parameters The user edit all required fields of the form. The set of visible fields depends on the parent product group’s settings (loan type, interest rate type, calculation type). Step 3. Saving The system validates the data while the fields are being edited, including verifying that the product’s ranges fall within the group’s ranges. If all fields are filled in correctly, the “Save” button becomes active. If errors are found, the system displays messages next to the corresponding fields. When a user clicks the “Save” button, the system saves the updated product. Result: the product is updated and is active by default (the “Active” flag is on). ### Overview Source: https://docs.hesfintech.com/loanbox/customer-onboarding-and-application-process/ Overview and definitions This document covers how a loan application is created and submitted on the LoanBox platform. It covers three questions: What is Customer onboarding / the Application process in the system. Ways to submit an application (Borrower Portal, Back Office, Agent Portal, Agent invitation to a lead). The detailed, end-to-end flow of the application submission process, including every step, check, integration, and form field, with notes on which fields appear depending on product group settings and borrower type. Throughout this document: Product group is the system’s name for a configurable lending offering. A product group defines which loan types, amounts, terms, forms, documents, and additional data blocks are used for applications made under it (see the Product groups and products page). Borrower type is either Individual (a natural person) or Legal Entity (a company). The platform is configured per deployment for one type only. ### Application process Source: https://docs.hesfintech.com/loanbox/customer-onboarding-and-application-process/what-is-customer-onboarding/ Customer onboarding / Application process Definition Customer onboarding (the application process) is the set of steps that capture a customer’s loan request and collect all the data the system needs before the request is handed to origination for a credit decision. It starts when someone opens the “apply for a loan” flow and ends when the customer (or operator) confirms the prepared loan conditions. From that point, the application is handed over to the origination process. Purpose The application process has one goal: intake. It collects all information required to evaluate the loan, namely identity, contact details, address, financial data, bank account, and—if the product group requires them—collateral details and any additional information. Key characteristics The process is the same regardless of channel. The same product groups, forms, and data collection logic apply in the Borrower Portal, the Back Office, the Agent Portal, and when the application is started from an agent invitation to a lead. Up to three parties can be involved: a customer (the borrower), an operator (back-office or agent user who initiates the application on behalf of the customer), and optionally an agent attached to the deal. The application has a single human-readable application number that identifies it across all channels and status changes. The application times out: if the customer or operator does not submit the initial loan calculator step within 48 hours, the application is automatically canceled. Starting a new application automatically closes any still-open application the same borrower had from a previous attempt. High-level flow The customer (or an operator on their behalf, or a lead invited by an agent) chooses a product group and opens the application flow. The system checks that the customer is not on the blacklist and does not already have an active application. The customer (or operator) chooses the loan amount, term, and payment frequency on a loan calculator. The customer (or operator) fills in personal/company data, identity documents, address, employment or financial information, and bank account. The system runs an identity check (KYC) and verifies the bank account via open banking. If the product group requires them, the customer (or operator) adds collateral details and/or any extra information requested by the product group. The customer (or operator) reviews and confirms the loan conditions and, if requested by the product group, attaches the required supporting documents. The application is handed over to the origination process for decisioning. ### Submitting an application Source: https://docs.hesfintech.com/loanbox/customer-onboarding-and-application-process/ways-to-submit-an-application/ Submitting an application There are four entry points that lead to the same application intake process. The resulting application goes through the same data collection logic. Channel Who initiates Typical purpose Borrower Portal The customer, logged into their own portal Self-service application submission Back Office A back-office operator (Credit Officer) Taking an application on the customer’s behalf (for example, over the phone or in a branch) Agent Portal A partner agent logged into the agent portal Taking an application on the customer’s behalf, with the agent recorded on the deal Agent invitation to a lead An agent invites an existing lead; the lead then completes the application themselves on the Borrower Portal Pre-qualifying a potential customer and letting them finish the application online Key differences at a glance Aspect Borrower Portal Back Office Agent Portal Agent invitation to a lead Who logs in Customer Credit officer Agent Agent sends the invite — Customer completes the application How the customer is identified The logged-in user is the customer Operator enters the customer’s phone or email; if a user with that contact does not exist, it is created Operator enters the customer’s phone or email; if a user with that contact does not exist, it is created Agent picks or creates a lead with first name, last name, phone, and email; the system creates (or reuses) a borrower user from the lead’s phone or email Agent association No agent No agent Agent is automatically set to the logged-in agent’s partner organisation Agent is the one assigned to the lead First screen Choose a product group Choose a customer, then choose a product group Choose a customer, then choose a product group Agent screen: Send a loan application for a lead (product group + suggested loan amount); the lead later picks up the Borrower Portal flow Who fills in the application forms The customer The operator The operator The customer (lead), on the Borrower Portal, after following the invitation All four channels invoke the same application intake process: initial eligibility checks → loan parameters → customer/company data → KYC → bank account verification → (collateral, further info if required) → loan conditions confirmation → handover to origination. ### Submission by channel Source: https://docs.hesfintech.com/loanbox/customer-onboarding-and-application-process/submission-process-per-channel/ Submission process per channel The detailed description below follows the user journey step by step. The same underlying pipeline runs for every channel; differences are called out inline. Product group settings that affect the journey Every product group has settings that determine which fields and steps the customer sees during intake. The main intake-relevant settings are: Product group setting Effect on the application flow Loan type (Fixed-term loan or Credit line) Drives which payment frequencies are offered and which loan management flow runs after approval. Calculation type For fixed-term: PDL, Annuity installment, or Linear principal repayment installment. For credit line: Revolving credit line or Non-revolving credit line. Affects the calculator behaviour and the conditions shown for confirmation. Interest rate type (Fixed or Floating) If floating, the interest rate is shown as “prime rate + margin”. If fixed, the interest rate is taken as is. Amount and term ranges (min/max amount, min/max term, amount selection step, term selection mode) Drives the sliders on the loan calculator: min/max, step, and whether the term is chosen from a fixed-step slider or from a predefined list. Available payment frequencies Populates the payment frequency selector on the loan calculator. If only one option is configured, the control is hidden. Credit bureau provider (Equifax for individuals; none for legal entities) When Equifax is selected, the National ID field becomes visible on the personal details form (the bureau itself runs in origination). Application form—Supporting documents (Request Bank Statement / Utility Bill / Financial Statement / P&L Statement / Balance Sheet) Each is a toggle on the product group. If any of them is on, a “Supporting documents” block is displayed on the Confirm Loan Conditions step. Application form—Request Loan Purpose If on, a “Loan purpose” dropdown is shown on the Confirm Loan Conditions step. Application form—Request Collateral (and the dynamic collateral form) If on, the customer sees a “Provide collateral info” step with collateral type, registration details, description, supporting documents, and any additional collateral fields defined by the product group. If off, the step is skipped. Application form—Request Further Info (and the dynamic further information form) If on, the customer sees an additional “Provide further info” step that renders the fields configured on the product group. If off, the step is skipped. The deployment also has one system-wide setting that affects intake: the borrower type (Individual or Legal Entity). Every customer that uses the platform is treated as the configured type; the data collected differs accordingly. Step 1. Starting the application (Channel-specific entry) The starting screen differs per channel. Borrower Portal — “Choose a campaign” a. Open the application flow. The logged-in customer selects “Apply for a loan”. The screen shows the active product groups in the system. b. Choose a product group. The customer picks one product group. The system: Records the chosen product group on the new application. Sends a “cancel previous not-finished applications” signal to close any half-started application from a previous attempt. Back Office — “Choose borrower” a. Open the “new application” screen. A Credit Officer clicks the button to create a new application. The system displays the “Create new application” form. b. Enter the customer’s contact. The operator enters the customer’s phone number or email (matching the system’s authentication method). If the system does not yet have a user for that contact, a new customer user is created; otherwise the existing one is used. c. Choose a product group. The operator selects one of the active product groups. d. Start the application. The system closes any previous not-finished application for that customer and starts a new one. Agent Portal — “Choose borrower” a. Open the “new application” screen. An Agent clicks the button to create a new application. The system displays the “Create new application” form. b. Enter the customer’s contact. The operator enters the customer’s phone number or email. The system creates a customer user if one does not exist, otherwise reuses the existing one. c. Choose a product group. The operator selects one of the active product groups. d. Start the application. The system attaches the logged-in agent’s partner organisation to the application automatically, closes any previous not-finished application, and starts the new one. Agent Invitation to a Lead This channel lets an agent invite a lead the agent has already captured in the system. Once the invitation is accepted the lead continues the application on the Borrower Portal. a. Create or open the lead. The agent opens the “Lead” screen in the Agent Portal. If the lead does not yet exist, the agent creates one by entering first name, last name, phone, and email. If the lead already exists, the agent opens it. b. Open “Send loan application” for the lead. On the lead’s card, the agent clicks the “Send loan application” action. The system shows a form with the lead’s full name at the top and the lead’s basic info below. c. Choose a product group and a suggested loan amount. The agent picks one product group from the list of active product groups available for their agent organisation and types a Suggested loan amount (validated against the product group’s min/max amount). d. Send the invitation. On “Send”, the system: Looks up or creates a Borrower Portal user for the lead using the lead’s phone (if the deployment authenticates by SMS) or email (if it authenticates by email). If the user does not exist, a new one is created and, for email deployments, a temporary password is generated. Sends a “lead invitation” notification containing a link the lead can use to sign in to the Borrower Portal and the chosen product group and suggested loan amount attached to their session. e. The lead opens the Borrower Portal. The lead clicks the invitation link, authenticates, and is placed directly into the Borrower Portal application flow. The product group is already chosen and the suggested loan amount is already pre-filled. The lead then proceeds through the same steps as any other Borrower Portal customer (eligibility pre-checks → loan calculator → data collection → confirm loan conditions). Step 2. Eligibility pre-checks Before the loan calculator is shown, the system checks two things: Blacklist check on the contact. The phone number (if the system authenticates by SMS) or the email (if the system authenticates by email) is checked against the blacklist. If it is on the blacklist, the application cannot proceed. The customer (or operator) sees a short “sorry, you cannot apply for a loan” screen and the application ends. Active application check. The system checks whether the customer already has an open (not closed) application. If they do, the customer sees an “already has an active application” screen and the new application ends. An application is considered “active” when it has been started by the borrower (or on their behalf) and has not yet reached a terminal (closed) state. In practice the check catches applications in any of the following statuses: Status When the application is in this status (Intake in progress — no status yet) The previous attempt reached the loan calculator, data collection, or the Confirm Loan Conditions step but has not been submitted to origination yet. Account verification The previous application was submitted to origination and is running automatic checks. Verification The previous application is waiting for a manual Verifier review. Update requested The previous application was returned to the initiator for updates. Underwriting The previous application is waiting for a manual Underwriter decision. Applications that have already been Approved, Declined (with a decline code), Canceled (with a cancel code), Disbursed, or marked Error are no longer active and do not block a new application. Step 3. Loan calculator The customer (on the Borrower Portal) or the operator (in Back Office and Agent Portal) sees a loan calculator form pre-filled with the product group’s parameters. The form looks the same on all portals, with only the form variant differing. Fields on the loan calculator: Field Description Type Required Possible values Notes Product group Name of the chosen product group Text — — Read-only Loan amount Requested loan amount Number (slider) Yes Between the product group’s min and max amount, stepped by the configured step Currency suffix from deployment settings. When a pre-calculated “suggested loan amount” is passed in (e.g., from an agent invitation to a lead), the slider is hidden and the suggested amount is used. Term Requested loan term Number (slider) or Radio button Yes When term selection mode is “Fixed step”: free slider between min and max term. When term selection mode is “Predefined options”: radio list of predefined term lengths. Period suffix matches the product group’s term period (e.g., months, days). Payment frequency How often repayments are due Radio button Yes Options come from the product group’s available payment frequencies (see values below) Hidden automatically if the product group has only one payment frequency configured. Agent Assigned partner/agent Object (read-only) — — Shown on the Agent Portal, when an agent is present on the Borrower Portal (for example, from an agent invitation), and on the Back Office when assigned. Payment frequency values (from the product group configuration): Value Meaning Weekly Every 7 days Fortnightly Every 14 days Monthly Monthly Quarterly Every 3 months Fixed-term product groups can use any of the four. Credit line product groups only offer Monthly. Completion of this step: On submit, the system creates a new application record with the chosen amount, term, payment frequency, product group, and (if present) agent. If the customer does not submit this form within 48 hours, the application is automatically canceled. Step 4. Borrower information collection From this point on, the flow splits by borrower type (Individual or Legal Entity). The system-wide setting determines which sub-flow runs. Individual borrower (person) flow a. System looks up or creates the customer record. Depending on whether the system authenticates by phone (SMS) or email, the system finds an existing person by that contact or creates a new one. b. Identity verification (KYC). The system runs an identity check. Depending on the system KYC configuration, this is done automatically through an external provider (Jumio or Ondato) or manually by an operator. The check enriches the customer record with first name, last name, date of birth, and ID document details. If the identity check is rejected, the application ends. c. Bank account verification. The system verifies the customer’s bank account depending on the system Bank account verification configuration. This is done automatically through an open banking provider (Flinks, Plaid, or Illion) or manually by an operator. Bank account details are saved on the customer. d. Provide address. The customer (or operator) fills in the residential address. Field Type Required Notes Formatted address / Country / Postal code / Street / City / State / Apartment Text fields, possibly auto-completed Yes (address provider dependent) Input method depends on the configured address provider: manual input, OpenStreetMap, or Google Maps. e. Provide personal details. Field Type Required Notes Tax number Text Yes Email Text Yes Shown only when the system authenticates by phone (email is asked here because it was not captured at login). Phone Phone number Yes Shown only when the system authenticates by email. Citizenship Dropdown (countries) Yes National ID Text Yes (conditional) Shown only when the product group uses Equifax as the credit bureau provider, or when the borrower already has a value. Marital status Dropdown Yes Values come from the deployment’s marital status list. Education Dropdown Yes Values come from the deployment’s education list. Monthly income Number with currency suffix Yes Must be between 0 and 100,000,000 with up to two decimals. Has vehicle Yes/No No Default: No. Has property Yes/No No Default: No. After submission, the system runs a first blacklist check on the person using phone, email, full name + date of birth, and ID document number. A match terminates the application. f. Provide employment information. All fields are collected inside the employment block of the customer profile. Field Type Required Notes Employer legal name Text Yes Employer phone Phone Optional (form-dependent) Employer website Text Optional (form-dependent) Industry sector Dropdown Yes From the deployment’s industry list. Position Dropdown Yes From the deployment’s position list. Length of employment Dropdown Yes From the deployment’s length-of-employment list. Employer address Address block Yes (address provider dependent) Same providers as the residential address field. From this form the customer can navigate back to the personal details step. When they come back, the personal details are preserved. After submission, the system runs a second blacklist check on the person (same checks as before) to catch values changed during the edit. A match terminates the application. The person record is then saved. Legal entity borrower flow a. System looks up or creates the legal entity record. The system finds the existing legal entity or creates a new one based on phone/email lookup. b. Provide company information. Field Type Required Notes Company full name (trading name) Text Yes Legal name Text Yes Official registered name. Corporate type Dropdown Yes Values come from the deployment’s corporate type list (e.g., C-Corp, S-Corp, LLC, etc.). Industry Dropdown Yes From the deployment’s industry list. Registration number Text Yes Registration date Date Yes Cannot be in the future. Tax number Text Yes Email Email Yes Website Text No Company address Address block Yes (address provider dependent) Annual revenue Number with currency suffix Yes Between 0 and 1,000,000,000. After submission, the system runs a first blacklist check on the legal entity using phone, email, and tax number. A match terminates the application. c. Identity verification (KYC) on the company representative. The system runs KYC on the authorized representative of the company (automatically or manually) depending on the system KYC configuration. If rejected, the application is terminated. d. Provide the company’s representative info. The operator fills in representative details (position and personal information of the authorized representative) based on the KYC-verified person. e. Provide bank information. Bank account details of the company are entered. From this form the user can navigate back to the representative info step. When they come back, representative data is preserved. After submission, the system runs a second blacklist check on the legal entity. A match terminates the application. The legal entity record is then saved. Step 5. Provide collateral info (conditional) This step is shown only when the product group’s “Request Collateral” setting is on. Otherwise, the system moves directly to the next step. Field Type Required Notes Collateral type Dropdown No (server-side rules apply) Values come from the deployment’s collateral type list. Registration number Text No Up to 255 characters. Registration date Date No Description Long text No Up to 3,000 characters. Supporting documents File upload No Up to 5 image files, 20 MB each. Item-specific fields Varies Varies A dynamic sub-form configured on the product group; its fields, types, and validations are defined by the product group administrator. Note When the product group requires collateral, its Verification decision-making must be set to Manual. This is a product group configuration rule. Step 6. Provide further info (conditional) This step is shown only when the product group’s “Request Further Info” setting is on. Otherwise, the system moves directly to the next step. The fields on this screen are fully dynamic—they are defined by the product group administrator on the product group’s “Further information form” and can include any mix of text, number, date, dropdown, checkbox, and file upload fields. Their labels, types, and validation rules are entirely product-group-specific. Step 7. Confirm loan conditions This is the last step of the intake. The customer (or operator) reviews the conditions they are about to submit and, if the product group has requested any supporting documents, attaches them here. Submitting this screen hands the application over to origination. The screen is organized into two blocks: Requested conditions (always shown) and Supporting documents (conditional on product group settings). Requested conditions block (always shown) Field Description Type Required Default Notes Loan amount The amount requested Number Yes Taken from the loan calculator step Must stay within the product group’s min/max amount. Currency suffix from deployment settings. Loan term The term requested Number Yes Taken from the loan calculator step Must stay within the product group’s min/max term. Period suffix comes from the product group’s term period (days, months, etc.). Loan purpose Reason for taking the loan Dropdown Yes — Shown only when the product group has “Request Loan Purpose” on. Values come from the deployment’s loan purpose list (filtered by borrower type). First payment date The date of the first repayment Date picker Yes — Shown only when the product group has “Configurable first payment date” on AND the product is not a PDL and not a Credit line. The selectable range starts 3 days from today and extends up to the product group’s configured “Range of days for first payment date”. Payment frequency How often repayments are due Dropdown Yes Taken from the loan calculator step Shown only when the product group has “Configurable first payment date” on AND the product is not a PDL and not a Credit line. Values come from the product group’s available payment frequencies. An “Apply” button at the bottom submits the step and hands the application to origination. Supporting documents block (conditional) The supporting documents block appears only when at least one of the following document requests is enabled on the product group: Request Bank Statement Request Utility Bill Request Financial Statement Request P&L Statement Request Balance Sheet If none of these are enabled, the block is hidden and Step 7 contains only the Requested Conditions fields above. When the block is displayed, it shows a file-upload control for each document type enabled on the product group. A control for a document type is only shown if that specific request is enabled (or if the customer has already uploaded a file of that type on a previous attempt). Upload Appears when Required Notes Bank statement Product group has “Request Bank Statement” on Yes Image/file upload, up to 20 MB per file. The number of files is capped by the deployment’s per-field attachment limit. Utility bill Product group has “Request Utility Bill” on Yes Image/file upload, up to 20 MB per file. The number of files is capped by the deployment’s per-field attachment limit. Financial statement Product group has “Request Financial Statement” on Yes Image/file upload, up to 20 MB per file. The number of files is capped by the deployment’s per-field attachment limit. P&L statement Product group has “Request P&L Statement” on Yes Image/file upload, up to 20 MB per file. The number of files is capped by the deployment’s per-field attachment limit. Balance sheet Product group has “Request Balance Sheet” on Yes Image/file upload, up to 20 MB per file. The number of files is capped by the deployment’s per-field attachment limit. Completion of this step: On “Apply”, the application moves out of the intake phase and is handed over to origination (the decisioning process). On the Borrower Portal, the customer is then placed on a read-only “application is being processed” view that refreshes automatically and lets the customer cancel the application at any time. Cancellation during intake During the intake phase the application can be canceled in the following cases. Cancellations that happen later (during origination) are not covered here. Cause When Customer closes the application from the Borrower Portal tracking view Any time after the loan calculator is submitted, until origination has started manual processing Customer did not complete the loan calculator within 48 hours During the loan calculator step Customer had an active application or was on the blacklist at start At the “eligibility pre-checks” step Customer was added to the blacklist during data collection During data collection ### Overview Source: https://docs.hesfintech.com/loanbox/loan-origination-process/ Overview This document describes the Loan Origination process — the underwriting and decisioning stage of a loan application on the platform. It runs after the borrower has submitted the application and before contract signing. It explains what the process does, how its flow changes depending on the borrower type (individual person vs legal entity) and the product group settings (verification mode and underwriting mode), and lists every task that the back-office staff and the borrower see during the process, together with all fields available on those tasks. ### How it works Source: https://docs.hesfintech.com/loanbox/loan-origination-process/what-is-the-loan-origination-process/ What is the loan origination process Definition The Loan Origination process is the stage at which the platform decides whether the loan application can be approved, declined, or canceled. It is performed after the borrower has fully filled in the application (this is done by a separate, earlier stage called the Application process). By the time the Loan Origination process starts, all borrower information, supporting documents, and bank account details have already been collected. Purpose The process is responsible for: Running automated checks (financial data retrieval, credit bureau report, stop-factor controls). Letting a back-office verifier review the application (when configured). Calculating the credit limit, selecting a suitable loan product, and scoring the application. Letting a back-office underwriter make the final credit decision (when configured). Approving the application with final loan terms or declining/canceling it. Calculating the repayment schedule once the application is approved. Sending the borrower a notification with the outcome (approved, declined, or canceled). Key characteristics Runs after the borrower has submitted all data — it never collects new application data from the borrower (except in the “request updates” loop, see below). The exact set of steps depends on who the borrower is (a person or a legal entity) and on the product group settings for verification, underwriting, decision making, and credit bureau. The borrower can monitor the application status in their portal during the entire process and may cancel the application at any point. The process always ends with one of three outcomes: Approved, Declined, or Canceled. ### What determines the process Source: https://docs.hesfintech.com/loanbox/loan-origination-process/what-determines-the-process/ What determines the process Two inputs drive the variations in the flow: the borrower type and the product group settings for decision making. Borrower type Value Description Person The applicant is an individual (a natural person). Legal entity The applicant is a company (a business client). The platform automatically routes the application to the corresponding origination flow based on this value. Product group settings (Decision making) Each product group defines settings that change how the process behaves. Credit bureau This setting controls whether the system initiates a credit bureau request or not. Value Description Empty The system doesn’t initiate a request to the credit bureau. Equifax The system initiates a request to the credit bureau (Equifax), if the client has a signed agreement with Equifax. Verification This setting controls whether a back-office verifier must review the application before it is scored. Value Description Manual A verifier must open the application in the back-office and either approve it, request updates from the borrower, or decline it. None The verification step is skipped entirely; the application proceeds directly to scoring (and, for legal entities, to the financial data step). Underwriting This setting controls whether an underwriter must make the final decision on the application. Value Description Auto The system decides automatically. If a suitable product is found, the application is auto-approved on the requested terms. If no product is found, the application is automatically declined. Semi-auto The system auto-approves only the safest cases (top scoring zone with a product found). Everything else is sent to an underwriter for a manual decision. Manual The application is always sent to an underwriter for a manual decision, regardless of the score or whether a product was found automatically. How the settings combine The decision after scoring is calculated as follows: Underwriting setting Scoring result Product auto-selected Outcome Auto Top zone Yes Auto-approved (no underwriter) Auto Top zone No Auto-declined (“no suitable products were found”) Auto Middle zone Yes Auto-approved (no underwriter) Auto Middle zone No Auto-declined (“no suitable products were found”) Semi-auto Top zone Yes Auto-approved (no underwriter) Semi-auto Top zone No Sent to underwriter Semi-auto Middle zone Any Sent to underwriter Manual Any Any Sent to underwriter Top zone = the lowest-risk scoring band. Middle zone = the medium-risk scoring band. The exact thresholds are configured separately for each product group. ### Step-by-step Source: https://docs.hesfintech.com/loanbox/loan-origination-process/step-by-step-description/ Step-by-step description The steps below cover both borrower types. Differences specific to Legal Entity borrowers are explicitly marked. Step 1. Start of the Loan Origination process What happens: The borrower has already submitted the full application in the previous stage. The platform now sets the application status to Account verification and starts the origination flow. The borrower portal shows the application as pending — the borrower can open it, see the requested loan conditions, and cancel it at any time. Step 2. Borrower sees the tracking screen A read-only tracking screen appears in the borrower portal automatically. It refreshes every 10 seconds, so the borrower always sees the current status. The tracking screen contains: The status of the application. The requested conditions (amount, term). The list of supporting documents. A note: “The final loan conditions in your contract may differ”. A Cancel application button (with a confirmation dialog: “Are you sure you want to cancel this application?” — Yes / Back). If the borrower clicks Cancel application at any moment, the process terminates with the cancel reason “Borrower canceled the application”. Step 3. Retrieve financial data What happens: The platform automatically pulls the borrower’s financial data from the connected open banking provider. No user action is required. If the open banking integration fails, the application is terminated as an error case. Step 4. Get the credit bureau report What happens: The platform automatically requests the credit bureau report for the borrower. No user action is required. Step 5. Run the stop-factor controls What happens: The platform runs an automated set of checks against blacklists, age limits, residency rules, etc. (the exact list depends on the system configuration). If any stop factor is triggered, the application is automatically declined. Step 6. Verification If the product group’s Verification setting is None, this step is skipped and the process moves on: For Person borrowers: directly to step 8 (Score the application). For Legal Entity borrowers: to step 7 (Provide financial data). If the setting is Manual, a back-office verifier opens the Verify the Application task. See the Tasks during the process page for the full list of fields available on this task. The verifier can choose one of three outcomes: Approve — the application moves on to the next step. For Person borrowers, the platform first records the current date as the collateral valuation date and then proceeds to scoring (step 8). For Legal Entity borrowers, the platform records the collateral valuation date and then opens the Provide financial data task (step 7). Request updates — the borrower is asked to update specific blocks of the application (see step 6a below). Decline — the application is declined immediately with one of the verification decline reasons. Step 6a. Update the application loop (only when the verifier selects “Request updates”) When the verifier requests updates, the following happens: The tracking screen in the borrower portal is dismissed. The borrower receives a notification: “Application returned for revision”. The borrower receives a new task in the portal called Update the application, with the message: “You need to update some of the fields in your loan application by [deadline], otherwise your application will be declined”. The deadline is set to 72 hours from the moment the verifier requested updates. The borrower edits the requested sections (only the sections selected by the verifier are unlocked) and submits. After submission, the platform re-runs the stop-factor controls (step 5) and returns to verification (step 6). If the borrower does not submit the update within 72 hours, the application is automatically declined. If the borrower clicks Cancel application on the update screen (with confirmation), the application is canceled. Step 7. Provide financial data If the borrower is a Legal Entity, a back-office verifier receives a task called Provide financial data. The verifier manually enters the company’s key financial figures (revenue, profit, total assets, etc.). See the Tasks during the process page for the full list of fields. After submission, the platform automatically: Saves the financial figures on the application. Calculates the profitability ratios (gross profit margin, net profit margin, operating profit margin, EBITDA margin, net worth to total assets, net debt to EBITDA). For Person borrowers, this step does not exist — the platform proceeds directly to scoring. Step 8. Score the application What happens: The platform automatically runs the scoring engine. The result is a scoring zone (top / middle) plus a score value. Step 9. Calculate the credit limit What happens: The platform automatically calculates how much credit can be approved for this borrower based on the configured limit-calculation rules. Step 10. Automatic product selection What happens: The platform tries to find a loan product that matches the borrower’s requested term, amount, and the calculated credit limit. The selected product (or no product) drives the next step’s outcome. Step 11. Underwriting decision (automatic) The platform decides what to do next based on the product group’s Underwriting setting and the scoring result (see the table on the What determines the process page). The result is one of: Auto-approve — the application is approved on the requested terms (see step 12). Send to underwriting — an underwriter must make the manual decision (see step 13). Reject — the application is automatically declined (this happens only in Auto mode when no product matches). Step 12. Auto-approval What happens: No user action. The platform sets the approved term equal to the requested term, then proceeds to the final approval steps (LTV calculation if there is collateral, prime rate, status set to Approved). Step 13. Make a decision on the application A back-office underwriter receives the Make a decision on the application task. See the Tasks during the process page for the full list of fields. The underwriter can choose: Approve — the underwriter sets the final loan amount, term, interest rate, first payment date (when configurable), and the loan product. The application then proceeds to the final approval steps (collateral / LTV, prime rate, status set to Approved). Decline — the underwriter selects a decline reason. The application is declined. Return to verifier — the underwriter returns the application back to the verifier for re-checking, providing a free-text reason (max 300 characters). This option is available only when the product group’s Verification setting is Manual. The flow returns to step 6. Step 14. Final approval and amortisation schedule When the underwriter approves (or when the application is auto-approved): If the application has collateral, the platform automatically calculates the loan-to-value (LTV) percentage. The platform stores the current prime rate on the application. The application status is set to Approved. The platform calculates the amortisation schedule (the list of repayment periods). The platform validates the amortisation schedule. If the schedule is invalid (interest exceeds payment in any period for non-credit-line, non-PDL products, or the amount to disburse is negative), the application is declined. The borrower is notified that the application is Approved (notification is sent to the borrower’s email and phone). The application then leaves the Loan Origination stage and continues into the contract-signing stage. ### Process tasks Source: https://docs.hesfintech.com/loanbox/loan-origination-process/tasks-during-the-process/ Tasks during the process This page lists every task that can appear during the Loan Origination process: when it appears, who sees it, and all fields available on it. 1. Verify the Application (back-office verifier) When it appears: Step 6, only when the product group Verification setting is Manual. Who sees it: Back-office users with the Verifier role. Task title in the back-office: Verify the Application #[application number]. The screen has two parts: a read-only summary of the application and a decision section. Read-only summary The verifier can review the application data through these tabs: Tab Contents General info Loan application general information (requested amount, term, product group, etc.). Borrower details Personal or company details of the borrower. Bank info Bank account information, including the bank account verification result. Attachments Supporting documents uploaded by the borrower. Collateral info Collateral details (this tab is editable, so any missing collateral fields can be filled in). Credit bureau The credit bureau report retrieved earlier in the process. A small header above the tabs shows: borrower name (clickable link to the borrower profile), Requested amount, and Requested term. If the application is being re-verified after an underwriter returned it, a read-only Return reason field is shown above the decision section. Decision section Parameter Description Type Required Possible values Default Notes Decision The verifier’s decision on the application. Radio (single choice) Yes See the Decision values table below. — Drives which extra fields are required next. Decline reason Reason for declining the application. Dropdown Yes when Decision = Decline See the decline reason lists below — different for Person and Legal Entity. — The list shown depends on the borrower type. Sections to update Which sections of the application the borrower must update. Dropdown (multi-select) Yes when Decision = Request updates See the sections-to-update lists below — different for Person and Legal Entity. — Only the selected sections are unlocked for the borrower. Request reason The reason for asking the borrower to update. Dropdown Yes when Decision = Request updates See the Request reason values list below. — Same list for both borrower types. Note Collateral validation on Approve: when the verifier selects Approve, the platform checks that all required collateral fields are filled in. If any are missing, a red warning is shown: “Unable to submit: Complete all required fields in the Collateral info section before proceeding”. Decision values Value Description Decline The verifier rejects the application. Request updates The verifier asks the borrower to correct or add information. Approve The verifier confirms the application can move forward. Decline reason values — Person borrower Wrong images Low income Low age Junk application Homeless Decline reason values — Legal Entity borrower Wrong images Low revenue Young company Junk application Sections to update — Person borrower Value Description Application info The general loan application data (amount, term, etc.). Personal info Borrower’s personal information. Personal details Additional personal details. ID document The borrower’s ID document. Address The borrower’s address. Employment info Employment information. Bank info Bank account information. Financial info Financial information. Collateral info Collateral information. Further info Additional borrower information. Supporting documents Uploaded supporting documents. Sections to update — Legal Entity borrower Value Description Application info The general loan application data. Company info The company’s information. Personal info Personal information of the contact person. ID document ID document. Company’s representative info Information about the company’s representative. Bank info Bank account information. Financial info Financial information. Collateral info Collateral information. Further info Additional information. Supporting documents Uploaded supporting documents. Request reason values The same list is shown for both borrower types: Incorrect ID number Poor image quality ID image and description do not match ID document expired Poor image quality of utility bill Poor image quality of Bank Statement Incorrect account number Update selected blocks Poor image quality of Registration Document 2. Provide financial data (back-office verifier) When it appears: Step 7, only for Legal Entity borrowers, immediately after verification (or, if verification is skipped, immediately after the collateral valuation date is set). Who sees it: Back-office users with the Verifier role. Task title in the back-office: Provide financial data #[application number]. The screen has the same read-only tabs as the verification screen (General info, Borrower details, Bank info, Attachments, Collateral info), plus the editable Financial data section. For Person borrowers, this step does not exist — the platform proceeds directly to scoring. Financial data fields All fields below are entered by the verifier from the company’s financial documents. Parameter Description Type Required Total sales The company’s total sales for the reporting period. Number Yes Operating profit The company’s operating profit. Number Yes Gross profit The company’s gross profit. Number Yes Total assets The company’s total assets. Number Yes Total liabilities The company’s total liabilities. Number Yes Revenue The company’s revenue. Number Yes Net income The company’s net income. Number Yes EBITDA The company’s EBITDA. Number Yes Net debt The company’s net debt. Number Yes After the verifier submits, the platform automatically calculates the following profitability ratios and stores them on the application. They are not entered by the user; they are derived from the figures above: Gross profit margin Net profit margin Operating profit margin EBITDA margin Net worth to total assets ratio Net debt to EBITDA ratio These ratios are later visible to the underwriter on the Profitability info tab of the underwriting screen. 3. Make a decision on the application (back-office underwriter) When it appears: Step 13, only when the underwriting decision must be made manually (the routing rules produced “Send to underwriting”). Who sees it: Back-office users with the Underwriter role. Task title in the back-office: Make a decision, Application #[application number]. The screen has three parts: a scoring header, a read-only summary in tabs, and a decision section. Scoring header Above the tabs, the underwriter sees: Result — a visual indicator of the scoring zone (top / middle). Score — the numeric score from the scoring provider (shown only when the scoring provider returned a score). Read-only summary (organised in tabs) Tab When it is shown Contents General info Always Loan application general information. Borrower details Always Personal or company details of the borrower. Bank info Always Bank account information and the bank account verification result. Attachments Always Uploaded supporting documents. Credit bureau Always The credit bureau report. Scoring Always Detailed scoring breakdown. Collateral info Only when the application has collateral Collateral details. Profitability info Only for Legal Entity borrowers with calculated profitability ratios Financial figures and the calculated profitability ratios. A small header above the tabs shows: borrower name (clickable link), Requested amount, and Requested term. Decision section Parameter Description Type Required Possible values Default Notes Decision The underwriter’s decision on the application. Toggle (single choice) Yes See the Decision values table below. — The Return to verifier option is available only when the product group’s Verification setting is Manual. Decline reason Reason for declining the application. Dropdown Yes when Decision = Decline See the decline reason lists below — different for Person and Legal Entity. — The list shown depends on the borrower type. Return reason Free-text explanation for returning the application to the verifier. Text area Yes when Decision = Return to verifier — — Maximum 300 characters. Loan amount The final approved loan amount. Number Yes when Decision = Approve — The borrower’s requested amount. Minimum 0.01; maximum 9,999,999,999,999.99. Currency suffix is the platform default currency. Loan term The final approved loan term. Number Yes when Decision = Approve — The borrower’s requested term. Minimum 1; maximum 1000. The unit (days / months / years) is taken from the product group. Approved interest rate The final approved interest rate (as a percentage). Number Yes when Decision = Approve — — Minimum 0; maximum 999. Suffix %. First payment date The date of the first repayment. Date Yes when Decision = Approve and the product group has “Configurable first payment date” turned on and the loan type is not Credit line or PDL — — Allowed range: from 3 days from today, up to 3 days plus the product group’s “Range of days for first payment date” setting. Loan product The specific loan product that will be applied to the application. Dropdown Yes when Decision = Approve The list is filtered live by the chosen amount, term, and interest rate, and by the application’s product group. — If the system pre-selected a product (and it still matches the underwriter’s chosen amount / term / rate), it is shown by default. The screen also displays calculated read-only fields under the loan term inputs, which refresh whenever the underwriter changes the amount, the first payment date, or the loan product: LTV — only shown when the application has collateral and the LTV is available. Total to pay — the total amount the borrower will repay over the life of the loan. Total interest — the total interest the borrower will pay. First payment — the value of the first scheduled payment (shown only when the product group has a configured payment frequency). A submit button labelled Submit is enabled only when all required fields for the chosen decision are valid. Decision values Value Description Decline The underwriter rejects the application. Approve The underwriter approves the application on the entered terms. Return to verifier The underwriter sends the application back to the verifier for re-checking. Available only when the product group requires manual verification. Decline reason values — Person borrower Not a resident Job instability Suspicion of fraud Existing non-performing loan Previous conviction Lives or works from abroad Declined applications in the last 30 days Incorrect data Decline reason values — Legal Entity borrower Not a resident Suspicion of fraud Incorrect data Declined applications in the last 30 days Existing non-performing loan 4. Update the application (borrower) When it appears: Step 6a, only after the verifier selected Request updates. Who sees it: The borrower (and back-office or agent users acting on behalf of the borrower — see “Where the form is shown” below). Task title in the borrower portal: Update the application #[application number]. The screen header shows the message: “You need to update some of the fields in your loan application by [deadline], otherwise your application will be declined”. The deadline is set automatically to 72 hours from the moment the verifier requested the updates. The screen displays the application in editable form, but only the sections selected by the verifier are unlocked. The rest are read-only. The available sections are: Requested conditions Personal info ID document Personal details Company info (Legal Entity only) Company’s representative info (Legal Entity only) Address Employment info (Person only) Bank info Financial info Collateral info Further info Supporting documents The screen has two action buttons: Submit — sends the updated application back to the verifier. Cancel application — opens a confirmation dialog (“Are you sure you want to cancel this application?” — Yes / Back). If confirmed, the application is canceled. If the borrower does not submit within 72 hours, the application is declined automatically. Where the form is shown The same Update the application task can be shown in three different portals depending on which portal originally submitted the application: Portal Who works there Borrower Portal The borrower fills in the update directly. Back Office Portal A credit officer fills in the update on the borrower’s behalf. Agent Portal An agent fills in the update on the borrower’s behalf. The fields and the behaviour are the same in all three portals. 5. Track verification status (borrower) When it appears: Throughout the entire Loan Origination process (until it ends), except while the borrower is filling in the Update the application task. Who sees it: The borrower. Task title in the borrower portal: Track verification status. This is a read-only screen that lets the borrower follow the progress of their application. It auto-refreshes every 10 seconds. The screen contains: Section Description Status The current application status: Account verification, Verification, Update requested, Underwriting, Approved, Declined, or Canceled. Requested conditions The amount, term, and other conditions the borrower requested. Supporting documents The list of documents the borrower previously uploaded. Note A reminder that the final loan conditions in the contract may differ from the requested ones. Cancel application button Opens the cancel confirmation dialog. Cancellation flow: the borrower clicks Cancel application, then confirms in the dialog (“Are you sure you want to cancel this application?” — Yes / Back). If confirmed, the application is canceled. ### Borrower notifications Source: https://docs.hesfintech.com/loanbox/loan-origination-process/notifications-for-the-borrower/ Notifications for the borrower During and at the end of the Loan Origination process, the platform notifies the borrower of the outcome through the following channels: Outcome Sent to Application approved Borrower’s email and phone Application declined (any decline reason) Borrower’s email Application canceled Borrower’s email Application returned for revision (only when the verifier requests updates) Borrower’s email and phone (Legal Entity flow) ### Overview Source: https://docs.hesfintech.com/loanbox/scoring-and-credit-decisioning/ Overview Every loan application is assessed by one or more scoring providers before a credit decision is made. HES LoanBox supports both the internal engine and the GiniMachine engine out of the box: Provider What it is Where the logic lives Internal A rule-based decision table (DMN) authored by the lender’s credit officer. Returns an internal rank. LoanBox — Settings, Scoring model GiniMachine A machine-learning model trained on the lender’s historical loan data. Returns a Probability of repayment, a resolution and a per-attribute explanation. The connected GiniMachine instance The provider outputs are not used directly. They are passed into a second decision table (Scoring result), which reconciles them into a single verdict called the Result Probability of repayment: green zone, grey zone, or red zone. The credit officer sees that verdict when making a decision. The providers are deliberately independent. The internal model encodes policy that the lender can read, audit, and change on demand. GiniMachine encodes patterns learned from the portfolio’s own repayment history. Running both means a lender gets a machine-learning signal without giving up a human-readable basis for the decision, and disagreement between the two becomes a routing signal rather than a problem. Scoring is configured in the Decision making block of the product group form, not globally. Two product groups on the same platform instance can use different providers and different GiniMachine models. ### Scoring providers Source: https://docs.hesfintech.com/loanbox/scoring-and-credit-decisioning/scoring-providers/ Scoring providers Scoring provider (definition) A scoring provider is a source of risk assessment for a loan application. HES LoanBox ships with two: Internal provider and GiniMachine. A third-party provider can be added as a customization: the integration is built into the platform, and the scoring decision table is extended so that the new provider’s output is reconciled with the others. A product group can be configured with one provider or several. When several are configured, all of them run. Internal provider The internal provider evaluates the application against the platform’s scoring model — a DMN decision table maintained by the lender’s credit officer under Settings > Scoring model. The platform always uses the active version of that model when scoring runs. Returns: an internal rank (a single letter, A to E) The rank scale is a platform convention; the rules that map borrower attributes to each rank are entirely lender-defined. The model is deterministic, fully readable in the decision table editor, and versioned with a full history of who changed what and when. A platform instance operates with a single borrower type — person or legal entity — and the scoring model is matched to that type. GiniMachine The GiniMachine provider sends the application to a trained model hosted on the connected GiniMachine instance. Returns: Output Description Model The name of the GiniMachine model that produced the result, for example, lb_person_scoring_9_columns. Recorded on the application. Probability of repayment The model’s numeric output for this application, for example, 0.8090. Can be in the green zone, grey zone, or red zone. Resolution The model’s verdict, shown in the interface as a label — Approve in the example above. It enters the Scoring result decision table as a boolean. Attribute effects Every attribute the model used, with the value taken from the application and that attribute’s signed contribution to the outcome. See Reading GiniMachine scoring results. Note Only the resolution feeds the Scoring result decision table. The Probability of repayment and the attribute effects are stored on the application and shown to the credit officer, but they do not change the zone directly. Choosing a provider Configuration How the zone is determined Internal only By the internal rank alone — rules 5 to 7 of the Scoring result table. GiniMachine only By the resolution alone — rules 8 and 9. Both Rank and resolution are reconciled — rules 1 to 4 where they match, otherwise rules 5 to 7. Internal, GiniMachine and a third-party provider The reconciliation rules are extended as part of the integration. ### Connecting GiniMachine to a product group Source: https://docs.hesfintech.com/loanbox/scoring-and-credit-decisioning/connecting-ginimachine-to-a-product-group/ Connecting GiniMachine to a product group Scoring is configured in the Decision making block of the product group form, on both Create product group and Edit product group. The settings apply to every application submitted under that product group. Selecting GiniMachine scoring model The GiniMachine scoring model field is a searchable, single-select field. The list is populated from the connected GiniMachine instance and shows the models available there — for example, SME Behavioral-Financial Delinquency, DevEU Transactional History (5), lb_person_scoring_9_columns. ### The Scoring result decision table Source: https://docs.hesfintech.com/loanbox/scoring-and-credit-decisioning/the-scoring-result-decision-table/ The Scoring result decision table The Scoring result decision table turns the provider outputs into a single verdict. Like the internal scoring model, it is a DMN decision table. Note To author and version the internal decision table, see Scoring model setting in the Settings section. Table structure Element Value Hit policy First — rules are evaluated from the top, and the first matching rule wins. Rule order is significant. Input: Internal rank String — “A” to “E”, or – (any) Input: GiniMachine resolution Boolean — true, false, or – (any) Output: Result Probability of repayment String — “GREEN_ZONE”, “GREY_ZONE”, “RED_ZONE” Annotations Free-text guidance shown next to each rule. Rules # Internal rank GiniMachine resolution Result Probability of repayment Annotation 1 “A” true GREEN_ZONE Suggestion to approve for the underwriter 2 “A” false GREY_ZONE Consider possible risks for the underwriter. 3 “E” true GREY_ZONE Consider possible risks for the underwriter. 4 “E” false RED_ZONE Reject the loan application 5 “A” – GREEN_ZONE Suggestion to approve for the underwriter 6 “B”, “C”, “D” – GREY_ZONE Consider possible risks for the underwriter. 7 “E” – RED_ZONE Reject the loan application 8 – true GREEN_ZONE Suggestion to approve for underwriter 9 – false RED_ZONE Reject the loan application How to read the table The rules fall into three groups, and the First hit policy keeps them from colliding. Rules 1 to 4: both providers ran, and the rank is at an extreme. These are the cases where the two providers can meaningfully agree or disagree. Both positive (A with Approve) gives green; both negative (E with Decline) gives red. Disagreement in either direction gives grey; neither provider overrides the other, and the application goes to a human. Rules 5 to 7: matched on the internal rank alone. These catch everything that did not match rules 1 to 4. Because rule 6 matches B, C, and D with the resolution set to any, mid-range ranks produce a grey zone regardless of what GiniMachine returned. That is worth knowing before go-live: a lender running both providers will route the middle of the rank distribution to manual underwriting even when GiniMachine gives a clear answer. A lender who wants GiniMachine to break ties on mid-ranks adds explicit rules for those combinations above rule 6 — under the First hit policy, position in the table gives a rule precedence. Rules 8 and 9: matched on the resolution alone. These apply when the internal rank is not present. The resolution maps straight to green or red, with no grey band. Result zones Zone Meaning Green zone Both available signals are positive. Grey zone The signals disagree, or the internal rank is mid-range. Red zone Every available signal is negative. What happens next The result score does not decide the application on its own. The platform’s action for each zone is set by the Underwriting mode on the product group. Underwriting modes Underwriting mode Green zone Grey zone Red zone Automatic Approved automatically Rejected automatically Rejected automatically Semi-Automatic Approved automatically Routed to a credit officer Rejected automatically Manual Routed to a credit officer Routed to a credit officer Routed to a credit officer Under manual underwriting, the zone is a recommendation, and the officer can decide against it. Under semi-automatic underwriting, the officer is involved only where the signals disagree. Under automatic underwriting, no officer is involved, and the grey zone resolves to a rejection. ### Reading GiniMachine scoring results Source: https://docs.hesfintech.com/loanbox/scoring-and-credit-decisioning/reading-ginimachine-scoring-results/ Reading GiniMachine scoring results GiniMachine results appear on the application’s Scoring tab and again inside the Make a decision task for applications awaiting a credit decision. The application record carries the following tabs: General info Borrower details Bank info Attachments Contract Credit bureau Scoring Collateral info Audit trail Profitability info The Result line The Result at the top of the Scoring tab is the output of the Scoring result decision table — the combined verdict, not GiniMachine’s. It is displayed with a color indicator. The GiniMachine scoring block Field Example Description Model lb_person_scoring_9_columns The model that produced this result. Recorded on the application, so a result can be traced back to the model that generated it. Probability of repayment 0.8090 The model’s numeric output for this application. Resolution Approve The model’s verdict and the value passed into the Scoring result decision table. The attribute effect table Below the Probability of repayment, GiniMachine lists every attribute the model used, with the value taken from the application and that attribute’s effect. Attribute Value Effect Owns vehicle False 0.0124 Current age 36.0 0.0077 Marital status Married 0.0051 Industry sector Chemical industries 0.0042 Education Masters degree 0.0040 Length of employment > 4 years 0.0029 Owns property False 0.0023 Position Senior level manager −0.0140 Monthly income 5000.0 −0.0810 How to read it: The table is sorted by effect, descending — the strongest positive contributors first, the strongest negative contributors last. The sign shows the direction of each attribute’s contribution to the outcome; the magnitude shows how much weight it carried. Magnitude matters more than sign when reviewing an application. In the example above, Monthly income = 5000.0 at −0.0810 carries roughly six times the weight of any single positive contributor: the application scored well overall, but income was the one attribute working against it. The attributes listed are exactly the ones the model was trained on. A model named ..._9_columns shows nine rows. The attributes with the largest negative effects are the starting point for explaining a declined application to the borrower, where the market requires it. ### Overview Source: https://docs.hesfintech.com/loanbox/contract-signing/ Overview and definitions The Sign Contract process is the stage of loan origination during which the borrower signs the loan contract before the loan is disbursed. It runs after the loan application has been approved and after recurring-payment setup (if any), and it precedes the activation and disbursement of the loan. During this stage the system: prepares the repayment schedule for the approved loan terms, generates a PDF contract from the product group-linked contract template, routes the contract through the appropriate signing channel (chosen by the product group settings), waits for the borrower (or the credit officer for offline signing) to act, saves the signed contract on the loan application and proceeds to the next stage of the deal. The process enforces a 72-hour deadline from the moment signing starts. If the borrower does not sign within that window, the application is automatically declined. The process can finish in one of the following outcomes: Contract signed — the signed PDF is attached to the loan application, and the deal continues. Contract declined by the borrower — the application is canceled. Contract expired — 72 hours passed without a signature; the application is declined, and the borrower receives a notification. A new offer was generated — while the borrower was on the signing screens, the conditions changed, and the signing of the previous version was dropped in favor of the new one. Application canceled — the application was canceled outside this process (for example, by the back office); the contract file is removed. In addition, before signing starts, the system performs a quick check on the First payment date. If the loan is not a Credit Line or a Payday Loan, and the configured first payment date is less than 4 days from today, the application is declined immediately with a notification to the borrower. ### Signing options (product-group level) Source: https://docs.hesfintech.com/loanbox/contract-signing/signing-options/ Signing options on the Product Group level The signing channel is configured at the product group level. Each product group has a Signing option parameter that determines how the borrower will sign the contract. The Signing option dropdown on the product group offers exactly the following values: Value What it means for the borrower E-signature The borrower signs the contract through an embedded electronic signature window inside the Borrower Portal (iframe). The system tracks signing status with the e-signature provider in the background. OTP The borrower reviews the contract on the Borrower Portal, requests an SMS code, and confirms signing by entering that one-time password. Outside the system The borrower signs the contract offline. A credit officer in the Back Office uploads the physically signed copy on the borrower’s behalf. In addition to the product group-level Signing option, the platform has a system-wide E-sign service setting (pandaDoc or pandaDocEmail). This setting becomes relevant only when the product group’s Signing option is set to E-signature: If the system-wide E-sign service is set to pandaDoc, the borrower signs through an iframe inside the Borrower Portal. If the system-wide E-sign service is set to pandaDocEmail, the borrower receives a signing link by email and signs entirely outside of the portal. ### Signing flow Source: https://docs.hesfintech.com/loanbox/contract-signing/signing-walkthrough/ Signing option The first part of the process is the same for all signing options. The signing-option-specific tasks come after the contract has been generated. Common preparation steps (all options) These steps run automatically, and the borrower sees the “Wait for an offer” screen on the Borrower Portal while they are happening. Step 1 — First payment date check. The system checks that the configured first payment date is at least 4 days in the future. If not (and the product is not a Credit Line or a Payday Loan), the application is declined and the borrower receives a decline notification. Step 2 — Show “Wait for an offer” to the borrower. The Borrower Portal displays the screen titled “Wait for an offer” with the message: “Please, wait a few minutes while we are working on your offer.” The screen refreshes automatically every 10 seconds. It stays visible until the contract is ready to be signed. Step 3 — Record the signing start time. The system stores the moment from which the 72-hour deadline starts counting. Step 4 — Calculate the repayment schedule. The system selects the amortization strategy that matches the product group and produces the planned repayment schedule for the approved amount and term. Step 5 — Generate the contract. The system generates the contract PDF from the contract template that is attached to the product group, filled with the borrower’s data and the approved loan terms. Step 6 — Select the signing service. Based on the product group’s Signing option, the system-wide E-sign service, and the document subject, the system picks one of four signing flows described below. After step 6 the borrower’s experience and the back-office tasks differ depending on the chosen signing option. Option A. Signing with OTP The borrower stays on the Borrower Portal throughout the signing. Borrower Portal tasks: Step A1. Review the contract — Borrower Portal Property Value Where it appears Borrower Portal Screen title Review the contract What the borrower sees and can do: A built-in PDF viewer that displays the generated contract. Two buttons: Agree — proceed to the OTP signing step. Decline — opens a confirmation popup “Are you sure you want to decline the loan offer?” with the buttons Yes and Back. Clicking Yes terminates signing and the application is cancelled. The screen refreshes automatically every 10 seconds, so if a new offer is generated in the background, it picks it up. Step A2. Sign the contract with OTP — Borrower Portal Property Value Where it appears Borrower Portal Screen title Sign contract When this step starts, the system generates a numeric OTP code and sends it to the borrower’s phone by SMS. What the borrower sees and can do: A built-in PDF viewer that displays the generated contract. A help message: “To sign the contract, please check your phone and enter the code into the field below.” An OTP code text field (required). If the borrower enters a wrong code, the message “Invalid OTP Code” is shown in red, and the field is reset. A Resend code button — when clicked, the system sends a new OTP code to the borrower’s phone and the previous code becomes invalid. A Sign the contract button — submits the entered OTP. If it matches, the contract is considered signed. A Decline the offer button — opens the “Are you sure you want to decline the loan offer?” confirmation popup with Yes and Back. Clicking Yes cancels the application. Validity rules for the OTP: The code is valid for 10 minutes after it is generated. After 10 minutes the code is automatically invalidated and the borrower must use Resend code to receive a new one. A successful match attaches the entered code to the signed contract record and moves the borrower to the next step. Step A3. Loan-origination completion notification — Borrower Portal Property Value Where it appears Borrower Portal Screen title Thank you The borrower sees a confirmation message: “Document is signed. Wait for the next step.” The screen automatically continues to the next stage of the deal after a short delay. Back Office tasks: none. Signing with OTP is fully self-service. Option B. Signing with E-signature in an iframe The borrower signs the contract directly inside the Borrower Portal using an embedded electronic-signature provider window. Background preparation by the system (no user task): The system identifies the signatory (the borrower if a person, or the legal entity’s representative if a company). The system creates the document in the e-signature provider, sends it for signing, and obtains a signing session. The system polls the document status every 5 seconds until the document is ready to be signed. Borrower Portal tasks: Step B1. Sign the contract with e-signature — Borrower Portal Property Value Where it appears Borrower Portal Screen title Sign contract What the borrower sees and can do: An embedded e-signature window (iframe) where the borrower reviews and signs the document directly. A Decline the offer button — opens the confirmation popup “Are you sure you want to decline the loan offer?” with Yes and Back. Clicking Yes marks the document as declined in the e-signature provider and cancels the application. While the borrower is on this screen, the system checks the document status with the e-signature provider every 30 seconds. As soon as the provider reports the document as completed, the borrower is moved to the next step automatically. Step B2. Loan-origination completion notification — Borrower Portal Same as Step A3: the Thank you screen with the message “Document is signed. Wait for the next step.” Background finalization by the system: The system downloads the signed contract from the e-signature provider and saves it on the loan application. Back Office tasks: none. Option C. Signing by email link The borrower does not interact with the Borrower Portal for signing. Instead, they receive a link by email and sign on the e-signature provider’s own page. Background preparation by the system (no user task): The system identifies the signatory. The system creates the document in the e-signature provider. The system sends the document to the borrower by email and notifies the borrower by SMS that the email has been sent. Borrower experience (outside the portal): The borrower receives a notification by SMS that the contract is ready for signing. The borrower opens the email from the e-signature provider, reviews the contract there, and either signs it or declines it on the provider’s page. System polling: The system checks the document status with the provider every 30 minutes. As soon as the provider reports that the document is completed, the system downloads the signed contract and saves it on the loan application. If the provider reports that the document is declined, the application is cancelled. Borrower Portal tasks: none for the actual signing. There is no signing screen in the Borrower Portal in this option. Back Office tasks: none. Option D. Signing outside the system The borrower signs the contract physically (offline). A credit officer in the Back Office uploads the signed copy. Borrower Portal tasks: none. The borrower does not see any signing screen in this option. Back Office tasks: Step D1. Upload the signed contract — Back Office Property Value Where it appears Back Office Who can do it Credit Officer Screen title Upload the signed contract, Application #{application number} The screen has two main areas: a read-only context block that lets the credit officer verify the application before uploading and the upload panel with the decision and the file uploader. Read-only context block — shown at the top, organized into tabs. Above the tabs, the screen also shows: Requested amount, Requested term, Approved amount, Approved term in the application’s currency. Tab Content General info Borrower name, loan-application general info, link to the application details page, and the loan product general info with a link to the product details page. Borrower details Borrower general info with a link to the borrower’s profile. Amortization Schedule The planned repayment schedule for this contract. Bank info Borrower’s bank and financial info, plus bank-account verification results (if any). Attachments Supporting documents previously uploaded with the application. Shows “No info” if none. Scoring Scoring details for this application. Collateral info Collateral general info for the application (if any). Upload panel — Upload the signed contract — this is where the credit officer enters the decision and file: Parameter Description Type Required Possible values Default Notes Generated contract A built-in PDF viewer showing the contract that the system generated. The credit officer downloads it from here, has the borrower sign it offline, then uploads the signed copy. PDF preview — (read-only) — — — Decision The credit officer’s decision after the borrower has signed (or refused to sign) the contract offline. Toggle Yes Decline — the borrower refused to sign; the application will be cancelled. Approve — the borrower signed; the credit officer must upload the signed file. — If Decline is chosen, no file upload is required. Signed contract The file uploader for the signed contract copy. Shown only when Decision is Approve. File upload Yes (only when Decision = Approve) Image-enabled file upload, max file size 20 MB. — The uploaded file replaces the placeholder file on the loan application as the signed contract. Submit The button that finalizes the task. Button — — — Disabled while the form is invalid (for example, when Approve is selected but no file is uploaded). After Submit: If Decision = Approve, the system saves the uploaded file as the signed contract on the loan application, and the deal continues. If Decision = Decline, the application is cancelled, and the borrower receives a cancellation notification. ### Deadline expiration Source: https://docs.hesfintech.com/loanbox/contract-signing/deadline-expiration/ Deadline expiration If the borrower does not complete signing within 72 hours from the moment signing started, the system: Stops the active signing task (regardless of the option in use). Removes the unsigned contract file. Declines the application. Sends an “agreement expired” notification to the borrower’s email. This timeout applies to all four signing options. ### New offer mid-signing Source: https://docs.hesfintech.com/loanbox/contract-signing/new-offer-at-mid-signing/ New offer at mid-signing If, while the borrower is on the signing screens, the loan terms change (for example, the back office issues a new offer), the current signing flow is interrupted: The unsigned contract file is deleted. For E-signature flows, the document is also cancelled in the e-signature provider. The borrower is taken back to the Wait for an offer screen, after which the process restarts: the system regenerates the contract, picks the signing service again, and shows the new signing screen. ### User tasks Source: https://docs.hesfintech.com/loanbox/contract-signing/user-facing-tasks/ User-facing tasks The screens each signing option shows to the borrower and to the back office: Signing option (product group) Borrower Portal screens Back Office screens OTP Wait for an offer → Review the contract → Sign contract (OTP) → Thank you — E-signature (pandaDoc) Wait for an offer → Sign contract (iframe) → Thank you — E-signature (pandaDocEmail) Wait for an offer (the borrower signs in their email outside the portal) — Outside the system Wait for an offer (until the credit officer finishes the upload) Upload the signed contract ### Overview Source: https://docs.hesfintech.com/loanbox/loan-management-and-servicing/ Overview The Loan management process is the long-running flow that manages an issued loan from the moment it appears in the system until it is fully repaid, closed, or written off. While the loan origination flow handles “should we lend” decisions, Loan management handles “what happens with the loan every day after we lend”. The system provides two types of Loan management according to the two product types: Aspect Fixed-term loan Credit line Money is given… as a single disbursement at the start gradually, on each drawdown the borrower requests Repayment fixed schedule of installments flexible, pay back what was drawn during the billing cycle Term defined maturity date revolving until drawdowns are frozen near maturity Interest base accrues on the principal balance accrues on the outstanding drawn balance Schedule full amortisation schedule (annuity, linear, payday) billing cycles (start, closing, payment date) Both types share the same daily schedule: a midnight job recalculates interest and updates the loan snapshot; a 03:00 AM job checks whether today is a payment day and, if so, kicks off the scheduled payment; borrower-initiated and credit-officer-initiated operations (write-off, register payment, waive fees, adjust loan, drawdown) feed events into the loan; each event produces a new immutable loan snapshot — the financial picture at that point in time. What differs is type-specific bookkeeping: fixed-term loans recalculate the amortization schedule when the rate or terms change; credit lines open and close billing cycles, and check the drawdown freeze date. ### Creating a loan / credit line Source: https://docs.hesfintech.com/loanbox/loan-management-and-servicing/loan-credit-line-created/ Loan / credit line created The loan record itself is created at the very end of the Loan origination flow, immediately after the loan application is approved and the loan agreement is signed. Behavior differs by loan type: Fixed-term loan. Created with status Pending. The loan exists in the system but is not yet active — no interest accrues, no payments are scheduled. The Loan management process starts straight away and waits for the disbursement to be created. Credit line. Created already with status Active. The credit limit is set; no funds have been moved yet. The Loan management process starts and waits for the borrower’s first drawdown. The loan number is inherited from the loan application number, so origination and servicing share the same identifier across the whole lifecycle. ### Activating a loan / credit line Source: https://docs.hesfintech.com/loanbox/loan-management-and-servicing/loan-credit-line-activated/ Loan / credit line activated Activation marks the moment when the loan starts to “live” — interest can accrue, payment dates apply, and the loan appears as Active in the loan list. Fixed-term loan. Activation happens automatically right after the disbursement transaction is successfully completed. The sequence the borrower experiences: The agreement is signed, and the loan is created in Pending status. The system selects the disbursement provider for the loan’s product (Manual or one of the integrated providers — Squarepay, VoPay EFT/ACH/eTransfer/Flinks, Plaid, Acquired). Funds are moved (or, for the manual option, a credit officer confirms the manual disbursement). The system records a Disbursement event; the loan flips to Active; and the linked loan application is marked as Disbursed. Credit line. Activation happens at creation — the credit line is born active. However, the line only becomes “useful” once the borrower issues their first drawdown. Each drawdown follows a similar disbursement step: the system picks the provider, moves funds (or asks a credit officer to confirm a manual disbursement), records a Disbursement event, and updates the snapshot to reflect the new principal balance and reduced available credit limit. ### Interest accrual Source: https://docs.hesfintech.com/loanbox/loan-management-and-servicing/interest-accrual/ Interest accrual Interest accrual is a daily job that runs at midnight for every active loan. The same engine is used for both loan types, but the inputs and outputs differ. Common rules The rate used for accrual is the agreed rate at the time of issue. Each daily run produces a new loan snapshot — the financial position as of that day. Loans in terminal status (Repaid, Closed, Written Off) are skipped. Fixed-term loan Daily interest is added to the interest balance until the next payment date. On the payment date, the scheduled payment process allocates the borrower’s payment to interest first, then to principal, following the amortization schedule. If the system prime rate changes (and the loan has a variable rate), the schedule is recalculated for all remaining periods on the effective date. If the borrower is overdue, default interest accrues on the overdue principal at the penalty rate from the product. Credit line Daily interest is calculated on the outstanding principal (drawn) balance and accumulates inside the currently open billing cycle. Each credit line has at most one open billing cycle at a time. When the closing date arrives, the cycle is closed: the accumulated interest plus principal due is the cycle’s payment amount, due on the cycle’s payment date. A new billing cycle then opens automatically. When the drawdown freeze date approaches (a configured number of days before maturity), drawdowns are blocked, and only repayments continue. In both cases, the loan moves to Overdue automatically if the payment day passes and the obligations remain unmet. ### Disbursement Source: https://docs.hesfintech.com/loanbox/loan-management-and-servicing/disbursement-process-and-options/ Disbursement: process and options Disbursement is the process of moving money from the lender to the borrower. The platform supports multiple providers and two operating modes — Automatic and Manual — selected by the loan product configuration. What drives the choice The product group the borrower applied under defines a “Disbursement option” with two values: Automatic — the platform integrates with an external payment provider and moves the funds itself. Manual — a Credit Officer confirms the disbursement was performed outside the system (cheque, wire transfer, etc.). In addition, an environment-level setting selects which automatic provider is wired up. The combination of these two values determines the actual disbursement sub-process used. Provider mapping Disbursement option Provider name Sub-process used Manual (any) Manual disbursement (Credit Officer confirms) Automatic squarepay Squarepay disbursement Automatic vopay-eft VoPay EFT disbursement Automatic vopay-ach VoPay ACH disbursement Automatic vopay-etransfer VoPay e-Transfer disbursement Automatic vopay-flinks-eft VoPay (via Flinks) EFT disbursement Automatic plaid-transfer Plaid Transfer disbursement Automatic acquired Acquired.com disbursement The same mapping applies to both fixed-term loans (single disbursement at activation) and credit lines (each drawdown). Manual disbursement tasks for the Credit Officer When the product uses the Manual option, the Credit Officer is the operator who actually moves the money outside the system and then records that fact in the platform. There are two distinct user tasks, one per loan type. They look similar but operate on different objects and have different downstream effects (see Result of a successful disbursement below). “Disburse funds” — fixed-term loan Who performs it: A user with the Credit Officer role. The task lands in the Credit Officer task queue. When it appears: Right after the loan agreement is signed, the loan is created in Pending status, and the system begins its disbursement process. If the product group is configured as Manual, the system creates this task instead of calling an automatic provider. The task is titled “Disburse funds, Application #{number}” — the loan application number is part of the title, so the operator immediately knows which deal is being disbursed. What the operator sees: The “Disburse funds” form shows the full loan application picture, all read-only: A header with the borrower’s full name (clickable link to the borrower’s profile), the requested amount and term, and the approved amount and term. A General info tab with the application’s general info card. A Borrower details tab with the borrower’s general info. A Bank info tab with bank and financial information and (if available) the bank account verification card — this is the account the funds must be sent to. An Attachments tab with all supporting documents collected during origination. A Scoring tab and a Contract tab (the signed agreement). A “Disburse” panel at the bottom — the only editable area on the form. What the operator decides: In the Disburse panel: Field Type Required Notes Type of disbursement Dropdown Yes One of Cheque, Cash, Wire transfer, Online transfer, Mobile money — how the funds were actually sent Document number Text No Up to 255 characters, e.g., the cheque number or wire reference Funds were disbursed Checkbox Yes The operator must tick this to confirm that money has actually left the lender The operator does not decide the amount or the destination account — both are determined by the application. The amount is the application’s disbursement amount (approved amount minus any product fees); the account is the verified bank account on the application. On submission: After the operator clicks “Submit,” the system: Records a successful outbound Disbursement transaction with the chosen method, document number, the operator’s name, and the timestamp. Activates the loan: the loan status flips to Active, and the linked application is marked as Disbursed. Fires a “Disbursement created” signal that adds a Disbursement loan event, rebuilds the loan snapshot (principal balance set to the disbursed amount), and starts the daily interest accrual and scheduled payment timers. Sends a “loan disbursed” notification to the borrower. Validations and limits: The amount field is read-only and inherited from the application — there is no operator-side override, so there is no min/max to police on this form. The application must be in the right state for the task to even appear; if it isn’t, the task does not exist. On failure / no decision: If the operator does not complete the task within 5 days, the system unassigns it and ends the disbursement attempt with a “Disburse funds decision hasn’t been made” outcome. This bubbles up to the parent flow as a disbursement failure: the loan and application are marked as Error, and a “Disbursement failed” terminal state is reached. The deal cannot continue without manual intervention. There is no automatic retry — disbursement of a fixed-term loan is a one-shot operation. “Confirm drawdown” — credit line Who performs it: A user with the Credit Officer role. When it appears: Each time the borrower initiates a drawdown from the borrower portal on a credit line configured as Manual, the system creates this task. The task title is “Confirm drawdown, Credit line #{number}”. Unlike the fixed-term loan version, this task can repeat any number of times during the life of the credit line — once per drawdown. What the operator confirms: The “Confirm drawdown” form is short and focused on a single drawdown: A read-only credit line info card at the top — credit limit, available credit limit, status, borrower. The drawdown amount the borrower asked for (read-only — this comes from the borrower’s drawdown request and cannot be changed by the operator). What the operator decides: Field Type Required Notes Amount Number Yes Pre-filled from the borrower’s request, read-only Type of drawdown Dropdown Yes One of Cheque, Cash, Wire transfer, Online transfer, Mobile money — same list as fixed-term Document number Text No Up to 255 characters — payment reference Drawdown was sent Checkbox Yes The operator must tick this to confirm the funds were transferred to the borrower On submission, the system: Records a successful outbound Disbursement transaction tied to the credit line with the chosen method, document number, the operator’s name, and the timestamp. Adds a Disbursement loan event for this drawdown only (the credit line itself is already Active, and stays Active; no status flip). Rebuilds the credit line snapshot: principal balance increases by the drawdown amount, available credit limit decreases by the same amount, and the current billing cycle’s interest base updates accordingly. Sends a “drawdown disbursed” notification to the borrower. On failure / no decision: Same 5-day rule as for fixed-term: if the operator does not complete the task within 5 days, it is unassigned, and the drawdown ends with a “Drawdown decision hasn’t been made” outcome. The drawdown attempt is canceled, and the credit line is unaffected — no event, no snapshot change, and the borrower’s available credit limit is not consumed. The borrower can request a new drawdown. Validations before the task exists: Before the system even creates the “Confirm drawdown” task, the borrower’s drawdown request goes through these checks; if any fail, the task is never created, and the borrower sees an explanatory error: Loan must be Active — drawdowns on inactive credit lines are rejected. Available credit limit not exceeded — the requested amount must fit within the available credit limit (plus product fees: establishment fee and service fee). Drawdown freeze date not reached — once the configured freeze period before maturity starts, no new drawdowns are accepted. No active drawdown is already in progress — only one disbursement transaction per credit line can be in progress at a time. Result of a successful disbursement The end state varies by loan type: Fixed-term loan. A Disbursement loan event is created (with date, amount, and attachments). The loan snapshot is updated — the principal balance becomes the disbursed amount, and the interest balance is zero. The loan flips from Pending to Active. The linked application is marked as Disbursed. The amortization schedule that was already calculated at contract signing becomes the live schedule from this point on — the daily interest job and the 03:00 AM scheduled-payment job both start using it. The borrower is notified. Credit line. A Disbursement loan event is created for this drawdown only. The snapshot is updated — the principal balance grows by the drawdown amount, the available credit limit shrinks by the same amount, and the current open billing cycle now has additional principal to accrue interest on. The credit line stays Active (it was already Active before the drawdown). The borrower is notified. ### Scheduled payments Source: https://docs.hesfintech.com/loanbox/loan-management-and-servicing/scheduled-payment-process/ Scheduled payment process Every active loan has a scheduled payment processing sub-process embedded in the Loan management flow. It is what makes the loan “self-collecting” — the system attempts to take the payment on the due date without manual intervention. When it runs A timer fires every day at 03:00 AM and asks: “Is today a payment day for this loan?” Fixed-term loan. A day is a payment day if it equals the next scheduled payment date in the amortization schedule. Credit line. A day is a payment day if it equals the payment date of the most recently closed billing cycle. If today is not a payment day, the sub-process ends silently. Otherwise, it proceeds with payment processing. Outside of the scheduled job, both loan types accept ad-hoc payments — initiated by the borrower from their portal (Initiate Payment) or by a credit officer (Register Payment, see the Register payment operation page). What happens on the payment day The loan record is refreshed from the database. The system checks that the loan is still active. Process Payment is invoked: a transaction is created and routed to the configured repayment provider (Squarepay, VoPay variants, Plaid, Acquired, etc., or “no repayment” if no automatic provider is configured). If the provider confirms the payment, a Repayment loan event is created with the transaction reference and amount. The borrower receives a “payment received” notification. The new snapshot reflects the reduced balances. Failure handling If the provider rejects the payment (insufficient funds, account closed, etc.), the transaction is marked as Failed. The scheduled payment sub-process ends; the loan moves to Overdue when the calendar advances past the payment day and the obligation remains unmet, triggering the collection workflow. ### Payment allocation Source: https://docs.hesfintech.com/loanbox/loan-management-and-servicing/payment-allocation/ Payment allocation When a payment of any kind is applied to a loan (whether scheduled, ad hoc from the borrower, or manually registered by a credit officer), the system allocates the amount across the loan’s outstanding components in a fixed order. This ensures consistent treatment across product types and providers. Allocation order The amount is consumed in this order, stopping when no money remains: Overdue penalties — accrued penalty fees on overdue amounts. Default interest — penalty interest accrued on overdue principal. Overdue interest — regular interest that became overdue. Overdue principal — principal that became overdue. Current interest balance — interest accrued for the current period. Current principal — principal due. Outcomes of allocation The loan snapshot is recalculated: each component is reduced by the allocated portion. Overdue date is cleared as soon as overdue amounts reach zero, and the loan returns to Active. If all obligations are satisfied, the loan moves to Repaid (terminal). A Repayment loan event is recorded with the full transaction amount and the resulting snapshot. Why the order matters Overdue obligations are settled first to bring the loan out of default as quickly as possible — this stops default interest from accruing. Current obligations come next. Borrowers who pay more than required see the excess applied to the loan early (early repayment), which can shorten the loan term or reduce future interest, depending on the product’s calculation strategy. Special cases Waived debt is removed from the snapshot before any incoming payment is allocated, so a waiver of overdue penalty effectively skips step 1 above. Adjusted loans (after a restructuring is applied) get a fresh amortization schedule; payments are allocated against the new schedule from the next period onwards. ### Loan list and filters Source: https://docs.hesfintech.com/loanbox/loan-management-and-servicing/loan-list-and-filters/ Loan list and filters Loans of both types live in a single Back Office module — “Loans” — with a unified list view. Differences between fixed-term loans and credit lines are displayed on the loan detail page rather than in the list itself. Available to Back Office users with one of the following roles: Underwriter, Credit Officer, Collection Manager. Other portals (Borrower, Agent) have their own scoped list showing only loans the user owns or services. Columns (list view, brief mode) The list shows summary information: loan number, borrower (full name from the linked application), loan product, status, loan amount, and loan term. Filters The list supports these filters: Filter Type Values Search Text input Free text. Matches on loan number, borrower full name, phone, email Statuses Multi-select Active, Overdue, Repaid, Closed, Written Off, Processing, Error (and the transitional Pending for fixed-term loans before activation) Loan types Multi-select Fixed-term loan, Credit line Issue date from Date Lower bound of the issue date range Issue date to Date Upper bound of the issue date range Sorting and actions Default sorting: by created date, descending — newest loan first. Pagination is supported. Available actions: navigate to the loan/credit line card (click on a row). What differs between loan types Although the list is unified, the detail page adapts: The fixed-term loan detail shows the amortization schedule (planned and actual), per-period interest and principal amounts, and the maturity date. Credit line details include the credit limit, available credit limit, frozen credit limit, current open billing cycle, drawdown freeze date, and a list of drawdowns. Operations available also differ by loan type — see the operation pages that follow (Write-off, Register payment, Waive fees, Adjust loan). ### Write-off Source: https://docs.hesfintech.com/loanbox/loan-management-and-servicing/write-off-operation/ Write-off operation Write-off declares a loan permanently uncollectible. It is irreversible. The platform has separate sub-processes for fixed-term loans and credit lines, but the user experience is similar across both. Who can do it Credit Officer (and Collection Manager during a collection workflow). The user must already be on the loan’s detail page. Steps Step 1. Open the Write-off form The user clicks “Write off” on the loan card. The system opens the form titled “Write off the fixed-term loan” or “Write off the credit line,” depending on the loan type. Step 2. Fill the form The form requires one field: Field Type Reason Dropdown The form also shows the loan title and current loan status (read-only), so the user can confirm they are on the correct loan. Reasons for an individual borrower (Person): Non-performing loan Legal decision Borrower went bankrupt Borrower died Reasons for a legal entity borrower: Non-performing loan Legal decision Borrower went bankrupt Step 3. Confirm The user clicks “Confirm”. The system reloads the loan and validates that it is still active. If not, an error “Write off is not available for closed loans” is shown, and the operation stops. Step 4. The system processes the write-off If the loan is active, the platform: Saves the selected reason on the loan. Creates a Write-off loan event tied to this user. Sends a “loan has been written off” signal into the loan flow, where the daily calculation excludes the loan from then on. The loan moves to Written Off (terminal). Step 5. Result The loan is now in Written Off status, no further interest accrues, and no scheduled payments are attempted. The reason is stored for audit. Write-off during collection Once the loan is routed to collection, the Collection Manager uses a different task (“Write off the loan during collection”). The reason list is the same; the difference is the workflow context (the operation happens inside the collection process rather than directly from the loan card). ### Register payment Source: https://docs.hesfintech.com/loanbox/loan-management-and-servicing/register-payment-operation/ Register payment operation Register Payment lets a credit officer record a payment that arrived outside the system (e.g., the borrower paid in cash or by cheque, or transferred funds to a bank account not linked to an integrated provider). The platform has separate sub-processes for fixed-term loans and credit lines, but the user experience is similar. Who can do it Credit Officer. Steps Step 1. Open the Register Payment form From the loan detail page, the user clicks “Register payment.” The system opens the form titled “Register payment fixed-term loan” or “Register payment credit line.” Step 2. Fill the form Field Type Required Notes Method Dropdown Yes One of the manual payment methods (see below) Document number Text No Up to 255 characters; reference of the external payment document (e.g., cheque number) Repayment date Date Yes Cannot be earlier than the loan issue date; cannot be later than today Repayment amount Number Yes Min 0.01; max 9,999,999,999,999.99 in the loan’s currency Supporting documents File upload No Multiple files allowed, each up to 20 MB; total count limited by environment setting Method values: Cheque Cash Wire transfer Online transfer Mobile money Step 3. Confirm The user clicks “Confirm.” The system reloads the loan and verifies it is active. If the loan is closed/written off, an error message “Payment registration is not available for closed loans” appears, and nothing is saved. Step 4. The system processes the payment If the loan is active: A Repayment transaction is created for the entered amount and method. A Repayment loan event is recorded with the repayment date and the attached documents. The payment is allocated to the loan balances in accordance with the standard payment allocation order (see the Payment allocation page). A new loan snapshot is produced. The borrower is notified. Step 5. Result The user returns to the loan card. The new operation appears in the loan operations list, including the date, amount, type, and attachments. If the payment fully settles the obligations, the loan moves to Repaid; if it clears overdue amounts, the loan returns to Active from Overdue. ### Waive fees Source: https://docs.hesfintech.com/loanbox/loan-management-and-servicing/waive-fees-operation/ Waive fees operation The Waive operation allows a credit officer to forgive part of the accrued debt — overdue penalties or default interest — without requiring a payment from the borrower. The platform has separate sub-processes for fixed-term loans and credit lines, but the user experience is similar. Who can do it Credit Officer. Steps Step 1. Open the Waiver form From the loan detail page, the user clicks “Waive accrued debt.” The system opens the form titled “Waive accrued debt fixed-term loan” or “Waive accrued debt credit line.” Step 2. Fill the form Field Type Required Notes Waiver type Dropdown Yes What category of debt is being waived (see below) Amount Number Yes In the loan’s currency. Pre-filled with the current balance of the chosen category, but the user can lower it. Must be greater than 0 and no greater than the current balance Supporting documents File upload No Multiple files allowed, each up to 20 MB Waiver type values: Value Display What it forgives Waive overdue penalty Overdue penalty The accrued overdue penalty fees on the loan Waive default interest Default interest The accrued default (penalty) interest The form pre-populates the Amount field based on the chosen type — selecting “Waive overdue penalty” sets it to the current overdue penalty balance from the snapshot; selecting “Waive default interest” sets it to the current default interest balance. The user can reduce this amount to a partial waiver. If the corresponding balance is zero, the form rejects submission with the message “no fee to waive.” Step 3. Confirm The user clicks “Confirm”. Step 4. The system processes the waiver A Waive Accrued Debt loan event is recorded with the waiver type, amount, attachments, and the user who performed it. The loan snapshot is updated: the corresponding balance is reduced by the waived amount. The borrower is notified. Step 5. Result The waiver appears in the loan operations history. Future payment allocations no longer include the waived portion. If the waiver eliminates the last overdue obligations, the loan transitions out of Overdue. Note Principal and current interest cannot be waived through this operation — only overdue penalty and default interest. ### Adjust loan Source: https://docs.hesfintech.com/loanbox/loan-management-and-servicing/adjust-loan-operation/ Adjust loan operation Adjusting a loan is the formal operation for restructuring an active loan/credit line: extending the maturity date, changing the interest rate, or applying a payment holiday. Unlike a write-off and waiver, an adjustment changes the future of the loan/credit line and therefore requires a new amendment agreement signed by the borrower. Adjust loan — fixed-term loan vs credit line The Adjust Loan operation is shared by both loan types, but what can actually be adjusted, what gets recalculated, and what conditions allow the change differ significantly. A credit officer who selects a credit line on the loan card will see a much shorter list of restructuring options than the same officer working on a fixed-term loan. Available restructuring options by loan type: Restructuring option Fixed-term loan Credit line Extend maturity date Available Not available — hidden from the dropdown Amend interest rate Available Available Apply payment holiday Available (except for payday-loan products) Not available — hidden from the dropdown For credit lines, the Amend interest rate is the only restructuring option ever offered, in both the back-office “Initiate loan adjustment” flow and the borrower-portal “Request loan adjustments” flow. The other two options are filtered out by the system before the dropdown is rendered. State conditions that allow each option: Option Allowed loan / line statuses Other conditions Extend maturity date Active, Overdue The current period is not the last period of the schedule Amend interest rate Active, Overdue, Processing (none) Apply payment holiday Active, Overdue, Processing Not a payday-loan product; current period is not the last; the current period is a payment period (no holiday already running) What is being changed when the operation is applied: Aspect Fixed-term loan Credit line Term / maturity Can be extended via Extend maturity date — the operator enters a new term length (in periods) greater than the current one Not adjustable through this operation Interest rate The operator enters a new interest rate (or new margin rate, if the rate is floating). The form re-prices the next installment in real time so the operator can preview the new payment amount The operator enters a new interest rate (or new margin) only. There is no “new payment amount” preview because credit lines do not have an installment schedule Payment holiday The operator enters Number of payment holiday periods (1–99) and a Term approach (currently only “Extend term”) Not adjustable through this operation Practical summary. For a fixed-term loan, “Adjust loan” is a true restructuring tool — it can move the maturity date, change the rate, or grant a payment holiday, and each of these triggers a fresh amortization schedule. For a credit line, “Adjust loan” is effectively a rate change tool — only the interest margin can be modified, and the change takes effect at the daily interest accrual level, not via a schedule rebuild. Two paths into the operation There are two ways an adjustment is initiated: Borrower-initiated — the borrower submits a request from the borrower portal (“Request loan adjustments”). It enters “For Review” and waits for a credit officer to review it. Backoffice-initiated — the credit officer starts the operation directly from the loan card (“Initiate loan adjustment”). The request is already in Approved status (the credit officer is an authorized decision maker), skipping the review step. Both paths converge at the signing step: the borrower must sign the amendment agreement before the changes take effect. Backoffice-initiated flow Step 1. Open the Initiate Loan Adjustment form On the loan/credit line card, the credit officer clicks “Adjust loan”. The system opens the “Initiate loan adjustment” form. Step 2. Fill the form Field Type Required Notes Restructuring option Dropdown Yes One of: Extend maturity date, Amend interest rate, Apply payment holiday — only options marked Available for this loan/credit line Adjustment parameters Group of fields Yes The set of parameters depends on the chosen option (see below) Supporting documents File upload No Multiple files Parameters by restructuring option: Option Parameters Extend maturity date New term length (number of periods) Amend interest rate New interest rate; for variable rates — new prime rate component; interest rate type (Fixed or Variable) Apply payment holiday Number of holiday periods Step 3. Confirm The system performs gating checks: The loan/credit line is still active. No other active loan adjustment request exists for this loan/credit line (only one at a time). The chosen option is still available for the loan/credit line’s current state. If any check fails, the operation is canceled with an explanatory error, and nothing is changed. Step 4. The adjustment request is created in the Approved status The system records who created it and stores the parameters and attachments. Step 5. The amendment agreement is generated and sent to the borrower for signing A document is prepared in accordance with the new schedule. The borrower receives a notification with a sign-the-agreement task. The borrower has a limited time window (set by configuration; commonly 72 hours) to sign. Step 6. Borrower signs the agreement The borrower opens the task in the borrower portal, reviews the amendment agreement, and signs it. The system: Re-checks restructuring availability (state may have changed during the signing wait). Calculates the new amortization schedule using the strategy of the loan’s calculation type (annuity, linear, or payday). Saves the signed document on the request. Creates a Loan Adjustments event with the option, parameters, and attachments. Marks the request as Applied. Sends an “adjustment applied” notification to the borrower. Step 7. Result Result Fixed-term loan Credit line Amortization schedule recalculation Yes — the schedule for all remaining periods is rebuilt using the calculation strategy of the loan (annuity, linear, or payday). Past periods stay frozen Skipped — credit lines have no amortisation schedule; the system records the change and moves on Next installment / payment amount New value, derived from the recalculated schedule Not applicable. The next payment amount is whatever the next billing cycle settles to — interest is now accrued at the new rate from the application date forward New rate kicks in From the effective date of the adjustment for the remaining schedule From the application date forward, it affects daily interest accrual on the outstanding drawn balance and, therefore, the closing amount of the next billing cycle Maturity / drawdown freeze date Maturity date moves later when Extend maturity date is applied; payment holiday extends the term per the chosen “Extend term” approach Unchanged — drawdown freeze date and maturity follow the original credit line setup Loan event recorded Loan Adjustments event with restructuring option set to “Extend maturity date,” “Amend interest rate,” or “Apply payment holiday” and the corresponding parameters Loan Adjustments event with restructuring option = “Amend interest rate” only Amendment agreement filed Yes — based on the new schedule Yes — based on the new rate, no schedule attached ### Overview Source: https://docs.hesfintech.com/loanbox/collection-process/ Overview The Collection process is the platform’s recovery workflow for overdue loans. When a loan misses a payment and crosses into Overdue status, the platform automatically opens a collection case and assigns contact tasks to the Collection Manager. The manager calls the borrower, records the result of every conversation, and either secures a payment, schedules the next reminder, or — if recovery is no longer feasible — escalates the loan to a Credit Officer for write-off. The process keeps running for as long as the debt remains outstanding. It only ends when one of three things happens: The borrower repays the debt, and the loan returns to a healthy state. The Credit Officer writes off the loan. The loan is written off through some other workflow outside of collection. Whether a loan enters the Collection process at all and how long the platform waits before starting it are determined by the product group under which the loan was issued. ### Overdue loans Source: https://docs.hesfintech.com/loanbox/collection-process/overdue-loan/ Overdue loan Loan moves to Overdue The platform performs a daily check on every active loan. The check evaluates the loan’s current financial position and assigns the appropriate status. A loan is marked Overdue when: it has an outstanding balance still to be repaid, and there are unpaid penalties already on the loan, and/or there is overdue interest (a scheduled interest payment that wasn’t made), and/or there is an overdue principal (a scheduled principal payment that wasn’t made). Once marked overdue, the platform records the Overdue date — the first day on which the loan was overdue. The number of Days in overdue displayed on screens is calculated from this date forward. If the borrower later pays enough to clear the overdue interest, overdue principal, and the penalties, the loan returns to Active status, and the overdue date is cleared. If the borrower clears all obligations entirely, the loan moves to Repaid. From any state, the loan can be moved to Written-off by an explicit write-off operation. The borrower also receives an automated overdue notification on the day the loan first becomes overdue. Calculation for an overdue loan While a loan remains overdue, the daily calculation continues to run and applies the loan’s product rules. Several things may be accrued: Accrual What it is What controls it Overdue penalty A one-time penalty for each missed payment. Accumulates on the loan as Penalties. The overdue penalty configured on the loan product. Default interest A separate interest charged on the overdue balance for every day it stays unpaid. Accumulates as Default interest. The default interest rate configured on the loan product. Regular interest Ordinary interest accrual continues on the principal balance according to the loan’s interest rate. The interest rate of the loan (fixed, or floating = prime rate plus margin). Product group dependency The product group is the lending program under which the loan was opened. It groups together loan products that share the same servicing strategy. The product group does not set the penalty or interest rates directly — those are set on each loan product inside the group — but it controls the collection-related parameters that frame the overdue period: Parameter on the product group Meaning Collection strategy Selects which recovery workflow runs when a loan in this group becomes overdue. Supported values: Default (the platform’s standard collection workflow runs) and None (no collection workflow is started — the loan stays overdue with accruals applied, but no contact tasks are created). Days in overdue before collection starts The waiting period in calendar days between the loan becoming overdue and the first contact task being created. During this delay, the loan is already overdue and continues to accrue penalty and default interest, but no Collection Manager task has been raised yet. The loan product inside the group then sets the financial parameters that are actually applied during the overdue period: Parameter on the loan product Meaning Overdue penalty A one-time penalty for each missed payment. Default interest rate A penalty rate applied daily to the overdue principal balance. In short: The product group decides whether the collection runs and when it starts. The loan product decides how much is accrued (penalties, default interest) while the loan is overdue. ### Collection flow Source: https://docs.hesfintech.com/loanbox/collection-process/collection-workflow/ Collection process The Collection process runs automatically in the background. It has three stages: Trigger and routing — the platform detects the loan is overdue, decides whether collection applies, and selects the right collection workflow. Default collection workflow — if applicable, the platform opens a collection case and runs iterative contact cycles with the borrower. Closure — the case is closed when the debt is settled, when the loan is written off after a credit officer’s decision, or when the loan is written off by some other workflow. Stage 1. Trigger and routing Step 1.1 — Loan becomes overdue. The platform’s daily check marks the loan as Overdue. An internal “Loan is in overdue” signal is raised. This is the trigger for collection. Step 1.2 — Choose the collection strategy. The platform looks at the Collection strategy configured on the loan’s product group: If the product group’s collection strategy is Default, the Default Collection workflow is started for this loan. If the product group has no collection strategy set (effectively “None”), the process ends immediately. The loan stays overdue and continues to accrue penalties and interest as configured on the product, but no contact tasks are created, and no collection case is opened. Note Today the platform supports two values for collection strategy: Default and None (no strategy). New strategies can be added through customization. Stage 2. Default Collection workflow If the product group uses the Default collection strategy, the platform runs the workflow described below. The workflow lives across two roles: the Collection Manager (who works with the borrower) and the Credit Officer (who authorizes write-offs). Step 2.1 — Wait for the configured number of days in the overdue state. The platform does not start contacting the borrower the moment the loan becomes overdue. It first waits for the number of days defined by the product group’s Days in overdue before collection starts parameter. During this wait, the loan continues to accrue penalty and default interest as described above. Step 2.2 — Open a collection case. When the wait period ends, the platform creates a collection case and links it to the loan. The case is created with a status of In progress. It carries: a unique case number (system-generated), a start date (the moment the case was opened), the linked loan, an empty list of call results that will be filled in over time, a promise-to-pay date field that is automatically derived from the most recent call result (no one types it manually). Step 2.3 — Refresh loan data. Before assigning the next contact task, the platform reloads the latest loan figures (balances, days overdue) so the operator always sees the most recent values. Step 2.4 — Assign the “Call the borrower” task to the Collection Manager. A new task is placed in the Collection Manager queue. Any user with the Collection Manager role can pick it up. The task is described in detail in the Collection task for the Back-Office user section. If a Collection Manager picks up the task but does not complete it within the configured timeout, the task is automatically returned to the queue for someone else to handle. Step 2.5 — Manager records the call result. The manager calls the borrower, picks one of three outcomes, fills in the supporting fields, and submits the form. The platform stores this as a call result on the collection case. Possible outcomes are: Got a promise to pay — the borrower has committed to repay by a specific date. Didn’t get a promise to pay — the borrower did not commit. Need to write off — the manager believes the debt is not recoverable. Step 2.6 — Branch by outcome. If “Got a promise to pay”: the platform schedules a wait until the day after the Promise to pay date the manager entered. When that day arrives, the workflow returns to step 2.3 — refresh the loan and assign the next “Call the borrower” task. If the borrower has actually paid in the meantime, the case is closed automatically before the next call is needed (see step 2.7 below). If “Didn’t get a promise to pay”: the platform schedules a wait until the Date of the next reminder entered by the manager. When that day arrives, the workflow returns to step 2.3 — refresh the loan and assign the next “Call the borrower” task. If “Need to write off”: the platform sends a Write off the loan task to the Credit Officer queue (see step 2.8). The contact loop (steps 2.3–2.6) repeats indefinitely until one of the terminal events listed in stage 3 occurs. Step 2.7 — Automatic closure on debt settlement. At any point during the contact loop, if the borrower repays the overdue debt (the platform receives a “debt has been settled” signal from the payments domain), the collection case is automatically closed with status Successful. The whole workflow stops. Step 2.8 — Credit Officer writes off the loan. If the Collection Manager selected Need to write off in step 2.5, the platform creates a Write off the loan task in the Credit Officer queue. The Credit Officer: Reviews the loan details and the full history of call results. Selects a Write-off reason from the list applicable to the borrower type (Person or Legal entity). Submits the task. The platform then writes off the loan and closes the collection case with a status of Failed. If a Credit Officer picks up the task but does not complete it within the configured timeout, it is returned to the queue. Stage 3. Closure A collection case can end in three ways: End condition Final case status Borrower repays the overdue debt (debt-settled signal received). Successful Credit Officer writes off the loan after the Collection Manager’s “Need to write off” outcome. Failed The loan is written off by some other workflow outside of collection (an external write-off signal is received). Failed Once a case reaches Successful or Failed, no further contact tasks are scheduled for that loan. These are terminal statuses. External debt-collection systems (optional) The platform supports forwarding overdue cases to an external debt-collection provider. When configured, a separate “Initiate debt collection” workflow chooses the provider for the current environment and transmits the loan data to that provider. Updates from the provider are not received automatically — the case remains closed by the same internal signals (debt settled, loan written off). Whether this integration is used at all and which provider is selected are environment-level configurations, not per-loan settings. ### Back-office collection tasks Source: https://docs.hesfintech.com/loanbox/collection-process/collection-task/ Collection task for the Back-Office user This section describes the Call the borrower task that the Collection Manager works with. It is the only task in the Collection workflow that the Collection Manager actually performs on screen. (The Credit Officer’s Write off the loan task is described separately at the end of this section.) Task appears A “Call the borrower” task appears in the Collection Manager queue: when a collection case is first opened (after the configured days-in-overdue waiting period), or whenever the previous contact loop reaches its scheduled re-contact day (the day after the promise-to-pay date, or the next reminder date). The task title shown in the queue is “Call the borrower, Loan #{loan number}”. Any user with the Collection Manager role can take the task. If the assignee does not finish it within the configured timeout, the task returns to the queue, and another manager can pick it up. Data seen by the operator The screen is split into three sections, top to bottom. Section 1 — Loan information (read-only) A summary of the loan being collected. It is read-only and is refreshed automatically with the latest values when the task opens. For a fixed-term loan, the summary card shows: Field Description Borrower Full name of the borrower, with a link to the borrower profile. Original loan amount Amount approved at origination, with the system currency suffix. Loan term Term of the loan, in days or months depending on the product. Outstanding balance Total amount still to be repaid (principal + interest + penalties + default interest). Next payment Amount of the next scheduled instalment. Date Date of the next scheduled instalment. The loan card also gives access to general information panels: General info, Product info, Application, Borrower details, Bank info, Amortization schedule, Contract, Transactions, Operations, Collateral info, Financial info. For a credit line, an equivalent loan information block is shown instead, sized to the credit-line layout. Section 2 — Call results history (read-only) A table listing every previous call recorded on this collection case, ordered from the most recent call first. Columns: Column Description Call date Date and time the call was made. Author Full name of the Collection Manager who recorded the call. Result Outcome chosen for that call (Got a promise to pay / Didn’t get a promise to pay / Need to write off). Promise to pay date Date the borrower committed to repay (only for “Got a promise to pay” outcomes). Amount Amount the borrower committed to pay, in the system currency. Comment Free-text note recorded by the manager. If no call has been recorded yet, the table is replaced by the message “No calls have been made.” Section 3 — Register call result (the operator’s input) This is where the manager enters the outcome of the current call. It is titled “Register call result”. Field Description Type Required Possible values Notes Result The outcome of the call. Dropdown Yes Got a promise to pay / Didn’t get a promise to pay / Need to write off Choosing a value reveals different supporting fields below (see the table after this one). Promise to pay date The date by which the borrower commits to pay. Date Yes (only when Result = Got a promise to pay) — The date must be in the future. Past or current dates are blocked by the date picker. Promise to pay amount The amount the borrower commits to pay, in the system currency. Number Yes (only when Result = Got a promise to pay) — Must be greater than 0 (minimum 0.01) and not greater than 40,000,000. Date of the next reminder to call the borrower The date on which the system should reassign a new “Call the borrower” task to the queue. Date Yes (only when Result = Didn’t get a promise to pay) — The date must be in the future. Comment Free-text note about the conversation. Multi-line text Yes — Maximum length: 255 characters. Upon submission, the platform automatically records the Author (the full name of the logged-in manager) and the Call date (the moment the form is submitted). The manager does not enter these fields. Result dropdown — full list of values The Result dropdown has exactly three values: Value Description Got a promise to pay The borrower acknowledged the debt and committed to repay on a specific date for a specific amount. Didn’t get a promise to pay The borrower did not commit to a payment (could not be reached, refused, asked for more time without a firm commitment, etc.). Need to write off The manager assesses that the debt cannot be recovered and the loan should be written off. Conditional fields — what each Result requires Result chosen Additional required fields Got a promise to pay Promise to pay date, Promise to pay amount, Comment Didn’t get a promise to pay Date of the next reminder to call the borrower, Comment Need to write off Comment only Available actions There is a single action button on the form: Submit. The button is disabled until all required fields for the chosen Result are filled in correctly. There is no separate “Save draft”, “Cancel”, or “Delete” action on this task. To release the task back to the queue, the manager simply leaves it untouched until the timeout expires; the platform then automatically returns it to the queue. Next steps after decisions After the manager clicks Submit: Decision (Result) What the system does next Got a promise to pay The platform records the call result on the collection case, then waits until the day after the Promise to pay date the manager entered. When that day arrives, a new Call the borrower task is placed in the queue. If the borrower repays the overdue amount before that day, the case is automatically closed as Successful instead, and no new task is created. Didn’t get a promise to pay The platform records the call result on the collection case, then waits until the Date of the next reminder the manager entered. When that day arrives, a new Call the borrower task is placed in the queue. As above, if the borrower repays first, the case is closed as Successful and no new task appears. Need to write off The platform records the call result on the collection case and creates a Write off the loan task in the Credit Officer queue. No further “Call the borrower” tasks will be created for this loan unless the Credit Officer’s task is somehow cancelled. In all three cases, the call result becomes immediately visible in the Call results table on the next “Call the borrower” task and on the Collection screen. “Write off the loan” task When the Collection Manager chooses Need to write off, a follow-up task is sent to the Credit Officer. Its title is “Write off Loan #{loan number}”. Any user with the Credit Officer role can take it. The Credit Officer screen has three sections: Loan information — the same read-only loan summary as on the Call the borrower form. Call results — the same read-only history of every call, so the officer can see why the loan was escalated. Write off the loan — a single dropdown: Field Description Type Required Possible values Notes Write-off reason The reason the loan is being written off. The list of options depends on the borrower type (Person vs Legal entity). Dropdown Yes See tables below — Write-off reason — values for Person borrowers Value Description Non-performing loan The loan is non-performing and is being written off as such. Legal decision A legal decision has resulted in the write-off. Borrower went bankrupt The borrower has been declared bankrupt. Borrower died The borrower has died and the debt cannot be recovered. Write-off reason — values for Legal entity borrowers Value Description Non-performing loan The loan is non-performing and is being written off as such. Legal decision A legal decision has resulted in the write-off. Borrower went bankrupt The legal-entity borrower has been declared bankrupt. The Credit Officer clicks Submit to confirm. The platform then: writes off the loan (status moves to Written off, with the chosen reason recorded), and closes the collection case with status Failed. After this point, no new “Call the borrower” tasks will be created for the loan, and the Collection screen will show the case as Failed. ### Overview Source: https://docs.hesfintech.com/loanbox/collateral-management/ Overview and definitions Collateral is a physical or financial asset pledged as security against a loan. Every collateral record belongs to one specific loan application. Collateral is captured during application intake, refined during verification, and kept up to date over the loan lifetime through periodic re-evaluations. Each collateral record carries: a type (e.g., real estate, vehicles) a registration number and registration date (e.g., property deed number, vehicle VIN) a description of the asset a value (current monetary worth) a valuation period (in months) — how often the value should be refreshed the latest valuation date and the next valuation date supporting documents (appraisal reports, title documents, photographs) product-specific custom fields (e.g., property address for real estate, VIN for vehicles) Collateral is the basis for the loan-to-value ratio (LTV) used during credit decisioning, and it is independently tracked over the loan lifetime so that secured exposure stays accurate. ### Collateral requirements Source: https://docs.hesfintech.com/loanbox/collateral-management/collateral-requirements/ Collateral requirements Whether collateral is collected on a given application is not a manual choice of the user — it is driven by the loan product group the borrower applied for. How it works in practice: Each product group declares whether collateral information is required and which fields make up the collateral form for that product. If the product group requires collateral, the application flow shows a step “Provide collateral information” to whoever is filling the application (borrower in the Borrower Portal, agent in the Agent Portal, or credit officer in the Back Office). If the product group does not require collateral, that step is skipped entirely and no collateral record is created for the application. As a result, collateral is product-group-driven: the same back-office team can run secured products (mortgages, auto loans, equipment finance) and unsecured products (consumer loans) side by side, and each application only collects the fields appropriate to its product. All three portals (Borrower, Back Office, and Agent) collect identical collateral fields for a given product group, so data stays consistent regardless of who filled out the application. ### Verification Source: https://docs.hesfintech.com/loanbox/collateral-management/verification-stage/ Verification stage When an application reaches verification, the Verifier opens the verification screen and reviews all application data, including the collateral block (if collateral is required for the product group). In the collateral block on the verification screen, the verifier sees the assigned-by-applicant collateral data and is required to enter (or confirm) the figures that drive secured-loan economics: Field Required Notes Value Yes Must be greater than 0 (between 0.01 and 100,000,000). Drives the LTV calculation. LTV % Auto-calculated, read-only Computed live as requested loan amount / collateral value × 100. Valuation period Optional A whole number of months between scheduled re-evaluations. Type Yes One of the five collateral types (see the Collateral list, filters, and details page). Registration number Yes Up to 255 characters. Registration date Yes Calendar date. Description Yes Up to 3,000 characters. Supporting documents Yes At least 1, at most 5 files; each file up to 20 MB. Product-specific fields As configured Whatever extra fields the product group defines (address, VIN, etc.). When the verifier approves the application, the system: Saves the collateral value and valuation period entered by the verifier. Sets the latest valuation date to today’s date (the system date — the verifier cannot back-date or future-date this). If a valuation period is set, computes the next valuation date as latest valuation date + valuation period (months). This is the date the system will use later for automatic re-evaluation. Calculates the application-level LTV from the saved value and the approved loan amount. Note Validation rule: if collateral fields are required for the product group and any are missing or invalid, the verifier sees a red warning block titled “Collateral fields required” and cannot complete the verification step until those fields are filled in. ### LTV Source: https://docs.hesfintech.com/loanbox/collateral-management/ltv/ LTV How LTV is calculated LTV is expressed as a percentage and computed using the standard formula: LTV % = Loan amount × 100 / Collateral value, rounded to two decimal places. There is one nuance about which “loan amount” is used: On the application, the LTV uses the approved loan amount. The result is stored in the application record as LTV %. In the verification screen (live preview, before the application is approved), the LTV is recalculated on the fly using the requested loan amount, so the verifier can see the impact of the value they just entered. What triggers an LTV recalculation The LTV is updated whenever any of its inputs change. In practice, this means: When the verifier enters or changes the collateral value during verification, the live LTV preview reacts immediately, and the saved LTV is updated when the verifier submits. When the system re-evaluates collateral, it does so either automatically (on the scheduled date) or manually (when initiated by a credit officer). A new collateral value produces a new loan-level LTV. When the approved loan amount changes as a result of underwriting decisions, the saved LTV reflects the latest approved amount. LTV recalculation never happens spontaneously — it is always tied to a value change or a re-evaluation event. ### Collateral list, filters and details Source: https://docs.hesfintech.com/loanbox/collateral-management/collateral-list-filters-and-details/ Collateral list, filters, and details Collateral list The back-office collateral list shows all collateral records across all loan applications. Access is granted to Verifier, Underwriter, and Credit Officer roles. The list supports paging and is sorted by creation date, newest first by default. Filters Filter Type What it does Search Free-text Searches across the collateral registration number and the loan number that the collateral is attached to. Collateral types Multi-select Filters by one or more of the five collateral types: Real estate, Vehicles, Equipment and machinery, Securities, Other. Collateral types in the dropdown (all 5 values): Value Display label REAL_ESTATE Real estate VEHICLES Vehicles EQUIPMENT_AND_MACHINERY Equipment and machinery SECURITIES Securities OTHER Other Collateral detail page Clicking a row opens the collateral detail page. The page header shows Collateral # and links to the related loan application and loan number (when a loan exists). Sections shown on the page: General information — collateral value, LTV %, valuation period, type, registration number, registration date, description, latest valuation date, next valuation date, supporting documents, and any product-specific custom fields. Loan navigation — clickable links to the loan application and the loan, when present. Actions available on the page: Re-evaluate — visible only to Credit Officers and only when the linked loan is currently active. Starts the manual re-evaluation process described on the Manual collateral re-evaluation page. If the loan is closed (no longer active), the re-evaluate action is hidden. ### Automatic re-evaluation Source: https://docs.hesfintech.com/loanbox/collateral-management/automatic-collateral-re-evaluation/ Automatic collateral re-evaluation What is automatic collateral re-evaluation The system automatically refreshes a collateral’s value on its next valuation date so that secured exposure stays current without manual intervention. The process is triggered as part of the daily processing of each active loan. Triggers for collateral re-evaluation Three conditions must all be true on a given day for automatic re-evaluation to start: The loan is active. The loan application has a collateral record attached. Today’s date matches the collateral’s “next valuation date” exactly. Information available for the user Automatic re-evaluation is mostly hands-off, but it is not fully silent: it produces a user task that a Credit Officer must complete to confirm or update the new valuation. This is the task that ends up on the Credit Officer’s task list at the start of the scheduled day. Task: “Re-evaluate collateral” (Credit Officer task, started automatically at 3:00 AM on the scheduled date). The task screen shows: A header with links to the related Loan application and Loan (clickable, opens the corresponding card). The Collateral information panel containing two sections: Collateral details with editable fields: Value (required, between 0.01 and 100,000,000) — the new collateral value. Valuation period (optional, between 1 and 999 months) — how often the next re-evaluation should happen. Collateral info — read-only summary of the existing collateral attributes (type, registration number, registration date, description, supporting documents, custom fields, latest and next valuation dates). The Collateral information panel also includes a Submit button (active only when the value is valid). When the Credit Officer submits: The system saves the new value and valuation period. The latest valuation date is set to today. The next valuation date is recomputed as today + valuation period (if a period is set). A re-evaluation event is recorded in the loan history with the new value and the re-evaluation timestamp. The loan-level LTV recalculates based on the new value. The task carries an “unassign on due date” property: if a Credit Officer claims the task and does not complete it by the due date, the task is freed up so another Credit Officer can pick it up. ### Manual re-evaluation Source: https://docs.hesfintech.com/loanbox/collateral-management/manual-collateral-re-evaluation/ Manual collateral re-evaluation What is manual collateral re-evaluation A Credit Officer can re-evaluate collateral at any time on an active loan, without waiting for the scheduled next valuation date. This is used when, for example, the market has moved sharply, an external appraisal has just been received, or the borrower has requested loan terms that depend on a fresh value. Prerequisites The user has the Credit Officer role. The loan attached to the collateral has active state. Manual re-evaluation is rejected for closed loans with the message “Reevaluate collateral is not available for closed loans”. Step-by-step workflow Step 1. Open the collateral The Credit Officer opens the collateral list, finds the relevant collateral, and clicks into its detail page. Step 2. Start the re-evaluation The user clicks the Operations dropdown in the page header and selects Re-evaluate. The system opens the re-evaluation form “Re-evaluate collateral #”. Step 3. Fill in the new values The form has two fields, both shown side by side on the left, and a read-only summary of all other collateral attributes below: Field Required Notes Value Yes New collateral value. Must be between 0.01 and 100,000,000. Valuation period Optional New re-evaluation interval, in months. Between 1 and 999. The right-hand side of the form shows two buttons: Confirm — disabled until the form is valid. Cancel — closes the form and returns to the collateral card without saving. Step 4. Confirm The user clicks Confirm. The system performs a server-side check that the loan is still active. If the loan is still active, the system: Saves the new value and (if entered) the new valuation period. Sets the latest valuation date to today. Recomputes the next valuation date as today + valuation period (months), when a period is set. Records a re-evaluation event in the loan history with the new value and the user who initiated the change. Recalculates the loan-level LTV from the new value. Returns the user to the collateral detail page, showing the refreshed values. If the loan turns out to be inactive at the moment of confirmation, the system shows the error “Reevaluate collateral is not available for closed loans” and does not save. Step 5. Result After a successful re-evaluation: The collateral now shows the new value, the new latest valuation date (today), and the recalculated next valuation date. A new entry appears in the loan event history reflecting the re-evaluation. Other staff viewing the collateral immediately see the updated figures. ### Overview Source: https://docs.hesfintech.com/loanbox/agent-portal/ Overview and definitions An Agent is a partner, merchant, or broker organization that originates loan applications on behalf of borrowers. Each agent represents a company, not a person — for example, a brokerage, a dealership, or any third-party referral partner that signs up borrowers for the lender. Key characteristics: An agent is uniquely identified by its legal name and tax number. No two agents can share either of these. An agent has its own contact details (phone, email, website), legal address, bank account for receiving partner payouts, and one or more logo files. Each agent groups one or more Agent Users — individual people who log in to the Agent Portal on behalf of that organization. An agent user only sees data that belongs to their agent. An agent is associated with a list of leads (prospective borrowers it has registered) and loan applications/loans that originated from those leads. Backoffice staff with the Partner Manager role have cross-agent visibility and are responsible for creating, editing, and inviting agents. How agents relate to other concepts: Lead — a prospective borrower registered by an agent. A lead belongs to exactly one agent. Loan Application / Loan — when a lead is invited to apply, an application is created and may turn into a loan. The originating agent stays attached to the loan throughout its lifecycle. Product group — agents can only offer product groups explicitly assigned to them. A product group defines the loan product, amount range, and other parameters. ### Agent list and filters Source: https://docs.hesfintech.com/loanbox/agent-portal/agent-list-and-filters/ Agent list and filters Who uses it. Partner Managers in the Backoffice. Purpose. Browse and search all partner organizations registered in the platform, open an agent’s detail page, or create a new agent. Columns Column Description ID Internal sequential identifier of the agent Legal name The official name of the partner organization Phone Primary phone of the agent Email Primary email of the agent Filters Filter Type What it searches Search Text input Matches the agent’s legal name, phone or email Tax number Text input Exact / partial match by tax number Sorting and actions Default sort: by ID, newest first. Default page size: 20 records per page. Actions on the list screen: Open agent — clicking a row navigates to the agent detail page. Create agent — opens the create form (described below). Agent detail screen Purpose. View the full information about a single agent and perform management actions. Header. Shows the agent’s legal name and ID, for example: Acme Brokerage #123. Top-right actions menu: Edit — opens the edit form. Invite user — starts the agent user invitation process (described below). Content tabs General Info tab Shown as four side-by-side panels: Agent info — legal name, tax number, phone, email, website, logo. Address — full legal address (country, state/region, city, street, postal code, etc.). Contact details — the contact details of the representative of the partner organization. Bank info — bank name and account number used for partner payouts. A summary header at the top of the page also displays the phone and email in larger text. Applications tab A paginated table of every loan application this agent has originated. Column Description Requested at Date and time the application was sent Number Application reference number (clickable, opens the application) Status Current status of the application Loan amount requested Amount the borrower asked for Loan term requested Term the borrower asked for Loan amount approved Amount finally approved (if approved) Loan term approved Term finally approved (if approved) Loans tab A paginated table of every loan this agent originated, with the loan number, status, issue date, maturity date, and key amounts. Column Description Issue date Date the application was disbursed Number Loan reference number (clickable, opens the loan) Status Current status of the loan Original loan amount The amount for which the loan was issued Loan term The term for which the loan was issued Outstanding balance The outstanding debt amount that the borrower must repay to close the loan Maturity date The specific date on which the final loan payment is due, meaning the loan is expected to be fully repaid and closed Users tab A list of all individual people (agent users) who have a login linked to this agent. Column Description First name First name of a user Last name Last name of a user Email Email of a user, used as a login Actions Possible actions with a user account, currently only “Re-invite” ### Creating an agent Source: https://docs.hesfintech.com/loanbox/agent-portal/creating-an-agent/ Creating an agent Who can do it. Partner Manager role. Where it starts. The “Create agent” button on the agent list screen. Step 1. Open the create form The user clicks Create agent on the agent list. The system opens the Create agent form. Step 2. Fill the agent details The user fills in the following parameters. All fields are required unless stated otherwise. Parameter Description Type Required Notes Legal name Official name of the partner organization Text Yes Up to 22 characters; multiple spaces are collapsed; must be globally unique (case-insensitive) Tax number Tax identifier of the organization Text Yes Up to 255 characters; only letters, digits, underscore, and hyphen are kept; must be globally unique (case-insensitive) Phone number Primary phone of the agent Phone Yes Digits only; an optional leading + is allowed Email Primary email of the agent Email Yes Up to 132 characters; lowercased; must match a standard email pattern Website Agent’s website URL URL Yes Up to 255 characters Logo Logo image of the agent File upload Yes Allowed types: JPG, JPEG, PNG, SVG; max size 20 MB Step 3. Fill in the address The user fills in the structured address (country, state/region, city, street, postal code, etc.) in the Address panel. Step 4. Fill in the contact details The user enters the contact details for the representative of the partner organization. Step 5. Save The user clicks Save. The system: Validates every field. If any required field is empty, invalid, or duplicates another agent’s legal name / tax number, an inline error message is shown, and saving is blocked. Stores the agent record. Opens the newly created agent’s detail page. The user can also click Cancel at any moment to close the form without saving. Note At this point, the agent has no users yet — it is just a partner organization profile. Inviting a user is a separate action (see “Invite an agent user” below). Bank account details are not collected on the create form; they are filled in later as part of the invitation workflow. ### Editing an agent Source: https://docs.hesfintech.com/loanbox/agent-portal/editing-an-agent/ Editing an agent Who can do it. Partner Manager role. Where it starts. The Edit button in the actions menu on the agent detail page. Step 1. Open the edit form The user clicks Edit on the agent detail page. The system opens the Edit agent form pre-filled with the current values. Step 2. Change any of the editable parameters All fields visible on the create form are editable here, with the same validation rules: Legal name, tax number, phone, email, website, logo Full address Contact details Bank info (bank name, account number) — once present, can be edited here at any time Step 3. Save The user clicks Save. The system: Validates every field, including the global uniqueness of the legal name and tax number (excluding the current agent’s own values). Persists with the changes. Returns the user to the agent detail page with the updated information. The user can also click Cancel to discard the changes. ### Inviting an agent user Source: https://docs.hesfintech.com/loanbox/agent-portal/invite-an-agent-user/ Invite an agent user This process gives a real person their first login to the Agent Portal on behalf of an agent organization. Who can do it. Partner Manager role. Where it starts. The Invite user action in the menu on the agent detail page. Step 1. Open the invitation form The user clicks Invite new user on the agent detail page. The system opens the Invite agent’s user form, displaying the agent’s legal name and ID at the top. Step 2. Enter the new user’s email The user fills the Email field. This email becomes the future agent user’s username. Parameter Description Type Required Notes Email Email of the person to invite Email Yes Up to 132 characters; lowercased; must match a standard email pattern Step 3. Send the invitation The user clicks Send invitation. The system runs the invitation process automatically: Generates a temporary password. Checks whether a user with this email already exists in the security system: If no, the system creates a new user account linked to the agent and sets the temporary password. If yes, the system updates the existing user’s temporary password and signals any previously running invitation for that user to terminate (so only one active invitation exists at a time). Sends an invitation email to the entered address containing the credentials. Checks whether the agent already has bank account details on file: If yes, the invitation process completes here. If no, the system assigns a task to the newly invited agent user titled “Fill bank account details” (visible in the Agent Portal’s Tasks list as soon as the user logs in). Step 4. The invited user fills in bank account details (if required) After logging in for the first time, the invited user opens the task and fills in the bank account form (bank name, account number). Upon confirmation, the system saves the bank account to the agent record, and the invitation is complete. Result. The invited person can log in to the Agent Portal with the credentials from the invitation email and start working on behalf of the agent. The agent now has the bank account information required to participate in loan disbursement. The user can also click Cancel on the invitation form to abort before sending. ### Re-invite an agent user Source: https://docs.hesfintech.com/loanbox/agent-portal/re-invite-an-agent-user/ Re-invite an agent user Reinvite is used when the previously sent invitation needs to be reissued — for example, the recipient lost the email, the temporary password expired, or the previous invitation was never completed. Who can do it. Partner Manager role. Where it starts. The re-invite action on the user row inside the Users tab on the agent detail page. Step 1. Open the re-invite form The system opens the Re-invite agent’s user form. The user’s email is already filled in and cannot be changed (the email field is read-only on this form). Step 2. Send the new invitation The user clicks Send invitation. The system runs the same invitation flow as a fresh invite (generate a new temporary password, update or create the security account, send a new invitation email, ask for bank account details if missing). Any previously running invitation for the same person is automatically interrupted, so the new credentials are the only valid ones. Result. The recipient gets a new invitation email with new credentials and can log in again. Previous credentials and any in-progress earlier invitations are no longer valid. The user can click Cancel to abort. ### The Agent Portal Source: https://docs.hesfintech.com/loanbox/agent-portal/the-agent-portal/ The Agent Portal The Agent Portal is the web application used by employees of the agent organization. After logging in (using the credentials provided in the invitation email), the user has access to data scoped strictly to their agent: they can only see leads, applications, and loans that belong to their organization. The portal is organized into the following modules. Module: Tasks Purpose. A unified to-do list of every step the system is currently waiting for the agent user to complete. What appears here. Any user task assigned to the agent user by an active business process. The most common ones are: Fill in bank account details — appears at the end of the invitation process when the agent does not yet have bank account information. Fill / continue a loan application — when a lead has been invited, but the application data still needs to be completed by the agent on behalf of the borrower. Provide additional borrower information — when a running application needs more borrower data (personal info, address, employment, company info, collateral, etc.) and the agent is the channel responsible for collecting it. Confirm loan conditions or review pending application — interactive checkpoints inside the origination flow. Manual KYC / manual bank details input — operational checkpoints when an external check could not be performed automatically. Each task entry shows its title (a human-readable name like “Fill bank account details”), the entity it relates to (the agent itself, a specific lead, or a specific application), and the date it was created. Clicking a task opens the corresponding form so the user can complete the work. When the user submits the form, the task is removed from the list, and the underlying process continues. Module: Applications Purpose. A list of every loan application originated by this agent, with full filtering and the ability to drill down into a single application. Filters available: Filter Type Notes Statuses Multi-select Filters by one or more application statuses Requested from Date / time Lower bound on the request timestamp Requested to Date / time Upper bound on the request timestamp Search Text Matches application number or borrower’s full name, phone, or email Sorting and pagination: Default sort: by request date and time, newest first. The list is paginated; the user can navigate pages and choose page size. Each row shows the application number, borrower name, current status, product group, and request date. Detail view. Clicking a row opens the Loan application detail page. This page shows the application number, current status, borrower details, requested vs. approved loan parameters, and the full origination history. The agent can review every stored field but cannot modify a submitted application — additional information is gathered through tasks. Module: Loans Purpose. A list of every loan that originated from this agent’s applications, along with the operational history of each loan. Filters available: Filter Type Notes Statuses Multi-select Filters by one or more loan statuses Issue date from Date Lower bound on the loan issue date Issue date to Date Upper bound on the loan issue date Search Text Matches loan number or borrower’s full name, phone, email, or product code Loan types Multi-select Two values: Fixed-term loan and Credit line Sorting and pagination: Default sort: by creation date, newest first. The list is paginated. Each row shows the loan number, borrower name, status, amount, term, and product group. Loan detail view. Clicking a row opens the loan card. The layout depends on the loan type: For a fixed-term loan, the page shows general loan info, the amortization schedule, contract details, and operations. For a credit line, the page shows credit-line-specific information (limit, used and available amounts, billing cycles, etc.). The agent can read loan data but cannot edit it through this module. Module: Leads Purpose. Manage prospective borrowers — register them, edit their contact details, and turn them into a loan application. List screen. A paginated list of every lead belonging to the agent, with a free-text search across the lead’s full name, phone, and email. Each row shows first name, last name, phone number, and email address. Available actions on the list: Create lead — open the create-lead form. Open a lead — click a row to navigate to the lead’s detail page. Create a lead Step 1. Open the form. The user clicks Create lead. Step 2. Fill in the lead’s details. The user fills in: Parameter Description Type Required Notes First name Lead’s first name Text Yes Up to 84 characters; multiple spaces are collapsed Last name Lead’s last name Text Yes Up to 84 characters; multiple spaces are collapsed Phone Lead’s phone Phone Yes Digits only; optional leading + Email Lead’s email Email Yes Up to 132 characters; lowercased; must match a standard email pattern Step 3. Save. The user clicks Save. The system validates the fields, checks that the phone+email pair is not already used by another lead of the same agent, and stores the lead. Validation: phone and email together must be unique within a single agent’s leads (different agents may have leads with the same contacts). Lead detail screen The detail screen displays the lead’s full name (header), phone, and email. Available actions: Send application — start the loan application process for this lead (described below). Edit — open the edit-lead form. Edit a lead The user can change their first name, last name, phone number, and email address. The same uniqueness rule applies (phone+email must remain unique within the agent). Send loan application from a lead See the Agent Invitation to a Lead section. Module: Profile Purpose. Enables the agent user to view and update their agent organization’s profile. View screen. Displays the agent’s general info (legal name, tax number, phone, email, website, logo), address, contact details, and bank info. Read-only. Available action: Edit — open the update-profile form. Update profile. The form contains the same panels as the view (general info, address, contact details, bank info). The user changes any field, then clicks Save. The system enforces: The same validation rules as the Backoffice create/edit forms (legal name uniqueness, tax number normalization, email pattern, etc.). An ownership check: the agent user can only update their own agent — a profile belonging to another agent cannot be modified through self-service, even if its identifier is included in the request. The user can click Cancel to discard changes. ### Overview Source: https://docs.hesfintech.com/loanbox/borrower-portal/ Overview and definitions The Borrower Portal is a self-service web application that gives borrowers — both individual persons and legal entities — full visibility into their relationship with the lending platform. Through the portal, borrowers can apply for loans, monitor application status, manage active loans, track transaction history, and submit loan modification requests. All actions are strictly scoped to the authenticated borrower’s own data; no cross-borrower access is possible. The portal is one of four user-facing channels on the LoanBox platform. It is designed specifically for end customers and operates independently from the Back Office and Agent Portals. Each borrower has a dedicated account in the Borrower identity realm, which keeps their credentials and access rights completely separate from internal staff accounts. The platform supports two borrower types, depending on the deployment configuration: individuals and legal entities (companies). Both types have access to the same portal modules, although the information collected during onboarding differs between them. ### Signing in Source: https://docs.hesfintech.com/loanbox/borrower-portal/signing-in/ Signing in The Borrower Portal uses OAuth 2.0 with the Authorization Code flow, backed by a dedicated Keycloak identity realm called BorrowerRealm. The portal client identifier is borrower-portal. Authentication can be configured in two modes depending on the deployment: Phone-based (SMS flow): The borrower’s phone number serves as the username. Keycloak stores the phone number both as the username and as a verifiedPhoneNumber attribute. Email-based flow: The borrower’s email address serves as the username and is stored as both the Keycloak username and email. A borrower account is created automatically during the first loan application, at which point a Keycloak user is provisioned in the BorrowerRealm. On subsequent visits, the borrower signs in using the same credential (phone or email) used during their initial application. ### Modules Source: https://docs.hesfintech.com/loanbox/borrower-portal/modules/ Modules Applications The Applications module displays all loan applications submitted by the borrower. Applications are listed in reverse chronological order by submission date. Each application shows: Application number — a unique human-readable identifier Status — current stage in the application lifecycle Requested amount and Requested term Approved amount and Approved term (once a decision is made) Interest rate (approved) Product group Application statuses visible to borrowers: Status Meaning On KYC Identity verification in progress Account verification Bank account verification in progress Verification Manual review of borrower data by the lender Update requested The borrower must provide additional or corrected information Underwriting Manual credit decision in progress Approved Application approved; contract is ready for signing Declined Application rejected Canceled Application withdrawn by the borrower or timed out Disbursed Loan has been issued When an application reaches Approved status, the borrower can view the contract document and proceed to signing. While the application is in “Update requested” status, the borrower must update the flagged sections and resubmit by the given deadline; otherwise, the application is automatically declined. The borrower can cancel an active application at any time before a final decision is reached. Loans The Loans module displays all loans issued to the borrower. Two loan types are supported: fixed-term loans and credit lines. Fixed-term loans — loans with a defined repayment schedule and maturity date. The detail view shows: Loan number, issue date, maturity date Interest rate, calculation type (e.g., Annuity, Linear) Current outstanding balance Next payment amount and next payment date Annual Percentage Rate (APR) Amortization schedule with payment dates, payment amounts, principal and interest breakdown Transaction history Contract document Bank account linked for repayments Credit lines — revolving credit facilities. The detail view shows: Credit limit and available credit limit Borrowed amount Next payment amount and due date Billing cycles Transaction history Contract document Drawdown freeze date Loan statuses visible to borrowers: Status Meaning Pending Loan created; disbursement not yet processed Active Loan is in good standing Overdue Scheduled payment was missed Repaid All obligations have been fulfilled Written-off Loan has been written off by the lender Processing A payment or operation is currently being processed From the Loans module, the borrower can initiate the following operations (availability depends on loan type and status): Initiate payment — make a repayment toward the loan. Get drawdown (credit lines only) — request a disbursement from the available credit limit. Request loan adjustment — submit a restructuring request (see Requests module). Change bank account — update the bank account linked to the loan for repayments. Transaction history entries show the date, type (Disbursement or Repayment), amount, and processing status for each monetary movement on the loan. Activities The Activities module surfaces pending tasks that require the borrower’s action. These tasks are generated by the platform’s process engine as part of ongoing workflows. A task appears here whenever the borrower needs to take an action to move a process forward. Tasks that may appear in the Activities module: Task When it appears Confirm loan conditions Before a new application is submitted, confirm the loan amount, term and payment frequency Provide personal details Data collection step during application intake Provide employment info Employment information required for individual person borrowers Provide address Address required during application Provide bank info Bank account details required for disbursement and repayments Provide company info Company information required for legal entity borrowers Provide company’s representative info Representative details required for legal entity borrowers Provide further info Additional information requested by the lender Provide collateral info Collateral details for secured loan applications Verify your identity (KYC) Identity verification via a configured KYC provider (e.g., Jumio, Ondato) Verify your bank account Bank account verification via an open banking provider Track verification status Informational waiting task during manual verification Update the application Correct or supplement application data after a verification return Review the contract Review the loan contract before signing Sign contract Sign the loan contract using OTP or e-signature Wait for an offer Waiting state while the lender prepares the contract Update the loan adjustment request Provide additional information after the lender returns an adjustment request Wait for a change of bank account Waiting state while the lender processes a bank account change Initiate drawdown Submit a credit line drawdown request Initiate payment Submit a manual loan repayment Tasks disappear from the Activities module once the borrower completes them or once the process engine moves the workflow past that step. Requests The Requests module shows all loan adjustment requests the borrower has submitted. These requests allow borrowers to apply for modifications to the terms of an active loan. Three types of restructuring are available (subject to eligibility, decided by the lender): Restructuring option Description Extend maturity date Extend the loan repayment period (available when future payment periods remain) Amend interest rate Apply a new interest rate to the loan Apply payment holiday Suspend payments for a specified number of periods (not available for payday-type loans) To submit a new request, the borrower selects a loan, describes the requested adjustment, and may attach supporting documents. Only one active (non-final) request per loan is permitted at a time. Request statuses: Status Meaning For review Submitted; awaiting lender review Under review Lender is currently reviewing the request Update requested Borrower must provide additional details or clarification Approved Lender has approved the restructuring; amendment agreement being prepared Signing Amendment agreement is ready for the borrower’s signature Applied Restructuring has been applied to the loan Declined Request was rejected by the lender Once a request reaches Signing status, the borrower must sign the amendment agreement by the specified deadline. If the deadline is missed, the request is automatically declined. The detail view of each request shows the request number, submission date, status, restructuring option, description, any attachments, the amendment agreement document (when available), and the decline reason if applicable. My Profile The My Profile module shows the borrower’s personal or company information collected throughout the onboarding journey. All fields on this screen are read-only — they reflect the data the borrower provided in earlier application steps, plus any data updated by back-office staff. The structure of the profile depends on the borrower type. Individual person profile The profile is organized into four tabs: Tab Content Personal info Full name (first name, middle name, last name), tax number, phone, email, date of birth, citizenship, residential address Bank info Bank account details linked to the borrower (bank title, account number) and general financial information Employment info Employer, position, employment status, monthly income and related employment details captured during onboarding ID document Identity document type, number, issue date, expiration date and uploaded scans/photos Legal entity profile The profile is organized into three tabs: Tab Content Company info Legal name, corporate type, industry, registration number, registration date, website, tax number, phone, email, months in operation, registered address Representative info Personal info and ID document of the company’s authorised representative Bank info Company bank account details and general financial information The portal does not provide an in-place edit form for profile data. If a borrower needs to correct profile information, the lender’s back-office staff applies the change on the borrower’s behalf, or the borrower is sent back to the relevant data-collection step during an application or update process. Once the changes are applied, the profile screen automatically displays the updated values. Restore Old Account The Restore Old Account feature is available to individual borrowers who have lost access to the phone number they used to register on the platform. It lets them link their existing borrower account — including past applications and loans — to a new phone number for signing in. The feature is offered as an option during sign-in/onboarding for individual persons only. Legal entities are not eligible. Form fields The restore form has a single input: Field Description Type Required Validation Old phone number The phone number previously used to register the account being restored Phone number Yes Must contain digits only (an optional leading + is allowed). No other characters are permitted. The user submits the form with a Save and next button. End-to-end process flow Step 1. Open the restore form. The borrower opens the Restore Old Account form in the sign-in/onboarding flow. The system shows a short explanatory message and the Old phone number field. Step 2. Enter the old phone number. The borrower types the phone number that was used to register the previous account and clicks Save and next. The form is validated locally; non-digit characters trigger an error. Step 3. System checks for duplicate processes. The system checks whether the borrower already has a Restore Old Account procedure in progress. If yes, the new attempt is silently discarded, and the existing procedure remains active. Step 4. The system runs an identity (KYC) check. The system runs an identity check against the configured KYC provider for the borrower’s new phone number. If the check fails, the borrower sees the message Sorry, we cannot verify your account, and the procedure ends. Step 5. Old account lookup. The system searches for an existing borrower record matching the supplied old phone number. If no account is found, the borrower sees Sorry, we cannot verify your account, and the procedure ends. If an account is found, the procedure continues. Step 6. Manual verification by the lender. The borrower sees the message Let us verify your account; we are checking your request; it may take a while. In parallel, a verification task is created for the lender’s verifier team. The verifier reviews the request and either approves or declines. Step 7a. Verifier approves. The system reassigns the past applications and loans of the old account to the new account. If the new account does not yet have an email address, the email address from the old account is copied over. The borrower receives a phone-number-changed notification. The procedure completes with Old account has been restored. Step 7b. Verifier declines. The new account is added to the blacklist. The borrower’s access restoration request is rejected. The procedure ends with Old account has not been restored. Step 8. The result. When the procedure completes successfully, the borrower signs in with the new phone number and immediately sees the full history (applications, loans, contracts) of the previous account. ### Borrower operations: detailed flows Source: https://docs.hesfintech.com/loanbox/borrower-portal/borrower-operations-detailed-flows/ Borrower operations: detailed flows This section documents the four most frequently used borrower operations in detail: form fields, validation rules, and the end-to-end process flow. Initiate Payment Initiate Payment lets a borrower submit a repayment toward an active loan — both fixed-term loans and credit lines. The borrower starts it from the loan detail view. Form fields Field Description Type Required Possible values Default Notes Full repayment Tick this to repay the full outstanding balance at once instead of paying a partial amount Checkbox No On / Off Off When ticked, Payment amount is hidden and Payoff amount as of today is shown instead Payment amount The amount the borrower wants to pay Number (currency) Yes (when Full repayment is off) Greater than 0; up to 100,000,000; up to 2 decimal places Empty Hidden when Full repayment is on Payoff amount as of today The system-calculated total needed to close the loan as of today (principal + interest + fees) Number (currency, read-only) — — Calculated by the system Shown only when Full repayment is on Payment method How the funds are taken Radio Yes Use saved bank account; Pay with card or bank Use saved bank account When “Use saved bank account” is selected, a confirmation message shows which masked account will be debited Buttons Confirm — submit the payment. Cancel — discard and return to the loan card. End-to-end process flow Step 1. Open the payment form. The borrower clicks Initiate payment on the loan card. The system shows the payment form pre-populated with the loan reference. Step 2. Choose the amount. The borrower either enters a custom Payment amount or ticks Full repayment. In the latter case, the system automatically fills the payoff amount and locks the field. Step 3. Choose the payment method. The borrower selects Use saved bank account (an automated withdrawal from the bank account linked to the loan) or Pay with card or bank (an interactive payment session). The form shows a description matching the choice. Step 4. Confirm. The borrower clicks Confirm. The system validates that the loan is still active and that no other payment is already being processed for the same loan. If another payment is in flight, the borrower sees an error, and the operation is rejected. If the loan is no longer active, the operation is rejected. Step 5. The system processes the payment. The system creates a payment transaction and routes it to the configured payment provider. For “Use saved bank account,” the borrower then sees a “Payment initiated” confirmation screen and the transaction proceeds in the background. For “Pay with card or bank,” the borrower is taken through the provider’s interactive payment flow. Step 6. Result. When the provider confirms the payment, the system records the transaction against the loan, updates the outstanding balance, and sends the borrower an email confirmation. The transaction appears in the loan’s Transaction history with status Active until settled, then Completed. Note If the provider declines the payment, the transaction is marked as failed, and the loan balance is unchanged. Get Drawdown Get Drawdown lets a borrower request a disbursement from an active credit line. It is available only on credit-line loans where the drawdown freeze date has not been reached and a credit balance remains. The operation is launched from the credit-line detail view. Form fields Field Description Type Required Possible values Default Notes Available credit limit The remaining amount the borrower can still draw Number (currency, read-only) — — Calculated by the system Shown for reference Service fee The service fee rate that applies to this drawdown Percentage (read-only) — — From loan product Shown for reference Establishment fee The fixed establishment fee that will be deducted from the drawdown Number (currency, read-only) — — From loan product Shown for reference Drawdown amount The amount the borrower wants to draw Number (currency) Yes Greater than 0; up to 2 decimal places; cannot exceed the available credit limit minus establishment fee and service fee Empty Validation error appears if the entered amount exceeds the allowed maximum Supporting documents Optional documents proving the purpose of the drawdown File upload No Image and document files up to 20 MB each Empty Multiple files allowed Buttons Confirm — submit the drawdown request. Cancel — discard and return to the loan card. End-to-end process flow Step 1. Open the drawdown form. The borrower clicks Get drawdown on the credit-line card. The system shows the form with the available credit limit, applicable service fee, and establishment fee already filled in. Step 2. Enter the amount and attach documents. The borrower enters the Drawdown amount and optionally uploads supporting documents. The form validates that the amount stays within the available limit. Step 3. Confirm. The borrower clicks Confirm. The system validates: the credit line is still active the drawdown freeze date has not been reached the requested amount does not exceed the available credit limit no other drawdown is currently in progress on the same credit line. If any check fails, the system displays the relevant error and stops the operation. Step 4. System initiates disbursement. The system selects the disbursement channel based on the loan product (either automatically via the configured payment provider or manually upon lender confirmation). For automatic disbursements, the funds are queued for transfer to the borrower’s linked bank account; for manual disbursements, a back-office task is created for the lender to confirm. Step 5. Confirmation screen. Once the disbursement is initiated, the borrower sees a “Drawdown initiated” screen confirming the amount, the linked credit line, and that the funds will arrive within 1–3 business days. Step 6. Result. When the disbursement provider confirms the transfer, a Disbursement transaction is recorded on the credit line, the borrowed amount and available credit limit are updated, and the borrower receives an email confirmation. Note If the disbursement fails, the borrower can retry from the credit-line card. Change Bank Account Change Bank Account lets a borrower replace the bank account linked to a loan — that is, the account from which scheduled repayments will be debited. The operation is launched from the loan detail view. Form fields The change request itself is a simple confirmation form. The new account details are not entered manually — they are captured automatically by the open-banking provider during step 3 of the flow. Field Description Type Notes Confirmation message Explanation that all future withdrawals will be charged to the new bank account Static message Read-only Loan reference The loan the change applies to Hidden Filled automatically from the loan the borrower started from Buttons Send — confirm intent and start the bank-account change procedure. Cancel — discard and return to the loan card. End-to-end process flow Step 1. Open the change form. The borrower clicks Change bank account on the loan card. The system displays the confirmation message “Are you sure you want to change your bank account?” and warns that future repayments will be debited from the new account. Step 2. Confirm intent. The borrower clicks Send. The system cancels any previously started (still-unfinished) change procedure for the same loan and starts a new one. Step 3. Verify the new bank account via open banking. The system redirects the borrower to the configured open banking provider (Plaid, Flinks, Illion, or Acquired, depending on the deployment). The borrower logs in to their bank, selects the account they want to use going forward, and authorizes the platform to retrieve the account details. If the borrower abandons or cancels the provider session, the procedure is canceled, and the existing bank account remains unchanged. Step 4. Wait for the lender’s approval. The system displays the “Wait for a change of bank account” task in Activities while a credit officer reviews the new account details. The borrower can return to the portal at any time; the task auto-updates every 10 seconds. If the lender does not respond within 24 hours, the procedure is automatically canceled. Step 5a. Lender approves. The new bank account replaces the previous one on both the loan and the borrower profile. The borrower receives a “Bank account change approved” notification. The loan card now shows the new account. Step 5b. Lender declines. The previous bank account remains in place. The borrower sees the message “Sorry, your request to update your bank account has been rejected” and receives a corresponding notification. The borrower can start a new change request afterward. Request Loan Adjustment Request Loan Adjustment lets a borrower ask the lender to modify the terms of an active loan. The lender ultimately selects which of the three restructuring options is applied (Extend maturity date, Amend interest rate, or Apply payment holiday) and runs the calculations; the borrower’s role is to submit a written request with optional attachments. The operation is launched from the loan detail view. Form fields The borrower’s request form captures only narrative information: Field Description Type Required Validation Notes Loan reference The loan the request applies to Hidden — — Filled automatically; the loan number and current status are also displayed read-only at the top of the form Description A free-text explanation of what the borrower wants to change and why Multi-line text Yes Maximum 3,000 characters The lender uses this text to decide which restructuring option to apply Attachments Supporting documents (e.g. proof of hardship, payslips, statements) File upload No Each file up to 20 MB Multiple files allowed The form blocks submission if the borrower already has an active request for the same loan (status For review, Under review, Approved, or Signing). In that case, the form shows the message “You already have a loan adjustments request. Please wait until the final decision.” The three restructuring options — and the type-specific fields associated with each — are not chosen by the borrower. They are selected by the lender’s credit officer when reviewing the request: Restructuring option What the lender configures What the borrower sees Extend maturity date New term (in periods) and the approach used to extend The updated maturity date and the recalculated amortisation schedule Amend interest rate New interest rate type and new interest rate The updated interest rate and the recalculated amortisation schedule Apply payment holiday Number of periods during which payments are suspended The suspended periods on the amortisation schedule Buttons Send — submit the request. Cancel — discard and return to the loan card. End-to-end process flow Step 1. Open the request form. The borrower clicks Request loan adjustment on the loan card. The system shows the form with the loan reference and current loan status pre-filled. Step 2. Describe the request and attach documents. The borrower types the description of the requested change in the Description field and optionally uploads supporting documents. Step 3. Send. The borrower clicks Send. The system validates that no other active request exists for the same loan. If the check passes, the request is saved with the status “For review” and appears in the Requests module. Step 4. Lender review. A credit officer reviews the request. The system status changes to Under review. The officer decides one of three outcomes: Approve — selects the restructuring option and fills in the type-specific parameters. The system recalculates the amortization schedule and generates an amendment agreement. Request updates — sends the request back to the borrower with a reason (see step 5). Decline — closes the request with a decline reason. Step 5. Update requested (optional). If the lender asks for more information, the request status changes to Update requested, and a task titled “Update the loan adjustment request” appears in the borrower’s Activities. The borrower has 72 hours to update the description and attachments and resubmit; if the deadline passes, the request is automatically declined. Step 6. Signing. Once the lender approves and the amendment agreement is ready, the request moves to the Signing status. A signing task appears in the borrower’s Activities. The borrower reviews the new schedule and signs the amendment agreement within the configured deadline. If the borrower signs in time, the request moves to Approved and then to Applied once the new terms take effect on the loan. If the borrower does not sign before the deadline, the request is automatically declined. Step 7. Result. When the request reaches the Applied status, the loan operates under the new terms. When the request reaches status Declined, the loan terms remain unchanged, and the decline reason is shown on the request detail screen. ### Borrower operations summary Source: https://docs.hesfintech.com/loanbox/borrower-portal/borrower-operations-summary/ Borrower operations summary All operations available to a borrower across the portal: Operation Where Description View loan applications Applications Browse all submitted applications with status and key parameters View application detail Applications See full application details including schedule, contract and attachments Cancel application Applications Withdraw an active application before a final decision Sign contract Applications Sign the loan contract to finalise approval and trigger disbursement Update application Activities Correct or supplement application data when returned by the lender Provide personal / company information Activities Complete data collection steps during onboarding Complete identity verification Activities Pass KYC verification via the configured provider Verify bank account Activities Complete bank account verification via open banking or manual input View loans Loans Browse all active and historical loans View loan detail Loans See loan balance, schedule, transactions, and contract Initiate payment Loans Submit a repayment toward a fixed-term loan or credit line Get drawdown Loans Request a disbursement from an available credit line Change bank account Loans Request an update to the bank account linked to a loan Submit loan adjustment request Loans Request restructuring of an active loan (extend term, amend rate, payment holiday) Update loan adjustment request Activities Provide additional information when the lender returns a request for revision Sign amendment agreement Activities Sign the amendment agreement to apply an approved loan restructuring View requests Requests Browse all loan adjustment requests and their statuses View request detail Requests See full request details including amendment agreement and decline reason View profile My Profile View personal or company profile information (read-only) Restore old account Sign-in flow Restore a previous borrower account when the registered phone number is lost (individuals only) Update portal settings Settings Change portal preferences such as language ### Overview Source: https://docs.hesfintech.com/loanbox/settings/ Overview and definitions Settings is the section of the back office where staff manage the platform-wide configuration that governs business rules, pricing, public-facing tools, and communications. Changes made here can affect every loan, every product group, every borrower-facing surface, and every outgoing message. The Settings area covers the following sections: Section Purpose Interest rate The system-wide prime rate used by all floating-rate product groups and products. License info The active license that authorizes the platform to operate. Landing page calculator The boundaries and parameters for the public loan calculator on the landing page. Scoring model The internal credit-scoring logic (DMN decision tables) used to evaluate loan applications during origination. Document templates The library of contract and amendment-agreement templates linked to product groups. Notifications The library of message templates used for borrower and agent communications. Most settings can be viewed by Verifier, Underwriter, Credit Officer, and Collection Manager. Editing is restricted to Credit Officer (and Underwriter, where noted), and every change is fully audited. ### Interest rate setting Source: https://docs.hesfintech.com/loanbox/settings/interest-rate-setting/ Interest rate setting The Interest rate setting holds the prime rate—a single, system-wide percentage that the platform uses as the base for every floating-rate product. Each interest rate record contains: Prime rate, %—the new prime rate value (between 0 and 999, with decimals). Effective date—the date on which the new rate becomes active. Note Interest rate records are append-only: the system never overwrites a previous rate. Each scheduled change is a new record with its own effective date, and the audit history retains every past value. Setting dependencies Depends on: nothing inside the platform. Credit officers set a new prime rate based on regulatory decisions, central bank announcements, or internal pricing policies. Affects: All product groups marked as floating-rate, and through them, all loan products inside those product groups. When a new prime rate becomes effective, the system propagates the change to every floating-rate product group and product in a single atomic update—there are no partial updates. Fixed-rate product groups are never affected by a change in the prime rate. Existing active loans with a floating rate will have their rate adjusted on the effective date based on their margin. How to view The Interest rate settings screen shows the details panel with the current and most recent scheduled prime rates. Roles allowed: Verifier, Underwriter, Credit Officer, Collection Manager. Edit process Only Credit Officers can edit the interest rate. Step 1. Open the edit form From the Interest rate settings page, the user clicks Edit. → The system opens “Edit interest rate settings” prefilled with the latest rate and the effective date. Step 2. Enter the new rate Field Required Notes Prime rate, % Yes Numeric, between 0 and 999. The new prime rate. Effective date Yes Calendar date. Cannot be today or in the past—the picker disables today and earlier dates. Step 3. Save The user clicks Save. Step 4. System processes the change The system runs the following checks and outcomes: No changes—if the new rate equals the current rate for the same effective date, the system finishes silently with “No changes to update”. Otherwise—the system: Cancels any previously scheduled prime-rate change that has not yet taken effect. Saves the new interest rate record with its effective date. Waits until the effective date begins. On the effective date, propagates the new rate to all floating-rate product groups and products in a single atomic operation. Marks the change as completed. A scheduled change can be canceled by triggering the cancellation signal before the effective date—the pending record is removed, and the previous prime rate continues to apply. Clicking Cancel during edit closes the form and returns to the settings page without saving. ### License info setting Source: https://docs.hesfintech.com/loanbox/settings/license-info-setting/ License info setting The License info setting is the screen where the active platform license is registered and inspected. A platform license authorizes the deployment to operate (e.g., for a tenant, environment, or region) and carries the following: License key—the encoded license content (up to 1,000 characters). Description—human-readable description of the license. Organization—the organization the license is issued to. Type—license type. Version—license version. Creation date—when the license was created. Purchase date—when it was purchased. Expiry date—when it stops being valid. All fields except the license key are read-only on the screen—they are decoded from the license content itself. Setting dependencies Depends on: the license file or key issued by the platform’s licensing authority (typically generated outside the system and provided to operations). Affects: The platform’s overall operational status. An invalid or expired license can cause platform features to be unavailable. Visibility of license-restricted features. How to view The License page shows the active license attributes (description, organization, type, version, creation date, expiry date, and purchase date) in read-only fields. Edit process The license is updated by replacing the active license key with a new one. Step 1. Open the License page. Step 2. Enable the license editor The user ticks the Set license toggle. → The system reveals the License input field. Step 3. Paste the new license key Field Required when “Set license” is checked Notes License Yes Up to 1,000 characters. Receives the encoded license key provided by the licensing authority. Step 4. Save The user clicks Save. → The system validates the key and, if valid, decodes it. The decoded description, organization, type, version, creation date, expiry date, and purchase date appear in the read-only block below. If the key is invalid, the system shows a validation error, and the previous license remains active. After saving, the platform operates under the newly registered license. ### Landing page calculator setting Source: https://docs.hesfintech.com/loanbox/settings/landing-page-calculator-setting/ Landing page calculator setting The Landing page calculator setting controls the public-facing loan calculator that potential borrowers use on the landing page to preview a possible loan. The calculator is the very first interactive surface a prospective customer touches, so its boundaries directly shape who can apply. There is exactly one landing page calculator configuration in the system. Updates modify this single record rather than creating new ones. Parameters The calculator is described by parameters grouped into three panels. Loan amount Parameter Range Min amount 0.01–99,999,999.99. Must not exceed Max amount. Max amount 0.01–99,999,999.99. Must not be smaller than Min amount or smaller than the amount selection step. Amount selection step At least 1; cannot exceed Max amount. Loan terms Parameter Range Min loan term 1–999. Must not exceed Max term. Max loan term 1–999. Must not be smaller than Min term. Period type Depends on Calculation type—see the table below. Period type values, by calculation type Calculation type Available period types PDL (Payday Loan) Days Annuity installment Days, Months, Years Linear principal repayment installment Days, Months, Years Revolving credit line Months Non-revolving credit line Months Rate and payment Parameter Notes Interest rate, % Between 0 and 999. Calculation type See full list below. Cannot be changed after the calculator has been initially set. Payment frequency (*required except PDL) Hidden when calculation type is PDL. See full list below. Calculation type Value Description PDL Payday loan—single repayment at the end of the term. Annuity installment Equal periodic payments combining principal and interest. Linear principal repayment installment Equal principal portions plus declining interest. Revolving credit line Credit line that can be drawn down and repaid repeatedly. Non-revolving credit line Credit line drawn down once and repaid. Payment frequency There are the following payment frequency values based on calculation type: Fortnightly Weekly Monthly Quarterly Note For credit-line calculation types, only Monthly is offered. Setting dependencies Depends on: the catalog of supported calculation types and period types in the platform. Affects: The public landing page: the calculator widget reads these parameters and uses them to bound the slider, the term picker, and the displayed payment estimates. Application intake: if a borrower configures a loan within the calculator, the entered amount and term are validated against these bounds before the application is created. Out-of-bounds requests are rejected. How to view The Landing page settings screen shows the parameters above grouped into the three panels (Loan amount, Loan terms, Rate and payment). Roles allowed: Verifier, Underwriter, Credit Officer, Collection Manager. Edit process Step 1. Open the edit form The user clicks Edit on the Landing page settings page. → The system opens “Edit landing page settings” prefilled with the current values. Step 2. Update the parameters The user changes any subset of the parameters above. The form enforces cross-field validations in real time (min ≤ max, step ≤ max amount, period type compatible with calculation type, etc.). Calculation type is read-only after the initial setup. Step 3. Save The user clicks Save. Step 4. System processes the change The system overwrites the single landing page record with the new values and emits an “updated” event so that the public calculator picks up the new configuration. The previous values are kept in the audit history. Clicking Cancel discards the changes and returns to the read-only view. ### Scoring model setting Source: https://docs.hesfintech.com/loanbox/settings/scoring-model-setting/ Scoring model setting The Scoring model setting is the screen where a credit officer manages the platform’s internal credit-scoring logic used during loan origination. A scoring model is a decision table (uploaded and edited as a DMN file) that takes borrower attributes from a loan application and returns a scoring outcome (rank, zone, decision). The system uses this outcome, along with other risk-evaluation results, to decide whether to approve, review, or reject the application. The platform ships with default scoring models. The exact catalog depends on the borrower type the platform instance is configured for: Borrower type Default scoring model Person (individual borrowers) Default person model Legal entity (corporate borrowers) Default legal entity model A platform instance always operates with a single borrower type, so a credit officer typically sees a single scoring model on this screen. The model itself is permanent—it is never deleted. What changes over time is its content, and every change produces a new version of the same model. A scoring model carries: Model ID / title—internal identifier shown on the screen header (e.g., “Scoring model #1”). Borrower type—which borrower type this model applies to (Person or Legal entity). Decision content (DMN)—the actual decision table that turns borrower data into a scoring result. Edited inline in the screen’s DMN editor. Version history—every previously deployed version of this model with its lifecycle dates. Version statuses A scoring model version can be in one of the following statuses: Status Description Draft A working copy of the next version of the model. The credit officer is editing the decision content; nothing the platform uses for live scoring has changed yet. Active The version that the platform currently uses for every internal scoring run. Exactly one version per model is active at any time. Inactive A previously active version that was replaced when a newer version became active. Kept in the history for audit. Failed A version whose deployment or validation against the test data failed. It is not used by the platform; the credit officer can edit it again and re-apply. At any moment, a model has exactly one Active version, optionally one Draft or Failed version being prepared, and any number of historical Inactive versions. Setting dependencies Depends on: The borrower type of the platform instance (Person or Legal entity). The set of scoring models displayed on the screen and the test data used for validation are selected accordingly. The decision-table file is uploaded / edited by the credit officer. The platform does not generate scoring logic on its own—a credit officer must author it. Affects: Every internal credit-scoring run during loan origination. When a product group is configured to use an internal scoring provider, the platform looks up the active version of the matching scoring model and evaluates the borrower’s loan application against it. The scoring outcome feeds into the application’s risk decision. Product group configuration. Product groups reference a scoring model by name in the “Internal scoring model” parameter. As long as the model exists and has an active version, the product group continues to work—only the content of that active version changes when a new version is applied. Existing loan applications already in scoring. Each scoring run uses the version that is active when scoring executes. Applications scored before the change keep their previous result; applications scored after the change use the new logic. Roles and permissions Editing the scoring model is restricted to Credit Officer. The screen is read-only for other roles. How to view The Scoring model screen shows: The model header—“Scoring model #{id}”. The decision-content editor with the active model’s decision table loaded. The History panel—a paginated table of every version (10 rows per page). The Apply changes button (top right), enabled only after the credit officer has edited the decision content. History columns: Column Content Name The version reference (e.g., “#42”). Click-through to that version’s content. Status Localized status: Draft, Active, Inactive, Failed. Active from Date and time the version became active. Active to Date and time the version was superseded. Empty for the currently active version. Updated at Last update date and time of the version record. Updated by The credit officer who last edited the version. Actions on a Scoring model The set of actions available on a scoring model is intentionally small—the model itself is permanent, only its content changes. Action Where Who Purpose View active model Scoring model screen Any authorised back-office role Inspect the currently active decision content and the version history. Edit the decision content Decision-content editor Credit Officer Modify the decision table to produce a new draft. The active version itself is not touched until the credit officer explicitly applies the changes. Apply changes “Apply changes” button Credit Officer Run the Apply changes process described below—deploy and validate the new content, then make it the active version. There is no manual “delete,” “deactivate,” or “rollback” action. A version becomes Inactive only when a newer version becomes Active. To roll back, the credit officer applies the previous content as a new version—the system treats it as a new change and goes through the full Apply changes process. Apply changes process The Apply changes process is what turns the credit officer’s edits into the new active scoring logic. It runs end-to-end automatically once the credit officer clicks Apply changes, with no further input required. Step 1. Edit the decision content On the Scoring model screen, the credit officer modifies the decision table inside the editor. The system stores the edits as a Draft version of the model—the active version is not yet affected. Step 2. Click Apply changes The credit officer clicks Apply changes. → The system saves the draft and starts the Apply changes process in the background. The screen does not block: the credit officer can navigate away. The outcome will be communicated by an email notification. Step 3. The system deploys the new version The system deploys the edited decision table as a new version of the scoring logic. If deployment fails (the file is malformed, references unknown attributes, etc.): The new version is marked Failed. The credit officer receives a “Dmn validation failed” notification. The previous Active version stays active and continues to be used for scoring. The credit officer can return to the screen, fix the content, and apply again—this re-uses the same Failed version (a new Failed/Draft version is not created on top of an existing one). End of process. If deployment succeeds, the process continues to Step 4. Step 4. The system validates the new version against test data The system runs the new decision table against a built-in test loan application that matches the platform’s borrower type (Person or Legal entity). This catches situations where the file deploys but produces an error during evaluation. If validation fails: The system rolls back the deployment (the just-deployed decision is removed). The new version is marked Failed. The credit officer receives a “Dmn validation failed” notification. The previous Active version stays active. End of process. If validation succeeds, the process continues to Step 5. Step 5. The system retires the previous active version The system finds the version of this model that is currently Active, sets its status to Inactive, and stamps its Active to date with the current moment. The previous content is preserved in the history. Step 6. The system activates the new version The system sets the new version’s status to Active and stamps its Active from date with the current moment. From this moment, every internal scoring run for this model uses the new content. Step 7. The system notifies the credit officer The credit officer receives a “New version created” notification confirming that the change is live. Result: The model now has one new Active version with the just-applied content. The previously active version is Inactive, with Active to set to the moment of the change. The model’s history records every step. All future internal scoring runs for this model use the new logic. Already-scored applications keep their original results. Important notes about the process: The previous active version is never deleted. It remains in the history as Inactive and can be inspected or re-applied later. While a draft is being prepared and applied, the platform continues to score new applications against the previous active version. There is no service interruption. Only one Draft or Failed version per model can exist at a time. The credit officer must finish (or fix) the current attempt before starting a new edit. If the platform is configured for Person borrowers, the test data used during validation is a sample person application; for Legal entity borrowers, it is a sample legal-entity application. ### Document templates setting Source: https://docs.hesfintech.com/loanbox/settings/document-templates-setting/ Document templates setting The Document templates setting is the registry of document templates the platform uses to produce contracts and amendment agreements during the loan lifecycle. Each template is a .docx file with placeholders that the system fills in with real data (borrower name, loan amount, signing date, etc.) at the time of generation. A template carries: Name—human-readable name of the template. Type—what the template is used for (see below). Updated at—when the template was last changed. Linked product groups—which product groups use this template (a small icon next to the name with the list of product group names). Template file—the underlying .docx. Template types Value Use Contract template Loan contract generated at origination. Amendment agreement template Document used to formalize loan adjustments after signing. Setting dependencies Depends on: uploaded .docx files; the catalog of placeholders the platform supports. Affects: Loan origination: when a borrower signs, the system generates the contract from the product group’s currently linked Contract template. Loan adjustments: when adjustments are formalized, the system generates an amendment agreement from the linked Amendment agreement template. Product group creation/editing: product groups can only link templates that exist in this registry. Document templates The Document templates page shows all registered templates as a paginated list (15 rows per page). Columns shown: Column Content Name The template name. Below the name, a small icon and a list of product group names that link this template (when any). Type Localized template type (“Contract template” or “Amendment agreement template”). Updated at The last update date and time. Download A download icon button exports the original .docx. Delete A trash icon button—only visible when the template is not linked to any product group. Page-level action: Add template (top-right)—starts the Add template process described below. Available actions on a template: Action Where Condition Add template Top of the list Always available to authorised users. Download Per-row Always available. Delete Per-row Only when the template is not linked to any product group. Shows a confirmation modal. Add template Step 1. Start the process On the Document templates page, the user clicks Add template. → The system opens “Add document template”. Step 2. Upload the template file In the Template panel, the user uploads a single .docx file (max 10 MB). Allowed file pattern: .docx File size limit: 10 MB As soon as the file is uploaded, the system: Validates the file and parses placeholders. Generates a sample document using test data. Step 3. Review the validation result If the template is valid: A preview of the generated sample document appears as a downloadable PDF link “generated-file.pdf”. Two more fields appear and become required: Document type—dropdown with the two values listed above (Contract template, Amendment agreement template). Template name—free text. If the template has problems, two red-bordered messages may appear: Unmapped placeholders—placeholders in the file that the system doesn’t recognize. Required placeholders—required placeholders that are missing from the file. The Save button stays disabled until validation succeeds (a generated sample exists). Step 4. Fill the metadata The user enters the Template name and selects the Document type. Step 5. Save The user clicks Save. → The system creates the document template record, attaches the uploaded file, sets the type and name, and adds the new template to the registry. The user is returned to the Document templates list, which now shows the new row. If the user clicks Cancel at any point, the upload is discarded, and they return to the templates list without changes. ### Notifications setting Source: https://docs.hesfintech.com/loanbox/settings/notifications-setting/ Notifications setting The Notifications setting is the registry of message templates the platform uses to communicate with borrowers and agents. Each notification template is bound to a specific business event and a delivery channel. A notification template carries the following: Event—the business event that triggers the message (e.g., Loan disbursed, Payment date tomorrow). Template name—internal name of the template. Channel—delivery channel: Email SMS Subject—message subject (email only). Body—message body. Up to 3,000 characters. Signature—message signature (email only). Up to 255 characters. Events The system ships with templates for a wide set of events covering the loan lifecycle and operational notifications, including: Application lifecycle: rejected, returned for revision, approved, canceled. Loan lifecycle: disbursed, fully repaid, overdue (fixed-term and credit line), payment received, payment date tomorrow, has become inactive, and last payment period reached. Adjustments: request approved, declined, returned for revision, applied, revision expired, and signing reached deadline. Operational: customer in blacklist, phone number changed, sign contract with OTP, contract signing, agent invitation, lead invitation, custom (notification / SMS / email), drawdown disbursed, credit-line statement created, bank-account-change approved/rejected, and OTP-related notifications. Setting dependencies Depends on: the catalog of business events the platform fires. New events become eligible for notification templates when the system version that introduces them is deployed. Affects: Every outgoing borrower or agent communication triggered by the listed events. The look, tone, and language of customer-facing messages. Notification templates list The Notification templates page shows all templates as a paginated list (15 per page). Columns: Column Content Event Localized event name (and decline reason, if applicable). Channel Email or SMS. Updated at Last update date and time. Updated by The user who last edited the template. Edit Pencil icon—opens the editor. Roles allowed to view: Underwriter, Credit Officer, Collection Manager. Edit process Only Credit Officers can edit a notification template. Step 1. Open the editor On the list, the user clicks the Edit (pencil) icon on a row. → The system opens “Edit notification” with the template prefilled. Step 2. Review the locked fields The header shows Event and Channel as read-only fields—these define which template this is and cannot be changed in the editor. Step 3. Edit the message Field Required Visible when Notes Subject Yes Channel = Email Up to 200 characters. Body Yes Always Up to 3,000 characters. Multi-line. Signature Yes Channel = Email Up to 255 characters. Multi-line. The form supports placeholders—the right-hand panel lists the placeholders supported for notification templates so the user can copy them into the body, subject, or signature. Step 4. Save The user clicks Save. → The system updates the template, records the change in the audit history (with the editor’s name and timestamp), and returns to the list. The new content is used the next time the corresponding event fires. Clicking Cancel discards the edits and returns to the list. ### Overview Source: https://docs.hesfintech.com/loanbox/reports-and-analytics/ Overview HES LoanBox does not maintain its own reporting module. Instead, it integrates with Metabase, a third-party business intelligence tool, and surfaces Metabase dashboards directly in the BackOffice portal. Operations, risk, finance, and product teams build their own dashboards and reports in Metabase, then make them available to HES LoanBox users through the embedded “Analytics” area of the BackOffice. This page explains how the integration works from the user’s perspective and lists the dashboards available in HES LoanBox environment. ### Metabase integration Source: https://docs.hesfintech.com/loanbox/reports-and-analytics/metabase-integration/ Metabase integration Metabase is a business intelligence (BI) tool that lets analysts build charts, dashboards, and reports on top of a database without writing custom application code. HES LoanBox connects to a Metabase instance and displays the dashboards prepared there inside the BackOffice portal, so users do not need a separate Metabase login or a second browser tab to view their analytics. Purpose Give business users (operations, risk, finance, product) a single place to view portfolio, application, collection, and product performance metrics without leaving the BackOffice. Let analytics teams iterate on dashboards in Metabase (where charts are designed and SQL is written) and have those changes appear in HES LoanBox automatically — no HES LoanBox release needed. Keep dashboard creation and editing in the hands of analysts, while the BackOffice acts purely as the viewing surface. Key characteristics The integration is optional. Each HES LoanBox deployment is connected to one Metabase instance; if no Metabase instance is configured, the Analytics area is not shown. Only dashboards explicitly marked as “embeddable” in Metabase appear in HES LoanBox. Private Metabase dashboards remain invisible to HES LoanBox users. Access to the Analytics area is restricted to users with the Loan Data Manager role. Users without this role do not see the Analytics navigation entry. Each time a user opens a dashboard, HES LoanBox issues a short-lived, signed viewing link (about 10 minutes by default). The link expires automatically; the next view opens a fresh link. The dashboard content itself (charts, filters, layout, data) is defined entirely in Metabase. HES LoanBox does not alter what the user sees on the dashboard. ### Opening a dashboard Source: https://docs.hesfintech.com/loanbox/reports-and-analytics/opening-a-dashboard/ Opening a dashboard This describes what a Loan Data Manager experiences when working with analytics in the BackOffice. Prerequisites The user is logged in to the BackOffice portal. The user has the Loan Data Manager role. The HES LoanBox deployment is connected to a Metabase instance (set up once by the platform administrator). Steps Step 1. Open the Analytics area The user navigates to the Analytics area in BackOffice → the portal displays the list of dashboards available to view. Step 2. Pick a dashboard The user clicks the dashboard they want to view → the portal opens the dashboard inside the page, embedded directly in the BackOffice. Step 3. Interact with the dashboard The user reads charts, applies any filters offered by the dashboard, and reviews the figures → all interactions happen inside the embedded dashboard. No data is stored in HES LoanBox; nothing changes in the system as a result of viewing. Step 4. Leave or switch dashboards The user navigates away or selects a different dashboard from the list → the previous viewing link is no longer needed and stops working shortly afterwards. Opening the same dashboard again issues a new viewing link automatically. Result: The user can view up-to-date analytics for the chosen area (portfolio, applications, collections, etc.) without leaving the BackOffice or needing a separate Metabase account. ### Analytics list Source: https://docs.hesfintech.com/loanbox/reports-and-analytics/analytics-list/ Analytics list The list of dashboards shown in the BackOffice is not hard-coded in HES LoanBox. It is read live from the configured Metabase instance every time the user opens the Analytics area. For each dashboard, the user sees: Attribute Description Dashboard name The title of the dashboard as set in Metabase. That is the only attribute HES LoanBox surfaces on the list. There are no filters, categories, or extra columns on the list itself—dashboards are identified by name. Search, grouping, and visual previews (where present) are part of the BackOffice UI design, not of the HES LoanBox backend contract. ### Access to Analytics Source: https://docs.hesfintech.com/loanbox/reports-and-analytics/access-to-analytics/ Access to Analytics Access is governed by a single role: Role Access Loan Data Manager View the Analytics area, see the list of dashboards, open any dashboard available in the list. Users without this role do not see the Analytics navigation entry and cannot open dashboards through HES LoanBox. Editing, creating, sharing, or exporting dashboards happens in Metabase itself, using Metabase’s own permission model—those actions are outside the HES LoanBox BackOffice. ### Dashboards and reports Source: https://docs.hesfintech.com/loanbox/reports-and-analytics/dashboards-and-reports/ Dashboards and reports Overview The dashboards visible in the HES LoanBox BackOffice Analytics area are not stored in the HES LoanBox source code. They live entirely inside the Metabase instance that an environment is connected to, and the list is fetched live every time a user opens the Analytics area. As a result, the only authoritative way to enumerate the dashboards available in HES LoanBox is to log in to the Analytics area on that environment (or to the connected Metabase) and read the list directly. The list of available Reports and Dashboards: The “Loan Applications” section: “Total Number of Loan Applications”, “Average Approved Loan Amount”, “Requested vs. Approved Amount Rate”, “Application Approval Rate”, “Loan Application Status Overview”. The “Deeper Dive into Loan Applications” section: “Total Number of Loan Applications Over Time”, “Application Approval Rate over Time”, “Requested vs. Approved Amount Rate over Time”, “Average Approved Loan Amount over Time”, “Loan Application Funnel”. The “Loans” section: “Total Number of Loans”, “Loans Fully Repaid”, “Average Loan Term in Weeks”, “Average Loan Term in Months”, “Pull-Through Rate”, “Loan Status Overview”. The “Deeper Dive into Loans” section: “Total Number of Loans Over Time”, “Total Number of Fully Repaid Loans Over Time”, “Pull-Through Rate Over Time”, “Total Disbursement Amount by Loan Product Over Time”. The following filters are supported: “Loan Product”, “Created At”. Loan Application Insights The following charts are presented on this tab: The “General Insights” section: “Average Loan Application Stage Duration in Minutes”, “Average Loan Application Stage Duration”. The “Underwriting Insights” section: “Number of Applications by Underwriter”, “Average Underwriting Duration in Minutes”, “Average Number of Loan Applications per Day”, “Approved vs. Declined Loan Applications by Borrower’s Age”, “Decline Reasons”, “Cancellation Reasons”. The following filters are supported: “Loan Product”, “Created At”. Ongoing Portfolio Health The following charts are presented on this tab: The “Active Loans Balance” section: “Active Loans”, “Total Principal Balance”, “Total Interest Balance”, “Total Overdue Amount”, “Total Principal, Interest & Overdue Balances Over Time”, “Total Disbursement Amount vs. Total Number of Active Loans Over Time”. The following filters are supported: “Loan Product”, “Activation Date”. Portfolio Risks The following charts are presented on this tab: The “Risks Overview” section: “PAR > 30”, “PAR > 60”, “PAR > 90”, “Portfolio Risk Concentration by Borrower’s Industry”, “Portfolio Concentration by Loan Product”. Borrower Demographics The following charts are presented on this tab: The “Deeper Dive into Borrower Demographics” section: “Total Number of Borrowers”, “New Borrowers to Date”, “Number of Borrowers by Age”, “Number of Borrowers by Marital Status”, “Number of Borrowers by Monthly Income”, “Number of Borrowers by Education”, “Number of Borrowers by Length of Employment”. The following filters are supported: “Created At”. ### Overview Source: https://docs.hesfintech.com/loanbox/security/ Overview HES LoanBox is delivered as configurable lending infrastructure that a financial institution runs either in the cloud, managed by HES FinTech, inside its own environment on-premises, or in a hybrid mode. Security is therefore a shared concern rather than a single product feature. The applicable security controls and the division of responsibilities between HES FinTech and the customer depend on the selected deployment model, system configuration, and connected services. This section explains the platform’s security architecture, how responsibility is divided between HES FinTech and the institution, and how that division shifts with the deployment model. Security architecture at a glance HES LoanBox applies controls at distinct layers. Each layer is documented on its own page in this section. Layer What it covers Identity Authentication, roles, permissions, password and lockout policy (delegated to Keycloak) Application and API Encryption, OWASP-category defenses, API authentication, KYC/KYB, anti-fraud Infrastructure Cloud and on-premises hosting, environments, backups, availability, disaster recovery Governance Activity logging, traceability, monitoring, incident response Standards ISO 27001, SOC 2, privacy regulation, NIST alignment, secure development lifecycle The platform is API-first: every capability is reached through authenticated, role-authorized APIs, and the same access rules apply whether a request comes from the user interface, an agent portal, a borrower portal, or an integration. Shared responsibility model Security divides into two parts: the security of the platform, which HES FinTech maintains, and the security of the deployment around it, which is shared with the institution and the cloud provider, in cloud deployments. The table shows where each responsibility sits. Area Cloud (HES-managed) On-premises (institution-managed) Physical and data-center security Cloud provider Institution Operating system and patching HES FinTech Institution Platform code and updates HES FinTech HES FinTech (release), institution (apply) Identity configuration (Keycloak realms, roles, policies) Institution Institution Encryption keys HES FinTech / provider KMS Institution Network controls HES FinTech Institution Backups and restore testing HES FinTech Institution Security monitoring and alerting HES FinTech Institution (with HES guidance) Incident response Joint Institution (with HES support) Regulatory compliance of lending activity Institution Institution Deployment models HES LoanBox runs on AWS or Google Cloud as a managed deployment, on-premises inside the institution’s own infrastructure, or as a hybrid of the two. The choice affects who operates each control in the table above. Deployment-specific details, such as cloud region, tenancy model, and network topology, are set during onboarding. Compliance posture HES FinTech maintains ISO 27001 certification, aligns its controls with SOC 2, and aligns its security program with the NIST Cybersecurity Framework. The platform is configured to the privacy regime of the institution’s market — GDPR, UK DPA, CCPA, PIPEDA, the Australian Privacy Act, and Saudi PDPL among them — through configurable controls and auditable records. Read more on this on the Compliance and secure development page. Note The institution remains responsible for the regulatory compliance of its lending decisions and operations. HES LoanBox provides controls that help automate regulatory workflows and keeps records that auditors can review, but it does not assume the institution’s compliance obligation. ### Identity and access management Source: https://docs.hesfintech.com/loanbox/security/identity-and-access-management/ Identity and access management HES LoanBox does not manage user credentials, sign-in screens, or password policies on its own. All authentication and identity management is delegated to Keycloak, an external identity and access management product. This page covers how users are authenticated, how roles and permissions govern what each user can do, and the password and lockout policies enforced at the identity layer. For the end-to-end administration flow see the User and role management section. Authentication via Keycloak Keycloak issues and validates the tokens that grant access to HES LoanBox. Authentication uses the OAuth 2.0 and OpenID Connect protocols; the platform trusts Keycloak-issued tokens and enforces access on every request against them. Users and roles Access is role-based. HES LoanBox is wired to a fixed set of role names. Every endpoint, process task, and menu permission maps to one or more of them. Roles are never assigned by the platform itself; an administrator assigns them in Keycloak. A user may hold more than one role in a realm, and permissions are additive. Permissions model Permissions are enforced at the endpoint level, not only in the interface: hiding a menu item does not grant access to the underlying action. The role set is designed around least privilege and separation of duties. For example, the underwriter who decides an application and the verifier who checks the underlying data hold different roles. Within an area, read-only roles can view but not change records, while full-access roles can create, edit, and approve. Login lockout and brute-force protection Keycloak provides brute-force detection. After a configurable number of failed sign-in attempts, the account is temporarily locked, with the wait time increasing on repeated failure; a permanent lockout requiring administrator intervention can also be configured. These thresholds are set per realm. Sessions and tokens Session and token lifetimes — access-token and refresh-token expiry, idle and maximum session duration, and single-logout behavior — are configured in Keycloak. Shorter lifetimes reduce the window in which a stolen token is usable; longer ones reduce re-authentication friction. The institution sets the balance. Note Two-factor authentication is configured in Keycloak and can be enforced for all users in a realm or conditionally for users with specified realm or client roles. ### Data, application, and API security Source: https://docs.hesfintech.com/loanbox/security/data-application-and-api-security/ Data, application, and API security This page covers how borrower and loan data is protected at rest and in transit, how the application defends against common web-application risks, how APIs are authenticated and authorized, and where identity, business, and fraud checks fit into the lending flow. Data encryption Data is encrypted both in transit and at rest. State Protection In transit HTTPS using TLS 1.2 or later for all external connections, including API traffic and portal sessions At rest Databases, file storage, and backups encrypted at rest using the mechanisms provided by the underlying cloud platform, typically AES-256 Keys In cloud deployment, encryption uses provider-managed keys by default. Customer-managed keys can be used where supported by the selected cloud services and deployment configuration. Data segregation and minimization Each deployment isolates its data. Personally identifiable information is confined to the records that need it, retention periods are configurable to the institution’s policy, and the data model supports the data-subject operations that privacy regimes require (access, correction, and erasure) handled operationally through administration. Tenancy (single- or multi-tenant) is set at deployment. Application security Secure development addresses the OWASP Top 10 categories of web-application risk — including injection, broken access control, and security misconfiguration — through the development lifecycle rather than as an afterthought. Controls include input validation and output encoding, enforced access checks on every request, dependency and vulnerability scanning, and peer code review before release. The secure development lifecycle behind these controls is described on the Compliance and secure development page. API security HES LoanBox is API-first, and the API is governed by the same identity layer as the interface. Every platform API request requires a valid Keycloak-issued token, is authorized against the caller’s roles, and runs over HTTPS, with tokens scoped to the minimum required permissions. Third-party services are connected using a unique authentication credential for each integration point, so each connection’s access can be controlled and revoked independently. The open API is also how integrations are built onto the platform. KYC, KYB, and sanctions screening HES LoanBox integrates with third-party providers to incorporate individual identity verification (KYC), business verification (KYB), sanctions and politically exposed person (PEP) screening, and document checks into the application workflow. Step-up identity checks can be required when a case needs stronger assurance. A predefined set of provider integrations is available out of the box, while customer-specific provider integrations are implemented through customization as part of project delivery. Note Named KYC/KYB and sanctions-screening providers are connected as part of the deployment configuration rather than shipped as fixed connectors. Anti-fraud HES LoanBox includes pre-configured fraud-prevention checks that can be fine-tuned to the institution’s risk profile and business model. Ondato and Jumio are tools used by default, and additional third-party fraud tools can be connected. Credit decisioning through GiniMachine can incorporate fraud and risk signals alongside creditworthiness, including at origination. ### Infrastructure and deployment security Source: https://docs.hesfintech.com/loanbox/security/infrastructure-and-deployment-security/ Infrastructure and deployment security This page covers the environments HES LoanBox runs in, the controls around them, and how availability, backups, and disaster recovery are handled across cloud and on-premises deployments. Which party operates each control depends on the deployment model described in the Overview. Cloud providers and hosting Managed deployments run on AWS or Google Cloud. Both providers operate physically secured, independently audited data centers, and the platform inherits their infrastructure-level controls. Institutions that require it can instead run HES LoanBox on-premises inside their own data center or in a hybrid arrangement. Data residency in a specific region can be provided to meet the client’s requirements if the cloud provider has data centers there. Environments Work is separated across environments so that changes are tested before they reach production. Environment Purpose Development Active development and internal testing Staging / UAT Pre-production validation and customer acceptance testing Production Live system serving borrowers and staff Changes are promoted through these environments via the release pipeline. Production data is not used unmodified in lower environments. Network security Network controls limit exposure to the minimum needed to run the service: network segmentation, firewall and security-group rules, private networking between components, and provider-level protection against volumetric attacks. Baseline DDoS protection is provided by the underlying cloud platform. Additional managed DDoS protection can be enabled depending on the deployment requirements. External web traffic can be fronted by a web application firewall. Backups Backups are automated and encrypted, with full backups performed once a day by default. In cloud deployments, the provider also performs incremental backups throughout the day to support point-in-time recovery (PITR). The default retention period is one week but can be adjusted to meet each client’s retention policy. Restores are tested to verify that backups are recoverable. Availability and resilience Managed deployments use redundancy across the hosting infrastructure and are monitored for availability. In an on-premises deployment, availability depends on the institution’s own infrastructure and operations. Disaster recovery As part of the SLA, a disaster-recovery plan covers restoring service after a major failure — backup restoration, failover, and defined recovery objectives. Note In on-premises deployments, physical, network, backup, and availability controls are owned by the institution. HES FinTech provides the platform, its update path, and operational guidance. ### Audit logging and monitoring Source: https://docs.hesfintech.com/loanbox/security/audit-logging-and-monitoring/ Audit logging and monitoring HES LoanBox records user and system activity so that operational and security-relevant actions can be traced, reviewed, and retained for audit. This page covers activity logging, traceability of a loan through its lifecycle, security monitoring, and incident response. Activity and audit logs The platform records who did what, when, and to which record. Logged events include: Category Examples Authentication Sign-in, sign-out, failed attempts, lockouts (recorded in Keycloak) Access administration Role assignments and changes, user creation Loan operations Application decisions, disbursements, write-offs, adjustments, waived fees Configuration Changes to products, product groups, templates, and settings API Authenticated API calls against protected endpoints Records carry a timestamp, the acting user, the action, and the affected entity, and are kept as tracked records for later review. Traceability Because each action is attributed, a loan or a credit decision can be traced end to end — who created the application, who verified the data, who decided it, and what the scoring result was at the time. Scoring outputs are retained alongside the decision, so the basis for a decision remains reviewable. These records support audit-ready reconstruction during an examination cycle. Security monitoring Platform health and security-relevant events are monitored, with alerting on anomalies. In managed deployments HES FinTech operates continuous monitoring and log aggregation; on-premises, the institution operates it, and logs can be exported into the institution’s own monitoring or SIEM tooling. Log retention and access Log retention is configurable to the institution’s policy (otherwise, 1–3 months by default), access to logs is restricted by role, and logs can be exported for the institution’s own systems. Incident response HES FinTech maintains an incident-response process covering detection, triage, containment, notification, remediation, and post-incident review. When an incident affects an institution’s deployment, HES FinTech notifies the institution within the agreed timeframe so it can meet its own obligations — including any breach-notification duties its regulators impose, such as the 72-hour notification required under GDPR. Note Audit-ready records are kept for the institution’s auditors. Responsibility for regulatory reporting remains with the institution; the platform supplies the records and traceability behind it. ### Compliance and secure development Source: https://docs.hesfintech.com/loanbox/security/compliance-and-secure-development/ Compliance and secure development This page describes the standards and attestations HES FinTech maintains as a vendor, how the platform helps an institution meet its own regulatory obligations, and the secure software development lifecycle behind HES LoanBox releases. Standards and attestations Standard What it covers HES FinTech status ISO 27001 Information security management system Certified (as of 01.07.2025, version 2.1) SOC 2 Independent attestation of security controls against AICPA criteria Aligned with SOC 2 as of 20.04.2026 GDPR EU data protection Supported through configurable controls and auditable records Note ISO 27001 is a certification. SOC 2 is an attestation report against AICPA criteria rather than a certificate, so HES FinTech LLC describes itself as aligned with SOC 2. Compliance of an institution’s lending operations remains the institution’s responsibility — the platform provides controls and auditable records, not automatic legal compliance. The platform supports the operations a data controller needs — data-subject access, correction, and erasure; data minimization; and records of processing — and is configured to the privacy regime of the institution’s market. Across the regions HES LoanBox serves, that includes: Regime Region GDPR European Union UK Data Protection Act United Kingdom CCPA California, United States PIPEDA Canada Privacy Act Australia PDPL Saudi Arabia In every case the institution is the data controller and remains responsible for compliance; HES LoanBox provides configurable controls for these requirements and keeps records that auditors can review. It does not assume the institution’s obligation on its own. Regulatory alignment HES LoanBox is configured to the requirements of the institution’s jurisdiction and lending products. The platform provides controls that help automate regulatory workflows and mitigate operational risk, and it keeps auditable records for the examination cycle. It does not make the institution compliant on its own — the compliance of lending decisions and operations remains the institution’s responsibility. NIST alignment HES FinTech’s security program is aligned with the NIST Cybersecurity Framework (CSF), which it uses as a reference for identifying, protecting against, detecting, responding to, and recovering from cyber risk. This is a framework alignment, not a certification. Secure software development lifecycle Security is built into how HES LoanBox is developed, not added at release. The platform is built on a Java LTS stack, and security practices run across the lifecycle. Phase Security practice Design Security requirements and threat consideration for new features Development Secure coding standards addressing the OWASP Top 10; peer code review Build Dependency and vulnerability scanning in the pipeline Test Security testing and, on demand, penetration testing Release and run Controlled release pipeline incorporating static application security testing (SAST) and software composition analysis (SCA), patch management, and monitoring ### Glossary Source: https://docs.hesfintech.com/glossary/ All terms