Stedi automatically validates and parses inbound EDI files in real time, according to the transaction settings you defined for the trading partner.

​
Files with multiple EDI interchanges

Stedi can process files containing multiple EDI interchanges. However, you may need to update the connection’s ISA validation options depending on the expected ISA values:
  • If every ISA header will have the same sender and receiver IDs, you can leave the connection on the Default option.
  • If the ISA headers could have multiple different sender and receiver IDs, you must set the connection to Ignore ISA validation. This option makes it harder to troubleshoot issues in your account, so we recommend only using it if you’re very sure you need it for your use case.
Stedi emits a file.processed.v2 event for the file and one transaction.processed.v2 event for each transaction within the file. You can review each processed interchange on the file’s details page in the Stedi portal.

​
Send transactions to your business system

You can use webhooks to automatically send transaction.processed.v2 events to any API endpoint. The transaction.processed.v2 event contains a URL that you can then use to fetch processed transaction data from Stedi.

​
Transform transactions to a custom shape

Stedi translates EDI files into Guide JSON, a JSON format that closely reflects the structure of an EDI transaction. You need to transform Guide JSON into a shape your system can understand and ingest. Visit Transformation approaches for details.

​
Large file support

This functionality is available in a Stedi module. Contact us for details.
If you need to process EDI files over 10 MB in size, we recommend adding the Large file processing module. Contact us for details. You may also want to use Fragments, a module that helps you split processed transactions from Stedi into smaller chunks for downstream ingestion.

​
Non-EDI file types

Stedi can route non-EDI formats like CSV, JSON, and XML for further processing. When a non-EDI file arrives, the file appears in the UI, and Stedi emits an event that contains a summary of the file execution. You can configure webhooks that forward this event to your business system. How Stedi processes non-EDI files depends on the file extension:
  • Stedi emits a file.processed.v2 event for all files with .json, .csv, .xml, .xls, .xlsx or .pdf file extensions.
  • Stedi attempts to process any other file extension, such as .txt or .edi, as EDI. If parsing fails, it attempts to parse the file first as JSON and then as CSV. If parsing still fails, it will mark the execution as failed and emit a file.failed.v2 event, which can be used to trigger additional processing.

​
Processing limits

Stedi can process EDI files that are gigabytes in size, and there is no hard restriction on the maximum file size you can attempt to process. If you run into issues processing a large file, please reach out and our engineers will help remove any limitations that you’re encountering.