Validation classes
Available classes
ℹ️ Use the HarmoneyDataValidation class wherever possible.
| Class | Type(s) | Info | Required module |
|---|---|---|---|
| AddressOutsideEU | AML | Ensures the dossier has an address outside of the EU. | AML |
| AdvisorDataAvailable | FSPC | Enabled when role is INVESTOR or all flow steps (except SIGN) are filled. | - |
| AdvisorDataSigned | FSPC | Enabled when the SIGN step is filled. | - |
| AMLCompleted | DST | Ensures that the AML questionnaires are completed. | AML |
| AssigneeHasRequiredRole | DST | The assignee of the dossier must have a specific role. | - |
| AssociatedIndividualsPoIDApproved | DST | ID of the associated individual needs to be approved before a state transition is possible. | IDENTITY |
| AssociatedIndividualsPoIDNotExpired | DST | ID of the associated individual must not be expired before a state transition is possible. | IDENTITY |
| AssociatedPartiesAreResponsibles | DST | Validates whether all of a Dossier's associated parties that are of certain configured types are responsibles. | INVESTOR_FLOW |
| AssociatedPartiesDocumentsAssessed | DST RBA | Validates that documents of associated parties configured for the given FSP have the correct assessment result (e.g. APPROVED). | PARTY_DOCUMENTS |
| AssociatedPartiesDueDiligenceValidation | DST | Checks that the defined associated parties on a dossier have valid due diligence values. V2 can additionally require a manual assessment when the system result of a parameter matches configured values. | DUE_DILIGENCE |
| AssociatedPartiesHaveAddress | DST | Checks whether all configured associated parties have their address configured. | - |
| AtLeastOneInsuredPerson | DST | Enforces that there is at least one insured person. | INSURED_PERSONS |
| AtLeastOneResponsible | DST | Checks that the dossier has at least one responsible. | INVESTOR_FLOW |
| BackOfficeAssociatedIndividualsPoIDApproved | DST | See AssociatedIndividualsPoIDApproved, but check's the BO approval. | - |
| BackOfficeAssociatedPartiesUBOApproved | DST | Validates whether the UBOs are approved by the BO. | - |
| BackOfficeIdentityApproved | DDPC | Validates whether the individual party's identity BO status is approved. | - |
| BackOfficeRbaScoreCalculated | DST | Evaluates if the Rba Score for the BO of the dossier is available. If it's not available, it will be calculated. | RBA, BACK_OFFICE |
| BackOfficeRbaScoreUpToDate | DST | The RBA score on the dossier must be up-to-date. Note: does NOT return an error if no RBA score is present on the dossier (-> use BackOfficeRbaScoreCalculated). | RBA, BACK_OFFICE |
| BackOfficeRequired | DST | The dossier must be linked to an existing back office. | BACK_OFFICE |
| BackOfficeUboApproved | DDPC | Validates whether the company's UBO status is approved. | - |
| BeneficiaryDataValid | DST | Ensures all beneficiary data is available and valid. | BENEFICIARY |
| ClientBankAccountRequired | DST | Validates if one or more client bank accounts are present. | PARTY_BANK_ACCOUNTS |
| ClientLegalEntityHasUbo | DST | If the client is a Company without type or with type PUBLIC_BODY, PUBLICLY_LISTED or STATE_OWNED, validate whether an UBO is specified. | UBO |
| ClientNonLegalEntityHasOwner | DST | An indivision or partnership must have at least 1 member. | UBO |
| ClientDeclarationUboAndRegistrationRequired | DST | Validates whether the document DECLARATION_UBO_AND_UBO_REGISTRATION is present. | - |
| ClientDocumentRequired | DST | Validates whether certain documents are present on the client. | - |
| ClientDocumentsAssessed | DST RBA | Validates that documents of the client have the correct assessment result (e.g. APPROVED). | PARTY_DOCUMENTS |
| ClientDocumentsFromFlowRequired | DST | Validates if the client documents who are required during the flow are still available on the dossier. | - |
| ClientOutsideBeLicensePreciousMetalTradingRequired | DST | Ensures that a client outside Belgium has a LICENSE_PRECIOUS_METAL_TRADING document. | - |
| CommonCompanyStructure | AML | Ensures the common company structure is defined. | - |
| CoSignerCanSign | FSPC | Enabled when the co-signer can sign. | - |
| DocumentsRequired | DST | Validates whether certain documents are present on the dossier. | - |
| DossierBankAccountDocumentRequired | DST | Ensures that a BANK_VERIFICATION document is present for non-NIHDI services. | - |
| DossierDocumentRequired | DST | Checks if document of certain type(s) are available on the dossier. | - |
| DossierDocumentsAssessed | DST RBA | Validates that documents of a dossier have the correct assessment result (e.g. APPROVED). | DOSSIER_DOCUMENTS |
| DossierIsNotLocked | DST | Validates that there are currently no locks on a dossier. | - |
| DossierOfferOrSignedContractRequired | DST | Validates whether an OFFER or SIGNED_CONTRACT are present on the dossier. | - |
| DossierOfferRequired | DST ADV | Validates whether an OFFER is present on the dossier. | - |
| DossierProductSheetRequired | DST | Validates whether an PRODUCT_SHEET is present on the dossier. | - |
| DossierQuestionAnswersValidation | DST | Checks the validity of question answers of dossier questions (defined by the settings). | - |
| DossierQuestionnairesCompleted | DST RBA | Checks if all mandatory questions in some/all dossier questionnaires are answered. | DOSSIER_QUESTIONNAIRES |
| DossierRelatedPartyRequired | DST | This class enforces that a certain related party is required. | INVESTOR_FLOW |
| DossierTaskRequired | DST | The dossier must have the task module enabled and must have at least one task. | - |
| DossierTasksCompleted | DST | Validates that all required tasks on a dossier are completed before status transition. | TASKS |
| EDDCompleted | RBA | Validates if all required due diligence results are present for the entities used in the RBA configuration. | RBA |
| EDDValid | RBA | Validates if aggregated EDD status is valid (not OPEN or FAILED). This can happen if not yet aggregated or if a provider has a 'FAILED' status. | - |
| FactFindNeedsAnalysisDocumentRequired | DST | Validates whether an FFNA is present on the dossier. | - |
| FlowSignatoryRequired | FSPC | Validates that atleast one signatory is selected on the dossier to sign. | - |
| FormDataGenerated | FSPC | Enabled when the form data is generated. | - |
| HarmoneyDataValidation | DST | See page HarmoneyDataValidation. | - |
| HarmoneyDossierDataValidation | DST FSC | See page DossierDataValidation. | - |
| HarmoneyAssociatedPartiesDataValidation | DST FSC | See page AssociatedPartiesDataValidation. | - |
| HighRiskCountry | AML | Checks if any of the countries of all associated parties of the dossier are present on a list. | - |
| IdentifinChecked | RBA | Checks if the IDENTIFIN is available when there was no face-to-face meeting. | - |
| IdentityComplete | ID | Validates whether the given identity is complete. | IDENTITY |
| IdentityDocumentAvailable | ID | Validates whether identity documents are valid. | IDENTITY |
| IdentityDocumentsPresent | DST | Checks if the identity documents are available on the client (also for the responsible if used in the flow). | IDENTITY |
| InsuranceIbanRequired (deprecated) | DST | Deprecated, replace with HarmoneyDossierDataValidation. Checks whether the insurance's IBAN is present. | - |
| InsurancePremiumIsPositive (deprecated) | DST | Deprecated, replace with HarmoneyDossierDataValidation. Ensures the insurance's premium is filled and a positive number. | - |
| InvalidStatusTransition | DST | A generic completeness check on a state transition using the Dossier Filter. | - |
| InvestmentHasAccount | DST | Makes sure that the dossier has accounts. | DOSSIER_BANK_ACCOUNTS |
| InvestorDataIsConfirmed | FSPC | Enabled when the investor data is confirmed. | - |
| LegalEntityAtLeastOneOwner | UBO | Client of type LegalEntity must have at least one owner if it's NOT publicly listed. | UBO |
| MainResponsibleOrGoalsConfirmed | FSPC | Enabled when the current person is the main responsible or the goals are confirmed or signed. | - |
| NaceCodeRequired | DST | Validates whether a company client has its NACE code filled. | - |
| NoDuplicateResponsibles | DST | This class enforces that a responsible isn’t added twice. | INVESTOR_FLOW |
| NonIndividual | UBO | Ensures the UBO is not an individual. | UBO |
| NonLegalEntityAtLeastOneOwner | UBO | An indivision or partnership must have atleast 1 member. | UBO |
| NonResponsibleAssociatedIndividualIdentitiesComplete | DST | Ensures that all relevant non-responsible individuals have completed identities. | - |
| NotConfirmedNorSigned | FSPC | Enabled when the flow is neither confirmed nor signed. | - |
| NotSigned | FSPC | Enabled when the flow is not signed. | - |
| NoUndefinedDueDiligence | DST | Ensures that there are not undefined DD checks. | DUE_DILIGENCE |
| RbaEscalatedNoAdvisor | DST | Ensures an advisor cannot proceed a dossier with escalated RBA. | RBA |
| RbaResultValidation | DST | Validation on the RBA result based on the provided settings. | RBA |
| RbaScoreCalculated | DST | RBA score should be calculated before a state transition is possible. | RBA |
| RbaScoreUpToDate | DST | RBA score should be up to date before a state transition is possible. | RBA |
| ResponsiblePEP | AML | Checks whether any of the responsibles is a PEP. | AML |
| SecurityCheckDataProvided | DST | Makes sure that the data for the security check is present. | - |
| StatusTransitionClientDocumentRequired | DST | Checks if documents of a certain type(s) are available on the party. | - |
| SuspiciousCircumstances | AML | Checks whether there are suspicious circumstances. | AML |
| TransitionByConfiguredRoleValidation | DST | Only a user with the configured role can do this status transition (applicable for all or configured dossier services). | - |
| UboApproved | DST RBA | Ensures all UBOs are approved. | UBO |
| ValidateDifferentReviewers | DST | This classes enforces the 4-eyes principle which enforces a different reviewer. Important: this validation requires the actions AddDossierReview and ClearDossierReview on the impacted statuses. | - |
| ValidResponsibilityMatrix | DST | Ensures a valid responsibility matrix. | INVESTOR_FLOW |
Note: There also customer-specific classes available. However, those are made to specifications and are documented in the customer requirement pages on Confluence.