Find integration issues and understand the next action

The dashboard and integration history gained visible statuses for current, hidden, and resolved issues. Open an issue, read the recommended action, and check the document again. Not every issue has retry. “Mark as handled” closes a notice after review; it does not register payment, change an invoice, or prove the provider fixed it. See the current guide ### Status is not resolution

All product updates

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

The dashboard and integration history gained visible statuses for current, hidden, and resolved issues. Open an issue, read the recommended action, and check the document again. Not every issue has retry. “Mark as handled” closes a notice after review; it does not register payment, change an invoice, or prove the provider fixed it. See the current guide (Markdown file, AI agent-friendly)

Status is not resolution

A hidden issue can still need action, and a resolved issue does not necessarily change a document that already failed. Open the related invoice or relation and check the result after the next synchronization.

From issue to check

Open the issue, read which document or relation it concerns, and perform only the recommended user action. Reopen the document and check the new status after the connection is ready. If an issue can only be hidden, still follow up on the document. A resolved issue does not mean a local invoice is paid.

Issue and document

An integration issue can concern a relation, document, or account. Note which part is affected and check that same part after the change. A new green connection status does not mean the old invoice was booked; open the document and read its own status.

FAQ and boundaries

The issue overview gathers visible user problems but does not replace document status. A hidden issue can return if the connection still needs action. A resolved issue can describe the next synchronization, but you still need to check the invoice, payment, or relation.

Support scenario

The interface can show a next action, but the team still needs to assess whether the document is financially correct. Check number, customer, amount, and payment after a correction. If the issue returns, review the connection or relation again.

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.

Bo Møller
Bo Møller
Emil Højbjerg
Emil Højbjerg

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.