Grid Reporting data export glossary
This glossary provides definitions for the columns and data in Grid Reporting.
This glossary defines the data included in Grid Reporting export files to help you understand the contents of each export.
Note
See the Grid Data topics for risk event and PEP code definitions.
Alerts by entity
Summarizes alert activity by matched entity, enabling entity‑level analysis of alert volume across screening batches.
Column | Description |
|---|---|
| The date a batch was created and submitted for processing. |
| A numeric identifier assigned to a batch submission. Batch IDs are unique within a Grid environment, for example, US or EU. |
| A unique, Grid‑specific firm identifier that facilitates compatibility with legacy data. Represents the same organizational unit as |
| The final alert count reported for an entity.
|
| The date associated with an alert count. |
| The entity name associated with an alert count.
|
| The number of decision-level alerts for an entity. |
| A unique numeric identifier for an entity within the Grid database. |
| A human-readable name corresponding to a |
| An alphanumeric identifier for a firm. |
| The name corresponding to |
| The logic version applied to aggregate the exported data, supporting traceability and consistency across reports. |
| The number of match-level alerts generated for an entity by Grid. |
Alerts by event
Aggregates alert counts by risk or event category, providing visibility into which risk types are driving alerts.
Column | Description |
|---|---|
| The date a batch was created and submitted for processing. This value is synonymous with |
| A numeric identifier assigned to a batch submission. Batch IDs are unique within a Grid environment, for example, US or EU. |
| A unique, Grid‑specific firm identifier that facilitates compatibility with legacy data. Represents the same organizational unit as |
| The final alert count reported for an entity.
|
| The date associated with an alert count. |
| The risk or event code associated with an alert.
|
| The description of the risk or event code associated with an alert. A human-readable description corresponding to |
| The number of alerts generated for a risk event. |
| A human-readable name corresponding to a |
| An alphanumeric identifier for a firm. |
| The logic version applied to aggregate the exported data, supporting traceability and consistency across reports. |
| The number of match-level alerts generated for an entity by Grid. |
| A three‑letter code representing a broad category of risk, for example, money laundering or terrorism. See Grid risk event codes for more information. |
| A description of the risk category associated with an |
| The date a batch was created and submitted for processing. This value is synonymous with |
Alerts by source
Groups alerts by originating data source or list, supporting source‑level analysis of alert generation.
Column | Description |
|---|---|
| The date a batch was created and submitted for processing. |
| A numeric identifier assigned to a batch submission. Batch IDs are unique within a Grid environment, for example, US or EU. |
| A human-readable name corresponding to a |
| An alphanumeric identifier for a firm. |
| The logic version applied to aggregate the exported data, supporting traceability and consistency across reports. |
| The published list, for example, a sanctions or watchlist, from which entity or event data is derived. |
| The number of match-level alerts generated for an entity by Grid. |
| The published source from which entity or event data is extracted. |
Analyst decision audit
Provides an audit trail of Analyst Review decisioning activity, including inquiry inputs, matched entities, scores, and review outcomes.
Column | Description |
|---|---|
| Known addresses linked to a matched entity |
| The date a batch was created and submitted for processing. |
| A numeric identifier assigned to a batch submission. Batch IDs are unique within a Grid environment, for example, US or EU. |
| A unique, Grid‑specific firm identifier that facilitates compatibility with legacy data. Represents the same organizational unit as |
| A list of cities associated with a matched entity’s addresses. |
| A list of countries associated with a matched entity’s addresses. |
| An alphanumeric, client-defined identifier used for reporting purposes. |
| A client‑defined identifier used for tracking purposes. |
| A risk categorization code used by Grid to group alerts into ranked priority categories: Critical (C), Valuable (V), Investigative (I), or Probative (P). Alerts that cannot be categorized may be classified as Unspecified (U). |
| A list of dates of birth associated with a matched entity. |
| The type of entity, either a person or an organization, represented in Grid. |
| A three‑letter code representing a broad category of risk used by Grid to organize risk data. |
| A human-readable name corresponding to a |
| An alphanumeric identifier for a firm. |
| A flag indicating whether an inquiry searched all available jurisdictions.
|
| A unique numeric identifier for an entity within the Grid database. |
| The name corresponding to |
| The city value submitted for an inquiry. |
| The country value submitted for an inquiry. |
| The address value submitted for an inquiry. |
| The postal code value submitted for an inquiry. |
| The state or province value submitted for an inquiry. |
| The age value submitted for an inquiry. |
| The date of birth value submitted for an inquiry. |
| A numeric identifier assigned to an inquiry. Inquiry IDs are unique within a firm. |
| The name submitted as part of an inquiry, represented in UTF‑8 format. |
| The logic version applied to aggregate the exported data, supporting traceability and consistency across reports. |
| The confidence score generated by the AI matching process. |
| A numeric score representing the strength of the match between an inquiry and a Grid profile. |
| The current status of a match within Grid. |
| The date of the most recent event occurrence. |
| A PEP rating with associated dates. |
| The PEP type and level, represented as a pipe‑delimited value. |
| An indicator of whether a search was performed as an inquiry or for monitoring purposes. |
| A list of states or provinces associated with a matched entity’s addresses. |
Audit data
Delivers a comprehensive audit record of screening activity, decisioning, and alert lifecycle data across inquiries and batches.
Column | Description |
|---|---|
| Known addresses linked to a matched entity |
| The high-level alert state for a match, for example, active or purged. |
| The timestamp reflecting when a batch finished processing. |
| The date a batch was created and submitted for processing. |
| A numeric identifier assigned to a batch submission. Batch IDs are unique within a Grid environment, for example, US or EU. |
| A unique, Grid‑specific firm identifier that facilitates compatibility with legacy data. Represents the same organizational unit as |
| A list of cities associated with a matched entity’s addresses. |
| Unique identifier for a Client Alert Decisioning match originating from an iList. |
| Unique identifier for a Client Alert Decisioning match record. |
| Human‑readable description for the Client Alert Decisioning decision reason. |
| Unique identifier for a Client Alert Decisioning review instance of an inquiry or match. |
| Username for the last user to modify the Client Alert Decisioning record itself, for example, status, notes, or decision. |
| A list of countries associated with a matched entity’s addresses. |
| An alphanumeric, client-defined identifier used for reporting purposes. |
| A risk categorization code used by Grid to group alerts into ranked priority categories: Critical (C), Valuable (V), Investigative (I), or Probative (P). Alerts that cannot be categorized may be classified as Unspecified (U). |
| The name of the user who made or was assigned to the decision an alert in Client Alert Decisioning. |
| Free‑text notes associated with a Client Alert Decisioning decision. |
| A list of dates of birth associated with a matched entity. |
| A unique numeric identifier for an entity within the Grid database. |
| The name of an entity in an iList when the audit record involves an iList‑related match or suppression. |
| The type of entity, either a person or an organization, represented in Grid. |
| A three‑letter code representing a broad category of risk used by Grid to organize risk data. |
| A human-readable name corresponding to a |
| An alphanumeric identifier for a firm. |
| A flag indicating whether an inquiry searched all available jurisdictions.
|
| A status code representing the processing state of a batch within Client Alert Decisioning decisioning. |
| The timestamp when an Client Alert Decisioning alert was created. |
| The status of a match in Client Alert Decisioning. |
| Client Alert Decisioning workflow status for a match, for example, open or in review. |
| The city value submitted for an inquiry. |
| The country value submitted for an inquiry. |
| The address value submitted for an inquiry. |
| The postal code value submitted for an inquiry. |
| The state or province value submitted for an inquiry. |
| The age value submitted for an inquiry. |
| The date of birth value submitted for an inquiry. |
| A numeric identifier assigned to an inquiry. Inquiry IDs are unique within a firm. |
| The name submitted as part of an inquiry, represented in UTF‑8 format. |
| Client-created, free-text notes for an inquiry. |
| The logic version applied to aggregate the exported data, supporting traceability and consistency across reports. |
| The confidence score generated by the AI matching process. |
| A numeric identifier representing an entity in an iList when the export includes an iList‑based match or suppression. |
| Free‑text notes specific to a match, typically entered during review and decisioning. |
| A numeric score representing the strength of the match between an inquiry and a Grid profile. |
| The current status of a match within Grid. |
| The date of the most recent event occurrence. |
| A PEP rating with associated dates. |
| The originating source, system, list, or provider for a PEP designation. |
| The PEP type and level, represented as a pipe‑delimited value. |
| A unique alphanumeric identifier for a curated profile associated with a person or organization. |
| An indicator of whether a search was performed as an inquiry or for monitoring purposes. |
| A concatenated list of event sources. This value is null for iList matches. |
| A list of states or provinces associated with a matched entity’s addresses. |
Data quality summary
Summarizes the completeness of inquiry data submitted for screening, highlighting usage of optional enrichment fields over time.
Column | Description |
|---|---|
| A unique, Grid‑specific firm identifier that facilitates compatibility with legacy data. Represents the same organizational unit as |
| The inquiry submission date. |
| A human-readable name corresponding to a |
| An alphanumeric identifier for a firm. |
| A flag indicating whether aggregated values reflect:
|
| The logic version applied to aggregate the exported data, supporting traceability and consistency across reports. |
| The number of organization inquiries included in the reporting period. |
| The number of organization inquiries submitted with a populated address line. |
| The number of organization inquiries submitted with a populated city value. |
| The number of organization inquiries submitted with a populated country value. |
| The number of organization inquiries that specified global search. |
| The number of organization inquiries submitted with inquiry notes. |
| The number of organization inquiries submitted with a populated postal code. |
| The number of organization inquiries submitted with a populated state or province value. |
| The number of person inquiries included in the reporting period. |
| The number of person inquiries submitted with a populated address line. |
| The number of person inquiries submitted with a populated age value. |
| The number of person inquiries submitted with a populated city value. |
| The number of person inquiries submitted with a populated country value. |
| The number of person inquiries submitted with a populated date of birth value. |
| The number of person inquiries submitted with a populated age or date of birth value. |
| The number of person inquiries that specified global search. |
| The number of person inquiries with inquiry notes. |
| The number of person inquiries submitted with a populated postal code. |
| The number of person inquiries submitted with a populated state or province value. |
| The total number of inquiries within a reporting period. |
Ops review
Presents operational screening metrics such as batch volume, inquiry counts, matches, and alert outcomes for monitoring and capacity analysis.
Column | Description |
|---|---|
| The count of batches that completed processing during a specified time period. |
| The count of batches submitted during a specified time period. |
| A numeric identifier assigned to a batch submission. Batch IDs are unique within a Grid environment, for example, US or EU. |
| A unique, Grid‑specific firm identifier that facilitates compatibility with legacy data. Represents the same organizational unit as |
| The total number of entities alerted from client decisions, such as Client Alert Decisioning. |
| The count of entity matches that were accepted. |
| The count of entity matches that were alerted. |
| The count of entities that matched against submitted inquiries. |
| A human-readable name corresponding to a |
| An alphanumeric identifier for a firm. |
| The count of individual inquiries that produced one or more matches. |
| The count of individual inquiries submitted during a specified time period. |
| The logic version applied to aggregate the exported data, supporting traceability and consistency across reports. |
| The month extracted from |
| The total number of entities alerted by Grid. |
| An indicator of whether a search was performed as an inquiry or for monitoring purposes. |
| The date a batch was created and submitted for processing. This value is synonymous with |
| The year extracted from Used to group operational metrics by calendar year for trend and capacity analysis. |
PEP data
Reports PEP screening results, including PEP classifications, jurisdictions, and related alert counts.
Column | Description |
|---|---|
| Represents the number of unique Grid matches associated with a specific PEP attribute combination. |
| The date a batch was submitted for processing. |
| The country associated with a PEP designation or classification. |
| The type of entity, either a person or an organization, represented in Grid. |
| An alphanumeric identifier for a firm. |
| A descriptive level associated with a PEP classification. Indicates the degree or scope of political exposure. |
| A rating value associated with a PEP classification, used to indicate relative PEP risk. |
| A classification code identifying the type of PEP exposure, such as the nature of the political role or relationship. |
Screening overview
Provides a detailed, row‑level view of screening results, combining inquiry data, match details, alerts, decisioning, and audit fields.
Column | Description |
|---|---|
| The delivery line of an inquiry address. Displays the street address submitted with the inquiry used for screening. |
| A list of all addresses associated with an inquiry. Displays all address values submitted with the inquiry. |
| The age of the inquiry subject. Shows the age value provided during the inquiry. |
| The AI agent’s confidence score for a match, expressed as a value between 0 and 1. Represents the AI confidence score associated with a level‑one alert. |
| The date an alert was created. Indicates when the alert associated with the match was generated. |
| A unique identifier assigned to an alert. Identifies the alert generated for the inquiry or match. |
| The timestamp when alerts were generated for a batch. Represents the alert creation time at the batch level. |
| A numeric identifier assigned to a batch submission. Batch IDs are unique within a Grid environment, for example, US or EU. |
| A label indicating the how the batch was submitted, for example, web, system, or portfolio monitoring. |
| A unique, Grid‑specific firm identifier that facilitates compatibility with legacy data. Represents the same organizational unit as |
| The timestamp when final processing completed. Represents the ultimate response file timestamp for the batch. |
| A Salesforce identifier used to link screening activity to a specific client contract. |
| The country associated with an inquiry address. |
| A risk categorization code used by Grid to group alerts into ranked priority categories: Critical (C), Valuable (V), Investigative (I), or Probative (P). Alerts that cannot be categorized may be classified as Unspecified (U). This value is null for iList matches. |
| The inquiry subject's date of birth. |
| The date a match was sent to Client Alert Decisioning. Populated only when Client Alert Decisioning is enabled. |
| A descriptive explanation for an Analyst Review decision. |
| The folder name associated with an entity item. This value is null for iList matches. |
| The type of entity, either a person or an organization, represented in Grid. |
| A descriptive category for a risk event. This value is null for iList matches. |
| A code representing a risk event category. Uses |
| A unique identifier for a risk event. This value is null for iList matches. |
| The folder name associated with an event item. This value is null for iList matches. |
| A description of the event subcategory or stage. This value is null for iList matches. |
| A code representing a risk event subcategory. This value is null for iList matches. |
| A descriptive name associated with a |
| A numeric identifier for the firm under which screening occurred. |
| A unique numeric identifier for an entity within the Grid database. |
| The name associated with an entity record in Grid. This value is null for iList matches. |
| The date a Client Alert Decisioning alert was closed. Populated only when a Client Alert Decisioning alert review status exists. |
| The review status of a Client Alert Decisioning alert. Indicates whether the alert is alerted, not alerted, or purged. |
| A status code representing the processing state of a batch within Client Alert Decisioning decisioning. |
| The date a Client Alert Decisioning match was closed. Populated only when a Client Alert Decisioning match status exists. |
| A code representing the Client Alert Decisioning match decision. Displays the client‑generated decision code. |
| A description of the Client Alert Decisioning match decision reason. Provides context for the Client Alert Decisioning decision outcome. |
| The status of a match in Client Alert Decisioning. |
| The user assigned to review a match in Client Alert Decisioning. Identifies the analyst responsible for the review. |
| The timestamp when the initial response file was generated. Represents the first response output for the batch. |
| A numeric identifier assigned to an inquiry. Inquiry IDs are unique within a firm. |
| The name submitted for screening. Uses the UTF‑8 version of the inquiry name when available. |
| The current status of an inquiry. Indicates screening or alerting outcomes such as alerted, not alerted, loaded, or purged. |
| A numeric identifier representing an entity in an iList when the export includes an iList‑based match or suppression. |
| iList entry name. |
| The timestamp when the matching engine completed processing. |
| A numeric score representing match strength. Shows the score calculated between the inquiry and matched entity. |
| The current status of a match within Grid. |
| The month extracted from |
| The total number of alerts generated. Reflects Grid or Client Alert Decisioning alerts based on client configuration. |
| The number of submitted matches. Represents the count of KYC matches identified. |
| The number of accepted Grid alerts. Represents system‑generated alert acceptances. |
| The number of inquiries in a batch. Shows inquiry volume per batch. |
| The portfolio monitoring date. Indicates when portfolio monitoring activity occurred. |
| The year extracted from the portfolio monitoring date. Used for portfolio monitoring trend analysis. |
| The postal code associated with an inquiry address. Shows the postal code submitted with the inquiry. |
| The province or state associated with an inquiry address. Displays the state or province submitted with the inquiry. |
| The date a batch was purged. |
| A code representing an Analyst Review decision reason. |
| The Grid database region. Identifies whether data resides in the US or EU region. |
| A customer‑provided reporting identifier. Used to align screening results with customer reporting systems. |
| A unique alphanumeric identifier for a curated profile associated with a person or organization. |
| An indicator of whether a search was performed as an inquiry or for monitoring purposes. |
| The date a batch was created and submitted for processing. |
| The user who submitted a batch. Identifies the user responsible for batch submission. |
| A client‑defined identifier used for tracking purposes. |
| A globally unique batch identifier with region prefix. Derived from region and batch ID. |
| A globally unique inquiry identifier with region prefix. Derived from region, batch ID, and inquiry ID. |
| A globally unique match identifier with region prefix. Derived from region, batch ID, inquiry ID, and entity ID. |
| The year extracted from Used to group operational metrics by calendar year for trend and capacity analysis. |
Search stats summary
Aggregates firm‑level search activity statistics, showing search volume and channels over a given time period.
Column | Description |
|---|---|
| The date a firm search record was created. Represents the date on which search activity was recorded for the firm, used to aggregate search statistics over time. |
| A human-readable name corresponding to a |
| An alphanumeric identifier for a firm. |
| The logic version applied to aggregate the exported data, supporting traceability and consistency across reports. |
| The channel through which a search was initiated. Identifies the originating channel for search activity, such as web or system‑initiated searches. |
| The count of search records within a specified time period. Represents the total number of firm search records captured for the reporting period. |