AML compliance screening support for New Zealand teams

A reporting entity is rarely criticised for reaching the wrong conclusion about a customer. It is criticised for being unable to show how the conclusion was reached: which checks were performed, on what date, by whom, and against which sources. That is the gap most compliance functions carry. The screening happens across several tools and a shared inbox, and the evidence of it ends up as a folder of screenshots with no consistent structure.

intelID addresses the enquiry half of that problem. Company registration, directors, shareholders, registered office and filing history come from MBIE and Companies Office data. Ownership can be traced through related entities to the individuals recorded behind them. Property and title data, PPSR registrations and insolvency events provide the enhanced due diligence layer that a higher-risk customer or an unusual transaction requires. Credit reporting data is available where the entity holds a lawful authorised purpose for it under the Credit Reporting Privacy Code 2020.

The output is one consolidated result per enquiry with the sources identified, rather than five exports that an analyst has to reconcile by hand. For onboarding at volume, that shortens the time between a customer being accepted and the file being complete. For periodic review, it makes re-checking an existing counterparty a single task rather than a project. intelID is not a sanctions, PEP or adverse media screening list, and it does not replace one; it covers the New Zealand registry, asset and credit picture that sits alongside those checks.

Compliance teams are held to a standard of demonstrable control, so a tool that quietly allows unlimited access to personal information creates risk rather than removing it. intelID requires an authorised-purpose declaration before results are returned on every search, and records it with the user, the timestamp and the sources queried. The log cannot be edited by the person who created it.

Role-based access lets an MLRO give analysts a narrower reach than senior staff, and allows access to be withdrawn immediately when a person changes role. Data is encrypted in transit and at rest, hosted on Google Cloud Platform, and handled under a vendor security programme benchmarked to SOC 2 Type II providers. Subject data is not used for marketing, is never resold, and is never exposed to public indexing. The full position is set out on the compliance page and the security page.

intelID treats the audit record as part of the search rather than an optional report. Every integrated source and its legal basis is published on the data sources page, the enquiry workflow on the platform page, and pricing, a monthly subscription plus a per-search fee, on the pricing page.