> For the complete documentation index, see [llms.txt](https://docs.complycube.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.complycube.com/documentation/changelog/2022/20-may.md).

# 20 May: Compliance Updates

Expanding Compliance Coverage. Product updates for AML list coverage, monitoring notifications, Multi-Bureau checks, service quotas, rate limits, and sandbox scenarios.

This release introduced new compliance checks, additional monitoring capabilities, and API improvements to help customers scale integrations with greater flexibility.

### **New features**

* Extended [list coverage](/documentation/product-guides/watchlist-pep-and-adverse-media/aml-screening-check/lists-included.md) for [AML Screening Checks](/documentation/product-guides/watchlist-pep-and-adverse-media/aml-screening-check.md).
* Email notifications have been added to **Continuous Monitoring** for AML Screening, allowing businesses to stay informed of client status changes over time. This feature complements existing webhook events, providing another channel to ensure important updates are never missed.
* Added [Multi-Bureau Check](/documentation/product-guides/identity-verification/multi-bureau-check.md) support via the API and Portal.

### **Improvements**

* Mobile SDKs updated with better localization and camera guidance improvements.
* Extended AML Screening coverage to additional international watchlists and jurisdictions.
* Introduced [Service Quota](/documentation/api-reference/service-quota.md) to our APIs.
* Increased API [rate limits](/documentation/api-reference/rate-limits.md) for the sandbox environment.
* Added more [test scenarios](/documentation/integration-resources/testing-data.md) to the sandbox environment.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.complycube.com/documentation/changelog/2022/20-may.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.