---
title: "Set up document flow - Sales order (Delfor)"
slug: "set-up-document-flow-sales-order-delfor"
description: "Set up a document flow to import sales orders into the EDI Delfor journal, ensuring automatic validations and seamless EDI message exchanges."
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-delfor"
---

> ## 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 (Delfor)

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

On the document flow, you can set the 'Sales (Delfor) - XML to EDI Delfor journal' (830) message (from the [Tutorial - EDI - Delfor](/data-management/docs/edi-tutorial-projects#tutorial-edi-delfor)) or a custom 830 message. This message imports the received sales order (Delfor) into the **EDI Delfor journal**. When the import is completed, the applicable validations are done automatically.

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 the 'Sales (Delfor) - XML to EDI Delfor journal' message 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**
> 
> 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:
  - Message, you can use one of these messages from the 'Tutorial - EDI' project. If you want to:
    - 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.

In the **Message** field or in the **Web service action** field, enter or select a value.
12. By default, a document flow is active. You can deactivate a document flow. So, it isn't used.

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).
> - Make sure, the appropriate journal validations are set up.

## Related

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