--- title: How to follow an order through Peppol description: Shows where an order and an order response appear at each step, where the unique transaction ID is found, and the four things that actually stop the flow. --- [Skip to content](https://knowledge.qvalia.com/order-flow-tracking#main-content) - [English](https://knowledge.qvalia.com/order-flow-tracking) - [Svenska](https://knowledge.qvalia.com/sv/sa-foljer-du-en-order-genom-peppol) English Show submenu for translations [Submit a ticket](https://knowledge.qvalia.com/kb-tickets/new?hsLang=en) [Customer portal](https://servicedesk.qvalia.com/tickets?hsLang=en) ![Qvalia Logo New Blue transparent.png\]](https://knowledge.qvalia.com/hs-fs/hubfs/Qvalia%20Logo%20New%20Blue%20transparent.png?height=24&name=Qvalia%20Logo%20New%20Blue%20transparent.png) Open main navigation Close main navigation - - [English](https://knowledge.qvalia.com/order-flow-tracking) - [Svenska](https://knowledge.qvalia.com/sv/sa-foljer-du-en-order-genom-peppol) English Show submenu for translations - [Submit a ticket](https://knowledge.qvalia.com/kb-tickets/new) - [Customer portal](https://servicedesk.qvalia.com/tickets) How can we help you? - There are no suggestions because the search field is empty. 1. [Knowledge base](https://knowledge.qvalia.com/?hsLang=en) 2. [Order management](https://knowledge.qvalia.com/order-management?hsLang=en) # How to follow an order through Peppol ## Track the order or order response in the transaction log. It shows the status, recipient and the transaction ID the recipient needs to search in their own log. - Every Peppol message that has passed through Qvalia carries a **unique transaction ID** in the form `@QVALIA-PSE000094`. Where you find it depends on the direction: see the section below. - Give that ID to the counterparty. It is the one detail that lets them locate the message in their own log. - If the message is in the log but not with the recipient: check that the recipient's Peppol ID is registered for the **right profile**, not merely that it exists. - If order responses disappear in numbers, the cause is almost always that the **transfer ID is not unique**: see the section further down. ### Where the order appears at each step Step Where you see it What you can do yourself You place the order file for sending The **send folder** on your SFTP account at Qvalia The file needs no particular prefix. You place it in the send folder Qvalia receives and processes the file The transaction log Check the status on the row. See the article on transaction log statuses The message goes out over Peppol The transaction log, the Message id field under Metadata Copy the transaction ID if you need to trace further with the counterparty An incoming order or order response reaches you The transaction log, the order management view, and through API or SFTP Retrieve it through the API or from SFTP as described below ### The unique transaction ID If the counterparty needs to troubleshoot on their side, the transaction ID is the most useful detail you can provide. Where you find it depends on the direction. For a message you have **sent**: open the row in the transaction log, click Metadata and read the **Message id** field under the Peppol heading. For a message you have **received**: read the **Correlation ID** column directly in the log. The value looks the same in both cases, for example `b923d1a5-492c-4948-928b-9d4444e5d11a@QVALIA-PSE000094`. The same metadata panel also shows the sender's and receiver's Peppol IDs, the document type and the time the message was exchanged. Field and column names appear in English even if you have selected Swedish in the portal. ### Retrieving orders programmatically There are two routes, and both require API or SFTP to be enabled for your account: 1. **API.** Incoming orders are retrieved with `GET /transaction/{accountRegNo}/orders/incoming/readorders`. Add the query parameter **includeRead** to get back orders already marked as read as well: that is the most common reason an order appears to be "missing" from a call. The API documentation is at `api.qvalia.io/api-documentation/apis/transaction-api`. 2. **SFTP.** The same orders can be collected as files, if that suits your integration better. Qvalia does not write orders directly into your own database. The recommended pattern is that you retrieve them through the API or SFTP and write them onward to your database yourself. ### Registration per profile: the thing most often missing A Peppol ID can be able to receive orders without being able to receive order agreements, or the other way round. Registration is done **per Peppol ID and per profile**, for example Peppol BIS Ordering 3 and Peppol BIS Order Agreement 3. Qvalia performs the registration, not you. To start receiving a new message type, list which Peppol IDs and which message types it concerns and ask Qvalia to register them. The established approach is to run a test in the QA environment first and then enable it in production. ### Where the flow actually stops #### 1. The transfer ID is not unique This is the heaviest cause of order responses going missing. The receiving system reads `InstanceIdentifier` in the **SBDH** (Standard Business Document Header, the envelope around the message itself) first. If there is no SBDH, the message's own `ID` is used instead. If the sender puts the same `ID` on every order response, the transfer ID is identical time after time: files overwrite one another and order responses vanish without anyone receiving an error. SBDH can be enabled as a **per-account setting configured by Qvalia**. Note the consequence: when SBDH is added, it applies to all incoming messages, including invoices. The change requires your approval and is tested in QA before it is enabled in production. You cannot change this setting in the portal. Contact Qvalia and state which message types are concerned. When building an integration, make sure that the source system creates unique IDs. This allows each message to be identified even when a filename or transfer step needs to be investigated. #### 2. The filename is not unique The filename can be configured by document type, including orders, order responses and catalogs. The pattern can include the message transaction ID, a running sequence number, the date or the document ID. For orders and order responses, the transaction ID is recommended because it is unique and can be looked up in the transaction log. Qvalia configures this setting. It is not available in the portal. Contact support and state which message types are concerned. Do not build the integration around an exact filename pattern until it has been confirmed for your account. #### 3. An invalid Peppol ID in the order An order carrying `` contains an organization number without a Peppol scheme and cannot be routed. See the article on the buyer's organization number not being their Peppol ID. #### 4. Technical stopping points in the test environment Symptom Cause according to Qvalia Action The AS4 error `EBMS:0102 FailedDecryption` or "Cannot find key for certificate" on order responses in the test environment The counterparty's test environment has not updated the SML entries Qvalia submitted and is still using an older certificate (G2) while Qvalia uses G3 in the test environment Ask the counterparty to update their SML entries in the test environment Broken characters in order text Character encoding. In Peppol it is always UTF-8 Make sure no re-encoding happens before the file is uploaded to Qvalia ### If the address remains after a deregistration An address still visible in the **Peppol Directory** after deregistration does not mean it remains in the network. The Peppol Directory is a separate, publicly searchable catalog that does not always keep up. In the technical catalog that access points actually use, the address is gone and can be registered by a new operator. See the article on deregistering a Peppol ID. ### If it still does not work - **Check one last time:** that the message is in the transaction log with a transaction ID, that the recipient's Peppol ID is registered for the right profile, and that your outgoing messages carry unique IDs. - **Have this ready when you contact support:** the unique transaction ID from the metadata field, the sender's and recipient's Peppol IDs, the message type and profile, the date and time, the file name if the file was placed on SFTP, and whether it concerns QA or production. - **Contact support:** through the support form at the bottom of https://qvalia.com or at help@qvalia.com. - [General](https://knowledge.qvalia.com/general?hsLang=en#main-content) - [Peppol](https://knowledge.qvalia.com/general?hsLang=en#peppol) - [Partner](https://knowledge.qvalia.com/partner?hsLang=en) - [Logs and monitoring](https://knowledge.qvalia.com/logs-and-monitoring?hsLang=en) - [Integrations](https://knowledge.qvalia.com/integrations?hsLang=en) - [Invoice management](https://knowledge.qvalia.com/invoice-management?hsLang=en) - [Order management](https://knowledge.qvalia.com/order-management?hsLang=en) - [Data management](https://knowledge.qvalia.com/data-management?hsLang=en) - [Security and compliance](https://knowledge.qvalia.com/security-and-compliance?hsLang=en) - [Account](https://knowledge.qvalia.com/account?hsLang=en) - [Troubleshooting](https://knowledge.qvalia.com/troubleshooting?hsLang=en) [![Chill listening crop-3](https://knowledge.qvalia.com/hs-fs/hubfs/Qvalia%20Logo%20New%20Blue%20transparent.png?width=107&height=24&name=Qvalia%20Logo%20New%20Blue%20transparent.png "Chill listening crop-3")](https://qvalia.com/) Knowledge base Copyright © 2025, Qvalia