1.4 Bank.AI changelog

Release date: 07/15/2026

This document details the technical changes and enhancements introduced in Bank.AI 1.4. It is intended for developers, system administrators, and DevOps engineers responsible for maintaining and extending Creatio customizations.

Important

Bank.AI 1.4 is compatible with Creatio Business Studio 8.3.3 and later.

For a comprehensive overview of the new features, refer to the 1.4 Bank.AI release notes.

The update guide for the on-site applications is available in a separate article.

Finserv Customer Management

Category	Feature	Description
Legal entity management	Legal entity page	Added KYB verification for legal entities, including verification status, evaluation history, and compliance checks. Previously, legal entities could not be evaluated through a structured verification process. This change enables compliance teams to verify commercial customers consistently and maintain an auditable evaluation trail. Creatio generates KYB evaluations for a legal entity, records the outcome in the evaluation history, and updates the legal entity verification status accordingly. More details Added: Legal entity verification statuses lookup that includes the "Suspended," "Not started," "Expired," "Denied," and "Verified" values. "Legal entity" value to the Evaluation activation scope lookup. "Sanction lists," "Ownership and management structure," "Adverse media," "Business registration verification," "Business address verification," and "Suspicious activity" values to the Evaluation checks lookup. "KYB onboarding process" value to the "Evaluation" column of the "Business address verification," "Suspicious activity," "Business registration verification," "Sanction lists," "Ownership and management structure," and "Adverse media" checks in the Evaluation templates lookup. "Verification status" (AccountVerificationStatus code) and "Risk score" (RiskScore code) columns to the "Legal entity" (Account code) object. Out of the box, the Verification status field in the legal entity profile of the legal entity page is set to "Not started." "Legal entity verification status" (AccountVerificationStatus code) column to the "Evaluation status" (EvaluationStatus code) object, so that an "Approved" evaluation sets the legal entity to "Verified" and a "Rejected" evaluation sets it to "Denied." "Evaluation history relationships" (EvaluationHistoryRelationship code) object that links related evaluation histories. For example, KYB and its underlying KYC records. "Legal entity" (Account code) column to the "Evaluation history" (EvaluationHistory code) object and the "Update legal entity verification status" (IsUpdateAccountVerificationStatus code) column to the "Evaluation" (Evaluation code) object, so that a KYB onboarding evaluation updates the legal entity status while a KYC onboarding evaluation updates the contact status. "Generate evaluation for legal entity" business process that creates an evaluation history record and generates its evaluation checks from the evaluation template. "Create manual evaluation for legal entity" business process that opens the "Create evaluation history mini page" (CreateEvaluationHistory_MiniPage code) schema of the "Client module" type and then launches the "Generate evaluation for legal entity" business process. "Deactivate old evaluation history per legal entity" business process that is run when a new active evaluation history is added for a legal entity, deactivates the prior evaluation history records of the same evaluation, reusing the "Deactivate evaluation history (sub-process)" business process. "Update legal entity from evaluation history" business process that is run when an evaluation history status changes, updates the matching legal entity verification status and risk score. Compliance & risk monitoring tab to the legal entity page. The tab includes the Evaluation history expanded list whose button launches "Create manual evaluation for legal entity" business process. Business rules display the Legal entity field and hide the Contact field on the KYB onboarding process window, and require the Evaluation date, Due date, and Evaluator fields when the Status field is set to "Approved" or "Flagged."
Legal entity management	Legal entity page	Added ownership structure management for legal entities and contacts to capture beneficial owners, signatories, and related roles. Previously, ownership relationships were not recorded in a structured way and had to be tracked manually. This change gives users read-only visibility into ownership structure on the legal entity page and the contact page, which protects data integrity while supporting KYB and compliance requirements. More details Added: "Ownership structure" (OwnershipStructure code) object that includes the "Legal entity" (Account code), "Contact" (Contact code), "Role" (OwnershipStructureRole code), and "Source" (OwnershipStructureSource code) columns. Ownership structure roles lookup that includes the "Beneficial owner," "Authorized signatory," "Controller," and "Legal representative" values. Ownership structure sources lookup that includes the "External solution," "Manual research," and "Provided by client" values. Ownership structure expanded list to the Legal entity info tab of the legal entity page and the Associated ownerships expanded list to the Contact info tab of the contact page. Both lists are read-only. Creatio populates ownership records automatically, for example, through the legal entity application form flow.
Legal entity management	Legal entity page	Added the Financial summary tab to the legal entity page. The tab captures financial statements, assets, and liabilities, and automatically calculates the legal entity equity. Previously, legal entity records did not store structured financial data required for commercial underwriting. This change gives sales and underwriting teams a consolidated view of a commercial customer's financial standing directly on the legal entity page. More details Added: "Legal entity financial statement" (AccountFinancialStatement code) object that includes the "Period start date" (PeriodStartDate code), "Period end date" (PeriodEndDate code), "Statement date" (StatementDate code), "Currency" (Currency code), "Fiscal year" (FiscalYear code), "Type" (AccountFinancialStatementType code), "Source" (AccountFinancialStatementSource code) columns, income-statement and cash-flow columns ("Revenue" (Revenue code), "EBITDA" (EBITDA code), "Net income" (NetIncome code), "Operating cash flow" (OperatingCashFlow code), "Capital expenditure" (CapitalExpenditure code), "Free cash flow" (FreeCashFlow code), "End cash flow" (EndCashFlow code)). "Legal entity asset" (AccountAsset code) object that includes the "Asset type" (AccountAssetType code), "Ownership type" (AssetOwnershipType code), "Value" (Value code), "Currency" (Currency code), "Collateral" (IsCollateral code), "Statement date" (StatementDate code), "Latest" (IsLatest code) columns. "Legal entity liability" (AccountLiability code) object that includes the "Liability type" (AccountLiabilityType code), "Amount" (Amount code), "Currency" (Currency code), "Secured" (IsSecured code), "Statement date" (StatementDate code), "Latest" (IsLatest code) columns. "Equity" (Equity code) column to the "Account" (Account code) object. Legal entity financial statement types lookup that includes the "Cash flow statement" and "Income statement (P&L)" values. Legal entity financial statement sources lookup that includes the "Uploaded statement," "Manual entry," "External source," and "Customer provided" values. Legal entity asset ownership types lookup that includes the "Leased," "Financed," and "Owned" values. Legal entity liability types lookup that includes the "Equipment lease," "Overdraft," "Taxes payable," "Accounts payable," "Bank loan," "Line of credit," "Real estate loan," and "Accrued expenses" values. The "Yes" value in the "Debt" column separates debt ("Equipment lease," "Overdraft," "Bank loan," "Line of credit," "Real estate loan" values) from non-debt ("Taxes payable," "Accounts payable," "Accrued expenses" values). Fiscal year lookup that includes the "2023," "2024," "2027," "2022," "2025," and "2026" values. The "Yes" value in the "Current" column is set for the "2027" value. Revenue, annually, EBITDA, annually, Net income, annually, Operating cash flow, annually, Free cash flow, annually, End cash flow, annually metrics to the Financial summary tab. P&L statements, Cash flow statements, Assets, and Liabilities expanded lists to the Financial summary tab. Total debt, Total assets, Total liabilities, Equity metrics to the Balance sheet expansion panel on the Financial summary tab. "Legal entity financial statement mini page" (AccountFinancialStatement_MiniPage code) schema of the "Client module" type that opens when adding the statement from the P&L statements or Cash flow statements expanded list on the Financial summary tab. The mini page includes the Name, Fiscal year, Statement date, Frequency and Currency fields. The statement type is set automatically from the Legal entity financial statement types lookup, and the visible fields depend on the statement type. When you add the statement from the P&L statements expanded list, the mini page includes the Revenue, EBITDA, and Net income fields. When you add the statement from the Cash flow statements expanded list, the mini page includes the Operating cash flow, Capital expenditure (CapEx), Free cash flow and End cash flow fields. "Legal entity asset mini page" (AccountAsset_MiniPage code) schema of the "Client module" type that opens when adding the asset from the Assets expanded list on the Financial summary tab. The mini page includes the Type, Value, Currency, Ownership, Statement date fields and the Collateral checkbox. "Legal entity liability mini page" (AccountLiability_MiniPage code) schema of the "Client module" type that opens when adding the asset from the Liabilities expanded list on the Financial summary tab. The mini page includes the Type, Amount, Currency, Statement date fields and the Secured checkbox. "Calculate legal entity equity (sub-process)" business process that computes equity as total assets minus total liabilities and writes it to the legal entity page. "Update latest legal entity asset and calculate equity" business process that is triggered when an asset is created. The process marks the new asset as the latest, clears the flag on the previous asset, and re-runs the "Calculate legal entity equity (sub-process)" business process. "Update latest legal entity liability and calculate equity" business process that is triggered when a liability is created. The process marks the new liability as the latest, clears the flag on the previous liability, and re-runs the "Calculate legal entity equity (sub-process)" business process. "Populate legal entity asset name" business process that sets the asset name from its asset type. "Populate legal entity liability name" business process that sets the liability name from its liability type.
Legal entity management	Legal entity page	Changed the legal entity page to present commercial entity and business details required for commercial sales and KYB. Previously, the legal entity page did not expose structured business details, countries of operation, or a risk score. This change improves visibility of commercial customer data and streamlines legal entity review during commercial sales processing. More details Added: Entity & business details expansion panel to the Legal entity info tab of the legal entity page. Previously, the Taxpayer number, Company code, Blacklisted on, Liquidated on, and Reason for blacklisting fields and the Blacklisted and Liquidated checkboxes were displayed on the page but were not grouped under a dedicated panel. The panel now includes these fields along with the new Country of incorporation, Registration date, Countries of operation, and Business activity description fields. Documents expanded list to the Legal entity info tab of the legal entity page. "Registration date" (RegistrationDate code), "Country of incorporation" (CountryOfIncorporation code), "Business activity description" (BusinessActivityDescription code), and "Risk score" (RiskScore code) columns to the "Legal entity" (Account code) object. "Countries of operation in legal entity" (OperatingCountriesInAccount code) object that links a legal entity to its operating countries. The object includes the "Legal entity" (Account code) and "Country" (Country code) columns. Renamed: "Company code" (Code code) column to "Registration number" in the "Legal entity" (Account code) object. MQL/SQL expanded list to Leads on the Sales tab of the legal entity page. Field labels and titles are aligned with legal entity and commercial terminology. Changed order of expanded lists on the Sales tab of the legal entity page. Current order: Recommended products, Leads, Opportunities, Competitors.
Financial documents	Document classification	Changed the document classification model to support commercial legal entity documents and financial statement data extraction. Previously, the document classes and properties covered retail scenarios only. This change adds commercial document classes and financial document properties, and maps them so that financial statement values can be captured from classified documents, which improves document handling for commercial customers. More details Added: Document client types lookup that includes "Legal entity" and "Individual" values. "Balance sheet," "Certificate of incorporation," "Internal governance," "Certificate of good standing," "Supplementary financial information," "Business registration," "Cash flow statement," "Debt schedule," "Business license," "EIN confirmation," "Management & operations," "Income statement (P&L)," "Tax return," and "Business plan" values to the Document classes lookup. "Operating cash flow," "Revenue," "Free cash flow," "Asset value," "Frequency," "Net income," "Liability amount," "Currency," "EBITDA," "Asset," "End cash flow," "Statement date," "CapEx," "Liability," and "Fiscal year" values to the Document properties lookup. "Legal entity identification" and "Financial statement" values to the Document groups lookup. Changed the "Class" column values in the Document properties in class lookup to map document property to document class and "Document group" column values in the Document classes lookup to map document class to document group, to wire the new financial properties and document groups to the new document classes.

Finserv Product Catalog Management

Category	Feature	Description
Banking and financial products	Product catalog	Added support for commercial banking products and client-type classification in the product catalog. Previously, product categories and types covered retail products only, and products had no classification indicating the client type to which they applied. This change enables product selection tailored to commercial (B2B) scenarios and improves filtering of products by client type. More details Added: "Available for" (ClientTypeForProduct code) column to the "Product category" (ProductCategory code) object and populated it for the existing categories. "Commercial credit cards & lines of credit" value to the Product categories lookup. The "Available for" column is set to "Legal entity." "Commercial credit cards" and "Commercial lines of credit" values to the Product types lookup. The "Category" column is set to "Commercial credit cards & lines of credit."

Finserv Account Management

Category	Feature	Description
Banking and financial products	Loan management	Added support for commercial lines of credit to the loan model and loan page. Previously, loans did not capture a linked legal entity, an automatic renewal setting, or commercial line-of-credit details. This change enables management of commercial lending products alongside retail loans. More details Added: "Automatic renewal" (AutomaticRenewal code) and "Legal entity" (Account code) columns to the "Loan" (Loan code) object. "Cash flow management," "Emergency expenses," and "Working capital" values to the Loan purpose lookup. Commercial line-of-credit and commercial credit-card product parameters, for example, Credit purpose, Credit limit, Revolving status, Automatic renewal, and Draw period, months. Creatio displays the parameters on the Product features tab of the corresponding product detail page. The Credit purpose parameter is bound to the Loan purpose lookup. Legal entity field to the loan profile of the loan page. Automatic renewal control to the loan page. Line of credit details expansion panel to the General information tab on the loan page whose Type is set to "Lines of credit." "Commercial credit cards" and "Commercial lines of credit" values to the Type field in the loan profile on the loan page. Business rules that show and require elements for closed and delinquent commercial lines of credit to the "Loans form page (Business rules)" (Loans_FormPageBusinessRule code) addon. Automatic renewal and Legal entity parameters to the "Loan: create new record" business process. Payment system data model attribute to the "Card form page" (Card_FormPage code) schema. Changed the "Application parameters: read retail loan parameters" business process to read the automatic renewal and loan purpose values from either the Loan purpose or the Credit purpose product parameter.

Finserv Application Management

Category	Feature	Description
Applications and credit processing	Application management	Added an end-to-end commercial opportunity-to-application flow that converts a qualified opportunity into a financial application governed by a dedicated commercial dynamic case. Previously, applications were created only from retail flows and there was no commercial underwriting lifecycle. This change provides a governed, auditable lifecycle for commercial lending applications and keeps the opportunity and application states consistent. More details Added: "Commercial credit card & line of credit application" (Application_CommercialCreditCardAndLineOfCredit code) schema of the "Case" type that manages the commercial application lifecycle across the "Underwriting," "Agreement & Signature," "Disbursement," "Settled," and "Declined" stages. "Submit opportunity for underwriting" business process that validates the product, product parameters, legal entity, KYB, and required documents and starts application creation. When required documents are missing, Creatio displays a detailed error message. "Create application from opportunity" business process that creates or reuses the application and copies the contact, legal entity, lead and product data, product category and type, and application form. "Application to opportunity stage synchronization" business process that moves the opportunity to "Contracting" stage when the application reaches "Agreement & Signature" stage, and to "Closed won" stage when the application reaches "Settled" stage. "Complete application for simple commercial credit product" business process that completes simple commercial credit products, sets the end date, updates the Type field on the contact profile of the contact page to "Customer" where applicable, and opens the created loan. "Offer structuring stage in Opportunity" business process. "Open application mini page" (OpenApplication_MiniPage code), "Submit opportunity for underwriting" (Opportunity_SubmitForUnderwriting_Dialog code), "Product is required" (Opportunity_Validation_ProdcutRequired_Dialog code), "Product parameters required" (Opportunity_Validation_ProductParametersRequired_Dialog code), "KYB evaluation is required" (Opportunity_Validation_KybRequired_Dialog code), and "Opportunity required documents not uploaded" (Opportunity_Validation_RequiredDocumentsNotValid_Dialog code) schemas of the "Client module" type. Applications expanded list to the Compliance & risk monitoring tab of the opportunity page. The list is read-only and includes the applications linked to the current opportunity. "Opportunity" (Opportunity code) column to the "Application" (FinApplication code) object. The column links each application to the opportunity it was created from, and the Legal entity field on the Overview tab of the opportunity page to the application full page and the loan page. "Application full page (Business rules)" (FinApplication_FullPageBusinessRule code) addon that hides the Contact info tab, Financial details tab, Risk ratios and Credit snapshot expansion panels on the Underwriting tab of the application full page for commercial credit card and commercial line of credit applications. "Application submission page (Business rules)" (FinApplication_SubmissionPageBusinessRule code) addon that hides the Customer details tab on the application submission page and makes the record read-only. Stage-based business rules to the "Opportunities form page (Business rules)" (Opportunities_FormPageBusinessRule code) addon. The rules lock it as the deal advances: the Customer need and Product fields on the Product details tab of the opportunity page become read-only and the manual add-application-form action is hidden in advanced and closed stages, the Customer request and Product parameters expansion panels on the Product details tab of the opportunity page are shown, and the Documents for signing expanded list on the Documents tab of the opportunity page is shown in the "Contracting" and "Signing" opportunity stages. Changed the "Process Agreement & Signature stage," "Process disbursement for loan application," and "Change application stage" business processes to support the shared stage-synchronization logic. These processes are also reused by the "Personal loan application" (Application_PersonalLoan code), "Auto & home loan application" (Application_AutoAndHomeLoan code), "Credit card & line of credit application" (Application_CreditCardAndLineOfCredit code), and "Retail deposit bank account application" (Application_RetailDepositBankAccount code) retail application cases. The "Process Agreement & Signature stage" business process creates and links the contract and stores it on the application. The "Process disbursement for loan application" business process creates the loan, passing the application, contact, legal entity, product, and contract.
Applications and credit processing	Application form management	Added a legal entity application form used to capture and verify commercial applicant data during opportunity processing. Previously, application forms supported individual (retail) applicants only. This change enables structured capture and verification of commercial applicant data and reduces manual data entry across the opportunity-to-application flow. More details Added: "Legal entity application form detail" (AccountAppFormDetail code), "Ownership structure in application form" (OwnershipStructureInAppForm code), "Countries of operation in application form" (OperatingCountriesInAppForm code), "Legal entity address" (AccountAddress code), "Application form type" (AppFormType code), and "Evaluation application form history" (EvaluationAppFormHistory code) objects. "Legal entity application form edit page" (AccountAppForm_FormPage code) schema of the "Client module" type. Schema includes a legal-entity header and the Legal entity details and Compliance & risk monitoring tabs. The Legal entity details tab includes Identification documents and Ownership structure expanded lists, Legal entity data, Communication options, Registration address, and Mailing address expansion panels. The Compliance & risk monitoring tab includes Evaluation history and Related application forms expanded lists. "Web" (Web code), "Fax" (Fax code), and "Application form type" (AppFormType code) columns to the "Application form" (AppForm code) object. "Ownership structure in application form mini page" (OwnershipStructureInAppForm_MiniPage code) and the "Ownership structure is required" (AccountAppForm_Validation_OwnershipStructureRequired_Dialog code) schemas of the "Client module" type that include validation logic. Application form types lookup with "Legal entity" and "Individual" values. "Application form type" column to the Roles of participants lookup. The column is set to "Individual" for "Coborrower," "Borrower," "Customer," "Debtor," "Spouse," "Contact person," "Applicant," and "Warranter" values. The column is set to "Legal entity" for "Warranter," "Debtor," "Customer," "Borrower," and "Applicant" values. "Completed" and "Approved" values to the Application form status lookup. "Evaluation rejected" value to the Reasons for application form closing lookup. The "Inactive" column for the "Evaluation rejected" value is set to "No." "Create application form for opportunity" business process that generates a legal entity application form, links it to the opportunity, and creates a follow-up task to complete the form when an opportunity reaches the "Qualification" stage. "Create and link legal entity application form detail" business process that creates and links its "Legal entity application form detail" record on creation of a legal entity application form. "Populate legal entity data for existing legal entity in application form" business process that populates the new form from the legal entity's data, communication options, addresses, ownership structure, operating countries, and documents. "Process application form and update legal entity data" business process that migrates the collected form data back into the legal entity and its related records on approval. "Process ownership structure contacts in application form" business process. "Approve application form once evaluation history approved" business process that sets the form to "Completed" once its evaluation is approved. Application forms expanded list to the Compliance & risk monitoring tab of the legal entity page and opportunity page. The list includes the related legal entity application forms. Stage-based locking so that fields and the Ownership structure expanded list are editable only while the application form is in the "Draft" status. The Opportunity field on the application form page is always read-only. Same as registration address checkbox to the Mailing address expansion panel on the Legal entity details tab of the application form page that copies the registration address into the mailing address and keeps it in sync. Validation that blocks submission until at least one ownership structure record exists. "Legal entity" and "Opportunity" columns to the default list settings in the "Application forms list page" (AppForms_ListPage code). Additionally, live data update on the list was enabled. Changed: Stage-based locking to both the individual and the legal entity application forms: the Compliance & risk monitoring tab on the legal entity page is shown only when the form is not in the "Draft" status (hidden by default), the toolbars on the read-only evaluation-history and related-application-forms lists are disabled, and on the individual form the Number of dependents field on the Customer details tab on the application form page becomes read-only once the form leaves the "Draft" status. "Create document from application form" and "Create document (sub-process)" business processes and the "Create document mini page" (CreateDocument_MiniPage code) schema of the "Client module" type to handle the legal entity context and show a legal entity compact profile for legal entity documents (and a contact compact profile for contact documents). "Populate application form name" business process to support legal entity and commercial application forms. "Create required document from application form," "Create document from required document," and "Deactivate identification document" business processes to populate and manage documents in the legal entity context.
Applications and credit processing	Application form page	Fixed the "Populate contact data for existing contact in application form" business process to process all matching contacts on the application form page. Previously, the process read only the first contact from the collection of matching contacts, which could leave related contact data incomplete. This change reduces the need for manual corrections.
Applications and credit processing	Evaluation management	Added KYB verification for opportunities so that commercial deals are verified before they progress to underwriting. Previously, opportunities had no compliance verification step. This change enforces compliance checks within the commercial sales flow and provides an auditable verification trail on the opportunity. More details Added: "Initiate KYB for opportunity" business process that, on opportunity qualification, reuses a valid active KYB evaluation for the opportunity or generates a new evaluation history together with its KYB checks, due 180 days from creation, and records the outcome in the "Evaluation opportunity history" (EvaluationOpportunityHistory code) object. A manual restart is blocked when the opportunity is in a final stage. "Approve KYB evaluation history" business process. Compliance & risk monitoring tab to the opportunity page. The Compliance & risk monitoring tab includes Applications, Application forms and Evaluation history expanded lists. The Evaluation history list is filtered by the "KYB onboarding process" evaluation and the Restart KYB evaluation button. The "Evaluation restart not allowed for opportunity" (EvaluationRestartNotAllowedForOpportunity_Validation_Dialog code) schema of the "Client module" type implements the mini page that is shown when the opportunity is closed. Validation that requires a passed KYB evaluation before an opportunity can be submitted for underwriting.
Applications and credit processing	Evaluation management	Changed the evaluation flow so that submitting an application form drives verification and data synchronization as one coupled sequence, and consolidated the KYB and KYC initiation logic. Previously, the retail flow had two separate, independent actions: submitting an application form immediately synchronized its data to the contact, and the KYC evaluation ran separately afterwards. This change makes verification a gate before data is committed and removes divergent, duplicated verification logic across retail and commercial flows. More details Added: "Evaluation application form history" (EvaluationAppFormHistory code) object that links an evaluation history to an application form. "New application form" value to the Evaluation purposes lookup. "Complete individual application form" business process that launches "Process application form and update contact data" business process and sets the form to "Completed" when an individual application form is approved. "Generate evaluation for application form" business process that generates an evaluation history, links it to the application form through the "Evaluation application form history" (EvaluationAppFormHistory code) object, and launches the mock KYC checks. "Initiate evaluation for application form" business process. Forms & applications tab to the "Evaluation history mini page" (EvaluationHistory_MiniPage code) schema of the "Client module" type. The tab includes the Application forms and Applications expanded lists. The Application forms list is bound to the "Evaluation application form history" (EvaluationAppFormHistory code) object. Compliance & risk monitoring tab to the application form page. The tab includes the Restart KYC evaluation button in the Evaluation history expanded list. DisableGenerateEvaluationForApplicationProcess SQL script for Microsoft SQL, Oracle, and PostgreSQL to remove the deprecated "Generate evaluation for application" business process. The consolidated initiation logic now replaces it. Changed: "Submit application form" business process to set the form status to "Submitted" and launch KYC initiation for the individual application form, moving the contact-data update out of submission. "Initiate KYC for application," "Generate mock automated checks," "Generate underwriting evaluation for application," and "Initiate underwriting for application" business processes to reuse the consolidated initiation logic. Retail application cases so that "Initiate KYC for application" business process is the first step on the "Underwriting" stage. "Create application form for application" business process to create only individual application forms and set the application form type. "Deactivate old evaluation history per application" and "Deactivate old evaluation history per contact" business processes to also cancel not-started evaluations and their not-started checks. "Change application stage" business process to also set the linked application form status to "Submitted." Fixed the "Initiate KYC for application" business process to filter by the contact from the application so restart works, and made the Contact and Legal entity fields read-only on the Evaluation history mini page.
Financial documents	Document management	Added document management to the opportunity, including a required documents list driven by the selected product and bidirectional visibility of documents shared between an opportunity and its application. Previously, documents could be managed on the application only. This change gives sales users a complete document view during commercial opportunity processing and removes manual document reconciliation between the opportunity and the application. More details Added: "Opportunity" (Opportunity code) column to the "Required documents in application" (DocListInFinApp code) object. A required document can now be linked to an opportunity in addition to an application and an application form. "Opportunity" value to the Document list stage lookup. The "Filtering object" column is set to "Opportunity." A product condition can now define an opportunity document package and build its applicability filter over opportunity columns on the Conditions tab of the product detail page. Documents tab to the opportunity page. The tab includes the Required documents and Documents for signing expanded lists. The Required documents expanded list mirrors the application page. The list shows the generated required documents, and attachments of the document linked to the selected required document (or a placeholder when nothing is selected), refreshing automatically when the selection changes. New documents and attachments can be added directly from the Attachments expanded list. The Documents for signing expanded list automatically shows the contract and signature documents created in the application and enables a manager to upload an attachment to a selected document directly from the Attachments expanded list. "Create required document from opportunity" business process that creates and links the matching application document, preserving the document reference and status, when a required document is created on an opportunity that has a linked application. "Generate required documents for opportunity" and "Launch required document generation for opportunity" business processes that automatically build the opportunity's required-documents list whenever a product is set or changed on the opportunity. The list is taken from the active product condition's opportunity-stage records, and each record's applicability filter is evaluated against the opportunity. Role-bound documents are distributed to the opportunity's application forms by participant role. Records with no matching form stay at the opportunity level. On regeneration, not-uploaded records that are no longer relevant are removed, and requirements that are no longer needed are downgraded to optional. Records that already have an attachment or a linked document are never deleted. "Launch required document deletion" business process that deletes required document and its linked document when a required document is unmarked as required. "Link opportunity to required documents and document" business process that links existing opportunity documents to the application after it is created, so documents stay visible from both sides without duplicates. "Generate the list of documents in opportunity" (GenerateDocListOpportunityUserTask code) schema of the "User task" type. "DocListOpportunityConsts" (DocListOpportunityConsts code), "DocListOpportunityHelper" (DocListOpportunityHelper code), and "DocListOpportunityHelperService" (DocListOpportunityHelperService code) schemas of the "Source code" type. Changed: Manual document creation so that the document-class list on the "Select document class mini page" (SelectDocumentClass_MiniPage code) schema of the "Client module" type is filtered by context. Identification classes and classes already present on the record are excluded, and the offered classes are limited by client type (legal entity or contact) using the new "Available for" product-category classification and the "Document client type" class. "Create required document from application" business process to apply the same client-type filtration as the "Select document class mini page" (SelectDocumentClass_MiniPage code) schema of the "Client module" type. "Create document from required document" and "Update document status on attachment upload" business processes to also handle required documents linked to an opportunity, keeping a required document and its linked document in sync when attachments are uploaded or removed. Document selection on the application full page and application submission page to use more secure selection logic. "Unable to delete the document" (UnableToDeleteTheDocument_Dialog code) schema of the "Client module" type to prevent deleting a document still linked to other required documents.
Apps and packages	Package management	Changed the package structure by moving logic out of CrtFinservAppMgmtInSales into the application management packages. Previously, lead-to-application and referral logic was placed in a separate package that added an extra dependency layer. This change simplifies the dependency structure and improves maintainability of the application management layer. After upgrading to version 1.4, the CrtFinservAppMgmtInSales package is in place but empty. More details Moved: "Financial application" (FinApplication code) object to the CrtFinservAppMgmtObjMdl package. "Create application for selected product in lead," "Lead conversion to application," "Lead conversion processing," "Set referral status to successful," and "Set referral status to unsuccessful" business processes and the "Leads form page" (Leads_FormPage code) schema of the "Client module" type to the CrtFinservAppMgmt package. Removed all non-needed schemas from the CrtFinservAppMgmtInSales package.
Schema design and management	Module Designer	Added the crt.DynamicParameters type of Freedom UI component to render, validate, and persist configurable parameters. The component can be added in the source code of the Freedom UI page and used to manage customer need and product parameters on the opportunity page. Previously, dynamic parameter handling relied on the crt.ApplicationParametersModule component type, which was tightly coupled to a single page and could not be reused. This change gives developers a reusable component and provides sales users with consistent, validated parameter capture during commercial opportunity processing. More details Added: Reusable, remotely loaded crt.DynamicParameters component type with isolated services, stores, and validators, so that multiple instances can run on the same page, separated by a componentId. It renders "Integer," "Decimal," "String," "Boolean," and "Lookup" type parameters, and validates values against configurable source constraints. It also prevents duplicates and stages create, update, and delete operations into the parent page save flow. "Integer" and "Decimal" type parameters expose a guidance tooltip with the allowed min/max range. "String" and "Boolean" type parameters stay editable. "Lookup" type parameters list only the values available from the source, and a parameter scoped by the source to a single value renders read-only and auto-populated. "Application parameters" (FinApplicationSpec code) object that stores parameter values together with their "Customer need" (LeadType code) and "Opportunity" (Opportunity code) columns. "Product in need type" (ProductInLeadType code) object that links products to customer-need values. The object is used to filter the product selection on the opportunity page by the chosen customer need. Product details tab to the opportunity page. The tab includes Product suggestions, Customer need, and Product fields, Recommended products, Products, Customer request and Product parameters expanded lists. The Customer request list includes the crt.DynamicParameters placeholder and uses the opportunity's lead type as its source. The Product parameters list includes the crt.DynamicParameters placeholder, uses the opportunity's product and its active product condition, and validates values against the "Parameter in product condition" (SpecInCondition code) object. "Populate product parameters from customer need" and "Populate product parameters from customer need (sub-process)" business processes that are run when the opportunity product is set or updated and copy the values of parameters shared between the customer need and the product (matched on the shared specification, copied per value type). Renamed the Title property value in the General property block of Object Designer from "Total contract value" to "Opportunity value" for the Amount column in the "Opportunity" (Opportunity code) object. Moved the product parameter values captured on the opportunity into the application created from it.

Finserv Sales Management

Category	Feature	Description
Lead management	Leads section	Changed the lead management flow to support commercial (B2B) sales alongside retail (B2C). Previously, lead processing, qualification, and conversion were oriented to retail scenarios and did not account for commercial lead types or legal-entity-based handling. This change enables sales representatives to process commercial and retail leads within a single, motion-aware flow and improves conversion accuracy across segments. More details Added: A version of the "Finserv lead management" (FinservLeadManagementCaseCrtFinservSalesMgmtv1 code) schema of the "Case" type that overrides and replaces the base "Finserv lead management" (FinservLeadManagementCase code) schema of the "Case" type and is registered as the active lead case. It manages the lead lifecycle across the "Initial contact," "Processing," "Converted," and "Closed lost" stages, each triggering a dedicated business process: "Lead initiation processing," "Lead processing stage," "Lead conversion processing," and "Lead closed lost processing" respectively. It also exposes the Owner and Assignees group fields on the Overview tab of the lead page. "Commercial wealth management," "Commercial checking," "Commercial credit card," "Commercial lending," and "Commercial saving" values to the Product in need type lookup. "Processing" value to the Lead stage lookup. The "Display in Workflow Bar" column is set to "Yes." "Credit purpose," "Term, months," "Detailed purpose," "Credit limit," and "Down payment, amount" parameters to the Parameters detail on the Commercial lending page opened from the Need types lookup. Legal entity contacts expanded list to the Overview tab of the lead page. "Show elements: Branch" and "Show elements: Legal entity contacts, Account fields flex container" page-level business rules which show the legal entity information container and the Legal entity contacts expanded list on the Overview tab for the "B2B" sales motion and the Branch field on the contact person profile for "B2C." "Make elements required: Contact," "Make elements required: Legal entity," "Show elements/Make elements required: Referrer, Reward program for B2C," and "Show elements: Referrer, Reward program, Make elements required: Referrer for B2B" page-level business rules to the "Leads mini page" (Leads_MiniPage code) schema of the "Client module" type. The rules make the Legal entity required for the "B2B" sales motion, the Contact field required for "B2C" sales motion, and the Reward program field is no longer required for commercial leads. Renamed the "Lead qualification processing" business process to "Lead processing stage." It is run by the "Processing" stage of the lead page. Changed: "Lead initiation processing" business process so that, during the "Initial contact" stage, completing or canceling the initial "Get to know the new lead and start processing" task creates a follow-up "Review the legal entity's information and relationships" task assigned to the lead owner. "Lead conversion to opportunity" business process to map the customer need during lead-to-opportunity conversion, and removed the deprecated "Check KYB evaluation in opportunity" business process along with its references. Opportunities converted from a lead are created in the "Qualification" stage through the "Converting the lead into an opportunity" business process.
Applications and credit processing	Opportunity management	Added opportunity management for commercial sales. Previously, the application did not provide a structured opportunity pipeline for commercial sales. This change gives sales teams a consistent, stage-governed process for commercial opportunities and aligns opportunity handling with financial sales scenarios. More details Added: Opportunities section for the commercial sales flow. The section is available in the "Lead and Opportunity" workplace. Product details and Compliance & risk monitoring tabs to the opportunity page, along with business rules that adapt the page to commercial opportunities. Implemented by replacing the out-of-the-box "Opportunities form page" (Opportunities_FormPage code), "Opportunities list page" (Opportunities_ListPage code), and "Opportunities mini page" (Opportunities_MiniPage code) schemas of the "Client module" type, "Opportunities form page (Business rules)" (Opportunities_FormPageBusinessRule code), and "Opportunities mini page (Business rules)" (Opportunities_MiniPageBusinessRule code) addons in the CrtFinservSalesMgmt package, rather than creating new schemas. The Customer request and the Product parameters expanded lists on the Compliance & risk monitoring tab are covered under the KYB verification on opportunity features. "Opportunity management for commercial sales" (FinservOpportunityManagementCommercialSalesCase code) schema of the "Case" type. The schema manages the commercial opportunity lifecycle across the "Qualification," "Offer structuring," "Proposal," "Underwriting," "Contracting," and terminal ("Closed won," "Closed lost," "Canceled") stages. The "Qualification," "Offer structuring," and "Proposal" stages are advanced manually. The "Underwriting," "Contracting," and "Closed won" stages are system-driven. "Underwriting" is reached only by submitting the opportunity for underwriting, and "Contracting" and "Closed won" are set automatically by application-to-opportunity stage synchronization. The commercial-flow stage actions (create application form, submit opportunity for underwriting, offer structuring) are wired in the application management version of the "Opportunity management for commercial sales" (FinservOpportunityManagementCommercialSalesCaseCrtFinservAppMgmt1 code) schema of the "Case" type. "Evaluation opportunity history" (EvaluationOpportunityHistory code) object. "Offer structuring stage in Opportunity" business process that adds stage-driven tasks to the "Offer structuring" stage: two parallel tasks assigned to the opportunity owner — "Capture customer request" and "Define product parameters" — and, once both are completed, a third "Assess the need for compliance and risk monitoring" task. "Offer structuring," "Canceled," and "Underwriting" values to the Opportunity stages lookup. The "Show in funnel" column is set to "Yes" and the "Successful" column is set to "No" for "Offer structuring," "Canceled," and "Underwriting" values. The "Final" column is set to "No" for "Offer structuring" and "Underwriting" values and to "Yes" for "Canceled" value. DisableOpportunityManagementDCM SQL script for Microsoft SQL, Oracle, and PostgreSQL to remove the out-of-the-box opportunity management dynamic case. The new commercial sales case governs the "Opportunity" (Opportunity code) object. Renamed the out-of-the-box Products tab to Product details. Changed: Legal entity field to always required on both the opportunity page and the opportunity mini page replacing the previous rules that required Contact or Legal entity fields only when both were empty. Field ordering on the Overview tab. Opportunity page to hide the out-of-the-box product list and the Documents expanded list on the History tab. Removed the Customer need field from the Overview tab.