Interpreting the "authorities" response

The "authorities" node delivers both

a human-readable description of the company's signature rights and power of procuration
and, for a wide range of cases, a machine-readable specification of the same information

Examples

Example of CONCLUSIVE signature rights (machine readable)

"authorities": {
    "signatureRights": {
      "status": "CONCLUSIVE",
      "description": "Daglig leder alene. Styrets leder alene.",
      "options": [
        {
          "required": [
            {
              "name": "Lars Leder",
              "dateOfBirth": "1962-02-13",
              "role": "CEO"
            }
          ]
        },
        {
          "required": [
            {
              "name": "Siri Hansen",
              "dateOfBirth": "1973-04-01",
              "role": "CHAIRMAN_OF_THE_BOARD"
            }
          ]
        }
      ]
    },
    "powerOfProcuration": {
      "status": "NOT_SET"
    }
}

Example of IN_CONCLUSIVE signature rights (only human readable)

"authorities": {
    "signatureRights": {
      "status": "IN_CONCLUSIVE",
      "description": "To styremedlemmer i fellesskap. Daglig leder alene. Styrets leder alene."
    },
    "powerOfProcuration": {
      "status": "NOT_SET"
    }
}

Explanations

The "description" element in the response contains the full natural language description of the signature rights, unchanged and on the same format as written in the "Brønnøysundregisteret" data source.

In many cases, the BankID AML service manages to express the same information on a machine-readable format.

The "status" element specifies this categorization:

CONCLUSIVE - The signature rights description is a clear and specific list of alternative sets of people. A machine-readable specification is offered.
IN_CONCLUSIVE - The signature rights description is complex, and a machine-readable specification has not yet been implemented.
NOT_SET - The signature rights or power of procuration has not been specified for the company.

The "options" elements are only included in the response when the status is CONCLUSIVE. The content is a list of signature rights alternatives, where each alternative contains a list of the specific required people. In a future release, this functionality may be extended to express more complex variants.

Understanding the NOT_SET status

NOT_SET means the company has not specified the people with signature rights or power of procuration.

For signature rights in general, the understanding of this should be that the entire board of the company is required when signing documents.

When it comes to power of procuration, NOT_SET means the company has not defined any procuration, and the persons with regular signature rights must handle all signatures.

The "remarks" element. Signature rights may also come with a list of remarks (both in JSON and PDF report).

There are three categories of remark:

EXCEPTIONS_POSSIBLE	There are known exceptions to the rule. A common example is that there exist deputy board members that could sign on behalf of the main board members.
SUPPLEMENTED	The signature rights text is overridden by the system. A common example is if the registered text in Brreg is empty.
INCOMPLETE_DATA	The signature rights text could normally be handled as CONCLUSIVE, but the roles described are not documented. The service will instead return IN_CONCLUSIVE as a fallback.