Home

Payments and Collections User Manual

1. Contract Reference az Branch Code az Source Code zZ Source Reference a Account Entry Reference az Their Reference zZ Custom Reference laz Station Id a Network az Batch Number FE Product Category az Product Code PE Priority az Customer Number Pe Records per page 15 T j T T j E Contract Reference Branch Code Source Code Source Reference Account Entry Reference Their Reference Custom Reference Stati Contract Debtor Id Creditor Ic Fa ORACLE In this screen you can use the following fields to search the PC Transactions Creditor Identification Reject Code Original Collection Reference Number Clearing Branch Local Currency Equivalent Amount Agreement Identification Interest Amount Reject Detail Transaction Currency To recall all the contracts click on Recall button When you click Search button the records matching the specified search criteria are displayed 5 16 Viewing Transaction Exception Summary You can view all contracts that encountered a Transaction Exception TR during upload through the Transaction Exception Summary screen You can invoke this screen by typing PCSTEXSQ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button amp Transaction Exception Queue E Search t Advanced Search 9 Reset D Clear All Case Sensitive Contract Reference Account Entry
2. la Rule Number Condition Return Type Result Error Message During contract processing the system validates the check digit against each of these validations Maintaining a Learning Database The learning database facility enables the system to intuitively learn about customers and the counterparties that are involved in payments or collection transactions that use a product category These transaction details are stored in the learning database to enable defaulting of transaction details whenever transactions are entered for the same customer counterparty and product category combination You can also e Manually create a learning database according to your requirement by entering the details to be stored in the Learning Database Counterparty Details screen e Upload details from an external system into the learning database Creating the Learning Database You can create a custom learning database by specifying details in the Learning Database Counterparty Details screen oat ORACLE You can invoke this Counter Party Details screen by typing PCDPTYDWM in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Counter Party Details H save main By Fields Customer Identifier Counterparty Identification Customer Type X Counterparty Type x Bic ID Bic Id Date of Birth Ez Counterparty Date Of Birt
3. Fag ORACLE ne Trn Ref Accou Debit ian Ex LCY Txn No nt Credit t Rate Amt Code 6 GTSZ A2 Debit 10 15 1 35 7 00 023 MNDO8 040000 4 GTSz 320055 Credit 7 00 023 MNDO8 10 040000 4 3 24 Viewing Mandate Cancellation Charges Summary De tails You can view a summary of the mandate cancellation charges in the Mandate Cancellation Charges Summary screen You can invoke this screen by typing PCSMNDCN in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Mandate Cancellation Charges Summary amp search C Advanced Search 5 Reset Y Clear All Case Sensitive Authorization Status 7 Source Code Customer No Records per page 15 x 10f1 Authorization Status Record Status Source Code Record Status v Branch Code Account No Branch Code Customer No AccountNo Charge Currency Ince In this screen you can view the following details e Source Code e Branch Code e Customer Id e Customer No e Transaction Code 3 54 ORACLE e Income GL e Charge Amount e Charge Currency You can view specific details of mandate cancellation charges by specifying values for the following parameters e Source Code e Branch Code e Customer Id e Customer Account 3 25 Maintaining Customer Stations You can maintain customer station details in the Payments amp Collection Cust
4. Main Detail Clearing Fields UDF Number Learning Database Applicable User Defined Field Number Display Sequence Number Description Information Validation Type None Minimum Length List Of Values Code Maximum Length Description Minimum Value Maximun Value Future Back Date Details Default Value Derived Rule J Mandatory Back Date Period Days Derivation Rule e Future Date Period Days M Back Date Period Days pm uta E Force Derivation Future Dates Shipped m 5 BET Offset Reject Recall Approval Redispatch Reverse Network Duplication UDF Details Rule ELCs Date Time Mod No Checker Record Status Date Time Authorization Status You need to define the specific attribute of each UDF that you choose to associate with the product category Refer the Creating Custom Fields Chapter in the Core Services User Manual for details After you capture the derivation logic specify whether it is mandatory for the system to capture the corresponding value based on the derivation logic that you have maintained You can do this by checking the box positioned next to the Force Derivation Logic field To specify the multiple conditions for validating the UDF values that you capture while processing a transaction you can click on the Rule button in this screen PPR ORACLE 3 26 5 3 27 The Validation Rule Logic screen is displayed as shown below UDF Field Rule
5. Field Name Field Description Branch Indicates the current branch code Processed Date Indicates the processed date Transaction Reference Number Indicates the transaction reference number Salary Date Indicates the salary date Employer Indicates the name of the employer Employee Indicates the employee name Employee Account Indicates the employee account Salary Amount Indicates the salary account CCY Indicates the currency of the transaction 10 3 ORACLE 10 3 Unprocessed Salary Report You can generate salary report using Unprocessed Salary Report screen You can invoke this screen by typing CORUNPSL in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button Unprocessed Salary Report Branch Details Report Date All Report Date Single Branch ReportFormat PDF Printer At Client Report Output Print Printer Branch Code You can generate this report for all the branches or a single branch alone You can indicate the branch for which the report is being generated using the following options e All If you choose this the system will generate the report for all the branches e Single If you choose this you need to specify the branch code for which the report should be generated The option list displays all valid branch codes maintained in the system Choose the appropria
6. SI No Charge Charge Source Branch Txn Code Income GL CCY Amt 1 Channel1 GTS 023 32005510 EUR 5 2 Channel2 GTS 023 32005510 EUR 7 Assume account A1 is in EUR currency and account A2 is in USD currency Let the number of mandate cancellations on a given day be as follows SI No Source Branch Account No 1 Channel 1 GTS A1 2 Channel 1 GTS A1 3 Channel 1 GTS A2 4 Channel 1 GTS A1 5 Channel 1 GTS A1 6 Channel 2 GTS A2 7 Channel 2 GTS A1 8 Channel 2 GTS A2 Assume the following exchange rate between USD and EUR Ccy1 Ccy2 Buy Mid Sell EUR USD 1 45 1 4 Sraa ORACLE In the above scenario the accounting entries posted on the day by the mandate charge batch will be as follows ne Trn Ref Accou Debit oe Ex LCY Txn No nt Credit t Rate Amt Code 1 GTSZ A1 Debit 5 00 023 MNDO8 040000 1 GTSZ 320055 Credit 5 00 023 MNDO8 10 040000 1 2 GTSZ Al Debit 5 00 023 MNDO8 040000 2 GTSZ 320055 Credit 5 00 023 MNDO8 10 040000 2 3 GTSZ Al Debit 5 00 023 MNDO8 040000 3 GTSZ 320055 Credit 5 00 023 MNDO8 10 040000 3 4 GTSZ A1 Debit 7 00 023 MNDO8 040000 4 GTSZ 320055 Credit 7 00 023 MNDO8 10 040000 4 5 GTSZ A2 Debit 7 25 1 35 5 00 023 MNDO8 040000 3 GTSZ 320055 Credit MNDO8 10 040000 3
7. Transaction Input Xx H save lt i Hold Product Category Contract Reference Collection Type Product Code bl Custom Reference RFD Type P Source Reference Product Type Network fal Main Transaction Details Pern tera Party Details Message Details UDF General Collection Details Creditor ID fal Agreement ID Debtor Category az Mandate Agrement Details Sequence Type x Amend Indicator Original Mandate ID Sign Date Amend Type Original Debtor Account Original Debtor Bank Creditor Scheme Details Original Creditor Scheme Details Other Details ID v ID x Collected Amount ID Type Gal Name N Related Transaction 1D Value ID Type bel Response Date Scheme T ID Value Response Advice x Scheme T azl pee ype _ Response Advice Basis COC H Split Details Events Charge Status ProjectDetails Duplication Details MIS Tax input By Date Time Authorized By Date Time Cancel Contract Status Authorization Status General Collection Details Creditor Identification For an Incoming Collection transaction or its reject recall mention the Creditor ID Agreement Identification For Collection transactions enter the Creditor or Debtor Agreement ID as applicable Debtor Category Select the debtor category from the adjoining option list Mandate Agreement Details Sequence Type Select the sequence type of the DD transaction as first collection or One off The following options are available e FRST First Collectio
8. Note For incoming collection contracts cancellation the approval is not applicable and system recalls the contract with reject reason provided in camt 056 Since incoming collection cancellation requests cannot be rejected by the receiver bank on receipt of Camt 056 for Incoming Collection Cancellation system directly recalls the original contract The mark EOTI validations check the pending approval for the cancellation requests Validation is done considering the cancellation acceptance parameters captured at product level Number of days from the product will be validated for pending approval based on the cancellation reason If any of the cancellation request is not approved then the system aborts the EOTI process Handling of Camt 056 for Incoming payments in Transaction Repair queue Any Incoming Camt 056 on repaired Incoming Payment will fail since the original Incoming Payment contract is in TR queue A static data for the error code PC SVV 106 is made available and used during cancellation processing when the original contract is in TR queue 30 ORACLE 5 25 2 5 25 3 This error code and error description is logged against the Camt 056 received and the cancellation transaction is logged into CR queue An information message is displayed logged describing that the cancellation transaction is logged into CR queue In order to respond to the received Camt 056 message Original Incoming Payment contract in
9. ORACLE 5 2 5 Specifying the Party Details Transaction Input N SSN H save lt Hold Product Category Contract Reference Collection Type Product Code PS Custom Reference RFD Type Source Reference Product Type Network Main Transaction Details Collection Details Message Details UDF Indirect Participant Customer Details Name City Of Birth Type Address 1 Country Of Birth Bic ID Address 2 Counterparty Date Of Birth ID Value Country Scheme Name Type Account Number Scheme Name Value Currency Issuer Bank code Initiating Party Details Name City Of Birth Bic ID Address 1 Country Of Birth ID Value Address 2 Counterparty Date Of Birth Scheme Name Type x Country k Scheme Name Value ID x Issuer Ultimate Debtor Details Customer Name City Of Birth Bic ID D E Country Of Birth azl 1D Value Counterparty Date Of Birth EA Scheme Name Type gt Scheme Name Value PRI Issuer Ultimate Creditor Details Customer Name City Of Birth Bic ID ID Country Of Birth az ID Value Counterparty Date Of Birth E Scheme Name Type a Scheme Name Value azl Issuer Split Details Events Charge Status Project Details Duplication Details MIS Tax Input By Date Time Authorized By Date Time Cancel Contract Status Authorization Status Indirect Participant Customer Details Indirect Participant Customer Name Specify the name of the customer participating in the indirect transaction Indirect particip
10. pacs 008 001 01 Outgoing Payment pacs 004 001 01 Reject of Outgoing Payment pacs 002 001 0 SEPA Direct Particpant Outgoing payment Reject of Outgoing Payment N o pacs 008 001 01 S pacs 004 001 01 g n pacs 008 001 01 pacs 004 001 01 Incoming payment Reject of Incoming Payment SEPA Direct Participant pacs 008 001 01 Incoming payment acs 004 001 01 eject of Incoming Payment bacs 002 001 02 Beneficiary Bank SEPA Indirect Statements Advices particpant Beneficiary A SEPA Direct Debit Transfer SDD is a transaction done for collecting funds from a debtor s account with a debtor bank and is initiated by a creditor via its bank the creditor bank as agreed between the Debtor and Creditor FPE ORACLE The picture below gives the schematic representation for SEPA Direct Debits processing EPA Direct Debit M Pacs 003 Outgoing Collection Pacs 002 Pacs 002 Pacs 004 lt Reject of Outgoing Collection Pacs 004 Recall of Outgoing Collection Pacs 007 Statements Advices Pacs 003 Incoming Collection Pacs 002 Pacs 004 Reject of Incoming Collection Pacs 004 Recall of Incoming Collection Pacs 007 Pain 007 y Reversal of Outgoing Reversal of Incoming Collection Collection The Common Payments Gateway is used to handle the SEPA Single Euro Payments Area messages for Credit Debit Transfers The incoming XML messag
11. As stated earlier a book transfer is the movement of funds between two accounts within the bank Thus while processing an outgoing book transfer the system will also need to process the incoming leg of the book transfer It would resolve the incoming product using the offset category specified adjacent to the book transfer product in the Product Category maintenance Similarly while processing transactions belonging to an incoming collection product category it is necessary to maintain the reject recall or approval product categories In such a case while rejecting an incoming collection transaction the system generates a reject of an incoming transaction automatically using the offset Reject Category For incoming transactions resulting in a recall or approval the system resolves a recall or approval product using the product category specified therein You need to maintain the offset categories for the different product categories as follows Table of Offset Categories for Direct Debit Product Category Offset Product Category Sroa ORACLE Outgoing Collection category for DD Incoming Collection category DD Incoming Collection category DD Incoming Reject category DD Incoming Recall category DD Reject of Incoming Category DD Reject of Outgoing Category DD Recall of Incoming Category DD Recall of Outgoing Category DD Product Category Offset Product Category Outgoing C
12. Debtor Category Specify the debtor category to which the debtor of the transaction belongs If you do not specify this the system will use a default value from the customer maintenance for incoming collections or creditor DD agreement for outgoing collections Priority This indicates the priority assigned to the contract in the processing queue If you do not specify this after product resolution the transaction acquires the specification defined for the product Split Indicator This indicates whether the collection transaction has been split into multiple contracts If it has not been split this field indicates Not Applicable If the transaction has been split this 760 ORACLE 3 35 field indicates whether the transaction being viewed is a parent transaction or a child transaction Creditor ID For an Incoming Collection transaction or its reject recall mention the Creditor ID Agreement ID For Collection transactions enter the Creditor or Debtor Agreement ID as applicable Source Code The source of the transaction is displayed here Station ID The customer station of the transaction is displayed here User defined fields The user defined fields are displayed in the UDF screen which can be accessed using the UDF Tab The fields will be displayed based on the display sequence no defined at the product category level and the label of the field will be shown in the language of the Oracle FLEXCUBE user
13. EY New Enter Query Product Details Product Category Category Description Source Code Source Description Auto Authorization Auto Authorisation Limit Currency Delete Option Deletion Allowed Amend Fields M Customer Account Counterparty Bank Code Activation Date M Counterparty Account Local Clearing Format an _ Transaction Amount Ganne lt m r Fields Maker Date Time Checker Date Time Mod No Record Status Authorization Status In this screen you can specify the following details Product Details Product Category Select the product category from the list of options available Source Code Select the source code from the list of options available 320 ORACLE Auto Authorization Auto Authorization Limit If you specify an automatic authorization limit transactions belonging to the product category and source combination involving amounts less than or equal to the limit will be automatically authorized on upload Transactions exceeding the limit specified have to be authorized manually after upload The authorization limit is maintained in the local currency of the bank If you do not specify an authorization limit all transactions belonging to the customer source and product category combination will be automatically authorized on upload Deletion Option Deletion Allowed Check this box to indicate that the uploaded trans
14. Once the original Incoming Payment gets re activated the cancellation transaction is retried in Incoming Cancellation Exception Queue screen and the response for the cancellation request is sent to CSM Collections Case 3 Receipt of Camt 056 from Creditor Bank for Incoming Collections for which Pacs 002 is already sent by Debtor Bank When CSM processes Camt 056 for Incoming Collection Debtor Bank processes the incoming Camt 056 When the original Incoming Collection contract is not active cancellation processing on original Incoming Collection fails and the cancellation transaction gets logged into CR queue In order to respond to received Camt 056 message Reject of Incoming Collection is rejected either manually in Payments and Collections Transaction Input PCDONONL screen by the reject operation available or on receipt of Pacs 002 for Pacs 002 from CSM This rejection process would re activate the original Incoming Collection with the contract details as prior to the initial rejection An event RACT is logged for the original Incoming Collection in the contract events data store Once the original Incoming Collection gets re activated the cancellation transaction is retried in Incoming Cancellation Exception Queue screen and the response for the cancellation request is sent to CSM Case 4 Receipt of Pacs 002 from Debtor Bank for Outgoing Collections for which Camt 056 is already sent by Credi
15. The collection status of a transaction depends on the operations that have been performed in respect of it Accordingly a collection transaction could be in any of the following statuses Pending Approved Rejected Closed Recalled Status of a Transaction The status of a payments or collection transaction indicates the processing stage of the contract in the system The following statuses are possible Work in Progress This status indicates that the transaction has been booked manually and no subsequent operation has been performed on the transaction Held This status indicates the transaction is on hold typically due to incomplete transaction details and no operation can be performed on the transaction In sucha 3 0 ORACLE 5 9 5 10 case you must amend the transaction enter the missing details and save it again to release it from the Hold status e Uninitiated This status indicates that the transaction has been uploaded into the system and no subsequent operation has been performed on the transaction e Active This status indicates that the transaction has been initiated in the system e Outstanding This status only applicable for outgoing collection transactions indicates that the system has completed all requisite operations that need to be performed from the creditor s bank and that the contract is awaiting approval or rejection from the debtor s bank e Liquidated This status indicates tha
16. Viewing Creditor Direct Debit Agreement History You can view the history of agreement records pertaining to particular Creditor using Creditor Direct Debit Agreement History Summary screen You can invoke this screen by typing 3 105 ORACLE PCSCRAHS in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Creditor Direct Debit Agreement History Summary E gt search Ct Advanced Search Reset Y Clear All Case Sensitive Authorization Status gt Customer Creditor Account Agreement Id Records per page 15 x 10f1 Authorization Status Record Status Product Customer Record Status Branch Debtor Account Creditor Account Debtor Account Agreement Id You can query based on any or all of the following criteria Authorization Status Record Status Customer Branch Creditor Account Bank Code Debtor Account Agreement ID Click Search The system displays the following values Authorization Status Record Status Product Customer Branch Creditor Account Debtor Account Agreement ID Creditor ID Schema ID Version Number 3 106 ORACLE 3 41 3 42 The system displays the records in descending order of the version number Retrieving Debtor Direct Debit Agreement History Oracle FLEXCUBE facilitates retrieval of the history of agreement records pertaining to particular Debtor using Debtor Direct Deb
17. a 008 ORACLE If the Utilized Transactions for Calendar Year is less than the Number of Transactions per Calendar Year then the system processes the incoming collection and Utilized Transactions for Calendar Year are incremented on receipt of the incoming collection transaction If the Utilized Transactions for Calendar Year equals Number of Transactions per Calendar Year then the system moves the incoming collection transaction will to Transaction Repair TR queue Static data for error code PC SVV O9P with description as Number of Transaction per Calendar Year exceeded is available Auto rejection for the above error can be configured and the incoming transaction is rejected automatically Debtor bank originated R transactions such as Pre settlement Reject and Post settlement Reject on incoming collection transactions will decrement the count in Utilized Transactions for Calendar Year field on receipt of the incoming collection transaction Debtor originated R transactions such as Pre settlement Reject and Post settlement Reject on incoming collection transactions will not decrement the count in Utilized Transactions for Calendar Year field All cancellations of incoming collections must decrement the transaction amount in Utilized Transactions for Calendar Year field on receipt of the incoming collection transaction Reversal of incoming collection will not decrement the count in Utilized Tran
18. ee ORACLE 8 2 1 5 8 3 rent business day a warning message indicating the same during End of Transaction EOTI batch process For further details on generic attributes that you can define for liquidation of an LC contract please refer the Liquidation User Manual under Modularity Batch for raising DDs for Tax Relief at Source TRS This process generates a direct debit for Tax Relief at Source TRS rebate availed by customers on mortgage loans It is executed during the End of Day EOD process after the LD batch processes The following details are picked up by the process for raising the direct debit e PC Product Category The product category for DD generation is picked up from the Bank Wide Parameters maintenance e Counterparty Bank Code This is the code of the revenue bank picked up from the specification in the Bank Wide Parameters for which the DD is raised e Counterparty Account Number This is the revenue account number picked up from the specification in the Bank Wide Parameters for which the DD is raised e Counterparty Name This is the TRS Contact Person picked up from the specification in the Bank Wide Parameters where this information is maintained in the user defined fields e Customer Account GL Suspense Account This is the account that would be credited as part of DD Outgoing Collection processing and is picked up from the specification in the Bank Wide Parameters
19. RTGS then while saving the system will check if the Network Qualifier is RTGS If yes then the Network Type will be RTGS If you select the Network Type as Non RTGS and Network Qualifier as NEFT then while saving the system will check if the Network Qualifier is NEFT If yes then the Network Type will be Non RTGS Network Qualifier If the network type is RTGS indicate whether the network is TARGET 2 system To enable the system to perform TARGET 2 specific validations during contract input and message generation select TARGET 2 from the network qualifier option list You can select S for SKN I for RTGS TARGET 2 or Others as the network qualifier The default value is Others Note This field is enabled only if the network type is chosen as RTGS TARGET 2 is a RTGS clearing system for high value Euro payments All the participants in the current National RTGS system automatically become members of TARGET 2 Following are the units of TARGET 2 e Direct TARGET 2 participant e Indirect TARGET 2 participant If payment is done from direct TARGET 2 participant to another direct TARGET 2 the account of the sender will be debited and that of receiver is credited If payments are sent from a direct TARGET 2 participant to a direct TARGET 1 participant an interlinking account is used oe ORACLE Swift Type Select the swift t
20. The field is mandatory Customer Account Currency The field displays customer account currency The value for the field gets populated on selecting Customer Account Restrict All DD Transactions Check this box to reject all Incoming DD transactions for the selected customer Restrict All Future DD Transactions Check this box to reject all Incoming future DD transactions for the selected customer Restriction from Date Select the date from which the future DD transactions to be restricted using the adjoining calendar You need to enter the date only if you have selected the option Restrict All Future DD Transactions Restrict All DD Transactions of Ordering Customer Restriction Type A list of creditors are either allowed or restricted from initiating the collection transactions The restriction types are e Allowed gt Represents the approved White Listed Creditors e Disallowed gt Represents the disapproved Black listed Creditors The parameters that are used to identify the incoming collection transaction and restrict or allow collection from processing are e Creditor ID Scheme ID e Debtor Mandate ID e Creditor IBAN The default value is Disallowed Creditor ID Scheme ID The field is optional and accepts multiple values Specify the Creditor ID for NON SEPA scheme and Creditor Scheme ID for SEPA scheme here ot ORACLE 3 22 1 The value for the field can be specified from a list of values
21. Year Specify the calendar year When calendar is added for a year by default the system will mark all Sundays as holiday with Red color and Saturdays are marked as half day with Orange color and remaining days are marked as Green color that indicates working day Maintaining Purpose Code Purpose code specifies the purpose of the payment based on the agreement between the initiating party and the debtor s bank Purpose code maintained through this maintenance is made available during Payment Transaction Input You can invoke this screen by typing PCDPCDMT in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button ele ORACLE Purpose Code Maintenence H save Populate ISO Codes 1 Of 1 E Purpose Code Description ELGI Date Time Checker Date Time Mod No Record Status Authorization Status Specify the following details Purpose Code For maintaining the purpose code first time click on Populate ISO Codes to view all the factory shipped purpose codes maintained by the system Subsequently you can click Enter Query and Execute Query to view the same You can also add or delete the purpose code by clicking on or button respectively Purpose Code Description The description is auto populated in this field However if a new purpose code has been specified then specify a relevant description in this
22. Authorization Status Contract Status Exception Queue pp pae Detail Exception Reverse Retry Contract Status Account Entry Reference Product Code Customer No Account No Activation Date Local Clearing Account Account Entry Reference In this screen you can maintain the following details e Authorization Status e Exception Queue e Contract Reference Number e Product Category 5 60 Contract Reference Product Code ORACLE 5 19 e Contract Status e Account Entry Reference No e Product code To view the exceptions click Exception button Click Retry button to re process all the contracts Exchange Rate Queues For a payments or collection contract involving a foreign currency customer account the exchange rate required for processing is picked up by the system based on the exchange rate parameters specified for the branch and product combination involved in the transaction If the exchange rate is not picked up or if the exchange rate input process fails the contract is logged into the Exchange Rate Queue In this queue you can manually enter the required exchange rate for the transaction Until the exchange rate is manually entered for a contract logged in the Exchange Rate Queue it cannot be processed Also such a manually entered exchange rate must be authorized to be effective before the End of Day processes are executed for that business day You can access the exchange
23. BOOK and INTERNAL clearings are not permitted Collection Type Specify the collection type of the product category This could be either e DD e RFD Main Tab Payments Product Category Maintenance New EA Enter Query Product Category Product Category Transfer Type Bank Transfer Category Description Collection Type Product Type ET Detail Clearing Fields Offset Category Recall Category Reject Category Approval Category Redispatch Category Reverse Category Book Transfer 10f1 Product Currency Description Offset Reject Recall Approval Redispatch Reverse Network Duplication UDF Details Rule Maker Date Time Mod No Checker Record Status Date Time Authorization Status Once you have maintained these basic details you can proceed to associate products that have been created at your bank with the category For a product category you have to identify products for the following types of processing e Book Transfers e Internal Clearing e External Clearing 288 ORACLE For internal and external clearing you also have to specify the sequence in which the products should be taken up for product resolution An outgoing transfer includes information about the outgoing product category When this transaction is received Oracle FLEXCUBE resolves the product to be used for processing as follows Case One e The outgoing product category maintenance is referred Ifa book t
24. Camt 056 sent by Debtor Bank On receipt of Pacs 002 for an Outgoing Camt 056 the cancellation request for outgoing payments will be marked as Rejected Fields CSM Reject Code CSM Reject Detail and CSM Reject Reference Number for the cancellation request will be populated with the received reject code reject description and reject reference number from Pacs 002 Cancellation requests for the outgoing payments can be initiated again 002 for Reject of Incoming Payments Pacs 004 sent by Creditor Bank Reject of incoming payments are generated when Incoming payment is rejected by processing post settlement rejection REJT event On receipt of Pacs 002 for Reject of Incoming Payments the underlying Reject of Incoming Payment contract will be rejected by processing pre settlement reject RJBS event RJBS event on Reject of Incoming Payment Will mark the contract as rejected and accounting entries if posted will be reversed Will populate new fields CSM Reject Code CSM Reject Detail and CSM Reject Reference Number at contract level with the received reject code reject description and reject reference number from Pacs 002 Will also reactivate the Original Incoming Payment by processing Reactivation Event The reactivation event for the Original Incoming payment will revert the status of the incoming payment prior to post settlement rejection event processing REJT This enables incoming payment to
25. Event Account Debit Credit Amount DRLQ Unsettle GL Debit Transaction Amount DRLQ Intermediary GL Credit Transaction Amount CRLQ Intermediary GL Debit Transaction Amount CRLQ Outgoing Network GL NOSTRO Credit Transaction Amount ORACLE Reverse of Outgoing collections The following entries can be defined for reverse of outgoing collections Event Code Accounting Role Amount Tag Dr Cr DRLQ CUSTOMER TFR_AMT Dr INTSUSREC TFR_AMT Cr CRLQ INTSUSREC TFR_AMT Dr CLGSUSPAY TFR_AMT Cr Reverse of Incoming collections The following entries can be defined for reverse of incoming collections Event Code Accounting Role Amount Tag Dr Cr DRLQ CLGSUSREC TFR_AMT Dr INTSUSPAY TFR_AMT Cr CRLQ INTSUSPAY TFR_AMT Dr CUSTOMER TFR_AMT Cr If the incoming payment is rejected from the incoming authorization queue then system will process CRLQ event and pass the following accounting entries Event Account Debit Credit Amount CRLQ_ Intermediary GL Debit Transaction Amount CRLQ_ Unsettle GL will be picked up Credit Transaction Amount from Product Category If the incoming payment is rejected from the repair queue then system will process CRLQ event and pass the following accounting entries Event Account Debit Credit Amount CRLQ Intermediary GL Debit Transaction Amount CRLQ Suspense GL Credit Transa
26. Outgoing Payment You will need to define the following events while defining an Outgoing Payment product e BOOK e INIT e DRLQ e CRLQ e DCLG e RJBS e REJT e CONS Incoming Payment You will need to define the following events while defining an Incoming Payment product e BOOK e INIT e DRLQ e CRLQ e CONS Outgoing Direct Debit You will need to define the following events while defining an Outgoing Direct Debit product e BOOK e INIT e DRLQ e CRCO e CRLQ e DCLG oe ORACLE e RDSP e APPR e REJT e CLOS e RECL e REVR e CONS Incoming Direct Debit e BOOK e INIT e DRLQ e CRLQ e REJT e RECL e REVR e CONS Reject of Incoming Direct Debit e BOOK e INIT e DRLQ e CRLQ e DCLG e REVR Reject of Outgoing Direct Debit e BOOK e INIT e XREF e DRLQ e CRLQ e REVR Recall of Incoming Direct Debit e BOOK e INIT e DRLQ e CRLQ e DCLG e REVR Recall of Outgoing Direct Debit e BOOK e INIT e XREF e DRLQ os ORACLE CRLQ REVR Outgoing Request for Debit BOOK INIT DCLG RDSP APPR REJT CLOS REVR Incoming Request for Debit BOOK INIT APPR REJT REVR Approval of Incoming Request for Debit Outgoing Payment BOOK INIT DRFX DRCO DRLQ CRLQ DCLG REJT REVR Approval of Outgoing Request for Debit Incoming Payment BOOK INIT XREF DRLQ CRCO CRFX CRLQ REVR Reject of Incoming Request for Debit BOOK INIT XREF DCLG ORACLE 9 2 2 Reject of Outgoing R
27. PC SAV 027 Debit not allowed for customer account PC SAV 028 Customer account is dormant PC SAV 029 Customer account is frozen For more details on maintaining error codes for automatic rejection refer section Maintaining error codes for automatic rejection in Maintaining Information specific to the Payments and Collections Module chapter in this User Manual For more details on events and accounting entries for SEPA transactions refer chapter Annexure A Accounting Entries and Advices in this User Manual Validations done on the SCT and SDD Messages The system performs certain validation on the incoming and outgoing instructions for SCT and SDD Following are some of the validations done by the system e The SCT and SDD transactions should have the debtor and the creditor account should be in the IBAN format e The Counterparty account number should be in IBAN format if the IBAN validation is set as true in the network preferences or IBAN Mandatory flag is set as true in the PC Bank Directory Maintenance This validation is also done for outgoing messages e The customer account should be in IBAN number format if the IBAN validation is set as true in the network preferences or IBAN Mandatory flag is set as true in the Customer Account maintenance System will display an override if the IBAN is not maintained for the customer account This validation is also done for outgoing messages e The
28. Products can be categorized into groups based on the common elements that they share You must associate a product with a group This would facilitate retrieval of information of a class of products at one stroke For example you can group all products involving travelers checks into a product group You can group all products involving loans into a product group 2 ORACLE 4 2 1 Start Date and End Date A product can be defined to be active over a specific period When you create a product you can specify a Start Date and End Date for it The product can only be used within the specified period i e within the Start Date and End Date If you do not specify the Start Date the branch date will be displayed as the Start Date If you do not specify an End Date for a product it can be used for an indefinite period The start and end dates of a product come in handy when you are defining a product that you would like to offer over a specific period Remarks Enter the free hand remarks regarding the products Exchange Rate Variance in You can define the exchange rate variance that you would like to allow for a PC product This variance is expressed in terms of a percentage For a special customer or in special cases you may want to use an exchange rate a special rate that is greater than the exchange rate maintained for a currency pair The variance is referred to as the Exchange Rate Variance When
29. TR queue is corrected by re processing original contract with Unsettle GL Once the original Incoming Payment contract is cleared from TR queue cancellation transaction is retried in Incoming Cancellation Exception Queue screen and the response for the cancellation request is sent to CSM Handling of Camt 056 for Incoming Collections in Transaction Repair queue Manual approval of cancellation of Incoming Collections You can approve the cancellation request received for Incoming Collection transactions that are not auto approved or failed during auto approval using the screen Incoming Payments and Collections Cancel Approval Approval process on Incoming Camt 056 on Incoming Collection will fail since the original Incoming Collection is in TR queue Cancellation transaction would be logged into CR queue An information message is displayed logged that describes that the cancellation transaction would be logged into CR queue In order to process received Camt 056 message Original Incoming Collection contract in TR queue is corrected by re processing original contract after correcting the error cause Once the original Incoming Collection contract is cleared from TR queue cancellation transaction is retried in Incoming Cancellation Exception Queue screen Handling Conflict Scenarios Payments Case 1 Receipt of Pacs 004 from Creditor Bank for Outgoing Payments for which Camt 056 is already sent by
30. The list of values fetches the creditor ID s from Payments and Collections Creditor Details Maintenance If the value is not available in the list of values During save of instructions Oracle FLEXCUBE maintains a record for the entered Creditor ID in Payments and Collections Creditor Details Maintenance with Creditor IBAN Mandate ID Specify Creditor s agreement Id of a selected customer from the list of values If the value is not available in the list then enter the value in the field All the attributes Creditor ID Scheme ID Creditor IBAN and Mandate ID are maintained If Mandate ID is entered then it is mandatory to input Creditor ID Scheme ID for a record Creditor IBAN Specify international bank account number of creditor here the field is optional and accepts multiple values Document Ref No Select the document Reference Number Suffix Specify the suffix Reference Specify the reference identification Processing of Incoming Collection Transaction for a Mandate Following are the fields that are inserted updated with the mandate data during processing of Incoming Collection SI No Field in PC Debtor DD Value Agreement 1 Product PC Product 2 Customer Customer No of account 3 Customer Account Customer Account of Debtor IBAN 4 Creditor Scheme ID Creditor Scheme Identification 5 Agreement ID Mandate Identifica tion 6 Bank Code Creditor Agent 7 Name Credi
31. button in the Payments amp Collections Transaction Input and invoke this screen a ORACLE 6 2 When you enter a payments collection contract you can e View the details of charges computed for each set of conditions maintained for the product e Alter the computed charge amount The system will consider the transaction currency for charge computation e Waive the charge altogether if waivers are allowed in the Product Preferences PcCharge Contract Reference Charge Details 1 Charge Currency Charge Amount Waive Charge Details 2 Charge Currency Charge Amount Waive Charge Details 3 Charge Currency Charge Amount Waive Charge Details 4 Charge Currency Charge Amount Waive Charge Details 5 Charge Currency Charge Amount Waive Account Currency Account Branch Account Number Account Currency Account Branch Account Number Account Currency Account Branch Account Number Account Currency Account Branch Account Number Account Currency Account Branch Account Number The details of the charges computed for each condition set are displayed and you can make your changes or waive the charge if necessary If you make any changes to the charge amount or waive it an override is sought when you attempt to save the contract Building Charge Rules In Oracle FLEXCUBE you can define charges for different types of payment collection transactions which
32. default the Bank Code and the Clearing Network as ALL e ALL If you choose this the system will generate XML files for all customers Choose the appropriate one Service Identifier Specify the service type as of the clearing network The drop down list displays the following details e SCT e SDD Choose the appropriate one Clearing Network Specify the clearing network for which the dispatch file parameters are maintained The option list displays all valid clearing networks maintained in the system Choose the appropriate one Bank Code Specify the direct or the indirect participant bank code for which the dispatch file parameters are maintained Customer Number Specify the customer number for whom the file parameters are maintained Test Mode Specify the test or production mode for the clearing network If you have chosen dispatch type as Network you must specify the test mode File Format Type Specify the format of the file The supported file format is XML File Path Specify the path to locate the file Bulk Message Check this option to indicate that the message bulk should be created with many transactions Maximum No of Files Specify the maximum number of files that can be sent to the clearing network in one settlement cycle Maximum No of Message Bulks Specify the maximum number of message bulks in a file Maximum No of Transaction Specify the maximum number of transactions that can
33. then the agreement status will be changed back from Final to Active However if a Used collection is rejected cancelled returned reversed i e any R transaction on an OOFF collection then the agreement status will not be changed back to Active but remain as Used For Outgoing Collection transactions there will be a check for the existence of Creditor Mandate for the B2B scheme if DD Agreement Required is checked at customer agreement level If the creditor mandate for the B2B scheme is not found the outgoing collection will not be saved 42 ORACLE 3 22 Effective Date Specify the date from which the agreement is valid or invalid e The effective date from which the debtor agreement becomes valid Note At the Customer Agreement level you can choose the Agreement ID Counterparty Bank and or the Counterparty Account fields to validate the DD agreement details Maintaining Debtor Direct Debit Instructions You can maintain details of debtor direct debt instructions in Debtor Direct Debit Instructions screen You can invoke this screen by typing PCDIDRES in the field at the top right corner of the Application tool bar and click on the adjoining arrow button Debtor Direct Debit Instructions H save Customer ID fas E Restrict All DD Transactions Ginman of a debiting customer ro Restrict All Future DD Customer Account No ae Transactions of a debiting Customer Accou
34. 09D is configured and the incoming collection transaction is rejected automatically when transaction amount exceeds Maximum Amount per Transaction If Maximum Amount per Transaction is not maintained then the system considers Maximum Transaction Amount maintained at Payments amp Collections Debtor Preferences Maintenance If Maximum Transaction Amount is not maintained at Payments amp Collections Debtor Preferences Maintenance then the system considers Maximum Transaction Amount maintained at PC product definition 5 33 Restricting Maximum Amount per Calendar Year Each incoming collection transaction is validated against the Utilized Amount for Calendar Year with Maximum Amount per Calendar Year for a particular mandate Currency is converted when the incoming collection transaction s currency is different from debtor account s currency 37103 ORACLE e Ifthe Utilized Amount for Calendar Year is less than the Maximum Amount per Calendar Year then the system processes the incoming collection and the Utilized Amount for Calendar Year gets incremented on receiving the incoming collection transaction e If the incoming collection transaction amount and the Utilized Amount for Calendar Year are greater than the Maximum Amount per Calendar Year then the system moves the incoming collection transaction to Transaction Repair TR queue e Static data for error code PC S
35. 5 21 The Batch Browser The Batch Browser lists all open batches in the system for collection transactions You can close or re assign batches that you opened You can invoke this screen by typing PCSROWSE in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button S4 Advanced Search 5 Reset Branch zE Batch Number Batch Description az Authorisation Status Blocked az Maker Id Checker Id Records per page 15 First Previous 4 of 4 Next Last Batch Description Authorisation Status Blocked Maker Id Checker Id For each batch the following are displayed e Branch e Batch Description e Blocked e Checker Identification e Batch Number e Authorize Status Iba ORACLE 5 22 5 23 e Maker Identification Updating Cut Off Time Status During the end of day run for a branch the system resets cut off time for all products to the time mentioned in the respective product definitions You can use the Cutoff Time Update screen to update the cut off time for a collection product at a branch This update can be made applicable only for a specific branch product combination or can be propagated across all branches for the same product The screen displays all products active at the branch The cut off times for each product can be changed here if desired You can also invoke this screen
36. Account Number of Creditor from the adjoining list of values displaying IBAN number If the number is not available in the list and then insert the number in the field Direct debit Reference No Specify the direct debit reference number Maximum Amount per Transaction Specify maximum transaction amount allowed per incoming collection in this field The amount is in Debtor s customer account s currency The default value is null ORACLE Maximum Amount per Calendar Year Specify maximum sum of incoming collection transactions allowed against particular mandate per calendar year as a value for the field Maximum value for this field is 999999999999999 99 The amount is in Debtor s customer account s currency The field is optional and has a default value as null Utilized Amount for Calendar Year The field displays sum of successful incoming collection transactions amount against particular mandate at any point of the time within a calendar year Number of Transactions per Calendar Year Specify maximum number of incoming collection transactions allowed against particular mandate per calendar year Maximum value for this field is 999 The field is optional and has a default value as null Utilized Transactions for Calendar Year The field displays number of successful incoming collection transactions against particular mandate at any point of the time within a calendar year Address 1 2 3 and 4 Specify the counterparty add
37. Approval Category Select the approval category from the option list The corresponding description is displayed Approval categories are required to approve RFD collections For incoming collections RFD outgoing payment is the approval category Similarly for outgoing collections RFD incoming payments are the approval categories Redispatch Category For collection transactions for this product category that are redispatched the redispatch product category needs to be specified Redispatch is applicable to outgoing collections only aop ORACLE 3 26 2 Reverse Category For Outgoing collections product category you can specify the reverse product category from the option list Detail Tab Payments Product Category Maintenance H save Product Category Sm Product Category Transfer Type Bank Transfer oa Category Description Q Collection Type Product Type Main Detail Clearing Fields Counterparty Name Maximum Length 35 iv Mandatory Maximum Length 35 Character Set X Default Customer Account Unsettle AC Type Automatic User Reference Generation Default Account Type v Unsettle AC Type X F Auto Custom Reference Account Branch Currency Customer Reference Account Number a Branch Sequence Code Currency Account No a Rekey Dupli
38. BOOK Transaction Booking This event signifies the transaction s entry into the system INIT Transaction Initiation Involves Product Resolution Default of Product Parameters Dates Resolution BOOK and INIT are automatic events for transac tions uploaded from Electronic Banking Auto authorization is done for uploaded contracts if the amount is within the limit defined for the upload source product category For the manual input transactions BOOK is done on SAVE and INIT is automatic INIT can also be done manually DRFX Exchange Rate Popula The events DRFX occur before the customer leg of tion Outgoing Only accounting provided the customer leg is the debit Payments leg The system triggers these events automatically if the amount is within the limit specified for the cus tomer Agreement Product Currency Else you will have to trigger them manually DRLQ Debit Entry Liquidation The system triggers the event automatically and initiates the debit entry either to the customer account or to the clearing suspense account based on the type of transaction DRCO Debit Entry Consolida For debit transactions to the customer account that tion require consolidation this event is automatically triggered CRCO_ Credit Entry Consolida This event is triggered automatically for all credit tion transactions to the customer account that require consolidation CRFX Exchange Rate Popula The events CR
39. Calendar Year 5 106 Levying Charges on Payments and Collections Transactions 6 1 CI INthOGUCtOM 2 21 4 asec eaa r T T Baccara ater bedi te 6 1 6 1 1 Charge Specifications for a Payment Collection Product ccccececee 6 1 6 1 2 Specifying Charge COMPONENUS 0 0 2 eccceccee tee eeeentneeeeeeensaeeeeeeenaeeeeneeaaes 6 3 oy re MSY 0121011 57 1010 Bk Chagas re 6 3 6 2 Building Charge RUES eioen at n aA E E RAT 6 4 6 2 1 Specifying Parameters for Charge Rule Application ccccccseeeeentes 6 6 6 3 Defining the Charge Account Maintenance seeseeseeesrisseeerrrsserrrrsssttrrsssrrerrsseen 6 6 6 4 Defining Charge Product Categories 0 eecccceecceeceeeeeeeeneeeeeeeeeeeeeeeeeeaaeeeeseenaaeees 6 8 Outgoing Payments Workflow cccccccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees 7 1 Ged CWAPOGUCHION a sace ds disesccid buiseceds a de tadagedaedatudters aa 7 1 7 1 1 Enabling the Outgoing Payments Workflow eesssssseeeeseseeeennnnesiennnneeeennne 7 2 7 1 2 Viewing Message Status of a Contract sesessisseesiennneeernnnreernnnnneennnnee 7 2 Payments and Collections Operations and Processes ss cc 8 1 Sel ImtrOGUCtOn a a a E AET 8 1 8 2 Batch Process for the Payments and Collections Module eeeeeeeeeeneeee 8 1 8 2 1 Periodic Instructions uu iciccicecceccccccceeccccceeccseneeceeuecseceeessesaeeeesseeseueeeseneeeesnnsss 8 2 10 11 8 3 Background Processes marere ape
40. Clear All Case Sensitive Transaction Reference Branch Code Account Number 7 Email Id Telephone J Facebook ID Status x Records per page 15 z 10f1 Transaction Reference Branch Code Account Number Emailld Telephone Facebook ID Status End date In the above screen you can base your queries on any or all of the following parameters and fetch records e Transaction Reference e Account Number e Telephone e Status e Branch Code e Email Id e Facebook ID Select any or all of the above parameters for a query and click Search button The system displays the following details pertaining to the fetched records e Transaction Reference e Branch Code e Account Number e Email ID e Telephone e Facebook Id 3 24 ORACLE 3 16 e Status e End Date Maintaining Upload Sources You can identify the sources from which you would like to receive payment and collection transactions for processing The transactions are uploaded from these sources into Oracle FLEXCUBE You can identify a source in the PC Upload Sources screen and invoke the Upload Sources screen by typing PCDUPLDWM in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Upload Sources Maintenance E new amp Enter Query Source Code Description Fields Maker Date Time Checker Date Time Mod No Record Status Authorization Status In thi
41. Count e Customer Account Branch e Consol Account Reference Number e Product Type All contracts that are rejected during the accounting of a file consolidated entry forms part of a Consolidation Exception Queue The file level consolidation batches falling under this exception queue has the product code value as Null The consolidation exception queue has the following options e Accept Select the option to accept the transaction so that it can be processed even without adequate funds in the customer account by providing an overdraft to the customer e Retry Select this option if the funds have been credited to customer account subsequent to the credit exception a retry will result in successfully processing of debiting the consolidating amount e Carry forward This option forwards the consolidation processing to the next working day The consol batch will be marked for pickup on the next working day e Reject This option is to manually confirm the rejection 5 15 Viewing Transaction History Summary You can view all the transaction history using Transaction History Query screen You can invoke this screen by typing PCSCONHS in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Transaction History Query amp Search t Advanced Search 9 Reset Case Sensitive
42. Currency Calendar Maomum Transaction Days Amount Network Calendar Counterparty Entry Product Code Specify the product code for which you want to maintain the preferences Transfer Type Select the type of transfer The options are e Customer Transfer e Bank Transfer e Internal Transfer Type You can indicate the types of transfers that can be processed using the product bank transfers or customer transfers This specification is defaulted from the product category to which the product is linked Only bank transfer types of products can be mapped to product categories defined for bank transfers Book transfer products cannot be mapped to product categories defined for bank transfers Similarly only customer transfer types of outgoing payment products can be mapped to product categories defined for customer transfers This specification is only applicable for outgoing payment product types with external or internal Clearing Modes Bank transfer is allowed for outgoing payment type of products only EXTERNAL clearing is permitted for such products However BOOK and INTERNAL clearings are not permitted i ORACLE Product Type Incoming and Reject of outgoing payment product types e Collection Type e RFD Type e Max Interest Amount e Max Split Count e Invoice Split Required e Collection Stmt Required e Account details for rejection before response days e Account details for rejection after response days e
43. Customer Scheme Name Type Select the Identification Scheme Type of the Customer from the drop down list The valid field can be one ORACLE 3 28 e C Code e P Proprietary Customer Scheme Name Specify the value for Identification Scheme Name field If Scheme Name type is C then the Scheme Name can be selected from LOV and can have one of the values mentioned in value list depending on Organization Identification or Private Identification If the Scheme Name Type is P then you can enter the value for the field Customer Date of Birth Specify the date of birth of the Customer Counter Party BIC ID Specify the Bank Identification Code for the Counter Party Counter Party Scheme Name Type Select the Identification Scheme Type of the Counter Party from the drop down list The valid field can be e C Code e P Proprietary Counter Party Scheme Name Specify the value for Identification Scheme Name field If Scheme Name type is C then the Scheme Name can be selected from LOV and can have one of the values mentioned in value list depending on Organization Identification or Private Identification If the Scheme Name Type is P then you can enter the value for the field Counter Party Date of Birth Specify the date of birth of the Counter Party Defining User Defined Fields for Account Statements The User Defined Fields Maintenance screen in the Payments and Collections module allows you to define fields th
44. Details intermediary Reimbursement Institution Intermediary kal kzl 2 iv lad o o 2 El Country azl i Country fel Intermediary F Rtgs Payment ba Fields Change Log Da od No Da ord If you indicate payment over a clearing network you must also specify the account details of the external counterparties both pay and receive accounts in the Local Clearing tab change name in the Settlement Instructions screen Settlement Instructions Maintenance X H save Counterparty kal Module fal Counterparty Name Product Code bl Counterparty CIF Sequence Number 0 Currency GBP asl Relations Branch 000 bel Pay Receive E Ci r ee ee bal bal Covery Currency GBP P Currency GBP m Charges Deis Ourselves Account fel Account el Beneficiary Description Description Shared Payment By Tx PaymentBy Ts Pay Parties Pay Parties Receiver Parties Cover Parties EESg Eeg Cover Details Other Details External Counterparty Pay Details External Counterparty Receive details Bank Code cal Bank Code bal Account Account Name Name Clearing Network fae Bank Name Bank Name Fields Change Log Maker Date Time Mod No Checker Date Time Record Status Authorization Status For the counterparty details you can specify Bank Code Select the bank code from the list of options available Account Specify the account here 3100 ORACLE Name Specify the
45. If it is not found then it will display an error PC SVV O9L and saves the transaction Local Instrument Value The value for the field is defaulted from the collection scheme type field maintained at product level You can modify this value The field is enabled if the product type is Outgoing Collection e The Local Instrument Value defaulted or entered for the transaction should be same as the Collection Scheme Type of the outgoing collection Product Validation would be added for the same e Static data for error code PC SVV 09N would be available and used when Local Instrument Value and Collection Scheme Type doesn t matches e If Local Instrument Value is not specified for outgoing collection the collection scheme type specified at the product would be defaulted with Local Instrument Type as Code e If Collection Scheme Type is not maintained at product level then system will not validate on Local Instrument Value and Local Instrument Type e Validation will be done such that for the Collection Scheme type B2B the selected customer should not be of type Individual e During processing if Local Instrument Value is B2B and if Creditor s account is individual customer s account then system will raise an error PC SVV 09M e Incase the creditor account is Joint account then the customer type of the main customer only will be checked Customer types of the joint customers will not be check
46. Information 1 2 3 and 4 If you need to specify other information regarding the customer of the transaction free format 35 character text fields are provided with appropriate labels applicable for your installation You can specify the customer information in these fields Customer Reference Specify the reference number to identify a customer Source Code System displays the source code when you provide the customer reference and information Station Identification System displays the identification number of the station when you specify the customer information and reference numbers Creditor Identification Specify the identification number of the creditor Agreement Identification Specify the identification number to identify an agreement 780 ORACLE 3 34 1 Customer Address Address Line 1 2 3 4and 5 Specify the address of a customer in the lines 1 2 3 4 and 5 Customer Identification details Identification Select the option to identify the customer either by Organization details or by Individual person details The options available in the drop down list are Organization and Private Identification Value Specify the identification value for the Customer for the given identification type This is mandatory only if the Identification type is specified Issuer Specify the issuer of the customer This is used to identify if the Organization identification is used as Proprietary Identification or Pri
47. Name can be selected from LOV and can have one of the values mentioned in value list depending on Organization Identification or Private Identification If the Scheme Name Type is P then you can enter the value for the field Customer Identification details You need to specify customer identification details of the customer of the transaction free format 35 character text fields are provided with appropriate labels applicable for your installation You can specify the following details e Identification e e Identification Value e Country e Issuer e City Of Birth e Country of birth Counter party Details The Bank Code Name and City details are displayed on the Transaction Input screen when you select the bank code Account Number You can specify the account of the counterparty here In case of internal transfers the account needs to be a valid account of Oracle FLEXCUBE either in Oracle FLEXCUBE or in the Local Clearing Format You can also select an account number from the option list provided In such a case the system will default the counterparty name and the address lines as maintained for that account If at the time of selection of counterparty account Bank Code is null then Bank Code and Name will also get defaulted Counter party Name Specify the nameof the customer counter party You can click Learning Database button to invoke the learning database to specify the counter party details All co
48. ORACLE 11 Function ID Glossary c PCDMSGMA cscscccsssees 3 92 CFDCHGCE fja 6 6 PCDNKTYP eee 3 2 CORPRSAL sssagedacctaeiiss 10 2 PCDNWHOL 2e eee 3 13 CORUNPSL aa 10 4 PCDONONL osise 5 2 CSSJOBBR onnsa 8 6 PCDPCDMT seeeeeee 3 13 PCDPDOTG essccsssscesssseee 3 57 E PCDPRCAT eessccsssstecssoeee 3 78 EIDMANPE ccssscccssseeceoees 8 1 PCDPRDAT ssscsssscecosseees 3 15 P PCDPRMNT ccsssccecseeeeoees 4 1 PCDPROCH scccssssesssteeseee 6 8 FTSCONON resets 5 40 PCDPTPBN ossis 3 19 PCDPTPPM oninia 3 22 PCDPTYDM essscsssseesosseees 3 68 ISDINSTN occcscsssscecssseeeessees 3 99 SCOBElNicces aie M PCDRCLOT esssccsssscecenseee 5 77 MSDPRMAP sssssesseeeee0 3 91 PCDRICOD eerie 3 74 MSSBLKBR ssessssesessesteee 5 95 PE DRF ERNI biisiin 3 87 5 90 PCDTRFSH csssscsssseecssseees 5 52 P PCDUDMNT seiiscaistastosstcedts 3 70 PCDACARE ooeesscsssecssseeee 3 16 PCDUPLDM cccsscessssees 3 25 PCDACSMT eescssseccsssteeee 3 72 PCDUPLDT ssscsssseecssseees 3 26 PCDBENMT cscscccsseeeee 3 17 PCDUTOPFP ssscsssssesssseees 5 64 PCDBKRED cssssccsssseeee 3 11 PCSAUTQI ooecesssecsssseesensees 4 31 PCDBNKMT cssscccssseees 3 3 3 POSAUTO scessiteicnnshcccace 4 32 PCDCHACM essscssseccssseseoees 6 7 PCSBERGQ o escccseesseecee 3 24 PCDCLAGT o eessccssssccssteeee 3 28 PCSCNLEX ccesscccsseessteeeos 5 55 PCDCLNTQ o essccssseecssseeee 3 1
49. PC Module Before you proceed with operations in the Payments and Collections module you must maintain the following information e Local Bank Directory e Clearing Networks e Bank Redirection details e Account Redirection details e Upload Sources e Upload Source Parameters e Products e Client Agreements after product maintenance e Customer Station details e Details of Creditors e Product Category after product maintenance e Account Statement Fields e User Defined Fields UDF and User Defined LOVs e Reject Codes l ORACLE 3 3 e Debtor Customer Categories e Charge Product Categories e Charge Account Mappings e Cover requirement You can maintain this information in screens that are invoked from the Application Browser The subsequent sections of this chapter talk about each of the above mentioned maintenances in detail Maintaining Bank Code Types You can maintain the different types of bank codes that you intend to maintain for banks in the System through the Bank Code Type Maintenance screen This maintenance is required to distinguish between the types of bank codes You can invoke the Bank Code Type screen by typing PCDNKTYP in the field at the top right corner of the Application tool bar and click the adjoining arrow button Bank Code Type Maintenance E New Enter Query Bank Code Type Bank Code Type Description ELCs Date Time Checker Date Time Mod No Rec
50. RCUR would be and no processed amendment details No mandate Incoming No Change Used Collection would be Final rejected Cancelled 3 49 ORACLE Existing New SI No Transaction Mandate Action mandate Status Status 4 Incoming Old man Incoming No Change pacs 003 date details Collection with RCUR status Can would be and amend celled rejected ment details present Mandate Existing Used Status is Mandate sta active tus would be updated New Man Active date details would be inserted 5 Incoming Active Mandate Final pacs 003 Status would with FNAL be updated No mandate Incoming No change Used Collection would be Final rejected Cancelled 3 23 Maintaining Mandate Cancellation Charge Details In Oracle FLEXCUBE you can capture the details related to handling of charges for the mandate cancellation in the Mandate Cancellation Charges Maintenance screen You can invoke this screen by typing PCDMNDCN in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Mandate Cancellation Charges Maintenance ee H save Source Code Branch Code Source Code ae Branch Code el Charges Customer Detail Income GL fal Customer No Gal Transaction Code az Account No laz Charge Currency laz Charge Amount Maker Date Time Checker Date Time Mod No Record Status Authorization Status d ORACLE
51. Reference Number The system displays the recall file reference number Status The system displays the status of the recall request Note When you generate the recall request Camt 056 message for the contract then the system displays the details with status as Sent When you receive the negative response to the recall request Camt 029 message then the system displays the status as Failed If the network is SEPA then for Local Instrument Type CODE the Local Instrument Value should be CORE COR or B2B for outgoing collection If Local Instrument Value is not entered as COR B2B for outgoing collection contract then system displays an error message as Invalid Local Instrument Value value should be either CORE B2B When the system generates Camt 056 message then the system displays the recall details in the Message Details tab The system changes the recall message status to Rejected if the Camt 056 message is either rejected by SEPA or Camt 029 message is received On receipt of Pac 004 system reverses the original contract The system does not change the recall message status to any other status as it remains Sent Incoming Message Details Specify the following incoming message details File Reference Specify the reference number of the file that is used in the incoming message processing Message ID Specify the mode to identify a message Message Name Specify the name of the message
52. Rejected Queue e Exchange Rate Queue e Unexpressed Transactions e Rejected Transactions e Deleted Transactions e Authorized Transactions e Transaction Reinput Queue e Credit Exception Queue 8 5 Source fc ENEA Reversed Transactions Deleted Transactions Unaut ORACLE 8 5 You can trigger a background process using the Jobs Browser screen You can invoke this screen by typing CSSJOBBR in the field at the top right corner of the Application tool bar and click on the adjoining arrow button C Advanced Search 9 Reset Job Module f Process Status g Records perpage 15 v First Previous 4 op 4 Net Last a Job Module ocess Process Sequence Number Start Stop Status N Here you can query on jobs based on the following criteria Job Module Choose the appropriate one from the adjoining drop down list Process Specify the process for which you wish to run a job Status Indicate the status of the process Click Search button All jobs and processes satisfying the specified criteria will be displayed along with their status and sequence numbers Check the box adjoining the desired job and then click Start button to run the job s The Online Mode When the volume of transactions being processed is not inordinately high the system can be configured to run in an online mode wherein all
53. SEPA Payment Cancellation Approval Summary screen You can invoke this screen by typing oes ORACLE PCSRCLOT in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Summary incoming Payment Cancel Approval E gt search C Advanced Search 4 Reset KY Clear All Case Sensitive orization Status 7 Record Status v Recall Reference Number Contract Reference Approve Reject H Reject Code Account No Counterparty Account Number Customer No Records per page 15 7 10f1 Authorization Status Record Status Recall Reference Number Contract Reference Approve Reject Reject Code Ink In this screen you can query based on any combination of the following fields e Authorization Status e Recall Reference Number e Approve Reject e Account Number e Customer Number e Record Status e Contract Reference Number e Reject Code e Cpty Account Number After specifying the parameters for the query click Search The system displays all the records matching the parameters specified 5 25 5 Processing Negative Answer to Recall of a Credit Transfer Camt 029 001 03 The receiver bank sends the Camt 056 message to recall already sent Pacs 008 Pacs 003 If the receiver bank is unable to process the Camt 056 then the receiver bank sends the Camt 029 001 03 message to STEP2 in case of Payment Cancellation You can generate the Camt 029 001 03 for all incoming Cam
54. Tax screen The role to head mapping of PC product maintenance will provide a GL account details to liquidate the tax Tax Details Product Code Product Description Scheme Details Tax Scheme Default Scheme Description Tax Details 1 Of 1 Tax Rule TaxComponent Basis Component Event Tax Type You can specify the following details Product Code The system displays the product code Product Description The system displays the description for the specified product code Scheme Details Tax Scheme Specify the tax scheme details You can also select the valid tax scheme from the adjoining option list Description The system displays the description for the selected tax scheme Tax Details Tax Rule The system displays the tax rule Tax Component The system display the tax component Basis Component Specify the basis component You can also select the valid component from the adjoining option list Event Specify the event details aran ORACLE 4 3 Tax Type Select the tax type from the drop down list Following are the options available in the drop down list e Withholding Tax For further details on Customer FATCA maintenance please refer Customer FATCA Classification in Core User Manual Viewing Level 1 Authorization A1 Details You can view the Level 1 Authorization A1 details using the Payments amp Collections Auth1 Queue screen To invoke
55. The lower half shows contracts grouped by the consolidation parameters All options provided on the main screen are provided on this screen as well You can opt to process all the contracts or select contracts e Reject Choosing this option allows you to reject contracts If a contract is rejected the contract status is updated as rejected No further processing of such transactions is allowed Click Reject to reject a transaction The Reject Contract Details screen is opened You must specify the Activation Date for the rejection and indicate whether the reject must be dispatched You must also specify the reason for rejection by selecting the appropriate reject code e Choose Carry Forward option if you would like to forward the activation date to the next working day The contract will be marked for pickup on the next working day e Retry This option marks the contracts for reprocessing If funds have been credited to the customer account subsequent to the credit exception a retry would result in the successful processing of the contract Click Retry to retry a transaction e Accept Choose this option if the contract can be processed even without adequate funds in the customer account This typically means you are providing an overdraft to S89 ORACLE 5 13 the customer If you specify a limit amount transactions grossing the limit amount would be allowed for processing However if you d
56. actual amount transferred during the transaction For example if the you have maintained the Charge Mode as Discount at the Product Preference level then the actual amount sent to the beneficiary will be the difference between transaction amount and charge On saving the transaction after entering all the required details in the system the system validates the value of the transaction amount against the following e Product transaction limit e User Input limit If the transaction currency and the limit currency are different then the system converts the amount financed to limit currency and checks if the same is in excess of the product transaction limit and user input limit If this holds true the system indicates the same with below override error messages e Number of levels required for authorizing the transaction Transaction amount is in excess of the input limit of the user Foreign Currency Amount The system displays the foreign currency which is involved in the PC transaction Remitted Amount The system displays the remitted amount that is involved in the PC transaction LCY Equivalent The system displays the transaction amount in the local currency Charge Amount You can specify the charge amount in this field This specification will override the charge amount computed for the first charge condition set applicable for the transaction To view the charges for the other condition sets specified for the product c
57. an override message is displayed However if the rate variance is more than the maximum limit maintained for the product an error message is displayed You have to specify a rate that is within the variance limits specified for the product If the contract amount exceeds the Auto Exchange Rate limit defined for the remitter account an override is displayed If you have specified an appropriate rate for the contract you can save your specification by clicking on the SAVE button Any manual exchange rate input requires an authorization Once the exchange rate is authorized the contract is moved from the Exchange Rate Queue to the normal processing queue for further processing Authorizing the Input of Exchange Rates All contracts for which the exchange rate has been input manually need to be authorized before the end of day The date and time and the User ID of the person authorizing the contract will be recorded for audit purposes Note that the person who entered the exchange rate for a contract cannot authorize it oat ORACLE 5 11 5 12 When you invoke the authorization function from the Application Browser you will be prompted to specify a product category If you enter a valid code the authorization screen is displayed To begin the authorization process click on the AUTH button You will be prompted to specify a valid Batch Number A User ID or Reference number is then displayed If re key of exchange rate i
58. as per the product currency calendar if the Currency Calendar option is checked or else it is considered as per the local branch calendar The payment reject days is added to the activation date of an incoming payment to arrive at the payment rejection date Earliest Collection Receipt Days You can specify the number of calendar days to arrive at the earliest date by which the incoming collection transaction should be received by the debtor bank The no of days that you specify here will be subtracted by the activation date or the due date to arrive at the earliest collection receipt days System will display an override if it receives an incoming collection with activation date greater than the earliest collection receipt days maintained Note This is applicable only for incoming collection type of products Earliest Collection Receipt Days is configured as 14 and Calendar Basis as Currency Calendar for Outgoing Collection type and Incoming Collection type of COR1 and B2B scheme Existing timeline check for Earliest First and Recurrent collections on Incoming col lection transactions will be extended to check for Outgoing Collection transactions as well Calendar Basis Specify the value for the field from the adjoining drop down list to derive the time window for the earliest collection for CORE COR1 and B2B schemes The field is enabled and mandatory if Earliest collection Receipt Days fi
59. batch process refer the AEOD user manual aaa ORACLE Note The parameter MANDATE AUTO CANCEL MONTHS has the configurable value of 36 and is factory shipped 3 19 Maintaining Creditors You can maintain the creditor identification like the Creditor ID and description for creditors with whom your bank transacts These details are maintained in the Payments and Collections Creditor ID Maintenance screen You can invoke this screen by typing PCDCREID in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Payments amp Collections Creditor ID Maintenance H save Creditor ID Scheme ID Description Creditor IBAN Creditors Name Address 1 Address 2 Address 3 Address 4 Country Date Time Date Time Record Status Authorization Status Creditor Id Scheme ID Specify the Creditor Scheme ID for SEPA scheme and Creditor ID for Non SEPA scheme For SEPA scheme the value for Creditor ID Scheme ID can be provided as below e Positions 1 and 2 contain the ISO country code e Position 3 and 4 contain the check digits e Positions 5 to 7 contain the creditor business code When the creditor business code is not used then value is set to ZZZ The creditor business code is not considered while checking for existence of the agreement Description Enter a description for the creditor id that you have entered Creditor IBAN Speci
60. be bulked in a message bulk 38 ORACLE File Per Transaction Type Check this option to create dispatch files with message bulks of each of the transaction types If you do not check this option the file is created with the following transaction types in the same order e SCT Credit Transfer Pacs 008 Payment Cancellation Request Recall Camt 056 Returns Positive Answer to Recall Pacs 004 Resolution of Investigation Negative Answer to Recall Camt 029 e SDD Direct Debit Instructions pacs 008 Rejects pacs 002 Reversals pacs 007 Return Refunds pacs 004 If this option is selected then the one file is created for each transaction type You can view a summary of dispatch file parameters using Dispatch File Parameters Summary PCSSFPRM screen Dispatch File Parameters Summary Qq Advanced Search Reset Authorization Status Record Status Dispatch Type Service Identification TestMode v File Path File FormatType gt Files No Of Transactions In Bulk Message Bulks Network Code Records per page 15 v 10f1 Authorization Status Record Status Dispatch Type Service Identification TestMode FilePath File Format Type q The parameters given above are STEP2 clearing system specific to handle SEPA Credit Transfers and SEPA Direct Debits Files sent to STEP2 clearing system follow the naming conventions given below 1 File Naming Conv
61. be rejected further 002 for Positive Response to Cancellation Requests Pacs 004 sent by Creditor Bank Reject of incoming payments are generated when cancellation request for Incoming Payment is accepted and thereby processing post settlement rejection REJT event On receipt of Pacs 002 for positive response the underlying Reject of Incoming Payment contract will be rejected by processing pre settlement reject RUBS event RJBS event on Reject of Incoming Payment Will mark the contract as rejected and accounting entries if posted will be reversed Will populate new fields CSM Reject Code CSM Reject Detail and CSM Reject Reference Number at contract level with the received reject code reject description and reject reference number from Pacs 002 Will also reactivate the Original Incoming Payment by processing Reactivation Event Will enable cancellation request as active and the cancellation request can be further accepted a8 ORACLE Pacs The reactivation event for the Original Incoming Payment will revert the status of the Incoming Payment prior to post settlement rejection event processing REJT 002 for Negative Response to Cancellation Requests Camt 029 sent by Creditor Bank On receipt of Pacs 002 for Negative Response Camt 029 Cancellation Request will be nullified Fields CSM Reject Code CSM Reject Detail and CSM Reject Reference Number for the cancellation negative re
62. can enter basic information relating to a PC product such as the Product Code the Description etc Product Definition EENT AA Exchange Rate Variance rodu le Product Description i Override Limit Product Type S Stop Limit Description Rate Code 0 H Slogan E Rate Type Bal Product Group laz Start Date End Date Remarks S E Events Expression MIS Preferences Accounting Roles Tax Maker Date Time Checker Date Time Mod No Record Status Authorization Status For any product you create in Oracle FLEXCUBE you can define generic attributes such accounting roles and heads events and MIS details etc by clicking on the appropriate icon in the horizontal array of icons in this screen For a PC product in addition to these generic attributes you can specifically define other attributes These attributes are discussed in detail in this chapter You can define the attributes specific to a PC product in the PC Product Definition Main screen and the PC Product Preferences screen In these screens you can specify the product type and set the product preferences respectively 4 ORACLE For further information on the generic attributes that you can define for a product refer the following Oracle FLEXCUBE User Manuals under Modularity e Product Definition e User Defined Fields e Settlements Product Code Specify the product code Description It may be difficult
63. can invoke this screen by typing PCSPTPBN in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button P2P Beneficiary Summary E gt search C Advanced Search Reset KY Clear All Case Sensitive Authorization Status li 5 Record Status Telephone Bank code KYC Status z Email Id Facebook ID Account Number i mj m E Records per page 10f1 Authorization Status Record Status Emailld Telephone FacebookID Bankcode BankName Account Number In the above screen you can base your queries on any or all of the following parameters and fetch records e Authorization Status e Email ID e Facebook ID e Account Number e Record Status e Telephone sal ORACLE e Bank Code e KYC Status Select any or all of the above parameters for a query and click Search button The records meeting the selected criteria are displayed If you are allowed to query beneficiary details then system displays the following details pertaining to the fetched records e Authorization Status e Record Status e Email Id e Telephone e Facebook ID e Bank Code e Bank Name e Account Number e Beneficiary Name e Address 1 2 34 and 5 e KYC Status e Remarks 3 14 Maintaining P2P Payments Parameters You can maintain peer to peer payment processing details in the P2P Payments Parameters Maintenance screen You can invoke this screen
64. can specify whether the contract information is to be written into handoff tables to be picked up or referenced by the external agency Collection Stmt Required Collection statements can be generated for contracts involving the product if indicated in this screen Response Advice Required You have the option of indicating that a response advice needs to be generated for approvals rejections and closures by enabling the check box positioned next to the Response Advice Required field Response Days The response days indicates the number of days after the activation date beyond which an incoming collection transaction using the product cannot be rejected Basis If you indicate that a response advice needs to be generated you have to indicate the basis for response advice generation The response advice generation can be based on the Event Date or on the Response Date aM ORACLE P2P Payments P2P Payment Type Select the P2P payment type from the adjoining drop down list The options available are e Customer Debit e Test Transaction e P2P Final Payment e NULL Note P2P Payment Type is applicable for Outgoing Payment and Reject Outgoing Payment product types only Ifthe P2P payment type is Customer Debit then it is not mandatory to specify the Counterparty Bank Code and Counterparty Account Number as long as email ID telephone number and facebook ID are specified for the transaction Ifthe P2P payment t
65. clicking Preferences button Payments and Collections Product Preferences Product Code Collection Type Collection Scheme Desciption RFD Type Type Product Type Transfer Type Main Additional Network Parameters gt g Details le g House Accor r Clearing Detail Clearing House Account External Clearing Clearing Mode p 3 Cleanng Network Payment Type Bott Description Currency Currency Dispatch Response Fields Charge Details Dispatch Auto Response Waiver Charge Auto Dispatch ASCII Handoff Reqd Allow Third Party Charge ng Payment Collection Statement Charge Customer Workflow Required St Dispatch Media Response Advice Charge Account Statistics Dispatch ys 7 negana Response Days e Name gt Basis No of Records Descripton Charge Searer Reject Account Details before Response Days Reject Account Details after Response Day P2P Payments Account Type Process Rejects After P2P Payment Type e Days B AccounyGL ch oct Verify Funds Only RecallRefund Charges Currency Rejection Details Restrict Customer Currency Rejection Response Days Basis Calendar Working Currency Common Preferences Currency Cut Of Hour Invoice Split Required Minimum Drv Cut Off Min A Processing Prionty Currency Customer Entry Days Override Overdraft Minimi ansacton z b jispatch Acc ting Minimum Tra ppc Customer Entry Value Dispatch Accounting Amount A jt Days Referral Required Currency e Counterparty Entry
66. counterparty leg of the transaction is processed using this product Case Two e The outgoing product category maintenance is referred Ifthe transaction does not fit the specifications of the book transfer product the system tries to fit the transaction in the list of internal clearing products you have maintained in the sequence you have specified Ifthe transaction fits the parameters defined for an internal clearing product the transaction is processed using the product Case Three e The outgoing product category maintenance is referred Ifthe transaction does not fit the specifications defined for any internal clearing product the system tries to match the transaction with the external clearing products you have specified for the product category in the sequence you have specified The transaction is then processed using the first product in the list of external clearing product whose parameters match that of the transaction Apart from specifying the different clearing products you can specify certain preferences for a product category The preferences you specify for a category determine the manner in which transactions are ultimately processed Payments Contract Batch processing A payment transaction from an electronic banking system is handed off to the Incoming Message Queue of Oracle FLEXCUBE The message is then translated into contract details by the interface function The transaction details
67. default attributes to suit a specific transaction You can capture the details of a Payment Collection transaction in the PC Transaction Input online screen Capturing Details of Payment Collection Transactions You can invoke the PC Transaction Input online screen from the Application Browser Entering a Transaction To enter a transaction in this screen select new icon from the toolbar Product Category Product Category Batch Number Batch Description In this screen you must enter the following details al ORACLE Product Category Enter a valid product category code The transaction that you are capturing will be associated with the product category you specify If you enter a valid code the Transaction Input screen is displayed Batch Number and Batch Description Specify the Batch Number and a description of the batch A batch is used to group transactions When you confirm your input the main PC Transaction Input screen is displayed In this screen you will view the batch number to which your transaction will be posted the current number and the reference number of the transaction you are capturing You can invoke this screen by typing PCDTRONL in the field at the top right corner of the Application tool bar and click on the adjoining arrow button Click new icon in the application toolbar and enter the details E New amp Enter Query Product Category Contract Refe
68. e Customer This is defaulted to the Walk in Customer for the processing branch e Transaction Amount The transaction amount is the total of all the debits to the suspense account maintained in the Bank Wide Parameters for the TRS amount tags for the processing date Reversals represented as negative amounts are not considered You must also consult the Core Services user manual for information about the maintenance in the Bank Wide Parameters for TRS DD generation Background Processes The Payments and Collections module processes large volumes of transactions during a given business day In such a scenario the processing can be configured to run in a background or JOB mode This mode involves very little or no front end processing in the online screens all processing being done by the various background processing jobs of the system The following background processes or jobs comprise the JOB mode e BOOK_INIT processor Used mainly for contracts that are uploaded and not as yet initiated this job processes the BOOK and INIT events for uninitiated contracts It also processes the accounting for those contracts for which accounting is due including newly authorized contracts that are ready for accounting e INIT processor This job processes the INIT event for contracts that are already booked e MISC processor This job processes the contracts that are due for miscellaneous processing es ORACLE 8
69. for a particular Creditor DD agreement here On the maintained date agreement status will get updated as Expired as part of the existing batch process Agreement Status Specify the value for the field The value determines the status of the mandate at any point of time Options available for this field e Active The agreement is available for usage e Used One Off transaction sent e Auto Cancelled Agreement auto cancelled because of non usage for specified period e Final FRST RCUR and FNAL transactions sent e Customer Cancelled Agreement closed by Creditor e Expired Agreement has crossed expiry date e Amended Unique identification of an agreement changes Agreements with agreement status as Active and record status as Open is considered as valid agreement Modify operation changes the agreement status from Active to Customer Cancelled when creditor is initiating the closure of agreement Agreements with status as Used Auto Cancelled Final Expired Amended cannot be changed back to Active There are validations to restrict this status change Used Auto Cancelled Final Expired Amended agreements can be closed and these agreements cannot be re opened Customer Cancelled agreements can be closed and can be re opened The agreement status is Active for future effective dated agreements If a Final collection is rejected cancelled returned reversed i e any R transaction on a FNAL collection
70. from the adjoining drop down list The options available are e Calendar Days Select Calendar Days to consider all days in a calendar e Branch Calendar Select Branch Calendar to consider only the working days of a transaction branch By default the system selects Branch Calendar Registration Notification Frequency Select the frequency for generating registration notification from the adjoining drop down list The options available are e Daily e Weekly e Monthly e Quarterly e Half Yearly e Yearly The system defaults Daily as Registration Notification Frequency Notification Alert on End Date Check this box to indicate that the notification needs to be generated on the registration expiry date Archival Days Specify the days after which the record should be moved from P2P Payments Registration Queue to corresponding history data store The data movement is done if any record becomes older than the archival days maintained Ta ORACLE 3 15 Viewing P2P Payments Beneficiary Registration Queue You can view the customer debit transactions and amount block requests for the P2P payments in the P2P Payments Beneficiary Registration Queue screen You can invoke this screen by typing PCSBERGQ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button P2P Payments Beneficiary Registration Queue E gt search C Advanced Search 9 Reset KY
71. identification details for the SEPA transaction is maintained in the PC Beneficiary Maintenance screen For more details on this refer section Maintaining Beneficiary Accounts for a Counterparty Bank in the chapter Maintaining Information specific to the Payments and Collections Module of this User Manual Learning Database Maintenance The customer and counterparty details of the SEPA transaction is maintained in the Counterparty Details screen These details that you maintain here can be viewed in the Contract Online screen if the learning database option is selected For more details on this refer section Maintaining a Learning Database in the chapter Maintaining Information specific to the Payments and Collections Module of this User Manual Creditor DD Agreement The details of the Creditor involved in the SEPA Direct Debit Transactions are maintained in the PC Creditor DD Agreements screen For more details on this refer section Maintaining DD agreement details for creditors in the Chapter Maintaining Information specific to the Payments and Collections Module of this User Manual PC Periodic Instructions The identification details of the customer and the counterparty involved in the SEPA transactions are also captured in the PC Periodic Instructions screen For more information on this refer section Maintaining Details for Periodic Instructions in the chapter Maintaining Infor
72. in the Correspondent Bank Maintenance screen You can invoke this screen by typing PCDCYCOR in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button amp Currency Correspondent Maintenance urrency Correspondent Branch Code 000 Account Description Bank Futura Currency Account Type L W Bank code Bank Name Branch Account Number Currency Clearing Network 0 0 fi A E Primary Correspondent Maker Date Time Checker Date Time Mod No Record Status Authorization Status The following details are maintained Branch Code The system defaults the code of the current bank here Description The system defaults the description of the current bank here 3 103 ORACLE 3 39 Currency Specify the currency code from the adjoining option list Account Type Select the account type from the adjoining drop down list Bank Code Specify the bank code of the correspondent from the adjoining option list Bank Name The system displays the bank name of the bank code specified Branch The system displays the branch name of the bank code specified Account Number Specify the account number of the correspondent from the adjoining option list Currency The system displays the currency code of the account number specified Clearing Network Specify a value for the field from the adjoining list of values The field is used to specify the clea
73. incoming XML SEPA SCT and SDD messages are validated for BIC The debtor agent BIC and creditor agent BIC should have valid bank codes maintained in the PC Bank directory maintenance or BIC upload directory Refund Compensation and Balancing Payment for Debtor Bank The processing done at Debtor bank CSM and Credit Bank for handling refund of compensation is given below Debtor Bank Processing On Debtor s request for Refund Debtor bank sends Refund instruction to CSM Debtor bank has rights to collect refund compensation for the loss incurred by crediting the debtor with value date as settlement date of original collection transaction Crediting the debtor with back value dated will be achieved by configuring Original Transaction Value Date parameter at product level This compensation facility is only for the Refund transactions originated by the Debtor Apart from the compensation amount balancing payment charges from the Creditor Bank to the Debtor Bank can be recovered by existing charge mechanism Hence Debtor Bank can send the Refund instructions with original collection amount compensation amount charges amount 389 ORACLE 5 25 11 During Refund processing Debtor bank debits CSM for the original collection amount compensation amount and charge amount and credits original collection amount into Debtor account as of value date of the original collection transaction Compensation amount and charge amount will ge
74. indicates the settlement amount and currency of the original instruction This is a display only field Source Reference This indicates the source reference number of the original instruction for which reject refund is received This is a display only field Settlement Date This indicates the settlement date of the original instruction This is a display only field Original Payment Info ID Specify the unique identification as assigned by the original sending party to unambiguously identify the payment information group This field maps to field Payment Info ID of Common Payment Gateway aay ORACLE 5 2 7 Redispatch Details Redispatch Number Specify the redispatch count for the parent transaction which is being redispatched Redispatch Reference For collection transactions specify the reference number of the parent transaction that is being redispatched Redispatch Indicator This indicates whether the collection transaction has been redispatched If it has not been redispatched this field indicates Not Applicable If the transaction has been redispatched this field indicates whether the transaction being viewed is a parent transaction or a child transaction Auto Redispatch Indicate if this outgoing collection transaction needs to be redispatched automatically if rejected Redispatch Date Specify the date of redispatch of the parent transaction Viewing User Defined Fields for a PC contract In the
75. information in the form of reports in Oracle FLEXCUBE For every module you can generate reports which give you data about the various events in the life of a specific contract or across contracts at a specific point in time You can have analysis reports daily reports exception reports reports on events that ought to have taken place on the contract but have not due to various reasons history reports and so on A set of report formats is pre defined for every module Generating Reports From the Application Browser select the Reports option A list of all the modules to which you have access rights are displayed in the screen When you click on a module all the reports for which you have access rights under the selected module are displayed Click on the report you want to generate You will be given a selection Criteria based on which the report would be generated Click OK button when you have specified your preferences The Print Options screen gets displayed where you can specify the preferences for printing the report Report Options Format Output Output Print View Spool PrintAt Client Server Printer Printer In this screen you can indicate the following preferences for printing the report Format Select the format in which you want the report to be generated from the options provided in the drop down list The following options are available e HTML e RTF e P
76. le Currency Minimum Transaction Amount Currency Maximum Transaction Amount Dispatch Auto Dispatch ng Payment 5 before Response Days Restrict Customer Rejection Co n Type RFD Type Transfer Type stomer Transfe Clearing House Account Currency Response Fields Auto Response Respo Required Response Days Basis Reject Account Details after Response Dav Process Rejects After Respo Days Reject Verity Funds Only Account Type Branch AccounvGL Currency Response Days Basis Calendar Working Currency Cut Of Hour Cut Of Min Processing Priority Customer Entry Days Customer Entry Value Days Counterparty Entry Days Counterparty Entry Collection Scheme Type External Clearing Clearing Network Description Charge Details Volume Statistics Charge Bearer P2P Payments P2P Payment Type Recal Retund Charges Compensation Clearing D etails Payment Type Payment type indicates whether the payment is within the country or outside The options are e Domestic e Cross Border e Both 4 6 Waiver Charge Allow Third Party Charge Charge Account Statistics invoice Split Required Allow Post Cutoff Transaction Override Overdraft Dispatch Accounting Referral Required Currency Calendar Network Calendar E miasma ian Smee ORACLE At the time of product resolution system compares the counterparty bank code s count
77. maintenance are not considered for updating Utilized Transactions for Calendar Year R transaction received after Number of Transactions per Calendar Year maintenance for the original parent transaction processed before Number of Transactions per Calendar Year is not considered for updating Utilized Amount per Calendar Year SUE ORACLE 6 1 6 Levying Charges on Payments and Collections Transactions Introduction At your bank you can opt to levy charges on payments and collection transactions in any of the following ways e Asa flat amount e As a percentage of the transaction amount You can also apply charges depending upon the level at which they need to be applied when levied on a transaction by building a charge rule and a charge class e Forall the accounts of a customer e Fora particular customer account e For all transaction currencies e Fora specific transaction currency Charges that you levy on a payments or collection transaction are computed when the transaction is initiated and are liquidated along with the transaction The Charge Mode Also you can levy charges either as a premium collected over and above the transaction amount or a discount discounted from the transaction amount This is known as the charge mode and can be specified for each payments collections product category so as to default to any transactions processed under the product category Charge Specifications
78. may need to refer to any or all of the User Manuals while working on the PC module e Procedures e Products e User Defined Fields Glossary of Icons This User Manual may refer to all or some of the following icons Icons Function x Exit Add row E Delete row a Option List tg ORACLE 2 1 2 Payments and Collections An Overview Introduction The Payments and Collections PC Module of Oracle FLEXCUBE helps you process local currency funds transfer transactions initiated either by your customer through an Electronic Banking System or by your staff in any of your branches on behalf of a customer The PC module handles the following types of transactions e Payment transactions involving the transfer of funds from one s own account to another account s Such transactions are initiated by the debtor who instructs his bank debtor s bank to draw transfer a certain amount from his debtor s account to the creditor s account in the creditor s bank e Collection transactions involving the transfer of funds from a different account into one s own account Such transactions are initiated by the creditor who instructs his bank the creditor s bank to draw a certain sum from the debtor s account in the debtor s bank assuming that such an agreement exists between the debtor and the creditor of the transaction and between them and their respective banks Collecti
79. of the Ultimate Creditor The valid values are e C Code e P Proprietary Sar ORACLE Ultimate Creditor Scheme Name If Scheme Name type is C then select the Scheme Name from the values mentioned in the LOV depending on Organization Identification or Private Identification If Scheme Name type is P then enter the Scheme Name your own which can contain free format text and should of length 35 Ultimate Creditor Date of Birth Specify the Date Of Birth of the Ultimate Creditor Input the Date of Birth is only for Private identification 5 2 6 Capturing the Message Details New B Enter Query Product Category Contract Reference Collection Type Product Code Custom Reference RFD Type le Source Reference Product Type Network Main Transaction Details Collection Details Party Details Message Details UDF Dispatch Details Dispatch Dispatch Date Recall Message Details Message Creation Recall Message Recall Reject Code Date Reference Recall Reject Code Cancellation Id Recall Message Originator Name Reject Code Additional Number Recall Reject Code Recall Status r Recall File Ref Number Originator Bank N incoming Message Details File Reference Message ID Instructing Bank Setiement Method Message Name Instructed Bank Message Creation H a Date Outgoing Message Details Original Message Details Outgoing File Original Message Original Settlement Reference Name Date Outgoing Message ID Original Reference Original S
80. or the scheme 4 24 ORACLE Service Level Code You can select an identification code for a pre agreed level of service between the parties from the drop down list This service level code is used in the outgoing SCT and SDD messages of the product The option available in the drop down list is SEPA Recurrent Collection Receipt Days System will display an override message if the recurrent collection which determined based on the Direct Debit sequence type is not received within the Recurrent Collection receipt days from the activation date You can specify the number of calendar days to arrive at the latest date by which the recurrent incoming collection transaction should be received by the debtor bank This is applicable only for incoming collection transaction First Collection Dispatch days You can specify the number of calendar days to indicate the dispatch days for the first outgoing collection transaction The dispatch date for the first collection determined by the DD sequence type will be derived by adding the first collection dispatch days to the activation date This is applicable only for outgoing collection products Recall Refund Charges Compensation Suspense Account Specify the value for the field from the adjoining list The list contains the GLs The field is enabled for Recall of Incoming collection and Recall of Outgoing Collection products Charge Suspense Account Specify the value for the f
81. process code ZFCN and the credit leg for the individual transfer amount will be based on the corresponding product code of the transaction The accounting entries for PC transactions with customer consolidation across products is as follows ORACLE 9 3 For Outgoing Payment Event Code Accounting Role Amount Tag Dr Cr DRLQ CUSTOMER FILE_AMT DRLQ INTSUSPAY TFR_AMT Event Code Accounting Role Amount Tag Dr Cr CRLQ INTSUSPAY TFR_AMT CRLQ CLGSUSPAY TFR_AMT For Outgoing Collection Event Code Accounting Role Amount Tag Dr Cr DRLQ CLGSUSREC TFR_AMT DRLQ INTSUSPAY TFR_AMT Event Code Accounting Role Amount Tag Dr Cr CRLQ INTSUSPAY TFR_AMT CRLQ CUSTOMER FILE_AMT For Reversal of Outgoing Collection Event Code Accounting Role Amount Tag Dr Cr DRLQ CUSTOMER FILE_AMT DRLQ INTSUSPAY TFR_AMT Event Code Accounting Role Amount Tag Dr Cr CRLQ INTSUSPAY TFR_AMT CRLQ CLGSUSREC TFR_AMT Event Advices for PCs The following list of advices can be generated for the various events that get triggered during the life cycle of a PC transaction Event code Advice INIT REMIT_SLIP CRLQ CREDIT_ADVICE APPR APPROVAL_ADVICE REJT REJECTION_ADVICE ORACLE CLOS CLOSURE_ADVICE RECL RECALL_ADVICE DRLQ DEBIT_ADVICE APPR APPROVAL_ADVICE REJT REJECT_ADVICE RECL RECALL_ADVICE The following advices will b
82. rate queue in the Exchange Rate Exception Queue You can invoke this screen by typing PCSXRXSQ in the field at the top right corner of the Application tool bar and click on the adjoining arrow button Exchange Rate Queue E gt Search Advanced Search 9 Reset 4 Clear All Case Sensitive Authorized Contract Status Account Entry Reference Number Product Code Customer No Account No Activation Date LBL_CST_AC_LCF Exception Queue Contract Reference Product Category Customer Account Branch Customer Account Currency Customer Bankcode W j l I L AAN Records per page 15 10f1 Authorized Contract Status Exception Queue Account Entry Reference Number Contract Reference Product Code oe um Details Exception Retry All contracts logged into the exchange rate queue are displayed grouped according to the following e Authorization e Exception Queue e Contract Reference Number e Product Category e Contract Status ap ORACLE Account Entry Reference No Product code Customer Number Customer Account Number Activation Date Click Exception to view the exceptions 5 20 Periodic Exception Queues All periodic instructions that have failed to be executed in the immediate previous Beginning of Day batch and which are still pending resolution can be viewed in the Periodic Exception Queue You can access this queue in the Periodic Exception Queue screen Y
83. s account The various types of collection transactions can be summarized as follows Direct Debit DD Transactions Outgoing Direct Debits Incoming Direct Debits Reject of Outgoing Direct Debits Reject of Incoming Direct Debits Gu Py Recall of Outgoing Direct Debits a ORACLE 6 Recall of Incoming Direct Debits Request for Debit RFD Transactions Outgoing Request for Debits Incoming Request for Debits Approval of Incoming Request for Debits results in an Outgoing Payment Approval of Outgoing Request for Debits results in an Incoming Payment Reject of Outgoing Request for Debits oa F wr gt Reject of Incoming Request for Debits In the Payments module you can perform the following operations e Module specific Static data maintenance e Product definition e Contract input e Transaction processing e Process Monitoring and Recovery e Batch Processing e Generation of Advices Maintaining Module Specific Information Before you begin operations in the Payments and Collections module of Oracle FLEXCUBE you have to maintain certain information that is required to process the transactions that you receive This maintenance is done in screens invoked from the Application Browser Local Bank Directory Maintenance You can maintain a directory of Local Clearing Banks in the Local Banks screen In this screen you have to specify a unique Code for the bank a brief description In addition you can capture t
84. system ID ST2 with description as EBA Clearing STEP 2 is available Direct Participant Check the box to indicate that the processing bank is either Direct Participant or Indirect Participant of the clearing network and or the scheme Clearing Network BIC Handoff Directory e The Incoming and Outgoing Handoff directories Incoming and Outgoing transactions will be handed off to the respective directories that you indicate in this screen ORACLE e IBAN validation for the Counterparty Account Number is required for outgoing payments and incoming collections using the clearing network Note For SEPA products PC products where Service Level Code is SEPA system will do the IBAN validation even if the IBAN Validation check box is not checked For Non SEPA prod ucts PC products where Service Level Code is not SEPA system will do IBAN validation only when the IBAN Validation check box is checked e Indicate whether the processing bank is an indirect participant of the clearing network If yes then the counterparty account will be replaced with the currency correspondent account RTGS The following RTGS network details should be specified Network Type Select the network type This can be RTGS or Non RTGS By default system selects Non RTGS The network type is RTGS for RTGS networks and Non RTGS for SKN networks If you select the Network Type as RTGS and Network Qualifier as
85. that is been referred in the incoming messages Message Creation Date Specify the date on which a message was created Instructing Bank Specify code of the instructing bank from which the message was instructed oe ORACLE Instructed Bank Specify code of the instructed bank to which the message was instructed Settlement Method Specify the settlement mode Outgoing Message Details You can maintain the following outgoing message details Outgoing File Reference No This indicates the file reference number of the incoming message This is a display only field Outgoing Message ID This is a unique message bulk reference number populated from the incoming instruction This is a display only field Outgoing Message Name This indicates the message name identifier of the outgoing message For e g Pain 001 001 01 Message Creation Date This indicates the date and time the transaction was created This is a display only field and is defaulted with the value in the incoming message Original Message Details Name This indicates the message name of the original instruction for which a new instruction is received This is a display only field Reference Number This indicates the message identification of the original instruction for which a new instruction is received This is a display only field Amount The system displays the new instructions received for the original amount Original Settlement Currency This
86. the Customer Country Specify the address country code of the customer from the option list This is optional Account Number Specify the account number of the customer participating in the indirect transaction Currency Specify the currency that is used in an indirect transaction Bank Code Specify the Bank code of the bank that has participated in a transaction Initiating Party Details Name Specify the name of the initiating party This is an optional field Address Line 1 Specify the address line1 of the initiating party This is an optional field Address Line 2 Specify the address line 2 of the initiating party This is an optional field Country Select the country of the initiating party from the option list This is a mandatory field if the address details are specified Issuer Specify the Identification Issuer of the initiating party This is an optional field This is applicable for Organization identification as Proprietary Identification or Private Identification City of Birth Specify the city of birth of the Initiating party Initiating Party Identification Select the unique way of identifying the initiating party from the drop down list The following are the options available e Organization Identification e Private Identification gag ORACLE Country of Birth Select the country of birth of the Initiating Party from the option list Initiating Party BIC ID Specify the Bank Identification Cod
87. this screen by typing PCSAUTQ7 in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Authorizer 1 Queue I Search Advanced Search 9 Reset 4 Clear All Case Sensitive Contract Reference No Product Category la Exception Queue Account Entry Reference Product Code a Network Customer Account No jl Branch Records per page 15 v 10f1 Contract Reference No Product Category Exception Queue Account Entry Reference ProductCode Network Customer Bankcode Account Branch Detail Reverse Authorize You can query the record based on the following details e Contract Reference Number e Product Category e Exception Queue e Account Entry Reference e Product Code e Network e Customer Account Number Clicking on Search button the system will display all the records pertaining to the specified criteria Double clicking on any of the records the system will display the record details Clicking on Authorize button you can authorize the contract s The system will validate the contract amount against the Auth2 Limit amount If the contract amount exceeds the Auth2 Limit amount then the contract will be moved into Level 2 Authorization A2 queue If the contract amount does not exceed the Auth2 Limit then the contract will be ready for dispatch and also system will process the DRLQ event You can select multiple contracts and authorize them in bulk oat
88. to check the original incoming collection contract and its status This field is applicable for Reverse of Incoming Collection products Based on the field value Reversal without Matching at product level the system will am ORACLE e Validate the Original incoming collection contract and its status for the reversal processing when Reversal without Matching at reversal of incoming product level checkbox is unchecked e Not validate original incoming collection contract and its status for reversal processing when Reversal without Matching at reversal of incoming product level checkbox is checked Reversal will be performed irrespective of whether the original incoming collection contract is available or not with contract status as Rejected Reversed Split or Deleted Dispatch Dispatch You can control the dispatch of transactions processed under a product Choose the Dispatch option if you would like transactions involving the product to be dispatched to the Clearing Server on the basis of the Dispatch Days that you specify Auto Dispatch You can indicate that outgoing transactions must be dispatched to the clearing server on authorization Outgoing Payment Workflow Outgoing payment transactions could be tracked to closure if required Such tracking indicates monitoring of the transaction in each different status in its life cycle If you do not indicate this in the product preferences then outgoing payment tr
89. to differentiate B2B scheme mandates from CORE COR1 scheme mandates Agreement Id Specify a unique ID to identify the agreement between the creditor and the debtor participating in a transaction Debtor IBAN Specify International Bank Account Number of Creditor from the adjoining list of values displaying IBAN number If the number is not available in the list and then insert the number in the field Debtor Reference Code Specify the reference of the debtor of the mandate as the value for the field The Maximum length of the field is 35 characters The field is optional Charges Applicable To indicate applicability of charges or fees levied on setting up and or amending direct debit creditor or debtor agreements you can enable the Charges Applicable option in the PC Debtor DD Agreements screen The applicable charges are computed through the Interest and Charges IC module For details refer the Interest and Charges module user manual Counterparty Creditor ID Scheme ID Specify a value from a list of values The list of values fetches the creditor ID s from Payments and Collections Creditor Details Maintenance Sraa ORACLE On selecting Creditor ID from list of values FLEXCUBE defaults the address details in the corresponding fields Specify the value for the collection scheme types CORE COR1 and B2B The field value is validated against the format specified for Creditor ID Scheme ID field in Payments
90. to recognize a product just by its code In the Description field therefore suitably describe the product code so that it can be easily identified This description will be displayed along with the code throughout Oracle FLEXCUBE Product Type An important detail in defining a product is to specify the type of product you are creating The product type identifies the basic nature of a product This helps to classify the product The entries that are passed the messages that are generated and the processing of contracts depend on the Product Type A payment and collection product that you define can belong to either of the following categories e Incoming Collection e Incoming Payment e Outgoing Payment e Outgoing Collection e Reject of Incoming Collection e Reject of Outgoing Collection e Recall of Incoming Collection e Recall of Outgoing Collection e Reject of Incoming Payments e Reject of Outgoing Payments e Reverse of Outgoing collection e Reverse of Incoming collection These product categories are referred to as product types When you create a product you must specify its type Slogan You can enter a marketing punch line for every product you create This slogan will be printed on all advices that are sent to customers who avail of the product For example if you set up a borrowings product called Money Multiplier you could enter the slogan Watch your money grow with Money Multiplier Product Group
91. top right corner of the Application tool bar and click on the adjoining arrow button Payments and Collections Cancellation H save Contract Reference Account Number eon Reference Settlement Date Recall RefNo OO00RECL110040001 Recall Reason Additional Recall Reason Additional Recall Information Service Type x 4 Contract Reference Cancellation Originator Name Cancellation Originator Bank Account Numt az al Maker Date Time Checker Date Time Mod No Record Status Authorization Status You need to capture the following details here Original Message Reference Number Select the original message reference number from the adjoining option list Contract Reference Number Select the contract reference number from the adjoining option list Customer Reference Select the customer reference number from the adjoining option list Account Number Select the account number from the adjoining option list Settlement Date Specify the settlement date Recall Reference Number System displays the unique sequence number Fpa ORACLE Recall Reason Select the recall reason from the adjoining list of values that display the valid ISO Reject codes applicable for the Payments and Collections Cancellations Cancellation initiation processing in this screen validates the entered ISO Reject code against the applicable exceptions as maintained in the Rej
92. transaction is saved Future Value Limit Days If the Booking date of the transaction is future date then the Default Activation Date is Future Value Limit Days Consider the example e If the activation date is not specified the online screen the Default Activation Date is considered as the activation date which in this case is 11th June 2003 Since there is a difference of a day between the activation date and Default Activation Date the future valued limit days are not exceeded and the transaction is accepted e f you specify 12th June 2003 as the activation date in the online screen the System compares it against the Default Activation Date which is 11th June 2003 Since the difference between activation date and Default Activation Date is within the future valued limit days the transaction is accepted e If you specify 10th June 2003 as the activation date in the online screen the System compares it against the Default Activation Date which is 11th June 2003 Since the difference between activation date and Default Activation Date is not within the back valued limit days an and an override is sought when the transaction is saved Move Back Dated Activation Date You can indicate that the activation date if in the past is to be moved forward to the default activation date by enabling the Move Back Dated Activation Date option If you enable this option you have to indicate the Default Activation Date as well The defa
93. transaction validations are done in the front end online screens with user driven resolution of errors and overrides Contract Partitions Another facility provided by Oracle FLEXCUBE for processing large volumes of payments collection transactions is data division of the contract tables using range partitioning The use of range partitioning divides very large tables and indexes into smaller and more manageable pieces called partitions Once the partitions are defined SQL statements can access and manipulate the partitions rather than entire tables or indexes The method of d ORACLE 8 6 partitioning used in the Payments and Collections module is Range Partitioning which maps rows to partitions based on ranges of column values The contract table is partitioned based on the column SEQ_NO The module supports a maximum of ten partitions of the table The business logic used in the partitioning is that certain customers institutional would have extremely high volumes of contracts Therefore for each customer the value for the SEQ_NO column is maintained and for contracts of all customers for whom the SEQ_NO is not maintained the value of SEQ_NO is 1 The value for SEQ_NO for a customer is maintained in the Payments and Collections Partition Sequence Maintenance PCDSQMNT screen which you can invoke from the Application Browser Payments and Collections Partition Sequence Maintenance E New
94. typing PCDLUPMT in the field at the top right corner of the Application tool bar and click the adjoining arrow button User Defined LOV Maintenance es New E Enter Query List Of Values Code Description List Of Values 10f1 E Field Values Date Time Date Time Mod No Record Status Authorization Status List of Values Code Specify the code for the list of values Description Specify the description of the code 3 30 Specifying Fields to be Included in Account State ments You can specify the fields that should be included in the account statements that you generate You can do this in the Account Statement Fields screen invoked from the on ORACLE Application Browser by typing PCDACSMT in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Payments amp Collections Account Statement Field Maintenance E New Enter Query Account Stataement Fields Product Type Description Product Code Description Fields Field Number Field Name Field Description m C i Input By Authorized By Modification Date Time Date Time Number E Authorized E Open You need to specify the product type and the product code before specifying the fields You can specify a maximum of fifteen fields for an account statement In this screen you must also specify the se
95. you can specify the authorized customers and the accounts for a specific station and source combination All transactions that you receive will be validated for the existence of a valid Customer Station and Account Client Agreement Maintenance You can capture customer agreements relating to a product in the Customer Agreements screen For the transactions processed under a specific product involving a specific customer you can specify the manner in which the value date of the accounting entries for the customer leg of the transaction should be arrived at the cut off time whether consolidation is required or not and other such parameters which take precedence over the parameters defined at the product level While generating outgoing DD collections on behalf of your customers you should maintain the Creditor s DD agreements wherein the details pertaining to the debtor s account bank and agreement ID are captured Similarly while receiving incoming DD s on behalf of your customers you must ensure that you maintain DD agreements wherein the details pertaining to the creditor such as the creditor s bank account number and agreement ID are captured Account Statement Fields Definition You can specify the fields that should be included in the account statements that you generate You can do this in the Account Statement Fields screen You can specify a maximum of fifteen fields for an account statement You must also specify the sequen
96. you have to indicate if a direct debit DD agreement is required for processing Incoming and Outgoing transactions Unlike the customer agreement which is used to validate the product and customer involved in a transaction a DD agreement exists between the customer and the counterparty participating in a transaction San ORACLE If the selected customer is Individual type then a static data for error code PC SVV 09M with description as Customer type cannot be Individual for B2B Collection Scheme will be generated Counterparty Bank Code Check the box if you have the counterparty bank code that is involved in the DD agreement Counterparty Account Number Check the box if you have the counterparty account number that is involved in the DD agreement Creditor ID Scheme ID Required MRA don dnaucannidatignunterparty account number that is involved in the DD agree Check the box if you have the DD agreement identification details Redispatch Details Redispatch Required An outgoing DD RFD may be rejected for various reasons one such reason being the lack of funds in the customer debtor s account The debtor s bank may therefore reject the Incoming DD RFD The creditor s bank will process the same as a reject of Outgoing DD RFD However the system allows you to redispatch a rejected outgoing DD RFD A redispatch initiates a new transaction which is referred to as the child contract of the original rejected t
97. 1 2 Payment Details 2 E Payment Details 3 Payment Details 4 a Purpose of the Collection Maker Date Time Checker Date Time Mod No Record Status Authorization Status The details maintained here will be used to validate outgoing transactions initiated by the creditor Note If a branch has been maintained as a customer of your bank and you are specifying an internal GL of the branch as the account for the agreement you can choose the CIF ID of such a branch in the Customer field and the requisite GL in this field Such agreements would be validated for whenever a direct debit transaction is entered with a GL as the ac count and the branch CIF ID as the customer of the transaction oe ORACLE Product Code Select the product code from the list option provided This is applicable only if the corresponding customer agreements exist and you have indicated that a DD agreement is required for the respective customer agreements Product Description Give a brief description on the product Customer No Specify the customer if the corresponding customer agreements exist and you have indicated that a DD agreement is required for the respective customer agreements Customer Account Branch Specify the branch if the corresponding customer agreements exist and you have indicated that a DD agreement is required for the respective customer agreements Account No Specify the account if the corresponding customer agreem
98. 2 PCSCNSOL on cessecssseesseeceoes 5 55 PCDCLRNT oo cessccssscccssseceoees 3 7 PCSCONAU 0 cccseesseeceees 5 44 PCDCRAGT o ceesscssssecsseeeee 3 34 PCSCONHS ccseess cece 5 57 PCDCRAHS ccsscccssseee 3 105 PCSCRAHS ecscccsseesse 3 106 PCDCREID ssccssssecssseeee 3 33 PCSDRAHS ccssseessees 3 108 PCDCRXSQ ooeeescessstecssseeee 5 53 PCSIDRHS cccseesseees 3 109 PODOUSST since wucsce 3 55 PCSINAUQ o oo esssecsssstecssseees 4 40 PODOYOOR ciceccccsicectecs 3 103 PCSIPRSQ o cceessecsssseesssseee 4 42 PCDDCCAT ooeeesecsssescsssteeee 3 77 PCSMNDON ssccssscecssseees 3 54 PCDDRAGT eessscssssecssseeee 3 38 PCSONMON sccssceeeeeee 8 5 PCDDRAHS cssscccssees 3 107 PCSPEXSQ ueceessecsssstscsssee 5 60 PCDERRCD o esscssseccssseeee 3 95 PCSPRXSQ ooceessecsssstecesseee 5 62 PCDFTONL cscssseccssseeee 5 42 PCSPTPBN o ccsscsssscesesseees 3 21 PCDIDRES ssccsssecccsseeee 3 43 PCSRCLULIN sctecscccesatcctccceasts 5 75 PCDIDRHS ccscscecsssees 3 109 PCSRCLOT cesscccsecsseeceoes 5 84 PCDIFGEN cssccscsseessseeee 5 92 PCSRLXSQ ooeceessecsssstesenseee 4 33 PCDINSTM ccsccscsecssseeen 3 79 PCSROWSE o eececcecsseece 5 63 PCDISMAP ssccssseessseeee 3 98 PCSSPLTS o scccscccseesseeeeees 5 59 PCDLUPMT s csssccccsseeee 3 71 PCSTEXSQ ooecesssecscsstesssssees 5 58 PCDMNDON cccsseee 3 50 PCSXRXSQ oceessecscsstecsnseees 5 61 14 1 ORACLE
99. 3 1 e CONS processor This job processes all the consolidation batches that are present in the system liquidating and closing them e MNTR processor This job is a system monitoring process keeping a tab on the various contracts in the system and updating the monitor tables that can be viewed from the System Monitor Viewing Background Processes You can view the details of progress of jobs executed by the background processes in the System Monitor Account is displayed for transactions in each stage of their life cycle You can invoke the Payment and Collections System Monitor screen by typing PCSONMON in the field at the top right corner of the Application tool bar and click on the adjoining arrow button Ct Advanced Search Reset Branch Code EEI Unprocessed Transactions Hold Transactions LHI Rejected Transactions Reversed Transactions zz Deleted Transactions Unauthorized Transactions H Authorized Transactions Transaction Rejected Queue Fj Transaction Re Input Queue Exchange Rate Queue EHI Credit Exception Queue Process Exception Queue Records per page 45 v First _ Previous 4 of 4 Next Last Branch Code Unprocessed Transactions Hold Transactions Rejected Transactions The following details can be maintained in this screen e Source e Hold Transactions e Reversed Transactions e Unauthorized Transactions e Transaction
100. 5 Cancellation No No of Incoming Collection 6 Cancellation No No of Outgoing Collection 7 RSF rejects No No for Incoming Collection oe ORACLE 3 22 2 Transaction Pee Insert SI No Type Validation Update 8 RSF rejects No No for Outgoing Collection 9 Reversal of No No Incoming Collection 10 Reversal of No No Outgoing Collection 11 Return of No No Incoming Collection 12 Return of No No Outgoing Collection 13 Refund of No No Incoming Collection 14 Refund of No No Outgoing Collection 15 Return of No No Reversal of Incoming 16 Return of No No Reversal of Outgoing Processing Based on Sequence Type The different sequence type values are OOFF FRST RCUR and FNAL During transaction processing system checks the following parameters to verify if the mandate details are already maintained e Product e Customer Number e Customer Account e Agreement ID mandate identification e Creditor Scheme ID While processing Incoming pacs 003 the different sequence types and the amendment indicator parameters result into possible scenarios with relation to the mandate details as explained below Per ORACLE 3 22 2 1 3 22 2 2 3 22 2 3 3 22 2 4 Transaction with Sequence Type OOFF When an Incoming Collection is processed with the sequence type OOFF system checks whether the mandate details are m
101. Amount from Product Category If the incoming payment or return of outgoing payment is authorized from the repair queue then system will not post any accounting entries and the transaction will be moved into incoming authorization queue If the transaction is completely authorized from the incoming authorization queue i e if the transaction does not fall on any exception queue then system will process the CRLQ event and pass the following accounting entries Event Account Debit Credit Amount CRLQ Intermediary GL Debit Transaction Amount CRLQ Customer Account Credit Transaction Amount If the contract does not require any manual authorization or release action then both DRLQ and CRLQ event will be processed and following accounting entries are passed Event Account Debit Credit Amount DRLQ Customer Account Debit Transaction Amount DRLQ Intermediary GL Credit Transaction Amount CRLQ Intermediary GL Debit Transaction Amount CRLQ Outgoing Network GL Credit Transaction Amount NOSTRO If the transaction does not fall in to any of the exception queues then both DRLQ CRLQ will be processed and following accounting entries are passed Event Account Debit Credit Amount DRLQ Incoming Network GL NOSTRO Debit Transaction Amount DRLQ Intermediary GL Credit Transaction Amount CRLQ Intermediary GL De
102. Any failures in generation of contracts are logged into the Periodic Exception queue from where you can process them at a later juncture For details about the Periodic Exception Queue refer the chapter titled Processing a Payment or Collection Transaction in this user manual If there are failures in online event processing the contracts are generated notwithstanding the exceptions are logged into the respective exception queue from where you can process them at a later juncture Approval This process identifies all outgoing direct debit transactions satisfying the following conditions and marks the collection status as approved and the contract status as liquidated e Contract status is outstanding e Collection status is pending e Response date is the same as or earlier than the system date Redispatch This process identifies all outgoing direct debit transactions satisfying the following conditions and marks the contract status as liquidated and automatically generates corresponding new transactions for redispatch e Contract status is outstanding e Collection status is rejected e Automatic redispatch is required e Redispatch date is the same as or earlier than the system date For all outgoing request for debit transactions satisfying the following conditions this process marks the contract status as liquidated and automatically generates the corresponding new transactions for r
103. Branch Customer A C Customer Description Product Code Product Description Component Component Description Currency Charge Account Branch Charge Account Number Charge Description Maker Date Time Checker Date Time Mod No Record Status Authorization Status Charge Account Mapping Customer Number Select the number of the customer that is stored for charge mapping Customer Accounts Branch Select the branch of the account that a customer is holding for charges mapping Customer Account Select an account for the customer that is eligible for charge mapping Product code Select the product code that is applicable for charge mapping Component Select the component that is used to levy the charge Currency Select a currency that will be used collecting the charges Charge Account Branch Select the branch where the charge is levied on the customers account Charge Account Charge account is an income GL where the charges collected by the bank will be posted oF ORACLE 6 4 Defining Charge Product Categories Your bank may wish to obtain statistics relating to transaction volumes of a customer for the purpose of extending preferential service charges You may wish to collect such volume statistics separately for transactions involving different product categories When you compute the total business volumes that a customer has given your bank over a certain period you might wish to con
104. C Authorization screen you can view the details of a contract that you wish to authorize However you must first specify the details that are to be rekeyed if any in the Rekey Fields section After this click hold icon to view the contract details The PC Transaction Input screen is opened in view mode with the selected contract details displayed Authorizing contracts To authorize a contract after you have verified it select it in the grid at the top of the screen and click Ok button The contract is marked as authorized To authorize all transactions choose the ALL option at the top of the screen and then click the Ok button All validations that are performed at the time of input or amendment of the contract are performed at the time of authorization to ensure consistency The details relating the authorization time and User ID of the person authorizing the contract are recorded for audit purposes You cannot authorise a transaction in the following cases e the contract has multilevel of authorization pending the same will be done using the Multilevel Authorization Detailed screen e the level of authorization is greater than or equal to N e the Nth or the final level of the users authorisation limit is less than the difference between amount financed and sum of the limits of all the users involved in authorizing a transaction this case holds good when the Cumulative field is checke
105. DF e Excel 10 1 ORACLE 10 1 2 10 2 Output Select the output for the report from the options provided The following options are available e Print select this option if you wish to print the report e View select this option if you wish to view the contents of the report e Spool select this option if you wish to spool the report for further use Printer Specify the name of the printer or select it from the option list provided All the configured printers are displayed in the list This is applicable only if you have specified the output as Print Contents of the report The contents of the report are discussed under the following heads Header The Header section of the report carries the title of the Report information on the User who generated the report the branch code the date and time and the page number of the report Body of the report The actual contents of the report are displayed in this section It is detailed for each report in the subsequent sections of this document Processed Salary Report You can generate salary report using Processed Salary Report screen You can invoke this screen by typing CORPRSAL in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button Processed Salary Report Branch Details Report Date Branch Code Report Date AIl Single Branch Report Format PDF Printer At Client Repor Outpu
106. Debtor Bank When CSM processes Pacs 004 for Outgoing Payment Debtor Bank processes the incoming Pacs 004 and cancellation request is rejected e When original Outgoing Payment is unaffected after Cancellation Camt 056 request Incoming Pacs 004 on original Outgoing Payment is processed as Reject of outgoing payment e The cancellation request can be manually rejected in Payments and Collections Cancellation PCDRCLIN screen or can be rejected by processing Pacs 002 on Camt 056 sent by CSM Case 2 Receipt of Camt 056 from Debtor Bank for Incoming Payments for which Pacs 004 is already sent by Creditor Bank e When CSM processes Camt 056 for Incoming Payment Creditor Bank processes the incoming Camt 056 and reject of Incoming Payment is rejected e When the original Incoming Payment contract is not active cancellation processing on original Incoming Payment fails and the cancellation transaction gets logged into CR queue e In order to respond to received Camt 056 message Reject of Incoming Payment has to be rejected either manually in Payments and Collections Transaction Input aed ORACLE PCDONONL screen by the reject operation available or on receipt of Pacs 002 for Pacs 004 from CSM This rejection process re activates the original Incoming Payment with the contract details as prior to the initial rejection An event RACT will be logged for the original Incoming Payment in the contract events data store
107. Default Activation Date up to which back valued transactions can be allowed Similarly you can indicate the number of calendar days after the Default Activation Date up to which future valued transactions can be allowed During transaction processing you will be allowed to post back future valued transactions up to the specified date in the past or future no check will be done If you have not specified the Back Value Limit Days the System checks against the back value limit days maintained for the branch in the Branch Parameters If the limit in either case is exceeded an override is sought when the transaction is saved For example inn the product preferences you have maintained the Back Value Limit Days as zero and the Future Valued Limit Days as 1 The Booking date of the transaction is 10th June 2003 and the Default Activation Date is Today aN ORACLE elf the activation date is not specified the online screen the Default Activation Date is considered as the activation date which in this case is 10th June 2003 Since the activation date and Default Activation Date are the same the back valued limit days are not exceeded and the transaction is accepted e f you specify 12th June 2003 as the activation date in the online screen the System compares it against the Default Activation Date which is 10th June 2003 In this case the future valued limit days are crossed and an override is sought when the
108. F Details Rule Maker Checker Date Time Mod No Record Status Date Time Authorization Status Product Category Identify the Product Category that you maintain with a unique code and a brief description Product Type You should also specify the product category type A product category can be of either of the following types e Incoming Payment e Outgoing Payment e Outgoing Collection e Incoming Collection e Reject of Incoming Collection e Reject of Outgoing Collection e Recall of Incoming Collection e Recall of Outgoing Collection e Outgoing Request for Debit e Incoming Request for Debit e Reverse of Outgoing collection e Reverse of Incoming collection Category Description Give a brief description of the product here Fa ORACLE 3 26 1 Transfer Type Select the type of transfers that can be processed from the drop down list Following are the option available in the drop down list e Bank Transfers e Customer Transfers e Internal Transfer Only bank transfer types of products can be mapped to product categories defined for bank transfers Book transfer products cannot be mapped to product categories defined for bank transfers Similarly only customer transfer types of outgoing payment products can be mapped to product categories defined for customer transfers Bank transfer is allowed for outgoing payment type of products only EXTERNAL clearing is permitted for such products However
109. F file to the receiver bank The SCF file will contain the below details e Notification of Credit Transfer e Return Positive Answer to CT Recall e Payment Recall e Negative Answer to a CT Recall On receipt of the SCF file if any payment recall request is available in SCF system cancels the incoming payment contracts which is already created using pacs 008 Debit Verification File DVF Messages If Camt 056 recall request is send for the outgoing collection the status of the Camt 056 will be send in DVF file by STEP2 On receipt of the DVF file by the sender bank system will read the DVF file and find the status of the Camt 056 message If the status is rejected then the status will be updated as rejected in the system Debit Notification File DNF Process The messages and bulks sent to the receiving Direct Participants are grouped by Interbank Settlement Date but there is not a one to relationship between the Bulk messages received aS ORACLE by STEP2 and the Bulk messages sent by STEP2 Only pacs 003 Debit requests pacs 002 Rejections and camt 056 Payment Cancellation Request are forwarded in a DNF On receipt of DNF file the receiver bank system will process the new message camt 056 and cancel the already received incoming collection contract which is created using pacs 003 Incoming Cancellation Exceptions Queue PCSCANEX The Incoming Cancellation Exception Queue PCSCANEX is used to log the tran
110. FX occur before the customer leg of tion Incoming Only accounting provided the customer leg is the credit payments leg The system triggers these events automatically if the amount is within the limit specified for the cus tomer Agreement Product Currency Else you will have to trigger them manually a ORACLE CRLQ Credit Entry Liquidation The system triggers the event automatically and initiates the credit entry either to the customer account or to the clearing suspense account based on the type of transaction RJBS Reject prior to Interbank In the case of Outgoing payment this event hap settlement pens prior to the interbank settlement of the outgo ing payment In the case of Outgoing Collection this event is pro cessed before the due date of an outgoing collec tion In the case of Incoming Collection this event is pro cessed before the due date of an incoming collec tion REJT Reject In the case of outgoing payment this event is pro cessed when a rejection message is received after the interbank settlement date of the outgoing pay ment In the case of incoming payment this event is trig gered with in the payment rejection date REVP Reverse This event is triggered on receiving the reverse of Incoming collection transactions AMND Amend This event is triggered whenever an authorized contract for which either DRLQ or CRLQ or DCLG events are not triggered is modi
111. GS Bank transfer Bulk operation is not allowed for this Clicking on Post to Suspense button the system will credit the unsettled GL instead of the customer account The transaction can then be handled operationally from the Unsettle GL This Unsettle GL is picked up from the Product category maintenance based on the product category of the contract Clicking on Details button the system will display the details of the selected contract Aa ORACLE 4 8 2 Viewing Repair Queue Oracle FLEXCUBE allows you to view the details of incoming payments awaiting for repair using Incoming Payment Repair Queue screen To invoke this screen by typing PCSIPRSQ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button amp Incoming Payment Repair Queue E Search Advanced Search Reset 4 Clear All Case Sensitive Contract Reference Product Category Account Entry Reference Product Code N Network Account No Records per page 15 v 10f1 Contract Reference Product Category Exception Queue Account Entry Reference ProductCode Network Detail Repair Reject You can query the record based on the following details e Product Category e Contract Reference Number e Product Code e Customer Account Number e Network e Account Entry Reference Number Clicking on Search button the system will display all the records pertaining to the specified cri
112. Incoming Payment and creates another transaction as Reject of Incoming Payment Reject amp enter Query Contract Reference Product Code Custom Reference Number Type Product Category Transaction Amount Reject Details Reject Code Reject Reason The product category for the reject of incoming payment is maintained in the Product Category of Incoming Payment oo ORACLE 5 Processing a Payment or Collection Transaction 5 1 5 2 5 2 1 Introduction In the Payments and Collections module of Oracle FLEXCUBE a product refers to a specific type of transfer of funds For example you may process payments collections that involve transfer of funds between accounts maintained at your bank You can define this type of internal payment collection as one of the payment collection products at your bank Defining a product makes it easier for you to enter transactions The other advantage of defining a product is that you can define certain general attributes for a product which will default to all contracts processed under it Note Contracts are customer specific A customer could make a payment through your bank lo cal payments or collect payments from debtors through your bank direct debits or re quests for debit Every time you process a transaction you do not have to specify its general attributes since a transaction acquires the attributes defined for the product it involves You can change these
113. Module ssssesseesssesrrssseerrsssreerresrrerrrsses 3 1 3 3 Maintaining Bank Code TypeS essesisseesessrissrrnsesrsrrnnssrinnessnnnadsstennnesttinaneeieiinanna 3 2 3 4 Maintaining Bank Directory cceceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeseeeaeeeeeseeeaaeeeeneeaaeees 3 3 3 4 1 Specifying UDF Details essei riian iin riai EEEE Ea EAE 3 6 3 5 Maintaining Clearing Network Details ccc ccceeeeeeeeeeeeenneeeeeeeenaeeeeeeenaeeeeeeeaaes 3 6 3 5 1 Specifying the UDF Detalls ccccccsecceccenteeeeeeenteeeeeeenneeeeseenaeeeeeseaaes 3 10 3 5 2 Maintaining Redirection Details for a Bank ccccccccctteeeeeeenteeeeeenenaees 3 10 3 6 Maintaining Clearing Network Qualifier Details 2 0 0 0 eceeeeeeeeeeeeeeeenteeeeeeenaees 3 12 3 7 Maintaining Network Calendar ccccccccceeeeeeeeeeenceeeeeeeeaeeeeeeeaeeeeeeenaeeeeesenaaes 3 12 3 8 Maintaining Purpose Code 20 0 eeeeceeeeeeeeeeeenneeeeeeeeaaeeeeeeeaaeeeeeeeenaeeeeseenaeeeeeeseaes 3 13 3 9 Modifying Window Period Information cccceceeeeeeeeeeeeeeeeeenteeeeeeeeneeeeeeeenaees 3 14 3 10 Maintaining Redirection Details for an ACCOUNL ceeeeeeeeeeeeeteeeeeeenteeeeeeeaees 3 16 3 11 Maintaining Beneficiary Accounts for Counterparty Bank ceceeeeeeeeeenteees 3 17 3 12 Maintaining P2P Beneficiary Details eee cence eeeeeneeeeeeeeeteeeeeeenaeeeeeeeenaes 3 19 3 13 Viewing P2P Beneficiary Details 20 0 0 eee eeeneeeeeeeeenaeeeseeeeaeeeseeetaeee
114. ORACLE 8 11 8 12 8 13 Notifying for Split Event You can view the notifications of successful processing of DRLQ and CRLQ event through the external system In case of split event processing where debit and credit leg has different value dates the notification is generated for both debit as well as credit leg of payment processing Notification is generated only if one of the accounting entries has a customer account If both debit as well as credit is between a GL and Nostro account then a notification is not generated Notifying for Reversal of Payment You can view the reversal of payment request notification through the external system This notification is generated when the contract is reversed that is the status of the contract becomes V Notifying on Consolidation of Contract You can view notifications relating to consolidation of contracts through the external system The notification is generated for the consolidated contract status where in only the customer account processing details are shared and beneficiary details are Null Notifications of Rejected Status of Payment Reversal of Payment and Split Events are suppressed if the contract is a consolidated contract a ORACLE 9 Annexure A Accounting Entries and Advices 9 1 Events for the Payments and Collections Module The following are the events defined for the PC module Event Code Event Description Remarks
115. ORACLE Clicking on Reverse button you can reverse the selected contract s You can also select multiple contracts and reverse them in bulk Clicking on Details button the system will display the details of the selected contract 4 4 Viewing Level 2 Authorization A2 Details You can view the Level 2 Authorization A2 details using the Payments amp Collections Auth2 Queue screen To invoke this screen by typing PCSAUTQ2 in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Authorizer 2 Queue I Search t Advanced Search 9 Reset 4 Clear All Case Sensitive Contract Reference No PE Product Category Account Entry Reference Product Code Network Fe Customer Account No Branch 3 Records per page 15 v 10f1 iT Contract Reference No Product Category Account Entry Reference ProductCode Network Customer Bankcode Account Branch Customer Accoun Detail Reverse Authorize You can query the record based on the following details Product Category Contract Reference Number Product Code Customer Account Number Network Account Entry Reference Number Clicking on Search button the system will display all the records pertaining to the specified criteria Double clicking on any of the records the system will display the record details Clicking on Authorize button you can authorize the contract s and set it for dispat
116. ORACLE Payments and Collections User Guide Oracle FLEXCUBE Universal Banking Release 12 0 3 0 0 Part No E53393 01 April 2014 Payments and Collections User Guide April 2014 Oracle Financial Services Software Limited Oracle Park Off Western Express Highway Goregaon East Mumbai Maharashtra 400 063 India Worldwide Inquiries Phone 91 22 6718 3000 Fax 91 22 6718 3001 www oracle com financialservices Copyright 2007 2014 Oracle and or its affiliates All rights reserved Oracle and Java are registered trademarks of Oracle and or its affiliates Other names may be trademarks of their respective owners U S GOVERNMENT END USERS Oracle programs including any operating system integrated software any programs installed on the hardware and or documentation delivered to U S Government end users are commercial computer software pursuant to the applicable Federal Acquisition Regulation and agency specific supplemental regulations As such use duplication disclosure modification and adaptation of the programs including any operating system integrated software any programs installed on the hardware and or documentation shall be subject to license terms and license restrictions applicable to the programs No other rights are granted to the U S Government 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
117. PC Transaction Input main screen based on the preferences assigned to the product category of the transaction the contract User Defined Fields are displayed in the UDF tab in the screen and you can specify the values for these fields which are applicable for the contract oo ORACLE You can execute queries on the user defined fields and select specific records based on the user defined fields Transaction Input aes H save lt i Hold Product Category Contract Reference Collection Type Product Code bl Custom Reference RFD Type Source Reference Product Type Network bal Main Transaction Details Collection Details Party Details Message Detaiis ag UDF Details 10f4 Name Description Split Details Events Charge Status Project Details Duplication Details MIS Tax Input By Date Time Authorized By Date Time Contract Status Authorization Status You can maintain the following details Field Name and Description System displays the name and description of the UDF 5 2 8 Specifying Split and MIS Details Click the Split Details button to specify multiple debit credit accounts for the transaction so that the Split Details screen can be viewed Only leaf GL transactions involving local currency can be entered in the Split Details screen You can specify the MIS code for each split leg using the MIS button against each split entry The sum of the amounts spe
118. Payment Amount gt Auth2 Limit amount v Level 2 Authorization Payment Amount gt Release Limit amount v Release the contract Send the Message to Network 4 37 ORACLE The details of amount block processing on different stages Initiation Level 1 Authorization Level 2 Authorization Release are explained as follows If the transaction goes through this workflow On Initiation On completion of Level 1 Authorizatio n On completion of Level 2 Authorization On completion of RELEASE Initiation gt Account is deb Not applicable Not applicable Not applicable ited and amount oe block will not be done Initiation gt Amount will be Amount Block Not applicable Not applicable Level 1 Author blocked on is removed eae account and ization gt Account is Newark debited Initiation gt Amount will be Amount Block Not applicable No action Level 1 Author blocked on is removed account and ization gt Account is Release gt debited Network Initiation gt Amount will be No action Amount Block is Not applicable blocked on removed and Level 1 Author soe ke account Account is deb ization gt A ited Level 2 Author ization gt Network Initiation gt Amount will be No action Amount Block is No action blocked on removed and Level 1 Author ooa account Account is deb iza
119. Payment Details You can indicate any specific details regarding the payment in this section Closing periodic instructions When you close a periodic instruction and subsequently have another user authorize the closure the instruction ceases to generate any transactions in future Maintaining Details for Dispatch File You can define the parameters of dispatch files generated from Oracle FLEXCUBE using Dispatch File Parameters PCDSFPRM screen Dispatch File Parameters H save Network Code az Bank Code Dispatch Type aa Customer Account Service Identification x Maximum Tracers Pale Files Message Bulks No Of Transactions In Bulk Test Mode E F Bulk Message File Format Type x F File Per Transaction Type File Path Maker Date Time Checker Date Time Mod No Record Status Authorization Status You can capture the following details here oot ORACLE Dispatch Type Specify the type of the dispatch The drop down list displays the following details e Network If you choose this you must specify the clearing network code The system will default the Bank Code and the Customer Number as ALL e Bank Code If you choose this you must specify the bank code The system will default the Clearing Network and the Customer Number as ALL e Customer If you choose this you must specify the customer number The system will
120. QT 04 PC SEQT 05 and PC SEQT 06 are available If DD Agreement Required is selected and Debtor Mandate for B2B scheme doesn t exist then the system moves the transaction to Transaction Repair TR Queue If auto reject mapping is configured then system will automatically reject the incoming collection transaction 5 30 2 Restricting Automatic Upload of Mandate e For incoming collections transactions if the DD Agreement Required check box at Customer agreement is checked and when there is no debtor mandate maintained the system automatically populates the mandate details from the incoming collection transaction e For CORE COR1 scheme Mandate upload process will upload debtor mandate even if DD Agreement Required check box at Customer agreement and Restrict Automatic upload of Mandate is unchecked at product level at ORACLE During automatic upload of mandate if unique identification of a particular mandate changes then a new mandate is created with agreement status as Active The agreement status for existing record is updated as Amended Mandate exists check will not be done after the automatic upload of mandate when DD Agreement Required is not setup at Customer Agreement To support the SDD B2B schemes the automatic upload of mandate when debtor mandate is not maintained is driven by the value of the parameter Restrict Automatic upload of Mandate For B2B scheme Rest
121. RACLE PCDMSGMA in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Payments amp Collections Message Mapping Maintenance EL New Enter Query Message Type Product Category Source Code Station Id Network Id Payment Type Default Message Mapping Detail Tag Value Description Line Number Field Names Input By Authorized By Modification Date Time Date Time Number W Authorized E Open In the Payment Type select the Payment type from the adjoining option list Once you select the Payment Type and click Default button the field mapping for the selected Payment Type is done However you can change the field mapping after it is defaulted Note System does not validate the default type and product product category type This mapping enables the STP process to interpret the CPG fields in uploaded incoming payment messages and resolve the tags into a PC contract in the system The list of fields supported as a part of the instruments transaction will be factory shipped in the common payments gateways fields data store Example of an Incoming Message resulting in an outgoing RTGS 1 F01 RTGPDEFFAXXX1111111111 2 0103 CITIGB21XXXXN 3 103 RTP 113 LIYN 108 021104213084001 1 119 STP 4 20 000PRTG033650001 23 CRED 32A 031231EUR1000
122. Recall Days Details e Re dispatch details e DD Agreement Required e Creditor Agreement Required Collection Type For the selected collection product type you have to indicate the collection type The options available are e Direct debit e Request for debit If you capturing the details of Incoming or Outgoing collection product types you must necessarily specify direct debit as the collection type While creating product meant for outgoing and incoming payments you will not be allowed to define product types For outgoing incoming collection products and for Reject of incoming outgoing collection products you can choose either one of the collection types The Direct Debit collection type can be selected for both Customer Transfer and Bank Transfer type of product codes and product categories A counterparty bank code indicates the bank from which funds will be transferred If the counterparty bank code is an indirect participant then the system derives the direct participant based on TARGET 2 directory maintenance and defaults the direct participant as the receiver The message type DIRECT_DEBIT is available to generate MT204 Refer the section titled Validations performed on the Product and Collection Type combination for detailed information on the various validations performed by the system depending on the Product and Collection type combination RFD Type The RFD type indicates the manner in which you
123. Reference Product Category Number Exception Queue Product Code Authorized Contract Status Records per page 15 v 10f1 Contract Reference Account Entry Reference Number Product Category Product Code Exception Queue Contract m Details LBL_EXCEPTIONS Retry In this screen you can maintain the following details Authorization Status a 88 ORACLE e Exception Queue e Contract Reference Number e Product Category e Contract Status e Account Entry Reference NO e Product code To re upload all the contracts click the Retry button If the contracts are successfully uploaded they will no longer be visible in the screen 5 17 Viewing Details of Split Transactions In certain cases you may find it necessary to split an outgoing collection transaction into multiple transactions due to restrictions on the amount of each payment that can be sent over the payment network In the Split Summary screen you can view details of such split transactions by drilling down from the parent transaction to the child transactions You can invoke this screen by typing PCSSPLTS in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Split Summary Query f Search t Advanced Search 9 Reset D Clear All Case Sensitive Contract Reference Network Activation Date Initiation Date Transaction Currency Transaction Amount B
124. Release button you can release the contract s If the contract is released then further processing continues on the transaction wherein the transaction is transmitted to the network This will process the CRLQ event You can select multiple contracts and release them in bulk Clicking on Reverse button you can reverse the selected contract s The system will reverse the accounting entries which were posted in DRLQ event You can also select multiple contracts and reverse them in bulk Clicking on Details button the system will display the details of the selected contract ara ORACLE 4 6 Validations for Product and Collection Type Combinations The system performs various validations during transaction processing based on the Product type and Collection type combination and the various dates that you have specified during product definition These dates include Customer Entry Days Customer Entry Value Days Counterparty Entry Days Counterparty Entry Value Days Dispatch Days Response Days Listed below is a set of validations that you can capture while creating products for specific Product and Collection type combinations Product Collection Set of Validations Type Type Outgoing NA Customer entry days should be less than or equal to coun Payment terparty entry days Customer entry value days should be less than or equal to counterparty entry value days Counterparty entry days should b
125. Required Referral refers to the process of handling customer transactions which force the accounts involved in such a transaction to exceed the overdraft limit Payments and Collections are examples of typical transactions which can force an account to move into overdraft While maintaining the details of a PC product you can indicate whether transactions involving the product need to be considered for referral checks Enabling this option indicates that transactions involving the product needs to be considered for referral If a product is marked for referral the details of transactions resulting in the account involved in the transaction moving into Overdraft will be sent to the Referral Queue Note If a PC transaction breaches the limits the details of all transactions processed during the day will also be moved to the Posted Entries section in the Referral Queue You can choose to accept or reject the transactions The details of the transaction which has breached the limits will be displayed in the Unposted Entries section of the queue For further details on Referrals refer the Processing Referrals in Oracle FLEXCUBE chapter of the Core Entities manual Currency Calendar While processing the contracts if you want the system to use the currency calendar for deriving the processing days instead of the local branch calendar check the Currency ani ORACLE Calendar box This is used when the system has to derive the
126. Rules refer the Charges chapter in the Modularity User Manual os ORACLE 6 2 1 Specifying Parameters for Charge Rule Application You can specify the parameters for charge rule application when building the Charge Class to which you associate the charge rule To invoke this screen type CFDCHGCE in the field at the top right corner of the application toolbar and click the adjoining arrow button Charge Class Maintenance Module List Class Code Description Description Charge Type Third Party Type LT E Net Consideration Debit Credit Ix Add Subtract Swift Qualifier 6 3 Propagation Required Association Event Application Event Liquidation Event Basis Amount Tag Default Charge Rule Default Settlement Currency 7 Default Waiver F Allow Rule Amendment IZ Capitalize E Consider as Discount Discount Basis Amend After Association F Allow Amount Amendment F Accrual Required 7 Amend After Application E Collect LC Advising Charges in Bills Maker Date Time Checker Date Time Mod No Record Status Authorization Status The charge rule specifies the amount to be charged to the customer To recall charges levied on payments and collection transactions are computed at the time of transaction initiation and are liquidated along with the contract The amount tags available for charges on pay
127. Scheme The system displays the tax scheme details Waiver Check this box to indicate waiver details Rule Details Rule The system displays the rule details Basis Component The system displays the basis component details Event The system displays the event details Waiver Check this box to indicate waiver details 5 38 ORACLE Amount Details Value Date The system displays the value date Transaction Date The system displays the transaction date Currency The system displays the currency details Amount The system displays the amount details Event Sequence Number The system displays the ESN details While saving a PC contract for outgoing PC payment the beneficiary bank will be the beneficiary customer If there is no classification for the beneficiary bank then the system will treat the contract as a normal PC contract with no applicability of FATCA This is applicable in case of external clearing contracts also For an incoming PC payment the customer who owns the account being credited will be the beneficiary customer If an incoming collection results in an independent outgoing payment the system will consider FATCA applicability as part of the outgoing payment and not as part of the incoming collection If an incoming collection results in a direct debit then the beneficiary customer will be the bank to which the payment is being sent If the contract is being closed then the
128. Sme ORACLE 57A AABSDE31 59 BENAC 12345 Sender RTGPDEFF Amount 1000 Currency EUR Value Date 31 Dec 2003 AWI AABSDE31 Beneficiary BENAC 12345 Incoming Message from a direct participant for passing funds to Non Addressable In direct participant For a truly incoming message you will need to link tag 57 content to the customer account and sender to the counterparty BIC Example of a truly Incoming Message 1 FO1UBSWGB2LAXXX1111111111 2 0103 CITIGB21XXXXN 3 103 RTP 113 LIYN 108 0211042130840011 119 STP 4 20 000PRTG033650001 23 CRED 32A 031231EUR1000 57A AABSDE31 59 BENAC 12345 Sender UBSWGB2L Non Addressable Indirect Participant AABSDE31 Amount 1000 Currency EUR Value Date 31 Dec 2003 Beneficiary BENAC 12345 For SEPA transactions the mapping between Common Payment Gateway Fields and PC will be as follows e SEPA Credit Transfer CPG PC mapping e SEPA Direct Debits CPG PC mapping ae ORACLE 3 36 3 Maintaining the Unsettled Payment Account or GL Details in regard to maintaining the unsettled Payment Account or GL are explained below 3 36 3 1 Incoming Payments Processing an incoming payment message could be aborted due to specific reasons for instance the beneficiary of the payment not being resolved You can ensure that such aborted incoming payments are processed using an unsettled payment account or a GL You can spe
129. Specify account number that is used in the rejection leg While creating products which cater to outbound DDs you can indicate whether the rejects from the outbound DDs should be processed before the response days In such as case you will need to identify the reject suspense account which has to replace the customer leg as a PC product preference Note Note the Following Ifan outbound DD is rejected before the response days the loans payment can also be reversed along with the reject processing You can choose to reverse the loan payment for contracts involving a product by enabling the Reverse LD Payment preference in the LD Product Preferences screen This reversal is supported only if there is a single DD generated for the schedule Reversal Fields Allowed Reversal Days Specify a value for the field to validate on the time window for the reversal operation for B2B CORE and COR1 products The field is applicable if the product types are Outgoing Collection and Incoming Collection Configure the field as 5 for B2B type of product ats ORACLE Reversal Calendar Basis Specify a value for the field The field is enabled and mandatory if Allowed Reversal Days field is defined It has two optional values e Branch Calendar The system considers only the current branch working days to calculate the number of days allowed for reversal e Currency Calendar The system considers only the currenc
130. Specify the following mandate cancellation charge details Source Code Source Code Specify the source code for which the mandate cancellation charges are applicable The adjoining option list displays all the valid source codes maintained in the system You can choose the appropriate one Here you can maintain mandate cancellation charges applicable to specific external system channel If the cancellation is from Oracle FLEXCUBE specify the source code as FLEXCUBE Branch Code Branch Code Specify the branch code for which mandate cancellation charges are applicable The adjoining option list displays all the valid branch codes maintained in the system You can choose the appropriate one You can maintain mandate cancellation charges for a Branch Code Source Code combination Charges Income GL Specify the income GL into which the charges should be credited The adjoining option list displays all the valid income GL s maintained in the system You can choose the appropriate one Transaction Code Specify the transaction code for passing accounting entries The adjoining option list displays all the valid transaction codes maintained in the system You can choose the appropriate one Charge Currency Specify the currency of the charge amount The adjoining option list displays all a list of currencies maintained in the system You can choose the appropriate one Charge Amount Specify the charge amount that should be coll
131. Start Time Specify the contract Level 2 Auth start time in hours and minutes for Full Day Auth2 End Time Specify the contract Level 2 Auth end time in hours and minutes for Full Day Release Start Time Specify the contract Release start time in hours and minutes for Full Day os ORACLE 3 10 Release End Time Specify the contract Release end time in hours and minutes for Full Day Clicking on the Default button the system will default the window period information for the given product If the current process date is Full Day then system will default the Full Day window period information else if the Process Date is Half Day then system will default the Half Day window period information Maintaining Redirection Details for an Account Just as you redirect transactions from one bank to another so also on occasions transactions involving a specific account maintained in Oracle FLEXCUBE may have to be redirected to another valid account maintained in Oracle FLEXCUBE In the Account Redirection Maintenance screen you can maintain the redirection details for an account You can invoke this screen by typing PCDACARE in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Accouyt Redirection Maintenance E New amp Enter Query Account Redirections From Account Redirections To Account Number Redirected Account Number Customer Name Redirected Cu
132. Status In this screen you can to maintain the following details Bank Code Every bank with which you have a relationship for processing local payments direct debits and requests for debit should be identified by a unique code The clearing bank will be referred by this code throughout the system Bank Code Type You can select the type of identification code being specified for the bank in the directory For instance it could be SWIFT BIC BLZ IFSC and so on The drop down list contains the bank code types maintained in the system and you can choose the appropriate code type Bank Name Specify the name of the bank maintained in the directory City Specify the name of the city of the bank in the bank directory ORACLE Address In addition to the bank code you can also capture the name of the bank and the address for correspondence Country Specify the country of the bank in bank directory This adjoining option list displays all valid country codes maintained in the system You can choose the appropriate one Note The country information is captured to enable Mantas to analyse the transactions for pos sible money laundering activities For more details on Mantas refer Mantas interface document National Clearing Code Enter the national clearing code to be used in case the system is not able to resolve the TARGET 2 participant based on the bank code TARGET 2 is a high value Euro Payment clearing sy
133. System will not validate on local Instrument value and Local instrument type If product type is Incoming Collection STP rule and Setup are done in such a way that value of Local Instrument value is considered in addition to the existing parameters to resolve in to the product with collection scheme type as COR1 CORE and B2B Anew static data for the ISO Code FFO5 with description as Invalid Local Instrument Code will be released Anew static data for an error code PC SVV 09K will be released and used if Debtor mandate not found for shorter time cycle transactions A new static data for an error code PC SVV O9L will be released and used if Creditor mandate not found for shorter time cycle transactions os ORACLE During incoming Collection Processing System checks for the Debtor Mandate created for shorter time cycle transactions COR7 if it is not found then it raises an error FFO5 The error code PC SVV O9K is mapped with ISO Code FFO5 in Payments amp Collections Auto Reject Mapping Maintenance screen PCDERRCD in order to reject the Incoming Collection Transaction automatically when debtor mandate not found If auto reject mapping is not configured then incoming collection transaction will be moved into Transaction Repair TR queue During Outgoing Collection Processing System checks for the creditor mandate created for shorter time cycle transactions
134. Type as Allowed in Debtor Direct Debit Instructions If Incoming Collection transaction for a Debtor does not match with these maintained data then the system moves the transaction to Transaction Repair TR queue If restriction type is Allowed and Creditor ID Scheme ID Mandate ID and Creditor IBAN are not maintained then the system moves all incoming collections for the Debtor accounts to Transaction Repair TR queue Static data for error code PC INDD 12 is available and auto rejection can be configured for this error code If auto rejection is configured then Incoming Collection transaction will be automatically rejected when does not match with white list The system rejects the transaction in following scenarios e If any of the incoming collection transaction s Creditor Scheme ID does not match with maintained value e If any of the incoming collection transaction s Creditor IBAN does not match with maintained value e If any of the incoming collection transaction s Creditor Scheme ID or Creditor IBAN not matches with the maintained value e If any of the incoming collection transaction s Creditor Scheme ID and Mandate ID are not matches with the maintained values e If any of the incoming collection transaction s Creditor Scheme ID and Mandate ID or Creditor IBAN are not matches with the maintained values The creditor business code in Creditor ID Scheme ID are not considered while checking for Bla
135. VV 090 with description as Maximum Amount per Calendar Year exceeded is available e Auto rejection for the above error is configured and the incoming transaction is rejected automatically e Debtor bank originated R transactions such as Pre settlement Reject and Post settlement Reject on incoming collection transactions will decrement the transaction amount in Utilized Amount for Calendar Year field on receipt of the incoming collection transaction e Debtor originated R transactions such as Pre settlement Reject and Post settlement Reject on incoming collection transactions will not decrement the transaction amount in Utilized Amount for Calendar Year field e All Cancellations of incoming collections would decrement the transaction amount in Utilized Amount for Calendar Year field on receipt of the incoming collection transaction e Reversal of incoming collection will not decrement the transaction amount in Utilized Amount for Calendar Year field e For CORE and COR1 collections scheme types Debtor originated recall Refund transactions will not decrement the transaction amount in Utilized Amount for Calendar Year field e The R transaction will decrement the Utilized Amount for Calendar Year only if the R transaction is received in the same calendar year as the due date of original collection If the R transaction is received in a different calendar year then it will not decrement the Utilized Amou
136. Y TFR_AMT CRLQ DR INTSUSPAY TFR_AMT CRLQ CR CLGSUSPAY TFR_AMT The following accounting entries can be defined for Reject of Outgoing Payment for which the P2P payment type is P2P final payment Event DR CR Accounting Role Amount Tag DRLQ DR CLGSUSREC TFR_AMT DRLQ CR INTSUSREC TFR_AMT CRLQ DR INTSUSREC TFR_AMT 9 10 ORACLE CRLQ CR CUSTOMER TFR_AMT The CRLQ event of the PC contracts where FATCA withholding has been determined will have the following entries Event DR CR Amount Type Account CRLQ DR Payment Amount Suspense GL Consolidated CRLQ CR Payment Amount Settlement Consolidated Account GL CRLQ DR FATCA Tax Settlement Account GL CRLQ CR FATCA Tax Tax GL Escrow GL DRLQ for Outgoing Collection Reject of Outgoing Collection and Recall of Incoming Collection products The following accounting entries can be defined for outgoing collection reject of outgoing collection and recall of incoming collection products Event Code Accounting Role Amount Tag Dr Cr DRLQ CLGSUSREC TFR_AMT Debit INTSUSPAY TFR_AMT Credit CRLQ INTSUSPAY TFR_AMT Debit BENEFICIARY TFR_AMT Credit DRLQ for Incoming Collection Reject of Incoming Collection and Recall of Outgoing Collection products The following accounting entries can be defined for incoming collection reject of incoming collection and reca
137. Yes No 3 101 ORACLE 3 37 3 3 37 4 Maintaining Local Clearing Details and Cover Details for Settlement Messages For local currency transactions for which the payment instructions are to be generated through the Payments module you can specify the following settlement details e Whether the payment is to be effected through messaging or via the local clearing network e Whether a cover is required for the payment e Whether the cover must be available through messaging or through the local clearing network You can specify these details in the Settlements Message Details screen In the Message Details tab you can indicate the payment mode and the cover details If you indicate payment through the local clearing network or cover through the local clearing network you must indicate the external counterparty details in the Local Clearing tab in the Settlement Message Details screen For processing direct debits on loans you will also need to capture the Agreement ID of the counterparty in order to facilitate a cross referencing between the Loans Payment and the Direct Debit instruction when a reversal of payment is carried out due to rejection of the outbound DD The post accounting option is defaulted from the Settlements to Payment Product and UDF Mapping screen If enabled this indicates that accounting entries maintained for the PC product should be posted for the PC contract initiated for Clear
138. _Instrument_Value needs to be considered in addition to the existing parameters to resolve into product with collection scheme type as B2B e During processing if Local Instrument Value is B2B and if Creditor s account is individual customer s account then the system displays an error and transaction is moved into Transaction Repair TR queue Debtor Bank Manual Creation For manual creation of Incoming Collection collection scheme type and customer type are validated with respect to Incoming Collection product File Processing e For Incoming Collection file processing STP rule is setup in such a way that Local_Instrument_Value is considered in addition to the existing parameters to resolve in product with collection scheme type as B2B e During processing if Local Instrument Value is B2B and if Debtor s account is individual customer s account then system will raise an error e If the debtor account is Joint account then the system checks the customer type of the main customer e The system rejects the above by default with the error code PC SVV 09M and ISO reject code AC13 e If auto reject mapping is not configured then the system moves the incoming collection transaction into Transaction Repair TR queue e Static data for ISO Reject code is AC13 Note The message generated from DP to CSM is compliant with EBA STEP2 SEPA rule book and the message generated from DP to IP is ISO standard complian
139. account maintenance screen Account in LCF You can specify the customer account in Local Clearing Format in the A C LCF field Customer Name The name of the customer who is linked to the customer account will be defaulted here when you save the PC transaction The name is maintained in the customer account maintenance screen Customer Number The system defaults the customer number of the customer linked to the PC transaction Bank Code You can enter the bank code and the account in LCF local clearing format for the transaction The option list displays the Bank Code Name Bank Code Type and City for each bank in the list The Bank Code Name and City details are displayed on the Transaction Input screen when you select the bank code Bank Name The system displays the name of the bank Bank Address 1 Specify the address of the customer s bank name specified 4 ORACLE Bank Address 2 Specify the address of the customer s bank name specified Note The fields Bank Name Bank Address 1 and 2 are not sent out in the outgoing Pacs 008 001 02 message These fields available at common payment message browser are mapped to fields at Payments and Collections Transaction Input for the new fields Branch Name The system displays the branch name of the bank Clearing Branch The clearing branch for the specified customer bank code is displayed in this field Bank City The system displays the bank city Add
140. account will be debited for outgoing transfers and credited for incoming transfers If you do not input a date here it will be derived from the activation date by adding the working days to the value of customer entry days specified for the product The values will be used based on the cutoff status of the transaction Customer Entry Value Date This indicates the value date of the debit entry for outgoing transfers and credit entry for incoming transfers If you do not input a date it will be derived from the activation date by adding the working days to the value of customer entry value days specified for the product The values will be used based on the cutoff status of the transaction Counterparty Entry Date This indicates the date on which the counterparty account will be credited for outgoing transfers and debited for incoming transfers If you do not input a date it will be derived from the activation date by adding the working days to the value of counterparty entry days specified for the product The pre post cutoff values will be used based on the cutoff status of the transaction Counterparty Entry Value Date This indicates the value date of the credit entry for outgoing transfers and debit entry for incoming transfers If you do not input a date it will be derived from the activation date by adding the working days to the value of counterparty entry value days specified for the product The pre post cutoff values will be used bas
141. action If any of the above criteria is not met then the system displays an appropriate error message The following validations and processes are involved FX contract can be linked only for Payment transactions Linking FX contract to PC transaction is optional for cross currency transaction If linked then the system considers the FX contract exchange rate as the exchange rate for the PC transaction During creation and modification of the PC transaction FX Contract can be linked to PC transaction FX contract will not be linked to a PC transaction with Auto Exchange Rate checkbox checked at PC product level While saving a PC Transaction the system triggers LINK event in FX to decrease the available utilization amount If the FX linked PC Transaction is deleted before authorization then the system deletes the existing LINK event in FX to increase the unutilized amount If the FX linked PC Transaction is modified before authorization then if FX linkage is removed the system deletes the existing LINK event in FX to increase the unutilized amount FX linkage is attached the LINK event is created in FX to decrease the unutilized amount The transaction amount is increased the system validates if the outstanding amount of the linked FX forward contract would cover the increased amount If it is then the system deletes the existing LINK event FX with old amount and increases the unutilized amount This is followe
142. action can be deleted Amendable Fields For a combination of customer source code and product you can also specify a list of fields that can be amended on upload This implies that on upload the transaction details corresponding to the fields you specify here can be amended before the transaction is processed You can amend the following fields e Customer Account e Activation Date e Transaction Amount e Counterparty Bank Code e Counterparty Account Local Clearing Format e Counterparty Name Days Message Retention Days The number of working days calculated from the initiation date of the transaction for which the messages need to be retained in the system As stated earlier Oracle FLEXCUBE has the following inbuilt sources for which you need to maintain the corresponding preferences Upload Source Product category Manual Book Incoming Collection Reject Of Outgoing Collection Recall of Outgoing Collection Manual Redispatch Outgoing Collection Manual Approval Approval of Incoming Collection RFD Manual Reject Reject Of Incoming Collection Manual Recall Recall of Incoming Collection DD oat ORACLE 3 18 Capturing Customer Agreements Prior to processing payment and collection transactions you need to capture the details of the agreement between your bank and the customer involved in the transaction The agreement details maintained in the Customer Agreement Mainten
143. age Check this box to indicate that the message bulk should be created with many transactions File Per Transaction Type Check this box if you want the system to generate one file for each transaction type If this option is not selected then one file is created with the following transaction type in the same order e SCT Credit Transfer Message Bulk pacs 008 Payment Return pacs 004 e SDD Direct Debit Instructions pacs 008 Rejects pacs 002 Reversals pacs 007 Return Refunds pacs 004 If this option is selected then one file is created for each transaction type 5 25 12 Generating Dispatch File Once the SCT and SDD messages are processed in Oracle FLEXCUBE the system needs to generate and dispatch the handoff files You can generate the dispatch file using the Dispatch File Generation screen You can invoke this screen by typing PCDIFGEN in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Dispatch File Generation amp Execute Query H Clearing Network Service Identifier aaa Bank Code Account Number Dispatch Type L H Reference Number Network Description Message Exchange Pattern Cheque By Cheque Bank To Bank al fs You can capture the following details in this screen oe ORACLE 5 26 Dispatch Type Select the option from the drop down list to indicate to whom you w
144. ail and CSM Reject Reference Number at contract level with the received reject code reject description and reject reference number from Pacs 002 Will also reactivate the Original Incoming Collection by processing Reactivation Event e The reactivation event for the Original Incoming Collection will revert the status of the incoming Collection prior to recall event processing RECL This enables incoming collection to be recalled further 5 28 3 Processing Re activation Event 5 29 You can process the reactivation event to reactivate the contract from further processing after it has been rejected cancelled recalled or reversed This is a system driven event and triggered when rejection is received for any of the following operations e Rejection of incoming payment e Approval of Cancellation of incoming payment e Cancellation of Outgoing collection e Reversal of outgoing collection e Pre settlement Rejection of Incoming Collection e Post settlement Rejection of Incoming Collection e Recall or Refund of Incoming Collection This event will revert the changes that were done as part of the post settlement rejection REJT pre settlement rejection RJBS reversal REVP and recall RECL event processing Black List and White List of Creditors Black List You can restrict allow incoming collection transaction to be processed based on Creditor Scheme ID Creditor IBAN and combination of Mandate ID and Creditor Schem
145. ails Counterparty Name Address Line 1 Address Line 2 Address Line 3 Address Line 4 Address Line 5 Sumame Father Name Telephone Email id Facebook ID ID Value Id Bicld Scheme Name Type Date Of Birth E Scheme Name City Of Birth Issuer Country Of Birth Maker Date Time Mod No Checker Date Time Record Status Authorization Status Counterparty Account Bank Code You need to specify the Bank Code of the Counterparty Account from the option list provided The Bank Name will be displayed alongside Account Number You need to specify the Account Number of the counterparty account This along with the Bank Code will be uniquely identified in the system If you have checked the option IBAN Check Required at clearing network level the system validates IBAN for the counterparty account for outgoing payments and incoming collections However the system does not validate the account number that you specify here You need to specify the correct account number for the counterparty Bank Name The system displays the name of the bank ou ORACLE Counterparty Details Counterparty Name You need to specify the counterparty name for the local payment transaction Address Line 2 3 4 and 5 Specify the address of the counterparty You can maintain up to five lines of address information Surname Specify the surname of the counterparty Fathers Name Specify the fathers name of the counterpart
146. ained happens to be two the Response Date will be 03 April 2003 Scenario Il If you have selected Working as the Response Days Basis the Response Date is computed as the Next Working Date based on the Response Days Account Type Select the type of account that is used in the rejection leg You can select any one of the following options e Account e GL Redispatch Details Redispatch Required You have the option of re despatch required on the outgoing DD RFDs involving a product If you choose this option you will have to indicate whether such DDs and RFDs need to be re dispatched automatically or manually ae ORACLE Auto Redispatch If you indicate that rejected DDs and RFDs need to be re dispatched automatically you have to specify the maximum number of tries for a rejected outgoing DD RFD Additionally you will also have to specify the number of working days past the activation date after which the system will query for a rejected outgoing DD RFD and re dispatch automatically Count Count determines the number of times a re dispatch should take place Days Days determine the number of days in which the re dispatch should be done Recall Days Days As part of specifying the preferences for Recall Days you have to specify the maximum number of days past the activation date within which the transaction entered using this product can be recalled Basis You will also need to specify whether the basis fo
147. aintained in the Payments amp Collections Debtor DD Agreements screen If the mandate details are not maintained system inserts a record into the mandate details and updates Mandate Status to Used In this case the mandate details are obtained from the transaction details If a mandate record with the combination Product Code Customer Account Agreement Id and Creditor Scheme Id exists along with any Mandate Status then system generates pacs 002 reject message which is sent to SIBS Payment Status is updated as Rejected If Incoming Collection is processed successfully then Amendment Reason is updated with the value PACSOO3 and the Mandate Status is updated as Used During subsequent processing of the same Incoming Collection if the Incoming Collection is rejected due to reasons other than mandate validation failure the status of the mandate record will remain unchanged Transaction with Sequence Type FRST When an Incoming Collection is processed with the sequence type FRST system checks whether the mandate details are maintained in the Payments amp Collections Debtor DD Agreements screen If the mandate details are not maintained system inserts a record into the mandate details and updates Mandate Status to Active and Amendment Reason to PACSO003 If a mandate record with the combination Product Code Customer Account Agreement Id and Creditor Scheme Id exists along with any Mand
148. alculated as the difference between the amount of the rejected outgoing collection transaction that has been uploaded and the amount of the original transaction This specification is applicable only for outgoing collection transaction products The accounting entries while collecting third party charges are as follows Accounting Role Amount Tag Debit Credit Indicator CUSTOMER THIRD_PARTY_CHG Debit CLGSUSPENSE THIRD_PARTY_CHG Credit 4 20 ORACLE Note If the transaction amount of the reject contract is less than the original contract the contract is sent to the Processing Exception queue This is also true for uploaded reject contracts Allow Third Party Charge This field is checked when the product type is Recall of Outgoing Collection or Reject of Outgoing Payment Insert the following accounting roles for Reject of Outgoing Payment SI No Acraunting Amount Tag Dr Cr Role 1 CHARGE TFR_AMT Debit ACC 2 CLGSUS TFR_AMT Credit REC Charge Customer Statistics Check this option to indicate that the customer statistics is charged for collection of charge data for transactions using the product Charge Account Statistics Check this option to indicate that the account statistics is charged for collection of charge data for transactions using the product Charge Category The charge category indicates the category under which charge related transaction details
149. all valid projects maintained in the system You can select the appropriate one Input to this field is mandatory If you specify the Unit ID the system will display the corresponding project name here Unit Payment Indicate whether the transaction is a unit payment or not by choosing the appropriate value from the adjoining drop down list The following values are available e Yes e No Unit ID Specify the unit ID of the project This field will be enabled only if you have selected Yes against Unit Payment The adjoining option list displays all unit IDs along with the unit holder names corresponding to the project name chosen You can select the appropriate one Deposit Slip Number Specify the deposit slip number for the payment Viewing a Tax Scheme You can view a tax scheme defined in the tax Click Tax button in the Payments and Collection Transaction Input screen to invoke the Tax screen oar ORACLE You can compute the tax based upon the tax rule and linked amount from PC contract and liquidate the tax in the appropriate event Tax Details Contract Reference Tax Scheme waiver Rule Details 1 Of 1 3 F Rule Basis Component Event Waiver Amount Details 10f1 E Value Date x Transaction Date Currency Amount Event Sequence Number You can specify the following details Contract Reference The system displays the contract reference number Tax
150. an be 4 characters Account Indicates the customer account used in the transaction Maximum length can be 35 characters Transaction Amount Indicate the amount of the original transaction Maximum amount can be 999999999999999 99 Transaction Currency Indicates the currency used in the original transaction Maximum length can be 3 characters Error Code Indicates the error faced during cancellation processing Maximum length can be 11 characters Error Description A display field to describe the error faced during cancellation processing Exception Queue Indicates the status of exception queue Maximum length can be 2 characters Click Retry button to retry the cancellation processing Once the transaction is corrected from the error cause cancellation processing can be retried by using Retry button Retry option will execute the cancellation processing on the selected transaction On successful processing the exception queue status of a transaction will be changed to Viewing SEPA Payment Cancellation Summary Details You can view the summary details of a SEPA Payment Cancellation in SEPA Payment Cancellation Summary screen You can invoke this screen by typing PCSRCLIN in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button oe ORACLE Summary SEPA Payment Cancellation E search Ct Advanced Search Reset Y Clear All Case Sensitive Authorization S
151. ance screen are for a product customer and account combination You can invoke this screen by typing PCDCLAGT in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Customer Agreement Maintenance X H Save General Information Mandatory Fields Cutoff Time Product azl E Creditor ID Scheme ID Hour Required Minute Product Description fe El Agreement Id Invoice Split Required Collection Scheme Type X _ El Invoice Split Required Customer Customer Name Account Branch Account az Currency Customer Days Customer Entry Consolidation Redispatch Details Entry Value Days E At Product Level Required E Redispatch Required Entry Days Consolidation Limit E Auto Redispatch F Currency Calendar Redispatch Count Redispatch Days Direct Debit Agreement Fields Response Details Other Details E DD Agreement Required E Automatic Response Creditor ID Scheme ID az F Counterparty Bank Code E Response Advice Required E Counter Party Account E ASCII Handoff Required General Ledger o Number E Collection Statement Description Creditor ID Scheme ID Required Debio in _ Requir ed Response Advice Basis C H gory E Agreement Identification Description al Fields Maker Date Time Mod No Checker Date Time Record Status Authorization Status The following agreement details can be maintained General Information Product You can select the product for which the a
152. and Collections Creditors details maintenance PCDCREID If the value is not available in the list of values During save of the agreement FLEXCUBE maintains a record for the entered Creditor ID in Payments and Collections Creditor Details Maintenance While processing contracts for collection transaction the system will validate Creditor Scheme Identifier for the space between the positions 5 and 7 in Creditor Scheme Identifier If there are spaces then the system displays an error during manual contract creation in Payment amp Collection Transaction Input Then the incoming messages will be moved to Transaction Repair queue Positions 5 to 7 contain the creditor business code When the creditor business code is not used then value is set to ZZZ The creditor business code is not considered while checking for existence of the agreement Description The system displays a description of the creditor identification specified Creditor Account Specify the creditor account in Local Clearing Format LCF Banks within the same local clearing network will be assigned unique account numbers based on the local clearing format specific to the network Bank code Select the bank of the counterparty creditor Bank Name Specify the name of the counterparty bank Date of Signature Specify the date of signature from the adjoining calendar Suffix Specify the suffix for the creditor Debtor IBAN Specify International Bank
153. anization Identification or Private Identification If the Scheme Name Type is P then you can enter the value for the field Counterparty Date of Birth Specify the date of birth of the Counterparty City of Birth Specify the city of birth of the counterparty This is enabled and is mandatory if you have selected identification type as Date and Place of birth Country of Birth Select the country of birth of the counterparty from the option list This is enabled and is mandatory if you have selected the identification type as Date and place of birth Country Specify the country of residence of the counter party This adjoining option list displays all valid country codes maintained in the system You can choose the appropriate one Note The country information is captured to enable Mantas to analyse the transactions for pos sible money laundering activities For more details on Mantas refer Mantas interface document Periodicity Tab You can capture the following details First Generation Date Specify the date of first generation of the transaction This date would be the activation date for the transaction Next Generation Date When you first maintain periodic instructions for an outgoing collection transaction the next generation date is considered by default to be the same as the first generation date that you specified eS ORACLE End Date You can specify an end date for generation of transacti
154. ansactions will not be tracked through the different statuses Dispatch Media Oracle FLEXCUBE provides the facility to process outgoing payment orders for the bank s clients through the Payments and Collections module If the beneficiary is a client of an external bank Oracle FLEXCUBE generates the requisite message to be sent to the clearing network When you create a payments and collections product for processing outgoing payments you must indicate the medium through which the outgoing payment would be dispatched in the PC Product Preferences screen The dispatch medium that you specify could be either e Oracle FLEXCUBEOR e INTERFACE in which case the dispatch will be done through the Oracle FLEXCUBE Interface system Dispatch media should be selected as INTERFACE for SEPA products Dispatch Days Specifying the dispatch days refer to the number of working days to be added to the activation date to determine the date of dispatch to the Clearing Server For outgoing transactions the Dispatch Date should be later than or the same as the Activation Date Transactions received before the cutoff time you have specified will be processed according to your Pre cutoff Dipatch Days specification for the product Transactions received after the cutoff time specified for the product will be processed only if you have enabled the Allow Post Cut off option for the product Such transactions will be posted with the Activation D
155. ant Customer Address1 and 2 Specify the address of the customer participating in the indirect transaction Indirect participant Country Specify the country of the customer participating in the indirect transaction Indirect Participant BIC ID Specify the Bank Identification Code for the Indirect Participant BIC ID is only applicable for Organizational identification details Indirect Participant Scheme Name Type Select the Identification Scheme Type of the Indirect Participant from the drop down list The valid values are e C Code e P Proprietary Indirect Participant Scheme Name If Scheme Name type is C then select the Scheme Name from the values mentioned in the LOV depending on Organization Identification or Private Identification met ORACLE If Scheme Name type is P then enter the Scheme Name your own Indirect Participant Date of Birth Specify the Date Of Birth of the Indirect Participant Input the Date of Birth is only for Private identification Identification Value Specify the identification value This is optional Issuer Specify the Identification Issuer of the customer This is an optional field This is applicable for Organization identification as Proprietary Identification or Private Identification City of Birth Specify the city of birth of the Customer This will be enabled and is mandatory for identification type as Date and place of birth Country of Birth Select the country of birth of
156. ant to send the generated file It can be send to the CSM or another bank Files are sent to bank only for messages sent from direct participant to indirect participant or indirect participant to direct participant The options available in the drop down are e CSM e Bank e Customer Clearing Network Select the clearing network for the dispatch file to be generated Service Identifier Select the service identifier from the drop down list The options available are e SCT e SDD e SDD CORE e SDD B2B SDD B2B option is used for dispatch of outgoing collection for B2B transactions and SDD CORE option is used for dispatch of CORE and COR1 transactions e Dispatch file name has either COR or B2B as part of complete file name e CORE or COR1 S202CORABNDEXXX120224110227001 1 XML e B2B S202B2BABNDEXXX120224110227001 1 XML Bank Code Specify the bank code for which the dispatch file is sent This is enabled for Bank dispatch type Account Number Select the account number for which the dispatch file has to be sent This is enabled only for Customer dispatch type If you want to generate dispatch files for every customer you can select the option ALL Reference Number This indicates the reference number entered for every dispatch run This reference number is used to track the number of files generated as part of every dispatch run Maintaining Payment Gateway Message Browser You can hand
157. are made would be subject to IBAN validation for the counterparty account number Cover would be generated along with the payment Message as long as Payment message is linked as an advice to the PC Product DCLG Event ORACLE The cover message is sent to Direct Participant and Payment message to the addressable Indirect Participant Internal Clearing You need to determine whether the Clearing Bank being defined is an internal entity or an external entity A transaction is recognized as an internal type when it involves accounts maintained in Oracle FLEXCUBE and another maintained in any other system at your bank In other words the accounts belong to the same bank but are maintained in two different systems Oracle FLEXCUBE being one of them A transaction is recognized as an external type when it involves accounts maintained in Oracle FLEXCUBE and an external entity When processing transactions the system looks up this directory and identifies a clearing bank as internal if you have associated it with a valid branch code maintained in Oracle FLEXCUBE and opted for the Internal Clearing option If the clearing bank of the transaction is not specified for Internal Clearing the system recognizes the clearing bank as an external entity Clearing Participation Clearing Network Typically you would specify the clearing network for clearing banks that are defined for external clearing To recall externa
158. are then handed off to the P amp C module Uploaded transactions will ideally be one of following categories e Outgoing Incoming Payments initiated by Electronic Banking e Outgoing Incoming Collections initiated by Electronic Banking e Incoming leg of Internal Transactions All uploaded contracts along with the contract manually entered by the user from Online Screen form part of the processing queue Preliminary validations are done for checking the integrity of the contract data Validations are made along the following parameters e Upload Source an ORACLE e Product Category e Customer and Customer Account e Bank Code e Clearing Network e Product Code e Activation Date e User Defined Fields UDFs e Customer Agreements Based on the validations made the contract is moved to appropriate queue for event processing error handling Processed contracts are authorized based on the authorization parameter maintained in the Upload Source Depending on the errors encountered during processing the transactions will be handed off to the appropriate exception queue The following exception queues are available to view the details of contracts with exceptions Processing Exception Queue This queue displays the details of transactions for which an exception is raised during processing The system can raise an exception during charge computation or advice generation Credit Exception Queue Transactions that were rejected due to u
159. at you wish to appear in the account statements as well as the list of values for the user defined fields that need to appear in the statements You can invoke SDa ORACLE 3 29 this screen by typing PCDUDMNT in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button User Defined Fields Maintenance E New E3 Enter Query Account Description Field Number Field Description Data Type Data Type Numeric Date Mask Character Set Fields EL ig Date Time Checker Date Time Mod No Record Status Authorization Status In the User Defined Fields Maintenance screen you specify the following details for each user defined field you create Description Field Number Specify the identification number Field Description Specify the description of the field Data Type Date Type Specify whether the field is alphanumeric numeric or a date or an integer Date Mask If you specify a date field you can indicate a format for the date to be displayed Character Set Specify whether the values for the field should only contain Non SWIFT compatible characters Specifying UDF Details In the User Defined LOV Maintenance screen you can specify a list of values applicable for a user defined field that you have created Each list can be identified by an LOV Code and ony ORACLE description You can invoke this screen by
160. atched only if the reject reason is insufficiency of funds and if the Verify Funds box is checked Restrict to Exceptions Check this option to restrict the usage of ISO reject code to the list of Exceptions maintained If the option is checked then the system will restrict the usage of ISO Reject code If the option is unchecked then the system will not restrict the usage of ISO Reject code i e a particular ISO Reject Code is applicable for all possible exceptions Valid Days Specify the number of valid days within which reject should be performed Calendar Basis Select the Calendar Basis The options are e Branch Calendar e Network Calendar Exceptions You can add multiple values to this option field This field is used to input exceptions applicable for the Reject Codes List of Values are attached to display the valid exceptions based on the static data provided Description This field indicates the selected Exception type ISO reject codes for SEPA transactions can be maintained in the system using the PC Reject Code screen and the data is also factory shipped The following Reject Codes are factory shipped pad ISO Name SEPA Reasons Code AC01 IncorrectAccountNumber Account identifier invalid i e invalid IBAN or account number does not exist AC04 ClosedAccountNumber Account closed ACO6 BlockedAccount Account blocked reason not specified AGO1 TransactionForbidd
161. ate Status then system generates pacs 002 reject message which is sent to SIBS Payment Status is updated as Rejected Processing the Incoming Collection with sequence type FRST and with no amendment details is same as processing a transaction with Amendment Indicator set to TRUE This is because amendment is only in the debtor agent During subsequent processing of the same Incoming Collection if the Incoming Collection is rejected due to reasons other than mandate validation failure the status of the mandate record will remain unchanged Transaction with Sequence Type RCUR and with No Amendment Details When an Incoming Collection is processed with the sequence type RCUR and with no amendment details the mandate details are not inserted updated System checks whether the mandate details are maintained in the Payments amp Collections Debtor DD Agreements screen If the mandate details are maintained and Mandate Status is Active then the Incoming Collection is processed further and Amendment Reason is updated to PACSO03 Transaction with Sequence Type RCUR and with Amendment Details When an Incoming Collection is processed with the sequence type RCUR system checks whether the mandate details are maintained in the Payments amp Collections Debtor DD Agreements screen If mandate details are not maintained then system generates pacs 002 reject message which is sent to Credito
162. ate as the next working day For an outgoing payment product the System validates that the Dispatch days can be less than the Counterparty Entry Days but not less than the Customer Entry Days The local 4 ORACLE payments accounting process dispatches events for all Outgoing Payment contracts in respect of which the dispatch date is less than or equal to current system date and for which the DRLQ event has been processed but the CRLQ event has not been triggered Note The cut off time is also maintained at the Customer Agreement level for a product and customer combination This takes precedence over the cut off time defined for the prod uct Maximum Interest Amount of Transaction Amount Indicate the maximum percentage of the transaction amount that can be levied as interest for recalled transactions involving the product Maximum Split Count In certain cases you may find it necessary to split an outgoing collection transaction into multiple transactions due to restrictions on the amount of each payment that can be sent over the payment network In the Product Preferences you can restrict the number of transactions into which a parent transaction would be split by specifying the maximum split count Reject Account Details before Response Days Details Account Type Select the type of account that is used in the rejection leg You can select any one of the following options e Account e GL Account
163. ation Reference Number The system can create more than one consolidation batch for a same Customer consolidation reference based on the aggregation parameters The accounting entry reference number for the file consolidation batch is based on the process code ZFCN The closure of file consolidation batch will be through both automatic and manual e ORACLE 8 6 2 8 7 The system will not allow automatic closure of consolidation batch during the day for transactions that are consolidated across products during manual input The system will internally refer the following logic to consider the automatic closure of consolidation batch e Automatic closure of consolidation batch will be allowed if the transactions that are uploaded through file with File level Customer Consolidation Required as Yes at CPG browser level The system will follows the below logic for automatic closure of File Consolidation batch e During logging of each transaction in File Consolidation summary screen system will consider the transaction to be last transaction if Customer entry value date for all transactions in a batch is the system date Any transaction is in Unprocessed status in CPG browser for the same file reference number There are any transaction which is yet to consolidate in PC module for the same file or batch reference number There are any transaction in TR queue under the same file reference number and for the sa
164. be null If the P2P payment type is Test Transaction then the test transaction reference number will be same as the contract reference number If the P2P payment type is P2P Final Payment then the test transaction reference num ber will be reference number of the test transaction involved in P2P payment P2P Payment Type The system displays the value maintained for P2P Payment Type maintained for the product in the transaction Processing P2P Final Payment During the P2P final payment transaction an outgoing payment is created for P2P Final Payment Transaction When the customer debit transaction is processed the customer ledger in the debit liquidation is replaced with the suspense GL of the bank for debiting the transaction amount The debit GL used for debit liquidation is maintained at contract level This GL is used during the reject of P2P final payment transaction processing to credit the transaction amount in credit liquidation When an Amount Block request is processed the oN ORACLE amount block on senders s account is released Hence for the final payment the transaction amount will be debited from sender s account and will be credited to the clearing suspense GL Processing P2P Customer Debit Payment During customer debit transaction an outgoing payment of type Book Transfer is created You have to specify the email ID telephone number or facebook details for the transact
165. bit Transaction Amount CRLQ Customer Account Credit Transaction Amount If the transaction falls on incoming authorization queue then DRLQ event will be processed and following accounting entries are passed Event Account Debit Credit Amount ORACLE DRLQ_ Incoming Network GL NOSTRO Debit Transaction Amount DRLQ_ Intermediary GL Credit Transaction Amount If the transaction is moved from exception TA to exception T1 while authorizing the transaction from incoming authorization queue then system will not post any accounting entries The accounting entries posted for Outgoing Payment for which the P2P payment type is Customer Debit is as follows Event DR CR Accounting Role Amount Tag DRLQ DR CUSTOMER TFR_AMT DRLQ CR INTSUSPAY TFR_AMT CRLQ DR INTSUSPAY TFR_AMT CRLQ CR P2PCUSTTFR TFR_AMT The following accounting entries can be defined for Outgoing Payment for which the P2P payment type is test transaction Event DR CR Accounting Role Amount Tag DRLQ DR P2PTESTEX TFR_AMT DRLQ CR INTSUSPAY TFR_AMT CRLQ DR INTSUSPAY TFR_AMT CRLQ CR CLGSUSPAY TFR_AMT The accounting entries posted for Outgoing Payment for which the P2P payment type is P2P Final Payment is as follows Event DR CR Accounting Role Amount Tag DRLQ DR CUSTOMER TFR_AMT DRLQ CR INTSUSPA
166. by typing PCDPTPPWM in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button amp P2P Payments Parameters Maintenance EY New E Enter Query Bank Code Bank Name P2P Payment Details Registration Period in Days Archival Days Notify Days Calendar Basis Branch Calendar Registration Notification M Frequency F Notification Alert on End Date Maker Date Time Checker Date Time Mod No Record Status Authorization Status You can specify the following in this screen Bank Code Select the bank code from the adjoining option list 3 22 ORACLE Bank Name The system displays the bank name P2P Payment Details Registration Period in Days Specify the number of days within which beneficiary has to register in the sender s bank to receive the payments The activation date of the customer debit or effective date of the amount block request will be considered as From Date to calculate the end date for beneficiary registration Notify Days Specify the days to notify the end date for beneficiary registration in sender s bank Notify Days is mandatory if the Registration Period in Days is mentioned Registration Notification Start Date is derived based on notify days and end date for beneficiary registration Note Notify days cannot be greater than or equal to Registration Period in Days Calendar Basis Select the calendar basis
167. by typing PCDUTOFF in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Cutoff Time Update 7 Propagate Across Branches Product Cutoffs 10f1 E Product ProductCode ProductDesc CutoffHour Hours CutoffMin Minutes Select the Propagate Across Branches option to update the cut off time across all branches Handling SEPA Credit Transfers and Direct Debits A SEPA credit transfer SCT is a transaction done on behalf of the Originator holding a payment account with the Originator Bank in favour of a Beneficiary holding a payment account with the Beneficiary Bank one ORACLE The picture below gives the schematic representation for SEPA credit transfers processing SEPA Credit Transfer Message Flow Pain 001 001 01 Statements Advices Pacs 008 001 01 Pacs 008 001 01 Outgoing payment Incoming payment Pacs 002 001 02 Bank Pacs 004 001 01 Pacs 004 001 01 Reject of outgoing payment Reject of incoming payment Acceptance Date D Settlement Date Settlement Date 1 Max D 2 oe ORACLE The picture below gives the schematic representation for SCT processing from indirect participants Originator and Beneficiary of Indirect participants of SEPA SEPA Credit Transfer Messages Flow for Direct and Indirect Participants of SEPA pain 001 001 01 _ovainator Originator Bank SEPA Indirect pain 002 001 02 Participant Bank
168. call of DD Customer entry days should be less than or equal to coun Incoming terparty entry days solecon Customer entry value days should be less than or equal to counterparty entry value days Dispatch days should be specified Auto response should be null Recall of DD Counterparty entry days should be less than or equal to Outgoing customer entry days Collection Counterparty entry value days should be less than or equal to customer entry value days Dispatch days should be null Auto response days should be null 4a ORACLE Outgoing RFD Counterparty entry days and customer entry days should Collection be null Counterparty entry value days and customer entry value days should be null Dispatch days should be specified Dispatch days should be less than or equal to auto response days Incoming RFD Customer entry days and counterparty entry days should Collection be null Customer entry value days and counterparty entry value days should be null Dispatch days can be specified Dispatch days if specified should be less than or equal to auto response days Reject of RFD Customer entry days and counterparty entry days should Incoming be null Collection Customer entry value days and counterparty entry value days should be null Dispatch days should be specified Auto response days should be null Reject of RFD Counterparty entry days and customer entry days should Outgoing be null Collection C
169. can specify the address of the counterparty involved in the contract You can specify up to five lines of address information Counterparty BIC ID Specify the Bank Identification Code for the Counterparty Counterparty Scheme Name Type Select the Identification Scheme Type of the Counterparty from the drop down list The valid field can be e C Code e P Proprietary Counterparty Scheme Name Specify the value for Identification Scheme Name field If Scheme Name type is C then the Scheme Name can be selected from LOV and can have one of the values mentioned in value list depending on Organization Identification or Private Identification If the Scheme Name Type is P then you can enter the value for the field Counterparty Date of Birth Specify the date of birth of the Counterparty Counterparty Identification details You need to specify other information regarding the counterparty of the transaction free format 35 character text fields are provided with appropriate labels applicable for your installation You can specify the following details e Currency e ID e ID Type e ID Value e Other ID Type e Country e Issuer e City Of Birth e Country Of birth Counterparty Bank Direct Participant This is the Direct Participant for the Counterparty BIC and is derived from the Clearing Network information maintained in the PC Bank Directory screen Only if the counterparty is an indirect participant of the netwo
170. cate Recognition iv Required iv Required iv Customer Account iv Source iy Amount iy Station ID iv Counterparty Bank iv Source Ref y Counterparty Account iv Customer Account M Nauniarnarh hlama SS imanni sd i m r Offset Reject Recall Approval Redispatch Reverse Network Duplication UDF Details Rule Maker Date Time Mod No Checker Record Status peer Date Time Authorization Status me z Counterparty Name Mandatory For instance you can specify if transactions processed under a product should contain the Counterparty Name Maximum Length If you choose this option you can also specify the maximum length of that the name can extend to Character set You can specify if the characters must adhere to Non Swift standards Maximum Length If you choose this option you can also specify the maximum length of the character set can extend to Default Customer Account Default A C typeFor the product category you can specify the default customer account to be used for payments or collection transactions This account will be defaulted in the om ORACLE Transaction Input screen when you enter a payments or collection transaction involving the product category and it cannot be changed Default account type indicate the type of account that will be defaulted when an incoming collection is received The default customer maintained in the product category will be picked up and the transac
171. cation tool bar and clicking the adjoining arrow button The screen is as below Clearing Network Maintenance Clearing Network Description Clearing Currency Clearing System Id C Network BIC Network Type Default Account Incoming Branch Code Incoming Currency Code Incoming Account RTGS Non RTGS 7 New Cover format Required Handoff Directory Incoming Outgoing Network Qualifier Network Service Identifier SWIFT Type Outgoing Branch Code Outgoing Currency Code Outgoing Account IBAN Validation F Indirect Participant az E Description Description Dispatch Accounting Parameters i Branch Currency Nostro Account Outgoing Transaction Code Incoming Transaction Code m kzl ezl ez C a Fields Input By DOCCHO3 Date Time Authorized By Date Time Modification Number E authorized El open In this screen you should specify the following details Network e The Name of the Clearing Network This will uniquely identify the network in Oracle FLEXCUBE A brief description of the network Clearing currency of the network Clearing system ID code Specify a value for the field to identify a CSM It is same for all the clearing networks created for different schemes Also static data for clearing
172. ce in which the fields must be displayed in the account statements The fields are defined for a product type and product code combination User Defined Fields UDF and User Defined LOV Maintenance You can define additional fields required for processing DD and RFD transactions through the User Defined Fields screen You can also maintain a list of possible values for the User Defined Values Reject Code Maintenance DD and RFD transactions may be rejected because of several reasons You can associate the appropriate reject code with such transactions Reject codes are maintained in the Reject Code screen Debtor Customer Category Maintenance You can maintain debtor categories through the Debtor Customer Category screen This will enable you to define preferences for a debtor category instead of defining for each debtor participating in DD and RFD transactions The preferences for a category are maintained in the Product Debtor Category Preferences screen Charge Product Category Maintenance Maintaining charge categories will allow you to collate statistics involved in payment and collection transactions Using the data that is collated you will be able to define appropriate charges for processing transactions Charge Account Mapping Typically the processing charges are debited to the customer account involved in the transaction However through the Charge Account Mapping screen you can specify a different account for collecting
173. ce number You can view the reference number for the transaction that you are capturing Specify the following details in the main screen of the contract Capturing Details of the Main Transaction As mentioned earlier the PC Transaction Input screen is used to enter the details of a local payment collection transaction Apart from the standard fields that are available you will view the user defined fields that the administrator at your customer station has maintained These fields will be displayed in the sequence that your administrator has specified when defining the product category Customer Details Account Number Click A and select a valid customer account form the option list The list displays all customer accounts maintained in Oracle FLEXCUBE ora GL for which posting is allowed for instance a cash GL in case of remittance of cash handed over the counter in this field The option list displays customer accounts and internal GLs with the corresponding Clearing Account Number and the IBAN Account Number for GLs as maintained in the Chart of Accounts Note Note the following a ORACLE If you have specified an account that uses an account class that is restricted for debit or credit transactions for the product an override is sought when you attempt to save the contract Ifthe customer account is the debit account for a transaction you can indicate a GL of type Asset Liability Inc
174. ce screen will be displayed Only those bank codes using this network would be displayed Clearing Network Restrictions Clearing Network Allowed Disallowed Clearing Network Network id Description Transaction Details e User defined fields if any e MIS Details Customer Details e Customer Account in Oracle FLEXCUBE as well as in Local Clearing Format e Customer Name HS ORACLE 5 5 e Customer Information e Customer Bank Code and account details Saving a transaction in the PC Fast Transaction Input screen When a transaction is saved in the PC Fast Transaction Input screen any overrides or errors in respect of the transaction are displayed On saving the transaction after entering all the required details in the system the system validates the value of the transaction amount against the following e Product transaction limit e User Input limit If the transaction currency and the limit currency are different then the system converts the amount financed to limit currency and checks if the same is in excess of the product transaction limit and user input limit If this holds true the system indicates the same with below override error messages e Number of levels required for authorizing the transaction e Transaction amount is in excess of the input limit of the user The transaction is automatically authorized if automatic authorization is allowed for the profile of the user that has entered the transa
175. cellation PCDRCLIN You can manually reject cancellation for Payments and Collections using Payments and Collections Cancellation screen e Rejection of Cancellation of Payments On rejection Cancellation Status at cancellation request level would be marked as Rejected Reject Code Reject Detail entered during reject operation would populate CSM Reject Code and CSM Reject Detail fields respectively at cancellation request level e Rejection of Cancellation of Collections On rejection Cancellation Status at cancellation request level would be marked as Rejected Reject Code Reject Detail entered during reject operation would populate CSM Reject Code and CSM Reject Detail fields respectively at cancellation request level This rejection process would re activate the original Outgoing Collection with the contract details as prior to the cancellation Anew event RACT will be logged for the original Outgoing Collection in the contract events data store Credit Validation File CVF Process If Camt 056 recall request is sent for the outgoing payment the status of the Camt 056 is sent in CVF file by STEP2 On receipt of the CVF file by the sender bank system reads the CVF file and finds the status of the Camt 056 message If the status is rejected then the status is updated as rejected in the system Settled Credit File SCF Process STEP2 will send the SC
176. ch This will process the DRLQ event You can select multiple contracts and authorize them in bulk Clicking on Reverse button you can reverse the selected contract s You can also select multiple contracts and reverse them in bulk Clicking on Details button the system will display the details of the selected contract Aa ORACLE 4 5 Viewing Release Queue Details You can view the release queue details using the Payments amp Collections release Queue screen To invoke this screen by typing PCSRLXSQ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button amp Transaction Release Queue E Search t Advanced Search 9 Reset D Clear All Case Sensitive Contract Reference No Product Category Account Entry Reference Product Code Network Customer Account No Records perpage 15 v 10f1 Contract Reference No Product Category Account Entry Reference ProductCode Network Customer Bankcode ale Detail Release Reverse You can query the record based on the following details e Product Category e Contract Reference Number e Product Code e Customer Account Number e Network e Account Entry Reference Number Clicking on Search button the system will display all the records pertaining to the specified criteria Double clicking on any of the records the system will display the record details Clicking on
177. choose to process requests for debit for a product While setting up products meant to cater to outgoing type of RFD s you could choose any of the following options e No Tracking indicates that the RFD is not considered for approval or rejection e Full Payment indicates that the RFD is processed for payment of full transaction amount e Partial Payment indicates that the RFD payments can be made in multiple installments ORACLE Note You will not be allowed to select the first option while setting up a product meant for Incom ing RFDs Collection Scheme Type Specify the value for the field from the adjoining drop down list The list takes three values e CORE Selected for shorter time cycle transaction products e COR1 Selected for standard time cycle transaction products e B2B Applicable for incoming and outgoing collection products The field is enabled for Incoming and Outgoing collection products 4 2 2 Main Tab Click Main tab to capture the essential preferences of the product Payments and Collections Product Preferences x Product Code Description Product Type Main Additional Network Parameters Clearing Details Clearing Mode Payment Type Currency Dispatch Dispatch Media Dispatch Days File Name No of Records Reject Account Details Account Type Branch AccounvGL Currency Rejection Details Common Preferences Currency Minimum Div Amount
178. cified in the Split Details screen is defaulted to the main transaction input screen The first GL account specified in the Split Details screen is one ORACLE 5 2 8 1 5 2 9 defaulted as the customer account in the main PC Transaction Input screen and is also used in the corresponding payment message Split Details 10f1 E SerialNumber Branch AccountNumber Currency Amount MIS Total Amount Specifying Contract Split Details Serial Number The system displays the serial number of the contract Branch The system displays the branch where a contract is present Account Number The system displays the account number of the contract Currency The system displays the currency that is used in a transaction Amount The system displays the amount here MIS The system displays the MIS details of the contract Total Amount The sum of the split amount is displayed in this field This amount is displayed in the main screen as the actual amount Specifying the Split Details Split Number If a collection transaction needs to be split into multiple contracts specify the number of contracts into which the parent transaction is being split Split Parent Reference Number Specify the reference number of the parent collection transaction which is being split into multiple contracts Faa ORACLE Split Indicator This indicates whether the collection transaction ha
179. cify the requisite unsettled account or GL to be used for processing rejected incoming payments for each payments product category in the Payments and Collections Product Category Maintenance screen Payments Product Category Maintenance E New amp Enter Query Product Category Product Category Transfer Type Bank Transfer Category Description Product Type Collection Type WEW Detail Clearing Fields Offset Category Recall Category Reject Category Approval Category Redispatch Category Reverse Category Book Transfer 1 Of 1 al Offset Reject Recall Approval Redispatch Reverse Network Duplication UDF Details Rule Product Currency Description ELCs Date Time Mod No Checker Record Status Date Time Authorization Status When the aborted transactions are posted to the unsettled GL that you specify they can be rejected subsequently if communication is received from the customer Such rejection would generate a corresponding outgoing payment transaction The reject category for the rejected transaction can be maintained in the Product Category Maintenance for the incoming payment category If you do not specify the unsettled account or GL for a product category then incoming payments using the product category which are rejected will not be processed and no accounting entries will be posted in respect of them 3 36 3 2 Incoming Collections In the case of incoming collections proc
180. ck List White List of Creditors If Debtor Direct Debit Instructions are not maintained for a Debtor then the system will allow all the incoming collection transactions for that Debtor Managing Mandate Validating Mandate Existence for incoming collections The system validates mandate existence for incoming collection of a SDD B2B scheme if DD Agreement Required check box at Customer Agreement maintenance is checked after receiving incoming collection If the mandate exists then the system validates to match the transaction type as below e For One Off collection transactions transaction type of mandate is matched with OOFF e For First Recurrent and Final collection transactions transaction type of mandate is matched with RCUR e For the above cases if transaction type of mandate doesn t match with the sequence type of collection transaction then the system displays the override message as Sequence Type mismatch for an Incoming Collection and processes the transaction further e Static data for error code PC SEQT 01 is available 37104 ORACLE e PC SEQT 01 can be configured as type Error and auto rejection can be configured for sequence type checks failures The order of sequence type for the incoming collections transaction would be validated as shown in the following table Sequence SL No Type of Amendment validation Acton on Incoming Indicator Failure cas
181. coming Auth Queue screen To invoke this screen by typing PCSINAUQ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button an ORACLE S4 Advanced Search 5 Reset Contract Reference Product Category Exception Queue Account Entry Reference Product Code Number Customer Account Number Network Records per page 45 X First Previous 4 OF 4 Next Last W Contract Reference Product Category Exception Queue Account Entry Reference Number Product Code Network Customer Bank Cod m Detail Authorize Reject Postto Suspense You can query the record based on the following details e Product Category e Contract Reference Number e Product Code e Customer Account Number e Network e Account Entry Reference Number e Exception Queue Clicking on Search button the system will display all the records pertaining to the specified criteria Double clicking on any of the records the system will display the record details Clicking on Authorize button you can authorize the contract s and set it for dispatch You can select multiple contracts and authorize them in bulk Clicking on Reject button you can reject the contract s For this action the system will generate the return of incoming payment messages N07 for NEFT and R41 for RTGS customer transfer and R42 for RT
182. could be applied at the following levels e For all the accounts of a customer e Fora particular customer account e For all transaction currencies e Fora specific transaction currency You can specify the level at which a transaction charge applies when building a Charge Rule at your bank in ICCF Rule Maintenance screen CFDRUMNE When building a charge rule you can identify the transaction currency and customer on which the rule applies To define a standard charge rule that applies across your bank you would choose the ALL option at all levels That is you would select All at the transaction currency os ORACLE and customer fields When defining a charge rule you can choose to apply it selectively at one or more levels ICCF Rule Maintenance E New amp Enter Query Rule Type id Rule Id Transaction currency Description Branch Code Customer Group Customer Rate Details Te Tenor Basis Rate Type Flat Amount Tiered Amount FIXED RATE Tiered Tenor Rounding Duration Based Period in Months Interest Basis F As per Contract Currency Minimum Amount Minimum Rate Booking Currency Charge Currency Maximum Amount am Basis Amount Currency Maximum Rate Chae CRS Code Cascade Amount Rate O Rate Period Minimum Commision Period Fields Date Time Date Time Mod No Cig Authorization Statu For details on building Charge
183. count No azl Customer Account Branch az Collection Scheme Type 7 Records per page 10f1 C Authorization Status Record Status CustomerID Customer AccountNo Customer Account Branch Collection Scheme T i is Mi hip a a A a a UO You can query based on any or all of the following criteria e Authorization Status e Record Status e Customer ID Click Search The system displays the following values e Authorization Status e Record Status e Customer ID e Version Number The system displays the records in descending order of the version number ond ORACLE 4 1 4 2 4 Defining Attributes Specific to Payments and Collections Products Introduction In the Local Payments PC module of Oracle FLEXCUBE a product refers to a specific type of transfer of funds For example you may process payments that involve transfer of funds between accounts maintained at your bank You can define this type of local payment as a product at your bank In this chapter we shall discuss the manner in which you can define attributes specific to a local payments product Maintaining Product Details You can create a PC product in the Payments and Collection Product Definition screen invoked from the Application Browser You can invoke this screen by typing PCDPRMNT in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button In this screen you
184. creating a product you can express an Exchange Rate Variance Limit in terms of a percentage This variance limit would apply to all contracts associated with the PC product Override Limit If the variance between the default rate and the rate input varies by a percentage that is between the Override Limit and the Rate Stop Limit you can save the transaction involving the product by providing an override Stop Limit If the variance between the default rate and the rate input varies by a percentage greater than or equal to the Rate Stop Limit you cannot save the transaction involving the product Rate Code Specify the rate code that will be used to define at the product level Rate Type Specify the rate type that will be used to define at the product level Note You can AR or AP for ICCF components by maintaining Resultant Charge Type as Charge Component If the component is marked for AP or AR then the system creates the LQ record Specifying Preferences for a Product Preferences are the options available to you for defining the attributes of a product The options you choose ultimately shape the product For example you can specify the cutoff time entry dates redispatch dates and response days for transactions processed under a product This specification will apply to all transactions processed under the product You can a ORACLE invoke the Payment and Collection Product Preferences screen by
185. cription Message Type Queue li Product z Product Description Cover Required No v Direction Flag Incoming v On No Beneficiary Suspense Repair Input By Authorized By Modification Date Time Date Time Number Wi Authorized E Open For each incoming message type you can indicate the queue to which the messages must be routed and the Payments and Collection product product types instrument type that is to be linked to the queue to be used to process the resulting incoming payments transaction Mapping SWIFT and Non SWIFT Tags in Incoming Messages to Fields in the Payments and Collection Module To recall in order to facilitate the processing of incoming payment messages you must maintain mappings between the CPG fields and their corresponding fields in the Payments and Collections module for different combinations of incoming message type product category product instrument type source code station ID and network id You can do this in the PC Message Mapping screen Based on the Product Category Product Instrument type chosen the corresponding description will be displayed alongside Depending on the status of the instrument being uploaded the instrument will be uploaded as creation of a new instrument or liquidation of an issued instrument in the system You can invoke the Payments amp Collections Message Mapping Maintenance screen by typing oa O
186. ction Viewing the main PC Transaction Input screen From the Fast Transaction Input screen in View Mode you can view the main PC Transaction Input screen by clicking the arrow icon Authorizing a transaction All operations on a contract need to be authorized before the end of day Any user with the requisite rights can authorize an operation Importantly you cannot authorize an operation that you yourself have performed on a transaction For instance you cannot authorize a transaction that you have input even if you have the rights to authorize transactions If you have the requisite rights you can invoke the Payments and Collections Transaction Authorize screen You can invoke this screen from the Application Browser by typing PCDTRAUT in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button In this screen you can authorize the following operations that are unauthorized e Contract input e Amend Modification of contracts e Reversal of contracts When you launch the PC Authorization screen from the application browser you must specify a product category and click Authorize button If you wish to authorize all contracts in all product categories you can select the ALL option ons ORACLE When you specify a valid product category all contracts pending authorization in the selected product category or all categories as per your sele
187. ction are displayed Transaction Authorize amp Enter Query Product Category Contract Details Custom Reference No Contract Reference Rekey Details Customer Account Counterparty Bank Code Number Exchange Rate Counterparty Account Number Transaction Currency Counterparty Name Transaction Amount Activation Date Overrides 1 Of 1 E Confirmed Override Text Status Authorized By Authorize DateStamp Override Authorize Status Reject Error ChangeLog Contract Reference Specify the reference number of the contract you need to authorize The system displays the following values related to the contract reference number specified e Product Category e Contract Details Custom Reference No e Rekey Details Counterparty Bank Code Counterbank Account Number Counterparty Name Activation Date Customer Account Number Exchange Rate Transaction Currency Transaction Amount e Overrides Confirmed Override Text Status Authorized By Authorized Date Stamp Override Authorize Status a ORACLE Click Reject link to mention authorization reject remarks if you have rejected any transaction Reject Remarks Authorize Reject Remarks Click Error link the system displays the Error Code details screen You can view Error code details here Click Change Log link view the changes from the contract before and after Amendment The sy
188. ction Amount If the contract is reversed from Release queue then contract will be reversed and the following accounting entries are passed Event Account Debit Credit Amount REVR Customer Account Debit Negative transaction Amount REVR Intermediary GL Credit Negative transaction Amount If the contract is reversed from Authorization A1 A2 queues then the system will not process any accounting entries ORACLE The consolidated debit entry is posted to the customer account during the DRLQ event The entries posted will be as follows Event Debit Credit Amount Type Account DRLQ Debit Payment Amount Consolidated Customer A c DRLQ Credit Payment Amount Consolidated Suspense GL Customer Consolidation Across Products For transactions with Customer Consolidation Across Products as checked system triggers the DRLQ CRLQ entries during file consolidation batch closure A single debit entry is posted to the Customer account for the total file consolidation batch amount and individual credit entries are passed to the internal suspense account for each transaction amount The Amount tag FILE_AMT is used for consolidation across products which denotes the total File amount or transaction amount that are considered for Consolidation During file level consolidation for DRLQ event the accounting entry reference no for the debit leg will be based on the
189. cts 3 54 3 25 Maintaining Customer Stations ccccceeeeeeeeeeeeneeeeeeeeneeeeeeeeaeeeeeeeiaeeeeeeenaaes 3 55 3 26 Maintaining Product Categories 0 cc ceccceeeeeeeeeeeneeeeeeeenaeeeeeeeeeeeeeeseneeeeeeneaes 3 56 3 26 17 Main Tabi vette kisi ded AAR EE AEA iad i EELER UER AREE dai ALERE EEr 3 58 3 26 2 Detail Tab areis idiei tiii ar irira R EE E AE E EAEE ENAERE ENEE EEE r A AE EERE 3 61 3 26 3 Clearing Tabore a Adda aia 3 64 3 26 4 Associating User Defined Fields with a Product Category ccceee 3 65 3 26 5 Maintaining a Learning Database cccccccccceseeeeeeeeneeeeeteneeeeeeteenaeeees 3 67 3 27 Creating the Learning Database ee eccceeeceeeennneeeeeeenneeeeseetaeeeeeeeaeeeeeeenaees 3 67 3 28 Defining User Defined Fields for Account Statements 0 0 00 ececceeeeeeeeteeeeeenteees 3 69 3 29 Specifying UDF Details ecceceeeceneeceeeeeeeeeeceeneeneeeeeeeenaeeceeneenaneceestensaeensentanaes 3 70 3 30 Specifying Fields to be Included in Account Statements cccceeeeeeeeeeeeeenteees 3 71 3 30 1 Clearing Network Restrictions for Local Payment cccceeseteeeeneeeeees 3 72 3 31 Reject Code Maintenance ec cecceceeeeeeeeeeceeeeseeenneeeeeeeaeeeeseeeneeeeeeenaeeeeeeenaaes 3 74 3 32 Maintaining Debtor Customer Categories 0 0 0 0 ceececceeeeeeeeeeeeeetieeeeeeettaeeeeeeenaees 3 77 3 33 Defining Preferences for a Combination of a Product and a Debtor Category 3 78 3 34 Maintaining Details fo
190. customer Therefore you can use the ALL option in this field Branch Specify the branch that is that is associated with the customer for whom the agreement is being maintained Account You can specify the account for which the agreement details are being maintained The currency of the selected account will get displayed in the adjacent field based on the product linked In this field also you can select the ALL option for payments reject and recall products ONLY for reasons discussed above Note Note the following If you have specified an account that uses an account class that is restricted for debit or credit transactions for the product an override is sought when you attempt to save the agreement Ifabranchhas been maintained as a customer of your bank and you are specifying an internal GL of the branch as the account for the agreement you can choose the CIF ID of such a branch in the Customer field and the requisite GL in this field Such agreements would be validated for whenever a direct debit transaction is en tered with a GL as the account and the branch CIF ID as the customer of the trans action Mandatory Fields Creditor ID Scheme ID Required Check the box if you have the counterparty account number that is involved in the DD agreement It is mandatory to check this box to process mandate updates validations Agreement Identification Check the box if you have the DD agreemen
191. d Event Code and Accounting Entry combinations 0 9 3 9 2 1 Events for Payment and Collection Products ccccccceceeetteeeetetnteeeeetenee 9 3 9 2 2 ACCOUNTING EMOS re ia seienaehigs teenie nice ads eeeies S 9 6 9 3 Event Advices Tor POSi anaE a AE EE dentine aden eles 9 15 9 4 Credit Acknowledgement Messages ccceceeceeeeeeeeeeeeenteeeeeeeeaeeeeeeenaeeeeeeenaees 9 17 9 4 1 Message FOr cccssscccccccstteccecensesecedaccasancncdasdadecdenneadtecessussanectinecdaaecentes 9 17 FRE DOMS isos oes a eee ees cet wines cae ee cece eee 10 1 10 1 Intreductions tee iad deste iat ai eh Alda 10 1 10 1 1 Generating REPOS 11 ccceseeccceceseseeceaceseencnesensnuneetsesduncessedeanseestesananctteee 10 1 10 1 2 Contents Of the r DOrt cccccccccceeceeeneeeeceeeceteeeeeeseceeenaaecaeeeeeeeetettetneens 10 2 10 2 Processed Salary Report isistikinti arrini iarrann di eead i aeriana arant 10 2 10 3 Unprocessed Salary Report ccccccceceeeeeeeeeeeeeeneaeeeeeeeeeeeeeseesenesecaecaeeeseeeeees 10 4 Function ID Glossary nsssssssssssssssnnnunnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn na 11 1 1 1 1 2 1 3 1 4 Introduction 1 Preface This manual is designed to help you to quickly get familiar with the Payments and Collections module of Oracle FLEXCUBE It takes you through the various stages in processing a Payments or Collections transaction You can further obtain infor
192. d by creation of new LINK event and decrease in the unutilized amount The transaction amount is decreased the system deletes the existing LINK event and increases the unutilized amount followed by LINK event to create a new linkage and decrease the unutilized amount The Customer Entry Date is modified the system will validate if the new Customer Entry Date is greater than or equal to the option date and less than the maturity date min of Bought Value Date and Sell Value Date If it is then the system deletes the existing LINK event FX with old Value date and increases the unutilized amount followed by LINK event to create the new linkage FX with new Value date and decreases the unutilized amount If the condition is not satisfied then the system displays an appropriate error message For an Outgoing Payment Transaction if Debit Entry Liquidation DRLQ event is triggered then the system creates PLIQ event in FX to pass the reverse contingent entries to the equivalent amount of the PC Transaction For PC Incoming Payment Transaction if Credit Entry Liquidation CRLQ event is triggered then the system creates PLIQ event in FX to pass the reverse contingent entries to the equivalent amount of the PC Transaction If the FX linked PC Transaction future dated is amended after authorization then if FX linked is removed the system creates DLNK event FX to increase the unutilized amount ot ORACLE 5 2 3 N
193. d in the Product Transaction Limits Maintenance screen e the transaction amount is greater than the authoriser s authorisation limit if the Cumulative field is unchecked in the Product Transaction Limits Maintenance screen Canceling operations in the PC Authorization screen To cancel your operations and exit the PC Authorization screen click Exit button Amending Authorized Contracts The Payments and Collections screen enables you to modify the contract which is not liquidated or dispatched post authorization When a contract is modified the system triggers AMND event The features of the event are as follows oat ORACLE A new event AMND is triggered whenever an authorized contract for which either DRLQ or CRLQ or DCLG events are not triggered is modified When AMND event is triggered the system computes the values in the event log table cstb_contract_change_log for all the modified fields AMND event need not be attached in product it is triggered internally for all modifications performed as part of Step 1 AMND event is not triggered when un authorized contracts are modified No accounting entries will be passed for AMND event When a contract is booked with activation date in future and when the same contract s activation date is modified to current date the system will not trigger liquidation events since the system will not default the customer entry value dates To trigger
194. d of Day Beginning of Day Frequency Daily Holiday Rule Do Not Execute Execution Layer Database Application Sub Stage 1 Predecessors 1 Of 1 Predecessors Function Sequence Number Description Error Handling Stop Automatic End of Day and Run Emergency Program Continue with Automatic End of Day Number Of Days Run Date Job Code Description Maker Date Time Checker Date Time Mod No Record Status Authorization Status Module Choose the module code from the adjoining option list 8 1 ORACLE 8 2 1 8 2 1 1 8 2 1 2 Function Identification Choose the function ID of batch that you wish to run The adjoining option list displays all batch processes available for the module Select the appropriate one You can configure the batch to be run at various stages of day like EOD EOTI etc For further details about this screen refer the chapter Setting up Mandatory Programs for EOD in the AEOD User Manual The batch process for the Payments and Collections module contain the following sub functions Periodic Instructions This process identifies all periodic payments and collection instructions that need to be generated on the current date and generates contracts for those instructions These contracts are automatically authorized If the event processing parameter has been set to Online then these events are also processed online
195. d the available options are e C Code 20 ORACLE e P Proprietary Ultimate Debtor Scheme Name If Scheme Name type is C then select the Scheme Name from the values mentioned in the LOV depending on Organization Identification or Private Identification If Scheme Name type is P then enter the Scheme Name your own which can contain free format text and should of length 35 Ultimate Debtor Date of Birth Specify the Date Of Birth of the Ultimate Creditor Input the Date of Birth is only for Private identification Ultimate Creditor Details Name Specify the name of the ultimate creditor ID Select the identification code of the ultimate creditor from the drop down list Following are the options available in the drop down list e Organization Identification e Private Identification ID Value Specify the identification value of the ultimate creditor Issuer Specify the other identification type issuer of ultimate creditor City of Birth Specify the city of birth of ultimate creditor Country of Birth Specify the country of birth of ultimate creditor Ultimate Creditor Name Specify the Name of the Beneficiary Reference Party The field can contain any free format text of length 70 Ultimate Creditor BIC ID Specify the Bank Identification Code for the Ultimate Creditor BIC ID is only applicable for Organizational identification details Ultimate Creditor Scheme Name Type Specify the Identification Scheme Type
196. d to the total transaction provided in the Split Details and the MIS details can also be provided Split Details Serial Number Specify the serial number to know the order of the preference Branch Specify the branch where the split details are stored Account Number You can specify the multiple debit credit accounts for Outgoing Payments and Outgoing Collection Type of PC Product Categories Amount You can specify the amount for each of the debit credit accounts you have specified The sum of amounts specified for all the accounts must be equal to the transaction amount a2 ORACLE 3 34 2 CCY Specify the currency used in the split process MIS Click this button to capture MIS parameters Total Amount Specify the total amount that is used in the split process Note Note the following Split of debit credit amount is allowed only when currency is local currency and debit credit accounts are GL s Incase of Multiple debit s credit s the first account is defaulted as the Customer Account in the Periodic Instruction screen During generation of Outgoing Payment Collection the multiple accounts would be debited credited depending upon the instruction maintenance You can only select a local currency account for periodic instructions Customer No and Name If you opted to specify the customer account the name and number will be displayed when you save the contract If y
197. ded agreements can be closed and these agreements cannot be re opened Customer Cancelled agreements can be closed and can be re opened The agreement status is Active for future effective dated agreements If a Final collection is rejected cancelled returned reversed i e any R transaction on a FNAL collection then the agreement status will be changed back from Final to Active However if a Used collection is rejected cancelled returned reversed i e any R transaction ona OOFF collection then the agreement status will not be changed back to Active but remain as Used For Outgoing Collection transactions there will be a check for the existence of Creditor Mandate for the B2B scheme if DD Agreement Required is checked at customer agreement level If the creditor mandate for the B2B scheme is not found the outgoing collection will not be saved Effective Date Specify the date from which the agreement is valid or invalid At the Customer Agreement level you can choose the Agreement ID Counterparty Bank and or the Counterparty Account fields to validate the DD agreement details Amendment Reason Specify the reason for which the mandate details are amended oat ORACLE 3 21 Effective date Effective Date Specify the date from which the agreement is valid or invalid Note At the Customer Agreement level you can choose the Agreement ID Counterparty Bank and or the Counterparty Account fields to va
198. des for which the Direct option has been specified for the Clearing Network e For Non Addressable Indirect Participants the Indirect option can be specified without Cover and the Direct Bank Code Addressee This will default to the Bank Code in case the Bank Code is a Direct Participant in the Network If the Bank Code is a Non addressable indirect participant then this will default to the Direct Participant Bank Code ORACLE 3 4 1 3 5 If the Bank Code is an addressable Indirect Participant then this will default to the Bank Code You can also change the defaulted value if required Participation in Direct Debit and Request For Debit Transactions You also need to indicate the type of transactions supported by the clearing network whether DD and or RFD transactions This specification will be validated when the appropriate transaction type is being processed at your bank If not specified the network will be used to process only payment transactions Specifying UDF Details Click Fields button to provide values for the UDFs associated with the screen Maintaining Clearing Network Details In the Clearing Networks screen you can maintain the networks such as SORBNET and ELIXIR through which you communicate with other banks and financial institutions for funds transfers oe ORACLE You can invoke this screen by typing PCDCLRNT in the field at the top right corner of the Appli
199. details in new data store The table below explains the list of Recall Reason AGNT Incorrect Agent in the payment Agent workflow is incorrect on ORACLE 5 24 1 1 CURR Incorrect Currency of the pay Currency ment is incorrect CUST Requested Cancellation is By Customer requested by the debtor CUTA Cancel Upon Cancellation requested Unable To because an investiga Apply tion request has been received and no remedi ation is possible DUPL Duplicate Payment is a duplicate of Payment another payment UPAY Undue Pay Payment is not justified ment The set of transaction stored for payment cancellation is authorized and the system picks only authorized records for payment cancellation message generation Note The system generates the Camt 056 for all contracts for which recall is requested through SEPA Payment Cancellation It does not validate the number of days before which the recall can be made You can manually reject the cancellation request by inputting the CSM Reject Detail Reject Code and Reject Reference Number On saving the cancellation status will be changed into Rejected By STEP 2 Rejection of Cancellation of Payments On rejection Cancellation Status at cancellation request level would be marked as Rejected Reject Code Reject Detail entered during reject operation would populate CSM Reject Code and CSM Reject Detail field
200. duct you can define the priority with which the transactions associated with it should be processed You can indicate this priority on a scale of one to ninety nine Note Transactions received from the different queues are processed according to the following criteria The priority specified by the initiator and if unavailable The priority specified for the product with which they are associated Customer Entry days You can specify the number of working days to be added to the activation date to determine the entry date for the customer leg of transactions processed under a product For outgoing transactions the Customer Entry Date of a transaction should be earlier than or the same as the Dispatch Date The Customer Entry Date of a transaction should also be later than or the same as the Activation Date For an Outgoing product type your specification will apply to the debit leg of the transactions processed under the product For an Incoming product type your specification will apply to the credit leg of the transactions processed under the product Customer Entry value days You can specify the number of working days to be added to the activation date to determine the value date for the customer leg of transactions processed under a product For an Outgoing product type your specification will apply to the debit leg of the transactions processed under the product For an Incoming product type your specification wil
201. duct Category While defining a product category you can choose to associate UDF Values to the product category through the Product Category User Defined Fields sub screen You can choose to associate UDF Values with a product category to capture additional information which should be included in the payment or collection contract This information can pertain to the inclusion of option lists Numeric Text based or Date fields in the payments contract For the system to validate the correctness of the data captured against the user defined fields during contract processing you can choose to maintain the following information as well e Compose Derivation Rules whereby you can capture the logical derivation for the specified user defined fields These rules will be executed during contract processing e Define Validation Rule s Validation rules are multiple conditions for validating the UDF values that you capture while processing a transaction The validation that the system needs to perform can pertain to the length of the field whether the field is a mandatory field and the value restriction of the field and so on 3 65 ORACLE Click Fields tab in the Product Category Maintenance screen to invoke the PC UDF screen Payments Product Category Maintenance E New Enter Query Product Category Product Category Transfer Type Bank Transfer Category Description Collection Type Product Type
202. e Collection 1 FRST False To check Transaction whether this will be is the first moved into collection Transaction transaction Repair TR for the queue or Debtor Man auto rejected date with the error code PC SEQT 02 2 RCUR False To check Transaction whether will be FRST has moved into been Transaction received and Repair TR processed queue or successfully auto rejected and FNAL with the error has not code PC received yet SEQT 03 3 FNAL False To check Transaction whether will be FRST and moved into RCUR has Transaction been Repair TR received and queue or processed auto rejected successfully with the error and FNAL code PC has not SEQT 04 received already 5 103 ORACLE Sequence SL No Type of Amendment vaiidation ooo Incoming Indicator Failure case Collection 4 FRST True To check Transaction whether will be sequence moved into type is FRST Transaction if Identifica Repair TR tion under queue or Other under auto rejected Financial with the error Institution code PC Identifica SEQT 05 tion is SMNDA SMNDA stands for Same Man date with New Debtor Agent 5 FRST True To check Transaction whether will be sequence moved into type is FRST Transaction if Mandate Repair TR ID is queue or changed auto rejected with the error code PC SEQT 06 Static data for error code PC SEQT 02 PC SEQT 03 PC SE
203. e Beneficiary Generated MS03 NotSpecifiedReasonAgent Reason not specified Generated NARR Narrative AOS RCO1 Bankldentifierlncorrect Bank Identifier Incorrect RFO1 NotUniqueTransactionRefer AOS ence 3 76 ORACLE 3 32 TMO1 CutOffTime File received after cut off time EDO5 SettlementFailed AOS RRO1 Regulatory reason Usage Rule To be specified in Proprietary of Return Reason using the code RRO1 DNO Debtor bank is not registered Debtor Bank is not registered under this BIC R in the CSM CNO Creditor bank is not registered Creditor Bank is not registered under this BIC R in the CSM Maintaining Debtor Customer Categories Debtor categories are used to define preferences for a group of debtors rather than for each debtor For instance a creditor might wish to allow a longer recall period to debtors of a certain category The Payments amp Collection Debtor Categories Maintenance screen allows you to define such debtor categories This information is picked up while capturing customer agreement details You can invoke this screen by typing PCDDCCAT in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Payments amp Collection Debtor Category Maintenance FE New E3 Enter Query Debtor Category Description Fields Maker Date Time Checker Date Time Mod No Record Statu
204. e Details 0 00 0 ec cceeeeeceeee teeter eset eteneeeeeetaeeeeereiaeeeenenea 4 33 4 6 Validations for Product and Collection Type Combinations cccceeeeeteeeeeees 4 34 4 7 Processing Outgoing Payment Transaction cecceeeeeeeeceeee eee eenneeeeeetnaeeeeeeees 4 36 4 7 1 Window Periods for Outgoing PayYMentS cccccccecteeeeeetttteeetetnteeeeeteee 4 39 4 8 Processing Incoming Payment Transaction 0 cccceeeeeeeeecereeeeeeteteeeeeeeeneeeeeees 4 40 4 8 1 Viewing Incoming Transaction Authorization DetailS 0011000001100000 4 40 4 8 2 Viewing Repair QUCUCL 0 cececeeeceeeeeee eee teneeeeeeeteneaeeeeetenaaaeeeeseneaaeeeetenaaaees 4 42 Processing a Payment or Collection Transaction 0seeee 5 1 ST INMPOGUCHION serienn annaa aa EE EAE EEA R aTa aR 5 1 5 2 Capturing Details of Payment Collection Transactions ccceeceeeeseeeeeeeneeees 5 1 5 2 1 Entering a TranSaction i E r TEE EE A O 5 1 5 2 2 Capturing Details of the Main Transaction ccccccsseeceessteeeeeeentteeeeeeeeaes 5 3 9 2 3 Specifying Transaction Details cccccccccecceceeeeeeeentneeeeeetnnneeeeeetneeeeeneeae 5 12 5 2 4 Specifying Collection Details cccccccecceceseeeeeeceeenneeeeeeetnnneeeeeetiaeeeenenaaa 5 21 5 2 5 Specifying the Party Detals ccccccccscteeeeetecneee eee enneeeeeeetneeeeeetnaeeeenenee 5 24 5 2 6 Capturing the Message Details 0 0 0 cccccccteceeeeeeetetteeeeetenteeeeetetna
205. e FLEXCUBE for dispatch to clearing The following specifications are made in the Oracle FLEXCUBE Clearing Gateway for the outgoing payments workflow e The duration of the time out period in minutes after which the message could be re dispatched e The applicable re dispatch parameters including the number of times the message would be re dispatched before the transaction is timed out For details about the Oracle FLEXCUBE Clearing Gateway refer the Clearing Gateway user manuals Outgoing Payments Product Category Definition When you are defining the outgoing payment product category you can indicate whether custom reference numbers must be generated by the system for outgoing payments either on online entry or during upload If this option is indicated then you must also specify the sequence code that must be used to generate the custom reference number sequence The custom reference numbers are then generated according to the specifications made for the specified sequence code in the Sequence Generation maintenance For details about how the sequence code is constructed in the Sequence Generation Maintenance screen consult the Core Services User Manual Viewing Message Status of a Contract For contracts using an outgoing payments product for which the outgoing payments workflow has been enabled the status of the message can be viewed in the PC Transaction Input screen The status could be any of the foll
206. e ID for a specific collection scheme type with Restriction Type as Disallowed in Debtor Direct Debit Instructions Web services for Black List and White List of Creditors are available If Incoming Collection transaction for a Debtor matches with these maintained data then the system moves the transaction to Transaction Repair TR queue Static data for error code PC INDD 11 is available and auto rejection can be configured for this error code If auto rejection is configured then the system rejects the Incoming Collection transaction when details match with black list The system rejects the transaction in following scenarios e If any of the incoming collection transaction s Creditor Scheme ID matches with maintained value e If any of the incoming collection transaction s Creditor IBAN matches with maintained value e If any of the incoming collection transaction s Creditor Scheme ID or Creditor IBAN matches with the maintained value e If any of the incoming collection transaction s Creditor Scheme ID and Mandate ID matches with the maintained values e f any of the incoming collection transaction s Creditor Scheme ID and Mandate ID or Creditor IBAN matches with the maintained values N04 ORACLE 5 30 5 30 1 White List You can restrict allow incoming collection transaction to be processed based on Creditor ID Scheme ID Mandate ID and Creditor IBAN for a specific collection scheme type with Restriction
207. e generated for collection transactions e Remit Slip Based on the product advice definition this advice is generated when a contract is saved It is automatically printed and cannot be viewed regenerated subsequently e Debit Advice Based on the product advice setup this advice is generated while processing the Debit Entry Liquidation DRLQ event for the following type of transactions Incoming Direct Debit Reject of Incoming Direct Debit Recall of Outgoing Direct Debit Approval of Incoming Direct Debit Outgoing Payment e Credit Advice Based on the product advice setup this advice is generated while processing the Credit Entry Consolidation CRLQ event for the following type of transactions Outgoing Direct Debit Reject of Outgoing Direct Debit Recall of Incoming Direct Debit Approval of Outgoing Request for Debit Incoming Payment e Approval Advice Based on the product setup this advice is generated for the following type of transaction while processing Collection of Approvals APPR Outgoing Collection Incoming Collection e Reject Advice This would is generated for the following type of transactions Rejected Outgoing Collections If the advice basis date is the Event Date the advice is generated while processing the Collection of Rejection REJT event for the transaction If you have identified the Response Date as the advice basis date the advice is generated on t
208. e less than dispatch days Auto response days should be null Incoming NA Counterparty entry days should be less than or equal to Payment customer entry days Counterparty entry value days should be less than or equal to customer entry value days Dispatch days should be null Auto response days should be null Outgoing DD Counterparty entry days should be less than or equal to Collection customer entry days Counterparty entry value days should be less than or equal to customer entry value days Dispatch days should be less than or equal to counterparty entry days Customer entry days should be less than or equal to auto response days eat ORACLE Incoming DD Customer entry days should be less than or equal to coun Collection terparty entry days Customer entry value days should be less than or equal to counterparty entry value days Dispatch days should be null Auto response days should be specified Reject of DD Customer entry days should be less than or equal to coun Incoming terparty entry days olacan Customer entry value days should be less than or equal to counterparty entry value days Dispatch days should be specified Auto response days should be null Reject of DD Counterparty entry days should be less than or equal to Outgoing customer entry days Collscen Counterparty entry value days should be less than or equal to customer entry value days Dispatch days should be null Auto response days should be null Re
209. e of the Initiating Party Initiating Party Scheme Name Type Specify the Identification Scheme Type of the Initiating party and available options are e C Code e P Proprietary Initiating Party Scheme Name If Scheme Name type is C then select the Scheme Name from the values mentioned in the LOV depending on Organization Identification or Private Identification If Scheme Name type is P then enter the Scheme Name your own which can contain free format text and should of length 35 Initiating Party Date of Birth Specify the Date Of Birth of the Initiating party Identification Value Specify the identification value This is optional Ultimate Debtor Details Customer Name Specify the name of the ultimate debtor ID Select the identification code of the ultimate debtor from the drop down list Following are the options available in the drop down list e Organization Identification e Private Identification ID Value Specify the identification value of the ultimate debtor Issuer Specify the other identification type issuer of ultimate debtor City of Birth Specify the city of birth of ultimate debtor Country of Birth Specify the country of birth of ultimate debtor Ultimate Debtor BIC ID Specify the Bank Identification Code for the Ultimate Debitor BIC ID is only applicable for Organizational identification details Ultimate Debtor Scheme Name Type Specify the Identification Scheme Type of the Ultimate Creditor an
210. eant for Incoming Payments you can indicate whether the Counterparty Name should be validated against the authorized variations of the customer s name maintained in the Customer Names screen If you enable this option all incoming PC transactions involving the product category are processed only after the customer s Account Number and Name correspond to the authorized variations of the customer s name Note If the validation fails the contract will be uploaded as unauthorized Even during manual authorization of such contracts an override is displayed asking whether the customer name needs to be added to the existing list It will be added to the existing list on confirming the override Contract details Response Days As mentioned earlier an RFD transaction if not approved within the response period is considered closed You can specify the number of response days applicable to contracts using the product category Spa ORACLE 3 26 3 3 26 3 1 Archival Days You can also maintain the number of days for archival of transactions using the product category Purge Days You can also maintain the number of days for purging the transactions using the product category Learning Database details Applicable While maintaining details of a product category you can choose to check the Applicable box positioned next to the Learning Database field to indicate that the UDF details that you capture while proce
211. eceipt of Pacs 002 for Reject of Incoming Collection the underlying Reject of Incoming Collection contract would be rejected by processing pre settlement reject RJBS event e RJBS event on Reject of Incoming Collection Will mark the contract as rejected and accounting entries if posted would be reversed Will populate new fields CSM Reject Code CSM Reject Detail and CSM Reject Reference Number at contract level with the received reject code reject description and reject reference number from Pacs 002 Will also reactivate the Original Incoming Collection by processing Reactivation Event e The reactivation event for the Original Incoming Collection will revert the status of the incoming Collection prior to post settlement rejection event processing REJT This enables incoming collection to be rejected further Pacs 002 for Recall of Incoming Collection Pacs 004 sent by Debtor Bank e Recalls of Incoming Collections are generated when Incoming Collection is recalled by processing recall operation RECL event e On receipt of Pacs 002 for Recall of Incoming Collection the underlying Recall of Incoming Collection contract will be rejected by processing pre settlement reject RJBS event e RJBS event on Reject of Incoming Collection Will mark the contract as rejected and accounting entries if posted will be reversed a 108 ORACLE Will populate new fields CSM Reject Code CSM Reject Det
212. ecified Issuer Specify the Identification Issuer of the counterparty This is used to identify if Organization identification is used as Proprietary Identification or Private Identification City of Birth Specify the city of birth of the counterparty This is enabled and is mandatory if you have selected identification type as Date and Place of birth Country of Birth Select the country of birth of the counterparty from the option list This is enabled and is mandatory if you have selected the identification type as Date and place of birth Country Specify the country of residence of the counter party This adjoining option list displays all valid country codes maintained in the system You can choose the appropriate one Note The country information is captured to enable Mantas to analyse the transactions for pos sible money laundering activities For more details on Mantas refer Mantas interface document Multiple Dr Cr Account for Periodic Instruction To specify the multiple debit credit account for Outgoing Payment or Outgoing Collection PC category types with facility to specify MIS for each of the leg you can click the S button provided in the Periodic Instruction Maintenance which facilitates capturing the Split Details screen as shown below This button is enabled for Outgoing Payments and Outgoing Collection type of PC Product Categories The sum total of all debits credits is defaulte
213. ect Code maintenance An error message would be displayed if the entered Reject code is not applicable to the Cancellation initiation exception Additional Recall Reason Specify a text value of 105 characters for the field which must be a description about the fraudulent origin of the transaction Note If Fraudulent field is not Additional recall Reason and Additional Recall Information field is defined then the system throws an error Additional Recall Information If Fraudulent is selected in the Additional Recall Reason field then specify details on the fraudulent origin of the transaction The system will throw an error if Additional Recall Information is entered when Fraudulent is not the additional recall reason A maximum of 105 characters can be specified in this field Service Type Specify the value for the field from the adjoining drop down list The field takes following values e SCT e SDD CORE e SDDCOR1 e SDD B2B Note Option SDD B2B should be used for Request for Cancellation of Collections executed for B2B SDD CORT is selected for Request for cancellation of collections for shorter time cycle transactions Click on the Search button to fetch the matching contracts based on the search criteria provided Note The system generates the Camt 056 message only for liquidated contracts Contract Reference Number Select Contract Refer
214. ect the identification for the network Description The system displays the description of the network as electronic network or clearing Reject Code Maintenance Collection transactions can be rejected for various reasons for example insufficiency of funds in the debtor s account In such a case the debtor s bank sends a reject transaction with relevant reject codes to the creditor s bank The Reject Code Maintenance screen allows you to describe each reject code that you specify You can invoke this screen by typing PCDRJCOD in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Reject Code Maintenance Reject Code kz Valid Days Reject Reason Calendar Basis Branch Calendar Network Calendar Network Id lz Error Type x F Verify Funds Restrict to Exceptions Exceptions 1 0f1 F Exceptions Description Date Time Date Time Record Status Authorization Status Reject Code Specify the reject code for the rejected transaction here Description You can give a small description for the reject code you have specified Network ID Specify the network ID Error Type Select the type of reject code values from the drop down list Following are the options available in the option list e Error os ORACLE e Reschedule Verify Funds A collection transaction which has been rejected is redisp
215. ected from the customer when a mandate is cancelled The charge amount should be a flat amount and cannot be a percentage or tier slab You can configure different charge amounts for every Source Code Branch Code Customer No and Account No combination Customer Detail Account No Specify the account number for which the mandate cancellation charges should be maintained The adjoining option list displays all the valid account numbers maintained in the system You can choose the appropriate one Customer No Specify the customer id for which the mandate cancellation charges should be maintained The adjoining option list displays all the valid customer id s maintained in the system You can choose the appropriate one Jal ORACLE 3 23 1 Processing Mandate Cancellation You can initiate mandate cancellation from the Payments amp Collections Debtor DD Agreement Maintenance screen To cancel the mandate click the Close button on the Application tool bar System will mark the Payments amp Collections Debtor DD Agreement Maintenance screen as closed and will trigger the CLIQ event The reference number used for posting the accounting entry related to this charge uses the process code ZMND and this reference number will be updated as Charge Reference Number in the Payments amp Collections Debtor DD Agreement Maintenance screen Example Assume the following charges for mandate cancellation
216. ections Consolidation Exception Queue mae amp Search Ct Advanced Search Reset K Clear All Case Sensitive Consolidation Status Pa Customer Number i Account Number az Account Currency FS am az Customer Entry Value Date E gt Customer Entry Date E gt Product Code az Account Entry Reference az Exception Queue az _ Number Customer Account Branch as Transaction Count laz Product Type S Consol Reference la Records per page 15 x 10f1 Consolidation Status Customer Number Account Number Account Currency Amount Customer Entry Value Date Ct ni r Accept Reject Carry Forward Retry The other options available are e This option marks the contracts for reprocessing of consolidation Click Retry to retry consolidation of the transaction e Click Accept to force accept a transaction e Forward Choose this option if you would like to forward the consolidation processing to the next working day The contract will be marked for pickup on the next working day for consolidation Click the Carry Forward button to forward the consolidation processing date of the transaction to the next working day The parameters considered are e Consolidation Status e Customer Number e Customer Account Number e Account Currency e Account e Customer Entry Value Date e Customer Entry Date e Product Code e Account Entry Reference Number 280 ORACLE e Exception Queue e Transaction
217. ed Electronic Signature Specify the electronic signature of the debtor Charge Details Charge Bearer This indicates which party will bear the charges associated with the payment This value is received from the incoming SEPA instruction and you are not allowed to change this For manually input transaction this will be defaulted from the Product Maintenance Charge Mode You can indicate whether charges applicable for the transaction are to be applied over and above the transaction amount premium or subtracted from the transaction amount discount Waive Charge You can indicate that the charges in respect of the transaction computed according to the first condition set displayed in the Charge Amount field must be waived Third Party Charge Currency Select the third party charge currency from the adjoining option list ORACLE Third Party Charge Amount Specify the third party charge amount Payment Details Unstructured Remitter Reference Specify the remitter reference number Remitter Code Specify the remitter code Remitter Information Issuer Specify the issuer of the remitter information Additional Remittance Info Specify additional remittance information if any Structured Invoicee Details Identification Type Select the identification type from the adjoining drop down list The options available are e Private e Organization BIC Specify the bank identifier code Name Specify the na
218. ed for the product used by the contract For uploaded of transactions transactions that are rejected after response days are queued in the Process Exception Queue ORACLE Additional Tab Click the Additional tab to specify the additional preferences pertaining to the product Payments and Collections Product Preferences iption De Product Type Transfer Type Main Additional Network Parameters Activation Date Agreement Preferences Customer Entry Consolidation Back Value Limit Day Agreement id Required Required Future Value Limit Creditor Id Required Consolidation Limit Days Currency Move Back Dated I Activation Date Default Activation Date Exchange Rate Redispatch Details Recall Days Details Auto Exchange Rate Redspatch Required Days Rate Code Auto Recispatch Basis Rate Type Count Date Basis Day Reversal Details Cancellation Details Cancellation AcceptanceDetails Oays Days Basis Working Allowed Re Calendar Reversal Calendar Basis Calendar Basis Calendar Basis Collection Preferences First Collection Receipt Recurrent C on Day Receipt Days Calendar Basis Activation Date If at the time of booking a transaction involving the product if you have failed to specify the transaction date the default date that you specify in this field will be picked up Back Value Limit Days You can indicate the number of calendar days before the
219. ed on the cutoff status of the transaction oe ORACLE Instruction Date This indicates the requested execution date of the SCT transaction and Collection due date of an SDD transaction This is a display only field Settlement Date Specify the inter bank settlement date of the incoming instruction Initiation Date The date and time when the transaction was received through the Electronic Banking System is displayed Receive Date of Incoming The system displays the incoming receive date Purpose Details Category Purpose Specify the category purpose of the credit transfer from the option list Purpose Type Select the purpose type of the credit transfer from the drop down list Following are the options available in the drop down list e Proprietary e Code Purpose Value Specify the purpose value of the credit transfer Local Instrument Type Select the local instrument type from the drop down list Following are the options available in the drop down list e Proprietary e Code The value for the field is defaulted as CODE The field is enabled if the product type is Outgoing Collection Note Ifthe Collection Scheme type is maintained at product level then system validates local instrument value to Collection Scheme Type value maintained at product level and local instrument type as Code Ifthe Collection Scheme type is not maintained at product level then
220. edispatch e Contract status is outstanding e Collection status is rejected or closed e Automatic redispatch is required oe ORACLE 8 2 1 3 8 2 1 4 e Redispatch date is the same as or earlier than the system date Closure This process identifies all outgoing request for debit transactions satisfying the following conditions and marks the collection status as closed and contract status as liquidated e Contract status is outstanding e Collection status is pending e Automatic redispatch is required and is the final redispatch OR e Redispatch is not required e Redispatch date is the same as or earlier than the system date It also identifies all outgoing request for debit transactions satisfying the following conditions and marks the collection status as closed However the contract status of the transactions remains outstanding to enable redispatch of such transactions at a later date e Contract status is outstanding e Collection status is pending e Redispatch is required e Manual redispatch has been specified for the transaction e Automatic redispatch is applicable and the transaction is not the final redispatch e Redispatch date is the same as or earlier than the system date Dispatch to Clearing This process identifies all contracts that meet the following conditions and dispatches them to clearing using the interface system Oracle FLEXCUBE Clear
221. eeeeenaees 3 21 3 14 Maintaining P2P Payments Parameters 0 ccc cccceeeeeeeeeeeeeeeeeseeeneeeeeeenaeeeeeeeeaaes 3 22 3 15 Viewing P2P Payments Beneficiary Registration Queue eee eeeteeeeeeenees 3 24 3 16 Maintaining Upload SourceS osar nEn AAEE E ENE EE TEG 3 25 3 17 Specifying Parameters for a SOUFCEe seessseeeseersseeerirneesrerueaerinannserenneeerinneeettennaens 3 26 3 18 Capturing Customer Agreements cc cccccceeeeeeeeennneeeeeeeneeeeeeeeteeeeeeeianeeeenenaaes 3 28 3 18 1 Automatic Cancellation of the Mandate cceccccccieeteeeeeetnneeeeeeetnneeeeeeees 3 32 3 19 Maintaining Creditors cece eeeeeeeeeeeeeeeeeeeeeeeaeeeeeeeaaeeeeeeeeiaeeeessenteeeeeenaes 3 33 3 20 Maintaining DD Agreement Details for Creditors eeeeeeeeeeseeeeeeeentteeeeeeenaaes 3 34 3 21 Maintaining DD Agreement Details for Debtors ec eeeeeeeeeteeeeeeeeeteeeeeeeenaees 3 38 3 22 Maintaining Debtor Direct Debit Instructions 0 ee eeeeeeeeeeeeeeeeeeeeeeenteeeeeeeaaes 3 43 3 22 1 Processing of Incoming Collection Transaction for a Mandate 3 45 3 22 2 Processing Based ON SEQUENCE TYPO sssssrieerrrerrrrrnnnnrerrrenrrerennnrennne 3 47 3 23 Maintaining Mandate Cancellation Charge Details ccc eeeeeeeeeeneteeeeeeenaaes 3 50 3 23 1 Processing Mandate Cancellation ccccccccccceseeeeteseneeeeeseneseeeeeteeesaeeees 3 52 3 24 Viewing Mandate Cancellation Charges Summary Details ee
222. eeeeentaae 5 28 5 2 7 Viewing User Defined Fields for a PC contract ccccccceeeteceeetsteeeeeeenes 5 31 5 2 8 Specifying Split and MIS Details ccccccccceeceeceenteeeeeceeenteeeeeeeeseeeeeneeaas 5 32 5 2 9 Specifying the Split Details s issiissiiiniiiiinin isurien snurken iaaiiia enai aeai 5 33 5 2 10 Specifying the MIS DetailS 1s1sss1nneesrnnnnrennnnnnnrrnnnnnernnnnerrrnnnnnnnnnnnnrennaa 5 35 5 2 11 Viewing Event DAalS siere oiie ae Aee EAEE EEE EE EEE EERE 5 35 5 2 12 Viewing Duplication detailS sssereeerreeerrinnnrrerrrnnrrnnnnnnenrrnnerrrnnnnneennane 5 35 9 2 13 Specifying Project Details se ersi eeir n E EEEE EEE 5 37 5 2 14 Viewing a Tax SCHEME c cccseccccsetecdeceutesedeneesennansdassnendiensdesdaneteenseaedtnrele 5 37 5 3 Viewing Payments and Collection TransactionS eeeeeeseeeeeeeeeereeeerresseeerrssee 5 40 5 4 Simplified Entry of Payments and Collection Transactions ccceeeeeee 5 42 5 5 Authorizing a transaction reece n r T A TO 5 44 5 5 1 Amending Authorized Contracts essisseeeieineneeeennneernnnreerrnnenernnnneeenene 5 47 5 6 Viewing Transaction Authorization Details 0 00 00 ec ceccceeeeeeeeeeeeeeeeeeeeeennaeeeeeeenaaes 5 48 5 7 Multilevel Authorization of a Contract eee ccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeseeeaaeeeeeeeaaees 5 49 5 8 Operations on Collection Transaction ccccccceceeeeeeeeeeeeeeeeceeeeeeeeeeeeeeeeteeeeeneaes 5 49 5 8 1 Collecti
223. eeenteeeeeeeenees 3 104 3 40 Viewing Creditor Direct Debit Agreement History ecceeeeeeseeeeeeeettteeeeeeenaes 3 105 3 41 Retrieving Debtor Direct Debit Agreement History 00 0 ceeeeeeeeeeeeeteeeeeeeeee 3 107 3 42 Viewing Debtor Direct Debit Agreement HIStory ccceceeeeeeeneeeeeettteeeeeeenaes 3 107 3 43 Retrieving Debtor Direct Debit Instructions History 0 00 0 ceeeeeeeeeeeeeeetteeeeerenee 3 109 3 44 Viewing Debtor Direct Debit Instructions History ceeeeeeeeeeeeeeeetteeeeeeeeaee 3 109 4 Defining Attributes Specific to Payments and Collections Products 4 1 4 1 Introduction eienenn iA en ecnden ASE AE AENEAN E E aA 4 1 4 2 Maintaining Product Details ccc eeceeeeeeeeeneeeeeeeeceeeeeeeaeeeeeeeaaeeeeeesiaeeeeeeeaaas 4 1 4 2 1 Specifying Preferences for a Product eeeessseeesrreenerrnnnnenerrenerennnnneeernns 4 3 4 22 Main TA D E haste nee Ma ceiines a a fee ia A ets 4 6 45253 Additional Tabris eds ari a A lees aig 4 18 4 2 4 Network Parameters Tabuu cccccccccccccccccccccccceescsueeceeeeceseeeesessaeseesaseesenensaes 4 27 4 2 5 Specifying the List Of BANKS eccccceeeeeee eee enee eee eeetnneeeeeeetnaeeeeentnaeeeeentae 4 29 4 2 6 Linking a Tax SCHOIMC rieri T E AREO ETE an 4 30 4 3 Viewing Level 1 Authorization A1 Details eeeeeeeeeeeeeneeeeeeeeneeeeeseeaeees 4 31 4 4 Viewing Level 2 Authorization A2 Details ec eeeeeeeeeeeeneeeeeeeeeneeeeseenaeeees 4 32 4 5 Viewing Release Queu
224. efer section Queues Maintenance in the chapter Straight Through Processing An Overview of the Funds Transfer User Manual Product Mapping To handle SEPA transactions as part of mapping message types to product and queues you need to map PC product category for SCT and SDD message types This can be done using the Product Mapping Detailed screen For more details on mapping message types to products refer section Mapping Message Types to Products and Queues in the chapter Straight Through Processing An Overview of the Funds Transfer User Manual Message Mapping To handle the processing of incoming SEPA transaction messages you must maintain mappings between the Common Payment gateway fields and their corresponding fields in the Payments and Collections module for different combinations of incoming message type product category product instrument type source code station ID and network id For more details on mapping message tags to payment fields refer section Mapping Non SWIFT Tags in Incoming Messages to Fields in the Payments and Collection Module in the chapter Maintaining Information specific to the Payments and Collections Module of this User Manual Error Code Maintenance To handle auto rejection of incoming payments for SEPA you need to maintain some error codes based on which the system rejects the payment For more details on maintaining error codes refer section Mainta
225. eference Number and offset amount tag e Station This is derived from the mapping in the Settlements to Payment Product and UDF Mapping maintenance in the Settlements to Payment Product and UDF Mapping screen for the module and product 3 10 ORACLE e Counterparty Bank This is picked up from the Settlement Instructions maintenance where it has been defined for the customer of the contract e Counterparty Account This is picked up from the Settlement Instructions maintenance where it has been defined for the customer of the contract e Activation Date This is considered to be the Credit Value Date e Clearing Bank Code This is derived from the Clearing Bank Code maintained for the branch e UDF 1 30 These user defined fields are derived mapping in the Settlements to Payment Product and UDF Mapping maintenance in the Settlements to Payment Product and UDF Mapping screen for the module and product The PC contract for the local currency transaction is generated if the LCY Message Preferences option chosen is Generate PC Contract and provided e Payment By option chosen for the contract is Local Clearing e Payment By option chosen for the contract is Message and cover is required and the Cover By option chosen is Local Clearing It is not possible to have both Payment By and Cover By options as Local Clearing 3 38 Correspondent Bank Maintenance You can specify these details
226. eld is entered The calendar basis field takes following values e Calendar Days To consider all days in a calendar e Branch calendar To consider only working days of a branch e Currency Calendar To consider only working days of a currency attached at product Specify the value for the field as Currency Calendar for CORE COR1 and B2B Scheme Products First Collection Receipt Days You can specify the number of calendar days to arrive at the latest date by which the first incoming collection transaction should be received by the debtor bank System will display an override message if the first collection which is determined based on the Direct Debit sequence type is not received within the First Collection receipt days from the activation date This is applicable only for incoming collection transaction First Collection Receipt Days You can specify the number of calendar days to arrive at the latest date by which the first incoming collection transaction should be received by the debtor bank wee ORACLE System will display an override message if the first collection which is determined based on the Direct Debit sequence type is not received within the First Collection receipt days from the activation date This is applicable only for incoming collection transaction Reject Account Details after Response Days Process Rejects After Response Days If you indicate that the outbound DD is to be rejected after the resp
227. en Credit transfer or Direct Debit forbidden on this type of account For example savings account or for regulatory reasons AG02 InvalidBankOperationCode Operation Transaction code incorrect invalid file format AMO1 ZeroAmount AOS AM02 NotAllowedAmount AOS AMO3 NotAllowedCurrency AOS T ORACLE AM04 InsufficientFunds Insufficient Funds AMO5 Duplication Duplicate collection Duplicate Entry AMO6_ TooLowAmount AOS AMO7 BlockedAmount AOS AMO9_ WrongAmount AOS AM10 InvalidControlSum AOS BEO1 InconsistentWithEndCustomer AOS BE04 Missing Creditor Address Account address invalid BE05 UnrecognisedlnitiatingParty AOS BEO6 UnknownEndCustomer AOS BEO7 MissingDebtorAddress AOS DT01 InvalidDate AOS EDO1 CorrespondentBankNotPossi AOS ble EDO3 BalancelnfoRequested AOS MD01 NoMandate No valid mandate Account blocked for direct debit by the debtor MD02 MissingMandatorylInformation Mandate Data missing or incorrect InMandate Account blocked for direct debit by the debtor MDO03 InvalidFileFormatForOther Operation Transaction code incorrect invalid ReasonThanGroupingIndicator file format MD04 InvalidFileFormatFor AOS GroupingIndicator MDO6 RefundRequestByEndCus Disputed Authorized transaction tomer MDO7 EndCustomerDeceased Beneficiary Debtor deceased MS02 NotSpecifiedReasonCustomer By order of th
228. ence Number from the adjoining option list Cancellation Originator Name Specify the name of the cancellation originator a ORACLE The system validates the cancellation originator name fro cancellation request with reason 03 Cancellation Originator Bank Specify the bank of the cancellation originator Note Specify either Cancellation Originator Name or Cancellation Originator Bank The cancellation originator bank is validated for cancellation request with reasons 01 and 02 The system defaults the following e Account Number e Cpty Account Number e Product Code e Customer Ac Branch e Customer Ac Currency e Customer No e Bank Code e Transaction Amount e Transaction Currency e File Ref No e Out Message Ref No e Out Msg Name e Out Msg Date e CSM Reject Reference Number e CSM Reject Code Recall Status The system updates the recall status Original Contract Reference Number Specify the original contract reference number If the cancellation request is initiated with reason as Duplicate transference then the system captures the original contract reference number Cancellation Commission Code Select the cancellation commission code from the adjoining option list Cancellation Commission Amount Specify the cancellation commission amount You have an option to select the contracts from the list of contracts While saving the selected contracts the system creates a reference number and inserts the contract
229. enter Query Customer No Customer Name Sequence Number Fields Maker Date Time Checker Date Time Mod No Record Status Authorization Status In the screen above you can maintain the following details e Customer e Sequence Number The important background processing jobs namely BOOK_INIT INIT MISC run on specific partitions only Multiple copies of these jobs are submitted for each of the partitions Only data pertaining to the partition applicable to the job is picked up in each of these copies ensuring parallel processing architecture If the number of partitions required is less than ten at an installation or for that matter no partitioning the contract table is created normally at installation without any partitioning The SEQ_NO for all of the contracts is always 1 and only one copy of each of the background processing jobs is present Processing Customer Consolidation Batch You can create a customer consolidation batch at file level based on the following parameters e Product Type of ORACLE 8 6 1 e Customer e Customer Account Branch e Customer Account e Account Currency e Customer Entry Date e Customer Entry Value Date e Consolidation Reference Number You can create more than one consolidation batch for a same customer consolidation reference based on the aggregation parameters The closure of the file consolidation batch can be either manually or automatically For automat
230. ention oe ORACLE 3 36 EEVVSSSBBBBBBBBx X Z Where e EE is S2 STEP2 e VV is the format version 02 XML e SSS is the three character service identifier SCT in this case or SDD e BBBBBBBB is the BIC 8 of the Direct Participant e X X optional up to 15 characters is to be used by the Direct Participant e Z indicates the type of the file where ICF SCT or IDF SDD The STEP2 central system generates files with X X fields as follows and the same will be done in FLEXCUBE YYMMDDHHMMSSNNN where YYMMDDHHMMSS indicates the file creation date and time and NNN an incremental number starting from 000 This is reset to 000 every time the DD date is changed 2 File Size parameters The STEP 2 clearing system allows a maximum of 500 files in one settlement cycle Each file can have a maximum of 500 message bulks System can include 100 000 transactions in each of the message bulks Files are generated for customer or bank with the following naming convention EEVVSSSBBBBBBBBx X Where e EEisPC e VV is the format version 02 XML e SSS is the three character service identifier SCT in this case or SDD e BBBBBBBB indicate the BIC the processing bank e X X optional up to 15 characters is to be used by the Direct Participant e YYMMDDHHMMSS indicates the file creation date and time NNN is an incremental number starting from 000 This is reset to 000 every time the DD date is changed P
231. ents exist and you have indicated that a DD agreement is required for the respective customer agreements Service Level Code The system displays the value of Service Level Code maintained at product level once you select the product code Collection Scheme Type The value for the field is defaulted from the selected product The value is specified in Payments and collections product definition screen PCDPRMNT The field is used to differentiate B2B scheme mandates from CORE COR1 scheme mandates Creditor ID Scheme ID Specify the value for the collection scheme types CORE COR1 and B2B The field value is validated against the format specified for Creditor ID Scheme ID field in Payments and Collections Creditors details maintenance PCDCREID While processing contracts for collection transaction the system will validate Creditor Scheme Identifier for the space between the positions 5 and 7 in Creditor Scheme Identifier If there are spaces then the system displays an error during manual contract creation in Payment amp Collection Transaction Input Then the incoming messages will be moved to Transaction Repair queue Positions 5 to 7 contain the creditor business code When the creditor business code is not used then value is set to ZZZ The creditor business code is not considered while checking for existence of the agreement Agreement Identification Specify a unique ID to identify the agreement between the credi
232. equest for Debit BOOK INIT XREF Reject of Incoming Payments BOOK INIT DRLQ CRLQ DCLG MISC Reject of Outgoing Payments BOOK INIT DRLQ CRLQ MISC Reverse of Incoming Collection BOOK INIT DRLQ CRLQ DCLG MISC Reverse of Outgoing Collection BOOK INIT DRLQ CRLQ MISC CONS Accounting Entries DRLQ Debit Entry Liquidation for Payments While triggering this event for Outgoing payment transactions the system posts a debit entry to the customer account In the case of incoming transactions the debit entry will be posted to the Clearing Suspense account Those contracts satisfying the following parameters will be picked up for processing based on their priority The contract is Active and Authorized The Debit entry date is prior to the current system date or is on the current system date The Initiation event has been processed successfully ORACLE e For transactions involving the customer account having a foreign currency the exchange rate population event has been completed and authorized e For outgoing transactions the customer entry has been consolidated if the transaction has been marked for consolidation Entries posted for Outgoing transfers will be as follows Accounting Role Dr Cr Indicator Customer Account Debit Internal Suspense Payable Credit Entries posted for Incoming transfers will be as follows Accounting Role Dr Cr Ind
233. es for Full Day Release End Time HR MN Specify the contract Release end time in hours and minutes for Full Day 4 2 4 3 Viewing Transaction Periods for Half Day Initiator Start Time HR MN Specify the contract initiation start time in hours and minutes for Half Day Auth1 Start Time HR MN Specify the contract Level 1 Auth start time in hours and minutes for Half Day Auth2 Start Time HR MN Specify the contract Level 2 Auth start time in hours and minutes for Half Day Release Start Time HR MN Specify the contract Release start time in hours and minutes for Half Day Initiator End Time HR MN Specify the contract initiation end time in hours and minutes for Half Day Auth1 End Time HR MN Specify the contract Level 1 Auth end time in hours and minutes for Half Day Auth2 End Time HR MN Specify the contract Level 2 Auth end time in hours and minutes for Half Day Release End Time HR MN Specify the contract Release end time in hours and minutes for Half Day 4 2 4 4 Viewing Incoming Payment Parameters When the system is unable to process an Incoming Payment because the target credit account in the message does not exist in the system it keeps such transactions aside by see ORACLE 4 2 5 posting them to a Repair Queue awaiting corrections to be made to the transaction This process of manual correction of an Incoming Payment is called Repair Allow Transaction Repair Check this box t
234. es for SCT and SDD are uploaded into Common Payments Gateway and based on the STP rules specified the SCT and SDD transactions are created in the PC module Creditor Bank Manual Creation The following are the features for manual creation The Local Instrument Value defaulted or entered for the transaction must be same as the Collection Scheme Type of the outgoing collection Product and is validated Static data for error code PC SVV O9N is used when Local Instrument Value and Collection Scheme Type doesn t matches If Local Instrument Value is not specified for outgoing collection then the system defaults the collection scheme type specified at the product with Local Instrument Type as Code If Collection Scheme Type is not maintained at product level then the system will not validate Local Instrument Value and Local Instrument Type The system validates such that for the Collection Scheme type B2B the selected customer must not be of type Individual During processing if Local Instrument Value is B2B and if Creditor s account is individual customer s account then system will display PC SVV 09M error oer ORACLE 5 24 e Ifthe creditor account is Joint account then the system checks the customer type of the main customer File Processing The following are the features for manual creation e For Incoming file processing of Outgoing Collection STP rule must be setup in such a way that Local
235. essage Name e Original Message Reference e Original Number of Transaction e Original Control Sum e Status e Reject Originator Bank e Reject Originator Name e Reject Code e Reject Code Additional e Reject Process Status 5 28 Handling Payment Status Report You can process the received payment status report automatically or manually You can process the payment status report for the following outgoing messages e Reject of Incoming Payments Pacs 004 e Positive Response to Payment Cancellation Requests Pacs 004 e Cancellation of Outgoing Payments Camt 056 e Negative Response to Payments Cancellation Requests Camt 029 e Pre Settlement Rejection of Incoming Collection Pacs 002 e Reject of Incoming Collection Pacs 004 e Recall of Incoming Collection Pacs 004 e Cancellation of Outgoing Collection Camt 056 e Reversal of Outgoing Collection Pacs 007 os ORACLE 5 28 1 Processing Pacs 002 Messages Payments The processing of Pacs 002 message received from Clearing Settlement Mechanism for SEPA Credit Transfer is as follows Pacs Pacs Pacs Pacs 002 for Outgoing Payments Pacs 008 sent by Debtor Bank On receipt of Pacs 002 for the Outgoing Payment from CSM the underlying Outgoing Payments will be rejected by processing pre settlement reject RJBS Accounting entries during debit liquidation and credit liquidation if posted will be reversed 002 for Cancellation of Outgoing Payments
236. essing could be aborted due to the DD mandate being closed or posting to the relevant account not being possible and so on Such aborted transactions are rejected automatically and the customer account is replaced by the Unsettle GL Account that you specify in the Product Category maintenance at ORACLE Maintaining error codes for automatic rejection Also it is possible to maintain a list of errors that would result in rejection of the incoming collection contract and in posting to the Unsettle GL You can maintain this list in the Auto Reject Mapping Maintenance screen You can invoke this screen by typing PCDERRCD in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Auto Reject Mapping Maintenance E New amp Enter Query Error Codes Error Code Error Description Reject Code Reject Reason Maker Date Time Checker Date Time Mod No Record Status Authorization Status In this screen you can map the relevant error codes to the appropriate reject codes If any of the errors mapped in this screen are encountered in processing the customer account in the incoming collection would be replaced with the Unsettle GL that you have specified in the Product Category maintenance The following error codes can be mapped Error Code Description PC BK064 Currency restriction occurred PC BK043 Customer account is closed PC BK045 Customer account i
237. ettlement Outgoing Message Number Amount Name Original Source Original Settiement Message Creation Reference Currency Date Original Payment Info 1D Redispatch Details Redispatch Number Redispatch Indicator Not Applicable Auto Redispatch Redispatch Reference Redispatch Required Redispatcn Date Split Details Events Charge Status ProjectDetaits DuplicationDetaits MIS Tax Input By Date Time You can capture the following details here Dispatch Details Dispatch This indicates whether the contract needs to be dispatched to clearing In case of incoming transactions dispatch is not allowed If you do not specify this after product resolution the transaction acquires the specification defined for the product Redispatch Required Indicate if this outgoing collection transaction needs to be redispatched if rejected Dispatch Date This is the date on which the transaction will be sent for dispatch If you do not enter a date it will be derived from the activation date by adding the working days to the value of dispatch oe ORACLE days specified for the product The pre post cutoff values will be used based on the cutoff status of the transaction Recall Message Details Message Creation Date The system displays the message creation date Recall Message Reference The system displays the recall message reference number Recall Message Name The system displays the recall message name Recall File
238. ew FX linkage is created the system creates LINK in FX to decrease the unutilized amount The transaction amount is increased the system validates if the outstanding amount of the linked FX forward contract would cover the increased amount If it is then the system triggers DLNK event to delink the old linkage FX with old amount increase the unutilized amount followed by LINK event to create the new linkage FX with new amount and decrease the unutilized amount The transaction amount is decreased the system triggers DLNK event to delink the old linkage increase the unutilized amount This is followed by LINK event to create the new linkage and decrease the unutilized amount The Customer Entry Date is modified the system validates if the new Customer Entry Date is greater than or equal to the Option Date and less than the maturity date min of the Bought Value Date and Sell Value Date If it is then the DLNK event will delink the old linkage FX with old Value date and increase the unutilized amount This is followed by LINK event to create the new linkage FX with new Value date and decrease the unutilized amount e Ifin FX linked PC Transaction the Customer or the Currency is modified then the system will not allow you to save transaction unless the linked FX Contract is removed from the PC Transaction e Reversal of FX linked PC transaction before liquidation will decrease the FX contract utilization However if the
239. ew provides a snapshot of the fea Chapter 2 tures of the module Maintaining Information Specific to the Payments and Collections Chapter 3 describes the procedure to set up reference information related to the module 1 1 ORACLE 1 5 1 6 Defining Attributes Specific To Payments And Collections Products talks Chapter 4 about defining the attributes specific to setting up a Payments and Collec tion product Chapter 5 Processing a Payment or Collection Transaction deals with the sequence p of events involved to process Payments and Collection transactions Levying Charges on Payments and Collections Transactions provides a Chapter 6 snapshot of the charges applicable for Payment and Collection transac tions Outgoing Payments Workflow explains how you can use the outgoing pay Chapter 7 a ments workflow facility Chapter 8 Payments and Collections Operations and Processes explains the opera p tions and background processes for the Payments and Collection module Annexure A Accounting Entries And Advices acquaints you with the Chapter 9 accounting entries and advices generated in the Payments and Collec tions module Chapter 10 Reports explains about the types of reports that can be generated for this module Function ID Glossary has alphabetical listing of Function Screen ID s used Chapter 11 SEE in the module with page references for quick navigation Related Documents You
240. fault the name and the address lines and counterparty information fields as maintained for that account If at the time of selecting oe ORACLE Counterparty Account Bank Code is null then the Bank Code and Name will also appear by default Counterparty Name You can enter the name of the counterparty Counterparty Address You can specify the address of the counterparty involved in the contract You can specify up to five lines of address information Counterparty Information If you need to specify other information regarding the counterparty of the transaction free format 35 character text fields are provided with appropriate labels applicable for your installation You can specify the counterparty information in these fields Note The country information is captured to enable Mantas to analyse the transactions for pos sible money laundering activities For more details on Mantas refer Mantas interface document Specifying Transaction Details Txn CCY Enter the currency for the transaction You can click on the adjoining option list to choose from a list of valid currency codes maintained in the system Input to this field is mandatory If the product code is input then the system will display the currency linked to the product in this field You will not be able to change the defaulted value Actual Amount Specify the actual transaction amount in local currency Remarks Specify any requisite narrative
241. fer section Maintaining Clearing Network details in the chapter Maintaining Information specific to the Payments and Collections Module of this User Manual Common Payment Gateway Parameters To handle SEPA transactions the following maintenance needs to be done as part of maintaining the Common Payments Gateway parameters e Message types for SCT and SDD messages like pain 001 Customer Credit Transfer Initiation pain 008 Customer Direct Debit Initiation pain 007 Payment Reversal pacs 008 Customer Credit Transfer pacs 003 Customer Direct Debit pacs 007 Payment Reversal pacs002 Payment status report pacs 004 Payment return refund one ORACLE e Aunique message name to distinguish and identify SCT and SDD messages For more details on how to maintain Common Payments Gateway Messages Type refer section Maintaining Common Payment Gateway Message Parameters in the chapter Processing of Non SWIFT Incoming Payment Messages of the Funds Transfer User Manual Queue Parameters To handle SEPA transactions the following maintenance needs to be done as part of maintaining the Queue details e The Queue name for SCT and SDD messages For e g PCINSCT e The Queue Description For e g Incoming SEPA Credit Transfers e The code of the SCT and SDD messages that will be routed to this queue For e g PAINOO1 For more details on how to maintain Queues r
242. fied Accounting Roles The following list contains details of the accounting Roles that are applicable to the PCs you can process at your bank A ala Description Role Type INTSUSREC Internal Suspense Receivable Asset CLGSUSREC Clearing Suspense Receivable Asset INTSUSPAY Internal Suspense Payable Liability CLGSUSPAY Clearing Suspense Payable Liability CLGVOSTRO_ Clearing VOSTRO this could be used instead of using Settlement CLGSUSPAY and CLGSUSREC if a VOSTRO has been designated to be used and not a suspense GL CHG1_INC Charge 1 Income Income CHG2_INC Charge 2 Income Income CHG3_INC Charge 3 Income Income CHG4_INC Charge 4 Income Income v2 ORACLE 9 2 9 2 1 CHG5_INC Charge 5 Income Income COMPACC Compensation Account for Recall Transactions X User Defined CHARGEACC Charge Account for Reject Recall Transactions X User Defined P2PCUSTTFR Customer Debit for P2P Payments Liability P2PTESTEX Test transaction for P2P Payments Expense Product Type and Event Code and Accounting Entry combinations For your convenience we have listed the Events and Accounting Entries which need to be defined for the various product types that can be maintained for this module Events for Payment and Collection Products The Events that you need to set up for the various types of Payment and Collection products are as follows
243. field Modifying Window Period Information In the Payment Window Period Modification screen you can modify the window period information for a product for a branch for the current process date The window periods maintained in this screen is applicable only to the current process date aM ORACLE You can invoke this screen by typing PCDPRDAT in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Payment Window Period Modification E New amp Enter Query Branch Code Process Date ETI Product Code Payment Type Initiator Start Time HR MN End time Authorization 1 Start Time Authorization 1 End Time Authorization 2 Start Time Authorization 2 End Time Release Start Time HR MN Release End Time HR MN Maker Date Time Checker Date Time Mod No Record Status Authorization Status Branch Code Specify the branch code Product Code Specify the product code Process Date Specify the process date Payment Type The system will display the product type of the selected product Initiator Start Time Specify the contract initiation start time in hours and minutes for Full Day End Time Specify the contract initiation end time in hours and minutes Auth Start Time Specify the contract Level 1 Auth start time in hours and minutes for Full Day Auth1 End Time Specify the contract Level 1 Auth end time in hours and minutes for Full Day Auth2
244. for a Payment Collection Product When maintaining a Payment Collection product you can define the manner in which charges should be levied on transactions processed under the product You can build your specifications in the Products Condition Maintenance screen Invoke this screen by clicking 6 1 ORACLE Expression button in the Payments and Collection Product Maintenance PCDPRMNT screen Products Condition Maintenance Product Code Product Description Product Type SetTwo Set Three Set Four Set Five Product Charge Details 1 Of 1 E Serial Number Condition Resultant Charge Type Resultant Charge Component Amount Rate A Element Functions Operators Logical Operators For each set of conditions that you build you can indicate whether the resultant charge must be a flat amount a percentage of the transaction amount or computed as a charge component such as a charge rule or a charge class You must indicate this in the Resultant Charge field by choosing from the drop down list For details about building charges as components such as charge rules and charge classes refer the section Building Charge Rules found later on in this chapter The following example illustrates the manner in which you can build your charge specifications for a product For example assume you would like to define the following charges for a product linked to the clearing network e A netwo
245. for the Original Outgoing Collection will revert the status of the Outgoing Collection prior to reversal processing REVP This enables Outgoing Collections to be reversed further Pacs 002 for Pre settlement Rejection of Incoming Collection Pacs 002 sent by Debtor Bank e Reject of Incoming Collections are generated when Incoming Collection is rejected by processing pre settlement rejection RUBS event e On receipt of Pacs 002 for pre settlement Reject of Incoming Collection the underlying Reject of Incoming Collection contract will be rejected by processing pre settlement reject RJBS event e RJBS event on pre settlement Reject of Incoming Collection Will mark the contract as rejected Will populate new fields CSM Reject Code CSM Reject Detail and CSM Reject Reference Number at contract level with the received reject code reject description and reject reference number from Pacs 002 Will reactivate the Original Incoming Collection by processing Reactivation Event e The reactivation event for the Original Incoming Collection will revert the status of the Incoming Collection prior to pre settlement rejection event processing RJBS This enables Incoming Collection to be rejected further Pacs 002 for Rejection of Incoming Collection Pacs 004 sent by Debtor Bank e Reject of Incoming Collection are generated when Incoming Collection is rejected by processing post settlement rejection REJT event e On r
246. fy the International Bank Account Number of the Creditor Creditors Name Specify the creditor s name Faa ORACLE 3 20 Address 1 2 3 and 4 Specify the complete address of the Creditor Country Select the country from the adjoining option list Maintaining DD Agreement Details for Creditors This agreement is maintained by your bank on behalf of customers who participate as creditors in a direct debit transaction The details are maintained in the Creditor Direct Debit Agreement Maintenance screen You can invoke this screen by typing PCDCRAGT in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Creditor Direct Debit Agreement Maintenance H save Customer Service Level Code Product Fade la Collection Scheme Type I Product Description 2 Creditor ID Scheme ID p Customer No Agreement Id Customer Name Creditor Reference Code Customer Account Branch Account No Currency Counterparty Details Counterparty Name Counterparty Account Number Address 1 Counter Party Bank Code azl Address 2 Bank Name Kl Address 3 Date Of Signature E Address 4 Country HA Transaction Details Validity Details E Agreement Cancellation Effective Date E Charge Expiry Date E2 Charge Reference Number Agreement Status Active E Transaction Type z pa Amendment Reason Payment Details
247. greement details are being maintained The agreement details will be validated only for transactions involving the product selected in this field Collection Scheme Type The value for the field is defaulted from the selected product The field is used to differentiate B2B scheme customer agreements from CORE COR1 scheme customer agreements Customer In this field you will select the name of the customer taking part in the agreement The ALL option is available for all payment product types and for recall and reject collection product types An incoming outgoing DD or RFD may be rejected or recalled applicable only to DDs for various reasons Thus a reject or recall transaction involving the appropriate reject or recall product is in effect the child transaction of the corresponding incoming or outgoing parent transaction At the time of processing the parent transactions the system will perform the necessary validations When processing a reject or recall child transaction you will need to specify the Original Collection Reference Number of the parent transaction as mandatory information The system will use this number to associate the child transaction with the appropriate parent transaction No further validations will be performed on the child transaction In other words the agreement details for a reject or recall transactions will a8 ORACLE necessarily be the same for all customers and not specific to a
248. h 9 Reset D Clear All Case Sensitive Consolidation Status Customer Number Account Number Account Currency Amount Customer Entry Value Date Customer Entry Date E Product Code Account Entry Reference Exception Queue Number Customer Account Branch Transaction Count Product Type Consol Reference Records per page 15 v 10f1 Consolidation Status Customer Number Account Number Account Currency Amount Customer Entry Value Date Choose any of the following options in the Consolidation Summary screen e Search Allows for querying of specific records e Reset Resets the required details 5 14 Consolidation Exception Queues There could be many reasons why rejections can occur during processing of payment and collection transactions for consolidation Exceptions are raised in respect of transactions that are rejected Such transactions which are not considered for consolidation due to rejection can be viewed in the Consolidation Exception Queue You can invoke this screen by typing PCSCNLE in the field at the top right corner of the Application tool bar and click on the adjoining arrow button Jap ORACLE Here you can manually verify the rejections To confirm a rejection click Reject button This operation must be performed before the end of day cycle can be run Payments amp Coll
249. h Ez City of Birth Counterparty Birth City Customer Birth Country az Counterparty Birth Country laz Customer Identification Value Counterparty Identification Value Scheme Name Type x Scheme Name Type Scheme Name Value la Tal Scheme Name laz Customer ID Issuer Counterparty ID Issuer Maker Date Time Checker Date Time Mod No Record Status Authorization Status You must specify the following details e The product category for which the data is being maintained e The Creditor ID of the customer for whom the database is being maintained e The ID of the agreement in the context of which the learning database is to be used e Details of the customer such as the name and address Customer Number and Account Number as well as any user defined fields for customer information e The customer identification details like identification type identification value other identification type issuer city of birth country of birth e Details of the counterparty such as the name and address Account Number and Bank Code as well as any user defined fields for counterparty information e The counterparty identification details like identification type identification value other identification type issuer city of birth country of birth e The user defined fields applicable for the product category in which the learning database would be used Customer BIC ID Specify the Bank Identification Code for the Customer
250. he BIC codes for the clearing network will be derived using the Nostro Account so maintained Specifying the UDF Details Click Fields button to provide values for the UDFs associated with the screen User Defined Fields Details F Field Name Value Description Maintaining Redirection Details for a Bank On occasions transactions involving a specific bank may have to be redirected to another bank In the Bank Redirection Maintenance screen you can maintain the redirection details ae ORACLE for a bank You can invoke this screen by typing PCDBKRED in the field at the top right corner of the Application tool bar and click on the adjoining arrow button Bank Redirection Maintenance E New amp Enter Query Bank Redirections Bank Code Bank Name To Bank Redirect Bank Name Maker Date Time Checker Date Time Mod No Record Status Authorization Status In this screen you can specify From Bank Select the bank for which you are maintaining redirection details To Bank Select the bank to which transactions should be redirected All transactions involving the bank for which you are maintaining redirection details will be automatically redirected to the bank you specify here Note You can maintain redirection details only for banks maintained in the Bank Directory screen on ORACLE 3 6 Maintaining Clearing Network Qualifier Details In the Clearing Ne
251. he accounts associated with the chosen currency code will be displayed in the option list provided in the adjacent field Outgoing Account In case of outgoing transactions received over the network the account that you indicate here will be credited by default Description In case of TARGET 2 clearing network the default incoming account will be the primary nostro account with the central bank that should be credited while processing an outgoing TARGET 2 payment 39 ORACLE 3 5 1 3 5 2 Note You are not allowed to maintain the same default incoming or outgoing accounts for differ ent networks Dispatch Accounting Parameters To consolidate the accounting entries such that the Clearing Nostro GL is netted to post single debit and credit entries for each file that is dispatched you will need to identify the Clearing Nostro account through the Dispatch Accounting Parameters section in the Clearing Network screen Branch Select the appropriate branch code and the currency code from the corresponding option lists available Nostro Account You can maintain different clearing Nostro accounts for the above combination of branch and currency Outgoing and Incoming Transaction Code After you identify the nostro account to which the consolidated entry will be passed for all Dispatch entries you have to select separate transactions codes against which all the incoming and outgoing transactions are to be tracked T
252. he addresses of the bank its stage of transition to the IBAN Format and the various clearing networks supported by the bank You can also indicate whether the bank supports DD and RFD transactions Clearing Network Maintenance You can define the networks such as SORBNET over which you communicate with banks and other financial institutions for transactions Bank Redirection Maintenance On occasion the transactions involving a specific bank may have to be redirected to another bank You can capture this information in the Bank Redirection Maintenance screen Account Redirection Maintenance The transactions involving a specific account in Oracle FLEXCUBE may have to be redirected to another account maintained in Oracle FLEXCUBE You can capture this information in the Account Redirection Maintenance screen Upload Source Maintenance You can maintain the different sources from which you receive transactions as part of the Upload Source Maintenance The details of such transactions are uploaded from such external sources into Oracle FLEXCUBE ee ORACLE Upload Source Parameters Maintenance You can define certain parameters for a product category and upload source combination As part of the parameters you specify for the combination you can specify details such as the transaction retention period and if transactions should be automatically authorized etc Customer Station Maintenance In the Customer Station Maintenance screen
253. he creditor from the drop down list Following are the options available in the drop down list e Private Identification Scheme Identification Type Specify the scheme identification type of the creditor from the option list Scheme Identification Value Specify the scheme identification value of the creditor Scheme Type Specify the scheme type of the creditor Original Creditor Scheme Details Identification Select the scheme identification code of the original creditor from the drop down list Following are the options available in the drop down list e Private Identification Creditor Name Specify the name of the original creditor Identification Value Specify the scheme identification value of the original creditor oe ORACLE Scheme Type Specify the scheme type of the original creditor Other Details Collected Amount Specify the collected amount Related Transaction The system displays the related transaction Response Date Specify the date beyond which an incoming collection transaction cannot be rejected If you do not specify this the date is picked up from the customer agreement Response Advice Required Indicate whether response advice needs to be sent for this collection transaction By default the system picks up this specification from the customer agreement Response Advice Basis Specify the response advice basis from the adjoining drop down list the options are e Response Date e Event Date
254. he end date e Amount Block Number e Branch Code e Account Number e Beneficiary s Email ID e Beneficiary s Telephone e Beneficiary s Facebook ID The end date for the beneficiary registration would be derived based on the Registration Period in Days parameter value from P2P payments parameters level The derived end date is logged into P2P Payment Beneficiary Registration Queue and will be updated as expiry date in Amount Block Input function Exception Details Reject Code The reject code if any that was specified for rejection of the transaction is displayed here Reject Detail The reject reason if any corresponding to the reject code is displayed here oe ORACLE Reject Code Additional This is the reject reason for the reject messages This will be used in case the reject reason is not covered by available ISO reject codes Compensation Amount Specify the amount that the debtor bank has to receive from the creditor bank It should always be Euro EUR Their Reference This is the reference number of the counterparty bank for collections for instance incoming collections This is the reference that would be sent back when any responses are sent back to the counterparty bank Original Collection Reference If you are rejecting or recalling a collection transaction you must specify the reference number of the original collection transaction CSM Reject Reference No The system displays the CSM reject
255. he response date of the transaction Rejected Incoming Collections The advice is generated while processing Collection of Rejection REJT event for the transaction Rejected Approval of Incoming Request for Debit Outgoing Payment The advice is generated while processing Collection of Rejection REJT event for the transaction e Closure Advice This advice is generated for following type of transactions Outgoing Request for Debits without Re dispatch generated while processing the Collection Closure CLOS event of the transaction Outgoing Request for Debits with Re dispatch generated during contract re dispatch RDSP e Recall Advice Based on the product advice setup this is generated for the following type of transactions while processing the Contract Recall RECL event a9 ORACLE 9 4 9 4 1 Outgoing Direct Debit Incoming Direct Debit Credit Acknowledgement Messages For Outgoing Payments If we receive the Credit Acknowledgement message for our outgoing payment contracts then system will update the message status of the corresponding outgoing payment contract as CD Credit Done For Incoming Payments The system will generate the outgoing Credit Acknowledgment N10 message for incoming payment contract After processing the CRLQ event system will generate the Credit Acknowledgement Message for the incoming payment contract This process will group the number of inco
256. he transaction Error ER The receiver could also log an error in respect of a message due to technical problems for instance In such a case the message is said to be in error and an appropriate log would be maintained to document the error This situation could also arise when an error is logged in respect of a canceling message in which case the transaction acquires a Cancel Error CE status fl ORACLE 7 1 1 1 7 1 1 2 7 1 1 3 Note A message that has been timed out TO or is in error ER can be re sent in which case it moves back to being in waiting WT As mentioned earlier Oracle FLEXCUBE provides the facility to track the different stages enumerated above The facility is known as the Outgoing Payments Workflow and is only available for transactions processed using a product category for which the workflow has been enabled Enabling the Outgoing Payments Workflow In order to enable the outgoing payments workflow for payments processed using an outgoing payments product you must specify the following Outgoing Payments Product Definition You must select the Outgoing Payments Workflow option as a product preference when you are defining the product Specifications for Outgoing Payments Workflow in the Oracle FLEXCUBE Clearing Gateway Outgoing payments are dispatched through the Oracle FLEXCUBE Clearing Gateway which is an interface provided by Oracl
257. his box to indicate whether the transaction must be redirected from the customer or counterparty bank to any other bank Auto Response Indicate if a system generated response is required for the collection transaction Account Redirected Check this box to redirect the transaction from customer or counterparty account to any other account Auth Reject Remarks The system displays the authorization reject remarks Payment Reference Station ID The system displays the station identification Clearing System ID Specify the clearing system identification Priority The system displays the priority order of the messages Source Code The system displays the source code Event Details Last Event Code The system displays the last event code Next Event Code The system displays the next event code Next Event Date The system displays the next event date Payment Split Details You can maintain the following payment split details here Split Number Specify a valid number for the payment split Split Transaction Reference Specify a valid transaction number for payment split Split Indicator Select a valid indicator for the payment split from the adjoining drop down list The list displays the following values e Not Applicable e Parent 2 ORACLE 5 2 4 e Child Invoice Split Required Check this box if you need to invoice the split required Specifying Collection Details
258. ic closure of file consolidation batch e Customer entry value date for all transactions in a batch should be the system date e All the transactions should be in processed status in CPG browser for the same file reference number e All the transaction should be consolidated in PC module for the same file or batch reference number e The transactions should not be in TR queue under the same file reference number and for the same customer entry date While closing a consolidation batch manually the system displays an error message if e The customer entry date has to be the transaction date for the transactions under the consolidation batch e If there are any pending transactions to be consolidated for the same file reference number Processing of Logging the Batch into Consolidation Summary Screen During transaction processing the transactions with Customer Consolidation Across Products as Yes will be grouped under a consolidation batch and get logged into the existing Consolidation summary screen This consolidation batch will have the product code value as Null The CONS event will be triggered for all transactions that are logged in to Consolidation Summary screen The Customer consolidation batch at file level shall be created based on the following parameters e Product Type e Customer e Customer Account Branch e Customer Account e Account Currency e Customer Entry Date e Customer Entry Value Date e Consolid
259. ically by the system ASCII Handoff Required For contracts involving the product and customer combination you can specify whether the contract information is to be written into handoff tables to be picked up or referenced by the external agency oa ORACLE 3 18 1 Collection stmt Required Collection statements can be generated for contracts involving the customer and product combination if indicated in this screen Response Advice Required You can also choose to generate a response advice for Incoming Outgoing DD and RFD transactions If selected one of the following advices will be generated e Approval An advice of approval will be sent to the creditor s bank if the Incoming DD RFD is approved by the debtor s bank e Reject Reject of an Incoming DD RFD will result in the generation of the reject advice This will be from the debtor s bank to the creditor s bank e Closure A closure advice is sent when the transaction is closed by the system If you have opted to generate a response advice you need to indicate when the advice needs to be sent You can send the advice on the event date or on the response date Basis Select the basis for response You can select any one of the following options e Response Date e Event Date Other Details Creditor ID Scheme ID For outgoing collections initiated by the customer you can specify the creditor ID of the customer Whenever an outgoing transaction involves an outgo
260. icator Clearing Suspense Receivable or Clearing Vostro Debit Internal Suspense Receivable Credit Note If the entry dates of the debit and credit legs are the same the system will not pass the entry to the Internal Suspense account Also for transactions marked for client entry con solidation a single debit entry to the customer s account will be passed The system gen erates a new reference number for the consolidation and the accounting entries will be passed using this reference number Entries posted for Debit Notification will be as follows Accounting Role Dr Cr Indicator Interbank Receipt GL Debit Intermediary GL Credit Entries posted for Credit Notification will be as follows Accounting Role Dr Cr Indicator Network GL NOSTRO Debit Intermediary GL Credit If the contract is moved to release queue for DRLQ event then the following account entries are passed Event Account Debit Credit Amount DRLQ Customer Account Debit Transaction Amount DRLQ Intermediary GL Credit Transaction Amount oa ORACLE CRLQ Credit Entry Liquidation for Payments During this event a credit entry will be posted to the Internal Clearing Suspense account for outgoing transactions The entry will be posted to the customer account for incoming transactions Based on their priority the system picks up all active and authorized contracts if e The credit en
261. icking O button the system validates the access rights of the selected branch and Fast Track Input E new enter query Product Code Product Category Product Type an ustomer Details Customer Bank Code Account LCF Customer Account No Customer Address 1 Customer Address 2 Customer Address 3 Customer Address 4 Name ounterparty Details Counterparty Bank Code Counterparty Account Number Counterparty Name Payment Details 1 ransaction Details Transaction currency Activation Date LCY Currency Local Currency Equiv Amount Contract Reference Network Custom Reference Number Account Entry Reference Number Collection Type Rfd Type Customer No Customer Account Branch Customer Account Currency Bank City Virtual Account Virtual Account Name Resolve Physical Account Payment Details 2 Agreement ID Bank City Actual Amount Exchange Rate FX Contract Reference Cutoff Status Exception Queue Pre Cutoff Stat MIS Split Details Maker ID Checker Id Contract Status Release Time Checker Date Stamp Authorization Status function for the user If you don t have appropriate rights on the selected branch and function the system will display an error message If you select a valid branch the system updates the same as transaction branch and the transaction will be posted for this branch 5 42 ORACLE In the Fast Transaction Input screen yo
262. ield If Scheme Name type is C then the Scheme Name can be selected from LOV and can have one of the values mentioned in value list depending on Organization Identification or Private Identification If the Scheme Name Type is P then you can enter the value for the field Counter Party Date of Birth Specify the date of birth of the Counter Party City of Birth Specify the city of birth of the Counterparty This is enabled and is mandatory if you have selected identification type as Date and Place of birth Country of Birth Select the country of birth of the Counterparty from the option list This is enabled and is mandatory if you have selected the identification type as Date and place of Birth Maintaining P2P Beneficiary Details You can maintain peer to peer payment transactions by registering beneficiary details in the P2P Beneficiary Maintenance screen P2P beneficiary maintenance can be done for any of the following combinations e Email ID e Email ID and Telephone e Email ID and Facebook ID e Email ID Telephone and Facebook ID You can maintain same beneficiary account details with multiple email IDs or multiple combinations of Email ID Telephone and Facebook ID You can invoke this screen by typing PCDPTPBN in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button oe ORACLE P2P Beneficiary Maintenance E New Enter query Beneficiary Ide
263. ield from the adjoining list The list contains the GLs The field can be used for the following e Recall of Incoming Collection e Recall of Outgoing Collection e Reject Of Incoming Payment e Reject Of Outgoing Payment Rejection Details Restrict Customer Rejection Specify the value for the field The field has two options e Yes System doesn t allow beneficiary initiated reject process e No System allows beneficiary initiated reject process default Restriction of beneficiary originated reject transactions are achieved by checking the Restrict Customer Rejection parameter at product of type Incoming Payment Note System throws an error message if Reject Originator name is entered at reject process when Restrict Customer Rejection is checked at product level oe ORACLE Cancellation Details Days Specify the number of days within which the request for cancellation can be initiated for payment and collection Days Basis Select Working or Calendar to indicate whether the cancellations days computation is based on Working or Calendar Days Calendar Days Basis Select Branch Calendar or Network Calendar for computing the maximum cancellation request date and maximum cancellation request for duplicate transfer Cancellation Acceptance Details Acceptance Days for Bank Specify the number of days within which the incoming cancellation request with bank error needs to be accepted Accept Da
264. iginal Settlement Amount e Value Date e Currency e Status e Error Reason e Customer Reference Click on View button to view the complete details of received payment status report in a Common Payment Gateway detailed screen Click on Process Reject to process the received payment status report Once the payment status report is processed successfully the status is changed to Processed In case of failure during payment status report processing the error reason will be populated with the corresponding error and the status will be changed to Repair Click on Suppress to suppress the received payment status report Once the payment status reportis processed successfully the status will be changed to Suppressed This button option can also be used to suppress the Repair payments status reports Click on Retry to retry the failed payment status reports which are in R Repair status Payment Status Reports that are failed during processing can be retried using this button option Once the payment status report is processed successfully the status will be changed to Processed Note that EOD Processing will stop if any received payment status report exists with status other than Processed and Suppressed Maintaining Payment Gateway Message Bulks You can maintain all bulk messages in the Payment Gateway Message Bulk screen To invoke this screen type MSSBLKBR in the field at the top right corner of the a
265. ility exceeds the specified limit as a result of a contract an exception is raised and the contract is moved to the Credit Exception Queue You can Confirm or Reject these overrides in this screen 2 ORACLE You can invoke this screen by typing PCDCRXSQ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Credit Exception Queue amp Enter Query 1 Of 1 E E Product Code Customer Number AccountNumber AccountBranch Customer Account Currency Customer Bank Code Transaction Count Total Ar PA T Reject Detai i The contracts are grouped on the product code and customer account A consolidated amount for each combination is also furnished The information is sorted queried along the following criteria e Product Code e Customer Number e Customer Account e Customer Account Branch e Customer Account Currency e Customer Bank Code e Total Amount Local Currency e Total Amount Account Currency e Limit Amount Account Currency Choose any of the following options by clicking on the appropriate buttons in the toolbar in the Credit Exceptions Queue screen e Detail Choosing this option allows you to drill down to the details of a contract for the combination of Product and Customer Account The detailed view consists of two portions The upper half of the window displays all contracts where consolidation is not required
266. in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Debtor Direct Debit instructions History E Execute Query Customer ID Version No Customer Name Restrict All DD Transactions Guslomer Account No of a debiting customer Restrict All Future DD Customer Account Branch Transactions of a debiting Customer Ac Ccy customer Collection Scheme Type CORE Restriction From Date Restricted Details Restriction Type Allowed Disallowed 10f1 10f1 10f1 F Creditor ID Scheme ID Mandate Id E Creditor IBAN Document RefNo Suffix Reference Maker Date Time Mod No Checker Date Time Record Status Authorization Status Version Number This field displays the corresponding version number For further details refer the section Maintaining Debtor Direct Debit Instructions in this user manual 3 44 Viewing Debtor Direct Debit Instructions History You can view the history of Instructions records pertaining to particular Debtor using Debtor Direct Debit Agreement History Summary screen You can invoke this screen by typing PCSIDRHS in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button 3 103 ORACLE Debtor Direct Debit instructions History Summary E gt Search C Advanced Search Reset Y Clear All X Case Sensitive Authorization Status v Record Status v Customer ID las Customer Ac
267. ing Generation of the Local Payments Contract for Local Currency Transac tions In cases where outgoing payment transactions need to be generated for local currency transactions for a module as specified in the LCY Message Preferences in the Branch Parameters the payments transaction is created with the following fields e Product Category This is derived from the mapping in the Settlements to Payment Product and UDF Mapping maintenance in the Settlements to Payment Product and UDF Mapping screen for the module and product e Source This is derived from the mapping in the Settlements to Payment Product and UDF Mapping maintenance in the Settlements to Payment Product and UDF Mapping screen for the module and product e Branch This is the branch from which the contract was entered e Customer Branch The branch where the customer account resides derived from the Settlement Message Details maintenance for the contract e Counterparty Name This information is picked up from the counterparty details in the Settlement Instructions maintenance e Their Reference Number This is the same as the Contract Reference Number of the entered contract e Customer Account and Customer Entry Value Date This is the debit account of the contract For every amount tag an offset amount tag is defined During the generation of the contract the debit account and the debit value date are picked up for the ESN and Contract R
268. ing Gateway e No exception has occurred for the contract e Dispatch is automatic e Contract has not been dispatched as yet e Dispatch date is the same as or earlier than the system date If the Dispatch Accounting option has been enabled for PC products the system posts the netted consolidated entry on the Debit Liquidation Date or Credit Liquidation Date of the PC contracts involving the product Against each dispatch file reference number a consolidated credit and debit entry will be passed to the Nostro account and multiple debit and credit entries are passed to respective suspense accounts Incoming Payments Outgoing Collections Reject Of Outgoing Collections and Recall of Outgoing Collections product types are processed on the Debit Entry Liquidation date Similarly Outgoing Payments Incoming Collections Reject of Incoming Collections and Recall Of Outgoing Collections are processed on the Credit Entry Liquidation date For rejected DDs the entries are posted into Nostro Account as Contra entries In respect of contracts whose dispatch date is the same as the application date involving Outgoing Collection Products who s clearing mode is either external or internal clearing the dispatch event is triggered before the DRLQ CRLQ events Note If no dispatch has occurred during the course of a business day for the contracts with dis patch date as the current business day for the contracts having dispatch date as the cur
269. ing instruction This is a display only field Instructed Bank This indicates the receiver bank of the incoming instruction This is a display only field Settlement Method This indicates the settlement method used to settle the incoming transaction This is a display only field Note While you are processing a transaction you have the option of retrieving details based on Product Category Counterparty bank and Account combination by clicking the History but ton Reactivate Event Processed This is a display field that indicates that the contract is re activated on rejection of rejection process oe ORACLE 5 2 10 5 2 11 5 2 12 Specifying the MIS Details The MIS details for the contract can be captured through the MIS screen Click the MIS button from the PC Transaction Input screen to invoke the Transaction MIS Details screen If you do not specify MIS details for a transaction it acquires the MIS specifications made for the product under which it is processed Viewing Event Details All events overrides and accounting entries triggered by the user who processes the transaction during its life cycle are logged in the PC Contract View Events screen which you can invoke by clicking Events button in the PC Transaction Input screen Events El Serial Number EventCode Event Description EventDate Contract Status Collection Status Message Stati A Accounting E
270. ing product and customer combination the system defaults the creditor ID as mentioned in the customer agreement Debtor Category For outgoing collections initiated by the customer you can specify the debtor categories with which the customer deals Whenever an outgoing transaction involving an outgoing product and customer combination the system defaults the preferences maintained for the debtor category that has been specified in the customer agreement Automatic Cancellation of the Mandate For a given mandate if there are no transactions for 36 months system automatically cancels the mandate so that no further transactions are processed for this mandate The End of Day batch in Oracle FLEXCUBE which is run daily as part of EOD checks the mandate details maintained in Payments amp Collections Debtor DD Agreements screen System checks is the latest Effective Date for any mandate record is earlier than the current application date by more than 36 months and the Mandate Status is not Cancelled In this case Mandate Status is updated to Cancelled and the Effective Date is updated to the current processing date Also Amendment reason is updated as AUTO CANCEL For a mandate record if the Effective Date is either not earlier than 36 months or the Mandate Status is maintained as AUTO CANCEL then this record is skipped by the system For more details on End of Day
271. 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 failsafe 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 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 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 Corporati
272. ining error codes for automatic rejection in the chapter Maintaining Information specific to the Payments and Collections Module of this User Manual Reject Code Maintenance You need to maintain the ISO reject codes that are used for SCT rejects using the PC Reject Code screen For more details on maintaining reject codes refer section Reject Code Maintenance in the chapter Maintaining Information specific to the Payments and Collections Module of this User Manual STP Rule Maintenance To handle SEPA transactions the following maintenance needs to be done as part of maintaining the STP Rule maintenance one ORACLE e Rules for incoming SCT and SDD messages e Message queue for the incoming SCT and SDD messages e The PC product category will be picked up from the Product mapping maintenance based on the queue evaluated in the rule maintenance e STP Preferences e Post upload status and preferences when the uploaded file is invalid Based on the above mentioned maintenance the STP rule is set for the following e Outgoing Payments e Incoming Payments e Reject of Outgoing Payments e Reject of Incoming Payments e Outgoing Collections e Incoming Collections e Reject of Outgoing Collections e Reject of Incoming Collections e Recall of Outgoing Collections e Recall of Incoming Collections e Reversal of Outgoing Collections e Reversal of Incoming Collections PC Beneficiary Maintenance The counterparty
273. initial recall e Anevent RACT will be logged for the original Incoming Collection in the contract events data store e Once the original Incoming Collection gets re activated the reversal transaction is retried in Transaction Exception screen PCSREXQ Case 6 Receipt of Pacs 004 Recall from Debtor Bank for Outgoing Collections for which Pacs 007 is already sent by Creditor Bank e When CSM processes Pacs 004 for Outgoing Collection Creditor Bank processes the incoming Pacs 004 e When the original Outgoing Collection contract is not active recall processing on original outgoing collection fails and the recall transaction gets logged into TR queue e In order to process the received Pacs 004 message Reversal of Outgoing Collection is rejected manually in Payments and Collections Transaction Input PCDONONL screen by the reject operation available or on receipt of Pacs 002 for Pacs 007 from CSM e This rejection process re activates the original Outgoing Collection with the contract details as prior to the reversal event e Anevent RACT will be logged for the original Outgoing Collection in the contract events data store e Once the original Outgoing Collection gets re activated the recall transaction is retried in Transaction Exception screen PCSREXQ 5 25 4 Viewing SEPA Payment Cancellation Approval Summary Details You can view the summary details of a SEPA Payment Cancellation Approval in
274. ion to indicate that a particular product can be used for processing collection transactions beyond the specified cut off time by enabling the Allow Post Cut off Transactions option Override Overdraft While maintaining details of products which debit the customer account like Outgoing Payments or Incoming Collections you have to indicate whether transactions involving these products should be sent to the Credit Exception queue or whether the credit check should be ignored If you enable this option the transaction will be processed regardless of its overdraft status If you leave this box unchecked all such transactions are sent to the Credit Exception Queue as well as to the Referral Queue Upon Accepting or Rejecting a transaction in the Referral Queue these transactions are processed in the same manner as any other transaction in the Credit Exception queue For further details refer to the processing transactions in the Credit Exception Queue refer to the Processing Credit Exceptions section in the Processing a Payment or Collection Transaction chapter of this manual Dispatch Accounting To enable the consolidation run manually after each dispatch of clearing contracts for daytime processing Dispatch Accounting Batch in PC is available Dispatch Accounting E New E Enter Query Clearing Network To initiate Dispatch Accounting manually after physical dispatch of a clearing file use the Dispatch Accounting screen To inv
275. ions with P2P payment type as Customer Type For the customer type other than Customer Debit it is mandatory to specify the counterparty bank code and counterparty account umber details During the customer debit transaction processing following transaction data would be logged into P2P Payment Beneficiary Registration Queue to track the beneficiary registration till the end date e Contract Reference Number e Branch Code e Sender Account Number e Beneficiary s Email ID e Beneficiary s Telephone e Beneficiary s Facebook ID The end date for the beneficiary registration is derived based on the Registration Period in Days parameter value from P2P payments parameters level The derived end date will also be logged into P2P Payment Beneficiary Registration Queue Credit GL used for the credit liquidation will be maintained at contract level This GL is used during the Reject of customer debit transaction processing for debiting the transaction amount in debit liquidation Processing Amount Block The system creates an amount block on the sender s account for the transaction amount on receipt of amount block request from the external system A failure response message is sent to the external system in case of any error during amount block processing During the amount block processing following transaction data would be logged into P2P Payment Beneficiary Registration Queue to track the beneficiary registration till t
276. it Agreement History screen You can invoke this screen by typing PCDDRAHS in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Debtor Direct Debit AgreementHistory amp Enter Query Customer J a Version Number Product Code Collection Scheme Type E Poet Dem Agreement Id SR ND Debtor IBAN Customer Name Debtor Reference Code Branch Debtor Account Currency Counte seins Creditor Name Creditor ID Scheme ID Address 1 Address 2 Creditor Account Address 3 Bank code Adie gnk Name Country Date Of Signature Suffix g Direct Debit Reference No Transaction Details Validity Details Maximum Amount Per Effective Date Transaction i iry Date Maximum Amount Per PEY Calendar Year Agreement Status Utiized Amount For Calendar Amendment Reason Year Number Of Transactions Per Calendar Year Utilized Transactions For Calendar Year Agreement Cancellation Charge Charge Reference Number Transaction Type Payment Details 1 Payment Details 2 E Payment Details 3 Payment Details 4 Date Time Date Time Record Status Authorization Status Maker Checker Mod No Version Number This field displays the corresponding version number For further details refer the section Maintaining DD Agreement Details for Debtors in this user manual Viewing Debtor Direct Debit Agreement Histor
277. it with a product category A product category helps in identifying the product that should be used to process a transaction that is received A product category can be of either of the following types e Incoming e Outgoing Once you have maintained the basic details for a category you can proceed to associate products that have been created at your bank with the category For a product category you have to identify products for the following types of processing e Book Transfers e Internal Clearing e External Clearing at ORACLE For internal and external clearing you also have to specify the sequence in which the products should be taken up for product resolution Depending on the sequence the appropriate product will be associated when a transaction is initiated in the system An outgoing transfer includes information about the outgoing product category When this transaction is received Oracle FLEXCUBE resolves the product to be used for processing as follows Case One e The outgoing product category maintenance is referred Ifa book transfer the system picks up the outgoing book transfer product specified here the customer leg is processed using this product The Incoming Product Category specified for the outgoing product is picked up The Incoming Product Category maintenance is referred and the product which corresponds to the incoming transaction within this product category is picked up The
278. iti Eaa A NTA rae E REE 8 4 8 3 1 Viewing Background Processes eesseeeersrirrreerrennrrrnnrneerrrnerrrnnnnneernennne 8 5 Ba The Online MOde niena E EE A AENEA eats 8 6 8 9 Contract Partitions esrar E TE T EE 8 6 8 6 Processing Customer Consolidation Batch sseseeesessesriesseerrsssrerrssrrerrsssrrrrnssee 8 7 8 6 1 Processing of Logging the Batch into Consolidation Summary Screen 8 8 8 6 2 Processing EOD for Expiry of Beneficiary Registration 00 cccccscceee 8 9 8 7 Notifying KYC Status of P2P Beneficiary ce ceeceeeeceeeeeeeeeeeeeeeeeteeeeeeeeeteeaeeees 8 9 8 8 Notifying Successful P2P Final Payment 0 ec ceeeeeeeeeeeeeeeeeeeeeeeeeeennaeeeeeeenaaes 8 10 8 9 Notifying Rejected Test Transaction and P2P Final Payment 8 10 8 10 Notifying Rejected Status of Payment Request eeceeeeeeeeeeeeeeeenteeeeeeeenaees 8 10 8 11 Notifying for Split Event sss ernpu ried r A 8 11 8 12 Notifying for Reversal of Payment ccc cceeeeeeeeeeenneeeeeeennaeeeeeeeeaeeeeeeeneeeeeseenaes 8 11 8 13 Notifying on Consolidation of Contract cc ceccceeeeeeeeeeeeeeeeeeeeeteeeeeeenaeeeeeeenaaes 8 11 Annexure A Accounting Entries and Advices ccseseeeeeeeeeeeeeeeeeeeee 9 1 9 1 Events for the Payments and Collections Module c cceeeceeeeeeeeeeeteeeeeettteeeeeees 9 1 9 4 1 ACCOUNTING Roles teccitccccccciesesciecennececieennaendieenenesteebbbesnsdeueebecuteverbeeasiinbes 9 2 9 2 Product Type an
279. itional Customer Details Click on Additional Customer Details to maintain the additional details of the customer Customer Address You can specify the address of the customer involved in the contract You can specify up to five lines of address information Customer Information If you need to specify other information regarding the customer of the transaction free format 35 character text fields are provided with appropriate labels applicable for your installation You can specify the customer information such as Surname Email ID No Telephone and Customer Reference in these fields Communication Mode Indicate the mode of the communication to the customer to intimate about the beneficiary account credit You can select one of the following options e Mobile e Email ID The above field is enabled only for the product that uses the NEFT clearing network i e Network Qualifier of the Clearing network should be NEFT Customer Reference Specify the customer reference number Mobile Number Email ID Specify the mobile number or Email ID of customer Customer BIC ID Specify the Bank Identification Code for the Customer Customer Scheme Name Type Select the Identification Scheme Type of the Customer from the drop down list and the available options are e C Code a ORACLE e P Proprietary Customer Scheme Name Specify the value for Identification Scheme Name field If Scheme Name type is C then the Scheme
280. l apply to the credit leg of the transactions processed under the product Counterparty Entry days When creating a product you can specify the number of working days to be added to the activation date to determine the entry date for the counterparty leg of transactions processed under it For an Outgoing product type your specification will apply to the credit leg of the transactions processed under the product For an Incoming product your specification will apply to the debit leg of the transactions processed under it Counterparty Values days You can specify the number of working days to be added to the activation date to determine the value date for the counterparty leg of transactions processed under a product The Counterparty Entry Value Date of a transaction should be later than or the same as the Counterparty Entry Date oe ORACLE For an Outgoing product type your specification will apply to the credit leg of the transactions processed under the product For an Incoming product type your specification will apply to the debit leg of the transactions processed under the product Transactions received before the cutoff time you have specified will be processed according to your pre cutoff specifications Transactions received after the cutoff time you have specified will be processed according to your post cutoff counterparty entry value days specification for the product Allow Post Cutoff Transaction You have the opt
281. l be defaulted as the product currency Recall Days Specify the number of recall days here Recall Days Basis Select the basis for computing the recall days whether it has to be working days or calendar days Sp ORACLE 3 34 Recall Date Basis Select the basis for computing the recall dates whether it has to be working days or calendar days Maintaining Details for Periodic Instructions Your bank could process outgoing payments or collections that need to be initiated periodically at pre defined frequencies Oracle FLEXCUBE facilitates maintenance of details for such periodic payments or collections A batch process that is executed during the Beginning of Day processes generates periodic transactions for which details have been maintained You can maintain details of periodic payment or collection transactions in the Periodic Instruction Maintenance screen which you can invoke from the application browser You must maintain basic details such as the product category product code customer and counterparty details transaction amount and user defined fields You can invoke this screen by typing PCDINSTM in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Periodic instruction Maintenance X H save oTe dEle Counterparty Details Periodicity Fields Product Category ae Instruction Reference 000ZPCP110040008 Number Product Code fas Cu
282. l clearing involves accounts maintained in Oracle FLEXCUBE and an external entity The clearing network will be used to send local payments direct debits and requests for debit instructions from the bank Direct Indirect For each clearing network you can specify the nature of the clearing relationship whether direct or indirect If the relationship with the entity is indirect you have to indicate the name of the redirecting bank also Mention the account number that your bank maintains with the clearing network Cover For each RTGS and Network combination you can choose to generate both cover message and payment message for the direct participant of the counterparty Check the Cover Message option against the clearing network if the cover message has to be generated along with the payment message The system generates the cover message only if you have linked an advice format in the Dispatch event of Payment Product and also opted for cover message generation for the specified contract Direct Bank Code For processing incoming payment messages you can setup the following details in the PC Bank Directory screen for the clearing network e For direct participants the Direct option can be chosen in the Direct Indirect field e For Addressable Indirect Participants the Indirect option can be specified with Cover enabled and the Direct Bank Code the option list in the Direct Bank Code field contains those bank co
283. le the rejection Pacs 002 transaction on all outgoing messages through Payment gateway Message Browser screen This screen displays the payment status reports for which Reject Message is enabled in the Common Payment Message Browser You can oe ORACLE invoke the Payment Gateway Message Browser screen by typing MSSPMTSR in the field at the top right corner of the application tool bar and clicking the adjoining arrow button Payment Status Report Queue E search Ct Advanced Search 9 Reset Y Clear All Case Sensitive Message ID Original Message ID Message Creation Date Source Reference File Reference Number Reject Code External Reference Version Source Code Status Br a Bi Bi Be Records per page 15 7 10f1 Message ID Original Message ID Message Creation Date Source Reference File Reference Number Reject Code E m View Process Reject Suppress Retry You can filter your search based on any of the following criteria Message ID Message Creation Date File Reference External Reference Source Code Original Message ID Original Transaction ID Reject Code Version Status Once you have set the filters you want click Search button to view the payment status report summary Message ID Original Message ID Message Creation Date Original Transaction ID File Reference Reject Code d ORACLE 5 27 e External Reference e Version e Source Code e Or
284. lick the Charge button to invoke the PC Charges screen a ORACLE Collection Status The status of the transaction is displayed at the bottom of the screen The following details are displayed e Contract Status e Authorization Status e Exception Queue e Collection Status Exchange Rate The exchange rate of the transaction will be displayed in case the customer account is in a foreign currency only for payment transactions Exception Queue The name of the queue to which the transaction is logged in case of any processing exception is displayed here Message Status If the outgoing payments workflow is applicable for the transaction the status of the message is displayed here Batch Number The batch number to which the transaction will be posted is displayed here Batch Description The description associated with the batch is displayed here FX Contract Reference Specify the FX Contract Reference number you need to link to the PC contract for the currency pair The adjoining option list displays Forward Deal Type FX contracts which are authorized and active Select the appropriate one The system disables Rate Date and Rate Serial if the FX Contract Reference number is specified While entering a payment contract the system facilitates you to choose a FX forward contract This FX forward contract must meet the following requirements e The FX contract must be the only Forward Deal Type e The FX fo
285. lidate the DD agreement details Amendment Reason Specify the reason for which the mandate details are amended Maintaining DD Agreement Details for Debtors This agreement is maintained by your bank on behalf of customers who participate as debtors in a direct debit transaction The details are maintained in the Debtor DD Agreements screen You can invoke this screen by typing PCDDRAGT in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Debtor Direct Debit Agreement Maintenance Service Level Code Product Code Collection Scheme Type Customer Agreement Id Customer Name Debtor IBAN Branch Debtor Reference Code Account No Currency ounterparty Counterparty Name Creditor ID Scheme ID Address 1 Description Address 2 Creditor Account Address 3 Bank Code Address 4 Bank Name Country Date Of Signature Suffix Direct Debit Reference No Validity Details Maximum Amount Per Transaction Effective Date Maximum Amount Per Expiry Date Calendar Year t Utiized Amount For Calendar Pee SES Year Amendment Reason Number Of Transactions Per Calendar Year Utilized Transactions For Calendar Year _ Agreement Cancellation Charge Charge Reference Number Transaction Type Payment Details 1 Payment Details 2 Payment Details 3 Payment Details 4 Purpose of the Collection Fields Maker Date Time Mod No Checker Date Time Record Status Authorization Statu
286. liquidation events you need to visit Transaction Details tab modify the customer entry value date and save the contract 5 6 Viewing Transaction Authorization Details You can view the transaction authorize details in Transaction Authorize Summary screen You can invoke this screen from the Application Browser by typing PCSTRAUT in the field at the top right corner of the Application Browser e Transaction Authorize Summary f Search t Advanced Search 9 Reset D Clear All Case Sensitive Contract Reference Custom Reference No Product Category Customer Name Records per page 15 v 10f1 sal Contract Reference Custom Reference No Product Category ProductCode CUST_NO Customer Account Currer Bulk Authorize Authorize In the above screen you can base your queries on any or all of the following parameters and fetch records Contract Reference Custom Reference No Product Category Customer Name 38 ORACLE 5 7 5 8 Select any or all of the above parameters for a query and click Search button The records meeting the selected criteria are displayed Contract Reference Custom Reference No Product Category Product Code CUST_NO Customer Account Currency Customer Name Auth Status Multilevel Authorization of a Contract High value transactions may require multilevel of authorization The levels of authorizations are defined in the Product Transac
287. ll of outgoing collection products Event Code Accounting Role Amount Tag Dr Cr DRLQ REMITTER TFR_AMT Dr INTSUSREC TFR_AMT Cr CRLQ INTSUSREC TFR_AMT Dr CLGSUSPAY TFR_AMT Cr DRLQ for Recall of Incoming Collection Products The following accounting entries can be defined for recall of incoming collection products ORACLE Event Code Accounting Amount Tag Dr Cr Role DRLQ CLGSUS INT_AMT Debit REC COMPACC INT_AMT Credit DRLQ for Recall of Outgoing Collection Products The following accounting entries can be defined for recall of outgoing collection products Event Code Accounting Amount Tag Dr Cr Role CRLQ COMPACC INT_AMT Debit CLGSUS INT_AMT Credit PAY Reject of Outgoing payments The following entries can be defined for reject of outgoing payments Event Code Accounting Role Amount Tag Dr Cr DRLQ CLGSUSREC TFR_AMT Dr INTSUSREC TFR_AMT Cr CRLQ INTSUSREC TFR_AMT Dr CUSTOMER TFR_AMT Cr Reject of Incoming payments The following entries can be defined for reject of incoming payments Event Code Accounting Role Amount Tag Dr Cr DRLQ CUSTOMER TFR_AMT Dr INTSUSPAY TFR_AMT Cr CRLQ INTSUSPAY TFR_AMT Dr CLGSUSPAY TFR_AMT Cr For reject of Incoming Payments IN contracts following accounting entries will be posted for DRLQ and CRLQ events
288. llation for incoming payment is 08 Issuing entity request All the cancellation request transaction is logged to the CPG The system defaults the request with message type CNLCT You can accept or reject the request within the number of days maintained at product level If the request is accepted then the cancellation status will be approved If the request is rejected then the system updates the cancellation status as Rejected There is no accept or reject process for incoming collection cancellation requests The system books a reject of incoming collection contract with message type as CNLDD Cancellation Originator Name Specify the name of the cancellation originator Cancellation Originator Bank Specify the Bank of the cancellation originator Note Specify either Cancellation Originator Name or Cancellation Originator Bank Approve Reject Select Approve or Reject from the adjoining option list Reject Code Select the reject code from the adjoining option list You can specify the ISO Reject code in this screen during the Cancellation acceptance rejection operation During Cancellation acceptance rejection processing in this screen system validates the entered ISO Reject code against the applicable exceptions as maintained in the Reject Code maintenance An error message would be displayed if the entered Reject code is not applicable to the Cancellation acceptance rejection exception The sys
289. llowing statuses e Unprocessed e Processed e Suppressed e Repair e Rejected e Waiting for Queue Exchange The contracts with status Unprocessed or Waiting for Queue Exchange in the Common Payments Gateway browser will be picked up for processing and the PC contract will be created If the creation of the PC contract fails the transaction is marked as Repair in the Common Payments Gateway However you can amend and process this contract again In such a case a new version will be created for the amendment operation in the Common payments Gateway message browser The transaction in the reject messages Reject Payments Status Report pacs 002 001 02 from the Clearing and Settlement Mechanisms CSM will be kept in common payments gateway with status as Unprocessed and queue as REJECT When you click Process Reject button the system does a pre settlement reject of a SEPA transaction The status is further updated as Processed There will be no transactions created in PC module for these reject transactions and no further processing will be allowed on such transactions The incoming payment messages with the following error codes are automatically rejected Error Code Error Description PC SAV 024 Account is blocked oe ORACLE 5 25 9 5 25 10 PC SAV 025 Payment Not allowed for customer account PC SAV 026 Credit not allowed for customer account
290. mation specific to a particular field by placing the cursor on the relevant field and striking lt F1 gt on the keyboard Audience This manual is intended for the following User User Roles Role Function Back Office Trade Finance Department Clerks PC Contract Input functions except Authorization Back Office Trade Finance Department Officers PC Contract Authorization maintenance of static data specific to the BC module Front end Trade Finance Product Managers PC Product definition functions excluding authorization BC Report Query functions End of Day Operators End and beginning of day related processing functions PC Report Query functions Bank s Financial Controller Trade Finance Department Manager Branch level processing related setup for PC module and Authorization of the same Authorization of PC prod uct definitions amendments PC Report Query functions MIS Department Officers PC Query Report functions Documentation Accessibility For information about Oracle s commitment to accessibility visit the Oracle Accessibility Program website at http Avww oracle com pls topic lookup ctx acc amp id docacc Organization This manual is organized into the following chapters About this Manual gives information on the intended audience It also lists Chapter 1 S the various chapters covered in this User Manual Payments and Collections An Overvi
291. mation specific to the Payments and Collections Module of this User Manual oot ORACLE 5 25 8 PC Transaction Input The SEPA related details of the contract are captured in the PC Transaction Input screen For more information on this refer section Capturing the details of payment collection transactions in this User Manual Process Flow The various stages involved in processing a SEPA transaction are as given below 7 Receiving Incoming messages for SCT and SDD 8 Using the Common Payments Gateway to upload data from the Incoming SCT and SDD into PC module Queue is derived from STP rules 9 The PC product category will be picked up from the Product mapping maintenance based on the queue evaluated in the rule maintenance 10 Mapping the Common Payment gateway fields to PC contract fields for the product category using the PC message Mapping Maintenance screen for different combinations of incoming message type product category product instrument type source code station ID and network id 11 Using the contents of the message together with the static maintenance in the system to resolve the contract fields 12 Automatic booking of contracts in the system depending on the resolved contract fields 13 Processing the contracts depending on the status of the contract 14 Generating dispatch files which is sent to CSM Bank or the Customer The contract in the Common Payments gateway can have any of the fo
292. me customer entry date If all the above condition satisfies then the system performs the automatic closure considering that as the last transaction for the file reference number If any transaction is pending in TR queue for the same file reference number and if the transaction is repaired and processed the system performs the above processing logic while logging into consolidation summary screen If transactions are not pending for the same file reference number then the system performs the automatic closure of the file consolidation batch During manual closure of consolidation batch across products system validate based on the below conditions The customer entry date has to be the transaction date for the transactions under the consolidation batch Otherwise the system will display an error message on click of close button If there are any transactions that are yet to consolidated transaction pending in TR queue for the same file reference number and if you try to close the batch manually system will display an error message indicating that the transactions are still pending for consolidation under the same file reference number Processing EOD for Expiry of Beneficiary Registration The EOD will mark all the Customer Debit payments and Amount Block requests in Beneficiary Registration Queue as Expired on the end date for the beneficiary registration if the beneficiary has not registered This will process re
293. me of the invoicee Address 1 and 2 Specify the address of the invoicee Country Specify the country of the invoicee Structured Invoicer Details Identification Type Select the identification type from the adjoining drop down list The options available are e Private e Organization BIC Specify the bank identifier code Name Specify the name of the invoicer Address 1 and 2 Specify the address of the invoicer ve ORACLE Country Specify the country of the invoicer Payment Details Structured Payment Details 1 2 3 and 4 Specify the payment details Sender Receiver Information Sender Receiver Details Specify the sender receiver details Sender Receiver 1 2 3 and 4 Specify the sender receiver information P2P Payments Customer Debit Reference Number The system displays the customer debit reference number Note If the P2P payment type is Customer Debit then the customer debit reference number will be same as the contract reference number If the P2P payment type is Test Transaction or P2P Final Payment then the customer debit reference number will be customer debit reference Amount Block Reference Number The system displays the amount block reference number Test Transaction Reference Number The system displays the test transaction reference number Note If the P2P payment type is Customer Debit then the test transaction reference number will
294. ments Module Settlement Details to other Modules In order to facilitate processing of outgoing payments instructions for local currency transactions in any module through the Payments module you must map the requisite settlement details defined for specific payments product categories to the products in other modules You can do this using the Settlements to Payment Product and UDF Mapping screen ot ORACLE You can invoke the Payment UDF Mapping Maintenance screen by typing PCDISMAP in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Payment UDF Mapping Maintenance B New amp Enter Query Payment UDF Mapping Module Module Description Product Code Product Description Pay Receive Post Accounting Transfer Type Product Category Category Description Source Code Source Description Station ID Station Id Description UDF Mapping Fields 1 Of 1 E Settlement Fields amp Module UDF Product UDF Description Maker Date Time Mod No Checker Record Status Date Time Authorization Status OLE_LINK1In this screen you can map settlement details and user defined fields designated for specific product categories in the Payments module e To a specific product defined for a specific module e To all products defined for a specific module Pay Receive Option You will also need to identify the process direction of the set
295. ments and collection transactions are the CHG_AMT tags which must be mapped to the CRLQ and DRLQ events depending upon which of these is the event for the customer leg of the transaction during product definition The accounting entries and advices that would be generated during the payment or collection lifecycle depend therefore on the specifications made at the product definition level For details relating to building Charge Classes refer the Charges chapter in the Modularity User Manual Defining the Charge Account Maintenance Oracle FLEXCUBE allows you to book charges for payment collection transactions to an account different from the transaction account The charge account so designated accumulates the charges levied across transactions and the sum of the accumulated charges is swept in to the transaction account at a desired frequency You can specify a charge account to be applicable to e One many or all accounts of a particular customer e One many or all products e One many or all charge components eo ORACLE e One many or all currencies e Any combination of the above The Charge Account Maintenance screen allows you to set up the charge account You can invoke this screen by typing PCDCHACWM in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button amp Charge Account Maintenance E New Enter Query Customer Number Account
296. ments module oe ORACLE 3 37 2 e Any or all user defined fields defined for the payments product category Source Code and Customer Station id You must specify the code of the upload source and the ID of the customer station maintained for the source Enabling Post Accounting Entries option If you have indicated that PC Contracts should be generated for local currency payments within your bank LCY Message Type and if the settlement is routed through the Clearing House you have the option of posting accounting entries as part of PC processing Your specification in this field is defaulted to the Settlement sub screen Local Clearing for Funds Transfer transactions through the PC Module For funds transfer transactions with local clearing through the PC module you must map the requisite settlement details defined for the requisite payments product categories to the FT products in the Settlements to UDF Mapping screen When this setup is authorized the payment for such FT contracts is processed as follows e f payment is indicated by message the corresponding message is generated upon authorization of the contract e f payment is through local clearing a PC contract is generated with the clearing details mentioned in the Settlements screen In this case the FT contract reference number will be the source reference for the PC contract Note The payment message can be routed through SWIFT and the Cover can be routed
297. mer leg of the transaction should be arrived at Your specification in the Pre cutoff field will be added to the activation date to arrive at the Customer Entry Value Date for transactions received before the cutoff time specified for the product Customer Entry Consolidation You can opt to consolidate the customer leg of transactions involving the customer and product combination At Product Level Required Check the box to if you require transactions to be consolidated at product level Consolidation Limit If the customer leg of the transactions should be consolidated you can specify a transaction amount limit for the transactions that should be considered for consolidation Transactions that exceed the limit you specify will not be taken up for consolidation If you do not specify a consolidation limit the customer leg of all transactions involving the customer and product will automatically be consolidated Note Note that your specifications in this screen take precedence over any product or account level parameters Invoice Split Required Invoice Split Required Oracle FLEXCUBE allows you to split a transaction into multiple transactions if the transaction amount exceeds the maximum transaction amount limit specified above However you can choose to split the amount for transactions involving an outgoing product Direct Debit Agreement Fields Agreement Required For the product and customer combination
298. mes that lie outside of the window period Window periods are defined as follows e For each product level a separate window period is defined for initiation authorization and release of payments e The Window period can be extended for the current date using the separate window period modification screen 00 00 01 00 03 00 04 00 11 00 05 00 06 00 00 08 00 09 00 10 00 12 00 13 00 07 6 17 00 18 00 19 00 14 00 15 00 16 00 20 00 23 00 1 00 00 INTIATION WINDOW FOR RTGS FROM BRANCH AUTHORIZATION LVL 1 WINDOW FOR RTGS Product Lev Window Period Definition at el AUTHORIZATION LWL 2 WINDOW FOR RTGS RELEASE WINDOW FOR RTGS certain day Window Period Modification for a pa EXTENDED INTIATION WINDOW FOR RTGS ON A DAY Effective backout period for a certain day Cr A Extension Period Effective backout period for a certain day During the contract validation the system will check if the window period is maintained for the current date If the window period is not maintained for current date then the system will check the window period information from the product 4 39 ORACLE Based on the details provided in the Network Parameters tab in the Payments and Collections Product Preferences screen the appropriate window period validation are handled du
299. ming payment contracts and generates the single Credit Acknowledgement Message for those contracts Number of contracts for group will be parameterized in product maintenance Message Format The system will support the following credit acknowledgement messages M O FieldNo Field Name Contents Description Options M 2020 Transaction Refer 16x Uniquely identifies the mes ence Number sage Repeating Group Begins M 2020 Transaction Refer 16x Uniquely identifies the trans ence Number action loop M 5518 IFSC of Originator Ala4 c 3 c IFSC of Debit Originator of Remittance M 2006 Related Reference 16x For inward N10 message received for our outgoing pay ment Transaction reference number of the original NO6 message For outward N10 message generated for the incoming payment which we received we need to populate the Transaction reference num ber of the incoming payment message N02 ORACLE M 3501 Amt Credited Time 8 In 6 n Date and Time when the amount is credited to the cus tomer 8 n is the credited date YYYYMMDD 6 n is the credited time HHMISS Repeating Group Ends ORACLE 10 1 10 1 1 10 Reports Introduction During the day or at the end of the day you may want to retrieve information on any of the several operations that were performed during the day in your bank You can generate this
300. n e FNAL Final Collection e OOFF One Off Transaction e RCUR Recurring Transaction vel ORACLE Sign Date This indicates the date on which the mandate was signed by the debtor This would be defaulted based on the mandate ID selected This is a display only field Amend Indicator Select the option to indicate if the mandate has been amended or not The values available in the drop down are Yes and No The value that you select here is populated in the outgoing message for an outgoing collection transaction Amend Type Specify the type of mandate amend that has been done This is applicable only if Mandate Amend Ind is selected as Yes This value is populated in the outgoing message of the outgoing collection transaction Original Mandate ID Specify the original mandate ID if the mandate is amended This is applicable only if amend indicator is selected as Yes Orginal Debtor Account Specify the original Debtor Account under the scheme if the mandate is amended This is applicable only if amend indicator is selected as Yes scheme if the mandate is amended This is applicable only if amend indicator is selected as Yes Original Debtor Bank Specify the original Debtor bank BIC under the scheme if the mandate is amended This is applicable only if amend indicator is selected as Yes Creditor Scheme Details Scheme Identification Select the scheme identification code of t
301. n and the contract is tract rejected if the override is accepted If the override is not accepted no process ing is done Yes No Override No No processing is done Receiving Date is more than the response days Do you want to reject the con tract No Yes Override Yes Contract is placed in Pro Receiving cess Exception with excep Date is more tion queue RR from where than the it can be deleted if required response days Do you want to reject the con tract No No Reject the con tract 4 16 ORACLE Inward DD Process Response Overrid Rejects After Days greater e Response than Rejection Action Accept Acan Days Days Yes Yes Override Do you Yes Reject the con want to reject the tract contract Yes No Override Receiving No No processing Date is more than the is done response days Do you want to reject the contract Yes No Override Receiving Yes Reject the con Date is more than the tract response days Do you want to reject the contract No Yes Override Do you Yes Contract is want to Recall the Recalled contract No No Override Do you Yes Reject the con want to reject the tract contract Note Note the following For online transactions even after the response days have passed the System rejects the contract if the Process Rejects After Response Days option has been enabl
302. name of the account here If you indicate cover for payment via the local clearing network you must specify the account details of the cover party in the Cover Details tab in the Settlement Instructions screen The screen is as below Settlement Instructions Maintenance H save Counterparty PS Module Bz Counterparty Name Product Code bl Counterparty CIF x Sequence Number 0 Currency GBP am Relations Branch 000 enj Pa Receive x E Cover Required Branch 000 FA Branch 000 Cover By Currency GBP las Currency GBP las Charges Details Ourselves Account bal Account fae Beneficiary Description Description Shared Payment By v Payment By x Pay Parties Pay Parties Receiver Parties Cover Parties Clear Details ett ieets Other Details Cover Details Bank Code az Account Name fae Clearing Network bal Bank Name Fields Change Log Maker Checker Mod No Record Status Authorization Status Date Time Date Time For the cover party account details you can specify Bank Code Select the bank code from the list of options available Account Specify the account here Name Specify the name of the account here The following scenarios are possible Cover Cover By Payment By Local Clearing Cover Required Counterparty Details Details Yes Message Message No No Yes Local Clearing Message No Yes No Message No No No Local Clearing
303. navailability of funds will be displayed in this queue Consolidation Exception Queue All transactions that were rejected due to errors in posting the consolidated entry will be displayed in this queue 26 ORACLE 3 Maintaining Information Specific to Payments and 3 1 Collections Introduction Before you begin operations in the Payments and Collections PC module of Oracle FLEXCUBE you must maintain certain basic information in the system For example you must maintain the e Local Bank Directory e Clearing Networks e Upload Sources e Bank Redirection details This data is essential for processing the payments and collections transactions during the course of the day Data of this sort is referred to as Static Data because it remains constant over a period of time Maintaining Static Data The static data maintained in Oracle FLEXCUBE can either be common to several modules or be specific to a module For example data relating to exchange rates is common to modules such as Foreign Exchange Funds Transfer Payments etc Static Data that is commonly accessed by several modules is maintained in the Core Services module Data that is specific to a module is maintained in the module itself For example the details relating to the clearing networks that you support are specific to the Payments and Collections module It is therefore maintained in the PC module Maintaining Information Specific to
304. nt Specify the virtual account number in this field Based on the virtual account code and transaction currency the system derives the linked physical account If no physical account is mapped then the default physical account linked to the virtual account is derived If you change the defaulted physical account and if is not linked to the virtual account then system will replace the derived physical account providing an override for the same Virtual Account will not be allowed for Outgoing Payments as it is applicable only for Credit transactions and Collections Virtual Account Name The account name of the virtual account number is displayed in this field Additional Counterparty Details Click on Additional Counterparty Details to maintain additional details on the counterparty Counterparty Information If you need to specify other information regarding the counterparty of the transaction free format 35 character text fields are provided with appropriate labels applicable for your installation You can specify the counterparty information in these fields Surname Specify the surname of the counterparty Father Name Specify the father s name of the counterparty Telephone Specify the contact number of the counterparty Email ID Specify the email Id of the counerparty Facebook ID Specify the facebook Id of the counterparty ail ORACLE Remarks Specify remarks if any Counterparty Address You
305. nt Branch customer Customer Ac Ccy Restriction From Date E Collection Scheme Type CORE e Restricted Details Restriction Type Allowed Disallowed 10f1 E 1071 c 4 Ez 10f1 l Es Creditor ID Scheme ID Mandateld F Creditor IBAN E Document Ref No Suffix el kl E Date Time Date Time Mod No Record Status Authorization Status The following details are captured in the screen Customer Id Select the customer ID from the adjoining option list Customer Name System defaults the Customer name based on the Customer ID selected Customer Account No Specify the value for the field It helps in identifying a particular instruction List of values will be attached to display the list of customer accounts List of values will also have ALL value The Debtor DD instruction can be set up at a customer level or at a customer account level If specified at a customer level then the customer account and Branch should be with value ALL Fa ORACLE Customer Account Branch The field displays customer account branch The value for the field gets populated on selecting Customer Account Collection Scheme Type Specify the value for the field from the adjoining drop down list to distinguish the Debtor restriction instructions across collection scheme types The following options are available for this field e CORE e COR1 e B2B e ALL
306. nt for Calendar Year e Utilized Amount for Calendar Year field will get reset to 0 on beginning of every new calendar year if there are no active incoming collection transactions If there are active incoming collections at beginning of calendar year then Utilized Amount for Calendar Year field is updated with transactions amount e If Maximum Amount for Calendar Year is not maintained then incoming collection transaction would not be validated against maximum amount and Utilized Amount for Calendar Year is not updated e During the course of the calendar year when Maximum Amount for Calendar Year gets maintained then the subsequent incoming collection transactions and its R transactions will impact updating of Utilized Amount per Calendar Year e Anyincoming collection transaction and its R transaction processed prior to Maximum Amount for Calendar Year maintenance is not considered for updating Utilized Amount per Calendar Year e R Transaction received after Maximum Amount for Calendar Year maintenance for the original parent transaction processed before Maximum Amount for Calendar Year is not considered for updating Utilized Amount per Calendar Year 5 34 Restricting Number of Transactions per Calendar Year e Each incoming collection transaction will be checked against the Utilized Transactions for Calendar Year with Number of Transactions per Calendar Year for a particular mandate
307. ntaining Dispatch File Parameters cccccccc cece etneeeeeeetnteeeeeetaae 5 90 9 25 12 Generating Dispatch File 0 ccccccceteeeeeeetnteeeeeeetnneeeeeeesnaeeeeetetiaeeeeenenaa 5 92 5 26 Maintaining Payment Gateway Message Browser ccsccceeeeseeeeeeeeetteeeeeeenaaes 5 93 5 27 Maintaining Payment Gateway Message BUIKS eseceeeeeeeeeeeeeeenteeeeeeeeaees 5 95 5 28 Handling Payment Status Report ccc ccc eeeeeeeeenneeeeeeeeaaeeeeeeetaeeeeeeenaeeeeeeneaes 5 97 5 28 1 Processing Pacs 002 Messages Payments cccccccetsteeeeettteeeeeeeeaes 5 98 5 28 2 Processing pacs 002 messages Collections cccccecentteeeeettteteeeeeeaes 5 99 5 28 3 Processing Re activation Event eessseesrrreerrrrnnneerrrnnnnrrrnnneeernnnnrnna 5 101 5 29 Black List and White List of Creditors ccc eeceeeeeeee tent eee eeeetaeeeeeeeeaeeeeeeenaaes 5 101 9 90 Managing Mandates ataia E a N RE EEEE anaccenteaadaces 5 102 5 30 1 Validating Mandate Existence for incoming collections 0 1100000112 5 102 5 30 2 Restricting Automatic Upload of Mandate cccccccseeseeeessteeeeeeeneeees 5 104 5 31 Processing Expiry Dataset rT rt a AAA k A A ET eA E EEEL Eea 5 105 5 32 Restricting Maximum Amount per Transaction cccceeeeeceeeeeeneeeeeeeeenereeeeeeeaes 5 105 5 33 Restricting Maximum Amount per Calendar Year ccccccceeeeeeeeeeeeentteeeeeeeaas 5 105 5 34 Restricting Number of Transactions per
308. ntification Email Id Telephone Facebook ID Beneficiary Account Bank code Bank Name Account Number Beneficiary Details Beneficiary Name KYC Status Yet To Verify v Address 1 Remarks Address 2 Address 3 Address 4 Address 5 Maker Date Time Checker Date Time Mod No Record Status Authorization Status Beneficiary Identification Email ID Specify the email identification of the beneficiary Telephone Specify the contact number detail of the beneficiary Facebook ID Specify the facebook identification of the beneficiary Beneficiary Account Bank Code Select the bank code where the beneficiary holds the account from the adjoining option list Bank Name The system defaults the name of the bank based on the bank code selected Account Number Specify the account number of the beneficiary Beneficiary Details Beneficiary Name Specify the name of the beneficiary Address 1 2 3 4 and 5 Specify the address of the beneficiary 20 ORACLE KYC Status Select the KYC status from the adjoining drop down list The options available are e Yet to Verify e Verified e Verification Failed By default the system maintains Yet to Verify as the KYC status Remarks Specify remarks if any 3 13 Viewing P2P Beneficiary Details You can view the peer to peer beneficiary details maintained in the P2P Beneficiary Maintenance screen using the P2P Beneficiary Summary screen You
309. ntries Message The following details are displayed e Event Details This provides all the user initiated events during the life cycle of the contract e Accounting Details This provides all a list of the accounting entries passed by the system for the contract Click Accounting Entries button in the PC Contract View Events screen to view these details e Override Details Here you can view the overrides provided for the transaction during its life cycle e Message Details Click Message in the PC Contract View Events screen to view the messages advices generated against each event Viewing Duplication details The system checks for duplicate transactions while booking contracts based on the number of days for duplicate check maintained at the Branch Parameters Maintenance screen and the duplication preferences set at the product category level The system displays the duplicate contract reference number if there is a single match else it displays the following override message Duplicate Contracts recognized based on the product category preference oo ORACLE You can view all the duplicate contracts in the Duplication Details screen Click Duplication Details button in the PC Transaction Input screen to invoke this screen Duplication Details Contract Reference Duplication Details Contract Reference Custom Reference No Pr
310. o allow transaction repair The system will move the incoming payment transaction into the Repair queue if the customer account does not exist in the system Note The Repair function is available only for Incoming Payments Authorization Limit If the transaction amount exceeds this amount then corresponding contract will be moved into Incoming Payment Authorization queue Limit for Name Match This amount is used to identify if validation is required on customer name or not If Validate Customer Name checkbox is checked in product category and transaction amount also exceeds this amount then the system will check if the customer name is available in the system or not If it is not available then the system will move the contract to the Incoming Payment Authorization queue Specifying the List of Banks You can maintain list of the clearing branches of your bank to which the payments should be directed Click List of Banks button in the Product Preferences screen to invoke the List of Banks screen List of Banks Product Description Bank Details 1 Of 1 Bank Code Bank Name Role To Head Mapping 10f1 Accounting Role Role Description Account Head GL Description aaa ORACLE 4 2 6 Linking a Tax Scheme You can link a tax scheme defined in the tax Click Tax button in the Product Preferences screen to invoke the
311. o not specify a limit amount all transactions for the product customer combination would be processed Click Accept to force accept a transaction Note Note the following The carry forward option is not available for incoming collections All contracts need to be processed before the end of day operations for the day Consolidating Accounting Entries for Customer Legs If you wish to consolidate the accounting entries of customer legs of collection transactions use the Consolidation Summary screen Only contracts marked for customer entry consolidation will be grouped into batches based on the following Consolidated Status Customer Account Number Amount Customer Entry Date Consolidation Reference No Transaction Count Customer Number Account Currency Customer Entry Value Date Product Code Exception Queue Customer Account Branch Through consolidation you can post a single entry for the customer leg of all transactions grouped under the consolidation batch The transaction with customer consolidation across products are also grouped under a consolidation batch The batch populated for Contracts with customer consolidation across products will have Product Code as Blank ii ORACLE You can invoke this screen by typing PCSCNSOL in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button amp Consolidation Summary f Search t Advanced Searc
312. oduct Category Customer Number Initiation Date Activation Date Here you can view the following details e Contract reference no e Custom Reference no e Source Ref no e Product Cat e Customer Acc No e Counterparty Acc No e Counterparty Bank Code e Counterparty Name e Txn Ccy e Txn Amt e Activation Date e Payment Details Note Duplication check is done based on the following criteria Number of duplication days that is maintained at the Branch Parameters Maintenance screen Duplication recognition that is selected at the Payments and Collection Product Category Maintenance screen The duplication details are persistent and can be viewed by the authorizer too If duplication details are not maintained at branch level for Payments and Collec tions no duplicate checks will be carried out oe ORACLE 5 2 13 5 2 14 Specifying Project Details Click the Project Details button in the Payments amp Collections Transaction Input screen and invoke the Project Details screen You will have to capture project details in this screen only if the credit account is a Trust account Project Details Project Name Unit Payment Yes Unit Id Deposit Slip Number Specify the following details Project Name Specify the developer project name for which payment is being made The adjoining option list displays
313. of the contract will be displayed immediately after the authorizer calls the contract for authorization The re key option also serves as a means of ensuring the accuracy of inputs Fields You can specify any or all of the following as re key fields e Customer Account e Activation Date e Amount e Counterparty Bank e Counterparty Account e Counterparty Name e Exchange Rate a2 ORACLE e Currency Duplication Recognition Required You can ensure that the same transaction is not taken up a second time for processing by opting for the Duplicate Recognition Required feature If you choose this option you also have to specify the fields in a transaction that need to be matched with records in the transaction table for duplication For duplicate recognition you can choose any of the following fields listed below Fields e Source e Station Id e Source Ret e Customer Account e Amount e Counter Party Bank e Counterparty Account e Counterparty Name If you have opted for Duplicate Recognition during transaction processing Oracle FLEXCUBE provides an override message if it finds a matching record in the transaction table Deleted or reversed transactions will not be considered for Duplicate Recognition Note You can specify additional fields for duplicate record recognition in the Duplicate Recog nition User Defined Fields screen Validate Customer Name While maintaining Product Categories m
314. oke this screen select Dispatch Accounting under PC Processes in the Application Browser aa ORACLE You can specify the Clearing Network for which the dispatch accounting needs to be triggered if you do not specify a Clearing Network the Dispatch Accounting would be triggered for all Clearing Networks In order to facilitate the processing of loan repayments by customers who have their current or settlement accounts in some other bank of the clearing network you can generate Direct Debits to these accounts Loan DD Generation Days before the payment date Loan DD generation days are maintained in the Branch Parameters maintenance screen While generating the direct debit the following entries will be passed in Oracle FLEXCUBE Dr Clearing suspense Cr Dummy Settlement Account Liquidation is performed on the schedule date and the accounting entries passed during liquidation are Dr Dummy Settlement Account Cr Loan Asset GL Interest Income GL However if you would like to consolidate the accounting entries you can enable the Dispatch Accounting preference for the product As a result the Clearing Nostro GL is netted to post single debit and credit entries for each file that is dispatched The netted accounting entries that are posted will be as follows Dr Clearing Nostro Defined in the Dispatch Accounting details screen Cr Clearing Suspense Referral
315. ollection category for RFD Incoming Collection category RFD Incoming Collection category RFD Incoming Approval category RFD Outgoing Payment Category Incoming Reject category RFD Approval of Incoming Category RFD Outgoing Payment Category Approval of Outgoing Category RFD Incoming Payment Category Reject of Incoming Category RFD Reject of Outgoing Category RFD Product Category Offset Product Category Reject of Incoming payments Reject of Outgoing payments Reject Category For collection transactions for this product category that are rejected the reject product category needs to be specified This is not applicable for Reject of Incoming payment Reject of outgoing payment Reverse of Outgoing collection and Reverse of Incoming Collection Recall Category For collection transactions for this product category that are recalled the recall product category needs to be specified This is applicable to Direct Debit collections only This is not applicable for Reject of Incoming payment Reject of outgoing payment Reverse of Outgoing collection and Reverse of Incoming Collection Apart from specifying the different clearing products you can specify certain preferences for a product category The preferences you specify for a category determine the manner in which transactions are ultimately processed The following are the preferences that you can specify for a product category
316. ome and Expense type only Cash GLs cannot be specified During upload of incoming payments File upload the batch process checks whether the beneficiary customer account number is an IBAN account and resolves the customer account for the specified IBAN If it is not found the System checks the customer account or GL in LCF format and resolves the customer account for the specified LCF number If checks for IBAN and LCF formats fail the System checks for the customer account If the customer account is also not present the contract is marked for repair Ifyou specify a Trust account you will have to capture project details in the Project details sub screen by clicking Project Details button If you do not capture project details the system will display an error message while saving Account Description The system displays the description of the specified account number based on the details maintained at Customer Account Maintenance level Account Branch This is maintained for the branch in customer account maintenance screen The branch will be defaulted when you save the PC transaction Account Currency This is maintained for the account in customer account maintenance screen The values maintained will be defaulted when you save the PC transaction Available Balance The available balance of the customer will be defaulted here when you save the PC transaction The balance is maintained in the customer
317. omer Station Maintenance screen You can invoke this screen by typing PCDCUSST in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Payments amp Collection Customer Station Maintenance E New amp Enter Query Source Code Source description Station Id Station Id Description Restricted Station _ Allow General Ledger Allowed Customers Accounts 1 Of 1 Customer No Customer Name Account Number Customer Account Branch CustomerAcCcy m ELCs Date Time Checker Date Time Mod No Record Status Authorization Status First of all you must choose the Source for which you are maintaining Station details Source Code Identify the Station you are maintaining with a unique code Station Identification Specify a unique id for the station you have chosen Description Give a small description for the station you are maintaining Fap ORACLE 3 26 Restricted Station The station provides restricted access to specific customers and accounts and if so the list of customers and accounts Allow General Ledger You would like to allow access to a GL from the station If you have opted to restrict access to a station to specific customers you must identify the customers You must also identify the account s that the customer can access from the station Allowed Customer Accounts details Customer System displa
318. on Status Of a TrAnSa ctiOn cece ceeeeeeeeeteeeeeetnneneeeeenaeeeeneeee 5 50 9 8 2 Status Of a TANSACHON eE RAE eee ONEN A 5 50 5 9 Specifying Exchange Rate for a Transaction 0 cccccceeeeeseeeeeeeeeeeeeeeeeentneeseeenaaes 5 51 5 10 Authorizing the Input of Exchange Rates ce cceeecceeeeeeeeeeeeeeeneeeeeeetaeeeeeeeaaes 5 51 5 11 Refreshing the Exchange Rate eccccccceeceeeeeeeenneeeeeeeneeeeseeiaeeeeeeeiateeeenenaaes 5 52 5 12 Processing Credit EXCeptions 0 cceccccceeeeeeeeeeeeeneeeeeeenneeeeeeeeceeeeeeenneeeeeeeaes 5 52 5 13 Consolidating Accounting Entries for Customer LegS eeceeeeeeeeeeeeeeeeeeeneees 5 54 5 14 Consolidation Exception Queues e ecceeceeeeeeeeeeeeeeetecceeaaecaeeeeeeeeeeeteeeenneeas 5 55 5 15 Viewing Transaction History SUMMALY cc ccceeeseeeeeeeeeeeeeeeeeenaeeeeeeenaeeeeeeenaaes 5 57 5 16 Viewing Transaction Exception SUMMALY cceeeeceeeeeeeeeeeeeeeeteeeeeeeteeeeeeeeaees 5 58 5 17 Viewing Details of Split Transactions 200 0000 ee ceeee eee eeeee eee eeeeeeeeeeeeetaeeeeeeeeaees 5 59 5 18 Process Exception Queues cccceeeeeeeeceececaeeeeeeeeeeeeeeteesecaeaaesaeeeeeeeeeeeteeeeeneees 5 60 5 19 Exchange Rate Queues cccccceccececeeceeedeeeeeceeenseeeecesesseneeceeeteeedeceeetensaeeenenteadees 5 61 5 20 Periodic Exception Queues cccecceeeeeceeeeneecee eee eeee eee teeeeceaeeaecaeeeeeeeeeeeteeeeeneees 5 62 9 21 The Ba
319. on 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 Contents Preface Sones eS Sa nee es Re 1 1 We UMTMOMUGHON pp ctecte He bvsccet hecbt see E E E E 1 1 V2 PAUGION CO oana e a A E tt habia E T ea eina A AE 1 1 1 3 Documentation Accessibility 0 00 0 ccccceeeeeeecneeeeeeeeneeeeeeeeneeeeeesaeeeseeeiaeeeeeeeaes 1 1 TA Organizat asat aa EAE tea teak ARAE haste sade ETE A AAA 1 1 1 5 Related Documents rece anae ar a A EA E A R E a 1 2 1o Glossary or ICONS aieia a e th ea a ean ieee 1 2 Payments and Collections An Overview ssssssssssssesssnnnnnnnennnnnnnnnnnnne 2 1 21 IntroductiOn iic22 beeen edd A A E A A A A 2 1 2 1 1 Difference between DD and RFD cccccccceeceeceen tte eeeeeeennneeeeetenaaeeeeeeeaaes 2 1 2 1 2 Maintaining Module Specific Information ccccccccesececeeetsteeeeeesntteeeeeeenaaes 2 2 2 1 3 Maintaining Product ccccccccceeeeceecesnneeeeeeeenneeeeeeeeaeeeeeeeaaeeeeeesnaeeeeseeaaas 2 4 2 1 4 Product Categorii S moriani d aana EA OER A AE 2 4 2 1 5 Payments Contract Batch processing ssssseseeinneeeienneeernnnrerenenneeerennee 2 5 Maintaining Information Specific to Payments and Collections 3 1 SU ImtrOGUCthonsses4c2 ated a a AO ASE reel Micah Mis Ailes A 3 1 3 1 1 Maintaining Static Data ccc a re o E E EE E EE 3 1 3 2 Maintaining Information Specific to PC
320. on transactions are of two types e Direct Debit transactions DD e Request for Debit transactions RFD To process collection transactions the creditor s bank will send a message Outgoing DD RFD to the debtor s bank The debtor s bank will receive the message Incoming DD RD and after performing the required validations availability of funds agreement details etc will draw the specified amount from the debtor s account and transfer it to the creditor s bank In case of an RFD an approval message needs to be sent to the creditor s bank but in case of a DD no response needs to be sent A DD agreement is deemed to be approved in case no response is received from the debtor s bank within a specific number of days If for some reasons insufficiency of funds for instance the debtor s bank rejects the Incoming DD RFD the message will result in a Reject of Incoming DD RFD On the creditor s side the same will be processed as a Reject of Outgoing DD RFD Difference between DD and RFD The primary difference between a DD and an RFD transaction is that a DD will be considered processed settled if not rejected within the stipulated period known as the response period An RFD on the other hand will be considered closed if not approved within the specified response period Further you can recall a DD whereas an RFD cannot be recalled A recall is initiated by the debtor when he chooses to re collect his funds from the creditor
321. ons for the instruction Holiday Exception Indicate whether generation of transactions must be rolled forward when the generation date falls on a currency holiday If you check this box the system will check transaction value dates against the currency calendar of the transaction currency Frequency You must specify the frequency of generation of the instruction in terms of e Days e Months e Years Month End Flag In addition you can indicate that the transactions must be generated on the month end day Specifying Consolidation Details Consolidation This indicates if the customer leg of the transaction needs to be consolidated In case the customer account is in a foreign currency you cannot opt for consolidation Consolidation Reference If a reference is provided by the customer for the consolidation of the customer leg you must capture the same Specifying Other Details Generate Advice You can indicate whether a customer advice needs to be generated for the contract If you do not specify this after product resolution the transaction acquires the specification defined for the product Response Advice Basis Specify whether the response advice for the collection transaction is to be generated on the event date or the response date By default the system picks up this specification from the customer agreement Redispatch Reqd Indicate if this outgoing collection transaction needs to be redispatched if rejected
322. onse days by enabling the Process Rejects After Response Days option the customer leg of the transaction will be replaced by the reject suspense account that you identify for this purpose Reject Verify Funds Only Transactions involving a product can be rejected due to many reasons While defining a product you can indicate whether transactions involving the product should be rejected only if the reason is insufficiency of funds Response Days Basis As a product preference you have indicated whether the System needs to validate the rejects based on the maximum number of allowable days for receiving sending the rejects If the rejects are within the maximum number of allowable days i e 04 type of transactions a reversal of a DD is triggered for the rejects by enabling the Process Rejects After Response Days option If the rejects are beyond the maximum number of allowable days i e 05 type of transactions an appropriate warning or exception is given for the rejects You can indicate whether the Response Days should be derived on the basis of the Calendar Days or Working Days While processing transactions involving the product the Response Date is computed on the basis of your specification Scenario If you have selected Calendar as the Response Days Basis the Response Date is computed as follows Activation Date Response Days maintained for the product Therefore if the Activation Date is 01 April 2003 and Response Days maint
323. options available are e SCT SEPA Credit Transfer e SDD SEPA Direct Debits Bank Code Specify the direct or the indirect participant bank code for which the dispatch file parameters are maintained This is enabled for Bank dispatch type Customer Account Select the customer account number for which the dispatch file details are maintained This is enabled only for Customer dispatch type If you want to generate dispatch files for every customer you can select the option ALL Reference Number This indicates the reference number entered for every dispatch run This reference number is used to track the number of files generated as part of every dispatch run Maximum Number The following details are captured Files Specify the maximum number of files that can be sent to the clearing network in one settlement cycle Message Bulks Specify the maximum number of message bulks in a file No of Transaction in Bulk Specify the maximum no of transactions that can be bulked in a message bulk Test Mode Select the test mode from the drop down list The options available in the drop down list are e T Test e P Production mode for the clearing network This is a mandatory field for dispatch type as Network aan ORACLE File Format Type Specify the format of the file The supported file format is XML This is mandatory field File Path Specify the path where the file has to be generated Bulk Mess
324. ord Status Authorization Status In this screen you can specify the following details Bank Code Type Specify the type of identifying code that will be maintained for a bank in the system for instance SWIFT BIC BLZ IFSC and so on This code is used to identify the type of Bank code maintained in bank directory IFSC code is a unique code used to identify the banks in NEFT RTGS network Description Specify an appropriate description of the type of bank code specified in the Bank Code Type field 2 ORACLE 3 4 Maintaining Bank Directory You can maintain a list of Clearing Banks participating in payments and collections transactions in the Bank Directory Maintenance screen You can invoke this screen by typing PCDBNKMT in the field at the top right corner of the Application tool bar and click the adjoining arrow button Bank Directory Maintenance H save Bank Code Bank Code Type Bank Name City Address Country Code Pe National Clearing Code Valid From Date Ez Valid Till Date iE Main Bank Id Code Flag Branch Code SWIFT Address Customer No El International Bank Account Number Mandatory E Internal Clearing HHE Direct indirect Cover Direct Bank Code Direct Debit Participation Request For Debit Participati Gil e 6 baal Ce LC i Maker Date Time Mod No Checker Date Time Record Status Authorization
325. orization 1 Limit Specify the limit amount for level 1 authorization Authorization 2 Limit Specify the limit amount for level 2 authorization Release Limit Specify the limit amount for release Authorization Currency The system displays the authorization currency The outgoing payments will undergo one of the following treatments depending on the authorization limit and release limit e No authorizations and or release are needed e Only Level 1 authorization is needed e Level 1 and Level 2 authorizations are needed e Level 1 and Level 2 authorizations and release is needed e Level 1 authorization and release are needed fal ORACLE e Only Release is needed 4 2 4 2 Viewing Transaction Periods for Full Day Initiator Start Time HR MN Specify the contract initiation start time in hours and minutes for Full Day Auth Start Time HR MN Specify the contract Level 1 Auth start time in hours and minutes for Full Day Auth2 Start Time HR MN Specify the contract Level 2 Auth start time in hours and minutes for Full Day Release Start Time HR MN Specify the contract Release start time in hours and minutes for Full Day Initiator End Time HR MN Specify the contract initiation end time in hours and minutes for Full Day Auth1 End Time HR MN Specify the contract Level 1 Auth end time in hours and minutes for Full Day Auth2 End Time HR MN Specify the contract Level 2 Auth end time in hours and minut
326. ou can invoke this screen by typing PCSPRXSQ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Periodic Exception Queue f Search Advanced Search Reset D Clear All Case Sensitive Customer Account Branch Instrument Reference Product Code Records per page 15 v 10f1 Instrument Reference Product Category Product Code ui Detail Exception Ignore Retry Product Category Account No Customer No Account No Customer Account Branch Customer No c In this queue you can also view any instructions that have failed execution on any date earlier than the application date The periodic instructions in the queue are displayed grouped according to Instrument Reference Number Product Code Customer Account Customer Number Counterparty Name Counterparty Bank 5 62 ORACLE e Product Category e Transaction Amount e Customer Account Branch e Account Currency e Customer Bank e Counter Account Number To view the exceptions click the Exception button Click Retry to re process all the periodic instructions in the queue that have failed execution and have not been resolved on the application date If the generation is successful for any of the instructions they are marked resolved You can also choose to reject any of the instructions To reject a transaction click Ignore in the toolbar
327. ou selected the customer account using the option list available in the customer account field these fields will display the customer name and number respectively Clearing Branch The clearing branch for the specified customer bank code is displayed in this field Customer Bank Code and Account LCF You can input the bank code and the account in LCF local clearing format this is the clearing account number for the transaction Customer Address You can specify the address of the customer involved in the contract You can specify up to five lines of address information Customer Information If you need to specify other information regarding the customer of the transaction free format text fields are provided with appropriate labels applicable for your installation You can specify the customer information in these fields Specifying Counter Party details Counterparty Bank Select a valid bank code maintained in Oracle FLEXCUBE If you select a code from the option list the bank name is displayed instantly If you choose to enter the code the name of the bank is displayed when you save the transaction Counterparty Account You can specify the account of the counterparty here In case of internal transfers the account needs to be a valid account of Oracle FLEXCUBE either in Oracle FLEXCUBE or in the Local Clearing Format You can also select an account number from the option list provided In such a case the system will de
328. ounterparty entry value days and customer entry value days should be null Dispatch days should be null Auto response days should be null Processing Outgoing Payment Transaction Oracle FLEXCUBE allows you to manually authorize or release an outgoing payment transaction to the network If the transaction amount does not exceeds any of the authorization limits and release limit then the system will automatically send the outgoing payment transaction to the network Else you should send it manually When Outgoing Payment transactions require manual authorizations or release a significant time delay may exist between the initiation of a transaction in the system and actual transmission of the transaction message to the network During this time period the balance of the account which was found to be sufficient to support the payment at the time of initiation but if it is not sufficient at the time of authorization This will be handled by the system in the following manner e The system will block the funds against the account when the transaction is successfully initiated and unblock the funds and debit the account at a later and appropriate point of time 30 ORACLE e The system will unblock the funds if the contract gets reversed The process is as follows Initiate Outgoing Payment Payment Amount gt Auth1 Limit amount y Level 1 Authorization vy
329. owing e Waiting WT de ORACLE e Processed PD e Canceling CG e Canceled CD e Undelivered UD e Timeout TO e Reject XX e Error ER e Cancel Timeout CT e Cancel Error CE e Cancel Reject CX When the status of such a contract changes the event Outgoing Payment Status Change OPSC is triggered updating the status This event is logged in the event log for the contract and the details of processing can be viewed in the PC Contract View Events screen which you can invoke from the PC Transaction Input screen by clicking Events button a ORACLE 8 1 8 2 8 Payments and Collections Operations and Introduction Processes This chapter explains the following functions of the Payments and Collections module e Batch Process e Background Processing Batch Process for the Payments and Collections Module Batches are run automatically In the mandatory programs all batches whichever are required will be maintained in sequence and that is triggered automatically as based on the maintenance in the Mandatory Batch Program Maintenance screen You can invoke this screen by typing EIDMANPE in the field at the top right corner of the Application tool bar and click on the adjoining arrow button amp Mandatory Batch Program Maintenance E New amp Enter query Branch 000 Module End of Cycle Group Txn Input End of Txn Input End of Fin Input En
330. pecification will apply to all payment transactions processed under the product involving foreign currency accounts Alternatively you can choose to manually apply the exchange rate on transactions processed under the product In this case the exchange rate value that is specified for the transaction will be validated against the Exchange Rate Variance defined for the product Rate Code Specify the exchange rate code Rate Type Specify the exchange rate type that should be picked up for transactions processed under the product You can select any one of the following options e Mid Rate e Buy Rate e Sell Rate Mandatory Fields You can choose to validate collection transactions on the basis of the follwowing mandatory fields These include Agreement ID Required Check this box if you require customer agreement ID Creditor ID Required Check this box to make a customer agreement as mandatory Charge Details Waiver You can indicate whether charge processing is required for transactions involving the product If you would lile to process changes you can enable the check box positioned next to this field Allow Third Party Charge You can indicate that third party charges are allowed for rejected outgoing DD contracts using the product If third party charges are allowed the amount of a rejected outgoing collection transaction using the product is inclusive of the third party interest or charge The charge amount is c
331. pplication tool bar and click on the adjoining arrow button ad ORACLE Payment Gateway Message Bulks TSA E gt Search C Advanced Search Reset Y Clear All Case Sensitive Message Id az Message Creation Date faz Grouping Code FA File Reference fal Service ID az File Type Pa Instructing Bank fae Instructed Bank az Service Level Code az Priority az Original Message Name Status A Rejected Original Bank las Reject Process Status laz Records per page 15 x 10f1 a Messageld Message Name Message Creation Date Consolidation Required Control Sum Grouping Code File Refe View Process Reject You can filter your search based on any of the following criteria e Message ID e Message Creation Date e File Reference e Service ID e File Type e Instructing Bank e Instructed Bank e Service Level Code e Priority e Original Message Reference e Status e Reject Code e Reject Process Status Once you have set the filters you want click Search button to view the payment status report summary e Message ID e Message Name 20 ORACLE e Message Creation Date e Consolidation Required e Control Sum e Grouping Code e File Reference e Service ID e File Type e Bulk Count e Instructing Bank e Instructed Bank e Total Settlement Amount e Settlement Currency e Settlement Date e Settlement Method e Clearing System ID e Service Level Code e Priority e Original M
332. processing days for the following e Activation Date e Customer Entry days e Customer Entry Value days e Counterparty Entry days e Counterparty Entry Value days e Dispatch days e Payment Reject days e Response Days Network Calendar Check this box to validate the system date with network calendar Intermediary Suspense GL Required Check this box to generate the Intermediary Suspense GL entries if DRLQ and CRLQ are happened on same day Original Transaction Value Date Specify the value for the field to check whether back valued dated entry is allowed or not The field takes two values Yes No default The field is enabled for following product types e Reject of Incoming Collection e Reject of Outgoing Collection e Reject of Incoming Payment e Reject of Outgoing Payment e Recall of Incoming Collection e Recall of Outgoing Collection Restrict Automatic Upload of Mandate Select the option for the flag It is optional It has two options e YES Indicates FLEXCUBE will not allow upload of Mandate automatically during Incoming collection processing e NO Indicates FLEXCUBE will allow upload of Mandate automatically during Incoming collection processing This field is applicable for Incoming Collection products The default value for the field is NO but the value should be changed to YES for SEPA SDD B2B products Reversal without Matching Check this box if you want the reversal of incoming collection
333. pture transaction details ol ORACLE F New Enter Query Contract Reference m Reference Source Reference Network Main Transaction Details Collection Details Party Details Message Details UDF Processing Value Date Purpose Details Customer Entry Date Collection Type RFD Type Product Type Charge Details Charge Bearer Customer Entry Value Date Counterparty Entry Date Waiver Charge Counterparty Entry Purpose Value Third Party C Value Date Local Instrument Type Cu Instruction Date Local instrument Value Third Pai 9 r Amoun Settement Date Electronic Signature nitaton Date Receive Date of incoming Payment Details Structured Structured Invoicee Details Structured Invoicer Details Remitter Referenc Remi Remitter information uer Identification Type Identification Type BIC Name Additional Remittance info Payment Details Unstructured Sender Receiver information Payment Details 1 Sender Receiver Payment Details 2 Detaits Payment Details 3 Payment Details 4 P2P Payment Type Exception Details Other Details Reject Originator Name Reject Detail Reject Originator Bank Generate Remit Slip Reject Code Additional Reject Reference Bank Redirect Split Detaiis Events Charge Status ProjectDetails DuplicationDetails MIS Tax Processing Value Date Customer Entry Date This indicates the date on which the customer
334. quence in which the fields must be printed 3 30 1 Clearing Network Restrictions for Local Payment You can define and associate the Clearing Network Restrictions at the product category level in the product category through the Product Category Clearing Network Restrictions sub screen te ORACLE Click Network button in the PC Product Category Maintenance to invoke the Clearing Network Restrictions screen where you can define the clearing network restrictions for a Product Category Clearing Network Restrictions Clearing Network Allowed Disallowed Clearing Network Network Id Description li 3 30 1 1 Specifying Clearing Network Details You can maintain an allowed or disallowed list of networks The available networks are displayed in the Available list from where you can select the required networks and move them to the Allowed Disallowed section When a product category is defined the system validates that the network specified for the External Clearing Products linked to the Product Category are allowed for the Product Category also Also during modification of an existing Product with Clearing Mode as External Clearing the system validates that the Network being linked to the Product is not disallowed for any of the existing Product Categories which would have been already linked to the Product The Bank Codes linked to the available clearing network
335. r For existing mandate details if Mandate Status is set as Cancelled then system generates pacs 002 reject message which is sent to Creditor However if Mandate Status is set as a8 ORACLE Active then existing mandate status is updated as used and a new effective date is inserted with Mandate Status as Active 3 22 2 5 Transaction with Sequence Type FNAL When an Incoming Collection is processed with the sequence type FNAL system checks whether the mandate details are maintained in the Payments amp Collections Debtor DD Agreements screen If mandate details are maintained with Mandate Status as Active then the Mandate Status is updated to Final and Amendment reason is updated to PACS003 Also the Incoming Collection is processed further For the different transaction types the action taken as part of mandate maintenance based on the status of the existing mandate is summarized below Existing New SI No Transaction Mandate Action mandate Status Status 1 Incoming No mandate Mandate Used pacs 003 details would with OOFF be inserted Active Incoming No Change Used Collection would be Final rejected Cancelled 2 Incoming No mandate Mandate Active pacs 003 details would with FRST be inserted Active Incoming No Change Used Collection would be Final rejected Cancelled 3 Incoming Active Incoming No Change pacs 003 Collection with
336. r Periodic InstructionS ccccceeeeeeeeeeeeenteeeeeeeeneeeeeeeenaees 3 79 3 34 7 Counterpany TaD arser na jageeeed Manieedesdlaageereubldacerss bens 3 81 3 34 2 Specifying Counter Party details 0 cccccccccceeeseeeeeeeeneeeeeteeeaeeeeteeaeenees 3 83 3 34 3 Periddicihy fabisiic c e dai die ae ata a ek 3 85 3 35 Maintaining Details for Dispatch File eee eeeeeeeeeeeneeeeeeeeeeeeeeeeenaeeeeeeenaaes 3 87 3 36 Processing Incoming Payment ccccccceeseeeeeeeeeceeeeeeeeeaeeeeeeeaeeeeeeeneeeeeeeeaes 3 90 3 36 1 Mapping Product Categories to Message QUOUECS ccccceceteeteeeees 3 91 3 36 2 Mapping SWIFT and Non SWIFT Tags in Incoming Messages to Fields in the Pay ments and Collection Module 3 91 3 36 3 Maintaining the Unsettled Payment Account Or GL cccccccceseteeeneeeees 3 94 3 37 Outgoing Payments for Local Currency Transactions in Other Modules 3 96 3 37 1 Mapping Payments Module Settlement Details to other Modules 3 97 3 37 2 Maintaining Local Clearing Details and Cover Details for Customer Settlement In structions 3 99 3 37 3 Maintaining Local Clearing Details and Cover Details for Settlement Messages 3 102 3 37 4 Generation of the Local Payments Contract for Local Currency Transactions 3 102 3 38 Correspondent Bank Maintenance ceccecceeeeeceeceeeeeeeeeeeeeeseencnaecaeeeeeeeneees 3 103 3 39 Retrieving Creditor Direct Debit Agreement History eeeeeeee
337. r the recall days should be counted as Working Days or as Calendar Days Date Basis You need to select the date basis on which the recall date needs to be computed You can base it either on customer debit date or the activation date of the collection The options available in the drop down list are Debit Date or Activation Date By default Activation Date is selected Customer Entry Consolidation Required You can opt to consolidate the customer entry of transactions processed under a product Consolidated Limit If you choose to consolidate transactions processed under a product you can opt to specify a transaction amount limit Any transaction that exceeds the limit you specify will not be considered for consolidation All transactions will be considered for consolidation if you have chosen to consolidate transactions but do not specify a transaction amount limit Reversal General Ledger Reversal Settlement General Ledger In the Product Preference you can specify the GL to which the entries due to the debit leg of the DRLQ Debit Entry Liquidation event due to a cash reversal will be posted for transactions using the payments product Charge Bearer You can select the party who will bear the charges This is sent as part of the outgoing message for SCT and SDD The option available in the drop down list is e SLEV This indicates that the charges are to be applied following the rules agreed in the service level and
338. ranch Code Records per page 15 v 10f1 Contract Reference Network Activation Date Initiation Date Transaction Currency Transaction Amount Branch Detail Child In the Split Summary screen contracts marked for splitting in the transaction details are displayed based on the following e Contract Reference Number of the parent contract e Activation Date e Transaction Currency a9 ORACLE e Branch Code e Network e Initiation Date e Amount To view any of the child contracts for a split contract select it in the Split Summary screen and click Child button to view the child contracts 5 18 Process Exception Queues The Process Exception Queue lists exceptions that are raised in respect of transactions rejected during processing You have options for re processing or rejecting any or all of the transactions appearing in this queue These operations must be performed before the end of day cycle can be run You can invoke this screen by typing PCSPEXSQ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button amp Process Exception Queue E Search Advanced Search Reset 7 Clear All Case Sensitive Authorization Status Exception Queue Contract Reference Product Category Customer Account Branch Customer Account Currency Customer Bankcode Records per page 15 10f1
339. ransaction On initiation of the child contract the corresponding parent contract gets closed The child contract inherits all attributes of the parent contract The redispatched contract may be rejected by the debtor s bank again In such a case the creditors bank may redispatch the collection based on the parameters maintained in the agreement Every redispatch creates a new child contract The activation date of a rejected redispatch will be used to determine the date of the subsequent redispatch Auto Redispatch You can also select the Auto Redispatch option to indicate that the redispatch will be done automatically by the system Redispatch Count For an automatic redispatch you can specify the number of times a transaction can be redispatched in the Redispatch Count field A redispatch may eventually result in a funds transfer if sufficient funds are available in the debtor s account If funds are not available even after the last redispatch the system will process it as a reject transaction Redispatch Days For an automatic redispatch you can indicate the number of working days redispatch days to be added to the activation date to arrive at the date on which a transaction is to be redispatched Response Details Auto Response An RFD transaction if not approved within the response period is considered closed Select the Auto Response option to indicate that the approval or closure will be handled automat
340. ransfer the system picks up the outgoing book transfer product specified here the customer leg is processed using this product along with the product clearing currency You can capture multiple products for a book transfer The Incoming Product Category specified for the outgoing product is picked up The Incoming Product Category maintenance is referred and the product which corresponds to the incoming transaction within this product category is picked up The counterparty leg of the transaction is processed using this product Case Two e The outgoing product category maintenance is referred Ifthe transaction does not fit the specifications of the book transfer product the system tries to fit the transaction in the list of internal clearing products you have maintained in the sequence you have specified Ifthe transaction fits the parameters defined for an internal clearing product the transaction is processed using the product Case Three e The outgoing product category maintenance is referred Ifthe transaction does not fit the specifications defined for any internal clearing product the system tries to match the transaction with the external clearing products you have specified for the product category in the sequence you have specified The transaction is then processed using the first product in the list of external clearing product whose parameters match that of the transaction Offset Category
341. reference Their Reference Custom reference Network Batch Number Product Category Product Code Priority Customer Number Bank Code Account LCF Account Branch Account Number Account Currency Foreign Currency Amount Remitted Amount Exchange Rate Bank Code Account Number Counter Party Name Cutoff Status Activation date Redispatch Required Agreement ID Reject Code Reject detail Compensation Amount Original Collection Reference Clearing Branch Transaction Currency Local Currency Equivalent Auto manual Acknowledgement Status Contract Status Reject reference Number Creditor ID Exception Queue Collection Status Authorization Status FX Contract Reference BIC ID 5 41 ORACLE 5 4 Simplified Entry of Payments and Collection Transactions For entry of transactions using the following product types a simplified transaction entry screen the PC Fast Transaction Input screen is provided to enable you to key in transactions with the basic transaction details e Outgoing Incoming Payments e Outgoing Incoming Direct Debits e Outgoing Incoming Request For Debits You can invoke the PC Fast Transaction Input screen from the Application Browser by typing PCDFSTNL in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Transaction Branch Select the appropriate branch from the list of branches available in the option list On cl
342. reference number CSM Reject Code The system displays the ISO reject code for the rejection from Clearing Settlement Mechanism CSM Reject Detail The system display the CSM Reject Detail to describe the ISO reject code for the rejection from CSM Reject Originator Name The system displays the reject originator name Reject Originator Bank The system displays the reject originator bank Reject Reference Number The system displays the reject reference number Payment Reject Date Specify the payment reject date from the adjoining calendar Other Details Cutoff Status This indicates if the transaction was received before the cutoff time defined for the product Cover required The system displays the cover message preference you have maintained for the counterparty as part of the Clearing Network maintenance The system defaults the values in Direct Participant and Cover field only if you have maintained the information for the contract In case you have maintained the counter party bank code without a clearing network the system defaults the values for both the above fields only after you save the contract Generate Advice You can indicate whether a customer advice needs to be generated for the contract If you do not specify this after product resolution the transaction acquires the specification defined for the product a ORACLE Generate Remit Slip Check this box to generate remit slip Bank Redirect Check t
343. regarding the transaction that is to be generated Charge Mode You can indicate whether charges applicable for the transaction are to be applied over and above the transaction amount premium or subtracted from the transaction amount discount Counterparty ID Details The counterparty details are defaulted on selection of counterparty account number if the counterparty identification details are maintained in PC Beneficiary Maintenance screen Identification Select the option to identify the counterparty either by Organization details or by Individual person details The options available in the drop down list are Organization Identification and Private Identification Identification Value Specify the identification value for the counterparty for the given identification type This is mandatory only if the Identification type is specified a4 ORACLE 3 34 3 Issuer Specify the Identification Issuer of the counterparty This is used to identify if Organization identification is used as Proprietary Identification or Private Identification Counterparty Scheme Name Type Select the Identification Scheme Type of the Counterparty from the drop down list The valid field can be e C Code e P Proprietary Counterparty Scheme Name Specify the value for Identification Scheme Name field If Scheme Name type is C then the Scheme Name can be selected from LOV and can have one of the values mentioned in value list depending on Org
344. rence Collection Type Product Code Custom Reference RFD Type e Source Reference Product Type Network Main Transaction Details Collection Details Party Details Message Details UDF Customer Details Account Number Bank Code Customer Number Account Description Bank Name Customer Name Bank Address 1 Clearing Branch Account LCF Bank Address 2 Branch Name Account Branch Bank City Virtual Account Account Currency Virtual Account Name I Available Balance Additional Customer Details Counter Party Dotaits Counterparty Bank g Account Number Counter Party Name Direct Participant Bank Code Bank Name Bank City Bank Address 1 Bank Adaress 2 Additional Counter Party Details Transaction Detaits Book Date Exchange Rate Customer Activaton Date FX Contract Reference Transaction Currency Cutoff status Amount Message Status 0 on Local Currency Collection Status Reference Local Currency Exception Queue Account Entry Equivatent Reference Foreign Currency Current Number Service Level Coce Batch Number Foreign Currenc t Batch Description Amount Remed Amount AutoManual Currency Remite Amount Charge Amount Spit Detaiis Events Charge Status Project Details Duplication Details MIS Tax 2 The following details are displayed in the main screen of the contract Product Category The category you specified on invoking this screen will default here You cannot change the default Product Code Specify the produc
345. ress Agreement Cancellation Charge To indicate applicability of charges or fees levied on setting up and or amending direct debit creditor or debtor agreements you can enable the Charges Applicable option in the PC Debtor DD Agreements screen The applicable charges are computed through the Interest and Charges IC module For details refer the Interest and Charges module user manual System applies mandate cancellation charge only if Charge Applicable is checked For more details on mandate cancellation charges refer section Maintaining Mandate Cancellation Charge Details later in this chapter Charge Reference Number System displays a reference number for the mandate cancellation charge For more details on mandate cancellation charges refer section Maintaining Mandate Cancellation Charge Details later in this chapter Transaction Type Specify the value from the adjoining drop down list The list has following options e One off e Recurrent Maximum length for this field is 9 Transaction type is mandatory if the collection scheme type is B2B sal ORACLE Payment Details 1 Payment Details 2 Payment Details 3 and Payment Details 4 Specify unstructured remittance information The fields hold free format text of 35 characters each Purpose of Collection Specify the need of the collection transaction here The field is optional Validity Details Expiry Date Specify the end date
346. reversal is after liquidation it will have no impact on the utilization of the FX contract So if the PC contract is reversed prior to liquidation then the system will send DLNK details to FX contract to update the utilization Customer Consolidation at Product Level Specify the preference for consolidating customer at product level by selecting an appropriate option from the drop down list The options available in the drop down list are e Yes e No e Blank Customer Consolidation Across Products Check this box to consolidate the transactions of a customer across the products Customer Consolidation Reference The system displays the customer consolidation reference number If Customer Consolidation at Product Level or Customer Consolidation Across Products is checked then a unique customer consolidation reference number is captured for all those transactions booked Manually If Customer Consolidation Across Products is checked then system populates the customer consolidation reference number with Payment Information ID generated at the Common Payment Gateway for all those transactions consolidated for a customer across different products Account Entry Reference The system displays the account entry reference Service Level Code Priority which is a user defined field set at the product category level is defaulted in this screen Specifying Transaction Details Click on the Transaction Details tab to ca
347. rict Automatic upload of Mandate check box must be checked This will disallow automatic upload of debtor mandate 5 31 Processing Expiry Date For the expiry date maintained agreement records with status as Active are updated as Expired as part of batch process Each incoming collection transaction is checked against status of the corresponding mandate If the status of agreement is Expired then incoming collection transaction will be moved into Transaction Repair TR queue Static data for error code PC MAND 07 with description as Agreement Expired is available Auto rejection for the above error can be configured and the incoming transaction is rejected automatically Incoming Collection transaction will be processed only if the agreement status is Active Expiry Date validation is applicable to Outgoing Collection transaction also with respect to Creditor Direct Debit Agreement 5 32 Restricting Maximum Amount per Transaction Maximum Amount per Transaction maintained at Debtor Mandate level will be checked for each Incoming Collection transactions Currency is converted when the incoming collection transaction s currency is different from debtor account s currency If incoming collection transaction amount exceeds maintained Maximum Amount per Transaction then the system moves the incoming collection transaction to Transaction Repair TR queue Auto rejection for the error code PC SVV
348. ring contract Save Level 1 Authorization Level 2 Authorization and Release stages If the contract fails on the above validations then system will not process the contract further 4 8 Processing Incoming Payment Transaction An Incoming Payment transaction can be defined such that it requires authorization before its target account is credited INCOMING PAYMENTS PATH Message repair Incoming Payment from network Account credit Transaction authorization if Payment Amount gt pre defined INCOMING_AUTH_LIMIT Incoming payment transaction limits are be defined in product level You need to maintain a separate product for both NEFT and RTGS Following are the levels of authorization for incoming payments e A single level of authorization can be imposed on an Incoming Payment e Based on the transaction amount details the system will authorize the incoming payment In case the incoming payment exceeds the amount set for authorization it will require a maker and checker for authorization Ifthe incoming payment transaction amount is less than or equal to the authorization limit then no authorization is required Ifthe incoming payment transaction amount is greater than the authorization limit then authorization is required 4 8 1 Viewing Incoming Transaction Authorization Details Oracle FLEXCUBE allows you to view the incoming transaction authorization details using the Payments and Collection In
349. ring network for the currency correspondent Retrieving Creditor Direct Debit Agreement History Oracle FLEXCUBE facilitates retrieval of the history of agreement records pertaining to particular Creditor using Creditor Direct Debit Agreement History screen You can invoke this ait ORACLE 3 40 screen by typing PCDCRAHS in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Product Description Customer Customer Name Branch Creditor Account Currency Counterparty Details Debtor Account Bank code Bank Name Date Of Signature Transaction Details Charge Reference Number Transaction Type Payment Details 1 Payment Details 2 Payment Details 3 Payment Details 4 Purpose Of The Collection Creditor Direct Debit Agreement History Agreement Cancellation Charge Version Number Collection Scheme Type Creditor ID Scheme ID Agreement Id Creditor Reference Code Debtor Name Address 1 Address 2 Address 3 Address 4 Country Validity Details Effective Date Expiry Date Agreement Status Amendment Reason Fields Maker Checker Version Number Date Time Date Time Authorization Status This field displays the corresponding version number Mod No Record Status For further details refer the section Maintaining DD Agreement Details for Creditors in this user manual
350. rk the system displays the direct participant of the corresponding counterparty BIC In case of counterparty being direct participant the field is null op ORACLE Transaction Details Book Date The system displays the book date of the transaction Activation Date This is the activation date of the contract The system defaults to the current date However you can change this Since you can post back value dated PC transactions for the purpose of risk tracking you can indicate a date beyond which users will be prevented from posting a back value dated transaction by enabling the Back Value Check Required in the Branch Preference screen The System validates whether the activation date falls within the maximum period up to which back valued posting can be processed Transaction Currency Enter the currency for the transaction You can click on the adjoining option list to choose from a list of valid currency codes maintained in the system Input to this field is mandatory If the network ID is input then the system will be display the currency linked to the clearing network in this field If the product code is input then the system will display the currency linked to the product in this field You will not be able to change the defaulted value The system will ensure that this currency code is the same as that linked to the product code and network ID of the contract Amount This refers to the transaction amount i e the
351. rk charge e Charges for transactions initiated manually e Charges for transactions initiated through EB You would build the expression for the first charge for processing transactions over the clearing network as follows Set Condition No Case Charge Code 1 1 No condition CNSY You would build the expression for the second charge as follows Condition Charge Set No Case Code 2 1 IF Manual and Internal payments THEN CMIN G2 ORACLE 2 2 ELSE IF Manual and Inter branch payments THEN CMIB 2 3 ELSE IF Manual and Standing order charge THEN CMSO 2 4 ELSE IF Manual and Payment remittance by fax THEN CMPF 2 5 ELSE IF Manual and Payment remittance on paper CMPP form THEN You would build the expression for the last charge as follows Condition Charge ae No base Code 3 1 IF Through EB and Internal payments THEN CEIN 3 2 ELSE IF Through EB and Inter branch payments THEN CEIB 3 3 ELSE IF Through EB and Standing order charge THEN CESO 3 4 ELSE IF Through EB and Payment remittance by fax CEPF THEN 3 5 ELSE IF Through EB and Payment remittance on paper CEPP form THEN Note that the expressions IF THEN and ELSE are used to better explain the procedure of setting up a charge for different transactions conditions When building an expression in this screen these are implicit and exclusive wi
352. rocessing Incoming Payments Oracle FLEXCUBE provides the facility of processing incoming payment messages which are uploaded into Oracle FLEXCUBE and processed as incoming payment transactions in the Payments and Collections module In order to facilitate such processing for incoming payments you must e Map the requisite product categories in the Payments and Collections module to the requisite message queues to which the incoming payment messages are routed when they are uploaded e For different combinations of incoming message type product category source code and station ID maintain mappings between the CPG fields and their corresponding fields in the Payments and Collections module This enables the STP process to interpret the incoming message and resolve the details into a PC contract in the system aay ORACLE 3 36 1 3 36 2 Mapping Product Categories to Message Queues To recall in order to facilitate the processing of incoming payment messages you must map the requisite product categories in the Payments and Collections module to the requisite message queues to which the incoming payment messages are routed when they are uploaded You can do this in the Product Mapping Detailed screen You can invoke this screen by typing MSDPRMAP in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Product Mapping E New E3 Enter Query Branch Branch Des
353. ropriate reject code Note For transaction rejects outgoing or incoming DD that are uploaded after the applicable response days have elapsed an override is sought by the system The processing for such transactions is based on two factors Whether the Process After Response Days option has been set in the product preferences for the product used by the transaction Whether the override that is sought in such cases is accepted Accepting the over ride in the case of incoming DD transactions would result in rejection of the trans action In the case of outgoing DD the transaction is placed in the Process Exception Queue from where it can be taken up for processing or rejected For more details about the rejection process in the case of such transactions refer the chapter Defining the attributes specific to Payment and Collection products in this user manual Reverse an authorized active or liquidated collection transaction During reversal all accounting entries passed for the contract are reversed out A reversal operation must be authorized to be effective once authorized no further operations are possible on the transaction Click reversal icon to reverse a transaction Note During reversal of a transaction the System verifies whether the transaction has been dis patched earlier If so an override is sought On accepting the override the reversal will proceed Collection Status of a Transaction
354. rty An outgoing payment transaction goes through the following stages after it is dispatched Waiting WT After dispatch till a response is received the transaction is in waiting Processed PD When a positive response is received the transaction is said to be processed Canceling CG After processing if the transaction is required to be canceled an appropriate message to this effect is sent to the interface Canceled CD When a positive response to a canceling message is received the transaction stands cancelled Undelivered UD If after successful processing the creditor s bank is not able to deliver payment to the ultimate beneficiary and an appropriate message is received to this effect the transaction is said to be undelivered Timeout TO If no response is received within a stipulated period for an outgoing payment the message would be re dispatched a stipulated number of times When the stipulated count is reached the transaction is said to be timed out This situation could also arise when no response is received to a canceling message in which case the transaction acquires a Cancel Timeout CT status Reject XX The receiver of the payment message could reject it In such a case the message stands rejected This situation could also arise when a canceling message is rejected in which case the Cancel Reject CX event is automatically logged for t
355. rward contract must be active and authorized e Option Date is mandatory for the FX forward contract e Foran outgoing PC Transaction the Transaction Currency of the PC Transaction must be equal to the Sold Currency of the FX contract and Customer Account Currency of the PC Transaction must be equal to the Bought Currency of the FX contract e For Incoming PC Transaction the Transaction Currency of the PC Transaction will be equal to the Bought Currency of the FX contract and Customer Currency of the PC Transaction will be equal to the Sold Currency of the FX contract e For Outgoing or Incoming PC Transaction the Customer Entry Date must be greater than or equal to the Option date and less than the maturity date min of Bought Value Date and Sold Value Date of the FX contract e The Customer of the PC Transaction must be the Counterparty of the FX contract e The unutilized Amount of the FX contract must be greater than or equal to the PC Transaction amount r ORACLE The unutilized sold Amount of the FX contract must be greater than or equal to the transaction amount for Outgoing PC Transaction or unutilized buy Amount of the FX contract must be greater than or equal to the transaction amount for Incoming PC Transaction The FX forward contract linked to PC Transaction cannot be part of combination product It cannot have NDF feature and settlement cannot be through CLS The FX contract linked as Collateral cannot be linked to PC Trans
356. ry with the current logged in branch country to identify whether payment is a domestic or a cross border payment The product is then resolved appropriately Currency Specify the currency in which PC contracts linked to this product should be created The adjoining option list displays the currency codes maintained in the system You can select the appropriate one Clearing House Account Account The accounting entries for a payment or collection transaction using the product could be passed to either a clearing vostro account or to a clearing suspense GL If they are to be passed to a vostro account you must specify the appropriate vostro account in this field Note If you have indicated a clearing account the system populates the BIC of the clearing ac count in the advice message tag NOSTRO BIC This tag will be null if clearing account is not specified for the PC Product Branch The branch of the clearing house account is displayed Currency The currency of the clearing house account is displayed External Clearing Clearing Network Indicate the preferred clearing network All payments processed under this product will be funneled through this network to the external entity Minimum Divisible Amount A key preference that you can specify for a product is the lowest denomination in which transactions involving the product can be processed Specifying a minimum divisible amount helps you restrict transaction
357. s The details maintained here will be used to validate incoming transactions initiated by the creditor The agreement is maintained for a Product Customer and Customer Account combination only if the corresponding customer agreements exist and you have indicated that a DD agreement is required for the respective customer agreements oe ORACLE Customer Product Code Select the product from the list option provided This is applicable only if the corresponding customer agreements exist and you have indicated that a DD agreement is required for the respective customer agreements Customer Specify the customer if the corresponding customer agreements exist and you have indicated that a DD agreement is required for the respective customer agreements Branch Specify the branch if the if the corresponding customer agreements exist and you have indicated that a DD agreement is required for the respective customer agreements Account No Specify the account if the corresponding customer agreements exist and you have indicated that a DD agreement is required for the respective customer agreements Service Level Code The system displays the value of Service Level Code maintained at product level once you select the product code Collection Scheme Type The value for the field is defaulted from the selected product The value is initially Specified in Payments and collections product definition screen PCDPRMNT The field is used
358. s e Securities e Standing Instructions In the Branch Parameters you can specify whether these payment instructions for LCY transactions in the branch must be routed either through messaging or through the local clearing network 220 ORACLE 3 37 1 Click the LCY Msg Pref button in the Branch Parameters Preferences screen to invoke the LCY Message Preference screen 4 Branch Parameters LCY Message Preferences Branch Description Messages Type 1 Of 1 E Module Module Description Local Currency Message Type In this screen you can specify any of the following options for messages related to LCY transactions in any of the modules mentioned above In the LCY Message Type field the following options are available Suppress LCY message If this option is chosen then the payment is routed through the local clearing network external to Oracle FLEXCUBE and the message is suppressed Gen PC Contract If this option is chosen a contract is generated in the Payments and Collections module for the local currency payment provided that the payment option chosen is Local Clearing or if the payment option is Message and the cover option is Local Clearing Gen LCY Message Thru SWIFT If the option is chosen local currency payments are sent as SWIFT Messages routed through the SWIFT network This option is the default and you can change it if necessary Mapping Pay
359. s Authorization Status Debtor Customer Category Specify the Debtor Customer Category code here Description Enter a small description of the Debtor Customer Category you have entered a7 ORACLE 3 33 3 33 0 1 3 33 0 2 Defining Preferences for a Combination of a Product and a Debtor Category The Payments And Collections Debtor Preferences Maintenance screen allows you to define the preferences for a debtor category created by you You can invoke this screen by typing PCDPRCAT in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Payments And Collections Debtor Preferences Maintenance E New E3 Enter Query Products Product Code Debtor Category Product Description Description Preferences Maximum Transaction Amount Currency Recall Days Recall Days Basis Date Basis Maker Date Time Checker Date Time Mod No Record Status Authorization Status Specifying Product details Product Select the product from the list of options available You define a product the maximum amount for each transaction the number of recall days and the basis working days or calendar days for computing recall days Debtor Category Select the debtor category from the list of options available Specifying Preferences Maximum Transaction Amount Specify the maximum amount that can be used for a transaction The currency for this amount wil
360. s are displayed in PC Contract Online screen and PC Fast Input Screen for the Product Category The displayed bank codes list sequence is driven by the way of you navigate through the Contract Online screen After entering the product category details if you proceed to the bank code without entering the product code and network the entire list of bank codes used by that product is displayed If you enter the product code after entering the product category details then e Ifthe Product is Book Transfer Type the network field is blank The Book Transfer Type of Bank Codes from the PC Bank Directory is displayed in the list of Bank Codes from the PC Bank Directory e If the specified Product is internal type the network field is blank The entire list of bank codes used by that Product is displayed e Ifthe product is of the type external the default network chosen in the product preference screen is displayed Only those bank codes using this network are displayed On entering the product category details if you click on the Networks option list then only networks allowed for that product category are displayed and on selecting the network a8 ORACLE e If you click on the bank code without entering the product code then only the banks using this network are displayed e Ifthe product code is entered the network defaulting happens as explained 3 30 1 2 Specifying the Clearing Network Details 3 31 Network ID Sel
361. s been split into multiple contracts If it has not been split this field indicates Not Applicable If the transaction has been split this field indicates whether the transaction being viewed is a parent transaction or a child transaction Invoice Split Required Indicate if the collection transaction needs to be split into multiple transactions if the transaction amount exceeds the maximum amount specified in the debtor DD agreement Auto Redispatch Indicate if this outgoing collection transaction needs to be redispatched automatically if rejected Redispatch Date Specify the date of redispatch of the parent transaction Authorization Reject Remarks The remarks if any that were specified for rejection of the transaction are displayed here Incoming Message Details File Ref No This indicates the file reference number of the incoming instruction This is a display only field Message Identification This is a unique message bulk reference number populated from the incoming instruction This is a display only field Message Name This indicates the message name identifier of the incoming message For e g Pain 001 001 01 This is a display only field and is populated from the incoming instruction Msg Creation Date This indicates the date and time the transaction was created This is a display only field and is defaulted with the value in the incoming instruction Instructing Bank This indicates the sender bank of the incom
362. s required during authorization the value will not be displayed You have to input the values in the re key fields to authorize the contract If the re keyed values for the contract do not match the contract you are calling for authorization an error message is displayed All overrides provided by maker of the record will be displayed On confirmation the contract is marked as authorized You can Skip a record that is displayed for authorization or choose not to authorize it by clicking on the Reject button All records that you reject will form a part of the Transaction Re input Queue Refreshing the Exchange Rate As mentioned earlier the exchange rate applicable for transactions involving foreign currency customer accounts is either automatically picked up or manually entered depending upon the product preferences On a given business day you can trigger the refreshing of exchange rates for all products used at a branch in the Exchange Rate Refresh screen You can invoke this screen by typing PCDTRFSH in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Exchange Rate Refresh Propagate Across Branches Rate Refresh 1 Of 1 T Product Code ProductDesc Rate Available You can also update the refreshed exchange rate across all branches by selecting the Propagate Across Branches option Processing Credit Exceptions If the customer liab
363. s respectively at cancellation request level Rejection of Cancellation of Collections On rejection Cancellation Status at cancellation request level would be marked as Rejected Reject Code Reject Detail entered during reject operation would populate CSM Reject Code and CSM Reject Detail fields respectively at cancellation request level This rejection process would re activate the original Outgoing Collection with the contract details as prior to the cancellation An event RACT will be logged for the original Outgoing Collection in the contract events data store Handling Cancellation of Outgoing Payments amp Collections that are not dis patched to CSM Cancellation requests are made in Payments and Collections Cancellation PCDRCLIN screen You can Reject the Outgoing Payment contract by performing pre settlement rejection RUBS if the Outgoing Payment is not dispatched On Rejection The status will be changed into Recall Success Accounting entries passed during debit liquidation and credit liquidation would be reversed Dispatch process does not consider this rejected Outgoing aia ORACLE 5 24 1 2 Payment contract and Cancellation request Cancellation of Outgoing Collections that are not dispatched to CSM would follow the same processing as described in the above points Handling Manual Rejection of Cancellation Camt 056 for Payments and Col lections Payments and Collections Can
364. s screen you must enter the following details Source Code Specify a unique code that will identify the source throughout the system Description Enter a brief description of the source Oracle FLEXCUBE has the following inbuilt upload sources e MANUAL_BOOK Manual Book e MANUAL_REJT Manual Reject e MANUAL_APPR Manual Approval e MANUAL_RECL Manual Recall e MANUAL_RDSP Manual Redispatch Note Users at your bank can ONLY process payment transactions received from a source that is maintained in this screen cee ORACLE 3 17 Specifying Parameters for a Source For a combination of product category source code and customer you can maintain certain upload parameters such as e An Automatic Authorization Limit e Whether uploaded transactions can be deleted e The fields that can be amended e The number of working days calculated from the initiation date of the transaction for which the messages need to be retained in the system e The source parameter maintenances should be in sync with the maintenances for external systems in Gateway module For more information on Gateway Maintenances please refer to Gateway Maintenance user manuals You can setup upload parameters in the Source Parameters Maintenance screen and invoke this screen by typing PCDUPLDT in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Source Parameters Maintenance
365. s to specific denominations You can also use this facility to specify the minimum factor for the transaction amount In such a case the transaction amount of transactions processed under the product should be a multiple of the Charge Mode You can indicate whether charges applicable for a transaction involving the product are to be applied over and above the transaction amount premium or subtracted from the transaction amount discount Minimum and Maximum Transactions Amount For a Payments product you can specify a transaction range If a transaction is to be processed under a product its size in terms of the transaction amount should be within the transaction range that you specify for the product The Maximum Transaction Amount and the Minimum Transaction Amount that you specify constitute the transaction range ga ORACLE Invoice Split Required If the transaction amount of a transaction involving this product exceeds the maximum amount specified for the product you can indicate that the collection transaction needs to be split into multiple transactions You can enable this option by checking the Invoice Split Required option Cut Off Time Transactions received after the cutoff time that you specify for a product will be processed according to the postcutoff parameters you maintain Your cutoff time specifications will apply to all transactions processed under the product Processing Priority When creating a pro
366. s unauthorized PC SAV 024 Customer account has been blocked PC SAV 025 Stop Payment has been issued against customer account PC SAV 026 No Credit is allowed for the customer account PC SAV 027 No Debit is allowed for the customer account PC SAV 028 Customer account is dormant PC SAV 029 Customer account is frozen PC SVV 092 Unable to get creditor DD agreement for product 1 customer 2 and account 3 4 aae ORACLE PC SVV 093 Unable to get creditor DD agreement for product 1 customer 2 and account 3 4 PC SVV 094 Creditor DD agreement for product 1 customer 2 and account 3 4not valid as of 5 PC SVV 095 Creditor DD agreement for product 1 customer 2 and account 3 4not valid as of 5 PC SAV 024 Customer account is blocked PC SAV 025 Payment not allowed for customer account PC SAV 026 Credit not allowed for customer account PC SAV 027 Debit not allowed for customer account PC SAV 028 Customer account is dormant PC SAV 029 Customer account is frozen 3 37 Outgoing Payments for Local Currency Transactions in Other Modules Oracle FLEXCUBE provides the facility of generating outgoing payment instructions through the Payments and Collections module for local currency transactions in any of the following modules e Foreign Exchange e Money Market e Loans and Deposits e Letters of Credit e Bills and Collection
367. sactions that are failed during cancellation Acceptance and Rejection processing The exception queue status for the failed transactions during cancellation processing will be CR The error code and error description for the failures can be displayed in this screen against each transaction You can invoke this screen by typing PCSCANEX in the field at the top right corner of the Application tool bar and click on the adjoining arrow button Incoming Cancellation Exceptions Queue E search C Advanced Search 5 Reset 4 Clear All Case Sensitive Recall Reference Number az Contract Reference Records per page 15 x 10f1 Recall Reference Number Contract Reference Direction Recall Status Account No Product Code Customer No This screen will have the following fields Recall Reference Number Indicates the reference number generated for cancellation Maximum length can be 16 characters Contract Reference Indicates the original contract reference number for which cancellation is received Maximum length can be 16 characters Direction Indicates whether the transaction is incoming or outgoing Maximum length can be 1 character Recall Status Indicates the status of cancellation Maximum length can be 1 character ont ORACLE 5 24 2 Customer No Indicates the customer involved in the transaction Maximum length can be 9 characters Product Code Indicates the product used for the original contract Maximum length c
368. sactions for Calendar Year field For CORE and COR1 collections scheme types Debtor originated recall Refund transactions will not decrement the count in Utilized Transactions for Calendar Year field The R transaction will decrement the Utilized Transactions for Calendar Year only if the R transaction is received in the same calendar year as the original collection If the R transaction is received in a different calendar year then it will not decrement the Utilized Transactions for Calendar Year Utilized Transactions for Calendar Year field will get reset to 0 on beginning of every new calendar year if there are no active incoming collection transactions If there are active incoming collection transactions at beginning of calendar year then the Utilized Transactions for Calendar Year field will get updated with transactions amount If Number of Transactions per Calendar Year is not maintained then incoming collection transaction is not validated against transactions count and Utilized Transactions for Calendar Year is not updated During the course of the calendar year when Number of Transactions per Calendar Year gets maintained then the subsequent incoming collection transactions and its R transactions will impact updating Utilized Transactions for Calendar Year Any incoming collection transaction and its R transaction processed prior to Number of Transactions per Calendar Year
369. sage On receipt of Pacs 002 for an Outgoing Camt 056 for outgoing collection The cancellation request would be marked as Rejected Fields CSM Reject Code CSM Reject Detail and CSM Reject Reference Number for the cancellation request will be populated with the received reject code reject description and reject reference number from Pacs 002 The RJBS event processed will be nullified by processing reactivation event on the outgoing collection with contract details as prior to the cancellation This would enable the outgoing collection for further cancellation operation 002 for Reversal of Outgoing Collections Pacs 007 sent by Creditor Bank Reversals of Outgoing Collections are generated by processing reversal operation REVP event On receipt of Pacs 002 for Reversal of Outgoing Collections the underlying Reversal of Outgoing Collection contract would be rejected by processing pre settlement reject RJBS event RJBS event on Reversal of Outgoing Collection Will mark the contract as rejected and accounting entries if posted would be reversed 2 ORACLE Will populate new fields CSM Reject Code CSM Reject Detail and CSM Reject Reference Number at contract level with the received reject code reject description and reject reference number from Pacs 002 Will also reactivate the Original Outgoing Collection by processing Reactivation Event e The reactivation event
370. should be collected This is used to track the collection of statistics You can associate the appropriate charge category with the product which you are creating Volume Statistics As part of specifying the charge details you will need to indicate whether details of transactions using the product need to be tracked for charge computation or not Choose one of the following options to specify your choice e Add To add the transaction details to the volume statistics e Subtract To subtract the transaction details from the volume statistics e ignore To indicate that the transaction details are not to be collected for volume statistics You can also indicate the following levels for collection of charge data for transactions using the product e Customer charge statistics e Charge account statistics Dispatch File Name In the main section of the screen if you have indicated that transactions involving the product should be dispatched to the Clearing Server on the basis of the dispatch days that you specify then you have to indicate the dispatch file name that you wish to be generated ane ORACLE Number of Records Specify the number of record transactions to be considered while creating a dispatch file Specify the type of clearing network to which the dispatch file would be sent Payment Reject Days You can specify the number of days by which an incoming payment can be rejected The number of days specified will be considered
371. sider only certain product categories The Payments and Collections Charge Category Maintenance screen allows you to name and describe such product categories as will be considered for computing transaction volume statistics in the Product Preferences screen You can invoke this screen by typing PCDPROCH in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button amp Payments and Collections Charge Category Maintenance E New amp Enter Query Charge Category Description Maker Date Time Checker Date Time Mod No Record Status Authorization Status Charge Product Category Specify the category to which a charge product belongs to Description You can describe the category for charges which are maintained by the bank The transaction statistics so collated under various product categories may be used to define charge rules at the product definition level oe ORACLE 7 1 7 Outgoing Payments Workflow Introduction The normal life cycle of an outgoing payment transaction ends when the debtor makes payment After payment has been dispatched for an outgoing payment transaction your bank may require tracking related to receipt of confirmations from the counterparty For this Oracle FLEXCUBE provides the facility of tracking and monitoring outgoing payment transactions from the time they are dispatched till confirmation is received from the counterpa
372. sponse would be populated with the received reject code reject description and reject reference number from Pacs 002 This process will enable the cancellation request Camt 056 as active and the cancellation request can be responded with Negative response again 5 28 2 Processing pacs 002 messages Collections The processing of Pacs 002 message received from Clearing Settlement Mechanism for SEPA Direct debit is as follows Pacs Pacs Pacs Pacs 002 for Outgoing Collections Pacs 003 sent by Creditor Bank On receipt of Pacs 002 for the Outgoing Collection from CSM the underlying Outgoing Collection will be rejected by processing pre settlement reject RJBS The processing of Pacs 002 messages received on due date for the Outgoing Collection will follow the same procedure as stated above and the accounting entries posted during debit liquidation and credit liquidation would be reversed 002 from Debtor Bank for Outgoing Collections Pacs 003 sent by Creditor Bank On receipt of Pacs 002 for the Outgoing Collection from debtor bank the underlying Outgoing Collection will be rejected by processing pre settlement reject RUBS Accounting entries during debit liquidation and credit liquidation if posted will be reversed 002 for Cancellation of Outgoing Collections Camt 056 sent by Creditor Bank The cancellation operation on outgoing collection will process pre settlement RJBS reject and generate Camt 056 mes
373. ssing a payment or collection contract should be stored in the Learning Database Consequently while processing a transaction involving the product category the UDF values involved in the transaction will be saved in the learning database for the given Counterparty Bank and Account Number combination Clearing Tab Payments Product Category Maintenance E New amp enter Query Product Category Product Category Transfer Type Bank Transfer v Category Description f Product Type Collection Type Main Detail Clearing Fields Internal Clearing 10f1 E Product Sequence Number Account Description External Clearing 10f1 E Product Sequence Number Account Description m Offset Reject Recall Approval Redispatch Reverse Network Duplication UDF Details Rule Maker Date Time Mod No Checker Record Status Date Time Authorization Status You can specify the following details Specifying Internal Clearing details Product Specify the product details i ORACLE 3 26 3 2 3 26 4 Sequence Number Specify the sequence number Description The system will display the description for the selected product Specifying External Clearing details Product Specify the product details Sequence Number Specify the sequence number Description The system will display the description for the selected product Associating User Defined Fields with a Pro
374. stem For more information on TARGET 2 refer Maintaining Clearing Network details section Valid From Date Specify the date from which the clearing code is valid Valid Till Date Specify the date up to which the clearing code is valid Main Bank Identification Code Flag Main BIC Flag is used to resolve 8 characters BIC Check this option to indicate that the main BIC must be used if the bank code is incomplete Branch Code If the clearing bank being defined is a Oracle FLEXCUBE branch you can select the appropriate branch code from the option list available Every branch in Oracle FLEXCUBE is identified by a unique branch code A transaction routed through an internal branch will be processed as an Internal Book transfer SWIFT Address If the clearing bank is part of the SWIFT network you can select the corresponding SWIFT address from the available option list Customer You can indicate the customer CIF linked to the clearing bank code for which the bank directory details are being maintained For incoming messages in which the clearing bank code for which the CIF has been maintained is the counterparty bank code the CIF maintained here is used along with the product category of the incoming queue to which the message has been routed to determine the settlement account International Bank Account Mandatory You can indicate whether outgoing payments booked for the bank with clearing networks for which IBAN validations
375. stem displays the old and new values of the modified fields of the contract Change Log Contract Ref No Change Log 1 0f1 Description Event Sequence Number Old Value New Value The following details are displayed here e Contract Ref No e Description e Event Sequence Number e Old Value e New Value Status Details for Contracts Pending Authorization The status details for each contract are displayed in the Status Fields section e Contract Status e Collection Status a0 ORACLE 5 5 1 e Exception Queue e Message Status e ID of the user that entered the transaction with the date time stamp Rekey Fields for Contract Authorization If your bank has enforced re key of contract details during authorization the values to the re key fields will not be displayed You have to enter these values to authorize the contract If the re key values you enter do not match the contract you are calling for authorization an error message will be displayed If authorization is successful the next unauthorized contract in the batch will be displayed Overrides for Contracts Pending Authorization All override conditions that occurred at the time of contract input are also displayed for information in the Overrides section Click on the checkbox alongside the override field to confirm the override When confirmed the checkbox contains a tick mark Viewing contracts while authorizing them While in the P
376. stomer Details Customer Address Customer Information Clearing Branch Address Line 1 Customer Information 1 Account Branch Address Line 2 Customer Information 2 Customer Account Address Line 3 Customer Information 3 Currency 5 Address Line 4 Customer Information 4 j Address Line 5 Customer Reference Customer Account laz Customer Number Name Bank Code a Account Local Clearing Format Customer Id Details Id z Id Value Source Code zZ Bic ID Scheme Name Type RRN az Date of Birth El Scheme Name Value PB r Creditor City of Birth Issuer ERAEN Country of Birth fae Country et Fields Maker Date Time Mod No Checker Date Time Record Status Authorization Status In the Periodic Instruction Maintenance screen you can capture the following details for periodic payment or collection transactions Product Category View the product category that would be used to pick up default information for the periodic outgoing payment or collection The product to be used for the transaction will be picked up from this information You can only indicate an outgoing product category Instruction Reference umber This is the system assigned reference number of the periodic instruction Product Code It is not mandatory that you indicate the outgoing payment or collection product to be used for the periodic outgoing transaction since the system picks up this information from the outgoing product category specified However you can specif
377. stomer Name Account Branch Redirected Branch Code Customer Ac Ccy Redirected Currency Fields Maker Date Time Checker Date Time Mod No Record Status Authorization Status In this screen you can specify From Select the account number for which you are maintaining redirection details The following are displayed e The branch code of the selected account number e The currency of the account number e The customer name who is holding the account To Select the account to which transactions should be redirected On selection of the account number from the option lists available the following details get displayed 12 ORACLE 3 11 e The branch code of the selected account number e The currency of the account holder e The customer name who is holding the account All transactions involving the account for which you are maintaining redirection details will be automatically redirected to the account that you specify here Maintaining Beneficiary Accounts for Counterparty Bank You can maintain a list of beneficiary accounts for a counter party bank for local payments and collections transactions through the Beneficiary Maintenance screen You can invoke this screen by typing PCDBENMT in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Beneficiary Maintenance ounterparty Account Bank Code Account Number Bank Name ounterparty Det
378. such charges oe ORACLE Maintaining Products You may process transactions which involve transfer of funds between accounts maintained at your bank You can define this type of local payment as a product in the P amp C module You can define products for each type of DD and RFD transactions mentioned earlier The advantages of defining a product Let us consider the steps involved in processing an outgoing payment instruction involving a foreign currency account at your bank Your specifications would include the following e The type of payment being made that is outgoing in this case e The Clearing Mode e The Clearing Network e The Exchange Rate applicable e The Customer Entry days e The Customer Entry Value days e The Counterparty Entry days e The GLs to which the accounting entries should be posted e The advices that should be generated If you process a thousand such outgoing payments you would need to repeat these operations as many times By defining outgoing payments involving an incoming or outgoing collection as a product in Oracle FLEXCUBE and defining standard attributes for it you can make the task of processing such payments easier You can define the following broad parameters for a product e Product Preferences e Events and Accounting Entry Definition e Advices to be generated for the various events e MIS Definition Product Categories Once you have created a product you can associate
379. system will remove the contract row from the tracking table and the customer s FATCA balance will be updated accordingly if required 5 39 ORACLE 5 3 Viewing Payments and Collection Transactions You can view the Payments and Collection Transactions using Payments and Collection Transactions Summary screen To invoke this screen type PCSTRONL in the field at the top right corner of the Application tool bar and click the adjoining arrow button Transaction Summary iS E gt Search Ct Advanced Search 9 Reset Clear All Case Sensitive Contract Reference FS Branch Code esl Source Code fae Source Reference azl Their Reference fae Custom Reference az Network fae Batch Number Product Category az Product Code P Priority az Customer Number az Records per page 15 7 10f1 Contract Reference Branch Code Source Code Source Reference Their Reference Custom Reference Network You can click Search button to view all the pending functions However you can to filter your search based on any of the following criteria e Contract Reference e Source Code e Their Reference e Network e Product Category e Priority e Branch Code e Source Reference e Custom Reference e Batch Number e Product Code e Customer Number Click Search the system displays the following details based on the specified search criteria e Contract reference e Branch Code e Source Code oH ORACLE Source
380. t Processing Payment Cancellation Request The Payment Collection Cancellation Request Camt 056 001 01 message is sent by a Case Creator Case Assigner to a Case Assignee This message is used to request the cancellation of an original payment instruction The Payment Cancellation Request message is exchanged between the instructing agents The instructing agent requests the cancellation of an interbank payment message previously sent such as FIToFlCustomerCreditTransfer FIToFIlCustomerDirectDebit or FinanciallnstitutionCreditTransfer The negative answer to the Payment Cancellation message is Camt 029 message Note For Recalling the Outgoing Collection and for Recalling of Credit Transfer the system uses the Camt 056 message ae ORACLE 5 24 1 The Camt 029 is resolution of investigation message which is used to answer the Camt 056 Recalling Credit Transfer Camt 056 001 01 Oracle FLEXCUBE provides a facility to identify the contracts which needs to be re called for which pacs 003 01 02 or pacs 008 01 02 message already sent The system generates the Camt 056 message and sends it to the assignee to cancel the already sent message The Camt 056 message caters for single or group cancellation requests You can mark the list of contracts for which Camt 056 needs to be generated through Payments and Collections Cancellation screen You can invoke this screen by typing PCDRCLIN in the field at the
381. t Print Printer Branch Code You can generate this report for all the branches or a single branch alone You can indicate the branch for which the report is being generated using the following options e All If you choose this the system will generate the report for all the branches e Single If you choose this you need to specify the branch code for which the report should be generated The option list displays all valid branch codes maintained in the system Choose the appropriate one 10 2 ORACLE Report Date Specify the date of report from the adjoining calendar Contents of the Report The parameters specified while generating the report are printed at the beginning of the report Other content displayed in the report is as follows Header The following details are displayed in the header section Field Name Field Description Report Name Indicates Report Name Branch Code Branch Name Indicates Current Branch code and Branch Name User ID Indicates the Identification of the User Module Indicates the Module of the Report Report Run Date Indicates Current Branch Date Report Run Time Indicates Current Branch Time Branch Date Indicates the date of Branch in which report is taken Page No Displays Page No out of total No of pages in report Body of the Report The following details are displayed as body of the generated report
382. t 056 which are rejected from Incoming Payment Cancellation Approval screen 394 ORACLE 5 25 6 5 25 7 Processing Incoming Camt 029 001 03 The receiver bank sends resolution of investigation message to notify the sender that the cancellation request has been rejected On receipt of the Incoming Camt 029 message system reads the message and updates the original Camt 056 message status as Rejected Maintaining Parameters for SEPA Transactions The following maintenances need to be done for the SEPA transactions to be carried out Product and Product Category To handle SEPA transactions the following product types and product categories are maintained e Outgoing payment e Incoming Payments e Reject of Incoming payment e Reject of Outgoing payment e Outgoing Collections e Incoming Collections e Reject of Outgoing Collections e Reject of Incoming Collections e Recall of Outgoing Collections e Recall of Incoming Collections e Reverse of Outgoing Collection e Reverse of Incoming Collection For more details refer section Maintaining Product Categories in the chapter Maintaining Information specific to the Payments and Collections Module of this User Manual Clearing Network To include the ISO codes in the outgoing XML messages for SEPA transactions the ISO clearing system identification codes for clearing networks are maintained in the Clearing network maintenance screen For more details re
383. t N Contract Reference re Recall Reference Number 1 Of 1 F Check In Msg Reference Number Related Reference Number Cancellation Originator Name Cancellation Originator Bar Maker Date Time Mod No Checker Date Time Record Status Authorization Status You need to capture the following details here Original Message Reference Number Select the Original Message Reference Number from the adjoining option list Contract Reference Number Select the Contract Reference Number from the adjoining option list Recall Reference Number System defaults the unique sequence number Related Reference Number Select the Related Reference Number from the adjoining option list Account Number Select the Account Number from the adjoining option list Click on Search button to fetch the matching incoming messages based on the search criteria Incoming Cancellation Request You can accept or reject the process of incoming cancellation request through Incoming Payment Cancellation Approval screen The options for rejecting cancellation for incoming payment are 51 Insufficient balance 53 Customer specific order to not attend the request oad ORACLE 54 Charged account can celled or audited or confiscated 55 Public restrained account 61 Absence of beneficiary authorization 62 Already cancelled 65 Non existent or wrong data The option for accepting cance
384. t credited into compensation suspense account and charge suspense account respectively with value date as the date on which refund is initiated CSM Processing Once CSM receives the Refund instructions with compensation amount and charges amount it will debit the creditor bank with Returned Interbank settlement amount and credit debtor bank with Returned Interbank settlement amount Returned Interbank settlement amount comprises of Original Interbank Settlement Amount Compensation Amount Charge Amount Credit Bank Processing Debiting the creditor with back value dated will be achieved by configuring Original Transaction Value Date parameter at product level Creditor bank on receipt of Refund instructions will debit the creditor for the original collection transaction amount and debits compensation suspense account for the compensation amount and debits charge suspense account for charges amount The original collection transaction amount compensation amount charge amount will get credited in to CSM Maintaining Dispatch File Parameters You can maintain the details of the dispatch file to be generated using the Dispatch File Parameters screen You can invoke this screen by typing PCDSFPRW in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Dispatch File Parameters A Save Network Code az Bank Code Dispa
385. t identification details It is mandatory to check this box to process mandate updates validations Cut Off Time Hour Minutes You can indicate the cut off time in hr and min for the customer and product combination involved in the agreement The cut off time specified here takes precedence over the one specified at the product level During product resolution based on the cut off time maintained the system will determine whether the transaction is received before the cut off time For transactions received after the cut off time the system will resolve the product for which post cut off is allowed The activation date the current system date of such transactions will be moved to the next day Transactions with activation dates in the past or future will be resolved as received before the cut off time pre cut off oe ORACLE Customer Days Entry Days For the transactions processed under a specific product involving a specific customer you can specify the manner in which the booking date of the transaction should be arrived at Your specification in the Customer Entry Days field will be added to the activation date to arrive at the Customer Entry Date for transactions received before the cutoff time specified for the product Entry Value Days For the transactions processed under a specific product involving a specific customer you can specify the manner in which the value date of the accounting entries for custo
386. t that you wish to use to process the contract Based on the product code the system will default the currency code linked to this product in the Txn CCY field Alternately the system can also arrive at the product code based on the currency specified in the Txn CCY field a ORACLE 5 2 2 Network Specify the clearing network for the contract Based on the network ID the system will default the currency code linked to this network in the Txn CCY field Collection Type The Collection Type of the transaction will be displayed This could be either DD or RFD RFD Type If the incoming collection transaction is an RFD specify the RFD type This could be any one of the following e No Tracking indicates that the RFD is not considered for approval or rejection e Full Payment indicates that the RFD is processed for payment of full transaction amount Partial Payment indicates that the RFD is processed for partial payment Contract Reference The system identifies every transaction with a unique reference number You can view the reference number for the transaction that you are capturing Customer Reference The custom reference number for the contract is displayed Product Type It defines the product and the product category of collection payment In PC transaction input it will be defaulted from the Product Category Source Reference The system identifies every transaction with a unique source referen
387. t the processing cycle of the transaction has been completed e Reversed This status indicates that the transaction has been reversed in the system e Split Master This status applicable only for outgoing collection transactions indicates that the transaction has been split into multiple contracts because the transaction amount has exceeded the maximum possible transaction amount The system does not allow any operations on such split transactions e Partial This status only applicable for outgoing request for debit transactions indicates that the collection transaction has only been settled partially e Deleted This status indicates that the transaction is marked for deletion No further operations are possible on deleted transactions Specifying Exchange Rate for a Transaction If payment transactions involve a customer account maintained in a foreign currency the exchange rate to be used is either picked up automatically based on the product specifications or manually entered In the Exchange Rate screen invoked from the Application Browser you can specify the exchange rate for contracts involving customer accounts maintained in a foreign currency When you invoke the Exchange Rate Input screen from the Application Browser all details of the contract are displayed However you can only enter a value in the Exchange Rate field If the rate you input exceeds the override variance limit defined for the product
388. tatus 7 Record Status x Recall Ref No Contract Reference A Recall Reason Recall Status x Account Number ka Party Account Number Records per page 15 x 10f1 Authorization Status Record Status Recall Ref No Contract Reference Service Type Recall Reason Recall Status In this screen you can query based on any combination of the following fields e Authorization Status e Recall Ref No e Recall Reason e Account Number e Record Status e Contract Ref no e Recall Status e Cpty Account Number After specifying the parameters for the query click Search The system displays all the records matching the parameters specified 5 25 Processing Incoming Camt 056 Messages On receipt of incoming Camt 056 system identifies matching Pacs 008 Pacs 003 based on the Original Message ID and Original transaction ID provided in the incoming Camt 056 If no matching contract found system updates the Camt 056 message status as Repair Oracle FLEXCUBE provides a facility to approve reject the incoming Camt 056 for Incoming payment messages through Incoming Payment Cancellation Approval screen You can ale ORACLE invoke this screen by typing PCDRCLOT in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Incoming Payments and Collections Cancel Approval E New E gt Enter Query Original Msg Reference Related Reference Number Nu mber Accoun
389. tch Browser ae a AE eat Reds tae eased eet eee 5 63 84 5 22 Updating Cut Off Time Status occ eeeeenneeeeeeeaeeeeeeeeaeeeeeeeiaaeeeeeeenaaes 5 64 5 23 Handling SEPA Credit Transfers and Direct Debits 2 0 0 ee ceeeeeeeeeteeeeeeenteeees 5 64 5 24 Processing Payment Cancellation Request 00 ecccceeceeeceeeeeeeeneeeeeeeennaeeeeeeenaees 5 68 5 24 1 Recalling Credit Transfer Camt 056 001 01 ciseccceectseeeeeeeeetstteeeeteeee 5 69 5 24 2 Viewing SEPA Payment Cancellation Summary Details 9 75 5 25 Processing Incoming Camt 056 Messages 0 eceeeceeeeeesneeeeeeeeeneeeeeeeeneeeeeeenaaees 5 76 5 25 1 Handling of Camt 056 for Incoming payments in Transaction Repair queue 5 80 9 25 2 Handling of Camt 056 for Incoming Collections in Transaction Repair queue 5 81 9 25 3 Handling Conflict SC NAVIOS sereisererir eirin iaasa ttnteee eee taeeeeeetiaaeeeeeetaae 5 81 5 25 4 Viewing SEPA Payment Cancellation Approval Summary Details 5 83 5 25 5 Processing Negative Answer to Recall of a Credit Transfer Camt 029 001 03 5 5 25 6 Processing Incoming Camt 029 001 03 cecccccceeseeeeeeetteneeeeeetneeeeeenaee 5 85 5 25 7 Maintaining Parameters for SEPA Transactions ccccccceeeeeeetteeeeeeeee 5 85 Ter PrOCceSS FIOWs i E iran E eae O EOE T 5 88 5 25 9 Validations done on the SCT and SDD MeSSaG S 0 0 0 sceeeectttte cette 5 89 5 25 10 Refund Compensation and Balancing Payment for Debtor Bank 5 89 5 25 11 Mai
390. tch Type T Customer Account Service Identification X Maium Tracers Files Message Bulks No Of Transactions In Bulk Test Mode me E Bulk Message File Format Type x E File Per Transaction Type File Path Maker Checker Mod No Date Time Date Time Record Status Authorization Status The following details are captured here Dispatch Type Select the type of the dispatch from the drop down list The following options are available in the drop down list a0 ORACLE e Network If you select the dispatch type as network then clearing network code is mandatory and bank code and customer number will be defaulted value ALL e Bank If you select dispatch type as bank code then bank code is mandatory and clearing network and customer number will be defaulted value ALL e Customer If you select dispatch type as customer then Customer number is mandatory and clearing network and bank code will be defaulted value ALL There will be a provision to select ALL to generate XML files for all customers This is a mandatory field Network Code Select the clearing network for which the dispatch file parameters are maintained from the adjoining option list The list displays all valid clearing network maintained in the system This is a mandatory field Service Identifier Select the service type as of the clearing network from the drop down list The
391. te one Report Date Specify the date of report from the adjoining calendar Contents of the Report The parameters specified while generating the report are printed at the beginning of the report Other content displayed in the report is as follows Header The following details are displayed in the header section Field Name Field Description Report Name Indicates Report Name Branch Code Branch Name Indicates Current Branch code and Branch Name User ID Indicates the Identification of the User Module Indicates the Module of the Report Report Run Date Indicates Current Branch Date Report Run Time Indicates Current Branch Time 194 ORACLE Branch Date Indicates the date of Branch in which report is taken Page No Displays Page No out of total No of pages in report Body of the Report The following details are displayed as body of the generated report Field Name Field Description Branch Indicates the current branch code Employer Indicates the name of the employer Employee Indicates the employee name Employee Account Indicates the employee account Salary Date Indicates the date of the salary Salary Amount Indicates the salary account Transaction Reference Number Indicates the transaction reference number Bank Code Indicates the bank code Error Description Indicates the error description 10 2
392. tem defaults the following e In Msg Reference Number e Related Reference Number ag ORACLE Account No Counterparty Account Number Product Code Customer Account Branch Customer Account Currency Customer No Counterparty Bank Code Transaction Amount Transaction Currency Recall Reference Number Contract Reference Direction Recall Status Dispatch Reference Number Dispatch File Name Out File Reference Number Out Msg Reference Number Out Msg Name Out Msg Creation Date CSM Reject Reference No CSM Reject Code CSM Reject Detail Step 2 Reject Reference Step 2 Reject Code Process Status Error Code Original Recall Reason The value for the field is defaulted from the CPG upload data store Cancellation requests can be approved or Rejected based on the reasons defined in the field Original Additional Recall Reason The value for the field is defaulted from the CPG upload data store Cancellation requests can be approved or Rejected based on the reasons defined in the field Original Additional Recall Information The value for the field is defaulted from the CPG upload data store Cancellation requests can be approved or Rejected based on the reasons defined in the field Cancellation Originator Name Specify the value for the field which is of length 70 characters Note The name is viewed in the following messages Customer and FI Payment Cancellation Camt 056 001 01 Fl to Fl Negative answer to Pa
393. teria Double clicking on any of the records the system will display the record details Clicking on Reject button you can reject the contract s For this action the system will generate the return of incoming payment messages N07 for NEFT and R41 for RTGS customer transfer and R42 for RTGS Bank transfer Bulk operation is not allowed for this Clicking on Details button the system will display the details of the selected contract ante ORACLE Clicking on Repair button the Repair window is displayed as follows E New E3 enter query Contract Reference Customer Reference Product Code Product Type Product Category Transaction Amount Network Existing Details New Details Beneficiary Account New Account Number Number Beneficiary Name Maker ID Checker Id Record Status Maker Date Stamp Checker Stamp Mod Number Contract Reference Number Specify the contract reference number Beneficiary Account Number Specify the customer account number Beneficiary Name The system displays the beneficiary name New A C No Specify the new account number The above screen will display the following details of the selected contract e Customer Reference Number e Product Category e Product Type e Product Code e Transaction Amount e Network You can unlock the contract and capture the reject code aa ORACLE The Reject PCDIAUTC screen will reject the selected
394. the beneficiary bank in the external system This notification displays the contract details The system creates a database trigger to initiate based on the contract status of the payment This displays the transaction data in the notification data store The existing notification job considers this notification also to notify about the rejection of transactions Note While generating account statement the beneficiary account number will not be displayed for all the P2P payments During the account statement data assignment for all Customer Debit and P2P Final Payment transactions beneficiary account number will be replaced by the following P2P Payment to lt Email ID gt P2P Payment to lt Contact Number gt P2P Payment to lt Facebook ID gt The EOD PC batch process marks all the customer debit payments and amount block requests for which beneficiary is not registered as Expired on the end date of beneficiary registration Notifying Rejected Status of Payment Request You can view the notification for Rejected status through the external system For a payments and collections transactions the system will generate the reject notification based on the final outcome of the contract processing If payment gets into the exception queue then the notification will be generated once the status of the contract changes to reject If a contract is rejected then a notification with rejected status is sent ee
395. thin a single set Note that you should use single quotation marks while defining the value of the condition For example IF value is 0 The charges defined for a product are automatically applied on all transactions processed under the product The charges applied on transactions are liquidated according to the frequency specified for the Charge Class Specifying Charge Components After you have built the conditions based on which the charges will be levied you must also indicate during product definition the accounting roles and amount tags to be used to pass the requisite accounting entries for charges To recall charges levied on payments and collection transactions are computed at the time of transaction initiation and are liquidated along with the contract The amount tags available for charges on payments and collection transactions are the CHG_AMT tags which must be mapped to the CRLQ and DRLQ events depending upon which of these is the event for the customer leg of the transaction during product definition For details about associating accounting roles and amount tags and accounting entries for events during product definition refer the chapter Defining a Product in this user manual Specifying Charges Charges on a payments collection contract are computed based on the condition sets maintained in the Product Conditions Maintenance screen for the product that the contract uses Click Charges
396. through PC Maintaining Local Clearing Details and Cover Details for Customer Set tlement Instructions When you specify settlement instructions for a customer you can indicate whether payment for local currency transactions is to be effected via messaging or over the local clearing network You can also indicate whether a cover is required for payment and whether the cover is through messaging or over the local clearing network You can specify these details in the Settlement Instructions screen You can invoke this screen by typing ISDINSTN in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button In the Payment By field indicate the mode of payment either Message or Local Clearing and in the Cover By field indicate the mode through which cover must be available A ORACLE The screen is as below H sav Counterparty bal Module a Counterparty Name Product Code fae Counterparty CIF x Sequence Number 0 Currency GBP Relations Branch 000 bel Pay Receive F Cover Required Branch zi PR Branch 000 asl Cover By Currency GBP baal Currency GBP al Charges Details Ourselves Account Account asl Beneficiary Description Description Shared Payment By v Payment By v a Pay Parties Receiver Parties Cover Parties Clear Details Cover Detais Other
397. tion gt ited Level 2 Author ization gt Release gt Net work Initiation gt Amount will be Amount Block Not applicable Not applicable Level i Auth r blocked on is removed on SP account account ization 1 Reject Initiation gt Amount will be No action Amount Block is Not applicable blocked on removed on Level 1 Author ee account account ization gt Level 2 Author ization Reject 4 38 ORACLE 4 7 1 Initiation gt Amount will be Amount Block Not applicable Account debit blocked on is removed is reversed Level 1 Author ae account and ization gt Account is R debited Initiation gt Amount will be No action Amount Block is Account debit blocked on removed and is reversed Level 1 Author a account Account is deb ization gt ited Level 2 Author ization gt Release Rejec t Initiation gt Account is deb Not applicable Not applicable No action ited Release gt Network Initiation gt Account is deb Not applicable Not applicable Account debit ited is reversed Release Rejec t Window Periods for Outgoing Payments A Window Period is a time interval during which the operations of Initiation Level 1 Authorization Level 2 Authorization and Release of payment transactions are allowed Window periods are applicable for Outgoing Payments only The respective operations will not be allowed at ti
398. tion Limits screen You can use the Multilevel Authorization Detailed screen for authoring a contract n 1 times However final authorization can take place only in the contract screen For more details refer the Multilevel Authorization of Contract Loan Account section in the Procedures User Manual Operations on Collection Transaction The operations that you can perform on a collection transaction in the PC Transaction Input screen depend upon whether it is authorized If the transaction is unauthorized you can Put the transaction on hold if any of the details are incomplete The system performs no further processing on such transactions unless they are subsequently amended and saved again Amend the details of the transaction if necessary If a contract has been uploaded through the upload facility you can amend only those details that have been allowed for amend in the product category and the upload source preferences Delete the transaction Again in the case of contracts uploaded using the upload facility deletion is possible only if allowed in the upload source preferences for the source from which the contract was uploaded You can perform any of the following operations as required on an authorized collection transaction Redispatch an outgoing transaction that needs to be manually redispatched Click roll over icon in the toolbar to redispatch the transaction manually Only collection
399. tion transaction here The field is optional Charge Reference Number Specify the charge reference number in this field Transaction Type Select the debit transaction type from the drop down list The options are e One off e Recurrent aao ORACLE Validity Details Expiry Date Specify the end date for a particular Creditor DD agreement here On the maintained date agreement status will get updated as Expired as part of the existing batch process Agreement Status Specify the value for the field The value determines the status of the mandate at any point of time Options available for this field e Active The agreement is available for usage e Used One Off transaction sent e Auto Cancelled Agreement auto cancelled because of non usage for specified period e Final FRST RCUR and FNAL transactions sent e Customer Cancelled Agreement closed by Creditor e Expired Agreement has crossed expiry date e Amended Unique identification of an agreement changes Agreements with agreement status as Active and record status as Open is considered as valid agreement Modify operation changes the agreement status from Active to Customer Cancelled when creditor is initiating the closure of agreement Agreements with status as Used Auto Cancelled Final Expired Amended cannot be changed back to Active There are validations to restrict this status change Used Auto Cancelled Final Expired Amen
400. tion will be processed Account No Specify the account number of the default customer account The currency and the branch is displayed Automatic User Ref No Generation Auto Custom Ref No You can specify whether custom reference numbers must be automatically generated for payments or collection contracts using the product Custom Ref Seq Code You can specify the custom code to be used for sequential reference number generation The format specified for the selected sequence code in the Sequence Generation maintenance in the Branch Parameters is used to generate the custom reference numbers For details about the Sequence Generation screen refer to the Core Services User Manual Re Key Required You can specify the values of a contract that have to be rekeyed when authorizing it All operations on a contract have to be authorized as follows e By a user other than the one who carried out the operation e Before you can begin the End of Day operations As a cross checking mechanism to ensure that you are invoking the right contract for authorization you can specify that the values of certain fields should be entered before the other details are displayed The complete details of the contract will be displayed only after the values to these fields are entered This is called the re key option The fields for which the values have to be given are called the re key fields If no re key fields have been defined the details
401. tlement It can either be Pay or Receive If you select the Pay option a list of all Outgoing Payment categories will be displayed in the option list Similarly settlement will be restricted to Outgoing Collections if the process direction is Receive Transfer Type You can also specify the Transfer type which enables the System to distinguish whether the payment is a Customer Transfer or a Bank Transfer You can choose to maintain different Payment product categories for different types of payments In case of bank transfer select a Bank Transfer type of PC product category Similarly for customer transfer select Customer Transfer type of product category For the Receive Leg the Customer Transfer option is defaulted in the Transfer Type field and disabled Oracle FLEXCUBE allows you to route MT 400 messages from the Bills and Collections BC module through the PC module A separate Transfer Type called Collection Payment Advice is available for the purpose This is only applicable for the BC module when the settlement direction is Pay The PC Product Categories available for mapping in such a case will be Bank Transfer Type of Products You can specify the following details as part of the mapping for each module product process direction payments product category source code and station ID combination e Any or all settlement related fields defined for the payments product category e Any or all user defined fields defined for the Pay
402. tor Bank When CSM processes Pacs 002 for Outgoing Collection Creditor Bank processes the incoming Pacs 002 and cancellation request is rejected The cancellation request Camt 056 for Outgoing Collection is rejected manually in Payments and Collections Cancellation PCDRCLIN screen or on receipt of Pacs 002 for Camt 056 from CSM This rejection process would re activate the original Outgoing Collection with the contract details as prior to the cancellation An event RACT will be logged for the original Outgoing Collection in the contract events data store Now pre settlement rejection Pacs 002 on Outgoing Collection is processed Case 5 Receipt of Pacs 007 from Creditor Bank for Incoming Collections for which Pacs 004 Recall is already sent by Debtor Bank When CSM processes Pacs 007 for Incoming Collection Debtor Bank processes the incoming Pacs 007 When the original Incoming Collection contract is not active reversal processing on original Incoming Collection fails and the reversal transaction gets logged into TR queue a2 ORACLE e In order to respond to received Pacs 007 message Recall of Incoming Collection is rejected either manually in Payments and Collections Transaction Input PCDONONL screen by the reject operation available or on receipt of Pacs 002 for Pacs 004 from CSM e This rejection process would re activate the original Incoming Collection with the contract details as prior to the
403. tor Name 8 Effective Date Processing date 9 Amendment Reason Internal values explained below A ORACLE SI No Field in PC Debtor DD Value Agreement 10 Mandate Status Internal values explained below The mandate is inserted whenever the sequence type is FRST OOFF and is updated if the sequence type is RCUR if required For sequence type FNAL the Mandate Status is updated to Final For more details of processing of sequence types refer section Processing Based on Sequence Type explained later in this chapter Note Before performing insert update of the mandate details based on the sequence type of the message system performs validations to check if the mandate exists During processing of Incoming Collection contracts there could be updates to the mandate details Based on the sequence type of the mandate present in the Incoming Collection the updates can either be update of the existing mandate details or insertion of mandate details The different types of transactions for which the mandates are validated and the mandate details are inserted updated in the Payments amp Collections Debtor DD Agreement Maintenance screen are given below Transaction eg Insert SI No Type Validation Update 1 Incoming Yes Yes Collection 2 Outgoing No No Collection 3 Reject of No No Incoming Collection 4 Reject of No No Outgoing Collection
404. tor and the debtor participating in a transaction Creditor Reference Code Specify creditor s reference code here the field is optional The maximum length of the value in the field is 35 characters aag ORACLE Counterparty Details Couterparty Account Number Specify the counterparty account number Counterparty Bank Code Select the counterparty bank code from the adjoining option list Bank Name Specify the name of the bank Date of Signature Specify the date of signature from the adjoining calendar Counterparty Name Specify the counterparty name Address 1 2 3 and 4 Specify the complete address of the counterparty Country Specify the country from the adjoining option list Transaction Details Agreement Cancellation Charge To indicate applicability of charges or fees levied on setting up and or amending direct debit creditor or debtor agreements you can enable the Charges Applicable option in the PC Creditor Agreements screen The applicable charges are computed through the Interest and Charges IC module For details refer the Interest and Charges module user manual The preferences for product debtor categories are discussed in a later section of this chapter Payment Details 1 Payment Details 2 Payment Details 3 and Payment Details 4 Specify unstructured remittance information The fields hold free format text of 35 characters each Purpose of Collection Specify the need of the collec
405. transactions can be redispatched Approve a transaction in the case of active incoming RFD collection transactions Click liquidate icon in the toolbar to approve a transaction Close an outstanding collection transaction Click close button to close the transaction Recall an incoming direct debit transaction Click Re open to recall the transaction The Recall Contract Details screen is opened where you must specify the Activation Date for the recall and the interest amount applicable You must also indicate whether the recall must be dispatched Reject a transaction In the case of incoming DD and RFD contracts the system marks the parent contracts are rejected and automatically generates new transactions Click re open to reject such transactions The Reject Contract Details screen is opened You must specify the Activation Date for the rejection and indicate whether the reject must San ORACLE 5 8 1 5 8 2 be dispatched You must also specify the reason for rejection by selecting the appropriate reject code In the case of Outgoing DD and RFD contracts before the settlement date contract can be rejected the system marks the contract as rejected Click re open to reject such transactions The Reject Contract Details screen is opened You must specify the Activation Date for the rejection and indicate whether the reject must be dispatched You must also specify the reason for rejection by selecting the app
406. try date is prior to or is the current system date e The DRLQ event has been processed successfully Entries posted for Outgoing transfers will be as follows Accounting Role Dr Cr Indicator Internal Suspense Payable Debit Clearing Suspense Payable or Clearing Vostro Credit Entries posted for Incoming transfers will be as follows Accounting Role Dr Cr Indicator Internal Suspense Receivable Debit Customer Account Credit Entries posted for Debit Notification will be as follows Accounting Role Dr Cr Indicator Intermediary GL Debit Network GL NOSTRO Credit Entries posted for Credit Notification will be as follows Accounting Role Dr Cr Indicator Intermediary GL Debit Interbank Receipt GL Credit If the contract is moved to release queue for CRLQ event then the following account entries are passed Event Account Debit Credit Amount CRLQ_ Intermediary GL Debit Transaction Amount CRLQ_ Outgoing Network GL NOSTRO Credit Transaction Amount 78 ORACLE If the incoming payment or return of outgoing payment is suspended from the incoming authorization queue then system will process the CRLQ event with following accounting entries Event Account Debit Credit Amount CRLQ Intermediary GL Debit Transaction Amount CRLQ Unsettle GL will be picked up Credit Transaction
407. twork Qualifier Maintenance screen you can maintain the network qualifiers You can invoke this screen by typing PCDCLNTQ in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Clearing Networks Qualifier Maintenance E New E3 Enter Query Clearing Networks Qualifier Network Qualifier Description ELCs Date Time Checker Date Time Mod No Record Status Authorization Status Network Qualifier Specify the network qualifier details For BI SKN network specify the network qualifier as S and for BI RTGS network specify the network qualifier as T Description Specify the network qualifier description Network Qualifiers will be factory shipped as follows Network Qualifier Description T TARGET 2 O Others R RTGS INR N NEFT 3 7 Maintaining Network Calendar In the Network Holiday Maintenance screen you can maintain the working days half working days and holidays for the year and network You can invoke this screen by typing oie ORACLE 3 8 PCDNWHOL in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Network Holiday Maintenance S M T February March August September November December Network Code 1 0f1 ELS Date Time Mod No Checker Record Status Date Time Authorization Status Network Code Specify the network code
408. u enter details for a transaction as given below All validations to values entered in fields are made just as they are in the PC Transaction Input screen Refer PC Transaction Input screen details in the same manual Basic Details e Product Code you can only select those products that are linked to Outgoing Incoming Payment Direct Debit or Requests for Debit product categories e Network 5 4 0 1 Specifying Clearing Network Restriction Bank Code lists linked to the available clearing networks are displayed in PC Fast Input screen for the Product Category The displayed bank codes list sequence is driven by the way you navigate through the PC Fast Input screen After entering the product category details if you proceed to the bank code without entering the product code and network the functionality will remain as before The entire list of bank codes used by that product is displayed If you enter the product code after entering the product category details then e If the Product is Book Transfer Type the network field would be blank The Book Transfer Type of Bank Codes from the PC Bank Directory will be displayed in the list of Bank Codes from the PC Bank Directory e If the specified Product is internal type the network field would be blank The entire list of bank codes used by that Product would be displayed e If the product is of the type external the default network chosen in the product preferen
409. ult activation date can be either today s date or the next working day Default Activation Date Select the default activation date as Today etc from the option list provided Move Back Dated Activation Date You can indicate that the activation date if in the past is to be moved forward to the default activation date by enabling this option If you enable this option you have to indicate the Default Activation Date as well The default activation date can be either today s date or the next working day If at the time of booking a transaction involving the product if you have failed to specify the transaction date the default date that you specify in this field will be picked up Exchange Rate You can indicate exchange rate details as part of the preferences you define for a product The exchange rate parameters you define for a product will be used when payments involve foreign currency accounts Specify the Exchange Rate Code Standard TC Cash etc and Exchange Rate Type Mid Buy or Sell that should be picked up for transactions processed under the product The rate corresponding to the Rate Code and Rate Type you specify will be applied on all transactions involving the product ae ORACLE Auto Exchange Rate During transaction processing if you like to automatically apply the exchange rate that corresponds to the Rate Code and Rate Type specified for the product choose the Automatic Exchange Rate option This s
410. unter parties involved with the specific customer of the contract are displayed in the learning database You can select the Counter party Bank Code Counter party Account Number and Name of the required counter party Bank code Select a valid bank code maintained in Oracle FLEXCUBE If you select a code from the option list the bank name is displayed instantly If you choose to enter the code the name of the bank is displayed when you save the transaction Validations for counterparty details for bank transfers sp ORACLE e For bank to bank transfers it is not mandatory to specify the counterparty account and name If you indicate only the counterparty bank code it is considered as a beneficiary institution If you indicate both the Counterparty Bank Code and Counterparty Name the Counterparty Bank Code is interpreted as the Account With Institution and the Counterparty Name is interpreted as Beneficiary Institution e f both the Counterparty Bank Code and Counterparty Name are specified for bank to bank transfers the system validates the Counterparty name with that maintained in the PC Bank Directory The System also checks to ensure that both the Counterparty Bank Code and Counterparty Name have been defined with the same Bank Code Type Bank Name Specify the counterparty bank name Bank Address 1 Specify the address of the counterparty bank Bank Address 2 Specify the address of the counterparty bank Virtual Accou
411. vate Identification City of Birth Specify the city of birth of the customer This is enabled and is mandatory if you have selected identification type as Date and Place of birth Customer Country of Birth Select the country of birth of the customer from the option list This is enabled and is mandatory if you have selected the identification type as Date and place of birth Country Specify the country of residence of the customer This adjoining option list displays all valid country codes maintained in the system You can choose the appropriate one Note The country information is captured to enable Mantas to analyse the transactions for pos sible money laundering activities Oracle FLEXCUBE supports 24x7 functionality for PC periodic instruction For more details on Mantas refer Mantas interface document Counterparty Tab The counterparty details are defaulted on selection of counterparty account number if the counterparty identification details are maintained in PC Beneficiary Maintenance screen Identification Select the option to identify the counterparty either by Organization details or by Individual person details The options available in the drop down list are Organization Identification and Private Identification oe ORACLE Identification Value Specify the identification value for the counterparty for the given identification type This is mandatory only if the Identification type is sp
412. versal of payments for Customer Debit payments Notifying KYC Status of P2P Beneficiary You can view the KYC status of the P2P beneficiary through the external system The system notifies the KYC status of the P2P Beneficiary as Verified or Verification Failure You can view the following in the notification screen e Beneficiary Email ID e Beneficiary Telephone e Beneficiary Facebook ID s9 ORACLE 8 8 8 9 8 10 e Beneficiary Bank Code e Beneficiary Account Number e KYC Status The system creates a database trigger to initiate the notification task based on the KYC status of the P2P beneficiary This displays the data in the notification data store The existing notification job considers this notification also to notify about KYC status Notifying Successful P2P Final Payment You can view the notification for the successful P2P final payment in the external system The system notifies the liquidated status of the P2P final payment This notification displays the entire contract details The system creates a database trigger to initiate based on the contract status of the payment This displays the transaction data in the notification data store The existing notification job considers this notification also to notify about the liquidation of contracts Notifying Rejected Test Transaction and P2P Final Payment You can view the notification for rejected test transaction and P2P final payment from
413. y You can view the history of agreement records pertaining to particular Debtor using Debtor Direct Debit Agreement History Summary screen You can invoke this screen by typing a ORACLE PCSDRAHS in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Debtor Direct Debit AgreementHistory Summary E gt search Ct Advanced Search 9 Reset Y Clear All Case Sensitive Authorization Status O gH Branch Agreement Id Product Code Records per page 15 x 10f1 Authorization Status Record Status Branch Debtor Account Creditor ID Scheme ID Agreementid Creditor Name You can query based on any or all of the folowing criteria Authorization Status Record Status Branch Debtor Account Agreement ID Creditor Name Product Code Customer Click Search The system displays the following values Authorization Status Record Status Branch Debtor Account Key Details Creditor ID Schema ID Agreement ID Creditor Name Product Code Customer IOR ORACLE e Version Number The system displays the records in descending order of the version number 3 43 Retrieving Debtor Direct Debit Instructions History Oracle FLEXCUBE facilitates retrieval of the history of instruction records pertaining to particular Debtor and Debtor Account combination using Debtor Direct Debit Instructions History screen You can invoke this screen by typing PCDIDRHS
414. y Telephone Specify the telephone number of the counterparty Email Id The system defaults the email ID if an existing beneficiary is maintained in P2P Beneficiary Maintenance screen or new records of a new beneficiary is registered Facebook ID The system defaults the Facebook ID if an existing beneficiary is maintained in P2P Beneficiary Maintenance screen or new records of a new beneficiary is registered Remarks Specify the free hand text related information of the beneficiary Identification Details Identification Select the option to identify the counterparty either by Organization details or by Individual person details The options available in the drop down list are e Organization Identification e Private Identification BIC ID Specify the Bank Identification Code of the Counter Party Identification Value Specify the identification value for the Counterparty for the given identification type This is mandatory only if the Identification type is specified Issuer Specify the Identification Issuer of the counterparty This is used to identify if Organization identification is used as Proprietary Identification or Private Identification Counter Party Scheme Name Type Select the Identification Scheme Type of the counterparty from the select list The valid values are e C Codes e P Proprietary oe ORACLE 3 12 Counter Party Scheme Name Specify the value for Identification Scheme Name f
415. y the product if required if you choose to do so you can only choose a product belonging to the same product type as the product a9 ORACLE category that you specified Based on the product code the system will default the currency code linked to this product in the Txn CCY field Alternately the system can also arrive at the product code based on the currency specified in the Txn CCY field Customer Details Clearing Branch Specify the clearing branch where the amount is getting cleared Customer Account Branch Specify in which branch a customer is holding an account Customer Account Currency Select the currency for the customer account in which it is maintained Customer Account Number If you choose to specify the customer account the name and number will be displayed when you save the contract You must enter a valid customer account maintained in Oracle FLEXCUBE in this field or a GL for which posting is allowed If you use the option list available in this field the customer number and name will be displayed instantly Customer Number System defaults the customer number when you select the customer account number Name System defaults the customer name when you select the customer account number Bank Code Specify the code for the bank that is used in the clearing activity Account Local Clearing Format Specify the local format used in the clearing the amount Customer Information Customer
416. y working days of particular currency attached at product The field derives valid days for reversal based on the above options selected It is configured as Currency Calendar for SDD B2B CORE and COR1 products Note Activation Date of the contract will be considered as the from date for the calculation of number of days allowed for reversal process The requirement for Reversal timeline can be achieved by configuring Allowed Reversal Days as 5 and with Calendar Basis as currency calendar This is applicable for Outgoing collections and Incoming Collection Products Incase of manual creation of Reversal transaction in Payments amp Collections Transaction Input screen PCDONONL after 5 Currency working days from the activation date system will display an error PC REVRO06 message and transaction will not get saved Incase of Incoming Collection through upload for both Pacs 007 001 02 and Pain 007 001 02 reversal of outgoing collection transactions received after 5 Cur rency working days from the activation date will be moved into Transaction Repair TR queue Response Fields Auto Response For Outgoing requests for debit products you can indicate that the system generated response is required for collection transactions involving this product Enable this option by checking the Auto Response option positioned next to this field ASCII Handoff Required For contracts involving the product you
417. yment Cancellation Camt 029 001 01 a0 ORACLE 5 25 1 Additional Reject Reason Select the additional reject reason from the adjoining option list Note Specify either Reject code or Additional reject reason Cancellation Commission Code Select the cancellation commission code from the adjoining option list Cancellation Commission Amount Specify the cancellation commission amount The Incoming Payment Cancellation Approval screen lists only the incoming payment contracts You can select the message and approve or reject the recall request The system does not validate the number of days before the recall request can be processed If you reject the incoming recall message then you have to input the reject reason On save of the selected contracts the system creates a reference number and inserts the message details in new data store The table below lists the reject reason maintained in the system LEGL Legal Decision Reported when the cancellation cannot be accepted because of regulatory rules AGNT Agent Decision Reported when an agent refuses to can cel CUST Customer Decision Reported when the cancellation can not be accepted The system authorizes the set of transaction stored for payment cancellation It picks only authorized records for payment cancellation initiation During recall of the contract the recall reason should be the recall reason provided in the camt 056 message
418. ype from the drop down list The drop down list contains the options FIN and FIN Y Copy This preference is used in Funds Transfer module Network Service Identifier The service identifier that is specified here will be displayed in Field 113 of Block 3 header in the RTGS message Note This will be enabled if network type chosen is RTGS Customer cover messages are always generated in new format MT202COV or MT205 COV This preference is used in the Funds Transfer module For more details on new cover message formats refer to the Settlements user manual Incoming Branch Code Specify the code for the branch that is participating in the incoming account process Incoming Currency Code If you select the currency code all the accounts associated with the chosen currency code will be displayed in the option list provided in the adjacent field Incoming Account In case of incoming transactions received over the network the account that you indicate here will be debited by default Description In case of TARGET 2 clearing network the default incoming account will be the primary nostro account with the central bank that should be debited while processing an incoming TARGET 2 payment Outgoing Branch Code For all outgoing transactions sent over the network you are maintaining you can specify the default account that should be credited Outgoing Currency code If you select the currency code all t
419. ype is Test Transaction P2P Final Payment or Null then it is mandatory to specify the Counterparty Bank Code and Counterparty Account Number during the customer debit transaction 4 2 2 1 Processing Rejects of Inward or Outward DDs For transaction rejects outgoing or incoming DD that are uploaded after the applicable response days have elapsed an override is sought by the System The processing for such transactions is based on two factors e Whether the Process After Response Days option has been set in the product preferences for the product used by the transaction e Whether the override that is sought in such cases is accepted Accepting the override in the case of incoming DD transactions would result in rejection of the transaction In the case of outgoing DD the transaction is placed in the Process Exception Queue from where it can be taken up for processing or rejected The processing of rejection for such transactions is depicted below ORACLE Outward DD Are a Response Process Days Overrid Roles greater ayatam Action After than Action Accept Response ee Days Rejection Days Yes Yes Reject the con tract Yes No Override Yes Contract is placed in Pro Receiving cess Exception with excep Date is more tion queue PE It can then than the be unlocked and saved response days again if required If so the Do you want to same override is sought reject the con agai
420. ys for Customer Specify the number of days within which the incoming cancellation request with customer error needs to be accepted Days Basis Select the days basis to indicate whether the cancellation days computation is based on the working days or calendar days Calendar Basis Select the calendar basis for computing the maximum acceptance date 16 ORACLE 4 2 4 4 2 4 1 Network Parameters Tab Click the Network Parameters tab to specify the network parameters pertaining to the product Payments and Collections Product Preferences x a Product Code Collection Type Ooo Collection Scheme Type C W E Description RFDType Product Type Transfer Type Customer Transter z Main Aan Outgoing Payment Parameters Authorization and Release Limits Pe Authorization Currency Authorization 1 Limit Authorization 2 Limit N Release Limit ransaction Window periods Full Day Time in 24 hours clock Initiator Start Time H M Initiator End Time H M m Auth1 Start Time H M Auth End Time H M Auth2 Start Time H M Auth2 End Time H M Release Start Time H M Release End Time H M transaction Window Periods Half Day Time in 24 HR clock Initiator Start Time H M Initiator End Time H M Auth1 Start Time H M Auth1 End Time H M Auth2 Start Time H M Auth2 End Time H M Release Start Time H M Release End Time H M List of Banks Specifying Authorization and Release Limits Auth
421. ys the customer who is allowed for the station maintenance Customer Name System displays the customer name that is allowed for the station maintenance Branch System displays the branch that is allowed for the station maintenance Account System displays the account details that are allowed for the station maintenance Currency System displays the currency details of the transaction that is allowed for the station maintenance Maintaining Product Categories You can associate the products that you have maintained at your bank with product categories A product category helps in identifying the product that should be used to process a transaction that is received a0 ORACLE You can maintain product categories in the Payments Product Categories Maintenance screen You can invoke this screen by typing PCDPDCAT in the field at the top right corner of the Application tool bar and clicking the adjoining arrow button Payments Product Category Maintenance E New amp enter query Product Category Product Category Transfer Type Bank Transfer xj Category Description Collection Type Product Type VEW Detail Clearing Fields Offset Category Recall Category Reject Category Approval Category Redispatch Category Reverse Category Book Transfer 10f1 E Product Currency Description Offset Reject Recall Approval Redispatch Reverse Network Duplication UD

Payments and Collections User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents