Electronic Data Interchange with KNV



Similar documents
E-Supplier. Information for Siemens Vendors - Exchange of business transactions via EDI.

1 IT Service Delivery

EDI Definitions, Standards, Messaging

Basic principles of labelling and Electronic Data Interchange - Abridged version -

EDI FAQ Document ABOUT THIS DOCUMENT EDI. This document is a repository of frequently asked questions relating to: 1. EDI. 2. emessaging Standards

FTP FILENAMING STANDARD Issue 4

METRO Group data synchronization strategy master data quality is the key

EDI-guideline Electronic delivery note

B2BE Transaction Delivery Network

Lower costs, greater flexibility. Electronic Data Interchange (EDI): Optimisation of business processes through data exchange

S.2.2 CHARACTER SETS AND SERVICE STRING ADVICE: THE UNA SEGMENT

Art des Dokuments Supplier Logistics Manual EDI in Procurement

Media Saturn EDI Application Documentation

How To Use The Gs1 Databar Expanded

e-invoicing Supplier On-boarding Pack

Procure to Pay Process Four Requisition Types. Procure to Pay Process Four Payment Types

VAT invoice requirements in Germany

3. Phase at customer in Visma Proceedo. Integration Request. 1 Introduction COMPLETED BY CUSTOMER: 2 Customer information.

OB10 - Digital Signing and Verification

EDI ŠABATA. Implementation guideline for Electronic data interchange (version 1.0)

BAAN IVb and IVc. EDI User Guide

Valves, controls + systems Optimisation of logistics and business processes

Xerox EDI Direct Claims Gateway Communication Document for ASC X12N 837 Health Care Claim Transaction Submission

Efficient Data Sharing in Healthcare

EDI Collaboration: Increase your Business Efficiency through Technology Benefits

EDI On-Line Purchasing

Process. CS.Line. B2B communications services. 100% EDI integration of your business partners.

120: All You Need to Know About Implementing EDI Eduardo Valdes, Vilore Foods, Co., Inc. Bekki Windsperger, Best Buy Co., Inc.

ecommerce Overview Date: March 2015 Author: Jennifer Yi & Will Cartwright

EDI specifications. between. BLANCO GmbH + Co KG referred to in the following as BLANCO. and its business partners (suppliers)

Ariba SN Getting Started with Ariba EDI. April 2004

T.8 USING THE INVOICE FOR BILLING AND FOR DEBIT AND CREDIT NOTES

Best practice Bundle products in ONIX 2.1 and EANCOM

CA-EDI. Certification of the EDI Interface

Please read information below to determine if you need to provide pricing information on the NPC.

E invoicing: Ready for Prime Time

HIPAA TRANSACTION 837 INSTITUTIONAL STANDARD COMPANION GUIDE

TestRail Cloud Terms of Service

The role of E-Invoicing standards in France. Conference EXPP SUMMIT September 25 th

GPX Business CLOUD. Electronic Data Interchange.

International Compliance

997 Functional Acknowledgment

EPIC. Enterprise Process Integration Controller. Creating 100% Reliable Business Systems. ebusiness Solutions

WinSCP for Windows: Using SFTP to upload files to a server

TERMS & CONDITIONS of SERVICE for MSKnote. Refers to MSKnote Limited. Refers to you or your organisation

Sanford Health Plan. Electronic Remittance Advice 835 Transaction Companion Guide Trading Partner Information

EDI Cost Savings Report

Dear Valued Supplier, Re: Motorola Solutions is phasing out paper invoices AND paper checks!

Code of Practice on Electronic Invoicing in Europe

Code of Practice on Electronic Invoicing in Europe

Implementation of EDI in METRO Group Russia

How To Write A Paiso Certification Test

Adoption of GS1 and PEPPOL Standards:

Product Information CDI Premium EDI module

In-Network Translation User s Guide

EDI and IDOC Implementation for SAP Sales Order Processing Peter Sammons, IT Architect, Courier Corporation

Web Application. Web Application. Web-EDI - Logistic Data Exchange Tailor-Made from the Web

Kommerskollegium 2010:4. e-invoicing in cross-border trade

Accessing the FTP Server - User Manual

VARONIS CASE STUDY. Philip Morris International (PMI)

Molina Medicaid Solutions EDI Unit sftp Companion Guide 9/5/2012

Supply Chain Merchandise Logistics E-Commerce Operational Processes & Standards

OCAN - Ontario Common Assessment of Need

EDI Implementation Guidelines for Library Book Supply Changes, since issue 1.2

TEAL: Transparent Archiving Library

Dear Valued AllianceData Supplier, Re: AllianceData is introducing e-invoicing

System to System Interface Guide

E-logistics platform for the support of small and medium seized enterprises

LPI Approved Training Partner (LPI ATP) Program Agreement

Code of Practice on Electronic Invoicing in the EU

Using Internet or Windows Explorer to Upload Your Site

Supplier EDI Questionnaire

How to Order and Install Odette Certificates. Odette CA Help File and User Manual

Data Transmission Method Selection Monday, October 5, 2015

EDI 101 White Paper What every company needs to know about EDI

ELECTRONIC DATA INTERCHANGE (EDI) TRADING PARTNER AGREEMENT THIS ELECTRONIC DATA INTERCHANGE TRADING PARTNER AGREEMENT

Babelway B2B Integration Platform Documentation

Electronic Commerce. EDI with Debenhams

GS1 Newcomers to AS2. Implementation Guide. Issue 1, 23-June GS1 Newcomers to AS2 Implementation Guide

Walmart Stores, Inc. Getting Started with EDI Implementation Guideline Document version: 1.0 Published November 2011

Transmit X12 Data to AudaPro via Secure FTP

Online Banking for Business Secure FTP with SSH (Secure Shell) USER GUIDE

Bulk EDIFACT ASN MESSAGE FORMAT

Global Amazon Integration Module v1.1. Users Guide & Setup Instructions

Mercedes-Benz US International, Inc. Supplier Connection Guidelines

Automate order-invoice matching and payment with esolutions MAP at the core of your organisation s P2P processes

835 Transaction Companion Guide Healthcare Claim Payment/Advice. Version X91A1 (Addendum)

Transcription:

EDI Guidelines for suppliers Electronic Data Interchange with KNV 1

Table of contents 1. Preliminaries... page 3 2. Pre-requesites... page 3 2.1 GLN... page 3 2.2 Data transmission... page 3 2.2.1 AS2... page 4 2.2.2 FTP... page 4 2.2.3 X.400 addresses... page 4 2.2.4 SMTP (email)... page 4 2.3 Addressing in messages... page 4 3. EDI communications... page 4 4. Phases of EDI introduction... page 5 4.1 Preparation... page 5 4.2 Testing... page 5 4.2.1 Syntactic testing... page 5 4.2.2 Semantic testing... page 5 4.3 Acceptance... page 5 4.4 Go-live... page 5 5. Productive operation... page 5 5.1 INVOIC to KNV... page 5 5.2 ORDRSP to KNV... page 5 6. GLN of KNV... page 6 7. KNV Clearing Centre... page 7 8. Information... page 7 2

1. Preliminaries Electronic Data Interchange, or EDI, is the electronic exchange of business data between computer systems in a structured form. In order that the interface is successfully established between diverse systems, it is necessary to have a common language, a standard. EANCOM has risen to the fore the world over in this regard, a language that is spoken in every country and in (almost) every industry. KNV uses EANCOM for communicating orders to publishers and distributors. We expect invoices and messages from publishers and distributors to be sent to us in electronic form. In order to identify business partners, EANCOM uses Global Location Numbers (GLN). The use of the GLN is essential, particularly with invoices. This document describes the conditions, set up and testing of EDI processes and the productive operation. The communication of catalogues using ONIX will not be described here. Please request this information separately from us if required. 2. Pre-requesites EDI is only partly an IT issue; the most important conditions for the successful deployment of EDI are of an organisational nature. Of paramount importance is the reconciliation of the master data of partners and items and the harmonisation of communication processes and times. 2.1 GLN KNV uses GLNs for all addresses and locations significant for the electronic data interchange. EDI invoices from suppliers can only be processed provided the supplier (invoicer) includes its GLN in these. In Germany, GLNs are assigned by GSl- Germany; more information is available on the internet: www.gsl-germany.de or check www.gs1. org to find the national GS1 organisation in your country. 2.2 Data transmission We are able to exchange EDI communications with you in the following ways AS2 FTP (SFTP) X.400 3

2.2.1 AS2 AS2 is a specification about how to transport data securely and reliably over the Internet. The user does not depend on technical protocols for proof of audit compliance but has the MDN as proof in the form of a message. If you wish to use AS2 to exchange data with KNV please ask for our AS2 package and send yours including certificates for test and production 2.2.2 FTP On our FTP server we have set up directories to enable you to upload and download data, address: ftp.knv.de. We will provide you with your personal log-in data after you have contacted us. 2.2.3 X.400 addresses Test C=DE, A=viaT, O=Barsortiment, S=KNOBS Production C = DE, A = viat, O = KNO, S = KNO-EDI 3. EDI communications KNV utilises the following messages in accordance with EANCOM version D.96.A (1997) or D.01B MEDIA: ORDERS (orders) INVOIC (invoice) ORDRSP (purchase order response message) DESADV (dispatch advice message) We will gladly provide you with precise specifications of the following messages upon request. In these we adhere to the recommendations of the EDIfEUR and the former EANCOM working group of the business committee of the German Publishers and Booksellers Association (1996). We also support the new recommendations of GS1 Germany for EANCOM in the Media Sector. DESADV message will shortly be implemented for KNV Logistik GmbH in Erfurt. 2.3 Addressing in messages All orders for Koch, Neff & Volckmar GmbH Barsortiment are being placed by the buying department in Stuttgart. Each order includes the shipping address in Erfurt; invoicing address is always KNV Stuttgart. 4

4. Phases of EDI introduction Several phases must be completed before productive deployment of EDI is achieved; these phases are outlined below: 4.1 Preparation Definition of responsibilities on each side. Reconciliation of message types and procedures, harmonisation of master data, particularly the GLNs. Agreement of a road map with milestones for the introduction of EDI. Previous experience with suppliers has shown that it makes sense to convert the orders to EDI first, followed by INVOIC and ORDRSP. 4.2 Testing Each message to be used will be individually tested. The test phase is commenced following mutual reconciliation of the message types and specifications and completion of any development works required. A parallel operation may be agreed for a limited period. 4.2.1 Syntactic testing Then comes the syntactic test. This is where KNV tests incoming messages in the (test) EDI system solely for their formal correctness without reference to the contents. 4.2.2 Semantic testing Syntactically correct test messages will be tested at KNV by the competent operative department. In this respect it is very important, particularly in the case of EDI invoices, that real data is used. 4.3 Acceptance Following the successful completion of the tests and confirmation by the responsible technical staff of both sides. 4.4 Go-live Following acceptance. Depending on the agreement made, the exchange of paper documentation can be ceased at this point. 5. Productive operation Following the go-live, only EDI messages will usually be exchanged. The sender is then responsible for ensuring compliance with the standards verified during the testing phase, and that no syntactic or semantic errors occur. The exchange of individual messages with KNV is subject to the following conditions: 5.1 INVOIC to KNV For the introduction of the electronic invoice via EDI it will be necessary to conclude a separate agreement the Vereinbarung über den elektronischen Datenaustausch (EDI), Nachrichtentyp INVOIC mit EANCOM (EDI agreement, message type INVOIC with EANCOM). We send this to our suppliers at the appropriate time. Without this agreement it is not possible to waive the conventional paper invoice procedure 5.2 ORDRSP to KNV As is standard in the book trade, we only require ORDRSPs from suppliers for messages concerning non-deliverable items, not as order confirmations for items to be delivered immediately. Messages must always contain the reason why an item cannot be delivered immediately and must state the foreseeable delivery or publication date. 5

6. GLN of KNV Invoice to: KNV Stuttgart Koch, Neff & Volckmar GmbH Schockenriedstr. 37 70565 Stuttgart Basis GLN: 40 26725 00000 8 Department VKNR GLN 13540 4026725000008 Export 55040 4026725000022 Purchase 55030 4026725000015 Ship to: KNV Logistik Erfurt KNV Logistik GmbH Ferdinand-Jühlke-Str. 7 99095 Erfurt Basis GLN: 40 54989 00000 7 Department VKNR GLN Wholesale 31000 4054989000014 KNV Special Order Procurement 31003 4054989000038 KNV Export 31010 4054989000076 6

7. KNV Clearing Centre If you do not have your own EDI system and do not want to acquire one, the KNV Clearing Centre will nevertheless offer you the option of exchanging electronic data with all business partners in the book trade. More information on this is available from our website www.knv.de under IT, Clearing Centre or send an email to the head of our Clearing Centre, Uwe Janssen. 9 Informationen Zu EANCOM, 8. Information GLN etc.: on EANCOM, GLNs etc.: GS1-Germany GmbH Maarweg Maarweg 133133, 50825 Köln 50825 www.gs1-germany.de Köln www.gs1-germany.de Outside Germany contact the national GS1 organization in your country (http://www.gs1.org) Über On Internationale international standards Standards for the für book den trade: Buchhandel: EDItEUR EDItEUR United House 39-41 North North Road, Road, London N7 9DP, United Kingdom London, www.editeur.org N7 9DP, U.K. www.editeur.org Contact at KNV: Uwe Janssen Sales IT Head of EDI Clearing Centre clearing@knv.de www.knv.de October 2015 Legal notice: Koch, Neff & Volckmar GmbH, Clearing Centre, Schockenriedstraße 37, 70565 Stuttgart, E-mail: clearing@knv.de, Internet: www.knv.de Directors: Frank Thurmann, Oliver Voerster, Registered in Stuttgart, District Court of Stuttgart: HRB 11907, VAT ID: DE 147816562 Photography: Fotolia, Veer 7