Integrations
The Integrations screen manages the connections that link Scrivio to external systems: Certificates for the digital certificates Scrivio uses to set up secure connections on your practice's behalf (UZI, Zorgmail), Zivver for the SMTP credentials used to send letters securely through Zivver, and the ZorgMail, VECOZO COV, ZorgDomein and SnelStart tabs for the connections a practice switches on for itself. The screen is intended for the organization administrator.
What each connection can and cannot do today — outbound and inbound separately — is in Connection status.
This screen replaces the outdated "Integrations" page from the old admin guide.
Overview
| Route | /organization/integrations (open a specific tab with ?tab=certificates, ?tab=zivver, ?tab=zorgmail, ?tab=vecozo-cov, ?tab=zorgdomein or ?tab=snelstart) |
| Audience | Organization administrator |
| Required permission | integrations.manage |
The screen opens on the Certificates tab by default. The ZorgDomein tab only appears for users allowed to view the ZorgDomein activation — it shows a verification code for a live clinical intake channel, so it carries a permission of its own on top of integrations.manage. The Zivver and ZorgMail integrations are only available with a FULL license.
Connection status
A connection has two directions, and they rarely land together: sending can already work while receiving does not exist yet. So for each connection, what outbound and inbound do today, what it is waiting on and what you have to arrange yourself are stated separately. If a direction is not listed as available here, it is not available — not even partly.
Status as of 9 September 2026.
ZorgMail — letters to the general practitioner
| Outbound | Built, not in use yet. A letter from Scrivio goes to the general practitioner as a structured message (MEDVRI) and lands directly in their system, with the treating practitioner as the sender. |
| Inbound | Not available. Scrivio does not retrieve ZorgMail messages. That includes status messages: a message ZorgMail accepts and later fails to deliver does not come back to you in Scrivio. Scrivio therefore reports a letter as submitted, never as delivered. |
| Waiting on | The central ZorgMail (ASP) account Scrivio uses to send on behalf of practices. Until that exists the channel is switched off — for every practice at once. |
| What it replaces | Not Zivver. ZorgMail reaches care providers inside the ZorgMail community, the general practitioner first of all; mail to clients goes through the client portal or Zivver. Whether Scrivio will also send client mail over ZorgMail has not been decided. |
| What you arrange | A ZorgMail subscription with Enovation, Enovation's permission for Scrivio to send on your practice's behalf, and the practice's ZorgMail Account ID on the ZorgMail tab. Sending also requires a FULL license. |
ZorgDomein — receiving referrals
Updated 2 October 2026.
| Inbound | Being built, not in use yet. A referral arrives digitally with client details, insurer, referrer with AGB code, referral date and attachments, so nobody retypes them. The connection is now being tested against ZorgDomein's test environment, with test referrals and no real client data. |
| Outbound | Not part of this connection. Reporting back to the referrer goes over ZorgMail, not over ZorgDomein. |
| Waiting on | Four things: a PKIoverheid server certificate for the receiving address, issued by a certificate authority and taking weeks of calendar time; ZorgDomein's own technical validation, on their test environment; the referral inbox — the screen where you review an incoming referral; and Scrivio's NEN 7510 certification, which ZorgDomein ask for before the pilot with real referrals may start. We expect that certification in December 2026. While these are open we name no date. |
| Always a human | An incoming referral is staged, not processed. Someone at the practice reviews it and then turns it into a client and a care trajectory through the ordinary route. If you screen every referral yourself before accepting it, you keep doing exactly that. |
| What it replaces | Nothing. You keep your own ZorgDomein subscription; the connection delivers the referral into Scrivio instead of into a mailbox. |
| What you arrange | A ZorgDomein subscription, your practice's AGB code under Practice details (ZorgDomein finds your practice by that code; without an AGB code activation cannot succeed), and activation with the verification code on the ZorgDomein tab. |
Zivver — secure email to clients
| Outbound | Available. Letters from Scrivio are sent securely through Zivver to clients and other recipients. |
| Inbound | Not available and not planned. Replies arrive in your own Zivver mailbox, not in Scrivio. |
| What it replaces | Nothing. Scrivio sends through your own Zivver account, so that subscription stays necessary. |
| What you arrange | A FULL license, a Zivver account with SMTP credentials (the Zivver tab), and a sender address verified by Zivver for each user. |
SnelStart — sales invoices in the bookkeeping
Updated 5 October 2026.
| Outbound | Built. With SnelStart connected, Naar boekhouding under Declaraties › Batches books each insurer invoice in a batch as a sales booking (verkoopboeking) in your SnelStart administration: on the insurer's relatie, on the general ledger account (grootboekrekening) you choose, VAT-exempt, and under Scrivio's invoice number. An invoice already in SnelStart is not booked again. For each batch and each invoice you can see whether it was booked, and if not, why. Private invoices and restitution notes are not part of it yet. |
| Inbound | Not available. Scrivio reads nothing back from SnelStart, including whether an invoice was paid. |
| Waiting on | Besides your connection key, SnelStart needs a key from Scrivio itself. While that is missing, the SnelStart tab says so and nothing is booked. |
| Already mailed? | A batch already sent to the bookkeeping by email is skipped, because otherwise it would be in there twice. It is booked only if you tick Toch boeken in SnelStart in the confirmation. |
| What it replaces | The mail route, for a practice that has connected SnelStart (see below). |
| What you arrange | A FULL license and a SnelStart subscription. No connection is possible during a SnelStart trial period. On the SnelStart tab you connect with Koppelen met SnelStart, or you paste a connection key you create in SnelStart under Koppelingen → Maatwerk. Such a maatwerk key requires inZicht or inControle. Then you pick a relatie for each insurer or insurer concern, which must be a customer (klant) in SnelStart, and choose the general ledger account from your own administration's accounts. If 8005 is there, it is preselected. You still have to save the choice. |
| Backup restored | Restoring a backup in SnelStart invalidates the connection key. Reconnect on the SnelStart tab afterwards. |
Without SnelStart: the mail route. If you have not connected SnelStart, Naar boekhouding sends each insurer invoice as a PDF in its own email to the address you enter in the billing settings on the Contracts page, for example the intake mailbox of your bookkeeping package. The package then has to recognise and book the invoice itself. That does not always go well, which is why the SnelStart connection was built. The emails come from noreply@scrivio.nl. Make sure your intake mailbox accepts mail from that address, or nothing arrives.
For readers with repository access, the reasoning is in ADR-040 (the ZorgDomein receiving connection) and ADR-041 (ZorgMail as a second sending channel).
How it works
This screen doesn't manage Scrivio data, but the trust relationship with external systems: the certificates that prove your organization's identity and the channel through which Scrivio sends secure letters. A wrong or expired certificate doesn't break this screen, but rather the processes that rely on it (such as looking up client details in the BSN register). That's why it helps to understand what each connection is for.
Certificates: who you authenticate to, and for what
A certificate is a digital proof of identity Scrivio uses to authenticate to an external party on behalf of your organization. Each type authenticates for its own chain:
| Type | Authenticates to | Used for |
|---|---|---|
| UZI server certificate | SBV-Z and other healthcare integrations | Proving a valid care-provider identity on secure connections in the healthcare infrastructure. |
| Zorgmail | Zorgmail | Secure messaging in healthcare. |
VECOZO is not on this list: it needs no certificate from the practice. VECOZO works with an authorisation (machtiging, toestemmingsverklaring): in the VECOZO portal you give Scrivio permission to declare on behalf of the practice's AGB code, and Scrivio uses its own system certificate for that. What is needed is described in The VECOZO connection.
The certificate itself is a PKCS#12 file (.p12/.pfx) that holds both the key and its protection; when uploading you supply the passphrase the file is protected with. Scrivio uses this file to establish the connection on your behalf; Test connection checks whether that chain actually works.
Expiry lifecycle and the downstream break
Each certificate has an expiry date and moves through three statuses. The status isn't a cosmetic label — it predicts whether the chains above keep working:
| Status | Meaning | Effect |
|---|---|---|
| Valid | The certificate is usable. | The connections that rely on the certificate work normally. |
| Expiring soon | The expiry date is approaching. | Still usable, but this is your cue to Replace it in time — before it expires. |
| Expired | The expiry date has passed. | The dependent processes (e.g. looking up client details in the BSN register with a UZI server certificate) fail until a valid certificate is uploaded. |
Because an expired certificate halts dependent processes without anything appearing "broken" on this screen, Expiring soon is meant as a generous warning margin: replace the certificate during that window instead of waiting for errors to surface, say, when looking up client details.
Zivver as a sending channel
The Zivver tab is not a certificate but an SMTP channel: the username and password of your Zivver account that Scrivio uses to send letters securely. This configuration is the only channel for Zivver delivery — if you delete the configuration, letters can no longer be sent through Zivver. So only delete the configuration if you deliberately want to switch this channel off.
License and secret handling
The Zivver integration is subject to FULL-license gating: without that license the tab is visible but the form is unavailable. The Certificates tab is independent of this gating.
Secrets are handled write-only. The certificate passphrase and the Zivver password are stored securely and then never shown again: the form clears them after saving or deleting. When making a change you therefore always re-enter the password — Scrivio cannot pre-fill the existing secret for you.
Open the Certificates tab
Click the Certificates tab (or open the screen via /organization/integrations?tab=certificates). You see a list of your organization's uploaded certificates, each row showing the type, status, expiry date, and when and by whom the certificate was uploaded.
The status indicates whether a certificate is still usable:
| Status | Meaning |
|---|---|
| Valid | The certificate is valid and usable. |
| Expiring soon | The certificate expires shortly; replace it in time. |
| Expired | The certificate has expired and must be replaced. |
Open the Zivver tab
Click the Zivver tab (or open the screen via /organization/integrations?tab=zivver). Here you configure the SMTP credentials of your Zivver account that Scrivio uses to send letters securely.
Zivver is only available with a FULL license. Without it the tab shows a notice and the form is unavailable. Contact us to upgrade your subscription.
Configure a certificate
On the Certificates tab, click + New in the top right to upload a certificate. A dialog opens where you choose the type, select the certificate file, and enter the passphrase.
| Field | Required | Description |
|---|---|---|
| Certificate type | Yes | UZI server certificate or Zorgmail. When replacing an existing certificate the type is fixed. |
| Certificate file | Yes | A PKCS#12 file with the extension .p12 or .pfx. Drag the file onto the upload zone or click to browse. |
| Passphrase | Yes | The passphrase the certificate file is protected with. |
The personal VECOZO certificate you sign in to the VECOZO portal with does not belong here: you install that on your own computer, within 20 days of requesting it. See The personal certificate, and the 20 days.
Click Upload to save the certificate. After uploading you manage the certificate with the actions in the list:
- Test connection — checks whether the certificate establishes a working connection.
- Replace — opens the same upload dialog to refresh the certificate file (the type stays fixed).
- Delete — removes the certificate after confirmation. This cannot be undone.
Configure Zivver
On the Zivver tab, enter the SMTP credentials of your Zivver account. The host and port are pre-filled with the Zivver defaults.
| Field | Required | Description |
|---|---|---|
| SMTP host | No | The Zivver SMTP host. Defaults to smtp.zivver.com. |
| Port | No | The SMTP port. Defaults to 587. |
| Username | Yes | The Zivver-issued username (a UUID). |
| Password | Yes | The Zivver-issued password. It is stored securely and never shown; re-enter it to save the configuration. |
Click Save to store the configuration. Two further actions then become available:
- Test connection — checks whether Scrivio can establish a connection to Zivver with the entered credentials.
- Delete — removes the Zivver configuration after confirmation. Letters can no longer be sent through Zivver afterwards.
For security, the password is cleared from the form after saving or deleting and is never visible.