Reconcile acknowledgment for an EDIFACT transaction

Anitha Abraham

Updated May 12, 2026 06:55

An acknowledgment includes details such as:

Sender and receiver identification
Control numbers
Date and time of receipt
Status code indicating the transfer outcome, which depends on the EDI standards

Acknowledgment EDIFACT sample file

UNB+UNOA:2+123456TEST:01+102096559TEST:16+071121:1334+00000000000100+CONTRL
UNH+00000000000476+CONTRL:D:97A:UN
UCI+00000000000476+102096559TEST:16+123456TEST:01+7
UCM+1+INVOIC:D:97A:UN+7
UCM+2+INVOIC:D:97A:UN+7
UCM+3+INVOIC:D:97A:UN+7
UNT+15+00000000000476
UNZ+1+00000000000100

For example, an acknowledgment is a receipt issued by the receiver (trading partner) in response to a transaction sent from integrator.io in an outbound flow. The receipt confirms to the sender (integrator.io) that their transaction was successfully delivered by an import step.

Acknowledgment reconciliation for EDIFACT file

After the EDI file is generated and validated against the file definition rules in an import,

The file is sent by integrator.io to a trading partner.
The receiving trading partner in response to the transaction sent by integrator.io asynchronously provides an acknowledgment.An acknowledgment confirms receipt of the transaction along with the delivery status.

The main purpose of acknowledgments is to reliably confirm the integrity and successful delivery of EDI transactions between trading partners via integrator.io.

Create an acknowledgment reconciliation custom flow

To understand creating an acknowledgment reconciliation custom flow, consider it in the context of 2 flows, for example:

Flow 1 – EDI flow between two trading partners: A simple EDI flow with two steps:
- Step 1: An export to get an EDI file from a trading partner (TP1).
- Step 2: An import that gets the parsed export and then generates the EDI file to send to another trading partner (TP2).
Flow 2 – Acknowledgment reconciliation custom flow: Another simple EDI flow with:
- Step 1: An export to get the acknowledgments from trading partner (TP2) in Flow 1 for successful delivery of EDI files.
- Step 2: An import to send these acknowledgments to integrator.io for reconciliation.

This article focuses on Flow 2; Flow 1 is out of scope for this article.

Flow 2 – Acknowledgment reconciliation – EDIFACT custom flow

Export

In your integrator.io account, from an EDI integration, click + Create flow.

Note

Create this flow (Flow 2) in the same EDI integration that includes Flow 1 mentioned in the above section.
On the new flow page, below Sources, click Add source.
For the source application or export, you can configure the appropriate trading partner. For more information, see configure an EDI export. .

Important

In the EDI parser helper, add "documentType": "CONTRL" in the file definition rules for the Ack status column in the EDI activity dashboard to be updated.

Import

Click Add destination/lookup to add an import to the flow.
In the Application field, enter integrator.io.
On the Create destination/lookup window, in the What would you like to do? drop-down menu, select Import records into destination application.
Click Create flow step.
On the Create import window, provide a Name and Description.
In the Connection field, either select an existing connection or create a new connection.
Below the How would you like the records imported? section,
1. In the Resource drop-down menu, select EDI transactions.
2. In the API endpoint drop-down menu, select Update operation.
Click Save & close.

Check acknowledgment status or download the acknowledgment from the dashboard

In integrator.io, from the left menu, click Dashboard.
In the EDI activity tab, view the acknowledgment status or download the acknowledgment. For more information, see Understand the Dashboard - EDI activity.