---
title: How to troubleshoot using the Transaction log
description: The Transaction log provides metadata for each transaction. Understand why a message failed and how to correct it.
---

[Skip to content](https://knowledge.qvalia.com/how-to-troubleshoot-using-the-transaction-log#main-content)

- [English](https://knowledge.qvalia.com/how-to-troubleshoot-using-the-transaction-log)
- [Svenska](https://knowledge.qvalia.com/sv/how-to-troubleshoot-using-the-transaction-log)

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/how-to-troubleshoot-using-the-transaction-log)
    - [Svenska](https://knowledge.qvalia.com/sv/how-to-troubleshoot-using-the-transaction-log)

  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. [Logs and monitoring](https://knowledge.qvalia.com/logs-and-monitoring?hsLang=en)

# How to troubleshoot using the Transaction log

## The Transaction log provides metadata for each transaction. Understand why a message failed and how to correct it.

The Transaction log provides metadata for each transaction. The metadata modal contains detailed technical information that helps you understand why a message failed and how to correct it.

### Finding error transactions

1. Go to Organization logs → Transaction log.
2. Set the time range you want to analyse.
3. Open Filters and set Status to Error.
4. Click Apply.
5. Error rows are highlighted, making them easier to locate.

### Working with metadata

Each row in the Transaction log has a Metadata column. When a value is present, you can click it to open the metadata modal.

The metadata modal typically contains sections such as:

#### Error

- Message: human-readable description of the error, for example  
  “Error sending document via Peppol – see log for details”.

#### Peppol

- Message id: the unique Peppol network message identifier.
- Sender peppol id: the sender’s Peppol ID as used in the transmission.

Peppol reporting (and other context-specific sections)

- C2 id: identifier used in Peppol or operator reporting.
- C1 country: the country of the sending or receiving party, for example SE.

The exact structure and fields may vary depending on the message type and how it was processed, but the principle is the same: metadata provides the technical context for what happened to the transaction.

### Using metadata to correct erroneous transactions

The Transaction log is read-only. You do not edit or re-send messages directly from the log. Instead, you use the information in the log and metadata to correct the root cause in your systems and then send a new transaction.

1. Identify the error
   
     - Open the metadata modal for an error row.
     - Review the Error section and any Peppol-related information.
2. Interpret the cause. Typical causes can include:
   
     - Invalid or missing Peppol ID.
     - Recipient not reachable in the chosen network.
     - Non-compliant XML or missing mandatory fields.
     - Connectivity or timeout issues in the delivery channel.
3. Correct the source data. Make corrections in your ERP, invoicing system or integration:
   
     - Update customer or supplier master data (for example Peppol IDs).
     - Correct the document content and regenerate the message.
     - Adjust your integration settings if routing or formats are incorrect.
4. Resend the document
   
     - Trigger a new send from your source system or integration.
     - Use the Transaction log again to verify that the new transaction is processed and reaches status Processed.

### Exporting filtered error lists

When you need to analyse or share error information:

1. Apply your filters (for example a specific period, customer and Status = Error).
2. Click Export.
3. Open the CSV in your preferred tool to group, summarise or attach to support tickets.

### Use cases

- Periodic quality reviews of your integration.
- Coordinating corrections with customers, suppliers or internal IT.
- Providing evidence and technical detail to Qvalia support if you need assistance.

 

### Why do the transaction log and the invoice list show different things?

The transaction log and invoice list show different parts of the flow. Use the transaction log to follow processing and the invoice list to work with the invoice.

- The transaction log should update immediately when Qvalia has received the message.
- Read `Status` for the processing state and `Direction` to see whether the message was sent or received.
- `Processed` means that the message has been processed. `Processed with warning` means that it was processed but a warning was recorded.
- The invoice list has its own statuses, such as `Sent` and `Draft`. Do not confuse them with transaction log statuses.

#### What the two views show

| View | What it contains | How reliable |
| --- | --- | --- |
| **Transaction log** | Messages received or sent by Qvalia, with direction, status, timestamp and technical identifiers. | Use it to follow processing and troubleshoot the message. |
| **Invoice list** | Invoices that you can open and work with in the platform. | Use it for invoice management. Its statuses are not the same as those in the transaction log. |
| **Invoice timeline** | Events for the open invoice. For some integrations, a file name and delivery time may also be shown. | Use it as supporting information for the individual invoice. |

#### How to establish whether the invoice has been sent

1. Open **Transaction log**.
2. Select a date range and search by document ID, sending party ID, receiving party ID or another known value.
3. Read `Direction`, `Status`, `Status update` and the timestamp.
4. If an expected row is missing, reload the browser and search again.
5. If the difference between the views remains, contact support.

- [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