Getting started with e-conomic
The e-conomic connection enabled exchange of customers, products, invoices, credit notes, and payments. Connect the relevant account under Integrations, review team relations, and choose products before the first document. A customer import does not automatically move subscriptions. Create or select a test invoice, check customer, lines, and currency, then review status in both Alunta and e-conomic. A connection or attempt is not by itself proof of booking. See the current guide ### First review
Historical retrospective - September 2024–November 2025 This article was written afterwards and describes the feature as it worked during the stated period.
The e-conomic connection enabled exchange of customers, products, invoices, credit notes, and payments. Connect the relevant account under Integrations, review team relations, and choose products before the first document. A customer import does not automatically move subscriptions. Create or select a test invoice, check customer, lines, and currency, then review status in both Alunta and e-conomic. A connection or attempt is not by itself proof of booking. See the current guide (Markdown file, AI agent-friendly)
First review
Use a synthetic customer name and a small test invoice. Check that the local customer points to the expected e-conomic customer, that the product can be selected, and that the document status changes as the interface describes. If a relation needs attention, resolve it before sending many documents.
Setup in the right order
Connect the account first, select the right business, and wait until status is ready. Then link local customers to e-conomic customers and plans to sales products. Resolve missing product or customer relations before sending many documents. Choose payment and PDF settings after reviewing the options the provider exposes.
First test
Use a synthetic customer with one line and a small amount. Review the local invoice, send or book it according to the team’s workflow, then find the same document in e-conomic. Compare customer, amount, currency, number, and payment. Do not treat an external reference as Alunta’s stable id.
Questions: Why is the customer not ready? A relation or required field is missing. Why is the PDF missing? The team may use the provider’s document, available only after booking. Why is payment different? Payment synchronization and invoice booking are separate steps.
When the document differs
A local invoice and a booked document can have different numbers or PDF layouts. This is expected when e-conomic owns numbering. Compare invoice UUID, customer, line amounts, and currency instead. A payment line in e-conomic alone also does not say that Alunta registered it; check local payment status. For a product issue, confirm that the product is active and available for sales.
FAQ: Should I import a customer before creating a subscription? That is the safe order when the customer already exists in e-conomic, but import does not create a subscription. Can an e-conomic edit fix an old Alunta invoice? Not necessarily; documents can be snapshots. When is the connection ready? Use the status shown by the integration.
FAQ and boundaries
The connection grants the team access to e-conomic; it does not guarantee that every historical document was imported. Product mapping affects new documents while old documents keep their own data. Payment import and outgoing payment synchronization can have separate settings. During testing, note whether you are seeing local, booked, or delivery status so they are not mixed.
Support scenario
During onboarding, the team should decide who checks booking, payment, and delivery. The same invoice can have a local Alunta status and a different external status without either being wrong. Reconcile using number, UUID, and amount, and do not present a provider status as the customer’s payment status.
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.
