Skip to main content
intelID intelligence platform logo
Menu

Corporate risk and compliance

AML compliance screening support for New Zealand teams

Customer and counterparty due diligence across licensed company, ownership, property, security interest, insolvency and credit data, with an audit record produced by the platform on every enquiry.

Due diligence is judged on the record, not the result

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.

A comprehensive New Zealand media archive of newspapers, magazines and public notices, and published court, tribunal and regulatory decisions, cover the reported and adjudicated history of a counterparty.

Also available: individual and commercial credit checks from Centrix and Equifax, and sanctions, watchlist, politically exposed person and adverse media screening. Both are set out on the data sources page.

The searches a due diligence file runs

A counterparty file usually starts with a company and director search to establish the entity, its status, its officers and the shareholding recorded behind it. Where the transaction involves real property, a property and title search confirms registered ownership and the interests already registered against it. A PPSR search shows security interests over personal property, and an insolvency search shows whether a formal process is already on foot.

For the individuals behind an entity, corroboration is the work rather than verification in a formal sense. An identity confirmation enquiry tests whether the person presenting the file is consistent across several licensed records, and an address history search establishes the address position over time rather than the address a customer supplied. Higher-risk files add asset searches where the source of funds needs testing.

The registers behind a counterparty check

Entity and officer data comes from the Companies Office register maintained by MBIE. Registered ownership and interests in land come from Land Information New Zealand. Security interests in personal property come from the Personal Property Securities Register, and formal insolvency events from the Insolvency and Trustee Service. Each source and the legal basis attaching to it is listed on the data sources page.

The limits a reporting entity has to respect

Due diligence obligations do not displace the Privacy Act 2020. Collection must be for a lawful purpose connected with the entity's functions and limited to what that purpose needs, so the enquiry should track the risk being tested rather than everything the platform can reach. Where credit reporting information is involved, the Credit Reporting Privacy Code 2020 adds its own restrictions on access and use, and the declared basis is recorded against the query. A screening or registry result is an input to a risk decision, not a finding about a person.

An onboarding and review workflow

  1. Declare the authorised purpose for the file, for example customer due diligence on a new counterparty.
  2. Resolve the entity: registration, status, directors, shareholders, registered office and address for service.
  3. Trace ownership through related entities until the individuals recorded behind the structure are identified.
  4. Corroborate those individuals against address and identity records rather than relying on the details supplied.
  5. Add the enhanced layer where the risk rating calls for it: property and title, PPSR, insolvency and asset position.
  6. Export the consolidated result and the audit record into the customer file, dated, so the periodic review has a baseline to compare against.

A worked example, in outline

A new corporate counterparty is presented for onboarding. The company search returns a recent change of directors and a holding company as majority shareholder. A second search on the holding company identifies the individuals recorded behind it, one of whom is also recorded against a company subject to an insolvency event. A PPSR search returns registered interests over the trading company's plant. None of that determines the risk rating. It is passed to the compliance officer with the dated audit record so the enhanced due diligence decision is made on evidence rather than on the customer's own description. No customer, entity or outcome is described here.

Controls that match your own obligations

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.

Subject data is not used for marketing, is not resold, and is not exposed to public indexing. How a trace runs end to end is on the skip tracing page, the workflow on the platform page, every integrated source and its legal basis on the data sources page, hosting and encryption on the security page, and the statutory position on the compliance page. Pricing is a monthly subscription plus a per-search fee, published on the pricing page. intelID treats the audit record as part of the search rather than an optional report.

Questions from compliance functions

Can intelID support AML compliance screening in New Zealand?

intelID supports customer and counterparty due diligence by consolidating licensed company, director, property, security interest, insolvency and credit reporting data, with an audit record for every enquiry. Individual and commercial credit checks and sanctions, watchlist, PEP and adverse media screening are available as selectable sources.

Does it identify beneficial ownership?

It provides the registry and related-entity data needed to trace ownership through New Zealand companies and to identify the individuals recorded behind them. The judgement about beneficial ownership remains with your compliance officer.

Can the audit trail be used as AML/CFT record keeping evidence?

Every query is logged with the user, the timestamp, the sources read and the declared authorised purpose, which supports your own record-keeping obligations. You remain responsible for retaining records in the form your supervisor requires.

How is access controlled across a compliance team?

Accounts are issued to named, verified individuals and access is granted by role, so analysts, compliance officers and the MLRO can hold different reach across the integrated sources.

Which searches does an onboarding check normally use?

Company and director searches to establish the entity and the people recorded behind it, property and title searches where real property is part of the transaction, PPSR searches for registered security interests, insolvency searches for formal processes already underway, and identity corroboration for the individuals presenting the file.

Does intelID make a risk decision for us?

No. It returns licensed information from named sources with an audit record. The customer risk rating, the enhanced due diligence decision and any reporting obligation remain with your compliance function.

Can we evidence periodic review with it?

Yes. Re-running the same enquiry on an existing counterparty produces a dated record of what was checked and what the sources held on that date, which is the evidence a periodic review file usually lacks.

What does it cost for a compliance function?

Pricing is a monthly subscription plus a per-search fee. Team is $99 per month + GST for up to three users, then $25 per additional user + GST to a maximum of ten. Enterprise covers larger functions and bespoke terms.

Access and pricing

Accounts are issued to named, verified individuals only, with reach set by role, so an analyst, a compliance officer and the MLRO need not hold the same access. Pricing is a monthly subscription plus a per-search fee, published on the pricing page, and access is requested through the request access page.

Request access for your compliance function

Tell us about your entity and the checks your team runs, and we will get named accounts set up with the right reach.