Communication Protocols: How EDI Documents Are Exchanged
Cogential IT connects each trading partner over the transport method they already require — AS2 with signed MDN receipts, SFTP and FTPS drop folders, legacy VAN mailboxes, OFTP2 for automotive and retail, or modern API and AS4 delivery — so every document leaves encrypted and arrives with proof it was received.
AS2 Certificate Exchange
Establish signed, encrypted AS2 connections with mutual X.509 certificates and receive a signed MDN for every transmission.
SFTP & Managed File Transfer
Poll and push encrypted files through dedicated SFTP drop folders on a schedule that matches each partner's cadence.
VAN & OFTP2 Mailboxes
Route through legacy Value Added Networks or OFTP2 mailboxes for automotive and retail partners that require it.
API & AS4 Delivery
Push and pull EDI payloads over REST APIs or AS4 web services for partners moving toward real-time integration.
Every EDI transmission follows the same arc regardless of protocol: a secure connection is established, the payload is encrypted and sent, and the receiving system confirms delivery before either side considers the exchange complete.
Authenticates both endpoints with X.509 certificates before a single byte of the document moves.
Moves the payload over an encrypted channel to a mailbox or drop folder on the agreed schedule.
Hands the document to a Value Added Network or OFTP2 endpoint that queues it for the receiver.
Pushes the payload directly over a web service for partners that expect near-instant delivery.
Returns a signed receipt or acknowledgment so both sides have proof the exchange completed.
What Are EDI Communication Protocols?
EDI communication protocols are the transport methods that move a document securely from one trading partner's system to another once it has been translated into a standard like X12 or EDIFACT. Options range from AS2, which pairs mutually authenticated certificates with a signed MDN receipt, to SFTP drop folders, legacy VANs and OFTP2 mailboxes common in automotive and retail, and newer API or AS4 web-service delivery for partners moving toward real-time exchange. The right protocol depends entirely on what each trading partner already requires, and most organizations end up supporting several at once.
Built on the transport channel every partner already expects
-
Match each trading partner's exact protocol, certificate, and encryption requirements out of the box.
-
Monitor every transmission for delivery confirmation, retrying automatically when an MDN or ACK is missing.
-
Run mixed-protocol trading relationships without maintaining separate infrastructure for each channel.