Map plans and fees to accounting products
Open a plan's accounting mapping and choose an existing product or create one when the provider offers it. Check product number and group before saving. Fees can have a separate mapping. Mapping does not automatically overwrite every property, and blocked products cannot be normal sales items. e-conomic, Dinero, and Billy expose different options. See the current guide ### Example
Historical retrospective - May–June 2026 This article was written afterwards and describes the feature as it worked during the stated period.
Open a plan’s accounting mapping and choose an existing product or create one when the provider offers it. Check product number and group before saving. Fees can have a separate mapping. Mapping does not automatically overwrite every property, and blocked products cannot be normal sales items. e-conomic, Dinero, and Billy expose different options. See the current guide (Markdown file, AI agent-friendly)
Example
A plan can point to an existing product while a collection fee points to another. Check a new invoice line after saving to verify the mapping. Changing the mapping does not necessarily change earlier documents.
Provider-specific choices
e-conomic may ask for product number and group; Dinero and Billy can show other fields. Do not choose a blocked product, and check that fees have the intended separate mapping. Create a new test line after saving. Mapping applies to future documents; a booked invoice keeps its history.
Check a future invoice
Product mapping appears on a new document. Create a small test invoice or wait for the next new period, and check that description, item number, and group come from the expected product. If a fee should be booked separately, it needs its own product. Earlier PDFs do not change after new mapping.
FAQ and boundaries
Product mapping is a document setting, not a chart-of-accounts recommendation. Ask your accountant about the right product group. In Alunta, check that the product is active, currency and provider fit, and a new line uses the expected mapping.
Support scenario
If a product is blocked or unavailable in the selected currency, choose another valid option instead of sending a document with the wrong item. Compare a new invoice line and booked document because PDF source can differ.
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.
