Vialet Transactions — Report documentation

Purpose

The Vialet Transactions report shows every Vialet payment and operation in one place: dates, who paid and who was paid, amounts and fees, and which entity or brand each transaction belongs to. Finance and operations teams use it to reconcile payments, trace a specific payment by ID or entity, and review volume and fees over a chosen period.

What data this report uses

This report uses Vialet transaction data: one row per payment or operation from the Vialet system, with dates, identifiers, payer and beneficiary details, amounts and fees, and organisation or integration context (including brand and entity when the integration is in the metadata). For full field definitions, when columns can be empty, and how the data is structured, see the Vialet — User Guide.

Report-level filters

These filters apply to the whole report and narrow which transactions appear in the table.

Filter	What it does	How to use it	When it's useful
Payment ID	Finds transactions that match a given payment identifier.	Enter a value (exact or partial, depending on Looker configuration).	Tracing a single payment or a small set of payments.
Entity	Limits results to transactions for a specific entity (from integration metadata).	Pick one or more entities from the dropdown.	Analysing or reconciling by entity (e.g. SandTech, Igloo).
Brand	Limits results to transactions for a specific brand (from integration metadata).	Pick one or more brands from the dropdown.	Analysing or reconciling by brand.
Brand IBAN	Limits results to transactions for a specific internal account (IBAN).	Pick one or more IBANs from the dropdown.	Focusing on a single account or comparing a few accounts.
Date range	Restricts the table to transactions that fall within the selected period.	Choose a start and end date (e.g. Mar 8, 2026 – Mar 14, 2026).	Reviewing activity for a specific week or month; matching to bank or partner statements.

Resource-level filters

This report has no resource-level filters. Every filter applies to the entire report.

The main table

The report is built around one table that lists Vialet transactions. Each row is one transaction. The table can be long (tens of thousands of rows), so the report shows a page at a time; use the pagination controls to move through pages.

Columns appear in the same order as on the report. The following table describes what each column shows in plain language.

Column	Meaning
Date	The calendar date of the transaction. Use it to see when each payment or operation happened.
Internal IBAN	The internal (your side) account number for the transaction: for outgoing payments it shows the payer account; otherwise it shows the beneficiary account. This helps you see which of your accounts was involved.
Entity	The entity label from your integration metadata (e.g. SandTech, Igloo). Empty when the transaction’s integration is not in the metadata list.
Payment ID	The Vialet payment identifier for the transaction. Use it to trace or match a specific payment. It may show NOTPROVIDED or null when no identifier was supplied.
Operation Type	The kind of Vialet operation (e.g. INTERBANK).
Direction	Whether the transaction is incoming (CREDIT) or outgoing (DEBIT).
Payer	The name of the party that sent the money.
Beneficiary (Name)	The name of the party that received the money.
Beneficiary (IBAN/ID)	The account number or identifier of the beneficiary (e.g. an IBAN).
Payment Details	Any extra narrative or reference information for the payment.
Amount Currency	The currency of the transaction amount (e.g. EUR).
Fee Currency	The currency of the fee (e.g. EUR).
Amount	The transaction value. Incoming flows are positive and outgoing flows are negative, so you get a consistent view of net movement. Negative amounts are highlighted in the report (e.g. with a red background) to make outflows easy to spot.
Fee Amount	The fee charged for the transaction.