# Underskriftmappe

Tinglysningsretten
1.0.0

← Back to Main Page

## Overview

The signature folder service group consolidates all services related to the signing of notifications. Technically, the signature folder is located together with the administrative web services.

Business Overview

The signature folder is used to collect the necessary digital signatures required for a notification before it can be submitted for registration.

The submitter is responsible for the notification and its content, but it does not have to be the submitter who drafts the notification. Thus, one party may prepare a notification which another party will submit. If a notification is placed in the signature folder, and the drafter is not the submitter, the drafter will not be able to access the notification in the signature folder.

When the notification is placed in the signature folder, it must be fully completed. This includes submitter information and the fee section. The submitter may at any time withdraw the document and amend the information. The following operations will trigger a notification to the submitter:

- After receipt of a new document in the signature folder

- Receipt of a signature

- After a call to the HentOgSlet operation

The notification includes all data and is identical except for a status code indicating the operation. It is possible to specify an email address for notifications, for example, in cases where the submitter is not enrolled in the system-to-system scheme.

Authorized Signatories

In cases where one or more roles in the notification are companies, it is possible to specify how many signatures must be collected in the signature folder.

For each CVR number, it is possible to specify one or more authorized signatories. An authorized signatory may be unknown; in such cases, anyone with an employee certificate may sign on behalf of the company. Alternatively, a specific CPR number may be specified for the employee who will sign. In this case, the individual can sign with both their personal certificate and the employee certificate.

During review, e-TL checks whether the signing rules have been followed by consulting the CVR and the signature database. The specification of authorized signatories is only relevant in connection with the signature folder. The review of signing rules is based on CPR numbers and names (retrieved from the CPR register). Therefore, it is required that special employee certificates be used for registration, which can be traced back to a CPR number via a call to the CA (TDC).

Signing within the Signature Folder

Signing takes place exclusively within the signature folder. All parties who must sign parts of a notification log into tinglysning.dk and select the notification they wish to sign. DokumentUnderskriv is exclusively an internal e-TL service used by tinglysning.dk in connection with these signatures.

There is, however, the following exception to signing in the signature folder:

- The submitter may use the system-to-system interface and sign the notification document for all roles that can be covered by the submitter scheme within their own system. This is permissible because the submitter assumes full responsibility for the signed document.

All others must sign in the signature folder via tinglysning.dk. This is required because DSS is subsequently liable for compensation. Tinglysning.dk ensures via a secure signer that what is seen at the moment of signing is also what is registered (WYSIWYS).

Time Limitation

Documents remain in the signature folder for a limited period. If all signatures are not collected within this period, the notification is deleted and the drafter is notified via NotifikationModtag. The drafter must implement the e-TL.Udfaerdiger.Underskriftmappe web service that includes NotifikationModtag.

It is possible for the drafter to specify the validity period that should apply to the notification when it is placed in the signature folder. If set, the retention period defined in the system applies. The submitter receives a notification via NotifikationModtag about the impending expiration of a notification in the signature folder.

Revocation of Signatures

For each document in the signature folder, it is possible to specify whether the revocation of signatures should be permitted.

If revocation is enabled, the submitter will receive a notification if someone revokes their signature. The signature is removed from the document, which remains in the signature folder.

Registration

From the tinglysning.dk portal, it is possible to register from the signature folder. This is implemented by the portal retrieving and deleting the document, and then registering it.

System-to-system submitters are responsible for invoking HentOgSlet before a notification is registered, ensuring it is not present in the signature folder after registration.

Signing

Signing takes place exclusively within the signature folder. All parties who must sign parts of a notification log into tinglysning.dk and select the notification they wish to sign. DokumentUnderskriv is exclusively an internal e-TL service used by tinglysning.dk in connection with these signatures.

There are, however, the following exceptions to signing in the signature folder:

- An authorized submitter may choose to sign the required elements of the notification in their own system in accordance with the submitter scheme.

- An approved submitter may use the system-to-system interface and sign the entire notification document as the submitter.

- When signing in one’s own system, XML-based signatures are used and always on the entire notification. This means that all XML elements in the XML Body except Signature must be signed.

### Endpoints

#### DokumentIndsaet

Endpoint URL: `Underskriftsmappe/DokumentIndsaet`

Description | Inserts a notification document into the signature folder. A synchronous response is returned with a SignatureFolderIdentifier, which can subsequently be used to reference the document. An asynchronous notification is sent to the specified submitter. If an email address is provided, an email is also sent.
Input | DokumentIndsaet.xsd
Output | DokumentIndsaetSvar.xsd
Error Handling |
Interaction Pattern | Request-response

Example request:

    POST /s2s/Underskriftsmappe/DokumentIndsaet HTTP/1.1
    Content-Type: application/xml
    Tinglysning-Message-ID: uuid:be5e1639-2edc-4280-b365-08e551ab94dd
    Tinglysning-Relates-To: s2s-http-xml-api-end2end-test
    Content-Length: 7544

    <?xml version="1.0" encoding="UTF-8"?><DokumentIndsaet xmlns="http://rep.oio.dk/tinglysning.dk/service/message/administration/1/" xmlns:ns="http://rep.oio.dk/tinglysning.dk/service/message/tingbog/1/" xmlns:ns1="http://rep.oio.dk/tinglysning.dk/schema/anmeldelse/1/" xmlns:ns2="http://rep.oio.dk/tinglysning.dk/schema/model/1/" xmlns:ns3="http://rep.oio.dk/cvr.dk/xml/schemas/2005/03/22/" xmlns:ns4="http://rep.oio.dk/tinglysning.dk/schema/administration/1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://rep.oio.dk/tinglysning.dk/service/message/administration/1/ http://rep.oio.dk/tinglysning.dk/service/message/administration/1/DokumentIndsaet.xsd">
        <SignaturKanSlettesIndikator>false</SignaturKanSlettesIndikator>
        <ns:AnmeldelseTingbog>
            <ns:AfgiftPantebrevPaategn>
                <ns1:AnmeldelseInformation>
                    <ns1:Procesinstruktion>
                        <ns2:BrugerformularIdentifikator>c7366fbc-5982-4e70-ab56-15dae540eebb</ns2:BrugerformularIdentifikator>
                        <ns1:ProeveTinglysningIndikator>true</ns1:ProeveTinglysningIndikator>
                    </ns1:Procesinstruktion>
                    <ns2:ForespoergselsIdentifikatorSamling>
                        <ns2:ForespoergselsIdentifikator>
                            <ns2:Id>cc0852e9-9897-4031-a858-884b60a2f6a3</ns2:Id>
                        </ns2:ForespoergselsIdentifikator>
                    </ns2:ForespoergselsIdentifikatorSamling>
                    <ns1:AnmelderInformation id="test">
                        <ns3:CVRnumberIdentifier>21659509</ns3:CVRnumberIdentifier>
                    </ns1:AnmelderInformation>
                    <ns2:RolleSamling>
                        <ns2:Rolle id="ID_03">
                            <ns2:RolleTypeIdentifikator>kreditor</ns2:RolleTypeIdentifikator>
                            <ns3:CVRnumberIdentifier>21659509</ns3:CVRnumberIdentifier>
                        </ns2:Rolle>
                    </ns2:RolleSamling>
                    <ns2:ErklaeringSamling>
                        <ns2:Erklaering>
                            <ns2:ErklaeringKode>A19</ns2:ErklaeringKode>
                        </ns2:Erklaering>
                    </ns2:ErklaeringSamling>
                    <ns2:AnmelderOrdningSamling>
                        <ns2:AnmelderOrdning id="ID_5bce6036-48bb-4162-8c9a-257073d4997b">
                            <ns3:CVRnumberIdentifier>21659509</ns3:CVRnumberIdentifier>
                            <ns2:RolleReference>ID_03</ns2:RolleReference>
                            <ns2:Erklaering>
                                <ns2:ErklaeringKode>A19</ns2:ErklaeringKode>
                            </ns2:Erklaering>
                        </ns2:AnmelderOrdning>
                    </ns2:AnmelderOrdningSamling>
                    <ns2:FuldmagtOrdningSamling>
                        <ns2:FuldmagtOrdning id="FO_1">
                            <ns2:FuldmagtHaver id="FH_1">
                                <ns3:CVRnumberIdentifier>21659509</ns3:CVRnumberIdentifier>
                            </ns2:FuldmagtHaver>
                            <ns2:FuldmagtOmfangIdentifikator>1</ns2:FuldmagtOmfangIdentifikator>
                        </ns2:FuldmagtOrdning>
                    </ns2:FuldmagtOrdningSamling>
                    <ns2:TinglysningAfgift>
                        <ns2:StorkundeIdentifikator id="stor_kunde_id">
                            <ns3:CVRnumberIdentifier>21659509</ns3:CVRnumberIdentifier>
                        </ns2:StorkundeIdentifikator>
                        <ns2:Afgiftsbeloeb>1750</ns2:Afgiftsbeloeb>
                    </ns2:TinglysningAfgift>
                </ns1:AnmeldelseInformation>
                <ns2:DokumentRevisionIdentifikator>
                    <ns2:DokumentIdentifikator>5d3e2a92-7d3e-4f6b-8105-1b40a6f6dc9a</ns2:DokumentIdentifikator>
                </ns2:DokumentRevisionIdentifikator>
                <ns2:AktoerReference>
                    <ns2:AktoerID>aktoerid123</ns2:AktoerID>
                    <ns2:KorrelationID>aktoerkorrid123</ns2:KorrelationID>
                </ns2:AktoerReference>
                <ns:EkspeditionstypeIdentifikator>244</ns:EkspeditionstypeIdentifikator>
            </ns:AfgiftPantebrevPaategn>
        </ns:AnmeldelseTingbog>
        <ns1:TegningsberettigedeSamling/>
        <ns4:KvitteringIndikator>false</ns4:KvitteringIndikator>
        <Signature xmlns="http://www.w3.org/2000/09/xmldsig#" Id="Signature-4f790f41-c5db-4526-bbd8-5d2e6ed89c05"><SignedInfo><CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/><SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha512"/><Reference URI=""><Transforms><Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/><Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/></Transforms><DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/><DigestValue>J8UiXzO5GDPM7Vs6OOKfsZxbi6iM2WwjkZ51Oc52C60=</DigestValue></Reference></SignedInfo><SignatureValue>HtKKw4V9YsKNnmK8LK8F7Ay6F02KgsxyMSwIKnlIrgbu54uC0ZtOqS5AMC2lyR5wlndoENiR+kLW&#13;
            Wv27gY2H0sRFvyFuuL3wbcw10pUIaulS5UHtS3sLRzKrnAr/Fmci+iW/XQ5bD7Sys6rUvJGQ2DT/&#13;
            hF4YxLak3zIjHQ7FUgI4wMDmSUHgWvrv8OSCnCcSTj6cDESDQoHwGAIqjyNMd8xxPEdXBrL05iZp&#13;
            sIB7NdP5MVpparTW4rOEpagLGiiqQb7cnT6p3FREx/Yfh4FaesszzDtM8zKI/MoeaECAPyU+8SmC&#13;
            Ff9brt8wowE+MU/wV0nR2H9eU5fM5p7arHjH2JrfEEur6Zgi2ZaeIx5iC+Zq2Fxk/td1gHCSYPsw&#13;
            BMt8dm8Q++MxIGtFNRUaHf8Y4OX1Oj4L3mFlyWx9LU3yKsKaEmOCP/F8SyMj/KeqLA/Ml++rmJlR&#13;
            90VkykFtmJR4XjCCxmrVvpRRzL6hEmheCqIcXPOugQFrxyneItNY/8us</SignatureValue><KeyInfo><X509Data><X509Certificate>MIIGrDCCBOCgAwIBAgIUNDToBwFCKjTnfoTggwRZQ7NT70wwQQYJKoZIhvcNAQEKMDSgDzANBglg&#13;
            hkgBZQMEAgEFAKEcMBoGCSqGSIb3DQEBCDANBglghkgBZQMEAgEFAKIDAgEgMGsxLTArBgNVBAMM&#13;
            JERlbiBEYW5za2UgU3RhdCBPQ0VTIHVkc3RlZGVuZGUtQ0EgMTETMBEGA1UECwwKVGVzdCAtIGN0&#13;
            aTEYMBYGA1UECgwPRGVuIERhbnNrZSBTdGF0MQswCQYDVQQGEwJESzAeFw0yMzAzMDgxMzEzMDNa&#13;
            Fw0yNjAzMDcxMzEzMDJaMIGiMSUwIwYDVQQDDBxUTFIgZVRMIFRFU1QgLSBYTUwtc2lnbmVyaW5n&#13;
            MTcwNQYDVQQFEy5VSTpESy1POkc6ODg3YTFlNjktNGU4NC00NmI1LWI2NTQtMzgxYzcxYmU4NTU5&#13;
            MRowGAYDVQQKDBFEb21zdG9sc3N0eXJlbHNlbjEXMBUGA1UEYQwOTlRSREstMjE2NTk1MDkxCzAJ&#13;
            BgNVBAYTAkRLMIIBojANBgkqhkiG9w0BAQEFAAOCAY8AMIIBigKCAYEAvfks1Cq2hW2c7fmx2rUW&#13;
            oPgHdSNphG7GWO7GrRkVQSCB3GBzdf7qck56obK0XLui8yD00FDHJgyFCSLIOpesAi9fjQnc+Wl1&#13;
            HUx1WfzPzvGbQvGPB9oWtP1lhY9gNxb3ZObzrW3DfOGbKbbNCw6yaaac5ssi/T447Eg/psHnAACG&#13;
            cGCU9OxsBoTgx5Zq+4k1u+I3mpvGeczetzY6fpQyKzpc1NJNhe6UeKZFxYocWDrIvdoMsOlosI9Q&#13;
            +491FnmKj3heCSMGu8o59uhYw2CpwVDreXYK+tfRj1tZWGhj++uYHmA+SgV9qnw+1DvESZZdPPvX&#13;
            IFuHFJZ2SCO2ZOarvX2IrsjHfyLq1zi80fXS1SHeuIZOJwMclQ6uVrn5VYAzCRr/LPEEOptKsLRK&#13;
            m2q81vHcC2eEXq1IaTIhp4tFJyBsSp/JX0bvM23c4AaLnG1WeT1hAWB8oPUKP/Ai3cesn9VOLcv4&#13;
            Fm72jggT/YuS1dpEL6mgGqID3RVEW1t/0DHNAgMBAAGjggGmMIIBojAMBgNVHRMBAf8EAjAAMB8G&#13;
            A1UdIwQYMBaAFH8on9lxmULidefXNXYuTQglbXZeMHsGCCsGAQUFBwEBBG8wbTBDBggrBgEFBQcw&#13;
            AoY3aHR0cDovL2NhMS5jdGktZ292LmRrL29jZXMvaXNzdWluZy8xL2NhY2VydC9pc3N1aW5nLmNl&#13;
            cjAmBggrBgEFBQcwAYYaaHR0cDovL2NhMS5jdGktZ292LmRrL29jc3AwHgYDVR0RBBcwFYETZS10&#13;
            bC0wMTFAZG9tc3RvbC5kazAhBgNVHSAEGjAYMAgGBgQAj3oBATAMBgoqgVCBKQEBAQMHMDsGCCsG&#13;
            AQUFBwEDBC8wLTArBggrBgEFBQcLAjAfBgcEAIvsSQECMBSGEmh0dHBzOi8vdWlkLmdvdi5kazBF&#13;
            BgNVHR8EPjA8MDqgOKA2hjRodHRwOi8vY2ExLmN0aS1nb3YuZGsvb2Nlcy9pc3N1aW5nLzEvY3Js&#13;
            L2lzc3VpbmcuY3JsMB0GA1UdDgQWBBSVkuXJb5Td054/T6F0sIbTJm7MkjAOBgNVHQ8BAf8EBAMC&#13;
            BeAwQQYJKoZIhvcNAQEKMDSgDzANBglghkgBZQMEAgEFAKEcMBoGCSqGSIb3DQEBCDANBglghkgB&#13;
            ZQMEAgEFAKIDAgEgA4IBgQAJKLA11RSpBE+UO2iLl06PlMPOARixoU/3HPqGBPY0YRZvJ0iCUhMx&#13;
            vw/D/vlrk7wh37vkNLLrakau3d9Dcgkh2UUT9JBGy3JzFXQzOjrvaRfWCkY0jIZz945IgqEPjLXo&#13;
            7x+4e9FybtchHLdzkeg+O/n2uYezp8vkAUQJkJOWVQRZngKCADBdhfnqY/PYEO8S38QBMiS0ZWfC&#13;
            Ip+lrFCuKwOVgHZG16+KcSC6shbYYOurvsii6MAE0mFyCnpVmN4wtlbXaxsEreyQ2b2yTTocw24w&#13;
            Po0QBSPVH+wSfE7lQNHxJVEuFBcYUHhtWjhhYWnINmoBVWclZBAYE18m35vm/zrOyLzuYv79vTY/&#13;
            x1J/hPbsgos9D38Dj6Oc7m9BBuQhfS5bKU2ZsUINQgnypMveltm/6Qxc5cDTlrQp6c7/kxBcJTH3&#13;
            5qC4jIvaIB8v5npfpHCqaVPRj1LX6dFMB1dujqv9ME8yUVOTUHT8RPO/kgsxOdzhvBYRGmCU/7co&#13;
            vZk=</X509Certificate></X509Data></KeyInfo></Signature></DokumentIndsaet>

Example response:

    HTTP/1.1 200 OK

    <ns:DokumentIndsaetSvar xmlns:ns="http://rep.oio.dk/tinglysning.dk/service/message/administration/1/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsigModel="http://rep.oio.dk/tinglysning.dk/schema/model/1/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://rep.oio.dk/tinglysning.dk/service/message/administration/1/ http://rep.oio.dk/tinglysning.dk/service/message/administration/1/DokumentIndsaetSvar.xsd"><ns1:UnderskriftsmappeIdentifikator xmlns:ns1="http://rep.oio.dk/tinglysning.dk/schema/anmeldelse/1/">535ad970-a3d7-47d0-b110-f4a464d5d3bf</ns1:UnderskriftsmappeIdentifikator><Signature xmlns="http://www.w3.org/2000/09/xmldsig#" Id="ID26345709008001-ReplySignature"><SignedInfo Id="ID26345709008002-ReplySignatureInfo"><CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/><SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/><Reference URI=""><Transforms><Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/><Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/></Transforms><DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/><DigestValue>y9DgEC3LmlLwE4FsXLF3KSG+A8Y=</DigestValue></Reference><Reference Type="http://www.w3.org/2000/09/xmldsig#SignatureProperties" URI="#ID26345709008004-ReplySignatureProperty"><Transforms><Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/></Transforms><DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/><DigestValue>PPmGLol1vVxdBXuD5iTKMzlO9vo=</DigestValue></Reference></SignedInfo><SignatureValue> </SignatureValue><KeyInfo><X509Data><X509Certificate> </X509Certificate></X509Data></KeyInfo><Object Id="ID26345709008003-ReplySignatureObject"><SignatureProperties><SignatureProperty Id="ID26345709008004-ReplySignatureProperty" Target="#ID26345709008001-ReplySignature"><dsigModel:UnderskriftTidspunkt>2025-10-31T15:32:05</dsigModel:UnderskriftTidspunkt></SignatureProperty></SignatureProperties></Object></Signature></ns:DokumentIndsaetSvar>

#### DokumentHentOgSlet

Endpoint URL: `Underskriftsmappe/DokumentHentOgSlet`

Description | Retrieves and deletes a document from the signature folder. The response is provided as a notification.
Input | DokumentHentOgSlet.xsd
Output | DokumentHentOgSletSvar.xsd
Error Handling |
Interaction Pattern | Request-response This service operation is request-response, but is also a workflow, as subsequent notification events occur regarding the document.