Skip to main content

Introduction

e-conomic is a cloud-based accounting software developed by Visma, primarily used by small and medium-sized businesses in Denmark and Scandinavia. It offers features such as invoicing, bookkeeping, VAT reporting, and financial reporting.
e-conomic uses a dual-API model: a legacy REST API (restapi.e-conomic.com) and a newer OpenAPI (apis.e-conomic.com). Chift uses both depending on the endpoint.

Configure e-conomic

Prerequisites

The end user must have an active e-conomic subscription. Beyond that, the prerequisites depend on the authentication option you choose:
  • Option 1 — Use Chift’s app: no additional setup required.
  • Option 2 — Use your own app: you must have an e-conomic developer agreement, create an app in your developer account, and store its AppSecretToken.

Activation process

When connecting your end users to e-conomic, you can choose between two authentication approaches. In both cases the end-user experience is identical: the user clicks an installation URL and generates an AgreementGrantToken.

Option 1 — Use Chift’s app

Use Chift’s own e-conomic app. No setup is required — the app appears under the Chift name on the end user’s e-conomic account.
→ Reach out to your Chift point of contact and he will activate it for you.

Option 2 — Use your own app

Create your own e-conomic developer app and provide your own AppSecretToken. The app then appears under your own brand name on the end user’s e-conomic account. This requires an e-conomic developer agreement.
  1. In your developer account, click Create a new app.
Create a new app button in the e-conomic developer portal
  1. Fill in the New app form. Note that the name and roles cannot be changed later.
New app form in the e-conomic developer portal with required roles and required modules
Required roles — select at least one role based on your use case. e-conomic validates that the end user granting access has the matching rights.
  • Superuser — recommended for full accounting integrations (journals, customers, invoices, suppliers, attachments, company info). Note that regular users won’t be able to authorize access with this setting.
  • Bookkeeping — suitable if you only need access to journals, entries, accounts and attachments (no access to customers or company information).
  • Sales — if you want to handle customers and invoices.
  • Project employee — not applicable to the Chift connector.
To handle accounting data, customer data and company information at once, use one of these setups: Superuser, or Bookkeeping + Sales. Required modules — modules extend e-conomic’s default features. Select a module only if your app depends on it. If not all of your customers have a given module, leave it unselected — otherwise customers without it won’t be able to install the app.
  1. After creating the app, retrieve its AppSecretToken and InstallationURL from the app’s credentials page.
e-conomic app credentials page showing AppPublicToken, AppSecretToken and InstallationURL

Test e-conomic

e-conomic provides a free trial environment that can be used for testing integrations. To create a test account:
  1. Go to e-conomic.dk/regnskabsprogram/demo-alle.
  2. Sign up for a free 14-day trial with demo data.
  3. If you need the trial extended beyond 14 days for testing purposes, contact api@e-conomic.com with your agreement number and the duration needed.
The sandbox is a real e-conomic agreement — it uses the same APIs as production. There is no separate sandbox base URL.

Connect e-conomic

To activate a connection with e-conomic, users will have to go through the following steps.

Rate limits

e-conomic uses a cost-based token bucket system (rolled out December 2025). Rather than limiting the number of requests per second, e-conomic limits the cost of requests, where each endpoint has a different cost based on its load on the platform. When a limit is exceeded, e-conomic returns an HTTP 429 Too Many Requests error. Response headers include:
  • X-CallCost: the token cost of the request just made.
  • X-RateLimiting: current bucket status (e.g. limit-2000-per-60-seconds: 1450/2000).
Chift handles retries automatically using exponential backoff. For more details, see the e-conomic rate limiting documentation.

Technical limitations & specificities

Single-folder connector

Each e-conomic connection maps to a single accounting agreement. One Chift connection = one e-conomic agreement.

Journal restrictions

e-conomic journals have an allowedEntryType field that restricts which account types can be used within a journal. This affects how journal entries are created via the Chift API. When creating a journal entry, all lines must match the journal’s allowedEntryType. If mixed line types are sent to a restricted journal, the API returns an ERROR_JOURNAL_NOT_GOOD_SCOPE error. For journals with allowedEntryType: 2 (customer payment), the contra account (bank account) is automatically applied by e-conomic based on the journal’s customerContraAccount setting — no need to specify it explicitly. To retrieve the list of journals and their restrictions, use GET /consumers/{id}/accounting/journals. The force_general_account field is not supported when creating journal entries in e-conomic. e-conomic always uses the collective account associated with the customer or supplier, so providing this field returns an error.

VAT auto-calculation

When creating journal entries with a vatCode, e-conomic automatically calculates and posts the VAT amount to the corresponding VAT account at booking time. No explicit VAT line needs to be created.

Coverage