Try it now Login

Message type

UN/EDIFACT AUTACK

AUTACK is a UN/EDIFACT message published in 1 directory version of the standard. A written summary of its purpose has not been added to this library yet; the segment structure for each version is complete and linked below.

Open the SERVICE_V4 AUTACK specification
Message
AUTACK
Directory versions
1
Latest
SERVICE_V4

Sending and receiving

Exchange AUTACK with your trading partners

The specification tells you what a valid AUTACK looks like. Sending and receiving one means mapping it to the system that holds the data, agreeing the format with each partner, and handling the messages that come back when something is rejected. XEDI does the mapping, validation and transport.

Browse integrations Connect AUTACK to your ERP, WMS or accounting system Find your trading partner Document requirements by partner Talk to an EDI specialist Scope a AUTACK flow with us

Specifications

AUTACK in every directory version

A trading partner names both the message and the directory, for example SERVICE_V4 AUTACK, because the segments differ between versions. Open the one your partner specified.

1 directory version

Related messages

Messages in the AUT set

UN/EDIFACT groups related documents under a shared three-letter stem. These usually appear together in one trading flow.

AUTHOR Authorization message for communication access or permissions.

Frequently asked questions

Which directory version of AUTACK do I need?

The one your trading partner specifies. AUTACK is published in 1 directory version and the segment detail differs between them, so a mapping built for one version is not automatically valid for another.

How do I send a AUTACK message?

Map the data from the system that holds it into the segment structure the agreed directory version defines, then transport it by the route the partner uses, commonly AS2 or SFTP. XEDI handles the mapping, validation and transport, and surfaces the acknowledgements and errors that come back.

Sources and further reading