Skip to main content
The AI reviewer runs up to 9 checks per company. This page documents when each check is skipped or marked as failed, plus a diagnostic table for common symptoms.

​
Rules That Apply to All Checks

The following conditions block or skip any check, regardless of type:
  • No rule set configured for the partner — the reviewer has no instructions to run. Nothing executes.
  • Rule set exists but contains no rules — same result, nothing runs.
  • Rule targets a beneficiary type that is not present on the case — the rule is silently skipped. No result is created and the frontend shows nothing for it.
  • Check ran but outcome is not in the accepted outcomes list — the check is marked Unaccepted and the company is Denied (unless an override applies).
  • Unresolved AML flags on the case — even if all checks pass, the reviewer overrides Approve → Flagged and does not complete the case. It stays in the previous status until the flags are resolved manually.
  • Concurrent review attempts — the system locks per company. If two reviews are triggered simultaneously, only one runs; the other is rejected.

​
Check-Specific Skip and Failure Reasons

​
1. Details Comparison (AI / Gemini)

Compares company or person data against a source document using Google Gemini. Skipped when:
  • No data source document type is configured (e.g. no credit bureau, no Companies House report).
  • The configured document type is in settings but no document was uploaded or fetched for this company.
  • The fields to compare data in Settings are not set.
  • The document file is unreadable or corrupted.
  • The Gemini API call fails or times out.
Special failure — “Not Listed”: When checking a beneficiary (e.g. a director), Gemini may report that the person’s name does not appear in the document at all. Whether this counts as a failure depends on how beneficiary_not_found_status is configured in the rule. If not configured, it defaults to Unaccepted.

​
2. AML Check

Checks AML, sanctions, and PEP screening status for the company or a beneficiary. Skipped when:
  • No AML check record exists for the target (company or person).
Failed when:
  • Flags were found and the rule only accepts “No Flags”.
  • The AML check was never performed at all (treated as Unaccepted, not Skipped).

​
3. Identity Verification (IDV)

Checks whether a beneficiary passed KYC. Skipped when:
  • The rule is configured for the main company (IDV only applies to individual people).
  • The beneficiary has no linked client record.
  • The beneficiary’s client has no KYC or identification record.
Failed when:
  • The IDV status is not in the accepted list (e.g. rule requires Approved but the person is Rejected or Pending).

​
4. Address Verification

Checks whether the company’s address was verified. Skipped when: No address verification record exists for the company. Failed when: The status is below the accepted threshold (e.g. rule requires Verified but the result is only Partially Verified).

​
5. Address Audit

Checks the risk level of the company’s address. Skipped when: No address audit record exists. Failed when: The risk level is higher than the rule accepts (e.g. rule accepts up to Medium risk but the result is High).

​
6. Website Audit

Checks the risk level of the company’s website. Skipped when: No website audit record exists. Failed when: The risk level exceeds the configured threshold — same logic as Address Audit.

​
7. VAT Verification

Checks VAT registration validity. Skipped when: No VAT verification record exists. The check defaults to a “Not Checked” outcome, which may or may not be acceptable depending on rule configuration.

​
8. EIN Verification (US Only)

Same as VAT verification but for US EIN numbers. Skipped when: No EIN verification record exists. Defaults to “Not Checked”.

​
9. Proof of Address (POA)

Checks proof of address status for the company or a person. Skipped when: No POA check record exists for the target entity. Failed when: Status is No Match or Not Compared, and the rule requires Match.

​
Quick Diagnostic Guide

For partner-specific rule set configuration, contact the integrations team. For data pipeline issues (why an audit or AML check never ran), contact engineering.