2 2(16) Page Table of contents 1 Purpose of this guide Recommended information How to get started? 4 2 Project preparation List of interested parties and communication plan Project progress Checklist 8 3 Implementation Agreements signed Checklist Communication Checklist Formats Checklist Security Checklist 13 4 Test How are tests performed in Corporate egateway? What can be tested? Test accounts to be used Security and/or Authorisation Keys for the test period Go live and Service Support Security and/or Authorisation Keys for production Back-up systems Service Support Checklist 15 5 Documents to be read in relation to Corporate egateway... 16
3 3(16) Page 1 Purpose of this guide This manual is aimed at integration suppliers and customers who are about to integrate a financial system with Corporate egateway. The manual is primarily intended to support the project manager, but also members of the project team. Implementation is a part of the total project and this manual describes the tasks for project organisation and the planning of the implementation (blue parts in the plan). Detailed information for the implementation team is available in Project & activity plan. After each chapter you will find a checklist that should serve as inspiration for your work. Implementation of Corporate egateway requires a good organisation and a good understanding of the product as well as good communication among the parties involved. Investigation Decision Project preparation Implementation Test Go live Support Organisation established Agreements signed Communication established Formats implemented Security implemented List of interested parties finished Communication plan finished Documentation Activity list finished Four levels of information 1. (No colour) Level 1. The level to get an overview over the task, and primarily intended for the decision-makers. This level is not part of this manual. 2. (Blue colour) Level 2. The level at which you get more detailed information. You have to have sufficient knowledge to be able to react on the information, and you have to know where to collect more information about the subject. The target group is the project manager or project members who are not going to develop this task. 3. (Green colour) Level 3 is for the developers or persons with special responsibility. The information is detailed and easy to work with. 4. (Grey coloured) As level 2, but described in separate manuals.
4 4(16) Page 1.1 Recommended information If you have not been part of the previous part of the project, investigation and decision, you might need information about the functionality in Corporate egateway. Please see the list of manuals for further information connected to the Corporate egateway service. This description serves two purposes: 1. To describe the rules for implementation, give inspiration for what processes the implementation will go through, bring out factual issues regarding Corporate egateway and the implementation process, the organisation and who will participate. 2. To describe the support after implementation. The Message Formats and advises are described in special manuals. Most manuals can be downloaded in Adobe Acrobat Reader PDF format from Nordea's website Further information on the manual and general advice on integrated Messages can be obtained from Nordea's website The terms and definitions used in this document are defined in a separate document, Glossary for Corporate egateway, which can be found on Nordea's website: How to get started? There are many ways to start the implementation, depending on who is in your project, and how much they have been involved in the previous work around Corporate egateway. We cannot tell you exactly how to do or define roles and responsibilities for your organisation when starting up the project, but we can, out of previous experience and knowledge, offer you some advice from what we have learnt over the years, if you wish. A good start would be to define the preferred results of the implementation. This means to make sure in detail what the end-user expects from the system. This has nothing to do with technique, but the functionality and the picture of the result in the end-user s mind. If you and the end-user have the same picture in mind, you have a much better chance to guide the technique in the right way, and create a result acceptable for the end-user. In other words, less focus on the solution and more focus on the end-user. If your mind is on the end-user s everyday work, and all it implies, there is a bigger chance that the final solution will be better than expected. If you and the end-user can create a common idea of the starting point, you know exactly where you have to go and from where. So as a project manager, a good way to start is to make a common understanding in your company of the starting point and the final result of the implementation. To reach a common understanding, you need acceptance of the start and final result from the end-user as well as from the sponsors or owners of the systems. Organisation established
5 5(16) Page 2 Project preparation When it has been decided to implement Corporate egateway the first and most important step is to build a proper organisation and agree on how this organisation has to work, how it has to communicate internally, and what the members have to expect from each other. It is important for all parties to understand that this project organisation is not about sellers and buyers, but partners who work together to realise the same goal. The project organisation described below is not only applicable to Corporate egateway customer implementations, but could also be used in any cash management implementation. However, the work should be expanded to fully cover other CM strategic products. The project organisation described below is recommended to be used in all Corporate egateway implementations.
6 6(16) Page Further, in order to achieve fast implementations you should mirror this project organisation within your own organisation (illustrated with grey). Nordea do not require this but it may form a good basis for the discussion in relation to the allocation of sufficient resources, good communication and an appropriate escalation structure in the project. The Project Sponsors are the top authority of the project; they fund the projects and are the receivers of the project result. The global senior relationship manager and, if needed, the Head of the implementation team in Nordea are the Sponsors from Nordea. The Sponsor s function is also to support and/or solve serious problems that may arise during the project process concerning resources, support and co-operation between different departments both in your company and in Nordea. In smaller projects the Partner group and sponsor group can be merged. The Project Partners are responsible for following-up on the project and to make sure that this agreement is followed and are responsible for keeping themselves up-to-date with the project and ensure that this activity plan is complied with. They must receive status reports on an ongoing basis, decided by the Core Team. Further, it is their responsibility to follow up on the project manager if any deviations occur. They should also help the core team with significant questions or problems that may arise during the project phase, for instance resource problems. The project managers are responsible for the progress of the project and the daily project work. The project managers should handle all planning activities and exchange of information. The project manager may preferable participate in partner group meetings. However, formally she/he does not participate in the decisions in the group to prevent her/him from supervising his/her own actions. The Core Teams consist of specialists from different areas like functional issues, data flow and messages, implementation and testing. The Core Teams play an active part in the project and there may be direct contact between the members of the two teams. The core team members will receive all relevant information from the project. The Core Team is where the hands-on work is done in the project. The project manager is the driver of the Core Team and ultimately responsible towards the partner group. The extended team is an internal reference group. The members of the extended team should be informed of the ongoing process through status reports in order to be prepared and informed about what is going on concerning the specific implementation. The extended team will most likely at some point during the project process be actively involved, i.e. when setting up local systems for Corporate egateway. If obstacles occur that may influence the progress or the end-result of the project, they should be brought to the attention of the two project organisations at a higher level. Example: The project managers will discuss issues with the project partner and if necessary the issues will be brought to the attention of the project partner in the other project, and so on.
7 7(16) Page A complete list with names and roles in the project will be exchanged between the parties, see the document Project & activity plan. 2.1 List of interested parties and communication plan Communication plan finished Where do you find the resources? Who are pro and who are con the implementation? It might be an idea to make an analysis of the interested parties in the project. You can avoid conflicts beforehand or even get important input to the functionality. Do not forget the endusers, they often have important information on how the system works, or they might be negative to the implementation. An important part of the analysis is to make a plan for the communication in the project. There are two parallel organisations, and it is very important that information between you and the bank and vice versa is informative. 2.2 Project progress Activity list finished It is recommended to agree on a plan about the progress in the project. This project plan should contain the various implementation milestones, the responsible persons and the timetable. Timetable and processes Processes Collection factory Develop / Prepare format Test Prod. Information - Inform org and ensure commitment to the process Kick - off - Project scope - Structures defined - Accounts / overlay - Paym /collect. factory - Domestic cash mgt. - Implementation plan - Project team Payment factory Prepare format - Prepare format - Test Domestic CM / account structure Project management / coordination etc Test - Agree upon local requirements - Set up account structure, prepare documentation package - Startup following the local implementation plan - Combine local transaction accounts to ZBA structure - Set up local cash management structure and train staff in EB Test Prod. CM and PF finalised CF finalised Oct 2013 Oct 2013 Jan 2014 spring 2014 Milestones
8 8(16) Page The project plan will differ depending on the company and the technique involved and many other things and it are not possible to make a general project plan. Many of the tasks will be common for all but will depend on the ERP system and platform. The above figure shows an example of the timetable and processes, including the account opening processes, which are not described in this manual. Before completing the activity list, please read chapter 4 about implementation. You will find an example of the activity list in a separate document Project & activity plan Checklist Project start Project initiation, definition of project organisation, roles and responsibilities Decision on which business transactions will be exchanged, as well as the exchange of security and control Messages with each business transaction Establish test and go live dates with Nordea 3 Implementation The implementation task consists of four different subtasks: Agreements signed Communication established Formats implemented Security implemented Agreements signed Each subtask will be described to give you the possibility to estimate time, resources, and define goals for the final implementation. It is not possible to define a detailed activity list as customers differ and have different demands to the solution, but you will get a checklist based on our experience so that you can check whether you have touched all aspects in the implementation. 3.1 Agreements signed Agreements have to be signed by the persons authorised to sign on behalf of the company. The customer relationship manager at Nordea will provide you with the relevant agreements based on the decisions in the previous phase. We know from experience that this task may take some time as the persons authorised to sign for the company may not be available at the moment when the signing is needed. This is a risk for the timetable in the project, and you might prevent this at an earlier stage, if possible.
9 9(16) Page Checklist Agreements Sign the required agreements with the payment systems in the countries where the relevant Nordea Companies are located Sign the required account and other service agreements with the relevant Nordea Companies Sign a Testing Agreement and an Corporate egateway Agreement with the relevant Nordea Company 3.2 Communication Communication is about how to deliver and receive data to and from the bank. In other words, which line and protocol are we going to use? Many customers have their own way to communicate and Nordea also has its own way of communicating. If we cannot agree, we use a VANS operator to support the communication. If you decide to use a VANS operator, you are responsible for the connection between yourself and the VANS operator, and Nordea will take care of the connection between the VANS operator and Nordea. We have to co-operate about the addresses of the VANS operators. The present standard communication towards Corporate egateway is FTP/VPN, SFTP, AS2, WebServices (only for XML ISO20022) and SWIFTNet FileAct. You will find some detailed technical specification at Nordea s website Checklist Communication Order FTP/VPN, SFTP, AS2, WebServices or SWIFTNet FileAct service Install any required communication software if it is not a part of the message software Configuration of communication software Configuration of addresses Test communication software and set-up 3.3 Formats Formats implemented The format in Nordea s Corporate egateway service is EDIFACT D96.A or XML ISO20022, version 3. This chapter will give you an overall view of the formats, the flow and Message Formats. You will find detailed information about the EDIFACT and/or XML format to be used for mapping in the documents Message Implementation Guides and Message flow and use of EDIFACT / XML at Nordea s website This subtask might be the most complicated. At the investigation and decision tasks, the formats and the use of data are usually not discussed in details. At this stage you will go into detail with the format, and you will discover that small details make big difficulties.
10 10(16) Page First of all you need to be sure of how you want to use the Message Format in your own system, which fields are important and which is not. At this point the information you got from the end-user in the beginning of the project might be of great value. This subtask requires a good understand of the business and the demands from the users, and also a good understanding of the format and the content in the format. You as the customer know the demands, and we as the bank know the content in the format, so to be successful in this task, close co-operation is a must. By using the EDIFACT and/or XML format, you will have the benefit of using the same syntax for all Message Formats in Corporate egateway, but the content, however, will differ from country to country due to: What payment routines/products you use in each country What invoicing routine/system you use What payment routines/products your creditors use in each country The infrastructure and common practice of each country and each local clearinghouse The following types of Messages Formats will be supported between the Customer and Corporate egateway: From the Customer to Corporate egateway when using EDIFACT: Message name Message type EDIFACT directory Payment orders PAYMUL UN/EDIFACT D.96A directory Direct Debit Message DIRDEB UN/EDIFACT D.96A directory Authorisation Message AUTHOR UN/EDIFACT D.96A directory Message Acceptance Acknowledgement and Syntax errors Authentication CONTRL UN/EDIFACT, R.1186 AUTACK UN/ECE/TRADE/WP.4/R.1245 and R Adapted to the Recommended Practice - SJWG From the Customer to Corporate egateway when using XML ISO20022: Message name Message type XML ISO20022 Payment orders pain.001 CustomerCreditTransferInitiation Message (pain ). See an example of the use and Message flow of these Message Formats in the scenarios above. For a more detailed description, see the documentation Functional specification for each service, Message flow and use of EDIFACT / XML and Message implementation guides which all can be found on Nordea s website Before starting the mapping, a meeting between the programmers and Nordea should be held to explain the format and the differences in each country.
11 11(16) Page Checklist Application system interface Investigation of information requirements to Nordea. Is it possible to deliver all mandatory information from the internal application system? Investigation of return information from Nordea. How can we process the status information, bank statements etc from Nordea into our system? How can we achieve automated reconciliation? What set-up and modifications need to be made to our system in order to achieve the above? What internal controls do we need to apply? Message software Install Message software, if not already in place Create a test environment and prepare a production environment Create conversion programs for selected Message Formats Test outgoing Message Formats (test data can also be exchanged via mail for initial tests of incoming Message Formats before the communication is working) 3.4 Security Security implemented In order to prevent attempted fraud, it is important for the participants to make sure that the message formats are valid instructions to the bank. This means ensuring that the instruction is made by a valid party, who cannot subsequently deny having sent it, and that the instruction is not changed or manipulated by any other party during the transfer. To ensure this you should cover the transactions by Integrity, Origin Authentication, and Nonrepudiation of origin techniques. The Secure Authentication and Acknowledgement Messages AUTACK or is used to give origin authentication for EDIFACT Messages. In addition Nordea can offer PGP (Pretty Good Privacy) as a security method towards Corporate egateway for both EDIFACT and XML ISO20022 users.
12 12(16) Page Validation of sequence integrity (assuming a system of sequentially numbering messages is used and is covered by authentication). Non-repudiation of origin. For details, please see the document Security and communication description, which can be found on Nordea s website Corporate egateway follows the recommendations from UN/CEFACT regarding security when using EDIFACT and therefore supports AUTACK as a security message for EDIFACT Messages sent by you to Corporate egateway. Nordea does not as standard use security methods, such as AUTACK, in EDIFACT Messages sent from Corporate egateway to you. In addition Corporate egateway offers PGP (Pretty Good Privacy) for both EDIFACT and XML ISO20022 users. This security method may be used both from Nordea as well as from our customers. For XML ISO20022 users, Nordea also offers WebServices, using PKI as security method. It is assumed that normal professional standards of internal security are in operation, in particular covering access and modification of security keys, and their use in authorising the electronic transmission of transactions. The function of the security described here is simply to authenticate data while it is in transit, and a single signature is adequate. This would most probably be an automated signature. Nordea's policy concerning AUTACK (or PGP and/or PKI for WebServices) is not to recommend or provide any software. We will, however, upon request inform you about relevant software. The authentication is implemented in the following steps: Calculation of the hashed value of the interchange The hash value is then used as input to calculate the digital signature, i.e. it is encrypted under the originator s private key The digital signature is put into the AUTACK (or PGP and/or PKI for WebServices) If necessary, a second, or more, authentication(s) can be made by another signatory. The hash value is calculated again (to allow detection of changes to the data between signatures) and the Signature may be computed using a second, or more, private key(s) and put into the AUTACK to provide a double, or more, key(s). To use several signatures may form a personalised authentication/authorisation process in order for you to identify (authorise) individual persons in your company. The recipient will check that the received interchange matches the hash value extracted from the sender s digital signature, and this verifies both the validity of the content and the origin. The ordering party is responsible for assigning a unique customer reference to each Message. Corporate egateway may detect duplicate Messages immediately after acceptance and before booking. The reference number of accepted Messages is stored in Nordea for a period
13 13(16) Page of 90 days. Duplicate messages received after this period will be processed as normal messages. For information on the security messages PGP or PKI for WebServices, please contact your local cash manager adviser Checklist Security Purchase security software that handles digital signatures, if none exists Install security software and investigate interface to Message software creating AUTACK, PGP (or PKI for WebServices) Messages Investigate exchange and management of keys and/or certificates 4 Test TEST Tests are a project of its own, and are not described in detail in this manual. 4.1 How are tests performed in Corporate egateway? The test period in Nordea is mainly divided into two steps; 1. Format test Part 1. The Nordea Test manager will do a number of format test cases based on the services and payment types needed by you. The format testing is a very basic testing of the format itself and normally this part doesn t involve any from the business side. 2. Functional test Part 2. Functional test cases will also be created by the test manager on the basis of the same criteria as for Part 1. The Functional testing is aimed to replicate an end-to-end scenario at the customers side and therefore it normally involves also the business side. In some cases it might even be possible to pass the Functional test cases on to an in-country Nordea test environment. Before go-live we do always suggest our customers to do a Production Verification test: 3. Production Verification test Part 3. These tests will be performed in Nordea s production environment. No test cases are created by Nordea s test manager, but can be done jointly with you, if wanted. For this purpose it is recommended to open two new accounts in each Nordea Company, and send a very limited number of payments carrying small amounts between these accounts. The project team will monitor these payments closely together with you. It is, however, important to understand that Nordea cannot take any responsibility for these types of payments, since they are booked automatically in Nordea s production environment. Note: Please note that both the Corporate egateway Agreement and the Security keys must be in place before performing this kind of tests. After successfully having performed the Production Verification test you are now ready to go into production. However, Nordea strongly recommends that new Security Keys are first sent to Nordea s Security department. Outside consultants and/or other internal staff in the
14 14(16) Page company not related to the normal day-to-day business have often participated in the above test scenarios, and therefore this is necessary to prevent any unauthorised access when in production. 4.2 What can be tested? For information about what kind of Messages that can be tested in each local Nordea Company through Corporate egateway please refer to either your cash management adviser or technical adviser in Nordea. 4.3 Test accounts to be used For information about which test accounts to use please through Corporate egateway please refer to either your cash management adviser or technical adviser in Nordea. 4.4 Security and/or Authorisation Keys for the test period Test period: The responsible project manager, technical adviser or test manager will inform Nordea Bank AB s Security Department about any new customer s name, contact persons, test plans etc. As soon as you are ready to start testing your preferred security solution, the test period can start. The purpose of these tests is to ensure that you can create the relevant Message Formats for each service used in each chosen country. It is also aimed at giving you the possibility of getting familiar with and adopts the different types of Message Formats that Corporate egateway provides. Nordea Bank AB s security department will send an to Nordea s responsible project manager, technical adviser or test manager, when the public test keys have been installed. Nordea s project manager or test manager will then inform you that you can start testing messages with your preferred security solution. Before going into full production, new security keys must be sent to Nordea s Security Department. 4.5 Go live and Service Support When the test period has finished, and you have signed and accepted the performed tests, the time has come to go live. It is recommended to go live with one country at a time and with small volumes in order to see that the service is acting and performing as expected but also to enable you to react correctly to and understand the Message Formats sent by Corporate egateway. During the first week of production the project management, test manager and Corporate egateway Service Support will have full attention to the project and alert routines will be in place in case any unexpected errors should occur but also to help and support in any situation related to Corporate egateway.
15 15(16) Page 4.6 Security and/or Authorisation Keys for production Before you can go live with Corporate egateway, new security keys have to be sent to the security department in Nordea Bank AB (publ). To do this, certain requirements have to be fulfilled, all of which can be read in the document. The Corporate egateway Agreement has to be signed together with Schedule 3 (Authorisation document). Guideline for support including Contact List has to be filled in by you, stating the persons authorised to create and send new Security/ Authorisation Keys to Nordea Bank AB s Security Department, which also include the authority to block any payment services within Corporate egateway, if such action will be required. 4.7 Back-up systems Things might go wrong. It is a fact that sometimes the lines are down, damaged by accident, or whatever your fantasy can imagine. The keys are invalid, your ERP systems experience major break downs, lots of things that put you in the situation - You are not able to deliver your Messages to the bank - or - you can not receive data from the Corporate egateway. On the basis of the solution you have implemented you are recommended to think about an alternative solution for the situation mentioned above, and an emergency plan has to be documented. Discuss the alternatives with the project manager in Nordea, and find the back-up system you need or a procedure for emergency cases. 4.8 Service Support Guideline for support including Contact List Situations may occur when it is necessary to re-transmit one or more Messages and a standard solution is therefore needed for handling re-transmissions. In this document cancellation routines describes in detail how you can achieve this service through our Corporate egateway Service Support. For this purpose it is important that authorised persons at your company sign Appendix 3 to the Corporate egateway Agreement, to ensure a correct processing by Nordea. You will also find information on cover control routine, security related issues etc as well as opening hours and other contact information to Nordea s Corporate egateway s Service Support Checklist Go live Create and document routines for operation and error handling Appoint contact persons for questions and for error handling Create and document routines for emergency cases
16 16(16) Page 5 Documents to be read in relation to Corporate egateway There are a number of documents for Corporate egateway that you should read in order to ease the implementation and to get a true understanding of the Corporate egateway services and its Message Formats. For implementation purposes, the following documents are recommended: Nordea s interpretation of how a test procedure or project in Corporate egateway may be performed, which can be found within the Testing Agreement for Corporate egateway Project & activity plan For descriptions, guides and other specifications, please us the following documents: Main product description Message implementation guides Functional Specifications (for each relevant service) Message flow and use of EDIFACT / XML Guideline for Support including Contact List
Corporate Supports a centralised payment and collection factory Corporate is Nordea s file based mass payment service for customers demanding one point of entry for bulk payments and collections in the
Corporate Supports a centralised payment and collection factory Corporate is Nordea s file based mass payment service for customers demanding one point of entry for bulk payments and collections in the
Message flow and use of EDIFACT Corporate egateway Table of contents 1 PURPOSE OF THIS GUIDE... 1 2 INTRODUCTION... 1 2.1 THE EDIFACT MESSAGE STRUCTURE... 2 2.2 SEGMENT TABLE NOTATION... 3 3 IDENTIFICATION
Message flow and use of XML ISO20022 Messages Corporate egateway Table of contents 1 PURPOSE OF THIS GUIDE... 1 2 INTRODUCTION... 1 2.1 THE XML ISO20022 MESSAGE STRUCTURE... 2 3 PROCESS FLOW AND VERIFICATION
Secure Envelope specification for Corporate Access File Transfer 2/13/2015 Version 1.0.3 This document defines how a file (e.g. a payment file) which will be sent to the bank is digitally signed by the
CEN/WS einvoicing Phase 3 Date: 2011-11 CEN Workshop AgreementTC WI Secretariat: NEN Code of Practice on Electronic Invoicing in the EU Status: for public review (23 November 2011-23 January 2012) ICS:
EDI AGREEMENT This Electronic Data Interchange (EDI) Agreement is concluded by and between: And hereinafter referred to as 'the parties', Article 1: Object and scope 1.1. The 'EDI Agreement', hereinafter
R E A D S O F T W H I T E P A P E R E-invoices What they are. Different types. Best practices for implementation. This whitepaper describes different types of e-invoices, discusses what the differences
Welcome Making it possible Welcome to Nordea s webinar for vendors SEPA end date is approaching with increasing pace (October 2016) Follow up from the webinar in December Corporate customers are depending
Global Headquarters 90 Fetter Lane London EC4A 1EN Tel: +44 (0) 870 165 7410 Fax: +44 (0) 207 240 2696 OB10 - Digital Signing and Verification www.ob10.com Version 2.4 March 2013 Summary In order to comply
Service Partners SWIFTReady for Corporates Cash Management Label Criteria 2012 This document explains the business criteria needed to obtain the SWIFTReady for Corporates Cash Management label, aimed at
A Control Framework for e-invoicing White Paper by TWIST Dematerialisation of paper invoices and purchase orders may unleash greater efficiencies and cost savings in the order to pay process. Led by Steven
COMMUNICATING ELECTRONICALLY WITH CUSTOMS This fact sheet deals with communicating electronically with Customs via the Integrated Cargo System (ICS). The main elements covered by this fact sheet are: communication
Host - to - Host Automated Solution Documents Details Author NACH Technology Published Date 28/08/2014 Version V 1.0 Total Page number Document classification Public Document History Date Version Change
Service Partner Programme SWIFT Certified Application for Corporates - Trade and Supply Chain Finance Label Criteria 2016 This document explains the business criteria required to obtain the SWIFT Certified
Terms and Conditions for Remote Data Transmission (Status 31 October 2009) 1. Scope of services (1) The Bank is available to its Customers (account holders) for remote transmission of data by electronic
August 2013 EMA/264709/2013 EMA esignature capabilities: frequently asked questions relating to practical and technical aspects of the implementation This question and answer document aims to address the
SMS (txt) appointment reminders SMS (txt) messages are able to be automatically sent to patients to remind them of their forthcoming appointments. Being mindful of patient privacy related issues and the
Albany epay Intelli gent Payments Management Working in Partnership Albany works closely with relevant industry bodies to ensure high quality solutions are developed that directly meet the ongoing needs
SESSION 8 COMPUTER ASSISTED AUDIT TECHNIQUE Learning objective: explain the use of computer assisted audit techniques in the context of an audit discuss and provide relevant examples of the use of test
EDI ŠABATA Implementation guideline for Electronic data interchange (version 1.0) 1/5 www.sabata.cz Version history Ver. Date Description Author Reviewer 1.0 2016-04-18 First release R.Doležal, J. Škrobák
ADSS Server is a multi-function server providing digital signature creation and signature verification services, as well as supporting other infrastructure services including Time Stamp Authority (TSA)
Presentation of the ICCS Platform for the international communication of civil-status data by electronic means Introduction The International Commission on Civil Status (ICCS) is an international intergovernmental
GXS EDI Services In-Network Translation User s Guide GC34-3282-02 Third Edition (November 2005) This book replaces GC34-3282-01. Copyright GXS, Inc. 1998, 2005. All rights reserved. Government Users Restricted
Using SWIFTNet to communicate with the Deriv/SERV system at DTCC User Guide & Implementation Guidelines for using the Transaction Delivery Agent (TDA) 3.0 Version 2.0 August 2009 Deriv/SERV through SWIFTNet
SEPA Extra Payment news pg. 2 pg. 6 pg.8 pg. 20 SEPA harmonises payments The account number format when SEPA is valid SEPA will cause changes to material transfer services Is your company ready for SEPA?
ELECTRONIC SIGNATURES FACTSHEET Electronic signatures mean that you can exchange information with others electronically and securely safe in the knowledge that everyone is who they claim to be and that
1 SMDG-Interchange EDI - Understanding This draft is the result of work carried out by a SMDG-Subgroup. It was set up mainly on TEDIS drafts (May 1991/January 1994) but ideas and comments of EDI Council
Service Partner Programme SWIFT Certified Application - Exceptions and Investigations Label Criteria 2016 This document explains the criteria required to obtain the SWIFT Certified Application - Exceptions
PAYE Online for Employers Electronic Data Interchange (EDI) EB2 (PAYE) 1. Glossary 2. Introduction 3. Background 3.1 What is filing digitally? 4. EDI 4.1 What is EDI? 4.2 Who can use EDI? 5. Benefits 5.1
Business 360 Online - Product concepts and features Version November 2014 Business 360 Online from Software Innovation is a cloud-based tool for information management. It helps you to work smarter with
Business-to-Business EIPP: Presentment Models and Payment Options Part Two: Payment Options Contact: Director, Electronic Billing and Payment NACHA The Electronic Payments Association 13665 Dulles Technology
Net Solutions WEB-EDI Solution Documentation NET SOLUTIONS PAGE 1 OF 10 Table of Contents 1 INTRODUCTION 3 2 BUSINESS CONTEXT 4 2.1 GENERAL 4 2.2 EDI IMPLEMENTATION DIFFICULTIES 4 2.3 NET SOLUTIONS WEB-EDI
HIPAA TRANSACTION 837 INSTITUTIONAL STANDARD COMPANION GUIDE Refers to the Implementation Guides Based on X12 version 004010 A1 and version 005010 Companion Guide Version Number: 1.3 January 29, 2014 TABLE
Guidelines and instructions on security for electronic data interchange (EDI) English translation 2011-06-23 based on Swedish version 2.0 This is an unofficial translation. In case of any discrepancies
IT Cluster Vienna Cloud Computing Group Publisher: Paul Meinl Check list for the SaaS contract Check list for the contract negotiation This check list is intended for simpler cases of SaaS contract negotiations.
Guide on EDI automation and use of VAN services Copyright 2008-2009 Etasoft Inc. Main website http://www.etasoft.com Extreme Processing website http://www.xtranslator.com Basic Requirements...2 Software
BEYOND the INITIAL CONNECTION: HOW TO TRANSFORM YOUR B2B EXCHANGE 1 1EDI Source: BEYOND THE INITIAL CONNECTION WHAT THE CHANGING B2B EXCHANGE ENVIRONMENT MEANS TO YOU. For anyone in charge of automating
Webmail User Manual Table of Contents Chapter 1 INTRODUCTION TO MAILENABLE SOFTWARE... 3 MailEnable Webmail Introduction MailEnable Requirements and Getting Started Chapter 2 MAILENABLE KEY FEATURES OVERVIEW...
DigitalPersona Privacy Manager Pro DigitalPersona Privacy Manager Pro is a centrally-managed secure communication solution for businesses. It allows sensitive documents and communications to remain private,
BUSINESS ONLINE BANKING AGREEMENT This Business Online Banking Agreement ("Agreement") establishes the terms and conditions for Business Online Banking Services ( Service(s) ) provided by Mechanics Bank
Introduction to Online Payment Processing and PayPal Payment Solutions PayPal Helps Bring You New Customers Drivers of Consumer Demand for PayPal Opportunities for Merchants PayPal is: Secure Simple Fast
Service Partner Programme SWIFT Certified Application - Trade Finance This document explains the business criteria required to obtain the SWIFT Certified Application - Trade Finance 2016 label, aimed at
Payment Systems for E-Commerce Shengyu Jin 4/27/2005 Reference Papers 1. Research on electronic payment model,2004 2. An analysis and comparison of different types of electronic payment systems 2001 3.
Data Exchange and Protocol Process Flows for Electric Deregulation in The State of New Jersey Prepared by: The Consumer Process Working Groups July 17, 2000 Version 1.2 Table of Contents Table of Contents...
UK ATC Malcolm Stewart Royal Observatory Edinburgh 20 December 2001 Computing User Note CUN 23.1 Digitally Signing Acrobat PDF Files Contents 1. Introduction... 1 2. Acronyms... 1 3. Prerequisites... 2
User Manual Version 2.7 October 2012 Contents 1 To Access Shell Card Online e-invoicing Service... 3 1.1 How to access e-invocing service via Shell Card Online... 3 1.2 What to do if you forget your password...
AP Automation Best Practices and Trends Oracle E-Business Suite October 17, 2012 Agenda The challenges of efficiently processing invoices Technology Evolution Invoice Capture ERP Integration Oracle EBS
Payius GoLive Checklist Page 2 Table of Contents 1 Scope...3 2 Testing Complete?...3 3 Merchant account and legalities...3 4 Time to GoLive?...4 5 How the GoLive process works...4 6 Going live Accounting
Electronic signatures on demand White Paper July 2014 1. Management Summary... 3 2. Basics of electronic signature... 4 2.1 Electronic documents and signatures... 4 2.2 Electronic signature... 4 2.3 Standards
Digital delivery A PRESENTATION ON BASIC PRINCIPLES OF DIGITAL SIGNATURE FOR FDOT PROJECT DELIVERY Digital Delivery at FDOT Why the Change? Acquisition and Management of a Digital Certificate The Digital
FTP-Stream Data Sheet Problem FTP-Stream solves four demanding business challenges: Global distribution of files any size. File transfer to / from China which is notoriously challenging. Document control
WHITE PAPER ON CFDI I N D E X 1. What is the CFDI? 2. How does it work? 3. Who has to issue CFDIs? 4. What are the benefits of CFDI? 5. What is the difference between CFD and CFDI? 6. Steps to follow to
IBM i Security Digital Certificate Manager 7.1 IBM i Security Digital Certificate Manager 7.1 Note Before using this information and the product it supports, be sure to read the information in Notices,
e-invoicing Online Billing For any assistance please contact Email: Tel: Contents Welcome to Online Billing 3 Registering for Online Billing 4 einvoicing and epayment 10 Logging in 11 Accessing your new
Supply Chain Finance WinFinance Customer User Guide Westpac Banking Corporation 2009 This document is copyright protected. Apart from any fair dealing for the purpose of private study, research criticism
SAP HANA 1.0 SAP BusinessObjects Business Intelligence platform 4.0 Predictive Analysis 1.0 August 2013 English Quick Guide to Implementing SAP Predictive Analytics Content Adoption rapiddeployment solution
Managed Communications JPMorgan - Global Client Access Managed Internet (EC Gateway) Managed Communications Overview JPMorgan offers a variety of electronic communications services that are reliable and
480.84 en (pf.ch/dok.pf) 10.2015 PF Manual PostFinance ISO messages for banks [pacs messages] Customer service Enquiries concerning service ISO 20022 for banks PostFinance Ltd Customer Service Banks Mingerstrasse
Doc: EPC109-08 31 March 2009 (Version 1.5 approved) EPC e-mandates e-operating Model High Level Definition Abstract This is the High-level Definition for the development of an e- Operating Model for the
FSpec401 FSpec401 Royal Mail Customer Solutions Royal Mail Business Integration Gateway Specification - XB60 The FSpec401 document details, for customers, the various methods of connecting to Royal Mail
Chapter 10 e-payments AIS 360Prentice Hall, 2003 1 Learning Objectives Understand the crucial factors determining the success of e-payment methods Describe the key elements in securing an e-payment Discuss
UN/CEFACT United Nations Centre for Trade Facilitation and Electronic Business TBG International Trade & Business Processes Group Team 5 Finance Domain Maintenance Task Force for the use in all UN/EDIFACT
OSCI Transport 1.2 Specification Status: FINAL OSCI Leitstelle Bremen/Germany, June 2002 OSCI Transport 1.2 2 The following companies and institutions have been involved in the creation of this specification:
JOB DESCRIPTION Job Title: Division: Department/Region/Section: Location: Reports to: Responsible for: Grade: Email Marketing Officer Marketing and Communications Digital Media Southwater, HQ Digital Marketing
Fast Settlement Service Information Paper 3 Requirements Phase April 2014 Fast Payments SPRINT Program Glossary Below is a list of selected terms used in this document. Relevant definitions have been adopted
Schools purchasing card Department guidelines and procedures Published by the Communications Division for Financial Services Division Department of Education and Training Melbourne January 2015 State of