17 November 2026
Continia published a Denmark-targeted announcement on 25 September 2026 that all product prices will be adjusted from 1 January 2027. The headline items are a general 5% price increase for both cloud and on‑premises licenses, and higher increases (listed as 15%) for older payment products that Continia is phasing toward its new Continia Banking solution. Enhancement Plans that renew from 1 January 2027 will move from 20% to 21% of license value. Marketplace apps are included in the change and new price lists are already published on Continia’s pricing pages.
What changed (practical facts)
- Effective date: 1 January 2027. The announcement was published 25 September 2026.
- General licence price change: +5% for cloud and on‑premises products.
- Legacy payment solutions: a larger adjustment (noted in the announcement as 15%) for older payment modules. Continia is recommending migration to the newer Continia Banking product.
- Microsoft Marketplace: Continia apps sold via Microsoft Marketplace will reflect the new prices as of 1 January 2027.
- On‑premises subscriptions: price changes apply when those subscriptions are renewed.
- Enhancement Plan: increase from 20% to 21% for renewals from 1 January 2027; indexing remains 0% per Continia’s terms.
The announcement points customers to the published pricing pages for the full detail and to engage their Continia partner about migrations to Continia Banking where relevant.
Why this matters to Danish Business Central deployments
Many Danish customers use Continia for three concrete purposes that are sensitive to vendor price changes:
- Peppol/OIOUBL (NemHandel) e‑invoicing and document delivery: if you route E‑Invoices, OIOUBL or Peppol messages through a Continia delivery service or operator, licence and routing fees are part of your ongoing operating cost.
- Document output and PDF/email automation: Continia Document and Delivery components are commonly used for invoice output and transmission in Danish setups.
- Bank integrations and payment processing: Continia’s older payment modules (Payment Management, OPPlus, DynamoPay) are called out for higher increases and are being consolidated into Continia Banking.
At the same time, Danish legal obligations such as SAF‑T and VAT reporting are implemented by the Danish localization in Business Central (the localization handles SAF‑T exports and VAT reporting formats). Those localization obligations don’t disappear, but the cost of the third‑party delivery, routing and payment software that transmits e‑invoices and payments can rise independently of the localization.
What this means for companies in Denmark
- Check how many invoices and payments you actually route via Continia (including any Continia Delivery Network or operator arrangements). Quantify annual volume so you can calculate the impact of a 5% or 15% uplift.
- Map every Continia contract to a renewal date. Marketplace subscriptions follow the 1 January 2027 list price; on‑premises contracts will change at renewal. Know which contracts renew before or after 1 January.
- If you use older payment modules (Payment Management / OPPlus / DynamoPay), plan a migration path to Continia Banking or another bank connector — these modules face the larger increase and Continia explicitly recommends switching.
- Consider routing alternatives for Peppol/OIOUBL (NemHandel). Microsoft’s built‑in e‑document/Peppol connectors for Business Central or other Peppol operators can be an option; run a total‑cost comparison that includes per‑message fees, setup and ongoing maintenance.
- Remember SAF‑T and Danish VAT reporting remain the responsibility of the Danish localization in BC; the pricing change affects how you send documents and payments, not the localization files themselves.
How we would approach it (Invice recommendations)
1. Inventory and quantify: produce a short list of invoices/messages and payment files routed via Continia in the last 12 months. Include volumes per month, any per‑message fees and the parts of your setup using older payment modules.
2. Contract timeline: create a calendar of Continia licences and Enhancement Plan renewals. Mark which renew on or after 1 Jan 2027 so you know which will pick up the new prices.
3. Cost comparison: using your volumes, calculate the 5% / 15% uplift and model alternatives: continuing with Continia, migrating to Continia Banking (for payments), or moving Peppol routing to Microsoft’s e‑document service or another Peppol operator. Include migration effort and testing in the model.
4. Decision window: for contracts that renew in the coming 3–9 months, decide whether to absorb, negotiate with Continia/partner, or move routing before renewal.
5. Payment modules: if you still use Payment Management, OPPlus or DynamoPay, prioritise a migration plan to a modern bank connector (Continia Banking or a Danish bank connector that supports local bank formats).
If you want, we can help map volumes from your Business Central tenant, verify which objects use Continia routing, and run a straightforward TCO comparison against Microsoft’s e‑document connectors and other operators so you can make a procurement decision ahead of renewal.
Source: Continia

