Follow up on rejected Leverandørservice collections
When a Leverandørservice collection is rejected or charged back, Alunta now gathers it as a follow-up case so you can see which invoices need action and why. From the overview you can schedule a new collection on a later date, mark the invoice as paid manually or by bank transfer, or dismiss the case.
Historical retrospective - July 2026 This article was written afterwards and describes the feature as it worked during the stated period.
When a Leverandørservice collection is rejected or charged back, Alunta now gathers it as a follow-up case so you can see which invoices need action and why. From the overview you can schedule a new collection on a later date, mark the invoice as paid manually or by bank transfer, or dismiss the case.
You can also set your bank’s daily Leverandørservice limit. An individual collection above the confirmed per-collection limit is stopped and moved to follow-up. When several collections together exceed the day’s limit, Alunta sends what fits and moves the remainder to later bank days. If no later date can be found after continued attempts, follow the displayed recovery case.
Keep accepted and rejected collections separate
When a delivery contains several collections, review each status. Schedule new attempts only for rejected items and let accepted items follow their normal status. The bank limit affects the new date shown; a submitted collection is still not received money. See the current guide (Markdown file, AI agent-friendly)
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.
