View
354
Download
1
Category
Preview:
Citation preview
© 2015 IBM Corporation
SEPA Archiving with IBM OnDemand
IBM Enterprise Content Management
Reinhold Engelbrecht IBM Analytics - Enterprise Content Management (ECM) Technical Sales Leader Europe r_engelbrecht@at.ibm.com
© 2015 IBM Corporation
IBM Enterprise Content Management
2
SEPA context
SEPA = « Single Euro Payment Area »
– Stands for the European Union (EU) payments integration initiative.
– Within SEPA, bank customers can make electronic euro payments across 32 countries under the same basic rights and obligations
– SEPA represents 95% of European payement transactions
SEPA transactions concern :
– SCT = SEPA « Credit Transfers » >> about 5.400.000.000 transactions / year
– SDD = SEPA « Direct Debits »
– SEPA « debit cards »
SEPA messages
– All SEPA communications (transactions) are in XML format (ISO 20022)
SEPA message must be archived for compliance purpose (dispute management)
© 2015 IBM Corporation
IBM Enterprise Content Management
3
SEPA message structure
A SEPA message is made of : a) A header b) The list of all banking transactions carried by the message In the example below, the SEPA message deals with 4 transactions:
Header
Transaction record
4 transactions
Message
© 2015 IBM Corporation
IBM Enterprise Content Management
4
SEPA message structure (example)
Header General Info
• Msg ID
• Date & Time
• Nb of transactions
• Total amount
Settlement Info
• Sttl Date
• Sttl Account
• BIC Code
Transaction 1
…
Transaction n
FIToFICustomerCreditTransferV03 pacs.008.001.03
© 2015 IBM Corporation
IBM Enterprise Content Management
5
Transaction Info
Transaction Info
• Instructor ID
• EndToEnd ID
• Tx ID
• Tx Amount
• Tx type
Debitor Info
• Name/adress
• Account
• BICFI
Creditor Info
• BICFI
• Name/adress
• Account ID : IBAN
Remittant Info
Transaction 1
…
Transaction n
SEPA message structure (example) FIToFICustomerCreditTransferV03 pacs.008.001.03
© 2015 IBM Corporation
IBM Enterprise Content Management
SEPA archiving with IBM OnDemand
Highly efficient storage for SEPA transactions (XML data)
– Compression rate of 1:13 to 1:30 – IBM OnDemand is one of the most efficient backend
for storing high volume data with a small system footprint and huge storage savings
– Compliance archiving – leverage secure and compliant (WORM) storage which can be
used for transactional access as well
– General XML and other output format store
IBM OnDemand understands SEPA / ISO 20022 pain and pacs messages natively
– Extraction of transactions out of message streams
– Automatic indexing with important transaction details (configurable search fields)
– Additional processing information (e.g. from your core banking system) can be stored associated with
the data
Easy access and fast search for SEPA transactions
– All transactions and messages are accessible in a client and via a programming interface (API)
– All data is accessible in the original format as well as human-readable with a web-based viewer – but
all data is stored only once
• OnDemand can serve as application backend store from which your application can access their
old data directly (API)
• Users can access the SAME data through web client and viewers via on-the-fly rendering
(including printing and emailing) 6
© 2015 IBM Corporation
IBM Enterprise Content Management
7
© 2015 IBM Corporation
IBM Enterprise Content Management
SEPA transaction processing and viewing
Transaction processing is flexible and customizable
– Which metadata to capture
– Bulks can be split
• Transaction based, IBAN based, …
– Handling of group header information and
its relation to the transactions
– Storing of additional processing and
settlement data
Viewing transactions and transaction groups is done based on HTML (XSL) style sheets
– Can be customized as part of the implementation
– Viewing forms can be versioned
Splitting of a bulk messages (as received) into the different SEPA transaction types
– Access and retrieve for each single transaction
– Access security can be set on transaction level (via OnDemand SQL query restrictions)
Accessing related transactions and access of the entire bulk is possible (customization)
8
© 2015 IBM Corporation
IBM Enterprise Content Management
Example: Refund of authorised Direct Debt transaction (SDD)
A refund must be claimed within 8 weeks starting from the date on which your account was
debited.
The claim must be sent by the Debtor at the latest 13 months after the debit date of the
disputed Collection.
SEPA DS-05 (ISO 20022 pacs.004.001.01 and pacs.002.001.02)
9
Handling of dispute and refund cases
– Access to the entire message flow
– Access to related entries
– Free search
– Print or email
– Hand-over of the relevant data to the
core banking system – in the original
SEPA format
© 2015 IBM Corporation
IBM Enterprise Content Management
Search and display of related transactions
Display related documents through saved searches from the Web Client
– Example: returning a direct debit payment return Message (pacs.004)
– Go directly to other related documents (e.g., same IBAN)
Searches
– Go back to the original transaction
• Chargebacks include a reference to the OrgnlMsgId
– All transaction messages between this vendor and the customer (IBAN)
Complex custom searches
– Free, complex queries can be formed and executed against any search fields of the
entire dataset
• Differentiate between SDD/SCT reject, time intervals, …
• Return due to coverage error go to other systems for further information (link to
core banking)
– Aggregations possible (calculating totals, etc.)
– ... and further customizations possible
10
© 2015 IBM Corporation
IBM Enterprise Content Management
11
Recommended