> ## Documentation Index
> Fetch the complete documentation index at: https://control-dev.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Tripletex

> Create an employee token for Control's approved Tripletex application.

Control manages the production consumer token. The customer creates only an employee token for the **Control** application.

## Prepare Tripletex

1. Confirm that the Tripletex API or integrations module is active for the company.
2. Sign in as the user who will own the token.
3. Open that user's API access or token settings.
4. Select the application named **Control**.
5. Review the access template and create the employee token. The token owner must have every entitlement granted to the token; Tripletex disables entitlements the owner does not have.
6. Copy the generated token.

If Control is not available in the application list, use Tripletex's adapted setup flow and enter the Control application name exactly as instructed by Tripletex. Grant access only to the data areas below rather than choosing unrelated write permissions.

## Entitlements required

| Tripletex area      | Resources read by Control                                                                          |
| ------------------- | -------------------------------------------------------------------------------------------------- |
| Company access      | Companies available to the token; required when an accountant token connects a client company      |
| Accounting          | Accounts, general ledger, balance sheet, vouchers, voucher types, postings, and accounting periods |
| Sales and purchases | Sales invoices and supplier invoices                                                               |
| Parties             | Customers and suppliers                                                                            |
| Dimensions          | Departments and projects                                                                           |
| Bank                | Bank statements and statement transactions                                                         |
| Employees           | Employees; only needed when employee import is enabled and allowed                                 |

Control performs `GET` requests only. Tripletex filters both endpoints and fields according to the employee token's
entitlements, so a credential can verify successfully while returning incomplete data if some rights are missing. For
accounting-office tokens, also grant **API access** to each client company and assign the same entitlements there.

## Finish in Control

| Field                    | Value                                                                          |
| ------------------------ | ------------------------------------------------------------------------------ |
| Tripletex Employee Token | The employee token created for Control                                         |
| Tripletex Company ID     | Optional; leave at the default `0` unless connecting a specific client company |
| Base URL                 | Optional; the default is `https://tripletex.no/v2`                             |

Save and verify the credentials. Control creates short-lived Tripletex session tokens automatically when required.

<Warning>
  Do not create or paste a consumer token into Control. If the employee token is rotated, update the saved credential in
  Control.
</Warning>

## Data imported

* Accounts, ledger reports, balance-sheet reports, accounting periods, and voucher types
* Vouchers and general-ledger postings
* Sales invoices and supplier invoices
* Customers and suppliers
* Departments and projects
* Bank statements and bank-statement transactions
* Employees when the token has access to the employee endpoint

## Provider documentation

* [Tripletex authentication and tokens](https://developer.tripletex.no/docs/documentation/authentication-and-tokens/)
* [Tripletex OpenAPI endpoint reference](https://tripletex.no/v2-docs/)
* [Tripletex production integration setup](https://developer.tripletex.no/docs/documentation/getting-started/3-getting-ready-for-production/)