Custom SIVI AFD integration development
In the insurance chain, policy and booking data is exchanged according to SIVI standards. The foundation is the All Finance Data Catalogue (AFD): the agreements on entities, attributes, formats and code lists. The best-known application is the ADN booking messages, with the renewal message and the amendment message. Appfront builds the integration that processes and generates those messages and AFD data in your own systems, in AFD 1.0 or AFD 2.0, with the right code lists.
What is a SIVI AFD integration?
A SIVI AFD integration ensures that your systems exchange data in the language of the insurance chain. SIVI manages the All Finance Standard for this, and its core is the All Finance Data Catalogue: a source of entities, attributes, formats and code lists that describes how data is exchanged or stored. The AFD covers all branches of financial services except payment and savings accounts; for healthcare, only policy registration. It emerged in the late 1980s from the message traffic of the ADN, the Assurantie Data Netwerk (Insurance Data Network), which began in 1985 to improve the collection process for advisers. SIVI extends the AFD every month, mainly with code values and attributes.
There are two variants. AFD 1.0 works with XML and flat labels. AFD 2.0 has existed since 2020, uses JSON and has around thirty base entities, such as party, object, coverage and document, with a broader domain that also accommodates mortgage and energy contracts. SIVI has opted for a gradual transition, with no fixed date for everyone. In practice, the most widely used are the ADN booking messages: the renewal message, PPR, which comes with the payment terms, and the amendment message, PMB, for new or changed policies. They are EDIFACT messages in AFD 1.0; which data a provider sends per product is recorded in an AFD definition in SIVI's AOS register. Which product cluster a product belongs to is indicated by insurers, managing agents and lenders using the ADN Branch Code, ADNBRA, with main branches and sub-branches.
We build custom because every provider puts slightly different data in its messages, and your own administration has yet another structure. According to SIVI, there are more than 1,500 different ADN booking messages in total. The integration reads in renewal and amendment messages, uses the provider's AFD definition to know which data belongs in them, translates codes such as the branch code into your own structure and puts the policy, premium and term in the right place. In the other direction, it generates messages or AFD 2.0 data for your chain partners. A message that does not match the definition ends up in a work queue with the reason attached.
In the language of the chain
AFD 1.0 and AFD 2.0.
Per provider
According to the AFD definition.
Checked
Deviations in a work queue.
How we build your SIVI AFD integration
We start with your position in the chain: are you an adviser, managing agent, insurer or software supplier, which messages do you receive or send, via which mailbox or service provider, and in which administration the data needs to end up. We then record, per provider, which AFD definition belongs to its messages and how the data maps onto your administration. We first build the processing of renewal messages from one or two providers and have your staff review the result. Amendment messages, more providers and AFD 2.0 follow if that goes well. After that, we maintain the integration with every AFD release.
Role, messages, mailbox.
Per provider and product.
Renewals reviewed.
Go-live, monitoring, and maintenance per AFD release.
What a SIVI AFD integration actually does
The components below appear in almost every SIVI AFD integration. Which ones you need depends on your role in the chain and the messages you exchange.
Renewal
PPR messages processed.
Mutations
PMB for new and amended policies.
Definitions
From the AOS register.
Code lists
ADNBRA and other AFD lists.
AFD 2.0
JSON to your administration system.
Work list
Deviating messages handled separately.
Who we build a SIVI AFD integration for
The integration is intended for organisations that process or send large volumes of policy and booking messages and currently retype data or maintain separate translations for each provider. The more providers and policies you have, the greater the benefit.
Insurance intermediaries
Renewals and amendments imported.
Underwriting authorities
Messages to advisers.
Insurers
Submission according to the AFD.
Software builders
SIVI standards in your software.
Technology and integrations
This page is about exchanging data according to the AFD and the ADN messages. If you want to support the entire renewal process in your administration system, see our page on renewal software for policy administration; for the administration itself, there is policy administration software. We build claim notifications and insurer messages per file with software for claim files, and for the office as a whole there is insurance broker software. You can read about our approach on building custom software.
Why choose Appfront for your SIVI AFD integration?
A renewal that is retyped by hand, a policy that still shows the old cover after an amendment message, or a branch code that each provider translates differently all cost time in the office and lead to questions from customers. We build to prevent that: messages read according to the provider's definition, a fixed translation of code lists and a log where you can see what happened to each message.
According to the standard
AFD and ADN as SIVI describes them.
Less retyping
Messages processed immediately.
Traceable
Every message recorded.
Security and privacy in a SIVI AFD integration
Policy and booking messages contain personal data of policyholders and insured persons, and sometimes special category data, for example in cases of disability. The GDPR therefore applies in full. The integration only processes messages from the providers and relations you request, stores the original message alongside the processing and records every step with time and outcome.
The integration runs in a European data centre, with encrypted connections and storage. Login credentials for mailboxes, service providers and the AOS register are protected and not visible to staff. We agree with you in advance who may view messages, who may approve a deviation and who may send messages.
Frequently asked questions about a SIVI AFD integration
Questions that insurance brokers, authorised agents and software vendors ask before getting started.
The All Finance Data Catalogue: a source of entities, attributes, formats and code lists that describes how data in financial services is exchanged or stored. SIVI manages it as part of the All Finance Standard and expands it monthly.
AFD 1.0 works with XML and plain labels and is the basis of the ADN booking messages. AFD 2.0 has existed since 2020, uses JSON and around thirty basic entities, and covers a broader domain. SIVI is opting for a gradual transition; chain agreements such as the ADN booking messages are being migrated in phases.
Messages that originated from the Assurantie Data Netwerk (Insurance Data Network), which began in 1985. According to SIVI, the ADN booking messages are the only ones still in use: the renewal message, PPR, and the amendment message, PMB. They are exchanged as EDIFACT messages; how they are sent falls outside the ADN Protocol.
The renewal message comes with the payment terms and contains the current booking data and limited policy data. The mutation message is for new or amended policies and can contain more policy data alongside the booking data.
The AFD code list ADNBRA, which insurers, intermediaries with delegated authority and lenders use to indicate which product cluster a product belongs to, with main and sub-branches. The list has more than 140 codes and was revised on 1 August 2024; the old codes appear under the same code in the new list.
An XML schema in which a provider records, per product, which AFD data is included in its messages. Providers publish them in SIVI's AOS register, and software suppliers with an AOS account retrieve them there. This is how the integration knows which data belongs in a message.
For brokerages and intermediaries with delegated authority that process messages from many providers, for providers that generate messages, and for software suppliers that want to support the SIVI standards in their package. If your package already processes the messages well, an integration is mainly worthwhile for whatever the package does not cover.
Renewals and mutations without retyping?
Tell us which messages you receive or send and which system they need to end up in. We will show you how an integration processes them according to the AFD.