How to troubleshoot using the Transaction log

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.