FORMATS AND OUTPUT

EDI formats and output.
A defined destination.

Prepare EDI format and output requirements around the standard, version and representation your receiving application expects.

Discuss your workflow See how it connects

Document fields connected with a citron highlight across two business records

SAME
DATA
FURTHER
GOOD

DOCUMENT / CONTEXT / CONNECTION

EDI DOCUMENTS / BUSINESS SYSTEMS / TRADING PARTNERSEDI PARSEX / BY MALTEXI

01 / THE WORK, MADE CLEAR

A format name is a starting point.

X12 and UN/EDIFACT describe families of structured business messages. JSON and XML are representations frequently used by business applications. An evaluation should specify the exact input message and destination structure rather than assuming that any document can be converted into any format.

01
Input
Identify the standard, transaction or message type, release and partner guide.
02
Interpretation
Determine the relationships and values that must be preserved.
03
Output
Describe the required representation and destination fields with an example.

02 / THE CONNECTION THAT MATTERS

Document the boundaries.

Document the boundaries.
Context	What matters	The handoff
X12 requirements	Transaction, version and partner implementation	Confirm the required coverage
EDIFACT requirements	Message type, directory release and partner rules	Confirm the required coverage
JSON or XML output	Target schema, types and required fields	Agree the implementation

Business documents arranged for an order and shipment workflow review — Make the information useful.

03 / BUILT AROUND YOUR WORK

Keep business meaning through the conversion.

A conversion that changes syntax but loses item relationships is not a useful handoff. Include repeated lines, optional references and missing values in the sample set. Confirm supported input and output formats against the actual product implementation before committing the exchange.

Start a focused conversation

A CLEARER PICTURE