# Accounting integrations

Alunta supports integrations with e-conomic, Dinero, and Billy. Open the integrations overview to see which connections your team can access, whether they are active, and whether they need attention.

## Synchronized data

A connection can handle customers, products, invoices, credit notes, and payments. The exact direction depends on the provider and team settings. Customer import is master data; it does not automatically import subscriptions, payments, or historical invoices. Plan product mapping and any separate fee mapping are used for future documents.

### First document

Connect the account, review customers and products, and choose PDF and numbering settings. Create a fictional or low-risk invoice and check customer, lines, currency, and payment terms in both systems. A local invoice can be created or sent before external booking finishes. The invoice UUID is the stable local identity; a booked number may arrive later.

## Payments in both directions

Alunta can send a local payment to the selected accounting system, while enabled payment import can read a documented settlement back and register it locally. These are separate actions. Incomplete setup can skip synchronization without proving that the original payment failed. A zero remainder in accounting is not by itself proof of a cash payment; read the invoice payment control and its displayed match.

## Issues and next action

Open an issue from the dashboard or integration history. Statuses can show a current, hidden, or resolved issue. Follow the recommendation shown, such as checking a customer link, reconnecting an account, or reviewing a document. “Mark as handled” closes the notice after your review; it does not register payment, change an invoice, or prove that the provider fixed anything. Not every issue has a retry action.

## Payment checks and partial payments

Payment control shows the latest available observation, documented payment, partial payment, credit, and remainder. A pending check must finish before you draw a conclusion, and an older observation is not a new confirmation. Ambiguous or incomplete information should be reviewed in the accounting system.

A tolerance is a follow-up choice for a documented small remainder after payment or credit. Preview affected invoices before saving. Tolerance does not waive a wholly unpaid invoice, alter a payment, or hide an overpayment. The controls and tolerance fields available depend on the team's current settings.

### Payment control when available to the team

If payment control is available to your team, open it from the invoice or reconciliation overview and read the provider, currency, and observation date. Check the invoice number, customer, documented payment, any partial payment or credit, and the remainder in both systems. A pending observation is not a confirmed payment.

An administrator can set a tolerance for small documented remainders per currency. Select **Preview** after changing it to see affected invoices, which enter or leave tolerance, and current and proposed amounts. Save only while the preview is current. Tolerance does not waive a wholly unpaid invoice, alter a payment, or automatically stop an already issued Leverandørservice collection; follow that collection's own status and banking schedule.

Example: for a DKK 1,000 invoice with a documented DKK 995 payment and a DKK 5 tolerance, the preview shows the small remainder as a possible follow-up. An invoice with no payment is not paid by the setting, and an overpayment is not hidden. Which currencies and controls you see depends on the team's current access and setup.

### Provider differences

e-conomic, Dinero, and Billy have different document numbers, fields, and rules for credit notes and payments. Use the selected provider's displayed setup instead of copying fields from another integration. A credit note is a document; a refund is a money flow, and they should be followed separately.

## Checklist

1. Connect and confirm the right business.
2. Map customers and products, and review a test invoice.
3. Check document status, payment, and issues in both systems.
4. Use the current integration status to decide the next action.

Open the integrations overview to see the connections available to the team. Then open integration status or the issue overview to see current problems and the suggested next action.
## When an invoice is waiting

An invoice can wait for a customer relation, product mapping, booking, or a final document number. Read its specific status before sending it to the customer. When the team uses the accounting system's PDF, Alunta can hold the document until its number is available. A local preview is not the same as a booked document.

## Customers, products, and notes

Customer import and product mapping apply to the fields and documents shown by the selected flow. Review a change summary before import, especially when local addresses, emails, or invoice recipients must be kept. A note, reference, or footer can appear differently in the provider's PDF. Check a new invoice after changing it.

## When synchronization is missing

First check whether the connection is active. Then check the relevant relation and document status. An issue in e-conomic, Dinero, or Billy does not require the same action, and a successful connection does not mean all old documents were rerun. Mark a notice handled only after your review, then check the result in both systems.