e-conomic

Overview Legend 🧭

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 end 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, who 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.

2. Fill in the New app form. Note that the name and roles cannot be changed later.

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.

3. After creating the app, retrieve its AppSecretToken and InstallationURL from the app’s credentials page.

Connector setup

Before creating connections, you can preconfigure the e-conomic connector at connector level from the Chift Platform. Fields set here are shared by all connections and hidden from your clients.

Field	Description
App Public Token (required)	The app public token of your application.
Installation URL (required)	The URL used to retrieve the agreement grant token.
Entry numbering	Choose how voucher numbers are assigned when journal entries are created — see the options below.

Option	Behavior
Validate the entry number against the journal’s range and reject duplicates. (default)	Chift checks the entry number against the journal’s range and checks for duplicates system-wide, not just within this journal. This is because e-conomic doesn’t prevent duplicates across journals and booked entries carry no journal information. Returns ERROR_INVALID_FIELD_FORMAT_NUMBER (422) if out of range, or ERROR_ENTRY_NUMBER_ALREADY_USED (409) if a duplicate is found.
Let e-conomic assign the next sequence number automatically. The number field is combined with description instead of used as the voucher number.	e-conomic assigns the voucher number from the journal’s own sequence. The entry number that would have been used is instead appended to the description field.
Let e-conomic assign the next sequence number automatically. The number field will be ignored and won’t be added to the description.	e-conomic assigns the voucher number from the journal’s own sequence. The entry number that would have been used is discarded entirely and does not appear anywhere on the entry.

Sensitive information is not retrieved from the database once saved. Clear a field to delete it.

The two automatic assignment options carry risks (out-of-range sequences, duplicate voucher numbers, entries merged across journals). See Technical limitations & specificities below.

Test e-conomic

e-conomic provides a free trial environment that you can use to test 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 [e-mail] 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.

• English article: Help Center - e-conomic EN

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.

Parameter	Value
Bucket size (burst capacity)	2,000 tokens per agreement
Refill rate (sustained rate)	30 tokens/second (over 60s)
Cost per request	Varies by endpoint (e.g. GET /accounts/{id} = 1 token, GET /invoices/booked/{id} = 13 tokens)

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

Entry numbering

Entry numbering behavior is configured at connector level — see Connector setup above for the available options.

Risks with automatic assignment (either of the two “Let e-conomic assign” options)

• Sequence can run out of range. The sequence has no awareness of the journal’s configured min/max, and can drift past it. Returns ERROR_JOURNAL_NOT_CONFIGURED (400): “The next sequence for the journal entry id is out of bound. Please choose another journal or increase the max possible sequence number in the configuration of the journal.” Fixes: switch journal, raise the journal’s max (not possible once it’s at the system ceiling of 999999999), lower the journal’s sequence value instead (see below), or turn off automatic assignment.
• Lowering the sequence can cause duplicates. If the journal’s sequence is manually lowered in e-conomic (e.g. to work around a maxed-out range), new entries can collide with previously created ones. e-conomic gives no signal when this happens.
• Duplicates across journals are merged. Since booked entries carry no journal reference, two entries from different journals sharing the same voucher number and same year (e.g. 2026$9002602) will be merged into one. This can happen even without a manual sequence change, since each journal has an independent counter.

If entries need to stay strictly separate and traceable, keep validation enabled (the default).

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.

allowedEntryType	Restriction	Accepted Chift line types
0	All types	general_account, customer_account, supplier_account
2	Customer Payment	customer_account only
3	Supplier Invoice	supplier_account only
4	Supplier Payment	supplier_account only
5	Finance Voucher	general_account only
10	Manual Customer Invoice	customer_account only

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), e-conomic automatically applies the contra account (bank account) based on the journal’s customerContraAccount setting. You don’t 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. You don’t need to create an explicit VAT line.

Coverage