Bring across existing CDD refresh dates
When you move clients to First AML from another system, you can now tell us when each one was last verified. Their CDD refresh dates then follow your existing schedule, instead of every migrated client becoming due on the same day.
Set the optional lastVerifiedOn field on EntityDetailsInput or IndividualDetailsInput when calling createCase or addIndividualsToCase.
- Format: a date in
YYYY-MM-DDformat. The date you send is the date we store; no timezone conversion is applied. - New profiles only: the date sets the CDD refresh start date when a profile is created. If the profile already has CDD refresh dates, the value is ignored.
- Not a verification: the date doesn’t change the verification status. Verification checks still need to be run as normal, and they won’t move the CDD refresh date you supplied.
- Optional: if you leave it out, nothing changes. The CDD refresh date is set when the profile first passes verification.
mutation {
createCase(input: {
organizationId: "your-organization-id"
officeId: "your-office-id"
initialState: DRAFT
rootEntity: {
type: PRIVATE_COMPANY
tradingName: "Example Holdings Ltd"
lastVerifiedOn: "2025-05-10"
}
individuals: [{
preferredName: { firstName: "Alex", lastName: "Sample" }
needsVerification: true
lastVerifiedOn: "2025-08-01"
}]
}) {
... on CaseInformation { caseId }
... on ValidationErrors { errors { message fieldPath } }
}
}