Skip to content
Illustration: Structured documents and network cables representing EDI data exchange

wawiHEROES · JTL services

EDI

On this page 3 topics

How the processes fit together

Documents connect businesses.

Purchase orders, advance shipping notices and invoices should not have to be retyped. An EDI integration converts agreed business documents into structured data for your systems and trading partners.

  1. 01Receive a message
  2. 02Map fields
  3. 03Check processing

Planning overview · the specific workflow will be tailored to your project.

EDI Overview

01

Structured Business Documents Instead of Manual Work

EDI stands for Electronic Data Interchange: the structured electronic exchange of business documents between companies. Purchase orders, dispatch advices and invoices are transmitted according to agreed rules rather than entered manually again.

Illustration: organized business documents with data connections to a server
Structured Business Documents Instead of Manual WorkIllustration

Formats & Transmission

02

Message Types & Data Formats

Formate wie EDIFACT beschreiben die Struktur von Nachrichten. ORDERS steht für Bestellungen, DESADV für Lieferavise und INVOIC für Rechnungen. Welcher Standard und welches Partnerprofil erforderlich sind, bestimmt die konkrete Geschäftsbeziehung. Auch VDA, X12 oder openTRANS können je nach Partner in Frage kommen; ihr Einsatz wird für jede Anbindung einzeln geprüft.

  • Purchase orders: products, quantities and delivery information

  • Dispatch advices: announced deliveries and packing information

  • Invoices: agreed document and line-item data

03

Mapping & Transmission

A format alone does not establish a connection. Fields, identifiers, mandatory information and the transmission method are agreed with the messaging partner. Whether SFTP, AS2 or another connection is used depends on that partner's requirements and the solution in use.

Checks & Invoices

04

Monitoring Processing

Automation requires traceable checks. Missing product mappings, invalid mandatory fields and rejected messages must be detected and addressed. Test messages and clearly defined responsibilities are therefore part of the implementation.

05

Distinguishing EDI from Electronic Invoicing

XRechnung and ZUGFeRD are electronic invoice formats. A complete EDI integration can also cover purchase orders and dispatch advices. Format support, legal requirements and integration with your accounting system are coordinated separately.

Terms in context
  1. 01EDI
  2. 02Orders

Schematic overview of this section · not a software screenshot or an indication of the direction of a technical connection.

Before implementation

What matters for your project.

  • Agree on the message type and partner profile
  • Test transmission, required fields and error scenarios
  • Do not equate EDI with a single API
JTL EDI · Vendor information

Features and terms depend on the version, edition and extensions used.

Your next step

Let's discuss your requirements.

Contact

Let’s discuss your project.

Free initial consultation on JTL-Wawi, JTL-Shop, JTL-WMS and hosting.