# SailPoint Akaunting Connector Documentation

> Akaunting Connector Documentation

# Documentation

# Connecting SailPoint and Akaunting

To connect SailPoint to the source, perform the following tasks:

1. In SailPoint, create an **Akaunting** source (Express Setup / Quick Compliance).
2. Complete **Connection Settings** and save.
3. Select **Test Connection**.
4. Run **Account Aggregation**.

## Adding and Configuring the Source in SailPoint

To connect to SailPoint, perform the following steps. Once the connection is made, you can configure it to meet your company's needs.

1. Go to **Admin \> Connections \> Sources**.
2. Select **Create New**.
3. Search for a source type and select **Actions**.
4. In the **Actions** dropdown, select the setup method:

   - **Express Setup** - Quickly create a read-only connection to your target system by providing minimal configurations and authentication. On completion, aggregation is automatically started.

     > **Note**
     >
     > Express Setup supports Credential Providers. For information on supported credential providers and configuration, refer to [Credential Providers](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>). For more information, contact your SailPoint Customer Service Manager.
   - **Standard Setup** - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup.

### Express Setup

1. Review the directions and select **Start Express Setup**.
2. Review the pre-populated source name, source owner, and description. To update, select **Edit**.

   > **Note**
   >
   > Source name must be unique.
3. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider.

   > **Note**
   >
   > To add a Credential Provider in SailPoint, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>).
4. Configure the authentication to allow SailPoint to connect to the source. For more information, refer to the **Connection Settings** page.
5. Select **Finish**. After a successful test connection, the system creates your source and prompts you to run an aggregation.

   - If you want to aggregate now, select **Aggregate**.

     - To see the latest account aggregation history, go to **Account Management \> Account Aggregation**.
     - To see the list of aggregated source accounts, go to **Account Management \> Accounts**.
   - If you want to aggregate later, select **Exit**. This returns you to the **Sources** page. Your new source is listed, but contains no accounts or aggregation history yet.

### Standard Setup

Configure more detailed settings relative to Express Setup.

1. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters.
2. In the **Description** field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters.
3. In the **Source Owner** field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to [Assigning a Source Owner](<https://documentation.sailpoint.com/saas/help/sources/index.html#assigning-a-source-owner>).
4. (Optional) Select a governance group to grant its members [source](<https://documentation.sailpoint.com/saas/help/common/users/user_levels.html#source-sub-admin-user-level>) or [role](<https://documentation.sailpoint.com/saas/help/common/users/user_levels.html#role-sub-admin-user-level>) sub-admin level oversight of the source and its access. For more information, refer to [Creating and Managing Governance Groups](<https://documentation.sailpoint.com/saas/help/common/users/governance_groups.html>).
5. If this source represents a primary system containing your organization's personnel records, select the **Authoritative Source** checkbox. For more information, refer to [Creating Identity Profiles](<https://documentation.sailpoint.com/saas/help/setup/identity_profiles.html>).
6. Select **Continue**. The source is created, and you are navigated to the **Source Setup \> Base Configuration** page. Here, continue to configure your connected source.

## Base Configuration

Provide the base configuration parameters. Information you entered in the Create New Source dialog is automatically entered into the fields in the Base Configuration page. You can edit this information if necessary.

1. Enter a descriptive **Source Name** for the connection.
2. Enter the **Source Description** that provides details necessary to distinguish it from similar connection sources.
3. In **Source Owner**, begin typing the name of the source owner.
4. (Optional) Select the appropriate **Governance Group for Source Management** from the dropdown list. For more information about governance groups, refer to [Associating Governance Groups with a Source](<https://documentation.sailpoint.com/saas/help/common/users/governance_groups.html#associating-a-governance-group-with-a-source>).
5. Select **Create Manual Work Items** to enable the source to support additional source management features such as creating accounts and access profile management.

   > **Important**
   >
   > Once you enable this feature, it can't be disabled.

   For more information on manual work items, refer to [Work Items](<https://developer.sailpoint.com/docs/api/work-items>). For more information on SailPoint features, refer to [SailPoint Identity Services](<https://documentation.sailpoint.com/saas/help/index.html>).
6. Select **Save**.

## Connection Settings

Configure a secured, direct connection to the source.

1. Enter the Akaunting base URL as **Base URL**. For Cloud, use `https://app.akaunting.com`. For self-hosted, use your Akaunting site URL with no extra path.
2. Enter your Akaunting sign-in email as **Username**.
3. Enter your Akaunting sign-in password as **Password**.
4. Enter the numeric **Company Id** for the company you want to aggregate.
5. Select **Save**.

## Review and Test

Perform a test to confirm the connection to SailPoint.

1. Go to **Review and Test**.
2. Confirm that the entries in each field are correct.

   If you note any mistakes, return to the section and make corrections.
3. Select **Test Connection**.

## SailPoint Application Onboarding

SailPoint application onboarding enables you to easily onboard new applications and create sources following the successful onboarding of a discovery source. To use this feature, continue to **Discovered Applications** in the SailPoint user interface.

For more information, refer to [Application Onboarding](<https://documentation.sailpoint.com/saas/help/ai/app_onboarding/index.html>) in the SailPoint SaaS documentation.

# Integrating SailPoint with Akaunting

The Akaunting connector enables SailPoint to aggregate users for a single Akaunting company and their role names for that company. This document provides the instructions required to configure a new direct connection between SailPoint and Akaunting. For a reference to the terminology specific to SailPoint products, refer to [Source and Connector Definitions](<https://documentation.sailpoint.com/saas/help/sources/index.html#source-and-connector-definitions>).

> [!NOTE]
>
> To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes](<https://community.sailpoint.com/release-notes/saas>) page.

## Supported Features

The Akaunting connector supports the following:

### Account Management

- Aggregate Users

> [!NOTE]
>
> Roles are aggregated with users as an account entitlement on the `role` attribute. A separate entitlement schema is not used.

> [!IMPORTANT]
>
> Quick Compliance connectors have the following manual aggregation limits within a 24-hour period:
>
> - **Organization Admins**: Limited to 3 manual account or entitlement aggregations per day per source. This limit is cumulative across all admins in the organization.
> - **Regular Users**: Limited to 1 manual account or entitlement aggregation per day per source.
>
> These limits ensure that individual compliance statuses are kept up to date while maintaining continuous compliance monitoring. If you need to run additional aggregations beyond these limits, contact SailPoint Support.

## What Gets Aggregated

Each SailPoint source is tied to one Akaunting company.

```text
Akaunting
 └── Company you enter in Connection Settings
      └── Users of that company   → accounts
           └── Role               → entitlement
```

| In SailPoint | In Akaunting |
| --- | --- |
| Account | User |
| Entitlement | Role (for example Manager, Accountant) |
| Source scope | One company (Company Id) |

**Notes for administrators**

- If you need more than one company, create a separate source for each Company Id.
- A person can exist in several Akaunting companies. This source only shows them if they belong to the Company Id you configured.
- Role is the access level defined on the user in Akaunting. It is not a separate catalog you manage in SailPoint.

## Prerequisites

Before you add the source in SailPoint:

- You have an Akaunting Cloud tenant (`https://app.akaunting.com`) or a self-hosted Akaunting URL.
- You can sign in with a user that can view **Users** (typically **Manager** on Cloud, or **Admin** on self-hosted).
- You know which company you want SailPoint to govern.
- You have that company's **Company Id** (see below). Do **not** use the Account Dashboard API Key. Sign-in email and password are enough.

### How to Find the Company Id

Company Id is the number Akaunting puts in the browser address after you open a company. You do not look it up in a developer tool.

1. Sign in to Akaunting.
2. Open the company you want SailPoint to govern:

   - Select the **company switcher** in the navigation menu, then choose the company **or**
   - Select **Manage Companies** and switch to that company.
3. Look at the address bar. The number after the host is the Company Id.

**Example**

`https://app.akaunting.com/405319/dashboard`

Company Id = `405319`

Use that value in SailPoint **Company Id**.

### Auth Notes

> [!NOTE]
>
> - Akaunting REST supports **HTTP Basic only** (`email:password`).
> - There is **no OAuth / Bearer** for `/api/...`.
> - Account Dashboard **API Key** is for Apps/plan only - **not** for REST aggregation.

Header format:

```text
Authorization: Basic base64(email:password)
```

The connector uses **Basic Login**. SailPoint should build `$application.accesstoken$` as Base64(`username:password`) and send Basic auth on operations. You should not paste Base64 as the password.

## Required Permissions

| Who | Access |
| --- | --- |
| Manager / Admin (recommended service account) | Users list, companies list, API read |
| Accountant / Employee / Customer | Often insufficient for full user aggregation |

## Product Links

- [Akaunting website](<https://akaunting.com/>)
- [REST API documentation](<https://akaunting.com/hc/docs/developers/restful-api/>)
- [API routes (source of truth)](<https://github.com/akaunting/akaunting/blob/master/routes/api.php>)
- [Roles and permission levels](<https://akaunting.com/hc/docs/users-and-roles/roles-and-permission-levels/>)
- [Postman workspace](<https://www.postman.com/akaunting/workspace/akaunting>)

> [!NOTE]
>
> The linked document is not maintained by SailPoint and is subject to change without notice.

# Schema Reference

The application schema is used to configure the objects returned from a connector.

> [!NOTE]
>
> - The **Account Schema** tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as **Entitlement** or **Multi-Valued**. Refer to [Managing Source Account Schemas](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) for more information.
> - The schema attributes that are not present by [default](<#default-account-schema>) must be defined as strings if not specified.

The Akaunting connector uses the following default correlation and object configurations.

## Default Account Schema

Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location.

The set of account attributes each source stores and how they're organized is known as the account's *schema*. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to [Managing Source Account Schemas](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) for more information.

### Default Account ID

SailPoint requires that certain attributes remain in your configuration. These attributes are referred to as *account IDs*.

> [!CAUTION]
>
> Changing the attribute marked as the account ID after aggregating accounts can result in duplicate accounts being created. To avoid this, either reset the accounts on this source before editing the account ID attribute or edit the account ID attribute before aggregating accounts.
>
> To resolve issues caused by changing account IDs, reconfigure them to their default values.

The following table lists the default account IDs for this connector:

| Account ID | Schema Object Type |
| --- | --- |
| id | Account |

### Default Account Attributes

The Akaunting connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified.

| Attribute Name | Description |
| --- | --- |
| id | Unique Akaunting user ID |
| name | User display name |
| email | User's login email |
| locale | Preferred locale/language |
| landingPage | Default landing page after sign in |
| enabled | Whether the user is enabled |
| createdAt | Date and time the user was created |
| updatedAt | Date and time the user was updated |
| role | Role assigned to the user (from roles.data\[\*\].name), used as a managed entitlement |

> [!NOTE]
>
> `entitlementSchemas` is empty in the current connector. Roles are modeled as an account entitlement on the `role` attribute (not a separate Group/Company schema).