Getting started with Dinero

Dinero gained its own connection flow as a supported accounting system. Connect the account, confirm the business, and review the product and document options Dinero shows. Supported invoices and credit notes can be sent for booking; its fields and rules are not the same as e-conomic's. Review a fictional invoice before wider use, and follow payment and document-number status separately. See the current guide ### First review

All product updates

Historical retrospective - November 2025 This article was written afterwards and describes the feature as it worked during the stated period.

Dinero gained its own connection flow as a supported accounting system. Connect the account, confirm the business, and review the product and document options Dinero shows. Supported invoices and credit notes can be sent for booking; its fields and rules are not the same as e-conomic’s. Review a fictional invoice before wider use, and follow payment and document-number status separately. See the current guide (Markdown file, AI agent-friendly)

First review

Create a small test document and compare PDF, number, and status in both systems. Dinero can have product and credit-note rules different from other providers. Handle a relation issue in the integration view; do not change customer master data merely to obtain a green status.

Setup and review

Open Integrations, connect Dinero, and select the correct business. Review the product and customer relations shown before sending an invoice. Use a new synthetic customer for the first test and compare status, number, and PDF in both systems. Dinero may display credit notes, payment terms, and products differently.

When something is wrong

Read the visible issue status and inspect the affected relation. Do not treat an issue as solved merely because the document exists locally. After correcting a relation, check a new or retried document action. Payments and refunds have their own status signals.

Questions: Is a locally paid invoice booked? Not necessarily. Is a credit note a refund? No, document and money flow are separate.

From connection to booking

Connection is only the first step. Choose customers and products, try one document, and read status after each action. Dinero may assign a number at booking, so the team can see a local number first. Follow a credit note as a document and a refund through payment status. Resolve an ambiguous customer relation before synchronization.

FAQ: Can e-conomic instructions be used in Dinero? Only the general sequence; fields and rules are provider-specific. Is sent the same as booked? No. Does hiding an issue remove it? No, hiding does not change the document.

FAQ and boundaries

Evaluate the Dinero connection using the documents and fields Dinero shows. A product in Alunta is not automatically linked to Dinero, and an external document number does not replace the UUID as a stable reference. If an invoice was sent but not booked, read the synchronization status in Alunta and check Dinero afterwards.

Support scenario

Use the Dinero section as a provider-specific reference. If an action is absent, follow the visible option instead of copying an e-conomic step. Before wider synchronization, review a test customer, product, invoice, and credit note.

Check after the action

Use this check during follow-up: note what was visible before the action, perform only the selected action, and check the document or mandate afterwards. Read a status again before informing the customer if it changes later. The retrospective describes the documented milestone; the current guide and interface determine today’s steps. Examples use fictional customers, amounts, and dates.

Bo Møller
Bo Møller
Emil Højbjerg
Emil Højbjerg

The people and AI helpers behind the updates

Bo Møller and Emil Højbjerg are the primary developers behind Alunta. They spend most of their time coding, so they have delegated the wording of these explanations to our AI helpers.

The AI helpers write from the updates we have deployed to the product. Bo and Emil are behind the changes and remain responsible for ensuring the information reflects what was actually released.