---
title: "Set up document flow - Purchase invoice"
slug: "set-up-document-flow-purchase-invoice"
description: "Set up a document flow to import vendor invoices using EDI or web services, ensuring efficient invoice management and accurate record-keeping."
tags: ["Task topic"]
updated: 2026-07-28T05:24:12Z
published: 2026-07-28T05:24:12Z
canonical: "docs.staedean.com/set-up-document-flow-purchase-invoice"
---

> ## 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 - Purchase invoice

Set up a document flow to define how to import an invoice message from a specific vendor.

On the document flow, set the 'Purchase - XML to Invoice' (810) message (from the [Tutorial - EDI](/data-management/docs/edi-tutorial-projects#tutorial-edi)) or a custom 810 message. This message imports the invoice from your vendor into the invoice register journal.

You can choose to exchange this EDI message using a web service. In this case, instead of the message, use an inbound web service action with the 'Purchase - XML to Invoice' 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 '**Vendor**'.

> [!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 code** field, select '**Vendor**'.
7. In the **Account selection** field, enter or select a value.
8. In the **Document flow** field, select '**Invoice**'.
9. In the **Direction** field, select '**Inbound**'.
10. You can use a number sequence to define the **EDI history record ID**.

In the **Number sequence** field, enter or select a value.
11. 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.
12. Define the desired message or inbound web service action.

If you define a:
  - Message, you can use the 'Purchase - XML to Invoice' message from the 'Tutorial - EDI' project.
  - Web service action, make sure the 'Purchase - XML to Invoice' message 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.
13. By default, a document flow is active. You can deactivate a document flow. So, it isn't used.

Clear the **Active** check box.
14. 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).

## Related

- [Set up buyer messages document flows](/set-up-buyer-messages-document-flows.md)
- [Purchase invoice](/purchase-invoice.md)