# Transaction settings
Source: https://www.stedi.com/docs/edi-platform/configure/trading-partners/transaction-settings

***

title: Transaction settings
sidebarTitle: Transaction settings
----------------------------------

Within each [partnership](/edi-platform/configure/trading-partners/profiles-and-partnerships), you can specify the EDI transaction sets that you plan to exchange with that trading partner.

For example, you may want to receive inbound 837P professional claims from a provider and send outbound 835 Electronic Remittance Advice (ERA) transactions to them. This would involve creating an inbound transaction setting for professional claims and an outbound transaction setting for ERAs.

## Create transaction settings

To create a transaction setting, navigate to the partnership and click either:

* **Create inbound transaction setting** to configure a transaction set you plan to receive from your trading partners
* **Create outbound transaction setting** to configure a transaction set you plan to send to your trading partner.

### Choose a transaction set

When you configure a transaction setting, you must select a machine-readable EDI specification ([Stedi guide](/edi-platform/guides)) for the transaction set.

Guides allow Stedi to validate and parse (inbound) or validate and generate (outbound) EDI data according to your and your trading partner's specific requirements.

* **Import from network (recommended):** Search for your trading partner and click **Select** to import a local copy of the guide into your account.
* **My account:** Select an existing guide from your account.
* **Base guide:** Stedi validates the transaction against the generic X12 specification. This option is useful for testing inbound flows when your partner hasn't yet provided a guide. We do not recommend using it for outbound flows except in rare, advanced use cases.
  * Select the X12 **Release**. The release is present in the `GS` segment of every EDI file, and also should be specified in your partner’s documentation.
  * Select the **Transaction set**. The transaction set is the EDI transaction you are receiving from your partner.

### (Inbound) Configure fragments

If the guide you choose is set up to use [fragments](/edi-platform/fragments), you can enable fragments for the transaction setting. Fragments allow you to split large transactions from Stedi into smaller chunks for downstream ingestion.

### (Outbound) Application IDs

Stedi automatically suggests the default **Application IDs** that were assigned to the local and partner profiles. You can override these values if needed. For example, some trading partners may assign a specific `GS` ID to you during the onboarding process. Since this `GS` ID is used only for this partnership, you would not want to put it in your local profile.

### (Outbound) Connection

Specify the **Connection** to deliver generated EDI files. If no connection is specified, you can't generate outbound EDI files for this transaction.

For **SFTP/FTPS**, You can optionally add a subdirectory that Stedi uses for this transaction set only. For example, your trading partner may require that you place all claims in an `/837` subdirectory. We don't recommend specifying a subdirectory unless your trading partner has instructed you to do so.

### (Outbound) Custom filename expression

By default, Stedi autogenerates a unique name for outbound files using a UUID. To set a custom filename, open **Advanced settings** and enter a JSONata expression into the **Filename expression** field.

You can use `&` (Concatenation), `$random`, or `$millis` in the expression to generate a unique name based on a random number and/or the processing timestamp. For example, the expression `“EDI837-” & $millis()` results in filenames like `EDI837-5182341242`.

## Control numbers

Control numbers are used in the [`ISA` Interchange Control Header](https://www.stedi.com/edi/x12/segment/ISA) and [`GS` Functional Group Header](https://www.stedi.com/edi/x12/segment/GS) of X12 EDI files. You and your trading partners can use them reference EDI files and to detect duplicates and missing data. Control numbers must be unique within a partnership.

Stedi handles control numbers automatically for you. When you create a partnership, Stedi sets the control number counters to `0` for both the Interchange (`ISA`) and Group (`GS`) levels. Each time you send an outbound EDI file, Stedi increments the control numbers to ensure uniqueness.

### Reset control numbers

In rare circumstances, you may need to reset the control numbers for a partnership. For example, if you're migrating from another EDI system, you may need to reset the control numbers to match the last control numbers used in your previous system.

To reset control numbers for outbound documents:

1. Go to the partnership where you want to adjust the control numbers.
2. Open the **Advanced settings** menu.
3. Update the **Interchange** or **Group** control numbers as needed.

### Non-numeric control numbers

Stedi can translate EDI files containing non-numeric control numbers, if required for your use case.

Successful processing requires that you set the `ST-02` and `SE-02` control number elements in the associated Stedi guide to type `String`.

## Timezone and time format

Stedi uses the following default values:

* **Timezone:** UTC | Used in the `ISA` and `GS` segments
* **Time format:** `HHMMSS` | The [GS-05](https://www.stedi.com/edi/x12/segment/GS#GS-05) time element

You can change these values in the partnership's **Advanced settings** menu.

## Next steps

We recommend configuring [Acknowledgments](/edi-platform/configure/trading-partners/functional-acknowledgments) for inbound transactions within the partnership.

We also recommend configuring one or more [webhooks](/edi-platform/configure/webhooks) to automatically send events from Stedi to your internal systems and business applications.