Product Settings

Product settings allow you to configure the option sets available in your product types for selecting product features like payment schedules, types of collateral, insurance perils, types of fees, interest indexes, etc.

Banking

Bancassurance Classes

Bancassurance allows you to define classes of insurance for insuring your banking products. When associated to a payment schedule type, a corresponding insurance payment column will be displayed in the corresponding payment schedules.

NOTE  

Insurances with a periodicity set to once will not appear in payment schedules. The insurance must have a recurring periodicity to appear in a payment schedule.
  1. In the main menu, click Products > Products > Settings > Bankassurance Classes, to open the Bankassurance Classes list page.
  2. Click Insert to add a new class.
  3. Enter a name for the bancassurance class.
  4. Modify the default values filled in for the following fields:
    • Mandatory for Applicant - If selected, the schedule element class is applicable to the applicant customer. Default value: True.
    • Mandatory for Debtor - If selected, the schedule element class is applicable to the debtor. Default value: False.
  5. Click Save and close. Repeat as many times as needed.
NOTE  
FintechOS Studio uses the values of a saved bancassurance class record to automatically fill in the fields of an insurance during the creation of a new record.

Banking Product Document

This section allows you to track all the documents that have been set up in various banking product types to be requested from or provided to banking customers, such as identification documents or Terms and Conditions.

BIN

A Bank Identification Number (BIN) represents the first 6 to 8 digits of a payment card number. It identifies the institution and card network responsible for issuing and processing the card, determining how transactions are routed and handled.

To create a BIN:

  1. In FintechOS Studio, go to Main Menu > Products > Products > Settings > BIN.
  2. Click Insert.
  3. Enter the BIN number (e.g., 400000). The number must contain 6 to 8 digits.
  4. Select the Processor ID. This defines the card network (e.g., Visa, Mastercard)
  5. Click Save and Close.

Blockchain Networks

Blockchain networks define the infrastructures on which cryptocurrency-based products can be held and transferred. Each network represents a distinct processing environment with specific capabilities, protocols, and constraints that influence how transactions are executed and validated.

To set up blockchain networks that are available for your products, in FintechOS Studio, go to Main Menu > Products > Products > Settings > Blockchain Networks.

Each network has the following parameters:

Parameter Description
Name Unique name of the blockchain network (e.g., Ethereum, Bitcoin, Polygon).
Type Classification of the blockchain network based on its architecture and capabilities (e.g., Bitcoin-like chains, Privacy chains, Non-EVM smart contract chains).

Collateral Type

The Collateral Type dictionary is used to define the types of collateral used in the banking products' definition.

To manage collateral type records:

  1. In the main menu, click Products > Products > Settings > Collateral Type, and the Collateral Type List page opens.

    Or you can manage collateral types from FintechOS Portal's Core Banking Operational > Collateral Type menu.
  2. On the Collateral Type List page, you can add new allocation methods or search, edit, and delete existing ones.
NOTE  

You can insert, update, or delete records if you have the associated role of Banking Product Admin.

Follow these steps to create new collateral type records:

  1. Click Insert on the Collateral Type List page, and the Add Collateral Type page is displayed.
  2. Fill in the following fields:

    • Name: Enter the name of the collateral type.
    • Code: Enter the code of the collateral type.
    • Adjust Percent: Enter the adjusted value of the collateral type.
      NOTE  
      When a collateral type is defined, you can set an adjustment percent. The adjustment percent is a customization applied for that collateral. Further, when a collateral is linked to a secured loan contract, its market value is automatically adjusted by Loan Management using the adjustment percent.
    • Priority: Enter the priority of the collateral type to be considered within a contract.
  3. Click Save and Reload.

In the newly displayed Banking Products section, you can see the banking products that have this collateral type associated.

Covenant Types

Covenants represent conditions that the customer must comply with and that are periodically reviewed.

To create a covenant type:

  1. In FintechOS Studio, go to Main Menu > Products >Products > Settings > Covenant Types.
  2. Click Insert.
  3. Enter a Name for the covenant (e.g., Leverage Ratio).
  4. Select a Type:
    • Financial - Requires the customer to maintain specific financial metrics within defined thresholds. Example: Limits the ratio between the customer’s total debt and income or assets.
    • Negative - Restricts the customer from performing certain actions. Example: Restricts or caps the amount of new debt the customer can incur.
    • Affirmative - Requires the cardholder to perform specific actions or maintain certain behaviors. Example: Requires the customer to route a minimum amount of income into a designated account.
  5. (Optional) Enter a Description for the covenant.
  6. Click Save and Close.

Fee Types

To set up the fee types that are available for your products, in FintechOS Studio:

  1. Go to Main Menu > Products > Products.
  2. Click Settings.
  3. Select Fee Types.

Each type of fee has the following parameters:

Parameter Description
Commission Schema

Indicates the conditions under which the fee is applied.

  • Administration Fee - Management fee.
  • Commission Unusage - Fee applied for the amount unused from the contract's amount. Usually this is applied for unused overdraft amounts.
  • Commission Usage - Fee applied for the amount used from the contract's amount.
  • Front-end Fee - Fee paid at the beginning of the loan agreement to cover the costs of underwriting, evaluating, and processing the loan application. E.g.: loan origination fees, application fees, credit check fees.
  • Management Fee - Fee paid for administering and managing the loan throughout its duration, to cover operational costs such as regulatory compliance, maintaining the loan account, or providing ongoing customer support.
  • Payment Holiday - Fee charged when the borrower requests to temporarily suspend or defer making regular loan payments for a specific period.
  • Repayment Fee - Fee for repaying the loan in full or making larger payments than scheduled before the loan's maturity date.
  • Reschedule - Fee applied when the borrower seeks to modify the original repayment schedule, loan duration, or other terms specified in the loan agreement.
  • Return Fee - Fee charged when the borrower's payment is returned or cannot be processed.
  • Versioning Fee - Fee applied once when creating a new version of an approved contract.
Name Type a name for the fee.
Periodicity Type How often the fee is charged. Either only once or at regular intervals (annually, bimonthly, trimestrial, weekly, etc.).
Mandatory for Applicant This fee must be payed by the applicant.
Automatic Load on Contract If selected, this fee is automatically loaded on contracts.
Is for Contract Version Fee applied when creating a new contract version.
Is for Unusage Fee for when an account or credit line remains unused or inactive for an extended period of time.
Is Returnable Fee is refundable if the loan application is denied.

Is Return

Fee applied for Return Amount or Goods transactions on contracts.

Interest Indexes

The Interest Indexes option allows you to track all the individual interests that have been set up in various banking product types. To see the interests, in the FintechOS Studio main menu, go to Products > Products > Settings > Interest Indexes.

Limit Types

Limits configure the maximum amounts allowed for different types of payments or withdrawals over specific time periods. This section allows you to track all the limits that have been set up in various banking products and create new ones.

Loan Periodicity

Loan periodicity is the dictionary used to define the regularity of payments. For example, payments related to loan contracts, commissions, or installments can be performed once, daily, monthly, yearly, and so on.

To manage loan periodicity records:

  1. In the main menu, click Products >Products > Settings > Loan Periodicity, and the Loan Periodicity page opens.
  2. On the Loan Periodicity page, you can add new loan periodicity record or search, edit, and delete existing ones.
NOTE  

You can insert, update, or delete records if you have the associated role of Banking Product Admin.
  1. Click Insert on the Loan Periodicity page. The Add Loan Periodicity page is displayed.
  2. Fill in the following fields from the Loan Periodicity section:

    • Name: Enter the name of the periodicity.
    • Periodicity: Enter the number of measurement units for the periodicity.
    • Measurement Unit: Select the measurement unit applicable for the periodicity from the drop-down. Possible values: Days, Weeks, Months, Years, and Once.
  3. Click Save and Reload. The new loan periodicity is created and ready to be used.

Payment Schedule Type

A payment schedule represents the complete table of periodic loan payments, showing the amount of principal, interest, and other payments that comprise each installment until the loan is paid off at the end of its term.

The payment schedules are a quintessential part of a loan. Below you can see how to configure the installments, dates and calculations.

In FintechOS Studio, payment schedule types come with a business workflow attached in order to block changes to schedule types that are actively used on banking products. Read more about Business Workflows.

Follow the steps below to create a new payment schedule type:

  1. In the main menu, select Products > Products > Settings > Payment Schedule Type, and the Payment Schedule Types List page opens, showing all the already created schedule types.
  2. Click Insert to add a new type.
  3. In the newly opened Add Payment Schedule Type page, fill in the following fields:

    • Payment schedule code: Insert a code for the type to keep track of them.
    • Name: Insert a suggestive name for the type.
    • Banking Product Type: Select a product type to associate with the payment schedule type. Depending on the Product Type, different calculation rules are triggered. For example, the product type Overdraft has only the payment at maturity.
    • Day Count Conversion: Determines how annual interests are converted to daily interests when calculating installments for time intervals measured in days. FintechOS Studio supports industry-standard conversions, such as 30/360, 30/365, Actual/Actual, where Actual for years can be either 365 or 366. You can define other schedule interest calculation types, as needed. In practice, calculation types such as Actual/360 or Actual/365 may also be encountered.
      • Equal Installment Monthly 30/360 - payment schedule with equal installments, where every period is a month of 30 days, and every year has 360 days;
      • Equal Installment Monthly 30/365 - payment schedule with equal installments, where every period is a month of 30 days and every year has 365 days;
      • Equal Installment Monthly 30/366 (30/Actual) - payment schedule with equal installments, where every period is a month of 30 days and every year has 366 days;
      • Equal Installment Monthly Actual/365 - payment schedule with equal installments, where every period is the month's actual number of days (28,29, 30, or 31) and every year has 365 days;
      • Equal Installment Monthly Actual/366 (Actual/Actual) - payment schedule with equal installments, where every period is the month's actual number of days (28,29, 30, or 31) and every year has 366 days;
      • Equal Principal Monthly 30/360 - payment schedule with equal principals, where every period is a month of 30 days and every year has 360 days;
      • Equal Principal Monthly 30/365 - payment schedule with equal principals, where every period is a month of 30 days and every year has 365 days;
      • Equal Principal Monthly 30/366 (30/Actual) - payment schedule with equal principals, where every period is a month of 30 days and every year has 366 days;
      • Equal Principal Monthly Actual/365 - payment schedule with equal principals, where every period is the month's actual number of days (28,29, 30, or 31) and every year has 365 days;
      • Equal Principal Monthly Actual/366 (Actual/Actual) - payment schedule with equal principals, where every period is the month's actual number of days (28,29, 30, or 31) and every year has 366 days.
        NOTE  
        The payment schedule projection takes into consideration both the payment schedule type defined at the banking product level, and whether to collect the interest accrued on the contract until the date of an early repayment event, thus repaying the accrued interest, or not, thus adding the accrued interest to the repayment amount. Set the Collect accrued interest field in the Event page at the contract level to False to add the accrued interest to the repayment amount.
    • Time Unit: The type of measurement unit applicable for the payment schedule type: Days, Weeks, Months, Years, Once. The default is Months.
    • Annual Effective Rate Calculation: Whether the annual cost of borrowing is calculated based on the Annual Percentage Rate (APR) or the Annual Percentage Rate of Charge (APRC).
    • Is With Equal Installments: Select the checkbox if the installments are equal, so the annuity (also known as PMT) value calculation is needed, and the Principal is calculated with formula Annuity minus Interest. If there are Commissions that appear on the Payment Schedule, these Commissions are not included in the annuity calculation.
    • Installment Value Custom: If you select the checkbox with multiple disbursements, the Principal component of the installments is the one calculated for the entire Financed Amount, even if it was not entirely disbursed.
      For example, if Financed Amount is 10,000 EURO and the value calculated for Principal component of the Installments is 800 EURO, and the customer disburses only 5,000 EURO, the Principal component remains 800, but the Interest is calculated for the 5,000 EURO that were disbursed.
      If Installment Value Custom = False, then the Is Manual Value and Royalty/ Initial Principal Value fields at the contract level are read only.
      If Installment Value Custom = True, then the Is Manual Value field at the contract level is editable, with False default value.
    • Use Fix Maturity Date (from Activation Date): If you select the checkbox, then the Maturity Date equals to Activation Date plus the Contractual Period in Months, i.e. the number of installments depends on the Activation Date.
      If the checkbox remains unselected, the number of installments are fixed, the Maturity Date is equal to the First Installment plus the Contractual Period in Months, e.g. Installment date is on the first day of the month, this results in the Maturity day to be the first day of the month.
      NOTE  
      This is only valid for Period Type = Months.
  1. Click Save and reload.
  2. In the newly displayed Payment Schedule Type Details section, add fields for any additional columns you want to display in the payment schedule (fees, insurances, or other payment dimensions). Note that the fields change according to the selection of Column Type and Calculation Method.

    • Title: Insert a suitable title for the detail.
    • Column type: Select one of the following types: Payment Schedule Dimension, Fee Dimension or Insurance Dimension. Note that the selected type triggers changes in the displayed fields.
    • Column Repayment Schedule: Select one of the columns that is assigned in the Payment Schedule.
    • Calculation Method: Select a method. It triggers changes in the fields. There are the predefined values that are taken into consideration when calculating the Interest:
      • Linear: calculated as Amount / Number of Installments.
      • Effective Rate: percent applied to the Source field (see below), usually to the Remaining Value.
      • Fixed Value: a constant value that is completed in the Payment Schedule.
      • Column Formula: formulas having other columns as parameters. Formula used is specified in the field Formula that is displayed when this option is set.
      • Remaining Formula: specific to a column of Remaining.
      • Once: the value is paid once.
      • LinearOnYear: a value calculated based on the Remaining Value at the beginning of the credit year and a given percentage, divided in installments with the specified periodicity.
      • FeeOnce: takes into account a fee that is paid once.
      • ProductLevelFixedValue: method that calculates the capital percent defined for cards and credit cards type of products.
    • Operation Item: It is the item allocated to a column in the Payment Schedule on which the amount calculated at this step is allocated. Select an item from the list.
    • Fee: Select a fee configured in the Product Dimensions.
    • Fee Type: Select a fee type configured in the Product Dimensions. This is helpful when, for different banking products, there are different values applicable for the same type of fee.
    • Source: It is the source element from the JSON file returned by the Payment Schedule calculation from where to take the value.
    • Insurance type: Select an insurance type.
    • Is Calculated In Advance?: Select the checkbox if the calculation is done in advance.
    • Is calculated Upfront: Option available for Insurance Dimension and Fee Dimension. Select the checkbox for insurance or commissions that need to be paid at the activation of the lending contract.
      NOTE  
      This is only valid for products with Period Type = Months.
    • Totalization For Grace Period: This checkbox is available when the Calculation method is set to Effective Rate or Fixed Value. If you select it, then the values that are not applied during Grace period are added to the first non-grace installment.
    • Adjust Last Installment: This checkbox should be checked most of the time, as rounding loses of precision can exist, and the sum of Principal paid monthly should be the same as the Financed Amount.
    • Operation Item: Select the operation item from the list for which this schedule type details should apply.
    • Formula: This checkbox is available when the Calculation method is set to Column Formula or Remaining Formula or Once or LiniarOnYear. The formula can use other Schedule Details Names. For example, for a total installment calculated as Principal+Interest+ManagementFee that were added to Payment Schedule Type Details earlier.
  3. If you selected Fee Dimension, then fill in the following fields: Fee, Fee Type or Source.
  4. If you selected Insurance Dimension, then fill in the following fields: Insurance class or Source.
  1. Click Save and close. Repeat to add more details.
NOTE  
The first installment can be adjusted in situations when the algorithm forces an equal installment, by adjusting the Principal paid in the first interval.

For a Payment Schedule with equal installments, the first installment interest is calculated for the number of days between Activation Date and First Installment Date.

In general, for this first installment, the number of days can be lower or higher than the normal interval, so the Interest calculated makes the first installment to be different than the others.

The following picture illustrates the payment schedule type and the details defined for Credit Card Installments calculation:

Schedule Type Columns

To configure the calculation steps, use the Schedule Type Column option in the Settings menu. The order of the steps is determined by the Calculation column.

  1. In the main menu, click Products > Products > Settings > Schedule Type Columns, and the Schedule Type Column List page opens, showing all the already created schedule type columns.
  2. Click Insert to add a new column type.
  3. In the newly opened Add Schedule Type Column page, select a Column Type from the list: Payment Schedule Dimension, Fee Dimension or Insurance Dimension.

  4. Enter a Name for the column.
  5. Click Save and reload.
  6. The Payment Schedule Types section is displayed after saving, showing all the payment schedule types using this column, with the following information:
    • Name: The name of the Payment Schedule element.
    • Payment Schedule Code: The code of the payment schedule.
    • Calculation method: The calculation method.
    • Column Type: The column type: Payment Schedule Dimension, Fee Dimension or Insurance Dimension.

Insurance

Insurance Document

This section allows you to track all the documents that have been set up in various insurance product types to be requested from or provided to insurance customers, such as identification documents or Terms and Conditions.

Insurance Peril

An Insurance Peril, or condition - for example earthquake, car accident, tornados, theft, death, or disability, informs about the type of coverage for a particular insurance product, or product item (coverage). You can define perils independently from products, so that they can be used in conjunction with multiple insurance product types. Depending on your product, you can attach one or multiple perils, or conditions to it.

In FintechOS Studio, you can find an overview of all the insurance perils registered in your system - your nomenclature of perils, or conditions. You can also create and configure new records. Follow the steps below to add a new peril record.

  1. In the main menu, navigate to Products > Products > Settings > Insurance Peril. The Insurance Peril List is displayed, containing all the existing records.

  2. Click Insert to add a new peril.
  3. Fill in the following fields to configure the peril:
    • Insurance Peril Name: Name of the insurance peril.
    • Max Notify Period: Maximum period for the notification of the peril.
    • Event Count Limit: Number of events covered by the policy.
    • Implicit Reserve: Amount of the prudential reserve to be deposited for the current policy.
    • Implicit Reserve Currency: Currency of the prudential reserve.

  4. Click Save and Close. You can view the newly created record in the Insurance Peril List.

Insured Objects

IMPORTANT!  
For future use. Do not change.

This item allows you to see the insured objectsClosed Item or entity that is covered by an insurance policy. that can be covered in various insurance product types.

Plan Dimensions

Plan Dimensions, also referred to as Dynamic Dimensions, are values used to fine-tune claims or other financial parameters of an insurance plan (e.g., copay amounts).

Each plan dimension includes the following parameters:

  • Name - The identifier of the plan dimension.
  • Allows Percentage - Specifies how the plan dimension amount is defined:
    • Unchecked - The plan dimension amount is entered as a fixed value.
    • Checked - The plan dimension amount is calculated as a percentage of a reference value (e.g., a copay based on a percentage of the insured amount).

General

Currencies

Currencies define the denominations used across product components, including deposits, loans, fees, and interest calculations. The platform supports both fiat currencies and cryptocurrencies, allowing products to be configured with either traditional or digital asset values.

To set up currencies that are available for your products, in FintechOS Studio, go to Main Menu > Products > Products > Settings > Currencies.

Each currency has the following parameters:

Parameter Description
Code Unique identifier of the currency (e.g., USD, EUR, BTC).
Name Full name of the currency.
Symbol Symbol used to represent the currency (e.g., $, €, ₿).
Is Crypto Indicates whether the currency is a cryptocurrency. Select this option for cryptocurrencies or leave unselected for fiat currencies.

Lexicon Term

Lexicon terms are parameters (like the debt-to-income ratio, credit score, current credit amount, risk zone, etc.) used in the context of specific product types for rules, data sets, or formulas. Lexicon terms are the building blocks of product evaluations, such as requiring an insurance, calculating a price, offering a discount, or determining eligibility.

To set up the lexicon terms that are available for your products, in FintechOS Studio, go to Main Menu > Products > Products > Settings > Lexicon Term.

Each lexicon term has the following parameters:

Parameter Description
Name Name of the lexicon term.
Type Data type of the lexicon term.
  • Boolean - A selection between two mutually exclusive choices. Can be used for terms such as whether or not an applicant is an existing customer of if an insured house has or doesn't have an alarm system.
  • Date - A calendar date. Can be used for terms such as birth dates.
  • Option Set - Allows users to select a value from an option set (for details, see Option Sets).
  • Lookup - Allows users to select an option from a list of entity records. When configuring a lookup lexicon term, you must specify:
    • Lookup Entity - The business entity that contains the records to select from.
    • Lookup Column Key - The attribute that uniquely identifies each record within the entity (e.g., product code or SSN).
    • Lookup Column Value - The attribute whose values are displayed in the list of selectable options (e.g., loan term or interest rate).
  • Numeric - A numeric value. Can be used for terms such as a credit amount or insured value.
  • Numeric Array - A list of numeric values. Can be used for terms such as the historical monthly account balances or premium payments history.
  • Object - A structured data item with multiple related key-value field pairs. Can be used for terms such as a single insurance policy containing fields like policy number, coverage type, and expiration date.
  • Object Array - A list of objects. E.g.: list of a customer's bank accounts, each with its own account number, balance, and account type.
  • Text - An alphanumeric string. Can be used for terms such as license plate numbers or VINs.
  • Text Array - A list of alphanumeric strings. Can be used for terms such as a list of previous insurers, a collection of policy reference numbers, or a set of beneficiary names.
  • Value list - A list of preset values. Can be used for terms such as home types, engine displacement ranges, risk zones, etc.
Data Category Select a classification for the type of data that the lexicon term is modeling (personal information, digital and behavioral data, legal representatives, employment and financial information, etc.).
Status
  • Draft - The lexicon term hasn't been used yet and can still be edited.
  • Active - The lexicon term is currently in use. It can no longer be modified.
  • Inactive - The lexicon term is suspended from use.
Description Enter a description of the lexicon term. This explanation is visible when designing a product and selecting the lexicon term.
Context Enriched Before
  • First choice of a boolean lexicon term (e.g.: is, has, agrees with). If selected, this choice is displayed before the lexicon term name (e.g.: is in accordance with GDPR).
  • For non-boolean lexicon terms, this is an optional text displayed before the term (typically a verb), e.g.: is, has, covers. You can combine it with the Context Enriched After parameter to create complex syntax such as: covers ... % of the total surface.
Context Enriched After
  • Second choice of a boolean lexicon term (e.g.: is not, doesn't have, doesn't agree with). If selected, this choice is displayed before the lexicon term name (e.g.: is not in accordance with GDPR).
  • For non-boolean lexicon terms, this is an optional text displayed after the term (typically a descriptor), e.g.: meters long, % of the total surface, consecutive days. You can combine it with the Context Enriched Before parameter to create complex syntax such as: covers ... % of the total surface.
Lexicon Term Values Value list lexicon terms only.
Use this grid to configure the values that are available in the list.
Lexicon Context Use this list to set up the product types where the lexicon term is available.

Roles and Permissions

This item allows you to assign Product Factory permissions to Security Roles. By default, the following six security roles are preconfigured with Product Factory permissions:

  • Approver - Allows users to view and approve products and offers.
  • OfferEditor - Allows users to view, create, and edit offers.
  • OfferReadonly - Allows users to view offers.
  • ProductEditor - Allows users to view, create, and edit products.
  • ProductReadonly - Allows users to view products only.
  • ProductFactoryAdmin - Grants all Product Factory privileges, except those related to product testing, offer testing, and working with Custom Product Types.

If you have the config.edit permission, you can assign Product Factory permissions to any security role. To do so:

  1. In FintechOS Studio, go to Main Menu > Products > Products.
  2. Click Settings.
  3. From the drop-down menu, select Roles and Permissions.
  4. Double click the security role you want to configure. If you have the roles.manage permission, you can also click + Add Role to create a new security role.
  5. Select all the Product Factory permissions you want to assign to the security role:
    PermissionDescription
    config.editAssign Product Factory permissions to security roles.
    roles.manageCreate new security roles.
    offer.approveChange an offer's state to Approved.
    offer.cloneClone an offer.
    offer.closeChange an offer's state to Closed.
    offer.editEdit an offer.
    offer.tests.configureConfigure offer test cases.
    offer.tests.runRun offer test cases.
    offer.tests.viewView offer test results.
    offer.viewView offers.
    product.approveSet a product's state to Approved.
    product.cloneClone a product.
    product.closeSet a product's state to Closed.
    product.createCreate products.
    product.deleteDelete products.
    product.editEdit products.
    product.tests.configureConfigure product test cases.
    product.tests.runRun product test cases.
    product.tests.viewView product test results.
    product.version.createCreate new product versions.
    product.viewView products.
    producttype.activeChange a product type's state to Active.

    producttype.duplicate

    		Duplicate a product type.
    producttype.inactiveChange a product type's state to Inactive.
  6. Click Save Changes.

Underwriting Data Set Values

This item allows you to define lists of terms that constitute valid terminology for the Approved, Derogation, and Rejected underwriting outcomes. For each outcome, you can provide the corresponding terms separated by commas:

Outcome Data Set Values Examples
Approved Approved, Passed
Derogation Derogation, Manual Analysis
Rejected Rejected, Not Passed