Apply Authorization Control Screening Results via Integration

This feature introduces inbound support for authorization related to control data, whereas previously only outbound integration was available. You can now send data inbound on the Trade Transaction Line and Declaration Line using either XML integration or the REST API. The Authorization field is supported for inbound integration in Control Screening Results, Other Control Screening Results, and Sanction Screening Results.

Authorization data can be sent by specifying either the table’s primary GID key or a unique key composed of multiple fields. If you provide the primary GID (for example, the primary GID for Control Screening Results) and the authorization string, GTM will directly update the authorization. If the GID is not provided, GTM will identify the record to update based on other unique fields:

• Control screening results - (gtm_transaction_line_gid, gtm_control_type_gid, control_code, involved_party_qual_gid)
• Other control screening - (gtm_transaction_line_gid, gtm_control_type_gid, control_code)
• Sanction control screening - (gtm_transaction_line_gid, gtm_control_type_gid, control_code)

Business Benefit: This feature allows you to automate updates to control authorizations from external systems, improving data accuracy, reducing manual effort, and enabling faster, more efficient compliance processes.

Steps to Enable and Configure

You don't need to do anything to enable this feature.