Skip to main content

Configurations

What a KYB file has to establish is not one list. Onboarding a supplier and reviewing a counterparty ask for different facts about the same company, so that list is stored as data and a case is opened under one of them.

The configurations list with a row per configuration, its description and which is the default
One row per configuration, with one of them marked as the default.

The Fields tab on a case is the dossier a configuration produces: every field it asked for, the value that stands, and where the value came from.

Writing one​

The top of the configuration form: name, what it is for, and the use by default checkbox
The description is shown wherever this configuration is chosen, so it is worth writing.

Use this by default pre-selects it on every new search. Exactly one configuration can hold that.

The form is laid out as the three populations it actually has, in ascending order of cost.

Identity: free, and not selectable​

These values arrive with the registry lookup every case already pays for, so omitting one would hide a fact rather than avoid a cost. They are listed so you can see what you get for nothing, which is what stops a custom field being added for the share capital.

Ownership: selectable, on by default​

Shareholders, beneficial owners, parent company. These are typed as ownership, which is the type that carries structure: the dossier renders one row per holder and one column per source, so a holder one source has never heard of is a blank cell, and a stake two sources disagree about is two numbers on one line. See Ownership is a field set, not a tab.

From the accounts: the figures a filed annual account carries​

No register hands these over as data, so each has to be gone and got: a document has to be ordered or uploaded, and read with a schema. Each one therefore carries a coverage note saying which of your extraction schemas would actually answer it.

Financial fields with coverage notes underneath saying which extraction schemas cover them
Advisory, never a gate: you may well be about to write that schema.

Custom fields: whatever else this file has to answer​

A custom field being added, with a label, the name it has in documents, a type and a what to look for hint
The label is what a person reads. The name is what a schema and a research pass answer under.
  • Label: what appears on the dossier and in the report.
  • Name in the documents: the key everything joins on. Derived from the label if you leave it, and it is what an extraction schema must call the property and what the research pass will answer under.
  • Type: text, number, date, money, list, or ownership.
  • What to look for: optional, shown next to the gap when nothing on the case answered the field, and used as the hint a research pass is given.

The report block​

The bottom of the form decides what a report issued under this configuration carries: which optional sections, whether every source is shown or only the one that won, and a cover note.

See Report options.

Editing one does not rewrite existing cases​

A case stores both a reference to its configuration and a snapshot of the fields as they were when it was opened. The reference is how you get back to the editable configuration; the snapshot is what this case actually asked for.

When the two diverge, the case's Fields tab says so and offers Update this case. Explicit, because a case that quietly changed what it was asking for is a case whose report you cannot explain.

The notice on a case's Fields tab saying the configuration has changed since the case was opened, with an Update this case button
Your choice, per case.

History​

Every configuration form carries a History section: what it asked for before, when it changed, and who changed it. This is where what did this ask for last month is actually asked.

In this section​