Getting started with Leverandørservice
Leverandørservice is an agreement between customer and business. Complete the business agreement, activate the feature, and wait for customer consent and an active mandate status. Follow the setup and customer mandate cards. EAN and email describe invoice delivery; Leverandørservice describes the planned money route. A submitted collection is not received money. See the current guide ### Practical check
Historical retrospective - May–June 2026 This article was written afterwards and describes the feature as it worked during the stated period.
Leverandørservice is an agreement between customer and business. Complete the business agreement, activate the feature, and wait for customer consent and an active mandate status. Follow the setup and customer mandate cards. EAN and email describe invoice delivery; Leverandørservice describes the planned money route. A submitted collection is not received money. See the current guide (Markdown file, AI agent-friendly)
Practical check
Check mandate status and invoice status separately before following up with the customer.
Example
Example: A customer signs up on Friday, but the status is still Pending on Monday. Do not submit a collection from the old status; wait for Active and then check that the invoice is ready.
Setup before the first customer
Check the business agreement, activation, and visible contact details. On the customer card, consent and mandate status must be ready. Also check that the customer has an invoice address and the delivery method the document requires. A mandate can be active before the first invoice exists.
Questions: Is EAN an alternative to the mandate? No, EAN is document delivery. Why is the collection unpaid? The banking date and result come after submission.
Before submitting a collection
Confirm that the customer has not merely started sign-up but has Active status. Also check that the invoice is ready for its selected delivery method and that amount and date are visible. A customer can have an active mandate without old invoices being included automatically; choose those in the relevant review.
Payment status changes only when the banking result is recorded. Do not present a planned date in customer email as a payment receipt.
FAQ and boundaries
Leverandørservice requires both a business agreement and the customer’s mandate. One does not replace the other. EAN can deliver the document but does not create a mandate. An active mandate can still lead to a pending or rejected collection, and a submitted collection is not a receipt. Use customer and invoice status together.
Support scenario
Mandate, invoice, and bank result each have their own status. Check all three before replying to the customer. An active mandate is a prerequisite, not a guarantee that a collection was accepted or money was received.
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.
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.
