# Direct debit with Leverandørservice Leverandørservice is a payment method for Danish direct debit. It has two parts: the business agreement and the customer's mandate. Both must be ready before a new collection can be scheduled. Invoice delivery is separate: EAN or email sends the document, while Leverandørservice schedules the payment. ## Before inviting the customer Leverandørservice is Mastercard's scheme for collecting from Danish business customers. The payer needs a Danish CVR number and a Danish bank account. A mandate the team creates itself for a customer without a valid Danish CVR number is not sent to Mastercard, and the team gets an integration error. Customers outside Denmark therefore cannot use Leverandørservice; they can pay by card or by invoice. Alunta does not support SEPA Direct Debit or other non-Danish direct debit schemes. Open Leverandørservice in the team's payment settings and complete the setup shown by the interface. Confirm that the feature is active and the required business details are present. If setup requires approval, it must be shown as complete before you expect to use the customer mandate card. You need the business's five-digit Leverandørservice creditor number from Mastercard Payment Services. When setting up or switching to Alunta, give Mastercard Alunta ApS's data-supplier number, CVR **33643284**. This is the number the business enters with Mastercard; a technical data-supplier ID in a file is a different value. The first activation of a new setup starts in test mode. Check the setup and go live only when you are ready. If you have started the setup guide, go live through its final step. On the customer card, start the customer's sign-up or read the current status. A mandate can remain pending until the customer gives consent and confirmation is recorded. Wait for Active before using it for a new collection. ## Invoice and collection When the invoice is ready, the collection can be submitted on the displayed banking schedule. It may therefore remain unpaid in Alunta even after submission. Submitted means the process has started; it does not mean money was received. Read the collection status and invoice payment status separately. A new mandate normally applies to future invoices. Invoices created before the mandate appear separately in a review. They are not preselected. Choose only the old invoices you actually want to collect, and leave the others for manual payment or another agreed follow-up. Review amounts, dates, and the customer message before confirming. Selected existing invoices are scheduled at least three bank days after the notice to the customer. Several selected invoices can therefore fall on consecutive bank days, with the oldest due invoice first. Check the displayed date and notice for each review because bank days and notice timing can move the plan. ## The deposit on the bank statement Leverandørservice pays the money into the team's bank account as one deposit. On the bank statement it appears as `LS` followed by an eight-digit number, for example `LS 26114518`. The number is Mastercard's reference for that one deposit, and a deposit can cover several payments from several customers. Alunta stores the reference on each collection when the payment is recorded. Search for the text from the bank statement (`LS 26114518`) or just the number under **Payments**. The overview then lists the payments in that deposit, and a line above the table shows the number of payments, the total amount and the date. The line is shown only when the list is not also filtered by an invoice or by bookkeeping status. Each row shows the reference as LS deposit. The invoice's accounting details show the same reference next to the payment. Only payments recorded with a reference can be found; a payment without a reference does not appear in the search. New payments are booked with the reference in their text, so the bookkeeper can reconcile the bank line against the vouchers: in e-conomic and Uniconta as `Alunta payment invoice LS `, and in Dinero as the payment description `Payment LS `. Billy has no text field on a payment, so there the payment is booked without the reference. Payments booked before the change keep the old text. The team's AI can find the same with `find_payment_movement`: give it the text from the bank line or the number, and it answers with the payments in the deposit and the same count and total as the overview. ## The setup guide Start the setup guide under Leverandørservice or from the dashboard widget. Choose whether you are starting with Leverandørservice or moving from another system. The guide follows you onto the relevant setup pages. Administrators share the team's progress, while each person chooses whether to display the widget. Removing it does not change the agreement, collections or saved progress; add it again through the dashboard widget picker. **New setup:** You can start the guide before you have an LS agreement or creditor number. Apply through [Mastercard's agreement process](https://www.xn--leverandrservice-sxb.dk/leverandoerservice/administrer/aftale/), specify Alunta ApS as data supplier using CVR **33643284**, and save the creditor number in Alunta once the agreement is ready. Connect and enable the integration in test mode, prepare customers and subscriptions, then confirm that the agreement is ready and you have checked the setup in test mode. This is the team's own check; Alunta has not automatically verified the agreement with Mastercard. New teams do not need a switching date or existing mandates to take over. Once the new setup is ready, choose to go live through the guide. This explicit action removes the displayed test mandates and unfinished test collections through the existing test-to-live transition and completes the setup guide. Test mandates do not become live mandates. Register customers with valid live mandates before expecting real collections. A completed guide is not evidence of a mandate or a completed bank payment. **Moving from another system:** Prepare customers, subscriptions and their old LS customer numbers, obtain Mastercard's confirmed switching date, and confirm that the previous provider's collections have been stopped and outstanding submissions resolved. Alunta cannot check the previous provider's submissions or request Mastercard's switch for you. You can save and correct a confirmed future switching date before activation. Go live only on or after that date once Mastercard has completed the switch. Then take over existing mandates using their original LS customer numbers and review the first invoices through the existing LS screens. Taking over mandates does not create customers' subscriptions or mark old invoices as paid. Finish this flow after taking over mandates and resolving the displayed invoice review. In both flows, starting the guide holds new live LS transmissions until you go live through the guide. Test transmissions remain test, and necessary cancellations can still be sent. An Alunta test account must be converted to a production account before going live with Leverandørservice. The ordinary test-mode setting points to the setup guide while preparations are incomplete. ## Taking over existing mandates When a mandate cannot be safely linked to a customer, it appears in the Leverandørservice inbox. Open the preview and compare its details with the customer card. Select the customer when the match is clear, then check the customer card afterwards. Reject an entry that does not belong to the team. A takeover does not automatically move old invoices or change their status. ## Rejection, limits, and ending the connection A collection can be rejected after submission. Read the reason and follow the new-collection or manual-payment path shown by the interface. Bank limits and notice rules can affect a new date. Do not treat an accepted part of a delivery as rejected, because it could be collected again. When the bank returns a recorded payment, the invoice becomes outstanding again. Several collections can share the same mandate, date and amount. If the bank's chargeback cannot be attributed unambiguously to the right collections, an integration error requests manual review and the payments are not changed automatically. Compare the bank statement with the invoices before attempting another collection. When you deactivate Leverandørservice, review active mandates and open collections in the dialog. A cancellation request is not the same as a cancellation confirmed by the bank. Follow visible statuses for submitted collections before concluding that a debit stopped. New invoices must use another payment method afterwards. ## Example and questions Example: A customer receives an active mandate on Monday. An older DKK 500 invoice appears in the review; you select it, confirm the displayed date, and still see Submitted until the payment result is recorded. You leave another old invoice for bank transfer. Why is the invoice unpaid? The bank result has not been recorded yet. Why cannot an old invoice be selected? It must meet the conditions shown in the review, including document readiness. Why did a mandate enter the inbox? A safe customer match was missing. Why is a rejection not resolved immediately? A new attempt must follow the date and notice rules shown in the interface.