Coverage considerations

AMLOK normalizes information from connected sources and institution-supplied evidence. The fields returned for a request depend on your enabled integrations, product modules, permissions, market, and available history.

​

Check integration and resource coverage

Use the integration status catalog for availability and markets. Review provider coverage, resource coverage, and field mappings for the corresponding data references. A required field defines a valid resource when that resource exists. It does not guarantee that every connected account supplies every resource or optional field. Inspect data_status, missing_fields, and the returned coverage period before using a result.

​

Match evidence to the workflow

​

Permissions and additional sources

Collection, processing, retention, and onward use must follow source permissions and your agreement. Consumer-reporting, credit-bureau, payroll, tax-authority, and property-title workflows require the appropriate sources and permitted purposes. AMLOK supplies evidence, assessments, and risk alerts. Your institution owns borrower outreach, repayment follow-up, money movement, filings, and changes to credit terms through its own systems.

​

Preserve data quality

Keep missing, partial, stale, and conflicting evidence visible in your application. A failed lookup is not a verified no-hit result. Use normalization rules and response conventions to interpret the returned data consistently.