--- title: "Set up document flow - Sales acknowledgement" slug: "set-up-document-flow-sales-acknowledgement-edi-parties" description: "Set up a document flow for sending sales order acknowledgements via EDI or web service, ensuring efficient communication with customers." tags: ["Task topic"] updated: 2026-07-28T05:24:12Z published: 2026-07-28T05:24:12Z canonical: "docs.staedean.com/set-up-document-flow-sales-acknowledgement-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 acknowledgement Set up a document flow to define how to send a sales order acknowledgement message to a specific customer. On the document flow, set the 'Sales - Acknowledgement to XML' (855) message (from the [Tutorial - EDI](/data-management/docs/edi-tutorial-projects#tutorial-edi)) or a custom 855 message. This message sends the sales order acknowledgement to your customer. You can choose to exchange this EDI message using a web service. In this case, instead of the message, use an outbound web service action with the 'Sales - Acknowledgement to XML' 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 '**Acknowledge**'. 8. In the **Direction** field, select '**Outbound**'. 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 outbound 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 the 'Sales - Acknowledgement to XML' message from the 'Tutorial - EDI' project. - Web service action, make sure the 'Sales - Acknowledgement to XML' message is defined as the request message of the web service action. 12. In the outbound queue, several entries can exist for a unique message or web service action. For an outbound document flow, you can bundle the entries for the applicable message or web service action. The outbound queue entries are bundled by the applicable EDI party or EDI partner, depending on the setting in the **Bundle by** field. On processing the outbound queue, the entries are bundled in one message run or web service action run, which results in one file. Select the **Bundle outbound queue by message** check box. > [!NOTE] > **Note** > > - If, for the document flow, the account code is EDI group, the outbound queue entries are bundled by each EDI party as set up for the EDI group. > - You can also apply bundling to the **Additional setup** of an outbound document flow. 13. If **Bundle outbound queue by message** is set to **Yes**, you can bundle outbound queue entries by one of these options: - **EDI party** (default behavior): All outbound queue entries for the same EDI party are bundled in one message run or web service action run. This results in one file per EDI party. - **EDI partner**: All documents for EDI parties that share the same EDI partner are bundled in one message run or web service action run. This results in one file per EDI partner. If no EDI partner is assigned, bundling is done by EDI party. In the **Bundle by** field, select an option. > [!NOTE] > Note > > An EDI party can be part of another organization that does send and receive their EDI messages. We refer to this as an EDI partner. For example, the head quarter of your customer does send and receive all EDI messages instead of your customer. You can define the applicable EDI partner for each EDI party setup. 14. In some cases, for outbound, you only want to run a message or web service action for records that fit a defined range. You can have the range of the source document checked before the message or web service action is run. If the record doesn't meet the range, the **Outbound queue** status is set to '**No data exported**' instead of '**Error**'. **Example:** You run an EDI message on sales orders. However, you also receive return orders. For these return orders, no invoice amount is filled in. So, you only want to run the EDI message for sales orders with an invoice amount filled in. On the source document, you can define a range to check this. Select the **Flow condition** check box. 15. You can define a target connector for a document flow. This target connector overrules the target connector of the document flow message. In this way, you can use one message to send an EDI message to several EDI parties. So, no separate message is required for each of the EDI parties. In the **Connector** field, enter or select a value. > [!NOTE] > **Note** > > To apply a document flow target connector: > > - For each target, enter a document flow with the same message but a different target connector. > - The target connector you define for the document flow must match the type of the target connector of the message. If the message connector type is: > - **D365 F&SCM** -> **D365 F&SCM** > - **Database** -> **Database** > - **Staging journal** -> **Staging journal** > - **Azure file storage**, **Azure Blob Storage**, and **SharePoint** are interchangeable. > - Connectors of type '**Web service**' or '**Upload and download**' are not supported. > - The data structure of the different targets must be the same. 16. By default, a document flow is active. You can deactivate a document flow. So, it isn't used. Clear the **Active** check box. 17. Close the page. > [!NOTE] > **Notes** > > To be able to send an EDI message based on this document flow, the **GLN code** must be set for the current company (legal entity). ## Related - [Send additional message with outbound document flow](/send-additional-message-with-outbound-document-flow.md) - [Sales acknowledgement](/sales-acknowledgement.md) - [EDI tutorial projects](/edi-tutorial-projects.md)