Joint arrangements Multi-tenant per participant Wgr-proof

Custom software for partnerships

Appfront builds custom software for inter-municipal partnerships and joint arrangements (gemeenschappelijke regelingen): one application that serves multiple participants, each with their own configuration. With separation per participant (multi-tenant), authorisation per municipality, reporting and cost allocation per participant, and integration with the systems of every participating organisation. Precisely where off-the-shelf packages often fall short.

What is software for a partnership?

More and more municipalities carry out tasks together in a joint arrangement under the Joint Arrangements Act (Wet gemeenschappelijke regelingen, Wgr): shared service centres for ICT, HR or finance, tax collaborations, regional social services and work companies, environmental services, and waste and archive services. Such a partnership serves multiple participants, and it is precisely that multiplicity that places its own demands on the software.

Custom software for a joint arrangement therefore serves multiple participants, each with their own set-up, from a single system: data and case files kept separate per participant (multi-tenant), authorisation per municipality, reporting and cost allocation per participant, and integrations with the varied systems of each participating organisation. We configure the allocation key, roles and integrations exactly as agreed in the arrangement.

Off-the-shelf packages usually assume one organisation with one set-up; when there are several tenants with different ways of working, settlement and integrations, that becomes a constraint. Custom software lets you model that separation and settlement precisely. We build in line with the Baseline Informatiebeveiliging Overheid (BIO, the Dutch government information security baseline) and tailor the software to the arrangement's actual processes, so it grows with you as participants join or leave. Also see our software for municipalities.

One system, multiple participants

Set up as multi-tenant: each participating municipality has its own separate environment within the same application. The joint arrangement is managed centrally, while each participant keeps its own set-up, data and way of working.

Reporting per participant

Management and accountability information per municipality and for the arrangement as a whole. Each participant sees its own figures, while the board of the joint arrangement keeps the overall picture, aligned with the budget and annual accounts.

€

Cost allocation and settlement

Usage, volumes or effort are tracked per participant and allocated according to the agreed allocation key. Substantiated overviews per municipality make settlement within the arrangement traceable and auditable.

Our approach to software for joint arrangements

We follow an approach that removes uncertainty early and delivers software that all participants understand and trust. From an initial analysis of the arrangement, each participant's set-up and the integrations required, through to go-live and ongoing maintenance, every step is aimed at an application your joint arrangement can continue to manage itself.

1
Analysis & scope

We map out the arrangement: which participants, which processes, how the set-up differs per municipality, which allocation key applies and which systems need to be integrated for each participant.

2
Design

We design the multi-tenant architecture, the separation and authorisation per participant, the reporting and settlement model and the interfaces, with the BIO as our starting point.

3
Build and iteration

Implementation with automated tests, structured logging and monitoring. You and the participants see working versions along the way and help steer the set-up.

4
Go-live & maintenance

Controlled go-live with data validation and a safety net, followed by ongoing maintenance, including when a participant joins or leaves.

What software for a joint arrangement delivers in practice

We tailor every application to the arrangement, its participants and the connected systems. Below are the features we deliver most often for joint arrangements and shared service centres that serve multiple participants from a single system.

Multi-tenant per participant

Each participant's data, case files and settings are logically separated within the same application. The joint arrangement is managed centrally; each participating municipality keeps its own set-up, without data getting mixed between participants.

Authorisation per municipality

Roles and permissions per participant following the principle of least privilege: an employee sees and edits only what belongs to their own organisation. Administrators of the joint arrangement keep overall control, with an auditable separation of duties.

Reporting & accountability

Management information per participant and for the arrangement as a whole: dashboards, periodic overviews and exports aligned with the budget and annual accounts. Each municipality can account for itself, while the board sees the overall picture.

€

Cost allocation & settlement

Usage, volumes or effort are tracked per participant and allocated according to the agreed distribution key. We set up the allocation method as laid down in the joint arrangement (gemeenschappelijke regeling), with substantiated overviews per participant.

Integration per participant

Every participant runs its own systems. We connect to standard government interfaces such as Digikoppeling and the ZGW APIs, with an integration set up to suit each municipality.

Participants joining and leaving

Arrangements change: municipalities join or leave. The software is built so that a new participant can be set up or a departing participant can be wound down cleanly, including data transfer and adjustment of the distribution key.

Which partnerships it suits

Joint arrangements come in many forms. We see a number of patterns come up often, and the same core applies to each of them: multiple participants, each with their own set-up, with reporting and cost allocation per participant.

Shared service centres

Shared IT, HR or financial services for multiple municipalities. One application serves all participants, with service delivery and reporting per municipality and a settlement that substantiates the effort per participant. Often combined with our software for municipalities.

€

Tax collaborations

Regional partnerships that levy and collect municipal taxes for multiple participants. Assessments, objections and settlement are tracked per municipality. See also our software for municipal taxes.

Social services & work companies

Regional social services and work companies that handle benefits, reintegration and participation for multiple municipalities. Case files and reporting per participant, with integration to national services such as Suwinet.

Environmental, waste and archive services

Implementation services that carry out tasks on behalf of multiple municipalities, such as an environmental service that is itself a joint arrangement. Work processes and accountability per participant. See also our software for environmental services.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and government integrations

We build on a modern, maintainable web stack and connect to the standard government interfaces, configurable per participant. This way each connected municipality stays connected in its own way, and your partnership can continue to manage or further develop the software itself.

React / Vue / TypeScript Node.js / Python / .NET PostgreSQL multi-tenant REST & GraphQL APIs OAuth 2.0 / OIDC / SSO Role-based access control (RBAC) Digikoppeling ZGW APIs (case-oriented working) StUF messages Audit logging Containerisation / CI-CD Encryption in transit & at rest WCAG 2.1 AA / DigiToegankelijk Monitoring & alerting

Why Appfront for your partnership?

Appfront builds custom software for the Dutch government and understands the particular position of a joint arrangement: you work on behalf of multiple participants, each with their own set-up and their own accountability. We always start with a thorough analysis of the arrangement and the processes per participant, because software must not only be technically correct but also do justice to the agreements within the partnership.

On every project we write clear documentation and make sure your own organisation, or a future supplier, can understand and manage the software. No black box, but transparent code and clear agreements on monitoring, alerting and maintenance.

You work with a dedicated point of contact who understands both the technical and the functional side. That keeps communication lines short, prevents miscommunication and speeds up decisions when choices have to be made during the build.

Also see our services around software for municipalities, software for environmental services, software for water authorities and AI for municipalities and government. Or get in touch directly.

  • Experience with custom software for the Dutch government
  • Multi-tenant architecture with separation and authorisation per participant
  • Reporting and cost allocation per participant, configured around the allocation key
  • Development in line with the BIO, GDPR and accessibility requirements
  • Connecting to government interfaces such as Digikoppeling and the ZGW APIs
  • Clear documentation that your organisation can read and manage
  • A single point of contact, no passing you between account managers
  • Ongoing maintenance, including when participants join or leave

Security and privacy in software for shared-service partnerships

A shared-service partnership processes personal data on behalf of multiple participants. Appfront builds in line with the Baseline Informatiebeveiliging Overheid (BIO), the Dutch government information security baseline. That means, among other things: data minimisation, role-based access and data isolation per participant, encryption in transit and at rest, and extensive logging of processing activities.

We document the data flows and processor roles per participant, so that every connected municipality can keep its record of processing activities complete and demonstrably comply with the GDPR. Where citizens or businesses use the software, we build to the accessibility requirements (WCAG 2.1 AA / DigiToegankelijk) so that the service is usable for everyone.

More about our approach to security: information security policy and CVD policy.

  • Development in line with the Baseline Informatiebeveiliging Overheid (BIO)
  • GDPR-compliant data processing and data minimisation
  • Data isolation and role-based access per participant
  • Encryption in transit (TLS 1.2+) and at rest
  • Audit logs with traceable processing per participant
  • WCAG 2.1 AA / DigiToegankelijk where citizens use the software
  • Monitoring and alerting for anomalies
  • Documentation for each participant's record of processing activities

Frequently asked questions about software for shared-service partnerships

Answers to the questions we get asked most often about software for intermunicipal partnerships (gemeenschappelijke regelingen).

Software for a shared-service partnership is a custom application that serves multiple participants, for example the municipalities within an intermunicipal partnership (gemeenschappelijke regeling), from a single system, while each participant keeps its own configuration, data and reporting. Think of a shared service centre for ICT, HR or finance, a tax collection partnership or a regional social services department. The software handles separation per participant (multi-tenant), authorisation per municipality, reporting and cost allocation per participant, and connections to the systems of each participating organisation.

Off-the-shelf packages generally assume a single organisation with a single configuration. In an intermunicipal partnership you serve multiple participants, each with their own way of working, authorisation structure, reporting needs and settlement agreements. That is exactly where standard packages tend to fall short: multiple tenants with differing configurations, cost allocation and integrations per participant. Custom software lets you model that separation and settlement precisely as the partnership has agreed it, without having to bend to the assumptions of a package.

We build the application as multi-tenant: the data, case files and settings of each participant are logically separated, with authorisation per municipality or organisation. An employee only sees and edits what belongs to their own participant, while the partnership itself can still report across all of them. Roles, permissions and data isolation are set up on a least-privilege basis, so the separation is demonstrable and auditable.

Yes. A frequently requested feature is settlement and cost allocation per participant: usage, volumes or effort are tracked per municipality and allocated according to the agreed allocation key. This produces well-founded overviews per participant that align with the partnership's budget and annual accounts. We configure the allocation method exactly as it is set out in the intermunicipal agreement.

A partnership serves participants who each run their own systems. That's why we connect to the standard government interfaces, such as Digikoppeling for secure messaging between government bodies, the ZGW APIs for case-based working and StUF where it is still in use. The integration can differ per participant; we absorb that in the architecture so that every connected municipality stays connected in its own way.

Yes. We develop in line with the GDPR and the Baseline Informatiebeveiliging Overheid (BIO, the Dutch government information security baseline), with data minimisation, role-based access, encryption in transit and at rest, and extensive logging. Because a partnership processes personal data on behalf of multiple participants, we document the data flows and processor roles so that every participant can demonstrably comply with the GDPR. Where citizens use the software, we build to accessibility requirements (WCAG 2.1 AA / DigiToegankelijk).

Yes. Appfront regularly takes over the maintenance of existing applications, including ones built by another party. We review the architecture, the separation between participants, the integrations and the security, document the current setup and draw up improvement proposals. From that point on, we can handle changes, extensions, monitoring and further development, for example when a participant joins or leaves.

We build for a wide range of joint arrangements (gemeenschappelijke regelingen): shared service centres for the IT, HR or finance of multiple municipalities, tax collaborations, regional social services and employment agencies, environmental services, waste collaborations and archive services. The common denominator is always that multiple participants, each with their own setup, are served from a single system, with reporting and cost allocation per participant.

Ready to build software for your partnership?

Tell us which tasks your joint arrangement carries out, which participants are connected and how the setup differs per municipality. We're happy to advise on the multi-tenant setup, reporting and cost allocation per participant, and the right government integrations. A no-obligation initial conversation will quickly give you a clear picture of the possibilities.

Edit content