How to use filters in Transaction log

The Transaction log supports advanced filtering on message attributes. Filters help you quickly narrow down large volumes of data, especially when you work with API integrations or Peppol traffic.

Using filters

1. Go to Organization logs → Transaction log.

2. Define your basic time range using Start date, Start time, End date and End time.

3. Click Filters to open the advanced filter panel.

4. Set the parameters you need.

5. Click Apply to update the list.

Available filters

In addition to the time range, you can filter on:

Core identifiers

• Internal transaction ID – Qvalia’s internal transaction identifier.

• Document ID – the document reference, for example invoice number or order number.

• Document type – select one or more document types (Invoice, Credit note, Order, etc.).

• Status – for example Processed or Error.

Direction and parties

• Direction – Incoming or Outgoing.

• Sending party name/Sending party ID – search for messages from a specific party.

• Receiving party name/Receiving party ID – search for messages to a specific party.

Document dates and status dates

• Document start date/Document end date – filter by document date range.

• Status update start date/Status update end date – focus on messages whose status changed in a given period.

• Status update start time/Status update end time – refine within a single day.

Routing and format

• Source – for example Qvalia Portal, API, SFTP, Peppol.

• Source format – original format, such as PDF or UBL.

• Delivery method – how the message was sent, for example Peppol, Email, SFTP.

• Transformation – filter on specific transformation types if you need to analyse converted messages.

Other parameters

• Filename – filter on filenames for file-based batches.

• Correlation ID – locate all messages that share a specific correlation identifier.

• Metadata – free-text search in the metadata field. Useful when you know part of an error message or a Peppol message ID.

Tips and use cases

• Start with a reasonably narrow time range to keep the result set manageable.

• Add only a few filters at a time, then refine further if needed.

• Use Metadata search when you have an error code, network reference or message ID from another system.