Home /  Core / 

Transaction data in Stedi Core

You can monitor, inspect, test, and debug the transaction data flowing through Core.

Filter and sort

You can review all incoming and outgoing transaction data in two pages within the Core UI: Transactions and File executions.


This page shows every transaction set you exchange with trading partners. A single file can contain multiple transactions. Individual transactions only appear on this page after Core has successfully processed the entire file.

You can filter the data by transaction set, sender, receiver, direction, and usage (such as production or test). You can also search for specific transaction sets based on a business identifier, such as a purchase order number.

File executions

This page shows every file you exchange with trading partners, its processing status, and the number of transactions within the file.

You can filter file execution data by status (such as Failed or Completed), direction, partnership, and fault (such as failed to find guide).

Inspect raw data

You can review the raw EDI or JSON data for processed files and individual transaction sets. Click the name of the file or transaction set to review its data.

  • For transactions, Core displays the data in the EDI Inspector. In this view, you can review partnership details about the transaction, get more information about the segments or elements within the file, translate the data back and forth between JSON and EDI, and download the raw data.

    Note: When viewing the raw EDI for a single transaction, the data Core displays may differ from the original EDI file. This is because the transaction EDI only shows a single transaction, while a file may contain many separate transactions. However, the transaction EDI always includes the ISA (Interchange Control Header) and GS (Functional Group Header) from the source document.
  • For files, Core displays an overview page that contains processing results and the entire source of the original, unmodified file. You can copy or download the source file to your local machine.

Manage failed file executions

You can review the processing status for all incoming and outgoing transactions on the File executions page. You can choose to manually retry or ignore failed file executions.
  • To bulk retry, click Retry. Core automatically retries processing for every file with the Failed status.
  • To bulk ignore, click Ignore. You may want to ignore executions when they contain an outdated version of a file that you no longer need to retry.

Generate test files

You can generate test data from within Core to test your processing pipeline. Test files contain a T in the Usage element of the ISA header.

To generate test data:

  1. Go to the File executions page.
  2. Click Create and select Generate test file.
  3. Select a Partnership and a Transaction setting. Core autogenerates either EDI (inbound transactions) or JSON (outbound transactions) based on the transaction setting configuration.
  4. Enter test data for all required elements within the test EDI document. This step may not always be required.
  5. Click Create test.edi or Create test JSON, depending on the transaction direction.
Core automatically generates the test file and adds it to the inbound or outbound bucket directory associated with the test file’s transaction settings. When Core finishes processing the test file, it displays all transaction sets in the Transactions page with the TEST label.
Filter and sortInspect raw dataManage failed file executionsGenerate test files


Have an idea for something we could improve? Page not clear? We love feedback - send us a message.


Build EDI integrations fast, without being an EDI expert

Start building
  1. Twitter
  2. GitHub
Backed by
AdditionBloomberg BetaFirst RoundStripeUSV
Customer AgreementService TermsPrivacy Notice

Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on our site are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.