Choose old invoices for a new Leverandørservice mandate
With a new mandate, old invoices are not preselected. Open the review, deliberately choose invoices to collect, and leave others for manual payment. Review amounts, displayed dates, and the customer message. A selected invoice is scheduled, not paid, and must be ready with a final number where required. See the current guide
Historical retrospective - August 2026 This article was written afterwards and describes the feature as it worked during the stated period.
With a new mandate, old invoices are not preselected. Open the review, deliberately choose invoices to collect, and leave others for manual payment. Review amounts, displayed dates, and the customer message. A selected invoice is scheduled, not paid, and must be ready with a final number where required. See the current guide (Markdown file, AI agent-friendly)
Selected invoices are scheduled at least three bank days after the notice to the customer. Several selected invoices can fall on consecutive bank days, with the oldest due invoice first. Follow the date displayed after bank days and notice timing have been calculated.
Before confirming
Record which old invoices you select and which will be paid manually. Check that amounts and dates still match the preview. Once a collection is selected, follow its status separately; it does not change the balance until payment is recorded.
A deliberate choice
First list which old invoices should be included and which remain manual. Open the review and compare your list with amount, document number, and date. Confirm the customer message so the customer knows what was selected. Afterwards follow collection status; invoice status changes only when payment is recorded.
An invoice waiting for a final number or missing required delivery data may not be ready for submission.
The customer should understand the choice
The customer-facing message should match the invoices you select. If some documents remain for bank payment, check that they were not accidentally marked for direct debit. After confirmation, bank days and notice rules can change the date; follow the displayed date and later status rather than promising a particular banking day.
FAQ and boundaries
Old-invoice selection is deliberate so a new mandate does not change customer history without review. “Selected” means the system schedules a collection under the displayed conditions. If the customer should pay manually, leave the invoice unselected. Afterwards check both collection and invoice status.
Support scenario
Bank days and notices can change the planned date, but the selected invoice set remains what the team confirmed. Check both selection and later date. A manual invoice must not be marked collected merely because it appeared in the review.
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.
