Building a Verseon integration
For many organisations, Verseon is where cases and documents come together, but the work itself often happens in other systems. What is created there is then entered into Verseon by hand, or never arrives at all. Appfront builds integrations with Verseon so that cases, documents and statuses end up in the right place automatically, and helps with the migration if you move to a different system.
What is an integration with Verseon?
Verseon is a case and document management platform from Circle Software in Eindhoven, which has been part of Visma since 2020 and continues as Visma Circle. It is used by government bodies, educational institutions and non-profit organisations to manage cases, documents and files, and, with the Verseon E-Suite, also for digital services to residents.
A Verseon integration connects that platform with the systems where the work originates. A request from a portal becomes a case, a document from a line-of-business application lands in the right file, and the status goes back to whoever asks for it. Without an integration, this is done by hand: exporting, uploading, filling in metadata. That takes time and leaves you with incomplete files.
We build custom because no two organisations have the same landscape. Which line-of-business applications you use, which interfaces are available in your Verseon environment, and whether you stay on Verseon or move to a different system all determine what the integration needs to do. If Visma Circle already has an integration that does what you need, custom work isn't necessary, and we'll tell you so.
Complete file
Every document in its place.
Status sent back
To where the work happens.
Ready for a move
Data comes along cleanly.
How we build your integration with Verseon
We start with your landscape: which systems deliver cases and documents to Verseon, which interfaces are available, and where work is currently done by hand. Then we build a first integration for the flow with the biggest gain, often a line-of-business application or a portal. You work with it for a while. Further flows, status messages and reports follow if that goes well. If you are moving to a different system, we plan the migration in stages. Afterwards, we maintain the integration as your landscape changes.
Flows and interfaces.
The flow with the biggest gain.
Statuses and further flows.
Go-live, monitoring, and maintenance when things change.
What an integration with Verseon actually does
The components below appear in almost every Verseon integration. Which ones you need depends on your systems and your plans.
Creating cases
From a portal or line-of-business application.
Documents
With case type and metadata.
Statuses
Back to the source.
Migration
To a different system.
Notifications
When a message fails.
Log
Every exchange logged.
Who we build an integration with Verseon for
The integration is intended for organisations that work with Verseon and have systems that are not yet connected to it, or that want to move from Verseon to a different system.
Municipalities
From front desk to archive.
Provinces
Cases across multiple teams.
Education
Files and documents.
Suppliers
A line-of-business application on Verseon.
Technology and integrations
This page is about integrations with Verseon. For the standards, see our page on the StUF integration and our page on the ZGW API integration; for other systems, see our page on the Corsa integration and our page on the Djuma integration. You can read about our approach on building custom software.
Why Appfront for your integration with Verseon?
Documents that stay outside the file, requests that get retyped and a migration in which data goes missing all cost an organisation time and leave files incomplete. That is what we build against: every case complete, statuses returned to the source, and a migration that carries data across cleanly.
Complete file
Nothing stays outside.
Less retyping
Every flow comes in.
Safe migration
Data comes along in stages.
Security and privacy in an integration with Verseon
The integration processes data about residents, pupils or clients, sometimes including special category personal data. We only use what the case requires, access is set up per role, keys and certificates are stored encrypted, and every message is logged.
The part we build runs in a European data centre or in your own environment, with encrypted storage and daily backups. In a migration, we check at every step that all cases and documents have arrived in full, and we record the processing in a data processing agreement.
Frequently asked questions about a Verseon integration
Questions organisations ask before they get started.
Verseon is a case and document management platform from Circle Software, which has been part of Visma since 2020 and continues as Visma Circle. It is used by government bodies, educational institutions and non-profit organisations, and, with the Verseon E-Suite, for digital services as well.
Via the interfaces available in your Verseon environment, such as StUF-ZKN, or via another route if the environment offers one. In the first step, we look at which interfaces are available for your version and what arrangements you need to make with Visma Circle for them.
Yes. When the line-of-business application produces a document or decision, the integration places it with the right case in Verseon, complete with case type, document type and metadata. The case handler no longer has to upload anything.
Yes. We extract cases, documents and metadata from Verseon and load them into the new case or archive system, in stages and with a check at each stage. While both systems run side by side, an integration can keep them in sync.
Corsa and Djuma are other systems, also from Visma Circle. The principle is the same, but the interfaces and capabilities differ. If you work with several of these systems, or are moving from one to another, an integration can connect them temporarily or permanently.
The integration reports it and records what went wrong. The message is retried or queued for review, so no case or document is lost or ends up in Verseon twice.
For organisations that use Verseon alongside line-of-business applications and portals that are not connected to it, for organisations switching away from Verseon, and for suppliers who want to connect their application. If all your systems are already connected and you are missing nothing, you do not need a custom integration.
Verseon connected to the rest?
Tell us which systems you use alongside Verseon and what is currently done by hand. We will show you how the integration works.