How do I create an ABOR?

Important: This article only applies to older funds with an underlying ABOR. For the latest implementation, see this article.

Providing you have suitable access control permissions, you can create an ABOR providing an accounting view of one or more transaction portfolios.

To do this, you must have already created an ABOR configuration module referencing a chart of accounts and a recipe able to value these portfolios.

Subsequently, you can create a trial balance for the ABOR, or incorporate it in a fund.

Using the LUSID web app

1. Sign in to the LUSID web app as a user with suitable permissions.

2. From the top left menu, select Financial Reporting > Mapping.

3. On the ABORs dashboard, click the Create abor button and follow the instructions:
   
    

Using Luminesce

You can use the Lusid.Abor.Writer provider.

Using the LUSID API

1. Obtain an API access token.

2. Call the CreateAbor API, specifying a scope in the URL and, in the body of the request:

   • A code that together with the scope uniquely identifies the ABOR (the code must be unique within the scope).

   • A displayName and, optionally, a description. These are informational fields only.

   • In the portfolioIds collection, the scope and code of at least one transaction portfolio. Note portfolio groups are not currently supported.

   • An aborConfigurationId that identifies an ABOR configuration module.

   • Optionally in the properties collection, any number of custom properties from the Abor domain to extend the data model. Alternatively, you can add or remove properties using the UpsertAborProperties API at any time.

Consider the following example, of an ABOR with a scope of Abor (in the URL) and a code of Standard (in the body). Note the ABOR maps to a single portfolio:

curl -X POST 'https://<your-domain>.lusid.com/api/api/abor/Abor'
  -H 'Content-Type: application/json-patch+json' 
  -H 'Authorization: Bearer <your-API-access-token>'
  -d '{
  "code": "Standard",
  "displayName": "Standard Abor",
  "description": "This is a standard Abor",
  "portfolioIds": [
    {
      "scope": "Finbourne-Examples",
      "code": "UK-Equities",
    }
  ],
  "aborConfigurationId": {
    "scope": "Abor",
    "code": "Standard"
  },
  "properties": {
    "Abor/Abor/AccountantName": {
      "key": "Abor/Abor/AccountantName",
      "value": {
        "labelValue": "Sam Stokes"
      },
      "effectiveFrom": "2020-03-05T00:00:00.0000000+00:00"
    }
  }
}'

In the response, LUSID confirms the identifier of the module consists of the scope and code:

{
  "id": {
    "scope": "Abor",
    "code": "Standard"
  },
  "displayName": "Standard Abor",
  "description": "This is a standard Abor",
  "portfolioIds": [
    {
      "scope": "Finbourne-Examples",
      "code": "UK-Equities",
      "portfolioEntityType": "SinglePortfolio"
    }
  ],
  "aborConfigurationId": {
    "scope": "Abor",
    "code": "Standard"
  },
  "properties": {
    "Abor/Abor/AccountantName": {
      "key": "Abor/Abor/AccountantName",
      "value": {
        "labelValue": "Sam Stokes"
      },
      "effectiveFrom": "2020-03-05T00:00:00.0000000+00:00",
      "effectiveUntil": "9999-12-31T23:59:59.9999999+00:00"
    }
  },
  ...
}