Other

EDIFACT D96A Integration

Zynk's EDIFACT D96A integration lets you handle EDI messages inside your own automated workflows. Incoming D96A messages, such as purchase orders from a retailer, convert to XML so a workflow can import them into Sage 200, Sage 50 or Business Central. Outgoing documents travel the other way, from XML into D96A files ready for your trading partner.

Available for

Workflow

Capabilities may differ depending on the product.

See what you can do Book a call →

Benefits

Why businesses connect EDIFACT D96A

EDI orders any system can read

EDIFACT D96A messages convert to XML, which the XSLT Transform task can reshape into whatever format Sage, Business Central or another Zynk connector expects to import.

Replies in the format partners require

Order responses, despatch advice and invoices built as XML convert back to D96A, so trading partners receive files in the 1996 directory version their EDI guidelines specify.

Validation before anything is sent

The XML to EDIFACT D96A task can validate its input and will not write a file if the data fails, so malformed messages are caught before a trading partner has the chance to reject them.

Shared format with Amazon Vendor Central

The connector uses the same XML format as the Amazon Vendor Central (EDI) connector, so XML produced by those tasks can be converted directly, without building a second mapping.

Part of the wider workflow

Conversion sits alongside SFTP transfers, file handling and accounting imports in one Zynk workflow, so an EDI order can be collected, translated and posted without a manual step in between.

Capabilities

What you can do with EDIFACT D96A

Every task the Zynk EDIFACT D96A connector can run, grouped by the direction data moves.

Actions in EDIFACT D96A

Tasks Zynk can automate in EDIFACT D96A

2 tasks

EDIFACT D96A to XML → in EDIFACT D96A
XML to EDIFACT D96A → in EDIFACT D96A

Need something that isn't listed?

Most EDIFACT D96A projects include at least one custom step. Our team builds it for you.

Talk to us

The problem

Why integrate EDIFACT D96A?

Many retailers and manufacturers still ask suppliers to trade using EDIFACT D96A, a release of the UN/EDIFACT standard dating from 1996. The messages are compact, coded and strict about structure, so they rarely import straight into an accounting system. Without a converter, orders get printed and rekeyed, and invoices are typed into partner portals.

Without integration

EDI purchase orders opened in a viewer and keyed into the ERP
Invoices typed into a retailer's web portal one at a time
Partner rejections caused by badly formed files
A separate EDI tool to maintain alongside every other integration

With Zynk

Orders convert to XML and import into the ERP as sales orders
Invoices exported from the ERP are converted into D96A files
Validation checks the data before a D96A file is written
EDI conversion runs inside the same Zynk workflows as everything else

How it works

How the EDIFACT D96A integration works

Step 1: Collect the files
Inbound EDIFACT files are picked up from an SFTP or FTP server, a shared folder or whichever other location your trading partner delivers to.
Step 2: Convert to XML
The EDIFACT D96A to XML task turns each interchange into structured XML, keeping details such as order references, delivery points and line items available for mapping.
Step 3: Transform and import
An XSLT Transform reshapes the XML for the target system, and the matching connector creates sales orders or other records in Sage, Business Central or your ERP.
Step 4: Send the reply
Outbound messages follow the reverse route: data exported from the ERP is transformed to XML, validated, converted to D96A and uploaded for the partner to collect.

Integrations

What can you connect to EDIFACT D96A?

Sage 200

Microsoft Dynamics 365 Business Central

Amazon Vendor Central

FTP

Xero

Example use cases for EDIFACT D96A integration

EDIFACT D96A and Sage 200

Purchase orders from retail customers convert from D96A into Sage 200 sales orders, and Sage 200 invoices or despatch notes can be turned into INVOIC or DESADV messages in reply.

View the Sage 200 integration →

EDIFACT D96A and Microsoft Dynamics 365 Business Central

Business Central sales orders can be created from incoming EDI orders, while sales invoices and shipments exported from Business Central become D96A documents for the trading partner.

View the Microsoft Dynamics 365 Business Central integration →

EDIFACT D96A and SFTP

Where a trading partner exchanges EDI files over SFTP, Zynk's SFTP tasks download new messages for conversion and upload outbound D96A files once they have been built.

View the SFTP integration →

EDIFACT D96A and XML and XSLT

XSLT Transform does the mapping work, reshaping the XML produced from D96A into the formats each Zynk connector imports, and building XML that converts back to EDIFACT.

View the XML and XSLT integration →

Find your integration →

Articles

Articles related to EDIFACT D96A

Ecommerce

Streamlining operations with Amazon and Sage integration

Amazon and Sage integration automates order processing, inventory management, and financial reporting. Zynk's platform simplifies this connection, eliminating manual data entry and improving operational efficiency for Amazon sellers.

EDIFACT D96A integration FAQs

What is EDIFACT D96A?

D96A is a 1996 release of the UN/EDIFACT standard for electronic business documents, maintained through UNECE. Many retailers and manufacturers still specify it for messages such as ORDERS, ORDRSP, DESADV and INVOIC, covering orders, order responses, despatch advice and invoices.

Can EDI orders be imported into Sage 200?

Yes. Zynk converts the incoming D96A ORDERS message to XML, transforms it to the Sage 200 format and creates sales orders. Invoices and despatch notes exported from Sage 200 can be converted back into D96A for your trading partner.

Which EDIFACT versions does Zynk support?

The EDIFACT tasks in Zynk work with the D96A directory. If a trading partner specifies a different directory version, talk to our team about the requirement before you agree a go-live date with that partner.

Does Zynk validate EDIFACT files before sending them?

Yes. The XML to EDIFACT D96A task can validate its input. If the data fails validation, the task reports an error and produces no file, so you can fix the problem before anything reaches your partner.

How are EDIFACT files sent to and received from partners?

Zynk converts and maps the messages, and delivery depends on what your partner supports. Where files are exchanged over SFTP or FTP, Zynk's transfer tasks handle collection and upload in the same workflow. Other routes are discussed during scoping.

Can EDI messages feed Business Central or Sage 50?

Yes. Once a D96A message is in XML, it can feed any Zynk connector that imports orders or invoices, including Microsoft Dynamics 365 Business Central and Sage 50 UK. Outbound documents can be built from either system's exports.

Do I need to understand EDIFACT segments to use the connector?

Not in day to day use. The segment mapping is set up once in the XSLT Transform during the project, and after that orders and invoices move without anyone reading raw EDI. Your team only steps in when a partner changes its requirements.

See what Zynk can automate for your EDIFACT D96A setup

Book a 20-minute call. We'll review your systems, flag the quick wins and outline a practical route to going live.

Book a call See pricing →