> ## 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 e-conomic

> Approve Control's app and provide the agreement grant token.

export const ControlAppLink = ({path, breadcrumb, children}) => {
  const link = <a href={`https://app.control.dev${path}`} target="_blank" rel="noopener noreferrer" aria-label={breadcrumb ? `Open ${breadcrumb} in Control` : undefined}>
      {children}
    </a>;
  return breadcrumb ? <Tooltip tip={breadcrumb}>{link}</Tooltip> : link;
};

Control manages the e-conomic app credentials centrally. You provide the agreement grant token for the company being connected.

## Approve access

1. In Control, open <ControlAppLink path="/entities-data-sources/overview"><strong>Entities & sources</strong></ControlAppLink>, choose **Add data source**, and select **e-conomic**.
2. Sign in to e-conomic in the new tab.
3. Select the intended agreement or company.
4. Approve Control's access.
5. Copy the agreement grant token shown after approval.

The approval creates an agreement grant token for Control's app; it does not give Control the user's password. The app
role is managed by Control and determines which e-conomic entities the token can access.

## Finish in Control

1. Return to Control.
2. Paste the value into **e-conomic Agreement Grant Token**.
3. Leave the optional base URL empty unless Control has instructed you to use another endpoint. The standard endpoint is `https://restapi.e-conomic.com`.
4. Save and verify the connection.

## Data imported

* Chart of accounts, VAT accounts, accounting years, and accounting periods
* Journals, journal entries, journal vouchers, and posted entries
* Booked sales invoices
* Customers, customer groups, suppliers, and supplier groups
* Payment terms and payment types
* Dimensions, dimension values, distributions, and budget-figure dimension data when the required e-conomic module is available

## Access required

The approved app must be able to read these e-conomic REST areas:

| Area        | REST resources used by Control                                                                                |
| ----------- | ------------------------------------------------------------------------------------------------------------- |
| Accounting  | Accounts, VAT accounts, accounting years and periods, posted entries, journals, vouchers, and journal entries |
| Receivables | Booked invoices, customers, and customer groups                                                               |
| Payables    | Suppliers and supplier groups                                                                                 |
| Settings    | Payment terms and payment types                                                                               |
| Dimensions  | Departmental distributions and related dimension data; requires the applicable e-conomic module               |

e-conomic assigns access by the app's role rather than by per-token scope checkboxes. Its **Bookkeeping** role does not
cover booked sales invoices and customers, so the combined dataset requires Control's broader app role. Control only
sends read requests. Do not create a separate e-conomic app or enter app secret/public tokens into Control.

## Provider documentation

* [e-conomic REST API documentation](https://restdocs.e-conomic.com/)
* [e-conomic token authentication](https://www.e-conomic.com/developer/connect)
* [e-conomic app roles and resource permissions](https://www.e-conomic.com/developer/permissions)