Oracle Banking Platform

Transcription

1 Oracle Banking Platform Release Notes Release E December 2013

2 Oracle Banking Platform Release Notes, Release E Copyright 2013, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR , Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

3 Contents Preface... v Audience... Documentation Accessibility... Related Documents... Conventions... v v v vi What's New... vii Oracle Banking Base... Oracle Banking Current Accounts and Savings Accounts... Oracle Banking Loans... Oracle Banking Term Deposits... Oracle Banking Limits and Collateral Management... Oracle Banking Relationship Pricing... Oracle Banking Originations... vii viii ix x xi xiii xiii 1 System Requirements and Specifications 1.1 Tech Stack Components Out of the Box Applications Integrations Known Issues 2.1 Oracle Banking Platform Known Issues iii

4 iv

5 Preface Oracle Banking Platform Release Notes contains the release information for Oracle Banking Platform Release This Release Notes document contains the details of the new components that are a part of the release, and includes important known issues as of version Oracle recommends that you review its contents before installing, or working with the product. This preface contains these topics: Audience Documentation Accessibility Related Documents Conventions Audience This release note is intended for the users of Oracle Banking Platform. Documentation Accessibility For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at Access to Oracle Support Oracle customers have access to electronic support through My Oracle Support. For information, visit or visit if you are hearing impaired. Related Documents For more information, see the following documentation: For installation and configuration information refer the Oracle Banking Installation Guide For a comprehensive overview of security for Oracle Banking refer the Oracle Banking Security Guide v

6 For features, functionality, and options available for Oracle Banking and the licenses required to use them refer the Oracle Banking Licensing Guide For information related to setting up a bank or a branch, and other operational and administrative functions refer the Oracle Banking Administrator s Guide For information related to customization and extension of Oracle Banking refer the Oracle Banking Extensibility Guide Conventions The following text conventions are used in this document: Convention boldface italic monospace Meaning Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary. Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values. Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter. vi

7 What's New This chapter presents an overview of the new features and enhancements in Oracle Banking Platform Release Oracle Banking Base This section describes the key enhancements of Oracle Banking Base that are released as a part of Oracle Banking Platform Release Party Information Following are the key enhancements in Party Information: Relationship Management Relationship Management has been introduced in the solution to enable banks to maintain business relationships for large corporate and SME customers and enable specific access. KYC KYC solution now enables banks to maintain rules by which KYC can be carried out. Party Merge A mechanism has been built in the system where the parties IDs are merged and system will have a single party ID. The party ID on the accounts will also be replaced. Party Financials It now supports capture of multiple financial informations in definable format for different party types. Alerts Following are the key enhancements in Alerts: Ability to send alerts to 3rd parties: Earlier alerts were sent only to account holders. As part of Oracle Banking Release 2.2 enhancement alerts are sent to third parties like solicitors and brokers. Ability to send alerts to other Related parties linked to the account apart from the account holders. Ability to send alerts to Secure Mailbox. vii

8 Document Management System (DMS) Following are the key enhancements in DMS: Additional Primary Index Tracking Customer is the default and Primary Index for all Document Types, except for Origination. The "Additional Primary Index" linked in the Document Type definition screen is the default secondary index. User can, however, add other Indexes for storing the document. Recurring Nature of Document Certain documents are of recurring in nature i.e. have to be taken from Customer on a periodic basis unlike some others, which are treated as Received forever. The optional field "Period" can be used in case of documents, which though recurring in nature, can be treated as valid for a pre-determined period, usually in months. Scrutiny for Document Type Scrutiny of a document can be done internally or externally or in both ways, by adding an appropriate scrutiny type for a document, say Passport, in the Document Type Definition (Fast path: CNM01) screen. Note: For more information on the product features offered by Oracle Banking Base refer its functional overview document. Oracle Banking Current Accounts and Savings Accounts This section describes the key enhancements of Oracle Banking Current Accounts and Savings Accounts that are released as a part of Oracle Banking Platform Release Account Opening System supports creation of Current Accounts and Savings Accounts (CASA) with back value date within Backdated Account Opening Allowed period mentioned at the offer level. System supports Account opening sourced by Agents such as brokers. The agent details are stored at the account level. Backdated Limit Linkage to CASA Account System supports creation of CASA account and linkage of Overdraft (OD) limit to it with back value date when account is opened through Origination Process. Capture of Transacting Party Details System supports capturing Transacting Party details which are required for Anti Money Laundering (AML) tracking when transaction is done with Cash mode and transaction amount breaches the threshold limit maintained at the Bank Level. Simulation of Account Closure Amount System supports inquiry of simulation of closure of account within CASA Closure Simulation Allowed Days maintained at Product Level. The maximum value allowed for the simulation is 20 days. This simulation inquiry provides the amount to be paid to close OD facility. Hence it is useful for customers having CASA accounts with OD facility. Customers can close the OD facility and retain the CASA Account. viii

9 Multi Fund Deposit System supports deposit of cash and cheques simultaneously in a single transaction. It is configurable whether to display a single entry or multiple entries in statement for Multi Fund Deposit Transaction. Also it is configurable whether to charge a single fee for multi fund deposit transaction or charge separate fees for each cheque deposit and cash deposit in a Multi fund deposit transaction. Note: For more information on the product features offered by Oracle Banking Current Accounts and Savings Accounts refer its functional overview document. Oracle Banking Loans This section describes the key enhancements of Oracle Banking Loans that are released as a part of Oracle Banking Platform Release Backdated Transactions Backdated transactions such as backdated offer swap or backdated fee refund are done in order to rectify the operational errors and to support the business cases in a de-centralized set up where the request capture and execution happens on two different dates. Backdated Reversals Backdated reversals such as backdated reversal of advance payment are done to rectify the operational errors. Delinquency Counters Delinquency counters provide important information to understand the customer s payment patterns and risk behavior. Delinquency counters will count the number of dues which are past due during a defined period of time. Loans module supports display of delinquency counters at account level. Amend Loan Account Loan account can be amended as part of the existing facility amendment. As a part of amend account changes such as increase or decrease of sanctioned amount or term, update of communication preferences, repayment and rate type changes can be made. Annual Interest In Advance Loans Oracle Banking Loans supports the Annual Interest in Advance functionality. AIIA loans are generally offered with fixed rate terms of 1, 2, 3, 4 or 5 years. On completion of Interest only period, the loan will typically be converted into an equated monthly installment repayment schedule. Fees Based on Rate Type Oracle Banking Loans supports charging different fees in fixed and variable rate period for an event. Penalty Fee Oracle Banking Loans supports charging of penalty fee in case if customer defaults on repayments. This fee is charged in the loan account at the end of grace period. ix

10 Non Financial Transactions Display in Statement Oracle Banking Loans supports display of non financial transactions such as interest rate changes, change in loan account preferences and change in installment payment amount in the statement. Change Repayment Type or Rate Type Credit Assessment Oracle Banking Loans supports the option of movement of an account from Principal to Interest Only repayment stage. Option is available in the system to initiate a credit assessment for such cases. Loan Payout Quote Oracle Banking Loans supports generation of a payout quote for Early Final Settlement (EFS) for a particular date. If the EFS transaction is done within the period (from the quote generation date till the specified date), the amount specified in the quote needs to be applied. Periodic Credit to Loan Oracle Banking Loans supports setting up of periodic credit instruction to a loan account. The provider account is always an external account i.e. an account from other bank. Simulators Oracle Banking Loans supports simulators for early final settlement, partial payoff, rate change and payment appropriation. Inquiries Oracle Banking Loans now also supports inquiries for overdue aging history and early final settlement quote. Note: For more information on the product features offered by Oracle Banking Loans refer its functional overview document. Oracle Banking Term Deposits This section describes the key enhancements of Oracle Banking Term Deposits that are released as a part of Oracle Banking Platform Release Account Opening Oracle Banking Term Deposits supports creation of Term Deposit (TD) Account with back value date within Backdated Account Opening Allowed period mentioned at offer level. Backdated TD Account Opening is supported till tax occurrence event. System supports Account opening sourced by Agents such as brokers. Capture of Transacting Party Details Oracle Banking Term Deposits supports capturing Transacting Party details which are required for Anti Money Laundering (AML) tracking when transaction is done with Cash mode and transaction amount breaches the threshold limit maintained at Bank Level. x

11 Note: For more information on the product features offered by Oracle Banking Term Deposits refer its functional overview document. Oracle Banking Limits and Collateral Management This section describes the key enhancements of Oracle Banking Limits and Collateral Management that are released as a part of Oracle Banking Platform Release Limits Mangement Following are the key enhancements in limits management: Automatic Closure of Credit Facility (only Non Revolving type). Total of Sub credit facility limits should be equal to the Parent Credit Facility limit in case of Non Revolving Type of Credit Facility. Changes to the default or base lending category code to be applied to all existing facilities and not limited to new facilities. Applicable only for the Loan to Value Ratio (LVR) Calculation based on Quadrant Method - Deduction Process. Inclusion of additional attributes for searching Credit Facility in the Facility Summary Screen. Enhancement to the fields displayed as part of summary search result of credit facility. Collateral Linkage Panel of Credit Facility to enhance to display the collaterals of Parties who can share their collaterals with the Borrower/s based on the Party to Party relationship in Party Module. Inclusion of Notice days field as part of Facility Category. Provision to Capture Introducer and Broker at Credit Facility level. If the last availment date is lesser than the current date, then the system should not allow the user to increase the credit facility amount. Provision to update only the outstanding exposure amount without updating the utilization and available amount. Provision to capture periodic fee at Parent Credit Facility Level. Introduction of new LVR method i.e. Uniform LVR method for Calculating the Loan to Value Ratio. Trigger of re-pricing when the Low Doc attribute changes to Full doc. Creation or Amendment of Credit Facility with backdated date. Creation of Standalone Credit Facility (External Credit Facility not originated through Oracle Banking Platform). Capture Collateral Details Following are the key enhancements under collateral details: New collateral types have been introduced. New collateral categories have been added to existing collateral types. Multiple charge types are allowed to be set-up for a collateral category, with one being selected as default. xi

12 Multiple charge types are allowed to be set-up for a collateral category, with one being selected as default. Modification of address details is allowed. Modification of collateral owners is allowed (with validations). Linkage of External Term Deposit and Proposed Term Deposit to type of deposit collateral. Notice days for collateral expiry. Introduction of new Security Types of Debentures or Bonds, Certificates (in addition to existing security type of Shares or Stock. Introduction of Bank Value Hair Cut percentage at the security level. Addition of Probable Match criterion in the collateral de-dupe maintenance (any one or more of the de-dupe parameters can be selected for checking 'probable match'). Collateral Valuation and Title Search Following are the key enhancements under valuation and title search: Workflow enabled valuation and title search process (from standalone LCM screen). Separate sequential tasks to be created for request details, report capture, verification etc. Addition of Minimum Number of Valuations required for the collateral rule. Ability to manually select valuers and title search agents, in addition to existing capability of system derived valuers (based on valuer/title search agent preference). Ability to amend title search report. Verification is made mandatory even for online title search report. Conditions Following are the key enhancements under Conditions: Provision to extend the due date for internal type of Conditions and capture the reason thereof for such extension. Capture of Reason to be made mandatory if the Condition compliance breached status is marked as Yes. It will be optional if the status is marked as No. This will be applicable only for the subsequent type of conditions. Compliance Status, Party ID and Party Name to be the search criteria in the Condition Status Update and Condition Linkage Summary Screen. New status 'Override' to be included which will be applicable only for the Precedent and Preliminary type of conditions and mandatory capture of reason thereof for overriding the Conditions. Insurance Following are the key enhancements in Insurance: Support for Consumer Credit Insurance (CCI) type of policies. Introduction of 'cooling period' concept for policies. Enhancement to 'Insurance Policy Maintenance' with additional parameters. CCI Eligibility rule included in insurance policy maintenance. xii

13 Integration with Loans module for refund of premium for CCI type of policies. Note: For more information on the product features offered by Oracle Banking Limits and Collateral Management refer its functional overview document. Oracle Banking Relationship Pricing This section describes the key enhancements of Oracle Banking Relationship Pricing that are released as a part of Oracle Banking Platform Release Definition of Fee Groups for Free Transactions Bank can group fees and define how many transactions in the group can be free. The free transactions evaluation can be based on Occurrence, Cheapest or Costliest. Support For Fees at Facility level Periodic fees can be charged to credit facilities. Note: For more information on the product features offered by Oracle Banking Relationship Pricing refer its functional overview document. Oracle Banking Originations This section describes the key enhancements of Oracle Banking Originations that are released as a part of Oracle Banking Platform Release Sourcing Entity Capture & Processing - Applications sourced by Broker / Introducer Affiliates related enhancements & handling within Origination Consumer Credit Insurance (CCI) support for Loans & Credit Cards Capitalization of fees and insurance (LMI & CCI) Generation & printing of application form(s) Financial Profile Linked to employment, multiple employment detail capture, cloning of financials, net customer position, ratios Property Details capture for stamp duty computation Funds Table New funding parameters capture & display, Capitalization handling Conditions Capture in application form, subsequent stages in origination workflow Bundling Recommendation view, selection & link existing account(s) to bundle Credit Card Origination New Credit Cards & Amend Credit Card Limit options Structure Solution Current and Savings Account account configuration Term Deposit account configuration xiii

14 Mechanism to perform manual review for credit assessment in case of timeout scenario Edit Submission option in case of Reject Offer letter Fraud Status Resolution Task Valuation & Title Search process integration Verification Request More Information status with comments & conditions capture Create Offer - Split into Create Offer & Accept Offer Create Offer outbound documents - Offer Letter & CCI welcome letter templates Settlement Instruction Backdated, Partial Settlement, New modes for contribution Variation outside Arrangement Application Tracker related enhancements Joint Application Form related enhancements Notes Capture and other miscellaneous enhancements such as Cancel Application availability in Application Form and Integration for Proposed Term Deposit as collateral Note: For more information on the product features offered by Oracle Banking Originations refer its functional overview document. xiv

15 1 1System Requirements and Specifications This chapter lists the Oracle Banking Platform Release system requirements and specifications. 1.1 Tech Stack Components Oracle Banking Platform installation and configuration will not complete successfully unless users meet the following hardware and software pre-requisite requirements before installation: Database Oracle Database Operating System Oracle Enterprise Linux Server 6.4 (linux x86 64bit) Red Hat Enterprise Linux Server release 6.4 (Santiago) Kernel el6uek.x86_64 Oracle VM server release (Optional) Enterprise Application Server Oracle Weblogic Server ( ) with Oracle Jrockit JDK ( ) - jrockit-jdk1.6.0_51 Integration and Process Management Oracle Service Oriented Architecture (SOA) Suite Oracle Data Integrator (ODI) Systems Management Oracle Enterprise Manager - 12c Oracle WebServices Manager Identity Management Oracle OPSS Client Oracle Entitlement Server (OES) Oracle Adaptive Access Manager (OAAM) Oracle Internet Directory (OID) System Requirements and Specifications 1-1

16 Tech Stack Components Oracle Identity Manager (OIM) Oracle Access Manager (OAM) Content Management Oracle Imaging and Process Management / Webcenter Content Business Intelligence Oracle Business Intelligence Publisher Tools Oracle Repository Creation Utility (RCU) (Compatible with SOA) (or as applicable) Oracle Universal Installer Out of the Box Applications Integrations Integrations with Oracle Financial Service Analytical Applications (OFSAA) Oracle Financial Services Data Foundation (FSDF) Oracle Financial Services Loan Loss Forecasting and Provisioning (LLFP) Oracle Financial Services Funds Transfer Pricing (FTP ) Integrations with Oracle Customer Hub (OCH) Oracle Customer Hub (OCH) IIR-DQ AIA Foundation Pack Oracle Documaker Oracle Documaker on FMW For more information on the Oracle Banking Platform requirements from an environment perspective including minimum hardware requirements with Operating System (OS) and the middleware software products which the Oracle Banking Platform solution depends and runs on (e.g. Database or Weblogic) or interfaces with (e.g. OID or IPM) refer the Oracle Banking Platform Installation guide. 1-2 Oracle Banking Platform Release Notes

17 2 2Known Issues This chapter covers the known anomalies in Oracle Banking Platform Release Oracle Banking Platform Known Issues This section describes the known issues associated with Oracle Banking Platform. Table 2 1 Known Issues in Oracle Banking Platform Release Minor issues in Online Help for LN100 - Manage Loan Account (Loan Serve) If the same affiliate is linked to existing applicant and newly added guarantor, system will not display the existing Correspondence Preferences and Holder Preferences for the account in the respective panels during account configuration. Also, system displays the existing affiliate party in the 'link affiliates' panel There is a difference in the "Name on Title" field in the collateral ownership panel in the collateral details screen. This field appears as "Name of Title" in the Origination screen during capture of collateral details Collections expects User Id in upper case and all the SQL queries return incorrect result if characters in User Id string are in lower case Stop Payment transaction does not display any notification message when sent for approval due to fee negotiation During 'Collect Fees', the 'Ledger' mode for settlement is NOT supported as part of Origination. However, this should NOT be a problem when origination fees are capitalized since such fees will be part of the facility amount and the nominated loan account. In case of 'deferred' fees, these will be 'collected' from the nominated account identified as part of 'Structure Solution' stage in Origination Currently, there is a validation that 'outstanding balance' field cannot have a value greater than 'original amount'. However, this is incorrect validation which will cause the user to not move out of financial details step in the application form. A workaround has been put in place by providing user Id to Collections in upper case in 2.2 Workaround is to collect the fee via the nominated account in structure solution. Such fees will be 'deducted' from the final settlement. Known Issues 2-1

18 Data partitioning has to be done depending upon the business object used in the consumption screens. For example: The dataset is defined for a business object (com.ofss.fc.domain.commonservice.currency.dto.currency Def) and the businessobject being used in origination application form screen is com.ofss.fc.domain.pm.entity.casa.casaproductcurrencyatt ributes then partitioned currency will not be displayed If RPA balance is present in the account and if offer swap transaction is done then, system will try and recover the unbilled components (interest, periodic fee, penalty interest) from RPA balance and capitalize only the remaining amount In case of variation 'decrease in loan term', the simulation of repayment schedule is not correct due to incorrect balance base and interest rate Minor issues in Online Help for Bundle Details screen System will not support backdated transactions beyond 'Freeze Repayment' type hardship relief. There is no validation in the system. This has to be operationally controlled If the rates of interest are tiered in nature, then the handoff to OFSAA is not possible due to table structure issues As part of Amend, if user tries to do increase in sanctioned amount and offer swap, system does not validate with the remaining loan term due to which the account term will go beyond the facility term If one party belongs to multiple borrowing entities, then the mapping of this parameter when handed over to OFSAA will be incorrect The LOB from a multi entity perspective is not mapped from the handoff perspective from OBP to OFSAA There is no mapping for the field of location code for a party data when handed off from OBP to OFSAA While refunding origination fees debited to CASA Account, instead of passing correct set of accounting entries, system generates suspense entries A field name Subset mismatch found in online help As per the online help the Status field in proposed TD grid is editable which in not true as per tester comments. The same needs to be fixed in the online help The system charges Bundle Maintenance Fee from the nominated loan account even if the bundle has been un-subscribed by the party When settlement mode is selected as Own CASA, System does not display party ID field in settlement panel in few screens OCH does not publish the update for party address expiry to OBP. User should perform such reversal using Journal Voucher Entry screen. Address expiry has to be manually maintained in OBP after it is updated in OCH. 2-2 Oracle Banking Platform Release Notes

19 Since the system runs the immediate credit function for cheques which are below the clearing threshold value, the cheque deposit to accounts which are having AUF facility and the cheque value below the threshold amount is not allowed Currently, when an Add-on card holder is added the requisite documents defined in OBP can also be uploaded. However when the card holder is removed the attached documents do not get removed. Though these documents are present in the system, they would appear as not received by the system if the same "Add-on Card holder" is added/linked to the same or any other CC application When the same day reversal of a loan disbursal is done, which was disbursed to a managers cheque, the accounting part is handled but the status of the MC is not updated correctly System is providing benefit of AUF limit even after AUF limit expiry if AUF limit expiry is falling on holiday Whenever any facility or parameter is modified for CASA Account using CASA Account Preferences, Fixed period for the account is automatically getting changed which is incorrect Currently, the From address for a bank can only be one. There cannot be any differentiation made in the from address based on Market Entity or Business Unit When OD limit is attached to existing CASA Account with back value date, system is not computing the interest correctly System is not calculating interest correctly in case saving account is opened backdated and backdated transactions are performed for the account The Approver cannot see all the details entered as a part of Negotiation The Approver cannot see all the details entered as a part of Negotiation Reverse functionality for settlement instructions in Origination is not working if settlement mode is CASA In the factory shipped template available as part of R2.2, the system does not print the table of 'servicing fees' in the offer letter in case of multiple accounts under a facility Future Dated EFS Simulation value will not be accurate if there is Principal offset linkage on the account as on the current date and the same is expiring before the future dated simulation date The reversal entries in the statement will not be displayed properly for a redraw transaction reversed through EJ reversal screen As part of R2.2, in case the 'settlement mode' is used as either 'External Account' or 'MC', the system will NOT support the 'reversal' of the execution of settlement instruction. The information is passed from product and if the template is customized then the servicing fees section should be repeated per account. Known Issues 2-3

20 System will not validate the 'recommended' valuation type for a collateral vis-à-vis the allowed valuation type(s) for the particular collateral category via 'Collateral Category Preferences' within the 'valuation' landing task in Origination. This gets validated as part of the 'valuation request' task & therefore there is NO option to make any changes in recommended valuation type for that collateral The LMI related insurance policies cannot be inquired from the 'Insurance Linkage Maintenance' option An 'expired' submission (i.e. post the submission lag days beyond submission expiry date being lapsed) will appear as 'Expired' in the application tracker. Marking as 'expired' should also remove the 'proposed' facilities, if any. However, this has not been tested and confirmed. If this does not work properly, then user might get an error during amend lending facility option in Origination, that there is already a 'proposed' facility which will have to be removed (along with its internal dependencies) from the back-end with the assistance of technology teams The hardship design in 2.2 is unable to pass data field for case on (account/party) to event manager as a result event manager is unable to trigger any event on account/party related to Hardship Case Affiliates with relationship where 'collateral sharing' is enabled can be linked within the 'Ownership Details' panel in case of 'Property' type collateral / 'Guarantors' panel in case of 'Guarantee' type of collateral. However, system does not validate that such affiliates are captured or linked as 'Guarantor' in 'Applicant Details' panel in 'Product Details' step Principal, Interest as well as Fee component in the repayment Schedule has to be intimated to Collections module by Loans module. Currently, the hand off to collections module includes only Principal + Interest components In case of a book balance product, interest accrual starts on the unclear balance from the posting date of cheque. If the cheque returns before value date, this accrued interest should get reversed. Currently, it is not getting reversed This is considered as 'not a frequent' scenario where multiple applicant(s) have the same affiliate. Due to a validation in the document generation process, system will NOT generate multiple copies of the same document type to be dispatched to the same party. In this case, the submission will not move forward beyond 'Create Offer' stage in the origination workflow Report will not be generated for accounts pending closure due to pending fee amount. Workaround is as follows: 1. Validation in interface that the 'recommended' valuation type is applicable for the 'collateral category'. If not, then the interface should return that valuation is NOT recommended. 2. Update 'Collateral Category Preferences' to temporarily allow the valuation request for the concerned valuation type and collateral to go through. This issue can be handled with a different configuration. Current design has limitation to incorporate mentioned test case. Operationally ensure that the affiliates whose collateral will be linked to facilities should be captured as 'Guarantor' manually in 'Product Details'. 2-4 Oracle Banking Platform Release Notes

21 As part of 'amendment' to an account within the 'Variation Outside Arrangement' flow, if user is performing offer swap for an account then - in offer selector system should not display the offer to which account (being amended) currently belongs When system hold on the CASA account is getting removed due to credit interest in the account, in such case system is considering wrong balance base for interest computation for interest capitalization day If there is an account under hardship relief and then if it becomes eligible for reschedule due to an index level rate change, then the EOD aborts System is not updating the account closure details in OCH Batch updates are not published to OCH System shows the account's current offer also in the list of eligible offers while performing offer swap Variable rate period UDM applied from Origination will have start date of UDM equal to the 'variable period start date' of loan account. In case if backdated 'Change repayment type Rate type' is done which changes the variable period start date then, UDM start date also should get updated and should get aligned with the new variable rate period start date. Currently, system is not updating the UDM start date in the above case The updates to OD interest rate due to any event is not getting reported to collections Loan Product Preferences has a parameter 'Update Utilization on Capitalization'. The behavior of this parameter is that if this parameter is checked, then when principal arrears are raised during servicing of a loan account, the system will update the utilization and thereby eat into the 'Available Limit'. As such, if the account is fully disbursed, then the 'Available Limit' will be negative. The impact of this is that during 'Amend Lending Facility' option chosen from Origination where the user intends to amend an existing facility, the system will not allow the user to utilize the 'incremental' facility amount completely during Settlement Instruction. The system will try to earmark the additional amount and will fail since earmark function will not find the requisite available limit Collections considers NULL value as 0 and same is being displayed on UI as 0% ownership OCH only Parties are not getting fetched in Party Search in Origination flow. A validation existing in the system as part of the 'save' of the account configuration that the chosen offer does not belong to the same product under which the account exists. The only 'limitation' is that the handling does not happen in the system at an earlier stage in the account configuration i.e. either as part of offer selector processing or before the user selects 'Apply Now' to confirm offer selection. User will have to cancel such an offer and select an appropriate offer. The 'recommended' setup for loan product(s) should be that the parameter 'Update Utilization on Capitalization' should be kept as unchecked. This will ensure that any 'amendment' done to the facility and accounts within the facility will be handled properly as part of 'Settlement Instruction' task in OBP Origination. This has no business impact. Null value is getting displayed as 0%. It can be conveyed to users to treat this as null during user training. Known Issues 2-5

22 Hardship application runs with lot of operational inputs and there are a few stages where Collections is not aware of status of approvals when multi-level approval is required as rules are configured in SOA. At that point of time if someone performs a Hardship Cancellation in Collections, the application will be cancelled only in Collections but the same will not be reflected in CASA or Loan modules and these applications can go out of sync Party search from OCH is not happening As part of offer swap transaction, - All existing unpaid arrears are capitalized - Unbilled interest is charged in the account and then appropriated if RPA balance is available or is capped if RPA balance is not available - Pro-rated periodic fee is either capped or billed depending upon the fee treatment behavior defined at product level. System displays a non financial statement entry as 'total capped amount' which includes existing unpaid arrears and unbilled interest but does not include the prorated fee amount System is not calculating overline interest properly when OD limit is created with back value date If Backdated 'Change Repayment type Rate type' is done beyond an index rate change event in the account and if the account is moving from variable to fixed period then, system does not apply the new index rates. The rates applicable before the index rate change are applied A CASA account is linked as a principal offset account to another account. Then later as servicing, a holder is added to such a CASA account. The validation that all holders of the CASA account to be the same as that of the beneficiary account, is not done at this point In case of CASA Accounts which are in debit balance having hold placed on them, if any credit transaction is posted to the account, hold is to be removed from the account first. Due to bug in the system, system is debiting asset GL instead of liability GL which causes mismatch between liability GL and Net account balances Alert for insurance expiry is not getting generated currently during the EOD batch. Hardship cancellation is manual currently and user is prompted to put in cancellation reason at the time of cancellation. While doing that user can check operationally if the relief is in pending approval status in CASA/Loans module and only then cancel the application The lien summary table does not have the lien expiry date. The details when clicked, has the expiry date If UDM is given for the entire loan term and if due to some reason the loan term is reduced then system should align the UDM end date with the loan maturity date. Currently, it does not align it with the loan maturity date and displays the UDM end date as part of PMI stage in ELPBC screen There are duplicate contact method types configured and system works only for a specific contact method code Legacy Customers and Credit Card Account details are not getting fetched from OCH in Manage Bundle Screen. This can be handled by configuring a different contact method. Same has been included in Documentation. 2-6 Oracle Banking Platform Release Notes

23 Currently, there is no handoff to OFSAA from OBP party module for the financial information of a party as part of this release System will not permit 'user defined status' to be updated for a closed account. In the case where loan account has debit block status and is closed with some positive balance, user will not be able to remove money from RPA and pay it to the customer Alert will not be generated properly for auto rollover event if lead days as well as lag days are maintained as part of set up As part of 'Make Payment' option in Loan Serve screen, an option is available to pay 'no of installments'. If user selects this option, system will display the total amount to be paid considering the 'Principal and Interest' component of the Installment amount. It does not consider 'periodic fee' (if applicable) to be paid as part of repayment on every due date. Amount to Pay option available in the same screen can be used to pay the desired amount The Policy Number field in the Insurance Linkage screen should not be modifiable once the policy is created During Credit Card origination, in the structure solution screen (post decision), if the user changes the credit card offer (which was selected during product detail page), the system does not retain the field values which are common for both the offers, instead system refreshes the screen and user has to enter the data again. The user can re-enter the data which was common for both the offers. This is a manual workaround When there is a float extension for an inward clearing or an inward collection item, if there is again a failure condition on the retry date, the system does not behave in a consistent manner The UPK Demo simulations are not accessible If there is an account under hardship relief and then becomes eligible for reschedule due to an index level rate change, then the EOD aborts The transaction description in the statement will not indicate the amount in the transaction currency nor the exchange rate, when the account and transaction currency are different Receipt printing is not supported for payment made in Interest Only Loans Any suspended interest and fees which are not yet repaid, are not nullified when an EIPI type of loan is fully written off or closed in the natural course Edit and delete of already defined financial periods in a financial cycle is not allowed In case of joint collateral owners having Tem Deposits (TD) in joint names, the same TD is appearing twice - once under the individual name, another under the joint name Bucket movement due to proportionate OD results in change of overdue amount. This is not getting reported to collections. Known Issues 2-7

24 If an account having RPA balance is partially written off, system will debit expense only to the tune of 'written off amount less the RPA balance' Manage Loan account_blownup schedule is not proper while changing repayment day To include Temporary excess limit in net account balance should be driven by Include Behavioral Limit flag in Bank policy screen. However, Temporary excess limit is not considered in net account balance in the system and this is default behavior Alert will not be generated depending upon the lead day maintained for a future dated index rate change maintained in pricing module System runs into concurrency issue if nested configuration is done on CSAM, While taking action on existing cases using CSAM configuration. This can be handled by a different configuration in the current release When an application for hardship relief is committed by the maker, the information goes to collection rather than waiting for the approval of the application Penalty interest will be charged in the loan account if backdated EFS is done with process date as a date outside the grace period but back value date of EFS within grace period During lending account origination, if any interest margin rates are maintained during account configuration then these details are not getting displayed in the offer letter Bundle benefits are different for fixed and variable rate period. In fixed rate period, only fee benefits are given where as in variable rate period both fee and interest benefits are given in the account. When an account is linked to a bundle or is de-linked from the bundle it is rescheduled. As part of schedule generation, system is considering the benefits applicable (in case of linkage) or benefits to be dropped (in case of de-linking it from bundle) for the current rate period of the account only. Due to this the benefits applicable in the subsequent period (variable period) are not reflected in the repayment schedule For subsequent conditions, the 'End Date' has to be manually captured by the user. Also, the new end date has to be greater than the current posting date and also has to be greater than the start date. In case of condition capture or modification, this is a mandatory field as part of the 'Monitoring Preferences' panel as part of the 'Condition(s)' capture in OBP Origination. Via Origination, such conditions will be in 'Proposed New' status. However, from 'proposed new' kind of conditions which are not yet activated, this may not be accurate since the date might get lapsed by the time the condition is activated. (Note: Activation of condition(s) happens as part of either Create Account/Settlement Instruction task). The user has to ensure that if conditions of type subsequent are captured/modified as part of the origination workflow, the 'end date' for such 'proposed' subsequent condition(s) is manually maintained to be an end date beyond the account opening date During closure of a loan account, the fees waived in origination cannot be collected. 2-8 Oracle Banking Platform Release Notes

25 Amendment of an account through the 'amend flow' is not permitted if there is a future dated disbursement instruction maintained in the account. System currently permits customizing of an instruction to the current date but the deletion of same is not permitted Offer Letter generated for applications having Organization or Trust type of parties as applicants has following issues: 1. Letters Address affiliate is getting displayed instead of applicant. 2. Letter is addressed as Dear Sir/Madam System does not support backdated payin reversal if CASA Account is the mode for payin The instrument date for a cheque is not stored in instances and hence audit trail is not available System does not allow to set up debit blocked account as a beneficiary in standing instruction There is inconsistency in the way fee is calculated if there is a change in the PD between the last charging date and the closure date During 'copy' of an existing TD type of collateral to create a new TD type of collateral, certain fields are not getting copied properly If multiple backdated transactions occur, specially a credit followed by a debit, then the withholding tax computation will be inconsistent Account level facilities are not to be cloned to new account. Employee flag is present at account level. Hence, it is not be cloned to new account. However, cloning of employee account results in employee account System does not support 'Amend Facility/Account' scenario where the account nominated for Origination fee does not have any settlement amount UI Consistency issue in case limit utilized balance or net balance is in negative. In statement Inquiry and CASA account balance inquiry negative amount is denoted by brackets while in Account details panel, negative amount is denoted with -ve sign Loan provisioning event will not trigger a handoff to collections immediately. It will be sent as part of the subsequent event in loan which triggers a collection handoff During lending account opening, at structure solution stage user may need to nominate an account for charging 'facility level' fees. If user wants to nominate 'New' account, then system displays 'Product group name' with radio button to choose from. So in cases where multiple accounts are configured under a facility, multiple rows with same product group name are displayed and it's difficult to identify the exact account being nominated Alerts are not sent to the customer for backdated transactions including a backdated 'Change Repayment type Rate type transaction' No workaround in the 'factory shipped' template. As part of 'customization' of offer letter for organization/trust, the template can be appropriately changed for the salutation. Currently fee is getting charged. The issue is in calculating the fee to be charged. Known Issues 2-9