user group meeting – poland 2012 - andra.com.pl · pdf filecash management mcft...

© 2012 Omikron Systemhaus GmbH & Co. KG www.omikron.de

User group meeting – Poland 2012

www.omikron.de

MultiCash News / Roadmap


e-banking solutions

Classic Corporate Electronic Banking Internet Banking

Payment

Factory Solutions

Omikron Product Portfolio

ConsultancyProducts

Service

• MultiCash

• MultiCash WebEdition

• MultiCash Transfer

• UbiqCash

• MultiCash@SmartOffice

• MultiCash Portal


Classic Corporate Electronic Banking

EB

MultiCash in the Product Portfolio

-enabled

� MultiCash “classic“ corporate e-banking suite

� MultiCash WebEdition pure browser application, mobile-enabled

Current Footprint

- 17 languages

- 40+ modules - still growing (payments, trade, other …)

- approx. 300 banks (stable) across Europe and China


� “Multiple, local“ approach

− Number of country adaptations increasing

− Constantly updated to remain compliant with local changes

− User Groups, working groups, Steering Committees contribute to change process

� Popular with end-users

− Priorities different from banks (integration, automation, multibanking …)

− Many changes/enhancments driven by corporates, corporate communities

� Increasing focus on Large Corporates

− Large data volumes

− Application functionality

− Security / Audit

MultiCash Today


Integration PaymentsCash

Management MCFT

MultiCash and ….China

Accounting

MultiCash

WebEdition MultiCash

Bank Server

Inte

rfaces

Special Characteristics

� WebEdition is preferred

� Real-time services are expected

� Cash Management tools are in the

foreground

Payments

� Full support for CNAPS Clearing formats

� Order types

─ Credit Transfer

─ Direct Debit

─ Bulk Direct Debit

� International Orders

─ SWIFT MT101 format

─ Reporting interface planned (2011)


USER1

欢迎您使用广发银行

MultiCash现金管理系统


Erfahrung und Innovation

Thema

Slogan (optional)


ICBC

MCFT Secure

Communication

Corporate

BOC

ABC

CCB

Service Centre

Other :

• Joint-Stock Banks

• Regional Banks

• Urban Banks

Banks

Mid-size and

Regional Banks

The “Big Four“

BP – Enterprise Banking Platform

(adapter)

AcccountInformation

Payments

MultiCashWebEdition

MultiCashBank Server

BP Interface

Multibanking in China – Pilot Project

• China CITIC Bank

• China Everbright Bank

• HuaXia Bank

Current Status : • 25 Banks connected

• verified by Omikron


BP – Enterprise Banking

Platform (adapter)

MultiCashWebEdition

MultiCash Transfer

MultiCashBank Server

BP Interface

MultiCash

Bank Servers

MultiCash Payment Factory with China

MultiCash

Bank Servers

Other

Bank Servers

MCFT

MCFT

EBICS, SWIFT...

European / International

Banks

Chinese Banks


xie-xie

....and now back to business ...



www.omikron.de

MultiCash „classic“ – New Developments Version 3.22


� Separates internal workflows from bank authorization

� Configuration options : none, one, two approvals

� Signature before or after approval

MultiCash 3.22: Approvals in File Manager


� Unlimited archiving of all incoming / outgoing data

� Configuration options : global, annual, half-yearly, quarterly, monthly

� Simple selection of files from File Manager

� All standard functions and data profiles unchanged

MultiCash 3.22: History in File Manager


MultiCash 3.22: Account Information

� Statement import: control separately per account…

… for large volumes of transactions

− Complete (default): all transactions as to date

− Not imported: no account information imported

− Aggregated Import : One Credit/Debit transaction per value-date…

− … Cash Pool transfers are not aggregated

� Extended Data Model …

Accounts : 65.500 (up to version 3.22.003: 9.999)

Statements per month: 99.999

Transactions per statement: 2 billion (up to version 3.22.005: 65.500 )


MultiCash 3.22: Statement / Transaction History


MultiCash 3.22: New Modules / Enhancements

� Module Organisational Units …

… Authorization concepts for different corporate divisions or group companies

� Module Statistics …

… collects number of transactions and amount totals on monthly basis

� Inhouse Bank interface (SAP IDOC) …

… Format-Subsystem, manual payments, CSV-IDOC conversion

� Signature module PKCS#11 …

… supports new tokens, e.g. for France Keynectis and SWIFT 3SKey

� SEPA allround package …

… Format validation, Data migration, Payment conversion, Mandate administration

� EBICS module France …

… transparent support of French operating modes T or TS

� Module Bill Presentment and Payment (Invoice Service) …

… Administration of incoming / outgoing invoices with payment generation


SEPA – Important aspects at a glance

� Objective is one Europe-wide payments area for transactions in Euro

� From 01.02.2014 mandatory use of SEPA instruments Europe-wideas well as decommissioning of national payment formats

� Account details presented as IBAN and BIC instead of account/bank code

� Use of ISO 20022 XML formats for „European domestic payments“

� Payment details : up to 140 characters

� Direct Debits...

… Legitimation of direct debit via paper mandate, subject to strict rules

− Each direct debit must include a mandate reference and creditor ID

− Information obligation in form of a pre-notificaton incl. amount, due date, mandatereference and creditor ID

− Lead time of up to 5 days


SEPA – Challenges of Migration

� Is one payment module for all Europe possible ?

� Can I continue to use my recurring details ?

� What happens if I have not migrated all systems to SEPA by 01.02.2014 ?

� I do direct debits and have now to handle mandates. How can I manage them in future efficiently and comply with the organizational regulations ?

� How can I ensure that the payment files delivered by my internal systems are correct ?

� What must I consider if the the information provided by my banks is also generated in XML format ?

� What about payments in other currencies or from / to banks outside the Euro zone ?


Currently supported in the MultiCash Platforms :

� General

− MultiCash

− UNIFI 2006 and 2009

� Germany

− DK (ZKA)

− Container Solution (private banks)

� Belgium (UNIFI with defined special contents)

� Austria (STUZZA-Format)

� Switzerland

� Czech Republic

� Poland

� Slovakia

� Others as and when required

SEPA – Payment Module


• Character set• IBAN check digit• Check digit of Creditor-IDs

• General structure• Sequence of elements• Mandatory fields• Syntax of fields

Known XML-Schema ?• UNIFI standard• National variant

Accounting

SyntacticalRules

� SEPA Credit Transfer

� SEPA Direct Debit (Core)

� SEPA Direct Debit (B“B)

XML-SchemaSyntax /

Schema Match

MultiCash / MultiCash Transfer

On-Screen Display

Check Log

With error indicator :• Container level• Message header• Batch level• Transaction level

Functions :• Search• Print• PDF Report

Enter to File Manager(with signature)

SEPA File Checker


SEPA – Migration Tool

� Goal : Import of data from local payment modules

Payment orders (single order, standing order, template)

Banks, Ordering Parties, Accounts

Partners

� Conversion Bank code/Account number �� BIC/IBAN

Option 1: external with IBAN-“Output“-/IBAN-“Input“-file

Option 2: internal mit “Omikron IBAN-Finder“ …

… detect special cases !

� Status: available for German domestic/foreign payment modules …

… others possible on request

Local PaymentModule

MultiCash

SEPA Module

Import Data


SEPA – Migration / Conversion : IBAN-Finder

� Functions

Conversion IBAN-“Output“- � IBAN-“Input“-file

Integration in Application

Automatic update bank code table for BIC (currently AT, CH, DE)

Automatic update of library for special cases (currently DE)

� Status: available for Germany, Austria, Switzerland …

… all known special cases implemented, will be udpated as required

… other countries can be realized on request

IBAN-Finder

BundesbankAustrian NB

Swiss NB ..

MultiCashBank Code Table

Special Cases Omikron


� On the basis of existing components …

… Standard DTA-SEPA Converters realized as add-on module for MultiCash

DTAUS-Transfer � SEPA

DTAUS-Direct Debit � SEPA …

… Mandate data in defined details fields …

… provided from mandate administration

DTAZV-Transfer � SEPA (planned)

Austrian EDIFACT � SEPA (planned)

SEPA -Converter

ERP-Systems Banks

MultiCash

DTAUS

ATI

SEPA

SEPA – Converter


Mandate Administration

� Mandate…

… unequivocal identification of the contracting party and the agreement:

� Creditor ID

� MandateID

� Date of signature

� Cycle (OOFF, FRST, RCUR, LAST)

� Mandate administration …

… simply integrated into the payment module

… saves mandate information

… adds mandate information for payment

… supports mandate changes and transfers amendment information to payment


Mandate Administration


Mandate Admin Plus (1)

� Enhancement of the Standard Mandate Administration (divided into projects)

� Target group: Medium-sized businesses which administer mandates in MultiCash

� MandateID, Description, BIC/IBAN, List of internal IDs (e. g. contract numbers)

� Import/Export of mandate data from CSV files

� Import of mandate data from DTAUS files

� Print of mandate data to printer or in PDF format

� Mandate forms

� Entry of incomplete mandate data as basis for the printout of mandate forms

� Configurable form templates separated by direct debit type CORE/B2B and language

(default German, English)

� Printout of the correct mandate form depending on the chosen drawee (language) and

mandate type to printer or in PDF format

� Start of the Standard Mail program with predefined content (configurable text) for form

transfer (for Core module systems with E-Mail-Interface automatic transfer as serial

mail)

� Addition and check on completeness of the mandate after receipt of the signature



� Administration of dematerialised mandate forms

− Import of any display formats (as a rule PDF) for each mandate entry

− Start of the standard display program for the relevant display format from the

program dialog

− Export of saved display files

� Mandate history

− Version administration for the mandates

− Storage of an optionally large number of mandate versions in a history table

(including display file of the signed mandate form)

− Display, print and export of mandate history


� Status Monitoring Advance notices/Cycles/Validity

− Supervision of periods for mandates pending advance notices/expiry

− Signalling of due advance notices/expiry in the information manager of the Core

module system

− Creation of a list with due advance notices/expiry data

− CSV-Export of due advance notices/expiry data

− Start of standard mail program with predefined content (configurable text) for

each due advance notice (for Core module systems with E-Mail-Interface

automatic transfer as serial mail)

− Printout of a letter (configurable text) for each due advance notice



� Functional interfaces

− Add mandate information for direct debit order

− Add mandate amendment information for direct debit order checking the timely

remittance with correct mandate cycle according to the rules for CORE and B2B

direct debits

− Prompt and add direct debit status (validity, cycle) for direct debit order and

status adaptation

− Reset direct debit status (e. g. from Payment Status Report)

− Add amendment information for direct debit order

� Interfaces for the following modules

− SEPA Payment module

− Standard SEPA Converter

− UbiqCash Converter platform



Side Topic : XML - ISO 20022 – Payment module

� Requirement:

... Basic use of a flexible XML structure for payment orders as for SEPA

... But: Option for payments outside the SEPA area

and / or with foreign currencies

... An XML format for all banks:international, standardised, across all banks

� Solution:

... New Payment module on the basis of ISO 20022 with adaptations

to the new requirements of banks and corporates

... Basis: Specification of the Common Global Implementation Initiative (CGI) in the “XML ISO 20022 Version 03“


Summary

All in all, MultiCash platforms support:

� SEPA Payment module

� SEPA Enhanced mandate administration (Q3 2012)

� SEPA File checker

� SEPA Data migration

� IBAN-Finder (including bank code and SCT download / special cases download)

� SEPA Converter

� SEPA Returns/Rejects (pain.002)

XML in MultiCash is beyond SEPA:

� XML-CAMT account information

� Converter CAMT-XML -> UMSATZ.TXT / AUSZUG.TXT

� XML-CGI Payment module (Common Global Implementation)


SEPA – Overview of Solution Package


Germany France

Payment

authorisation

One profile, authorisation case by case:

Without ES:

attribute D (T) plus any signature or

attribute O with signature class T

With ES:

ES classes E, A, B

Distributed signature is standard

Two general profiles:

EBICS T: without signature

attribute D (T) plus any signature

EBICS TS: with ES

ES class E, 1-2 depending on amount limit

No Distributed signature supported

Session Type Classic session type handling by transaction type

Restricted to standardised session types plus

individual beginning with X, Y, Z

Session type FUL/FDL: File Upload/Download

+ Attribute FileFormat according to SWIFT

(individually enhanced by bank)

Key certificates Not used Certificates are mandatory

EBICS T: all self signed

EBICS TS: CA certificate on hardware token

mandatory for payment authorisation.

Several CAs supported, e.g. SWIFT

Side Topic: EBICS France (1)


Side Topic: EBICS France (2)

� Both FR-variants are supported by MultiCash …

• Profile T: with Transport signature, authorization by cover note …

… MultiCash: Module FR-EBICS

… Bank Server: Module FR-EBICS

• Profild TS: Transport, authorization by personal Signature …

… MultiCash: Module FR-EBICS + EU-PKCS#11 + Signature-Token

… Bank Server: Module FR-EBICS

� Signature Tokens with “CFONB-accreditated“ certificate

• Keynectis

• SWIFT 3SKey

• Both are hardware signature tokens with PKCS#11-Interface via USB (= security class 1)

� MultiCash 3.22.008 can connect with most banks in France …

… e.g. BNP-Paribas, Société Générale, CIC (all in production)

… sometimes problems with interpretation of certificates

… often non-standard FileFormat attributes to be supported


� Download incoming invoice and status …… store new invoices in database for processing …

… Invoice issuer and invoice receiver… Invoice number and date… Invoice amount and payment terms… Status

… store in sight format for checking and archiving… update status for existing invoices

� Key or Import (CSV or XML) outgoing invoices…… store in database for processing… create sight format (PDF)… upload to server… download status

� Generate payments in SEPA module …… Credit Transfer for incoming invoice… Direct Debit for outgoing invoice

� Report new status back to server…… accepted, forwarded for payment… rejected

Side Topic: Bill Presentment and Payment


Example : Overview and Details in Sight Format


MultiCash Bank

systemsERP-

systems

Statements

Payments

SEPAPayment Module

ModuleBill Presentment

Plan Data

InvoiceService

File Manager

File Creation

File Manager

Display SignatureFile

Transfer

File Transfer

Import Bank Data

Plan. Data reconcil.

Upload Status

Download InvoicesExport Invoice

Ch

eck

Invo

ice

s

Bill Presentment and Payment: Incoming Invoices


MultiCash Bank

systemsERP-

systems

Statements

ModuleBill Presentment

Plan Data

InvoiceService

File Transfer

Import Bank Data

Plan. Data reconcil.

Upload Status

Download Status

InvoiceImport

Invo

ice

En

try

Upload Invoices

Bill Presentment and Payment: Outgoing Invoices


User group meeting - Poland 2012

www.omikron.de

MultiCash „classic“ – New Developments Version 3.23


MultiCash 3.23: EBICS 2.5 - Overview

� Order number is set by bank server …

… Client sends request without order number

… Server sends order number back in response

� Session type HAC instead of PTK …

… XML-message pain.002 (PSR)

� Presentation in readable form

� Matching to order in File Manager (like PTK)

… PTK still supported

� For Bank Server : mandatory in Germany (and France?) from July 2012


� Transfer via XML-Container / ZIP-Container …

… assumes : MCC and MCB 3.23 and EBICS 2.4 / MCFT4

� Support for reference fields

in database, screens, selections, reports and export files:

− Transaction Reference / Batch Reference

− End-to-End Reference

− Mandate Reference

− Creditor ID

� Accounts matched via bank code / account number from IBAN

� Filling the fields BIC/IBAN in account record

� Processing the camt messages like SWIFT-MT messages as

− Balances / Statements / Transactions

− Intra-day items / Advices

� Generating AUSZUG.TXT/UMSATZ.TXT

� Reconciliation of plan data

� Transfer pain message to SEPA module

� Add-on modules for MultiCash and Bank Server

XML Statements : General Information


XML-Statements : Formats Supported

Message Session Type Content Processing mode

camt.052 C52 (ZIP-Container) Balance Report Statement

Intra-day items Intra-day items

camt.053 C53 (ZIP-Container) Daily Statement Statement

camt.054 C54 (ZIP-Container) Batch booking files - (only forwarding)

Debit advice / Credit advice Advice

pain.002 CRC (XML-Container)CRZ (ZIP-Container

Non-execution Credit Transfer SEPA History

CBC (XML-Container)CDZ (ZIP-Container)

Direct Debit Reject SEPA History


MultiCash 3.23: CAMT-Statement in MultiCash


XML-Statements : Notes on Introduction

� MultiCash …

… Realization as add-on module

… Pre-condition : version 3.23 and EBICS 2.4/2.5 or MCFT4

… Actions in the customer system (if needed):

� Collection with new session type, e.g. C53 instead of STA

� Extension UMSATZ.TXT interface with new fields

… Poss. merge accounts, if a new account record is created due to the IBANfrom camt (i.e. if IBAN <> bank code / account number)

� Bank Server …

… Add-on module for transfer of XML messages …

… alternative: converter MT940-CAMT

… Pre-condition : version 3.23 and EBICS 2.4 or MCFT4

… activate support of session types …

… and distribute e.g. C53 instead of STA where required

… if bank code / account number cannot be derived from IBAN …

… enter alias-account and allocate to customer and users

… Implementation of a new data transfer channel in the online interface or …

… as individual files per statement with standardised file name

… as pool file for all customers


MultiCash 3.23: Other Enhancements

� Signature keys in database …

… ease of use combined with secure storage

� HTML-Helps …

… Adaptation to current system environment

� File Manager: “Eyecatcher“ instead of file name …

… configurable : account number & name, reference, execution date

� Check for duplicate submissions …

… checks and compares with all current and historical files

� User administration: Standard profiles are delivered …

… makes it easier to configure and provides sample template

� SDS: Optimised setup and data exchange without internet browser

� MCFT 4


MCFT4: General Approach

� Change to current standards …

… for transport and security (encryption, authentication, authorisation)

� Security audit certification

� Keep “old” MCFT advantages (and avoid EBICS disadvantages) …

… flexible but standardised design independent from far-away specification boards

… easy setup handling for bank staff and customers

… qualified real-time acknowledgement including format and authorisation check

… no manual entry of bank parameters

… integrated messaging option

... integrated version management with seamless “protocol upgrade” …

… including automatic switch to MCFT4 with minimal user interaction

� Remove “old” disadvantages, improve easy handling and advanced features …

… remove: key change after each communication – AC27/29 problem

… remove: complexity in communication options (TCP/IP transport only)

… improve: exchange of bank parameter data

… add: recovery

… add: certificate support for digital signatures (optional addon-module)


MCFT4: General Redesign

� Transport layer / low level protocol …

… transparent TCP/IP communication (using configurable ports like today)

… optional HTTPS tunnel (via standard port 443)

… complete data stream processing with integrated recovery functionality

� Encryption: AES256 …

… secure Diffie-Hellman exchange of session keys before each communication ...

… separated from authentication key in order to encrypt INI job, too

… no storage of encryption keys -> no AC 29/27 problem, no backup problem

� Compression: ZIP method (like today)

� Logon / authentication …

… logon with authentication signature (based on additional user-key A)

… no communication password is send to bank

� Integrity: authentication signatures …

… in begin and end of connection

… plus MAC in each data block

� Payment authorisation (like today) …

… with personal signatures (B-key, all old and current versions supported unchanged)

� Qualified acknowledgement (like today)


� Initialisation

� Access data is sent as base-64-coded character string (by E-Mail)

� Cut-and-paste in entry field creates automatically BPD without data input

� First initialisation …

… generation of A- and B-keys (authentication and bank signature)

... local access password for A-key replaces communication password

… A-key is signed with B-key: only one key confirmation letter

… Bank approves B-key, signature on A-key is checked and access activated

� Special functionality

� Multi-file download integrated for transport of XML data blocks

� Integrated version management between client- and server systems

� Integrated master data management …… new user data is downloaded and imported automatically, no BPD sending necessary

� Integrated exchange of access class, organisational unit …… complete support of customer’s access rules for distributed or online signature

� Conversion procedure from old MCFT to MCFT4

� Protocol upgrade without configuration change (e.g. port) at client and bank sites

� MultiCash: Conversion assistant in client for generation and sending of new A-key signed by existing B-key -> immediate switch without confirmation letter

� Bank can open HTTPS channel at any time (with or without Omikron gateway)

MCFT4: Notes on daily work



www.omikron.de

Bank Server Today


Bank Server: General

� Objective : standard system …

… As far as possible – product, customization where necessary

… “conservative“ kernel

… “progressive“ and flexible interfaces as required

� Environments …

… only Windows Server, no additional components

… Cluster: Hot Standby Failover-Cluster (EMC2 und Microsoft)

… Virtualization : VM-Ware ESX-Server


Bank Server : Facts and Functions (1)

Databases …

… Standard: ZBase32

… SQL optional:

� Oracle: Optimization phase with a major international bank

� Microsoft SQL: in production

� IBM DB2 in operation as project development



EBICS-Performance

� Processing of large payment files …

… Measurements of one bank, sending high-volume files

… Investigation : how long does generation of customer report (PTK) take

Notes :

� Communication times were not measured, a differences in bandwidth would make this information useless

� In comparison : Omikron measurement with IZV-file, 400,000 orders (25 MB): transmission (100 MBit) in approx. 3:10 minutes

File Size Payments Omikron

Time with

Display

Competition

Time without

Display

1.5 KB 5 0 sec. 1 sec

600 KB 1,979 0 sec. 4 sec.

1.1 MB 3,506 1 sec. 5 sec.

340 MB 1,330,095 84 sec. 501 sec.



EBICS 24-hour stress tests :

Test environment :Processors/Memory: Intel Dual Quad 8 x 3.166 GHz / 4 GByte RAM

Hard disks: RAID 10 15.000 rpm, write cache with BBU

Network bandwidth: 100 MBit

System usage: 20 - 40 % (for test described)

Test data:DTAUS-files 1 – 1,000 orders (randomly generated)

In addition, a file with 1,000,000 orders (256 MB) every 10 minutes

Files Transactions Bytes

Total (24 hours) 127,431.0 173,970,831 44,569,154,560

Per hour (24 hours) 5,309.6 7,248,784 1,857,048,106

Per minute (24 hours) 88.5 120,813 30,950,801

Per second (24 hours) 1.5 2,013 515,846

Total (1 hour max.) 8,162.0 10,532,764 2,698,477,056

Per minute (1 hour max.) 136.0 175,546 44,974,618

Per second (1 hour max.) 2.3 2,926 749,577



� Realtime Host-Interfaces …

… Product components for integration in system kernal

… Customization to required environment within project, e.g.

Transaction data interface:

− IBM WebSphere MQ: in production

− Web-Service technology: in production

Static data interface:

− Web-Service technology: in production

� Administration …

… Windows-Client

… Terminal-Server / Citrix

… optional web interface “Admin@Web“


Add-On Module: Admin@Web



� Logon to central systems:

− LDAP/Domain-Controller: Windows user / password

− Central User Management Systeme …

… User / Password via Web-Service

… Token with Challenge/Response handling (e.g. Vasco)



Multi-Channel Platform

� “Classic“ Offline-Banking procedures …… in parallel MCFT, BCS-FTAM, BCS-FTP, EBICS

… compatible signatures, distributed signatures

� Online signatures with MultiCash@Sign …

… Authorization im Browser-Dialog with− Electronic Signature

− PIN/TAN, iTAN, mobile TAN

− Token solutions: Challenge Response (Vasco, Todos etc.)

… Delivery with− classic EB-procedures

− Upload via browser

− Import from third-party systems (FTP, SWIFT etc.)

… Batch submission via IT centres, e.g. DATEV (MCV, DTV)



� Internet Banking for corporates : MultiCash@Smartoffice

− Focus: payments / account reporting

− Target : internationally active corporates and banks

− Users in Europe - Africa - Asia

� Basis standard product – Adaptation in project

− Fully modular design

− Standard modules for many functional areas

− Functions / Layout / “Customizing” are key aspects of any portal

− Therefore : bank-specific layouts and settings



MultiCash@SmartOffice: Available payment and language modules

� Austria

� Bulgaria

� Croatia

� Czech Republic

� France

� Germany

� Hungary

� Kazakhstan

� Netherlands

� Morocco

� Poland

� Romania

� Russia

� Switzerland

� Slovakia

� Spain

� SWIFT MT101

� SWIFT MT103

� SWIFT MT200

� SEPA


Integration

� File-Interfaces ...

... standard formats of payment orders and statements:

− local payment format – routing by type, unit etc.

− SWFT MT940 – automatic distribution to customers´ mailboxes

� Online-Host-Interfaces ...

… for transaction exchange …

... real-time access to host while customer is on-line

... customized host connectors required

… for master data administration …

… automatic creation of master data by host application

... customized host connectors required

� Integration in Central User Management possible


Mainframe

Omikron Communication Platform

EBICSClients

EBICSClients

MultiCash

Server

Client

Client

Server

Server

Client

Client

Server

Transactions

Central User

Management

Client

Server

Logon

FTAM/FTP EBICS MCFT Sign SmartOffice

EBICSClients

EBICSClients

Browser-Clients

EBICSClients

EBICSClients

Browser-Clients

Admin@Web

Static Data

SAN

SQL

Bank Server : Summary



www.omikron.de

UbiqCash converter on bank server side


UBIQCash – Converter: Purpose

� Payment files (Files received from the customer)

− generally:

Converts various formats (e.g. SWIFT, EDIFACT, SEPA)

from various formats

(e.g. country or container formats)

− Specifically in the SEPA context:

Converts legacy country formats to SEPA XML files

� Account information (files to be provided from bank to customer)

− Converts CAMT back to STA, DTI, etc.


Bank-

Server

Back-office

UbiqCash

Files to be convertes

ParserConverter

Parser Converter

SEPA-Files

Administration

Converter-Engine

UBIQCash – Converter: main principle

SEPA or carrier format

Other

bank

servers

Country specific files


UBIQCash – Converter in the SEPA context

� Formatter are always kept on the latest status of format

descriptions / schema definitions

� Formatter can be added in a modular way

− Additional schema definitions

− Additional countries

� Flexible Routing of resulting files

− MultiCash Router with advanced capabilities

− MultiCash Transfer for the transport to other bank servers over the

available communication protocols (MCFT, EBICS, etc.)


UBIQCash – Converter: Product features

� Flexibility / Performance, Scalability as major design principles

� Parallel conversion distributed on several processes

� Priorities can be attached to the converter jobs (e.g. depending on the session

type)

� Converter jobs can be distributed to several servers

� Precise logging of the conversion process

� Exception Handling, if orders cannot be converted: complete rejection, or

partial processing. Repair station optional

� Optional: Extended Processing Monitor (EPM) indicating the exact root cause

of converting problems, exact matching between converter problem and

reason in the source file

� Resume at commit points, for interrupted conversion jobs

� Multi unit capability


UBIQCash – Converter: Challenges

� Conversion bank code/acc. no.-> BIC/IBAN

− IBAN-Finder (Omikron) or external conversion tool (using file interface)

− Checking with the well-known limitations (handling of the special cases)

� For SEPA direct debits: additional mandate information

required

− Adding mandate information to the legacy formats.

The definitions need to be published and implemented by the

customers. The definitions are limiting the filling of the details.

− Creation of a mandate database as service for the client?



www.omikron.de

Bank Server – New Developments Version 3.22


Bank Server 3.22: New Modules / Enhancements

� Module PDF-Statements …

… Delivery of statements in sight format (MCFT or MultiCash@SmartOffice)

� Module EBICS France …

… transparent support of the French operational modes T or TS

� Converter National SEPA-Format to UNIFI …

… standardizing SEPA messages for Back-Office interfaces

� SEPA-SRZ-Module …

… splitting SEPA-Container by service provider

… automated allocation to account/customer (like MCV/DTV process)

… entry to authorization queues according to usage rights …

… distribute signature (EBICS, MCFT), online signature (MultiCash@Smartoffice),approval by cover note

� Module New Messaging …

… Distribution of Messages


� Distribution of Messages via EB communication channel …

… encrypted and authenticated connection

… reliable delivery via statement download

� Configurable HTML message in the Corporate Design of the bank

� Simple operations for bank staff …

… Screen to enter messages, with support for attachments

… Communication via EB channel (MCFT, if required also for EBICS) or …

… via normal e-mail

… Simple selection of address data based on Bank Server data …

… also by use of freely definable mailing lists

… Different type of addressing :

globally per customer, for all users of a customer, for certain users of a customer

… Support of priority messages and validity period for message

… History of sent messages, option to re-send

Bank Server 3.22: New Messaging - Overview


Bank Server 3.22: New Messaging – Keying Messages


Distributing Messages: Customer side


New Messaging – Notes for Introduction

� Bank Server …

… Realised as add-on module

… Available from version 3.22.009

… Actions to activate in the bank system :

� Installation add-on module

� Only for e-mail:

– connection to e-mail Server

– storage of e-mail addresses of users

� MultiCash …

… Support in standard from version 3.22.008

… Actions to activate in customer system : none

… Automatic display in ILM, in main window

… Call of standard display program with double click for attachments

… Enforced display of “priority messages” at logon



www.omikron.de

Bank Server – New Developments Version 3.23


Bank Server 3.23: Other Enhancements / Add-on modules

� Support of MCFT 4 and EBICS 2.5

� Workflow optimisation: “Processing Mode 3“ …

… In-Tray procession integrated in communication process

… Out-Tray processing integrated in scheduler

� Reduces complexity, by reducing number of processes

� Increases throughput by reducing response times

� Easily horizontally scalable

… Out-Tray: new data model and delivery workflow …

… customer mailbox files replaced by new database handling with realtime delivery

… combination of current data, history data and SmartOffice download area

� reduced storage requirements, better access rule handling

� Limits for Direct Debits

� Add-on module MT940-CAMT Converter

� Extended First INI letter (printout or sent as PDF via e-mail) …

… Letter with access data in bank‘s design and overview of access right profile

… Response to submission of INI letters



www.omikron.de

MultiCash News / Roadmap

user group meeting – poland 2012 - andra.com.pl · pdf filecash management mcft...

Documents