Key takeaways
- Continia Software has acquired gbedv GmbH & Co. KG, the maker of OPplus for the German-speaking market.
- OPplus is being replaced by two products: Continia Banking and Continia Finance.
- Continia Banking bundles payments — the functions from OPplus and Dynamo Pay.
- Continia Finance takes the remaining OPplus modules, among them associations, item display and printing, balance sheet and VAT, AP-managed G/L accounts and extended fixed asset accounting.
- There is a published timeline for OPplus with an end of sale and an end of support; the dates differ between cloud and on-premises and should be checked directly with Continia.
- The change is not an update but a migration with setup, testing and training — it belongs in a plan rather than in a waiting position.
What has happened
Continia Software, best known in the German market for document management and capture, has acquired gbedv GmbH & Co. KG — the maker of OPplus. Two product families that previously sat side by side now belong together.
Rather than carrying OPplus forward unchanged, Continia has re-cut the functionality and distributed it across two cloud-native products. OPplus and Dynamo Pay are being retired; Continia Banking and Continia Finance take their place.
For companies running OPplus this is not a footnote. OPplus does not sit at the edge of the finance department but in the middle of it — in payments, in open item management, and in reports that are used daily.
What moves into which product
The split follows a clear line: everything to do with the movement of money goes into one product, the rest into the other.
- Continia Banking: all payment processing from OPplus and Dynamo Pay — payment runs, bank statements, matching and settlement
- Continia Finance: associations
- Continia Finance: item display and printing
- Continia Finance: balance sheet and VAT
- Continia Finance: AP-managed G/L accounts
- Continia Finance: extended fixed asset accounting
Why this is not an update
The most important point for planning: you are not swapping one version for a newer one but one product for two others. Configurations do not simply carry over, naming and workflows differ, and splitting across two products means responsibilities and licences have to be settled again.
In practice that means the same as any migration in the finance department: you need a test environment, a reconciliation of the setup, a dry run with real data — particularly for payment runs and bank statement processing — and time for the users. Switching in the middle of a month-end close is not a good idea.
The second point is timing. There is a published lifecycle for OPplus with an end of sale, limited support and an end of support, and the dates differ between cloud and on-premises operation. Because a finance department cannot work without functioning payments, do not take these dates second-hand: check the current timeline directly with Continia and plan with a clear margin ahead of it.
How to approach the change
The sequence does not differ fundamentally from other migrations, but the finance department is less forgiving than other areas.
- Inventory: which OPplus modules do you actually use, and who works with them daily?
- Mapping: which of those land in Continia Banking, which in Continia Finance — and what, if anything, is missing?
- Check the dates: the current lifecycle at Continia, for your operating model (cloud or on-premises)
- Set up a test environment and carry the configuration across rather than reinventing it
- Dry run with real data, particularly the payment run and bank statement processing
- Train the users and put the cutover outside the closing period
Frequently asked questions
- Continia publishes a lifecycle with several stages — end of sale, limited support, end of support — and the dates differ between cloud and on-premises operation. Because secondary sources circulate different dates and your payment processing depends on this, we deliberately do not name one here: check the current status directly with Continia, or talk to us and we will establish it for your specific installation.
- That depends on what you use today. Anyone using OPplus essentially for payments ends up mainly with Continia Banking. Anyone additionally using item display, balance sheet and VAT, or extended fixed asset accounting also needs Continia Finance. Taking stock of the modules actually in use is therefore the first step — and it often turns out that nobody has opened some of them for years.
- Technically the software keeps running for a while afterwards. In practice it is the worst option: without support there are no adjustments to new Business Central releases, no fixes, and no response to changed requirements in payments or VAT. And the migration does not get smaller, only more urgent — with less room for testing.
- Usually yes, and often it is the cheaper route. The successor products are cloud-native, and if you are touching every customisation and extension anyway, it is a good moment to plan both together. Two separate projects one after the other mean testing twice, training twice and disruption in the finance department twice.