UN/EDIFACT
The language of business exchanges.
UN/EDIFACT defines structured messages for commercial exchanges. Each implementation specifies a version and a guide suited to the partner or sector. EANCOM is a subset of UN/EDIFACT maintained by GS1.
We examine segments, groups, qualifiers and presence rules to produce the required document.
UN/EDIFACT · UNECE ↗| Message | Document | What is it used for? |
|---|---|---|
| ORDERS | Order | Send items, quantities and order terms. |
| ORDRSP | Order response | Confirm or adjust order details. |
| DESADV | Despatch advice | Prepare receipt: contents, packages and delivery references. |
| RECADV | Receiving advice | Report the goods actually received. |
| INVOIC | Invoice / credit note | Send billing data according to the document type. |
| CONTRL | Syntax check | Return the results of checks on the interchange structure. |
XML & UBL
Structured, verifiable documents.
XML represents structured data. UBL defines business documents in XML, including invoices and credit notes. For Peppol BIS Billing 3.0, checks cover UBL syntax and the applicable business rules.
- Structural validation using XSD schemas.
- Business rule checks using Schematron where required by the profile.
- Verification of identifiers, codes, totals, taxes and rounding.
CSV · JSON · Business files
Bridge the gap with your software.
Does your software produce CSV, fixed-width files or JSON? We analyse its structure to map it to the target document.
The interface contract specifies encodings, separators, date formats, units and missing values. It helps avoid ambiguity when changes are made.
Mapping & validation
Consistency before transmission.
A file can be syntactically valid yet unusable: an unknown reference, an incorrect unit or an inconsistent total. We distinguish structural checks, business checks and recipient-specific requirements.
The standard version and the partner’s guide are agreed during scoping. Tests must cover that specific scope.