Process - Technical Documentation - Docx - 0
Process - Technical Documentation - Docx - 0
Version
Control
Date
Author
Version
1.0 02/06/2023 Viviane Mancuso
1.1
Summary
1Purpose.........................................................................................................................................................2
2Scope............................................................................................................................................................2
3Structure.......................................................................................................................................................2
3.1Functional Requirements - Mandatory.................................................................................................2
4Files..............................................................................................................................................................2
4.1Customer Report (Customer Level)..................................................................................................... 3
4.2Deposit Report (Deposit Level) ...........................................................................................................3
4.3Position Report (Tranche Level)..........................................................................................................3
4.4Transaction Pending (Deposit Level)...................................................................................................4
4.5Cashflow Pending Report (Tranche Level) .........................................................................................4
4.6Transaction Report (Individual Deposit Level)....................................................................................4
4.7Cashflow Report (Tranche Level)........................................................................................................4
4.8Files to be Imported..............................................................................................................................5
1 Purpose
The purpose of the document is to describe the automation process to implement the time deposit for BB
Frankfurt.
2 Scope
Describe how the application will be implemented to create the Time Deposit between Raisin
and BB Frankfurt.
3 Structure
3.1 Functional Requirements - Mandatory
1 FUNCTIONAL REQUIREMENTS - MANDATORIES
1.1 Configure a sFTP drive where Raisin will send files to be processed.
1.2 Create an app on ServiceNow to read the files and save the information in an internal database.
1.4 Use an API to communicate with Flexcube and create/cancel a Time Deposit.
4 Files
6.2 Deposit
7 Flexcube Integration
The fields highlighted below are the most relevant one, when inserting deals in
Flexcube.
BIC: BRASDEFFXXX
IBAN: DE56 5122 0800 0000 1508 88
BB Frankfurt keep the settlement of the deals separate to the actual external
payment to and from raisin bank AG.
On settlement date BB Frankfurt will make a manual payment for capital and interest to raisin bank. The
separation of payments is essential.
That means interest needs to be paid onto one account of raisin bank AG and the capital
onto another raisin bank AG account.
Therefore, BB Frankfurt will need to receive a reconciliation report to align the amounts
from the trades in FC with the due amounts of raisins.
That’s also important for the reconciliation of the brokerage of each individual deposit,
which they must pay to raisin.
At Maturity:
BB Frankfurt will not do roll over mechanism, and no possibility of early repayment,
so each deposit will mature, and the tranche capital and interest are paid back to raisin.
Therefore, active deals are marked as OPC and maturing ones as PYO (pay out).
Pay-out amount: is the total amount to be paid out, BUT you need to separate capital
and interest.
Pay-out interest: the interest to be paid out.
7.2.1 TimeDepositCreateRequestExample.xml
7.2.1.1 Test Example:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:typ="http://types.ws.gw.fcubs.iflex.com">
<soapenv:Header/>
<soapenv:Body>
<typ:CreateLDContract>
<![CDATA[
<FCUBS_REQ_ENV xmlns="http://fcubs.iflex.com/service/FCUBSLDService/CreateLDContract">
<FCUBS_HEADER>
<SOURCE>DEPSOL</SOURCE>
<UBSCOMP>FCUBS</UBSCOMP>
<MSGID>0001ab2</MSGID> - referencia da Raisin
<CORRELID>0001ab2</CORRELID> - referencia da Raisin
<USERID>RPABBAG</USERID>
<BRANCH>FFT</BRANCH>
<SERVICE>FCUBSLDService</SERVICE>
<OPERATION>CreateLDContract</OPERATION>
<DESTINATION>DEPSOL</DESTINATION>
<FUNCTIONID>LDDCONON</FUNCTIONID>
<ADDL>
<PARAM>
<NAME>SERVERSTAT</NAME>
<VALUE>HOST</VALUE>
</PARAM>
</ADDL>
</FCUBS_HEADER>
<FCUBS_BODY>
<Contract-Master>
<AMT>15000</AMT>
<BOOKDT>2023-01-23</BOOKDT> - Data do dia
<CCY>EUR</CCY> -- pegar tabela raisin
<CPTY>485469982</CPTY> - MCI do Customer
<DFLT_ACC>0000150888</DFLT_ACC> - Conta de BBF – Create a table for instructions
<DFLT_ACC_BRN>FFT</DFLT_ACC_BRN> - Create a table for instructions – this field is fix for
Frankfurt
<DRSETLACBR>FFT</DRSETLACBR> - Create a table for instructions – this field is fix for Frankfurt
<DRSETLAC>0000150888</DRSETLAC> - Conta de BBF – Create a table for instructions
<MATDT>2023-02-27</MATDT> - get from Raisin file
<PRD>CDXX</PRD> - Create a table for instructions – this field is fix for Frankfurt
<ROLLALLW>N</ROLLALLW> - Add on the instructions table
<VALDT>2023-01-27</VALDT> - get from Raisin table (start dt)
<XREF>0001ab2</XREF> - referencia da Raisin
<Interest-Main>
<INTCOMP>CDINT</INTCOMP> - add on the reference table
<RTTYPE>X</RTTYPE> - add on the reference table
<INTRATE>1.5</INTRATE> - get from Raisin file
</Interest-Main>
<Taxdetails-Main>
<SCHEME>TAXIND</SCHEME>
<WAIVER>Y</WAIVER>
</Taxdetails-Main>
<Taxdetails>
<TAXRULE>TAXTD</TAXRULE>
<WAIVER>Y</WAIVER>
</Taxdetails>
<Taxdetails>
<TAXRULE>TAXTD1</TAXRULE>
<WAIVER>Y</WAIVER>
</Taxdetails>
<Taxdetails>
<TAXRULE>FFTINC</TAXRULE>
<WAIVER>Y</WAIVER>
</Taxdetails>
<Taxdetails>
<TAXRULE>FFTSOL</TAXRULE>
<WAIVER>Y</WAIVER>
</Taxdetails>
</Contract-Master>
</FCUBS_BODY>
</FCUBS_REQ_ENV>
]]>
</typ:CreateLDContract>
</soapenv:Body>
</soapenv:Envelope>
7.2.2 TimeDepositQueryRequestExample.xml
FCUBS_REQ_ENV xmlns="http://fcubs.iflex.com/service/FCUBSLDService/QueryLDContract">
<FCUBS_HEADER>
<SOURCE>DEPSOL</SOURCE>
<UBSCOMP>FCUBS</UBSCOMP>
<MSGID>MD20231626373148</MSGID>
<CORRELID>MD20231626373148</CORRELID>
<USERID>RPABBAG</USERID>
<BRANCH>VIE</BRANCH>
<MODULEID>LD</MODULEID>
<SERVICE>FCUBSLDService</SERVICE>
<OPERATION>QueryLDContract</OPERATION>
<DESTINATION>DEPSOL</DESTINATION>
<FUNCTIONID>LDDCONON</FUNCTIONID>
<ADDL>
<PARAM>
<NAME>SERVERSTAT</NAME>
<VALUE>HOST</VALUE>
</PARAM>
</ADDL>
</FCUBS_HEADER>
<FCUBS_BODY>
<Contract-Master>
<FCCREF>VIECDAL231220007</FCCREF>
</Contract-Master>
</FCUBS_BODY>
</FCUBS_REQ_ENV>
7.2.3 TimeDepositVAMIRequestExample.xml
<FCUBS_REQ_ENV xmlns="http://fcubs.iflex.com/service/FCUBSLDService/LDVamiContract">
<FCUBS_HEADER>
<SOURCE>DEPSOL</SOURCE>
<UBSCOMP>FCUBS</UBSCOMP>
<MSGID>MD20231626285461</MSGID>
<CORRELID>MD20231626285461</CORRELID>
<USERID>RPABBAG</USERID>
<BRANCH>VIE</BRANCH>
<MODULEID>LD</MODULEID>
<SERVICE>FCUBSLDService</SERVICE>
<OPERATION>LDVamiContract</OPERATION>
<DESTINATION>DEPSOL</DESTINATION>
<FUNCTIONID>LDDCONON</FUNCTIONID>
<ACTION>UNLOCK</ACTION>
<ADDL>
<PARAM>
<NAME>SERVERSTAT</NAME>
<VALUE>HOST</VALUE>
</PARAM>
</ADDL>
</FCUBS_HEADER>
<FCUBS_BODY>
<Contract-Master>
<FCCREF>VIECDAL231320013</FCCREF>
<AMTDT>2023-06-12</AMTDT>
<VALDT>2023-06-01</VALDT>
<MATDT>2023-06-15</MATDT>
</Contract-Master>
</FCUBS_BODY>
</FCUBS_REQ_ENV>
8 Servicenow
8.1 Structure
For the automation of the process, the following structure was built in ServiceNow:
Table
Access Control
The access to the Treasury transaction, as it is more sensitive, it has been configured with a double
signature approval. One administrator grants, another confirms.
9 Regulatory Reports