Take over mandates and work through the Leverandørservice inbox

Historical retrospective - June 2026 This article was written afterwards and describes the feature as it worked during the stated period.

Mandates that cannot be safely linked to a customer appear in the inbox. Open the preview, compare its details with the customer card, and choose a customer only when the match is clear. Reject entries that do not belong to the team. A takeover may replace a previous mandate on the customer card, but does not move old invoices or change their payment status. See the current guide (Markdown file, AI agent-friendly)

Decide before confirming

Compare the customer name and details shown in the preview. If two customers could match, do not guess. Reject or investigate the entry further so a mandate is not linked to the wrong customer.

Review with a fictional customer

Imagine a mandate for “Example ApS”. Open the preview, check that its identification details match the customer card, and select the customer. After confirmation, open the customer’s Leverandørservice card and check status. If details do not match, reject the entry rather than trying customers at random.

The takeover says nothing about open invoices. Open the invoice list and decide separately how they will be paid.

What takeover does not do

Creating the relation on the customer card does not change an old invoice’s payment method, create a payment, or automatically submit a collection. Open the invoice list after takeover and use the separate review when older documents should be selected. This keeps customer matching separate from money movement.

FAQ and boundaries

The inbox is for linking or rejecting mandates, not an automatic payment import. If a mandate replaces an existing one, the team must still review old invoices and open collections. Do not select a customer from one name alone when several records look similar.

Support scenario

Always check the customer card after a takeover. If status does not become active, follow the displayed mandate action and do not start an invoice collection based on takeover alone. Old invoices remain a separate 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.