Expertise · EDI and data exchange

Understand EDI and data exchange

EDI means exchanging business data electronically between companies. For the receiving system to use the information, its meaning, format and transfer method must align. We combine this expertise with implementation in existing systems.

Schematic illustrationElectronic data exchange
ERPCustomer / source system
Recipient / target system
excodata · agreed scopeXML · CSV · JSON
Mapping and rules
System handover
Review and approval
Documentation

EDI means exchanging business data electronically between companies. For the receiving system to use the information, its meaning, format and transfer method must align. We combine this expertise with implementation in existing systems.

What a reliable integration requires

Source data

  • clearly identified source and target systems
  • documented messages and formats

Mapping and rules

  • business mapping rules
  • security and transfer requirements

Exceptions and questions

  • defined error and retry logic

Acceptance

  • testable acceptance criteria

Responsibility

  • clear responsibility for operations and data quality

Common tasks

Source data

  • import supplier and partner data

Processing

  • map formats and field structures to one another
  • validate and transform messages
  • connect interfaces, file transfers and APIs

Exceptions and questions

  • log errors and handle them traceably
  • monitor recurring transfers

Depending on the requirements, standards such as EDIFACT, openTRANS, BMEcat, CSV, XML, JSON or API contracts may be relevant. Support is limited to the specifically assessed scope.

Example: purchasing and sales

Business documents between your systems and partners

Technical connection by excodata

Suppliers

Company to suppliers

  • Purchase order

Suppliers to company

  • Order confirmation
  • Despatch advice / shipping notice
  • Invoice
Your companyERP

Customers to company

  • Purchase order

Company to customers

  • Order confirmation
  • Despatch advice / shipping notice
  • Invoice
Customers
Example workflow: excodata connects existing systems for inbound and outbound transmission and processing of agreed business documents. Messages and transmission methods are agreed per project. Technical delivery does not mean business acceptance.

Project or managed service

The technical connection is implemented as a custom solution. Operations, monitoring and recurring data processing are agreed separately as a managed service.

FAQ

Which EDI formats and transmission methods are possible?

We discuss possible formats and transmission methods based on your business documents and systems. Before quoting, we check the specific format, message type, transmission and target system; the supported scope is agreed for each project.

Are ongoing operations included in the integration?

Operation and monitoring can be agreed additionally. They are a separate service and are not automatically part of the technical integration.

Can you process supplier files without a traditional EDI connection?

Yes, if a clearly defined process for import, field mapping and validation can be agreed.

Expertise · EDI and data exchange

Define your task