---
title: "Set up document flow - Sales order"
slug: "set-up-document-flow-sales-order-edi-parties"
description: "Set up an EDI document flow to import sales orders efficiently, using staging or direct methods for seamless order management."
tags: ["Task topic"]
updated: 2026-07-28T05:24:12Z
published: 2026-07-28T05:24:12Z
canonical: "docs.staedean.com/set-up-document-flow-sales-order-edi-parties"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up document flow - Sales order

Set up a document flow to define how to import a received order from a specific customer.

On the document flow, you can set these EDI 850 messages (from the [Tutorial - EDI](/data-management/docs/edi-tutorial-projects#tutorial-edi)) or a custom 850 message to import a sales order:

- 'Sales - XML to EDI order': If you use staging, use this message to receive an order from your customer. This message imports the received sales order into the EDI sales order journal. When the import is completed, the applicable validations are done automatically.
- 'Sales - XML order to Order': If you do not use staging, use this message to receive an order from your customer. This message imports the received sales order directly into the Sales orders table.

You can choose to exchange this EDI message using a web service. In this case, instead of a message, use an inbound web service action with one of the above messages as request message.

### Steps

1. Click **EDI party setup**.
2. Click the **Document flow** tab.
3. Click **New**.
4. You can use origins to indicate where messages originate from. For example, a message can originate from EDI, a web shop, or a customer self-service portal. You can set the origin to indicate that the document flow only applies to messages with the same origin. In the **Origin** field, enter or select a value.

> [!NOTE]
> **Note**
> 
> If you do not define an origin, the document flow only applies to messages that also don't have the origin defined.
5. In the **Account code** field, select **Customer**.

> [!NOTE]
> **Note**
> 
> - For a sales order document flow, you can also select **Legal entity**. You can use a legal entity document flow to receive sales order messages from a customer which, for example, does not exist in D365 F&SCM or has no EDI party setup. If you receive a sales order message from such a customer, it can be received with the document flow for your legal entity. If the **Account code** is **Legal entity**, make sure an origin is filled in which **Customer document flow** is set to **Customer + legal entity**.
> - You can also select **EDI group** to link the document flow to an EDI group. As a result, the document flow is applied to all EDI parties with the EDI group assigned.
6. In the **Account selection** field, enter or select a value.
7. In the **Document flow** field, select **Order**.
8. In the **Direction** field, select **Inbound**.
9. You can use a number sequence to define the EDI history record ID.

In the **Number sequence** field, enter or select a value.
10. You can use a document flow in a testing phase. If you do so, you can indicate this for informational purposes.

Select the **Test** check box.
11. Define the desired message or inbound web service action.

If you define a:

In the **Message** field or in the **Web service action** field, enter or select a value.
  - Message, you can use one of these messages from the Tutorial - EDI project.
    - Use staging, select the ‘Sales - XML to EDI order’ message.
    - Directly insert the sales order, select the ‘Sales - XML order to Order’ message.
  - Web service action, make sure one of these messages is defined as the request message of the web service action.
12. By default, a document flow is active.

Clear the **Active** check box.
13. Close the page.

> [!NOTE]
> **Notes**
> 
> - To be able to receive an EDI message based on this document flow, the **GLN code** must be set for the current company (legal entity).
> - If you use staging, make sure the appropriate journal validations are set up.

## Related

- [Sales order](/sales-order.md)
- [EDI tutorial projects](/edi-tutorial-projects.md)