EDI

How it works

The file format is the EDI spec. The transport is AS2, SFTP, or a VAN. A pretty PDF of the invoice is not EDI. Mapping errors are content errors after a good transfer.

A nightly 850 purchase order, 2 MB, lands by SFTP. The transfer row is green. The mapper rejects segment N1. The file moved. The document did not import. Both statuses belong on the ticket.

How it differs

EDI is not a generic file transfer. The payload has a schema. A ZIP of images is not EDI.

Partners freeze specs. A new field you add can fail their map after years of green transfers.

Version the map.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• On a real ticket, write down the door, the byte count, and the clock.
• For edi, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
• A progress bar is not that record.
• A 200 response that arrives before the complete call is not that record.
• If a retry is allowed, say how many and whether it resumes.
• If a person must approve the send, name the person.
• Partners who receive edi files should match on hash or size before they import.
• A same-length corrupt file passes a size check and fails a hash.
• Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
• When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.