Transaction-related exports
Last updated: September 23, 2026
You can export data from ComplyAdvantage Mesh as a .CSV file. This can help you to create management reports or analyse the efficiency and effectiveness of your compliance program.
This article describes the content of the following data exports for transactions:
Transaction Monitoring cases and alerts
Transactions
For the customer screening and ongoing monitoring exports, see Exports for Customer Screening and Monitoring.
Transaction Monitoring cases and alerts
The Transaction Monitoring Cases and Alerts export contains the transaction-monitoring cases raised for your customers and the alerts within each case, including case stage, assignee, and each alert's status, priority and type.
Each row represents an alert and also contains the corresponding case details (case_id, created date time, assignee details etc.)
If a case contains multiple alerts, the case appears multiple times in the export.
These are the fields in the export:
Column | Field name | Description |
A | case_id | The unique ID for the case. |
B | case_created_at | The date and time the case was created. |
C | case_updated_at | The date and time the case was last updated. |
D | case_assignee_id | The unique ID of the user or TM Agent assigned to the case. |
E | case_assignee_name | The name of the case assignee (user name, or TM Agent name). |
F | case_stage_name | The latest status of the case (for example: Not started, In Progress, Escalated). |
G | case_stage_type | The stage category the case is in. |
H | internal_customer_id | The unique customer ID generated by ComplyAdvantage. |
I | external_customer_id | Your unique ID for the customer. |
J | alert_identifier | The unique ID of the alert. |
K | alert_status | The current state of the alert. |
L | alert_updated_at | The date and time the alert was last updated. |
M | alert_created_at | The date and time the alert was created. |
N | alert_priority | The priority assigned to the alert. |
O | alert_type | The type of the alert. |
P | account_identifier | Your ComplyAdvantage account ID. This is the same for all rows of the export. |
Q | alert_last_updated_by_id | The unique ID of whoever, or whatever, last updated the alert: a user ID when a person last actioned it, or the TM Agent's ID when the agent did. Blank if the alert has not been actioned by a person or the TM Agent since it was created. |
R | alert_last_updated_by_user | The name matching that ID: the user's name if a person last actioned the alert, or the TM Agent's name if the agent did. Blank if the alert has not been actioned since it was created. Newly created, un-worked alerts show both fields blank; this is expected, and the fields populate from the moment an alert is first actioned (no historical backfill). |
Transactions
The Transactions export contains the transactions you have submitted to ComplyAdvantage Mesh, the amount and currency of each one, and the payment details that apply to its transaction type. It also shows which scenario evaluated the transaction, and the customer it belongs to, so that the exported data can be paired with your data for analysis.
Each row in the export represents a combination of a transaction and a scenario evaluation. If more than one scenario evaluated a transaction, the transaction appears multiple times in the export.
The payment detail fields are only populated for the matching transaction type. A card payment has values in the card_payment_ fields and blanks in the bank_payment_, remittance_ and crypto_ fields.
These are the fields in the export:
Column | Field name | Description |
A | internal_transaction_id | The unique transaction ID generated by ComplyAdvantage. |
B | external_transaction_id | Your unique ID for the transaction. |
C | transaction_type | The type of the transaction. |
D | customer_identifier | The unique ID of the customer the transaction belongs to, generated by ComplyAdvantage. |
E | classification | Whether the transaction is monetary or non-monetary. |
F | occurred_at | The date and time the transaction took place. |
G | occurred_at_timezone | The time zone the transaction took place in. |
H | received_at | The date and time ComplyAdvantage received the transaction. |
I | value_amount | The amount of the transaction. |
J | value_currency | The currency the transaction took place in, as a 3-letter ISO code. |
K | base_value | The amount of the transaction converted to your account's base currency. |
L | base_value_currency | Your account's base currency, as a 3-letter ISO code. |
M | bank_payment_scheme | For bank payments, the payment scheme used to make the payment. |
N | card_payment_stage | For card payments, the stage the payment reached (for example: authorisation, settlement). |
O | payment_channel | The channel used to initiate the payment. |
P | scenario_name | The name of the scenario that evaluated the transaction. |
Q | scenario_config | The unique ID of the scenario configuration used for the evaluation. |
R | scenario_id | The unique ID of the scenario. |
S | scenario_version | The version of the scenario used for the evaluation. |
T | highest_priority_matching_segment | The name of the highest-priority customer segment that matched the transaction. |
U | remittance_purpose_of_payment | For remittances, the stated purpose of the payment. |
V | remittance_relationship | For remittances, the relationship between the sender and the recipient. |
W | crypto_chain_identifier | For crypto transactions, the blockchain the transaction took place on. |
X | crypto_chain_network_name | For crypto transactions, the name of the network the transaction took place on. |
Y | account_identifier | Your ComplyAdvantage account ID. This is the same for all rows of the export. |
Z | bank_payment_state | For bank payments, the state of the payment. |
AA | bank_payment_debtor_name | For bank payments, the name of the party the money came from. |
AB | bank_payment_creditor_name | For bank payments, the name of the party the money went to. |
AC | card_payment_card_holder_customer_id | For card payments, the unique ID of the card holder, where the card holder is one of your customers. |
AD | card_payment_card_holder_name | For card payments, the name of the card holder. |
AE | card_payment_merchant_name | For card payments, the name of the merchant. |
AF | card_payment_sub_merchant_name | For card payments, the name of the sub-merchant, where one is involved. |
AG | remittance_debtor_name | For remittances, the name of the party the money came from. |
AH | remittance_creditor_name | For remittances, the name of the party the money went to. |
AI | crypto_destination_tag | For crypto transactions, the destination tag supplied with the transfer, where one is used. |
AJ | crypto_transaction_hash | For crypto transactions, the hash of the transaction on the blockchain. |
AK | crypto_chain_network_type | For crypto transactions, whether the network is a main network or a test network. |
AL | crypto_asset_id | For crypto transactions, the identifier of the asset transferred. |
AM | crypto_asset_symbol | For crypto transactions, the symbol of the asset transferred (for example: BTC, ETH). |
AN | crypto_debtor_name | For crypto transactions, the name of the party the money came from. |
AO | crypto_creditor_name | For crypto transactions, the name of the party the money went to. |
For more details on creating exports, see: