Import and update customer data from the accounting system
Customer import gained preview and field selection. Choose customer(s), review differences in name, address, country, contact fields, and invoice recipients, and confirm only wanted changes. Master-data import is not import of subscriptions, payments, or old invoices. Local edits can be overwritten for selected fields. Registration lookup is a separate source. See the current guide ### Review changes
Historical retrospective - June–September 2026 This article was written afterwards and describes the feature as it worked during the stated period.
Customer import gained preview and field selection. Choose customer(s), review differences in name, address, country, contact fields, and invoice recipients, and confirm only wanted changes. Master-data import is not import of subscriptions, payments, or old invoices. Local edits can be overwritten for selected fields. Registration lookup is a separate source. See the current guide (Markdown file, AI agent-friendly)
Review changes
Read what will change field by field. If you only want to update an address, deselect name and contact fields. Check the customer card and accounting master data afterwards.
Review the preview
Select the customer first, then open the change summary. Deselect fields you want to keep locally and confirm only changes from the selected accounting source. Open the customer card afterwards and compare country, email, address, and invoice recipients. Do not import subscriptions merely because master data looks correct.
Questions: What if e-conomic has another customer group? New and existing customers can follow different rules. What if the registration number differs? Treat registration lookup as a separate source.
Check the result
After confirmation, open the customer in Alunta and the accounting system. Compare selected fields and check that a local email or invoice recipient was not unintentionally overwritten. If several customers share an external identity, stop and resolve the match instead of accepting a bulk change.
FAQ and boundaries
Use import as a controlled master-data update. It is not a subscription migration and should not move payments. If you cannot explain a previewed change, leave that field deselected. Always check the result in the local customer card.
Support scenario
The import preview is the basis for confirmation. If a change looks wrong, deselect the field and keep the local value. Customers, products, subscriptions, and payments are separate domains; a successful customer import is not a complete accounting migration.
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.
If the result differs
If the result does not match expectations, keep the visible status and investigate the relevant prerequisite instead of repeating the action blindly. Check currency, date, customer, payment method, and whether the document was already sent or booked. When answering a customer, distinguish what the system recorded from what the bank or recipient has not yet confirmed.
Close the workflow
A safe workflow ends with a new check, not with clicking Save or Send. Open the new invoice, mandate, or payment record and confirm that the result matches the message the customer receives. If confirmation is still missing, describe the status as pending and set the next review point. Record internally what was selected and which status was shown. This makes the next support check concrete and prevents an already accepted delivery, payment, or relation from being treated as new.
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.
