addComplianceRequirement

Description
This transaction creates a new compliance requirement, enabling companies to address regulatory requirements For example, a compliance requirement could be created to require that a customer service representative verify a client's date of birth. This transaction enables companies to identify the documents required to prove that the client has met the compliance requirement.
Web Services
Operation name: addComplianceRequirement
Service name: DWLBusinessServices
Example
Add a new compliance requirement, Verifying Contact Information for ABC Bank that requires verification of a client's residential address using at least two different pieces of identification, such as a driver's license or a utility bill.
Usage information

The compliance target to be validated must be one of the party details stored in the system, such as a client's residential address.

There is no limit to the number of compliance documents used to validate a compliance requirement.

Preconditions
Not applicable
Mandatory input
  • ComplianceType
  • One or more ComplianceTargetBObj
  • One or more ComplianceDocumentBObj
Inquiry levels
Not applicable
Filter values
Not applicable
Transaction behavior
Each compliance requirement is uniquely defined by the ComplianceType of the ComplianceRequirementBObj and the ComplianceTargetType of the ComplianceTargetBObj. If a ComplianceRequirementBObj already exists with the values provided for these elements, the addComplianceRequirements transaction will fail.

If the EffectiveDate is not provided, the current system date is used by default.

Request message

<TCRMTxType> addComplianceRequirement

<TCRMTxObject> ComplianceRequirementBObj

<TCRMObject> ComplianceRequirementBObj

with additional mandatory business objects:
Response objects
ComplianceRequirementBObj
with additional mandatory business objects:
Special note
Not applicable