Digdir Docs - dokumentasjon av fellesløsninger

ICD 0192

Wed, 22 Apr 2026 12:49:31 +0000

All Peppol addresses in Elma under the ICD 9908 will be deleted from Elma by thursday 14. december 2024.

This step concludes the migration of Norwegian Peppol addresses from ICD 9908 to ICD 0192.

The migration started ~5 years ago when Elma first published information on the migration strategy on behalf of the Norwegian Peppol Authority.

New profiles were made available only under ICD 0192.

ICD 9908 was officially marked as deprecated in v8.3 of the Peppol code lists, released 19. january 2023. Shortly after, in v8.4, it was marked for removal at 24. may 2023.

Any questions may be directed to:

Your Peppol service provider (for end users)
The Norwegian Peppol Authority at peppolmyndighet@dfo.no (for Peppol service providers)

Access Point Provider Manual

Wed, 22 Apr 2026 12:49:31 +0000

Updated: 03.04.2023

Access Points

At the top of the access point page a list of your access points will be displayed. If you have no access points, a “Get Started!” box will be displayed, making it easy to initiate the creation of your first access point.
At the bottom of the page you will see a list of all access points in ELMA.

Add access point

To add an access point, you can press the “Add Access Point”-button. Then you can choose a title for your access point.

After pressing the “Save”-button, you will see access point page.

Please notice the empty Endpoint table. The next task will be to create one or more Endpoints.

Add endpoint

There can be one Endpoint for each Transport Profile. To add an Endpoint, press the “Add Endpoint”-button.

After pressing the “Save”-button, you will see access point again. This time the Endpoint-table will show the newly created Endpoint.

Agreements

Here you will see agreements for usage of your access point by the service providers.

The service providers initiate an agreement. The service provider will not be able to activate the agreement before you as the access point owner has added the public key certificate belonging to the service provider. This should only be done after you have installed the key-pair in your access point.

Adding a public key certificate

Select the agreement you want to add a public key certificate to by clicking the “View”-button. Then you will see the agreement page:

Then you press the “Add Certificate”-button:

Select the correct certificate type and the certificate itself and press the “Save”-button.

Now the agreement is ready for activation by the service provider.

Certificates

This is where you can see all the certificates belonging to one or more agreements. To add, update or delete a certificate, you need to go to select an agreement first.

The certificates should be of a PEM format with a .crt or .cer file type.

Service Providers

Here you will find the different Service Providers in ELMA and their contact information.

Access Point Providers

Here you will find the different Access Point Providers in ELMA and their contact information and access points.

Users

Whenever you make a new user it will be automatically added to the same Access Point Provider you are logged in as.

Add/edit new user

Make sure you fill in all the fields before you click save.

After you have successfully added a new user you can edit this user, add another or view log of the currently added users.

Events

Here you will find all the create, update and delete events related to you as an Access Point Provider.

If you have any questions don’t hesitate to contact us elma@digdir.no

Service Provider Manual

Wed, 22 Apr 2026 12:49:31 +0000

Updated: 03.04.2023

Participants

The participant page shows the participants belonging to the service provider.

Add participant

To add a new participant you can press the “Add participant”-button.

Fill in the required information

If successful the participant detail page will be displayed:

Note that process dependencies are shown. In a special case, when viewing a 0192-participant, profiles which are dependencies that are profiles on the 9908-sibling-participant will also be shown. Those dependencies are not processes on the 0192-participant, but are still shown in ELMA web. They are not visible in a SMP-lookup.

Edit participant

To edit a participant you can press the “Edit participant”-button.

Delete participant

To delete a participant you should be standing in the same window as above. (Endpoints->Your endpoint). From here you can click delete on the selected participant to remove it from your endpoint. If you attempt to delete a participant from the Participants view(pressing the home button) you will get an error. This delete button will be removed in a future release as it’s not meant to be there.

Access Points

Here you will see all the access point that are available.

Applying for an Access Point agreement

If you want to use a specific access point, you need to make an agreement with the access point provider. This can be initiated by pressing the “Apply for agreement”-button on the access point.

Then you will see a the New Agreement screen. You need to specify which domain the agreement is for. Click save when you’re done.

After the agreement is created, you will see something like this:

Notice that the agreement is not active yet. To activate the agreement you need to give the access point provider your certificate, so that they can install it in the access point. Then the access point provider will add the public key to the agreement. As soon as the public key is added, you as the service provider, will be able to activate the agreement.

Given that the access point provider has installed the certificate, then you will see something like this:

You can now activate the agreement so that the participants belonging to the same domain as the agreement will be recipients of the access point. Activate the agreement by pressing the “Activate”-button and get the following popup:

Confirm by pressing the “Yes, activate it!”-button.

Access Point Providers

Here you will see all the Access Point Providers in ELMA

Click on any one of them and get contact information and which access points they provide.

Processes

Here you see the different processes currently in use as well as deprecated ones. By clicking on either one you can see the document types connected to that process. Only the Elma admins and peppol authorities are allowed to add, edit or remove processes. To add a process to a participant you need to go to the edit/add participant menu.

Users

Whenever you make a new user it will be automatically added to the same Service provider you are logged in as.

Add/edit new user

Make sure you fill in all the fields before you click save.

After you have succesfully added a new user you can edit this user, add another or view log of the currently added users.

Events

Here you will find all the create, update and delete events related to you as an Service Provider.

SML Queue

When adding or deleting a participant there will be sent a request to update the SML (Service Metadata Locator) accordingly. The requests will be put on a queue and processed as soon as possible. Typically, within a minute. Below is a screenshot of the SML queue containing one entry that hasn’t yet been processed.

There can be situations where the requests can’t be processed. I.e. due to planned maintenance of the SML Application server or network problems. Is such scenarios the operations will fail, but they will automatically be retried later on. The SML Queue screen shows the active queue. Entries that are successfully executed will get status COMPLETED and will disappear after some time. Sometimes the same request will fail over and over again due to a specific problem. Then it is important to check the error message. You can manually retry the request be pressing the Retry-button or delete the SML request by pressing the Delete-button.

Peppol Directory Queue

When adding or deleting a participant there will be sent a request to update the Peppol Directory accordingly. Peppol Directory requires that a participant is registered in the SML. The requests will be put on a queue and processed as soon as possible. Typically, within a minute. Below is a screenshot of the SML queue containing one entry that hasn’t yet been processed.

There can be situations where the requests can’t be processed. I.e. due to planned maintenance of the Peppol Directory application server or network problems. Is such scenarios the operations will fail, but they will automatically be retried later on. The Peppol Directory Queue screen shows the active queue. Entries that are successfully executed will get status COMPLETED and will disappear after some time. Sometimes the same request will fail over and over again due to a specific problem. Then it is important to check the error message. You can manually retry the request be pressing the Retry-button or delete the SML request by pressing the Delete-button.

If you have any questions don’t hesitate to contact us elma@digdir.no

Elma

Wed, 22 Apr 2026 12:49:31 +0000

Updated: 20.01.2022

Please visit the manual for your current user role in the sidebar menu.

ELMA FAQ

Wed, 22 Apr 2026 12:49:31 +0000

Can I as a Service Provider have more than one Access Point agreement per domain?

No, you’ll then have use two different Service Providers for that domain.

Elma open data

Wed, 22 Apr 2026 12:49:31 +0000

Updated: 19.09.2024

Important note on use

NB! These datasets must not be used to check if a given norwegian organization is registered in PEPPOL or what documents an organization can receive. This should be done via a lookup via the SML (Service Metadata Locator).

See section below on how to do a proper lookup.

Datasets

We have previously published data sets of recipients in Elma at Datahotellet (hotell.difi.no). Datahotellet was discontinued on 11 February 2025. Elma will stop updating the datasets at 23 September 2024.

Read more about the discontinuation of Datahotellet

How to lookup participants in PEPPOL

The only valid way to lookup an organization is the PEPPOL way of lookup via the SML.

Previously, ELMA was the only PEPPOL SMP where norwegian organizations were registered. This is no longer the case. A norwegian organization may be registered to an other SMP. A lookup only in ELMA is no longer a valid way to lookup norwegian organizations in PEPPOL.

It is also possible to lookup organizations via PEPPOL Directory. It is currently not mandatory for SMPs to publish information to PEPPOL Directory, so the list there is not complete.

Recipe for creating the URL to lookup an organization can be found at helger.com
Under the section “Create participant in SMP and SML” at the bullet point “A new DNS entry in the form of …”

See official PEPPOL Documentation on SML and SMP for more details

See the vefa-peppol lookup library for a Java implementation.

ELMA Terminology

Wed, 22 Apr 2026 12:49:31 +0000

Updated: 2023-04-11

Terminology

Here are some terms which will be used throughout the ELMA manuals.

Service provider (SP): A company that connects organizations to the Peppol network. A service provider is associated with one or more domains, and participants registered by the provider will only be approved for message exchange within the provider’s domain(s).
Access point (AP): Represents a physical access point service endpoint, accessible through one or several URLs.
Endpoint: An access point has one or more physical endpoints represented by a URL and transport profile.
Transport profile: The transport method that must be used for communicating with a given AP. AS4 is an example of a transport profile.
Access point provider (APP): An access point provider operates APs that the SPs can use by making an agreement.
Agreement: An agreement between an SP and an APP for usage of a specific access point.
Processes: Standardized, maintained collections of document types used in e-procurement.
Participants: Organizations that are connected to the Peppol network. (An organization might act as its own SP.) You can think of this as a “contract” between an organization and an SP, that connects the SP’s customer organizations to the Peppol network by means of the SP’s associated APP’s AP.
Certificates: Your PEPPOL SP certificate.
Domains: Collections of processes used in e-procurement.
Document types: Standardized message types belonging to processes, used in communication between APs.
Identifier: Identifier for a participant, consisting of a set prefix and an organization identifier. e.g. 9908:991825827
SML (Service Metadata Locator): A DNS that returns the address of the SMP that holds the metadata of a given PEPPOL receiver. The SML is the only centrally operated component in the PEPPOL transport infrastructure. It is managed by OpenPEPPOL and operates out of Brussels by DG/DIGIT.

Om Elma

Wed, 22 Apr 2026 12:49:31 +0000

ELMA - Elektronisk mottakaradresseregister er eit norsk register over foretak som kan ta i mot dokument i EHF-format.

Alle foretak som vil ta i mot EHF-dokument må vere registrert i ELMA. ELMA inneheld informasjon om foretaket si internettadresse (aksesspunktadresse) og kva type dokument mottakaren kan ta i mot, som faktura, ordre, katalogar, tilbod m.fl. Sjølve sendinga skjer via EHF-infrastruktur/CEF eDelivery (PEPPOL) som er ein standardisert måte å sende til dømes fakturaer på til det offentleg sektor.

Les meir om ELMA på Samarbeidsportalen

Mottakarar som er registrert i ELMA må ta imot dokument frå alle avsendarar. Avsendar forpliktar seg til å sende i standardformat og versjonen som er ført opp i ELMA. Det er aksesspunktleverandøren som registrerer mottakarane i ELMA.

English

Elektronisk mottaker- og adresseregister (ELMA) is the SMP provided by Digitaliseringsdirektoratet for the Norwegian market. Using ELMA is free of charge for approved access points in the OpenPEPPOL network.

Approved access points may get access by sending an e-mail to servicedesk@digdir.no. Information on Samarbeidsportalen

Oppslag ved innlogget bruker (brukerstyrt datadeling)

Wed, 22 Apr 2026 12:49:31 +0000

Introduksjon

Kontaktopplysninger fra Kontakt- og Reservasjonsregisteret er oftest utlevert globalt gjennom Oppslagstjenesten. Men kunder kan også motta kontaktopplysninger kun tilhørende innlogget bruker, og det er i noen sammenhenger mer hensiktsmessig og bruke denne tjenesten.

Bruk av Oauth2

Oppslag ved innlogget bruker baserer seg på brukerstyrt datadeling. I tillegg til idporten-scopene openid og profile, må det forespørres ett eller flere av følgende scopes:

scope	beskrivelse
krr:user/kontaktinformasjon.read	Returnerer epostadresse og mobilnummer + tidspunkt for sist oppdatering
	Returnerer status for om kontaktinfomasjonen kan brukast for varsling iht. eForvaltningsforskrifta sin §32
	Returnerer brukerens foretrukne språk for kommunikasjon med det offentlige.
krr:user/digitalpost.read	Returnerer adresse for digital post til innbygger
	Returnerer brukerens krypteringssertifikat ved sending av digital post
krr:user/spraak.write	Endrer brukerens foretrukne språk for kommunikasjon med det offentlige.

API-endepunkt

miljø	url
TEST	https://test.kontaktregisteret.no/rest/v1/person
PROD	https://kontaktregisteret.no/rest/v1/person

Note: Merk den lille forskjellen mellom ‘person’ (dette endepunktet) og ‘personer’ (maskin-til-maskin endepunktet). De to tjenestene har også forskjellige domene-navn.

Følgende header-parametere må brukes på request:

Parameter	Verdi
Http-metode:	GET
Accept:	application/jose (evt. application/json )
Authorization:	Bearer <utstedt access_token>

Eksempel på respons:

Se https://begrep.difi.no/Oppslagstjenesten/Person for definisjon av kodeverket.

      {
         "personidentifikator": "23079421936",
         "reservasjon": "NEI",
         "status": "AKTIV",
		 "varslingsstatus" : "KAN_VARSLES",
         "kontaktinformasjon":
         {
            "epostadresse": "23079421936-test@minid.norge.no",
            "epostadresse_oppdatert" : "2018-06-29T10:14:52+02",
         }
      }

Eksempel på endring av språk:

Forspørselen nedenfor vil endre innlogget bruker sitt foretrukne språk i Kontaktregisteret til engelsk:

PATCH /rest/v1/person
Content-type: application/json
Authorization: Bearer SWDQ_pVct3HIzsIaC3zHDuMmIqffr4ORr508N3p0Mtg=

{
 "spraak" : "en"
}

Det er viktig at kunder som bruker skrive-API informerer brukeren om at endringer skjer i et nasjonalt register, og ikke kun for denne tjenesten.

Swagger

OpenAPI-dokumentasjon.

miljø	url
TEST	https://test.kontaktregisteret.no/swagger-ui/index.html
PROD	https://kontaktregisteret.no/swagger-ui/index.html

Eksempel på kall

Wed, 22 Apr 2026 12:49:31 +0000

Det er bare tre kall du kan gjøre mot oppslagstjenesten;

hente endringer
hente personer
hente printsertifikat.

Først må du sette opp OppslagstjenesteKonfigurasjon med virksomhetssertifikat og Miljø som skal brukes.

Sett opp klientkonfigurasjon

Med sertifikat fra thumbprint:

const string avsendersertifikatThumbprint = "fe14593dd66b2...";

var konfigurasjon = new OppslagstjenesteKonfigurasjon(
    Miljø.FunksjoneltTestmiljøVerifikasjon1,
    avsendersertifikatThumbprint
);

Vi anbefaler å laste sertifikatet fra thumbprint fordi passordet ikke er i koden. Sertifikat kan installeres i Personal for CurrentUser eller LocalMachine. Se hvordan du installerer sertifikatet her.

Med sertifikat fra fil:

const string avsendersertifikatSti = @"C:\Sti\Til\Sertifikat\Sertifikat.pfx";
var sertifikat = new X509Certificate2(
    File.ReadAllBytes(avsendersertifikatSti),
    "Passord",
    X509KeyStorageFlags.Exportable
);

var konfigurasjon = new OppslagstjenesteKonfigurasjon(
    Miljø.FunksjoneltTestmiljøVerifikasjon1,
    sertifikat
);

Hent endringer

string avsendersertifikatThumbprint = null;         //Som initiert tidligere
OppslagstjenesteKonfigurasjon konfigurasjon = null; //Som initiert tidligere

var oppslagstjenesteKlient = new OppslagstjenesteKlient(konfigurasjon);

var personidentifikator = new[] { "08077000292" };
var personer = oppslagstjenesteKlient.HentPersoner(personidentifikator,
    Informasjonsbehov.Kontaktinfo,
    Informasjonsbehov.Sertifikat,
    Informasjonsbehov.SikkerDigitalPost,
    Informasjonsbehov.VarslingsStatus
);

Hent personer

string avsendersertifikatThumbprint = null;         //Som initiert tidligere
OppslagstjenesteKonfigurasjon konfigurasjon = null; //Som initiert tidligere

var oppslagstjenesteKlient = new OppslagstjenesteKlient(konfigurasjon);

var personidentifikator = new[] { "08077000292" };
var personer = oppslagstjenesteKlient.HentPersoner(personidentifikator,
    Informasjonsbehov.Kontaktinfo,
    Informasjonsbehov.Sertifikat,
    Informasjonsbehov.SikkerDigitalPost,
    Informasjonsbehov.VarslingsStatus
    );

Hent printsertifikat

string avsendersertifikatThumbprint = null;         //Som initiert tidligere
OppslagstjenesteKonfigurasjon konfigurasjon = null; //Som initiert tidligere

var oppslagstjenesteKlient = new OppslagstjenesteKlient(konfigurasjon);

var printSertifikat = oppslagstjenesteKlient.HentPrintSertifikat();