End Leverandørservice and follow open collections
Deactivation starts a guided review of mandates and open collections. Decide how future invoices will be paid before confirming. A cancellation can be requested without being confirmed by the bank, and a submitted collection can continue its own flow. Check visible status changes before concluding that the debit stopped. See the current guide ### After deactivation
Historical retrospective - June 2026 This article was written afterwards and describes the feature as it worked during the stated period.
Deactivation starts a guided review of mandates and open collections. Decide how future invoices will be paid before confirming. A cancellation can be requested without being confirmed by the bank, and a submitted collection can continue its own flow. Check visible status changes before concluding that the debit stopped. See the current guide (Markdown file, AI agent-friendly)
After deactivation
Review open invoices and choose another payment method for future periods. Continue following collections already shown as submitted or pending. Deactivation does not change historical payments.
Before and after confirmation
Before deactivation, note active mandates and submitted collections. Review the dialog list, choose the new handling for future invoices, and confirm. Afterwards check that new periods no longer use Leverandørservice, while earlier submitted collections continue on their own status pages.
A cancellation request may need later confirmation.
Open collections need separate review
List submitted, pending, and cancelled collections before deactivation. After the feature is closed, still check outcomes for collections already in progress. If an invoice was not collected, choose another payment method or manual payment according to the visible status; deactivation alone does not change the amount.
FAQ and boundaries
Deactivation concerns future use of the feature. It does not automatically reverse historical payments or create a refund. Collections already submitted must be followed even after new periods use bank transfer or another method. A requested cancellation is only the next status until the outcome is confirmed.
Support scenario
After cancellation, follow a collection still shown as submitted until the bank returns a result. Only then can the team choose bank payment, a new collection, or another option. Deactivation is not a refund.
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.
