> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chift.eu/llms.txt
> Use this file to discover all available pages before exploring further.

# Dinero

> Connect Dinero to your product through Chift's unified Accounting API.

Chift connector information - accounting

> **Overview legend**
>
> > <table><thead><tr><th>Column</th>
> > <th>Value</th>
> > <th>Meaning</th></tr></thead>
> > <tbody><tr><td>Geography</td>
> > <td>🇫🇷 FR · 🇧🇪 BE · …</td>
> > <td>Countries where the connector is officially supported.</td></tr>
> > <tr><td rowSpan="3">Software type</td>
> > <td>SaaS</td>
> > <td>Through API.</td></tr>
> > <tr><td>On-premise (local agent)</td>
> > <td>Software running locally — installation of a local agent is
> > required.</td></tr>
> > <tr><td>On-premise (API)</td>
> > <td>Software running locally — API available.</td></tr>
> > <tr><td rowSpan="2">Status</td>
> > <td>🔵 Live</td>
> > <td>Connector is generally available and production-ready.</td></tr>
> > <tr><td>🟣 Beta</td>
> > <td>Connector is in beta — usable in production but may still evolve.</td></tr>
> > <tr><td>Multi folder</td>
> > <td>✅ Yes / ❌ No</td>
> > <td>Connection to multiple accounting folders at the same time (see
> > [accounting folders guide](https://docs.chift.eu/unified-apis/accounting/concepts/folder/multi-folder.md)
> > ).</td></tr>
> > <tr><td>Rate limits</td>
> > <td>✅ No / ❌ Yes</td>
> > <td>Whether the target software sets rate limits on API calls.</td></tr>
> > <tr><td rowSpan="3">API keys</td>
> > <td>❎ No</td>
> > <td>No API keys required (OAuth2 client secret and client ID). No
> > requirements to activate the connector — you can create a
> > connection.</td></tr>
> > <tr><td>🔑</td>
> > <td>Keys are required to activate the connector. Chift cannot act as
> > intermediary to obtain them; we can still assist with steps to get
> > keys directly from the software provider.</td></tr>
> > <tr><td>🔑 ☑️ via Chift</td>
> > <td>Keys are required to activate the connector. You can go through
> > Chift to get the keys (intermediary or partnership keys). An
> > approval process may still apply, but you do not need to request
> > keys from the vendor on your own.</td></tr>
> > <tr><td rowSpan="3">Approval / certification process</td>
> > <td>⚡ Instant</td>
> > <td>No keys required, or Chift can encode their keys for you when
> > requested. Activation is instantaneous.</td></tr>
> > <tr><td>🟢 Approval</td>
> > <td>Approval will be granted. The vendor may require information or app
> > configuration in a developer portal before issuing keys.</td></tr>
> > <tr><td>🟠 Approval</td>
> > <td>Approval is not guaranteed — often due to integration strategy; the
> > vendor may do a deeper assessment (competitors, partnership
> > requirements, and similar).</td></tr>
> > <tr><td rowSpan="2">Activation lead time</td>
> > <td>⚡ Instant</td>
> > <td>If no keys are required, or Chift has keys ready to share with you.</td></tr>
> > <tr><td>Time</td>
> > <td>Estimated time to get the connector activated in production as a
> > result of the approval or certification process (e.g. ⏱️ 2 days, 1
> > week).</td></tr>
> > <tr><td rowSpan="3">Extra fees — software editor</td>
> > <td>❎ No</td>
> > <td>No fees charged by the software editor.</td></tr>
> > <tr><td>💰 🕹️</td>
> > <td>Fees associated with obtaining a testing account.</td></tr>
> > <tr><td>💰 🔑</td>
> > <td>Fees charged to get API keys.</td></tr>
> > <tr><td rowSpan="2">Extra fees — end-user</td>
> > <td>❎ No</td>
> > <td>The end-user does not pay extra to get integrated.</td></tr>
> > <tr><td>💰 Yes</td>
> > <td>The end-user must pay extra to get integrated.</td></tr>
> > <tr><td>Comments on costs</td>
> > <td>—</td>
> > <td>Additional notes on fees or pricing when relevant.</td></tr>
> > <tr><td rowSpan="4">Sandbox account</td>
> > <td>✅ via Chift</td>
> > <td>Chift can provide you with a sandbox.</td></tr>
> > <tr><td>🟠 Only through integrator</td>
> > <td>Only the software's integrator can provide a sandbox.</td></tr>
> > <tr><td>✅ Self-service</td>
> > <td>You can create your own sandbox.</td></tr>
> > <tr><td>✅ Trial account</td>
> > <td>It is possible to create a trial account.</td></tr></tbody></table>

[See what this connector supports ↓](#coverage)

## Introduction

Dinero is a Danish cloud accounting and invoicing software developed by Visma. It is used by small and medium-sized Danish businesses for bookkeeping, invoicing and VAT reporting.

## Activate Dinero

### Partner keys

You can use Chift's app, or register your own with Visma.

> **Use Chift's app**
>
> Reach out to your Chift point of contact. They provide the `client_id` and `client_secret` of Chift's Dinero app and configure them on your Chift platform.
>
> **No additional requirement**: the fastest way to go live.

> **Use your own app**
>
> Register your own app on the [Visma Developer Portal](https://oauth.developers.visma.com/) and get it approved by Dinero.
>
> Requires a Visma Developer account, a **Web application** in Visma Connect with the right scopes and redirect URI, and a technical review by Dinero.

The steps below apply if you register your own app. If you use Chift's app, your point of contact handles the setup for you: skip straight to [Test Dinero](#test-dinero).

**1. Create your Visma Developer account**

Sign up on the [Visma Developer Portal](https://oauth.developers.visma.com/). Set your team's country to **Denmark** and use your real CVR number, otherwise your application is rejected.

**2. Add a web application in Visma Connect**

From **My Applications**, click **Add Application** and choose **Web application**. It is Dinero's only supported client type.

Naming rules, or your application is rejected:

* Pick a **Name** and **Client ID** that clearly identify your company, such as `isv_yourcompany`.
* Do not use generic names like `isv_test`.
* Do not include "Dinero" in the name.

**3. Configure grants, scopes and redirect URI**

* Grant: `Authorization Code`, with **offline access** enabled.
* Offline access: re-use the refresh token. A 365-day expiration is recommended.
* OpenID Connect: leave it disabled.
* Scopes: `dineropublicapi:read`, `dineropublicapi:write` and `offline_access`.

Set the redirect URI to:

```text theme={null}
https://chift.app/oauth2/redirect
```

**4. Pass Dinero's technical review**

Test your app, then submit it for review. Dinero approves or rejects the app within one working day. See the [Dinero Getting Started guide](https://developer.dinero.dk/documentation/getting-started/) for the full flow.

> **[Activate Dinero in your Chift account](https://chift.app/connectors?search=Dinero)**
>
> In **Connectors**, enter your client ID and client secret. End users are then redirected to Visma Connect to authorize access.

### Connector settings

No connector-specific settings.

## Test Dinero

| | |
| - | - |
| **Environment** | Trial account |
| **How to get it** | Go to [dinero.dk](https://dinero.dk/) and click **Opret gratis konto** ("Create free account"). The account includes a 30-day Dinero Pro trial, which gives API access. |

## Vendor fees

> **Software editor (you)**
>
> No fees.

> **End user**
>
> A **Pro** plan subscription is required to use the Dinero API. The **Total** plan also works.

For plans and pricing, see Dinero's [pricing page](https://dinero.dk/priser/).

## Connect Dinero

> **[Dinero setup guide for end users](https://docs.chift.eu/help/connectors/8050.md)**
>
> The full step-by-step, with screenshots.

**Before they start, your end users need:**

* an active Dinero subscription on the **Pro** plan or above (the **Total** plan also works)

**To connect, they:**

* sign in with their Dinero account and authorize the Chift app
* choose the Dinero organization to connect
* give each sales account in Dinero the VAT code its invoices use ([VAT codes on sales accounts](https://docs.chift.eu/help/connectors/8050.md#vat-codes-on-sales-accounts))

## Rate limits

Dinero allows **100 calls per minute per organization**, on a client ID basis.

When the limit is exceeded, Dinero returns HTTP `429 Too Many Requests` with the message "API calls quota exceeded!".

Chift automatically manages these limits to optimize performance and prevent interruptions. However, once the API rate limit is reached, Chift cannot bypass these limitations.

See Dinero's [API FAQ](https://developer.dinero.dk/documentation/faq/).

## Limitations & specificities

> **Bank feed**
>
> Dinero does not support a bank feed through Chift. Dinero only integrates directly with banks itself.

> **Chart of accounts & VAT**
>
> VAT rules on journal entries:
>
> * The VAT code comes from `tax_info.tax_code`.
> * Lines without `tax_info` are sent with no VAT.
> * `tax_amount` must match the code's rate, so 0 for a zero-rate code.
> * Reverse-charge codes need a `reversed_vat_account`.
> * Dinero books the reverse-charge VAT itself.

> **Contacts (clients & suppliers)**
>
> * A Dinero contact is both a client and a supplier. It appears in both lists, with a different id: a client id starts with `customer_`, a supplier id with `supplier_`.
> * `force_merge` is not supported.
> * `external_reference` is limited to 128 characters.
> * `vat` and `company_number` are only accepted on a company, with `is_company` set to true.
> * `company_number` is stored in Dinero's EAN number field.
> * A contact created without an address gets Denmark (`DK`) as its country.
> * Partner contacts return at most one person: the contact's attention person in Dinero.

> **Invoices**
>
> * Listing invoices by type works for `customer_invoice` and `customer_refund` only. Dinero has no list endpoint for purchase vouchers, so supplier invoices and refunds are read one at a time, by id.
>
> * `force_currency_exchange` and `force_financial_period` are not supported. Dinero applies its own exchange rate and derives the period from the invoice date.
>
> * The partner must be a client id (`customer_…`) on customer documents, and a supplier id (`supplier_…`) on supplier documents.
>
> * A draft cannot carry an invoice number. Dinero assigns it when the document is booked.
>
> * On a customer invoice, customer refund or supplier refund, `invoice_number` must be numeric. It becomes the Dinero document number.
>
> * On a supplier invoice, `invoice_number` and `reference` are merged into Dinero's single external reference field.
>
> - On a customer invoice, `due_date` cannot be earlier than `invoice_date`.
> - Each sales line must use a turnover account. Dinero takes the VAT from the account, so the line's `tax_code` must match the account's VAT code, and `tax_amount` must be 0 on an account without one.
> - Each supplier line must use an account of the chart of accounts.
> - If booking fails, Chift deletes the draft it created in Dinero.

> **Attachments**
>
> * Attachments can be added to customer invoices and credit notes only. A supplier invoice or refund takes its PDF when it is created, in `pdf`.
> * A file is limited to 6 MB.

> **Journal entries**
>
> * Only the `manuel` journal, id `1`, is writable.
> * The `sales` journal, id `2`, and the `purchase` journal, id `3`, are read-only.
> * No journal can be created.
> * A posted entry needs a unique, positive integer `number`. It becomes the entry's Dinero voucher number.
> * A duplicate `number` is rejected.
> * Only `general_account` lines are accepted, not customer or supplier lines.
> * Account numbers must be numeric.
> * `number` and `reference` are merged into Dinero's single `ExternalReference` field: a 2-line entry becomes one matched Dinero line.
> * Entries in a foreign currency need a `currency_exchange_rate`. Chift converts the amounts to DKK before sending them, because Dinero cannot store foreign-currency amounts on a manual voucher.
> * `force_currency_exchange` is not supported.

## Coverage

Open in new tab

Chift Coverage Matrix - accounting

> **Matrix Legend 🧭**
>
> <table><thead><tr><th>Status</th>
> <th>Meaning</th></tr></thead>
> <tbody><tr><td>✅ Implemented</td>
> <td>Endpoint is implemented and available.</td></tr>
> <tr><td>❌ Not supported</td>
> <td>Endpoint is not supported by the target software (connector
> limitation). Cannot be implemented.</td></tr>
> <tr><td>💬 On request</td>
> <td>Endpoint is not implemented but feasibility is validated. Can be
> implemented on request — contact your Chift point of contact to
> discuss scope and timing.</td></tr>
> <tr><td>🔎 To be analyzed</td>
> <td>Endpoint is not implemented and feasibility has not yet been fully
> assessed. Analysis is pending.</td></tr></tbody></table>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.