Introduction

T2A is an Application Programming Interface (API) providing fast, reliable and secure online transactional access to our data sets and validation services.

T2A is comprised of a number of methods which offer our services. These methods may be accessed from your website or application via XML, SOAP or JSON.

This documentation is intended to be used by software developers intending to use one or more of the T2A methods. We provide a simple XML/JSON interface, promising easy integration; we also provide code samples in some popular languages including PHP, "classic" ASP and JavaScript.

General API Guide

API Endpoint & Authentication

T2A offers XML / JSON and SOAP API endpoints to suit your development framework.

API Key Authentication

All T2A methods require authentication using the mandatory input parameter api_key. An API Key must be obtained by signing up. If you've already registered, you can view your API key by logging in.

Your API key should not be disclosed to third parties, and should not be included in web pages; however, other security measures are available to prevent unauthorised use of your account.

Example request URL

Free Test Mode

As an aid to developers during the early stages of integration, every method can operate in a limited test mode, which is free to use.

When in a test mode, the method returns dummy data in an identical form to a real execution. This facility is available to XML, JSON, and SOAP users.

To use test mode, simply set the API key (or a JavaScript key) to test.

Please note that the test mode should only be used for initial connectivity and parsing tests; ensure that your real API key is used on "live" services.

Further details on the free test mode for each method can be found in the detailed documentation for each method.

XML and JSON REST API Overview

https://api.t2a.io/rest

The default XML response is shown below. Note the status and error code:-

<?xml version="1.0"?>
<T2A_Result>
  <mode>normal</mode>
  <status>error</status>
  <error_code>missing_method</error_code>
  <t2a_version_number>1.0.0</t2a_version_number>
</T2A_Result>	
	

The default JSON response is shown below:-

{
  "mode":"normal",
  "status":"error",
  "error_code":"missing_method",
  "t2a_version_number":"1.0.0"
}
	

You can optionally specify a JSONP padding callback function in which the JSON is to be wrapped; the use of the parameter and values callback=myPadding is shown below:-

myPadding({
  "mode":"normal",
  "status":"error",
  "error_code":"missing_method",
  "t2a_version_number":"1.0.0"
});

URL Encoding a GET Request

The JSON and XML API is normally invoked as an HTTP GET request, with parameters included in the query string.

When making a GET request, remember to URL encode the value part of each parameter=value pair.

Here are some common code examples:-

SOAP API

Developers may prefer to use our SOAP XML API, which is a superset of the XML API.

The SOAP XML API is available:-

https://api.t2a.io/soap

The above location allows access to the T2A web services description page; it also allows developers to view the WSDL service description, and to test each method, using an API key.

Using XML, JSON and SOAP Methods

Each service can be executed in a single HTTP or HTTPS request to our servers; there is no requirement to negotiate an access key.

When using XML or SOAP, most methods return data in an XML element which is named (method_name)_res; for example, area_code returns the result in an XML element named <area_code_res>.

Every XML, JSON and SOAP result contains common status, error code and version number components.

Full details on the XML, JSON and SOAP API are available here.

Asynchronous Methods

Most of the services available in T2A are synchronous - they return as quickly as possible with the result.

For some methods, mainly those involving bulk operations, the operation is asynchronous.

Every asynchronous service revolves around the creation of a "job", and the background execution of T2A on that job.

A typical asynchronous service follows these stages:-

1. Create a Job. T2A gives you an encrypted unique job ID. This contains only alphanumeric characters plus underscore and dash.
2. Pass your data into that job.
3. Start the job processing.
4. Read the progress of the job, as a percentage.
5. When that percentage has reached 100, the job is completed.
6. Read or download the processed data from the completed job.

Currently the only asynchronous method is deceased_bulk.

Using Your Account Control Panel

The control panel is used to:-

• Buy credits
• Configure IP address restrictions
• View your transactions
• Download usage statistics

Security

As a T2A customer, you may configure and control the security of your account credits - preventing unauthorised use.

1. Using the control panel, add the IP address(es) of your server(s) which are permitted to use your T2A account. If any IP addresses are in the permitted list, requests from other IP addresses will be denied.
2. When invoking T2A from client-side JavaScript, generate a secure temporary key (we refer to this as a JavaScript key) that can be safely included in your HTML mark-up, using the javascript_key method. This key expires after a short period, and is restricted to only function on your specified domain, and can optionally be configured to only operate for the user's IP address.
3. All methods can be optionally invoked via HTTPS.

Code Examples

Code examples for the area_code method in PHP and jQuery:

PHP

<?php
// Get text from query string or set to empty
$text = isset($_GET['text']) ? $_GET['text'] : '';

$url = 'https://api.t2a.io/rest/?'
. 'method=area_code'
. '&api_key=YOUR_API_KEY'
. '&text=' . urlencode($text);

// Fetch XML from T2A API
$result = simplexml_load_file($url);

if($result) {

  // Check for errors
  if($result->status == 'ok') {

    $area_code_list = $result->area_code_list;

  } else {

    // Report error
    echo 'Error: ' . $result->error_code;
    exit;

  }
}
?>

<!DOCTYPE html> 
<html lang="en"> 
  <head> 
    <meta charset="UTF-8"> 
    <title>Code example</title>
  </head>
  <body>
    <!-- iterate over list of area codes -->
    <?php foreach($area_code_list->area_code as $area_code): ?>
    <!-- output area code -->
    <h3><?php echo $area_code->code; ?></h3>
    <ul>
      <!-- iterate over list of places in this area code -->
      <?php foreach($area_code->place_list->place as $place): ?>
      <!-- output place name -->
      <li><?php echo $place->name; ?></li>
      <?php endforeach; ?>
    </ul>
    <?php endforeach; ?>
  </body>
</html>                 
	
	

jQuery

<!DOCTYPE html> 
<html lang="en"> 
  <head> 
    <meta charset="UTF-8"> 
    <title>Code example</title>
    <script type="text/javascript" src="http://code.jquery.com/jquery-latest.min.js"></script>

    <script type="text/javascript">
    $(document).ready(function(){ 

      // Attach code to form's onsubmit event
      $(".demo").submit(function() {

        // Fetch JSON from T2A API
        $.getJSON("https://api.t2a.io/rest/?callback=?",
        { 
          "method" : "area_code",
          "api_key" : "YOUR_API_KEY", // better to use js_key obtained from javascript_key service for security reasons
          "output" : "json",
          "text" : $("#text").val()
        },
        // Function to parse resulting JSON
        function(result) {

        // Check for errors
          if(result.status == "ok") {

            var html = "<p><strong>Your search returned the following dialling codes:</strong></p>";
            $.each(result.area_code_list, function() {
              html += "<h3>" + this.code + "</h3><ul>";
              $.each(this.place_list, function() {
                html += "<li>" + this.name + "</li>";
              });
              html += "</ul>";
            });
            $("#results").html(html);

          } else {
            // report error
            alert("Error: " + result.error_code);
          }

        }
	    );

        return false;
      });
    });
    </script>

  </head>
  <body>
    <form class="demo">
      <label for="text">Dialling code, location, or postal area:</label>
      <input type="text" id="text" />
      <input type="submit" />
    </form>
    <div id="results"></div>
  </body>
</html>
	
	

XML, JSON and SOAP API Details

General XML, JSON and SOAP Overview

We offer a very simple, structured XML API, which can also return a JSON response. We also offer a SOAP API, which is a superset of the XML API, using the same format of results, wrapped in a SOAP response.

The primary focus of the documentation in this section is aimed at users of the XML and JSON API; SOAP users generally would use the SOAP API as an external web service, using an IDE such as Visual Studio which creates classes to de-serialize the SOAP responses.

Accessing the XML and JSON API

The XML and JSON API is available:-

https://api.t2a.io/rest

Accessing the SOAP API

The SOAP XML API is available:-

https://api.t2a.io/soap

.NET developers using Visual Studio should use the above location when adding web services to their projects. A WSDL is available.

A JavaScript Key

The T2A methods may be invoked from client-side JavaScript. In order to secure this facility, we have created a system allowing you to create a secure temporary key. Advantages are:-

1. There is no need to embed your API key in the HTML; use the temporary key.
2. The temporary key will only work when invoked in a specified website domain.
3. The temporary key will expire after a specified number of minutes, never more than 60.
4. The temporary key can optionally be further secured to only operate on the final client's IP address.
5. The key is encrypted using 256-bit AES encryption.

Use the method javascript_key to create the temporary key, to be embedded in your web page.

More information about using T2A from JavaScript can be found here.

Security

All server-side requests require your API key.

JSON requests, and XML requests which are launched from JavaScript, should use our javascript_key method to obtain a temporary, secure key which is safe to include in HTML markup, since it expires within an hour, and can be restricted to the final user's IP address.

Invoking Methods

The XML and JSON API accepts GET and POST requests; the methods can be tested using a web browser.

Using T2A from JavaScript

Developers experienced in using external web services from JavaScript may wish to skip this section.

Cross-Domain Ajax

For reasons of web browser security, it is not normally possible to load scripts from one domain into another. For example, the following are prohibited:

• Issuing an XMLHttpRequest() to another domain (a core component of Ajax).
• Accessing or modifying the DOM of a <frame> or <iframe> which has a src attribute with another domain.
• Accessing or modifying another window (or tab) which has a different location.

Therefore, it is not possible to use T2A directly from Ajax on your web pages, because your Ajax request will be to a domain other than your own.

We now demonstrate three solutions to this problem.

Solution 1 - Raw JavaScript

This section demonstrates how to securely use T2A from client-side JavaScript, without using a JavaScript Library such as jQuery.

We will use a technique known as on-demand JavaScript, to force the web browser to load an external Javascript source, which in this case, is a T2A JSON response.

These examples use PHP.

Obtain a Temporary JavaScript Key

In your server-side scripting, obtain a JavaScript key. This example uses PHP:-

<?php
$js_key = ""; //the temp key
$api_key = ""; //set your API key here
$url = "https://api.t2a.io/rest?"
. "method=javascript_key"
. "&api_key=" . $api_key
. "&lifetime_minutes=" . (2 * 60) // Life time in minutes (max 24 hours)
. "&domain=t2a.co"; // Replace with your website's domain
// Fetch XML from T2A API
$result = simplexml_load_file($url);
if ($result && $result->javascript_key)
{
  $js_key = (string)$result->javascript_key;
}
?>
	

The temporary key is stored in the server-side variable $js_key in the example above.

Action a Client-Side Request to T2A

Using the temporary key, we may now send a request from the browser, to T2A.

This is done by inserting a <script> tag into the DOM, where the external JavaScript is actually a request to T2A (JSON). This does not violate browser security.

The resulting JavaScript object returned from T2A can easily be accessed.

The JavaScript is part of a server-side script, in this case PHP. This allows the temporary key to be written into the HTML:-

// generic function to insert a script tag to execute the url
// which is an external JavaScript (JSON)
function get_json(url)
{
  var head = document.getElementsByTagName("head")[0];
  var script = document.createElement("script");
  script.type = "text/javascript";
  script.src = url;
  head.appendChild(script);
}

// set a javascript variable, note that this is actually written by the
// PHP to set the temp key
var javascript_key = "<?php echo $js_key; ?>";

// Fetch JSON from T2A API
// this is using the method ip_country
// note that we use the callback function to make the resulting
// JSON be sent to our parse_json function
window.onload = function()
{
  var url = "https://api.t2a.io/rest?"
  + "method=ip_country"
  + "&javascript_key=" + javscript_key
  + "&output=json"
  + "&callback=parse_json";
  get_json(url);
}	
	

The function we use to parse the JSON is shown below. Here, we use simple JavaScript alert boxes to show the result or error:-

function parse_json(result)
{
  if(result.status == "ok")
  {
    alert('Your IP address is ' + result.ip_address + ' and your country code is ' + result.country_code);
  }
  else
  {
    // report error
    alert(result.error_code);
  }
}	
	

Solution 2 - jQuery

Using jQuery simplifies the process of sending the client-side request to T2A.

The example below is in PHP. As with the raw JavaScript example above, we have obtained a temporary key (see above), stored in the server-side variable $js_key.

This is written into the HTML markup by PHP, so that it can become a client-side variable called javascript_key.

The jQuery functions are then used to send and process the JSON request to T2A:-

// set a javascript variable, note that this is actually written by the
// PHP to set the temp key
var javascript_key="<?php echo $js_key; ?>";
$(document).ready(function(){
  // Fetch JSON from T2A API
  $.getJSON(
    "https://api.t2a.io/rest?callback=?",
    {
      'method' : 'ip_country',
      'javascript_key' : javascript_key,
      'output' : 'json'
    },
    // Function to parse resulting JSON
    function(result) {
      // Check for errors
      if(result.status == "ok") {
        alert('Your IP address is ' + result.ip_address + ' and your country code is ' + result.country_code);
      } else {
        // report error
        alert(result.error_code);
      }
	}
  });
});
	

Solution 3 - Use Ajax

You could use Ajax to access T2A by creating a server-side component on your own web server which receives the Ajax request, and then communicates with T2A.

For example, if you were using the ip_location method on a PHP website:-

1. Create a .php file to process an Ajax request; we'll call it iploc.php
2. Your Ajax request will use iploc.php on your domain (and thus avoiding cross-domain security issues).
3. The php will send a request directly to T2A from the server, and will echo the response back, to the client-side Ajax component.

In effect, iploc.php is a proxy, allowing you to use Ajax.

.NET Developers and the SOAP API

.NET developers using Visual Studio should create a web reference using https://api.t2a.io/soap

In the examples below, our web reference is named t2a. The class containing the methods is named t2a.T2A, and the result classes are also in the t2a namespace.

This is a C# illustration of the use of the ip_location method:-

// create a web reference using https://api.t2a.io/soap
//
// the reference here is named t2a, and the class is called T2A
//
// create an instance of t2a.T2A
t2a.T2A myclass = new t2a.T2A();
// the result class is also in t2a
//
t2a.ip_location_res res = myclass.ip_location(api_key, null, ip_address);
// check the status, if ok, display results, otherwise display the error
if (res.status.CompareTo("ok") == 0)
	

This is a Visual Basic illustration of the use of ip_location:-

' execute the method
' replace with your own API key
Dim api_key As String = "---"
' create a web reference using https://api.t2a.io/soap
' the reference here is named t2a, and the class is called T2A
' create an instance of t2a.T2A
Dim myclass2 As New t2a.T2A()
' the result class is also in t2a
Dim res As t2a.ip_location_res = myclass2.ip_location(api_key, "",
ip_address)
' check the status, if ok, display results, otherwise display the error
If (res.status = "ok") Then	
	

Next: Result Page Caching

Result Page Caching

Some of our methods produce large result sets, comprising hundreds of records. To make this large result list usable to their end clients, developers will probably wish to present the records in shorter pages of results. In order to achieve this, it would be necessary to store the entire result set on your web server, either in a memory cache, or a short-lived database cache.

T2A offers a transparent page cache on methods that can produce large result sets. The XML, JSON and SOAP APIs will store the complete result in a cache on your behalf (only usable by you) for 60 minutes, to allow easy paging for your final clients. In order to use the cache, you must set both of the following parameters:-

• records_per_page - specifies the number of records to be displayed on a page.
• page_number - specify the page number to be displayed. This is a zero-based integer.

Those methods that offer page caching include the following in their result:-

• total_records - the total number of records in the result set.
• page_number - the current page number, a zero based integer.

Common XML, JSON, and SOAP Error Codes

The error codes below are applicable to all methods:-

Common Response Structures

These structures are returned by more than one method.

Common Response Structure <address>

The address structure is returned by the address_search method.

Common Response Structure <business>

Common Response Structure <company_short>

This structure is a brief summary of a company name and other details.

Note that the company_number value is used in order to access the main company information methods.

Common Response Structure <director>

This structure is returned by the director_details and company_details methods. All elements may be empty unless stated.

Common Response Structure <director_appt>

This structure is only used in conjunction with the above director structure, and only during the method director_details. This shows the appointments relating to this company officer.

Common Response Structure <director_disq>

This structure is only used in conjunction with the above director structure, and only during the method director_details. This structure contains the information on the companies from which the individual is disqualified.

Common Response Structure <geo_data>

The address structure is returned by the geo_code and geo_code_telephone methods; not all elements are returned by both methods.

Common Response Structure <person>

The person structure is returned by the person_search method.

<years_list>
  <string>2008</string>
  <string>2009</string>
  <string>2010</string>
  <string>2011</string>
</years_list>					
				

"years_list":["2009","2010","2011"],

Common Response Structure <place>

The place structure is used in place lists returned by the person_search and business_search methods; not all elements are returned by each method.

Common Response Structure <premises>

An array of records is returned from an address-only person_search - the end user should select the premises at which to view the occupants. Use the name value to replace the premises input parameter value.

You must use the entire name value, including the postal code, when replacing the premises value.

Common Response Structure <street>

This structure is returned by the person_search method. An array of records is returned from an address-only search - the end user should select the street on which to view the occupants. Use the name value to replace the street input parameter value.

Common Response Structure <date_details>

Common Response Structure <date_time>

Response Structure <company_shareholder>

This structure is returned by company_credit_report and company_details methods. This is a single shareholder within the <company_shareholder_list> of a credit report.

Response Structure <company_financial>

This structure is returned by company_credit_report and company_details methods. This is a single financial item (covering a described period) within the financial list. Note that there are sub-elements for profit and loss, balance sheet, capital reserve and ratio; the names of those elements are listed separately.

Company Profit and Loss

These are the elements within the profit_loss section.

Company Balance Sheet

These are the elements within the balance_sheet section.

Company Capital Reserve

These are the elements within the capital_reserve section.

Company Ratio

These are the elements within the ratio section.

Appendices

ISO 3166-1 Country Codes

Co-ordinate Systems

GS 84 (GPS Co-ordinates)

We use the World Geodetic System standard co-ordinate system. Co-ordinates are expressed as signed decimal latitude and longitude values. This reference system is also use by the Global Positioning System (GPS).

OSGB36

The Ordnance Survey grid system projects Great Britain onto a 2D system comprising X and Y co-ordinates, in metres. The origin is at a point to the south west of Land's End. The X and Y co-ordinates are referred to as eastings (or east) and northings (or north) respectively.

Note that the OSGB36 grid system applies only to Great Britain and offshore islands - Northern Ireland and the Channel Islands are not included.

Irish Grid Reference System

The island of Ireland uses a similar system to OSGB36; co-ordinates are projected onto a 2D system which covers the island. This is independent from the GB system.

Examples

Great Britain

Here are the approximate positions of some GB places, in WGS 84 and OSGB36.

Northern Ireland

Here are the approximate positions of some places in Northern Ireland, in WGS 84 and the Irish Grid Reference System.

Data Sources

BT OSIS

BT OSIS data is a daily updated directory of business and residential telephone numbers. BT OSIS data could be used for building a directory enquiries facility, telephone number appending large customer files, or screening existing customer data for updates or changes.

UK Edited Electoral Roll

The UK Edited Electoral Roll is a database of people who have registered to vote in the UK and not opted out of having their data included. You can search for people on the electoral roll by forename, surname and address. Electoral Roll data is useful for a variety of purposes such as building marketing lists or identity checking. It is a useful first step in confirming that an applicant for goods or services is providing accurate information.

Companies House

Companies House data is a collection of information on UK companies including: Company Names, Company Directors, Company Documents, Company Appointments and Company numbers. Companies House data is useful for verifying company details and for marketing purposes e.g. identifying potential decision makers within an organisation.

The Bereavement Register

The Bereavement Register is a database of people registered as deceased. It is used as a deceased suppression tool to avoid the distress caused to relatives when marketing material is sent to a deceased person.

Telephone Preference Service (TPS and CTPS)

The Telephone Preference Service (TPS) is a monthly updated central opt-out register of telephone numbers belonging to people who do not wish to receive unsolicited sales and marketing phone calls. It is a legal requirement that organisations screen any telemarketing data they hold against the TPS register.

Corporate TPS (or CTPS) is a similar service for business instead of residential telephone numbers - for organisations that telemarket B2B. It is a legal requirement that B2B sales data is also screened against this register.

Company Categories

Company Form Types

1 Post October 2009 Form Types and Descriptions

1.1 CATEGORY ACC: ANNUAL ACCOUNTS

1.2 CATEGORY ANRT: ANNUAL RETURNS

1.3 CATEGORY APPT: APPOINTMENTS

1.4 CATEGORY CROA: CHANGE IN REGISTERED OFFICE

1.5 CATEGORY MORT: MORTGAGE DOCUMENTS

1.5.1 England/Wales

1.5.2 Scotland

1.6 CATEGORY NEWC: NEW INCORPORATIONS

1.7 CATEGORY CAP: CAPITAL

1.8 CATEGORY LIQ: LIQUIDATION DOCUMENTS

1.9 CATEGORY CON: CHANGE OF NAME

1.10 CATEGORY MISC: MISCELLANEOUS

2 Pre October 2009 Form Types and Descriptions

2.1 CATEGORY ACC: ANNUAL ACCOUNTS

2.2 CATEGORY RET: ANNUAL RETURNS

2.3 CATEGORY DIR: 288 DOCUMENTS

2.4 CATEGORY ROC: 287 DOCUMENTS

2.5 CATEGORY NEWC: NEW COMPANIES

2.6 CATEGORY MORT: MORTGAGE DOCUMENTS

2.6.1 England and Wales

2.6.2 Scotland

2.7 CATEGORY CAP: CAPITAL

2.8 CATEGORY LIQ: LIQUIDATION DOCUMENTS

2.8.1 England and Wales

2.8.2 Scotland

2.9 CATEGORY CON: CHANGE OF NAME

2.10 CATEGORY MISC: MISCELLANEOUS DOCUMENTS

2.10.1 England, Wales and Scotland

2.11 LLP DOCUMENTS

The majority of the above document codes that apply to companies also apply to Limited Liability Partnerships and have the same purpose or significance. Note, however, that LLPs do NOT file Partnership Agreements at Companies House. Nor do they file Share Capital documents, Resolutions, Memorandum of Association or Articles of Association

Northern Ireland codes and descriptions are detailed below but documents that align with GB documents are included in the above categories for 'Monitor' etc.

2.12 Northern Ireland Documents

Credit Union Annual Return

2.12.1 Dormant Balance Sheet

Company Officer Disqualification Details

1 Company Directors and Secretaries

A company director may be disqualified as a result of an investigation by one of the following authorities:-

• The Police - if fraud is suspected.
• DTI Investigations - for general misconduct whilst running a company.
• The Insolvency Service - usually as a result of an investigation of a failed company (e.g. a director knowingly continues to trade while insolvent).
• Companies House - for breaches of the filing requirements as specified in the Companies Act. The Courts also have power to make a disqualification order where a company director is convicted of an indictable offence in relation to certain matters in connection with a company.

If a person is disqualified then that person shall not, for the period of his disqualification except with leave of the court:-

• Be a director of a company
• Act as a receiver of a company's property
• Be concerned or take part, whether directly or indirectly, in the promotion, formation or management of a company
• Act as an insolvency practitioner

1.1 The Company Directors Disqualification Act 1986 (the "CDDA")

Disqualification orders are made, and undertakings accepted, under sections 2 – 8 and 10 of the Company Directors Disqualification Act 1986 (the "CDDA").

Sections 2 - 5: Disqualifications for general misconduct in connection with companies –

2. On conviction of an indictable offence.

3. Persistent breaches of company legislation.

4. For fraud, etc, in winding-up.

5. On conviction of summary offences.

Sections 6 - 8: Disqualification for unfitness to act as company director –

6. Duty of court to disqualify unfit directors of insolvent companies.

7. The Secretary of State may accept a disqualification order where the conditions in section 6 are met and it appears to him to be expedient to do so in the public interest.

8. Disqualification after investigation of company, under companies and other legislation. The Secretary of State may accept an undertaking from a company director under sections 7 or 8 of the Company Directors Disqualification Act 1986.

Section 10: Fraudulent or Wrongful Trading –

10. A court may make a disqualification order where it makes a declaration in relation to fraudulent or to wrongful trading.

Sections 11 and 12: Miscellaneous Disqualification –

11. This section provides that, except with leave of court, undischarged bankrupts are disqualified from acting as directors or taking part in or being concerned in the promotion, formation or management of a company

12. This section provides that, except with leave of court, where an administration order under section 429 of the County Courts Act 1984 has been revoked and an order made under that section a person subject to such an order is similarly disqualified and also may not act as a liquidator. The maximum period of disqualification depends upon the provision under which the order is made, or undertaking accepted, and is either 5 years or 15 years.

Section 17: Application for leave under an order or undertaking –

17. A Director may apply to a Court to vary the terms of the original Disqualification Order or undertaking. In certain circumstances the court may allow the disqualified individual to continue as a director of a specific company or companies for either an interim period of time or the whole term of the disqualification. Details of any exemptions will be provided.

For further information, please refer to the Company Directors Disqualification Act 1986.

1.2 Members of Limited Liability Partnerships

A member of a limited liability partnership (LLP) can be subject to a disqualification order or undertaking under the provisions of the Limited Liability Regulations 2001.

A partner can also be subject to a disqualification order or undertaking under the provisions of the Insolvent Partnerships Order 1994.

Company Officer Types

Company Statuses