Custom solution · EDI

EDI integration for your partners

You want to connect a trading partner to your ERP or another system. We implement the agreed messages, field mappings and transfer methods. You receive a tested connection with traceable error handling.

Enquire about EDI integration
Schematic illustrationIntegrate partner processes
ERPCustomer / source system
Recipient / target system
excodata · agreed scopeEDIFACT · openTRANS
Mapping and rules
System handover
Review and approval
Documentation

You want to connect a trading partner to your ERP or another system. We implement the agreed messages, field mappings and transfer methods. You receive a tested connection with traceable error handling.

Typical components

Source data

  • analyse messages and partner profiles

Mapping and rules

  • map EDIFACT, openTRANS, XML, CSV or other assessed formats

System handover

  • set up file transfer or an API connection

Review and approval

  • validate required fields and values

Feedback

  • handle acknowledgements, status and errors

Acceptance

  • document test cases and production handover

Clear limits of responsibility

Partner requirements, data responsibility, technical availability and error handling are assigned in advance. An integration does not automatically promise support for every message type or partner.

Fictional example

Order B-470 · Schematic message, not a format segment

Delivered – but rejected by business validation

01 · MessageSender · Business data

Order
B-470
Delivery location
L-99

02 · Technical deliveryexcodata · Agreed connection

B-470 · Delivery confirmed

In this example, confirms message receipt only. Not yet business acceptance.

03 · Business responseRecipient · Business decision

B-470 · Rejected by business validation

Delivery location L-99 is unknown to the recipient.

Return path for B-470
Recipient → excodata → sender

excodata links the response to B-470. The sender clarifies the delivery location with the recipient and corrects the source data. The message is then checked again under the agreed procedure; the business decision remains with the recipient.

Fictional case without EDIFACT or openTRANS segments. Transport confirmation, business response, correlation and retransmission must be agreed for each partner and procedure. No universal protocol support or automatic retry is promised.

Operations

Production monitoring, retry logic, support hours and changes are only part of the project if explicitly agreed. Recurring operations can be added as a managed service.

FAQ

Can a new trading partner use an existing field mapping?

We check which parts of the existing field mapping can be used for the new trading partner. We clarify differences in messages, codes and processes beforehand to determine whether connection is possible and which adaptations are needed.

Is testing with the partner included?

Partner tests can be agreed in the quote. We define scope, test cases, contacts and acceptance; only this agreed testing scope is included.

Does excodata handle monitoring?

This can be agreed separately as a managed service.

Custom solution · EDI

Define your task

Enquire about EDI integration