Standard · UN/EDIFACT
EDIFACT, from order to invoice.
Read, write, map and validate UN/EDIFACT interchanges in every directory version, generated from the official UN/EDIFACT directories.
UNH+1+ORDERS:D:96B'
BGM+220+4711+9'
DTM+137:20261026:102'
<BGM>
<e2>4711</e2>
</BGM>
{ "BGM": {
"doc": "4711"
} }
EDIFACT support
01
Envelope handling
UNA, UNB/UNZ and UNH/UNT read and written; counts and control references are set when phaf writes EDI.
02
Directories
Every UN/EDIFACT directory version built in, generated from the official UN/EDIFACT directories. Each partner uses the version it sends, with no conversion between versions.
03
Trade
Orders, despatch advices and invoices.
04
EDI ⇄ XML ⇄ JSON
Convert both ways and map to any target.
05
Character sets
UNOA, UNOB and UTF-8 handled and validated.
How it works
Three steps.
01
Receive
From SFTP, FTP, email or a folder.
02
Validate and map
Three-level validation, then map to your system.
03
Deliver
Into a database, an API or back to a partner as EDIFACT.
See it running with your own data.
Bring a real file, message or API. We build the flow with you in the demo.