XML Format Reference

Version: 2.0 — June 2026
Format: Proprietary XML, aligned with GS1 XML conventions

EDIconnect uses an XML format with a common structure for all messages. This page describes the general rules for structure, encoding, and validation.

Document Types

The DocumentType field in the message header identifies the document type. The value determines how the message is processed in the system:

Message	DocumentType	Description
ORDERS	`OR`	Purchase Order
ORDRSP	`OA`	Order Confirmation (accepted)
ORDRSP	`OR`	Order Response with changes
DESADV	`DL`	Despatch Advice
INVOIC	`FV`	Fiscal Invoice
INVOIC	`NC`	Credit Note
RECADV	`NIR`	Goods Receipt Note
RECADV	`R`	Goods Return
RECADV	`70E`	Seizure (damage/quarantine)
PRICAT	`PC`	Price Catalogue

The field is specified in the <DocumentType> element within the <Header> section of the message:

<Header>
  <DocumentType>FV</DocumentType>
  <DocumentNumber>FACT2024001</DocumentNumber>
  <DocumentDate>2024-03-15</DocumentDate>
  ...
</Header>

Encoding & Declaration

<?xml version="1.0" encoding="UTF-8"?>

All messages must use UTF-8 encoding. The XML declaration is mandatory.

General Structure

<?xml version="1.0" encoding="UTF-8"?>
<Message>
  <Version>2.0</Version>
  <Documents>
    <{MessageType}>
      <Header>
        <DocumentType>{type}</DocumentType>
        <DocumentNumber>{number}</DocumentNumber>
        <DocumentDate>{date}</DocumentDate>
        ...
      </Header>
      <{Parties}>
        ...
      </{Parties}>
      <Lines>
        <Line>...</Line>
      </Lines>
      <Summary>
        ...
      </Summary>
    </{MessageType}>
  </Documents>
</Message>

The XML version (<Version>) varies per message: all messages use v2.0.

Namespaces

Message	Namespace
ORDERS	`urn:azuvio:ediconnect:orders:v1`
DESADV	`urn:azuvio:ediconnect:desadv:v1`
INVOIC	`urn:azuvio:ediconnect:invoic:v1`
RECADV	`urn:azuvio:ediconnect:recadv:v1`

Date and Time Formats

Type	Format	Example
Date	`YYYY-MM-DD`	`2024-03-15`
DateTime	`YYYY-MM-DDTHH:MM:SS`	`2024-03-15T14:30:00`
DateTime with TZ	ISO 8601	`2024-03-15T14:30:00+02:00`

Numeric Format

Decimal separator: . (period, not comma)
No thousands separators
Quantities: up to 3 decimal places
Prices: up to 4 decimal places
Monetary values: up to 2 decimal places

GLN (Global Location Number)

GLNs are 13-digit numeric strings. Always send as a string, with leading zeros preserved:

<BuyerGLN>0594123456789</BuyerGLN>  <!-- correct -->
<BuyerGLN>594123456789</BuyerGLN>   <!-- wrong — 12 digits -->

Warning

GLN and EAN must always be sent as strings, not as integers. A GLN such as 0594123456789 becomes 594123456789 if treated as a long — invalidating the partner identifier.

EAN / GTIN

Product codes follow GTIN-13 (EAN-13): 13-digit numeric strings.

Unit of Measure Codes

EDIconnect uses UN/ECE Recommendation 20 codes:

Code	Description
`PCE`	Piece
`KGM`	Kilogram
`LTR`	Litre
`CTN`	Carton
`PLT`	Pallet
`MTR`	Metre
`SET`	Set

Currency Codes

Three-letter ISO 4217 codes: RON, EUR, USD, GBP.

Message Size Limits

Parameter	Limit
Maximum file size	10 MB
Maximum lines per message	9,999
Maximum packages per DESADV	999
Maximum items per PRICAT	50,000

XSD Validation

Validate against the corresponding XSD schema before sending:

Message	XSD Schema
ORDERS	`Azuvio-CRMconnect-EDIconnect-ORDERS-v2.0.xsd`
DESADV	`Azuvio-CRMconnect-EDIconnect-DESADV-v2.0.xsd`
RECADV	`Azuvio-CRMconnect-EDIconnect-RECADV-v2.0.xsd`
INVOIC	`Azuvio-CRMconnect-EDIconnect-INVOIC-v2.0.xsd`

HTTP transport returns 400 Bad Request with an error body if validation fails.

HTTP Headers (REST transport)

Content-Type: application/xml; charset=UTF-8
Accept: application/xml
Authorization: Bearer {token}
X-EDI-SenderGLN: {your GLN}
X-EDI-ReceiverGLN: {partner GLN}
X-EDI-MessageType: ORDERS
X-EDI-DocumentType: OR

The X-EDI-DocumentType header must match the <DocumentType> field in the message body.