What are data exports?

Last updated: September 7, 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:

Customer screening
Customers
Screening and monitoring cases
Profiles

Customer screening

The Customer Screening export provides details about the customers screened, the date and time of the screening, and the match results.

This information is essential for understanding your screening processes. You can use it to calculate metrics such as the number of screenings over time, match rates and the average number of hits per match.

Each row in the export represents one screening.

These are the fields in the export:

Column	Field name	Description
A	screening_id	A unique ID for the screening.
B	screening_config_id	A unique ID of the screening configuration used.
C	screening_config_name	The name of the screening configuration used.
D	screening_config_version	The version of the screening configuration used.
E	internal_customer_id	The unique customer ID generated by ComplyAdvantage.
F	created_at	The timestamp of when the screening took place.
G	updated_at	The timestamp of when the screening was updated.
H	match_status	Indicates whether a screening returned any hits with TRUE or FALSE.
I	number_of_hits	The total number of hits returned for a given screening.
J	account_identifier	Your ComplyAdvantage account ID. This will be the same for all the rows of the export.
K	external_customer_id	Your unique ID for the customer. This ID is generated by you and is your reference for the customer.
L	person_full_name	If the customer is a person, their full name is provided.
M	company_legal_name	If the customer is a company, the legal company name is provided.
N	undefined_name	If the customer type is undefined, the customer name is provided.

Customers

The Customer export contains information about your customers, including their creation date and monitoring status. It also details each customer's risk level and their case count.

Each row in the export represents one customer.

These are the fields in the export:

Column	Field name	Description
A	internal_customer_id	The unique customer ID generated by ComplyAdvantage.
B	external_customer_id	Your unique ID for the customer. This ID is generated by you and is your reference for the customer.
C	created_at	The date and time the customer was created.
D	updated_at	The date and time when the customer was updated.
E	customer_status	The status of a customer (processing, active or closed).
F	customer_type	The type of customer (person or company).
G	customer_labels	The labels associated with this customer
H	customer_version	The version of the customer
I	person_first_name	The first name of the customer if the type is person.
J	person_middle_name	The middle name of the customer if the type is person.
K	person_last_name	The last name of the customer if the type is person.
L	person_full_name	The full name of the customer if the type is a person, and if their name information was provided as a single field.
M	person_date_of_birth	The date of birth of the customer if the type is a person.
N	person_country_of_birth	The country of birth of the customer if the type is a person.
O	person_nationality_list	A list of the customer’s nationalities if the type is a person.
P	person_country_of_residence_list	A list of the customer’s countries of residence if the type is a person.
Q	person_address_country_list	A list of the customer’s address countries if the type is a person.
R	company_address_country_list	A list of the customer’s address countries if the type is a company.
S	company_legal_name	The legal name of the customer if the type is a company.
T	company_place_of_registration	The place of registration of the customer if the type is a company.
U	company_incorporation_date	The incorporation date of the customer if the type is a company.
V	undefined_name	The name of the customer for a customer where the customer type was not provided and hence is categorised as 'undefined'.
W	undefined_country_list	Countries associated with a customer where the type is 'undefined'.
X	undefined_birth_year	Year of birth of a customer where the type is 'undefined' .
Y	customer_risk_level	The overall risk level of a customer (low, medium, high, prohibited or unspecified).
Z	is_monitored	Whether the customer is being monitored on an ongoing basis (YES or NO).
AA	last_monitor_run	The date and time the customer was last monitored.
AB	total_open_onboarding_cases	The number of open onboarding cases associated with the customer.
AC	total_closed_onboarding_cases	The number of closed onboarding cases associated with the customer.
AD	total_open_monitoring_cases	The number of open monitoring cases associated with the customer.
AE	total_closed_monitoring_case	The number of closed monitoring cases associated with the customer.
AF	total_open_payment_screening_cases	The number of open payment screening cases associated with the customer.
AG	total_closed_payment_screening_cases	The number of closed payment screening cases associated with the customer.
AH	account_identifier	Your ComplyAdvantage account ID. This will be the same for all the rows of the export.
AI	acquisition_source	The source through which the customer was acquired

Screening and monitoring cases

The Screening and Monitoring Cases export contains the creation date, type and decision for each case. It also shows who worked on the case, the total time taken to remediate the case and the screening configuration applied.

There are customer details, so that the exported data can be paired with your data for analysis.

Each row in the export represents a combination of a case and an alert within the case. If a case contains multiple alerts, then the case will be shown multiple times in the export, once for each alert.

These are the fields in the export:

Column	Field name	Description
A	case_id	The unique ID for a case.
B	case_type	The type of the case (onboarding or monitoring).
C	case_stage_name	The latest status of the case. You can customize the statuses but the defaults are: Not started In Progress Escalated On Hold No risk - Accept Manageable risk - Accept Unacceptable risk - Reject
D	created_at	The date and time the case was created.
E	updated_at	The date and time the case was last updated.
F	assignee_id	The unique ID of a ComplyAdvantage Mesh user assigned to a case.
G	external_customer_id	Your unique ID for the customer. This ID is generated by you and is your reference for the customer.
H	customer_type	The type of customer (person or company).
I	customer_labels	The labels associated with this customer.
J	customer_acquisition_source	The acquisition source of the customer.
K	customer_version	The customer version.
L	customer_risk_level	The overall risk level of a customer (low, medium, high, prohibited or unspecified).
M	person_first_name	The first name of the customer if the type is person.
N	person_middle_name	The middle name of the customer if the type is person.
O	person_last_name	The last name of the customer if the type is person.
P	person_full_name	The full name of the customer if the type is a person, and if their name information was provided as a single field.
Q	person_country_of_birth	The country of birth of the customer if the type is a person.
R	person_nationality_list	The nationality of the customer if the type is a person.
S	person_country_of_residence_list	The country of residence of the customer if the type is a person.
T	person_address_country_list	List of countries in customer addresses, if the customer type is a person.
U	person_date_of_birth	The date of birth of the customer if the type is a person.
V	company_legal_name	The legal name of the customer if the type is a company.
W	company_place_of_registration	The place of registration of the customer if the type is a company.
X	company_incorporation_date	The incorporation date of the customer if the type is a company.
Y	company_address_country_list	List of countries in customer addresses, if the customer type is a company.
Z	undefined_name	The name of the customer for a customer where the customer type was not provided and hence is categorised as 'undefined'.
AA	undefined_country_list	Countries associated with a customer where the type is 'undefined'.
AB	undefined_birth_year	Year of birth of a customer where the type is 'undefined'.
AC	screening_id	The unique ID of the screening that triggered a case.
AD	screening_type	The origin of the screening (onboarding or monitoring).
AE	screening_configuration_id	The ID of the screening configuration used to screen or monitor the customer.
AF	screening_configuration_name	The name of the screening configuration used to screen or monitor the customer.
AG	number_of_profiles	The number of profiles returned for a given case.
AH	Sanctions	The number of profile hits for Sanctions.
AI	Warnings	The number of profile hits for Warnings.
AJ	Fitness and probity	The number of profile hits for Fitness and probity.
AK	PEP	The number of profile hits for politically exposed persons (PEPs).
AL	PEP Class 1	The number of profile hits for PEP Class 1.
AM	PEP Class 2	The number of profile hits for PEP Class 2.
AN	PEP Class 3	The number of profile hits for PEP Class 3.
AO	PEP Class 4	The number of profile hits for PEP Class 4.
AP	Adverse Media	The number of profile hits for Adverse Media.
AQ	assignee_name	The name of the case assignee.
AR	time_to_remediate	Time taken to remediate the case, calculated from case creation, until (the final) case decision.
AS	Sanctions risk	The number of profile hits for Sanctions (v3 data).
AT	Political exposure risk	The number of profile hits for Sanctions (v3 data).
AU	Terrorist financing risk	The number of profile hits for Terrorist financing (v3 data).
AV	Proliferation financing risk	The number of profile hits for Proliferation financing (v3 data).
AW	Money laundering risk	The number of profile hits for Money laundering (v3 data).
AX	Regulatory & Reputational risk	The number of profile hits for Regulatory & Reputational risk (v3 data).
AY	Fraud risk	The number of profile hits for Fraud (v3 data).
AZ	account_identifier	Your ComplyAdvantage account ID. This will be the same for all the rows of the export.

Profiles

When a customer is screened against the ComplyAdvantage database and there are matches, the screening results are returned as individual profiles. A profile is a collection of information about a person or company.

The screening and monitoring cases exports give you the total number of profiles broken down by anti-money laundering (AML) types within a case. The profiles export lists all the profiles that were created and can be used to identify which sources are producing a lot of results, and how many of those are true positives.

Each profile is linked to the screening that generated the hit and the associated customer. This enables data to be paired for analysis of the true positive (TP) and false positive (FP) decision ratios, as well as the type and level of risk found during initial customer screening.

Each row in the export represents one profile.

These are the fields in the export:

Column	Field Name	Description
A	profile_id	The unique identifier for each profile generated by ComplyAdvantage.
B	risk_id	The unique identifier for each risk generated by ComplyAdvantage.
C	screening_id	The unique ID of the screening that returned a hit.
D	internal_customer_id	The unique customer ID generated by ComplyAdvantage.
E	external_customer_id	Your unique ID for the customer. This ID is generated by you and is your reference for the customer.
F	person_full_name	The full name of the customer who the profile is matched with, if the customer type is a person.
G	company_legal_name	The legal name of the customer who the profile is matched with, if the customer type is a company.
H	undefined_name	The name of the customer who the profile is matched with, if the customer type is undefined.
I	created_at	The date and time when the initial screening took place.
J	updated_at	The date and time when the profile status was last updated.
K	profile_last_updated_by_id	The unique ID of the user who last updated the profile.
L	profile_last_updated_by_user	The name of the user who last updated the profile.
M	profile_change_type	The type of the latest profile change.
N	profile_status	The latest status of a profile. The statuses are: Not Reviewed In Review True Positive False Positive
O	aml_category_list	The list of anti-money-laundering (AML) categories associated with a profile. The categories are: Sanctions Warnings Fitness and probity Politically exposed persons (PEPs) Adverse media
P	aml_source_list	The list of sources associated with the corresponding AML category for a given profile (for example: OFAC).
Q	risk_type_list	The list of risk types associated with the profile.
R	account_identifier	Your ComplyAdvantage account ID. This will be the same for all the rows of the export.
S	screening_type	The type of Screening: Screening or Monitoring.
T	screening_configuration_id	The unique ID of the screening configuration used.
U	screening_configuration_name	The name of the screening configuration used.
V	is_muted	A boolean value indicating whether the profile was muted at the time of screening: TRUE or FALSE.
W	has_alerted	A boolean value indicating whether the profile has alerted in this screening: TRUE or FALSE.
X	matched_profile_name	The name of the matched profile.
Y	match_types	The types of matches found for the profile.
Z	match_score	The confidence score (1-100) of the match for the profile.
AA	screening_configuration_version	The version of the screening configuration used.
AB	alert_id	The unique ID of the alert raised for the profile.
AC	case_id	The unique ID of the case that the alert belongs to.

Transaction Monitoring:

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: