LogoLogo
timvero.comMaven Repository
  • timveroOS SDK guide
  • timveroOS how-to
  • timveroOS admin-side setup
  • timveroOS Setup guides
    • v. 7.11
      • Working with the Data sources
        • Ready-to-deploy Data Providers
      • Low-code Decision processes/ Workflows
        • timveroOS workflows - [Beta]
          • Manual Decision-Making Process in timveroOS
        • Profiles formalization and mapping entities with workflows
        • User's Assignement to Warning (-s)
      • Credit products and additives, collateral
        • Credit products
          • Additives
        • Collateral/ securitization setup
      • Configuration of the pricing algorithms
        • Deal block
      • Documents
        • Generated documents
          • Signing of generated documents
        • Required documents
      • Roles creation
      • Notifications
      • Counters
      • Servicing
      • BI
      • Other useful features
        • Catalogs
        • Form builder
    • v. 7.10
      • Admin-side system setup
      • Data sources and BPM / Underwriting setup for Dynamic Profile formation
        • Selecting integrated data sources and Feature set management
          • Ready-to-deploy Data Providers
        • Developing of Participants' or Collateral's evaluation algorithm
          • Manual Decision-Making Process in timveroOS
          • User's Assignement to Warning (-s)
        • Mapping Participants' or Collateral's evaluation algorithm
      • Credit products and additives, collateral
        • Credit products
          • Additives
        • Collateral/ securitization setup
        • Deal TnC
      • Configuration of the Offer Generator Script
      • Documents
        • Generated documents
          • Signing of generated documents
        • Required documents
      • Roles creation
      • Notifications
      • BI
        • Adding custom chart to BI Dashboard
      • Servicing
      • Catalogues
Powered by GitBook
On this page
  • Manual Decision-Making Process in timveroOS
  • How to
  • Important

Was this helpful?

  1. timveroOS Setup guides
  2. v. 7.11
  3. Low-code Decision processes/ Workflows
  4. timveroOS workflows - [Beta]

Manual Decision-Making Process in timveroOS

PrevioustimveroOS workflows - [Beta]NextProfiles formalization and mapping entities with workflows

Last updated 2 months ago

Was this helpful?

Manual Decision-Making Process in timveroOS

timveroOS enables the inclusion of certain conditions (referred to as “Warning facts”) that prevent the system from automatically proceeding with a participant’s workflow decision (i.e., approving or declining). In these scenarios, Financial Institutions (FIs) can configure policies linking a specific warning to the department responsible for reviewing it and rendering a manual decision.

For instance, a FIs may have four departments dedicated to distinct underwriting responsibilities:

  • Underwriting: Evaluates debt obligations and assesses credit history.

  • KYC (Know Your Customer): Verifies client identity and confirms address information.

  • AML (Anti-Money Laundering): Reviews transaction-related concerns.

  • Financial Department: Analyzes financial metrics and accounting data.

Within the system, there is a catalog known as Decision Departments, where an administrator can define the departments involved in manual decision-making. Each department record in the catalog contains three attributes: a code, a description, and an activity status. Catalogs

How to

When configuring warnings in the decision tree, the administrator should utilize Decision department field to select to which of them this warning will be assigned for a review. For example:

Administrator should also utilize the Form Scheme field to choose which form will be rendered for the relevant worker to complete/adjust the formalisation of the Client Profile. With this form worker will be able to fill the information about the value of specific Client profile parameter, giving extra flexibility on the manual decisions.

Note: How to build and use Form builder Form builder

Name of the Warning fact will be later displayed in the LOS/ LSS on the participant/ asset block on the Application page in the Scoring and Decision tree tab for the eyes and review of the relevant department worker:

Only users with the corresponding department assigned to their account can take the “Approve” or “Decline” actions, once they are assigned to solve warnings associated with the combination: Participant + Warnings related to this department. More about this you can learn here User's Assignement to Warning (-s)

Important

If multiple warnings exist and different departments are assigned to them, the system follows this logic:

  • If a user from any assigned department declines the warning under their purview, the participant’s application is immediately declined, and no further department reviews are necessary.

  • If a user from an assigned department approves the warning under their purview, the system then requires the remaining departments to review their respective warnings. The participant is fully approved only after all assigned departments have approved all relevant warnings.

  • The users assigned to participant from different departments can work in parallel with each other.

Financial department selected to review the Warning fact of value for the scoring