Document Denmark inbound invoice responses

[rilla]

Context

invopop/gov-dk#18 ships the reading half of inbound OIOUBL ApplicationResponses: a received response becomes its own bill/status silo entry, and the import job's result carries the business outcome (accepted, rejected, …) so workflows can branch on it. The Denmark docs still describe the previous behaviour, where any response failed the import job. Part of APP-728.

Changes

• Updates the receiving guide's behaviour list: responses become status entries with the outcome on the job result; only Reminders and unsupported response profiles now take the surfaced-not-looped path.
• Updates the receiving FAQ leaf to match, and adds "How do I know if an invoice I sent was accepted or rejected?".
• Flips the app page's "Invoice responses" limitation to Available, noting that linking a response to the invoice it answers comes in a follow-up. Extends the key features list and the Load from NemHandel action card with the response path.
• Adds a rejected color to the workflow diagram's state chips — other templates already use that state and it rendered gray.
• Adds a "Hearing back from the customer" note to the issuing guide, separating delivery confirmation from acceptance, pointing at the receiving guide.

Next

• Merge only once invopop/gov-dk#18 ships. APP-728 is deferred to post-launch (the app launched on v0.7.0 without it); the remaining chain is: review and merge Adding the OIOUBL ApplicationResponse converter gobl.dk.oioubl#26 (Related Documents Guide #25 is already approved), release the addon, repin gov-dk#18 to that release, merge Improved CO sandbox setup doc #18 and release gov-dk, then merge this PR.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
invopop	🟢 Ready	View Preview	Aug 14, 2026, 1:43 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.