Send to real estate broker
- Monica Jacobsen
- Bjørn Hamre
- Ronny Opsahl
- Maja Larsen Breyholtz
Collaboration with broker
Our collaboration service Electronic Property Settlement (Elektronisk Eiendomsoppgjør), enables collaboration between bank and broker. This enables a bank to send the mortgage document to the broker for registration in the Land Registry, as part of a document package, together with the deed, which enables use of digital documents in the process of buying a house(realty). To do so we have implemented the possibility to generate documents for the future owner (buyer) so that, together with the deed, it will both change ownership and establish collateral for the bank, via the broker/real-estate agent.
Figure 7 Collaboration overview
For more information about detailed flows and error cases see scenarios for sending pantedokument to broker.
New, easier flow with Etinglysing version 51.38
From version 51.38 of Etinglysing, the new method sendToRealEstateBroker makes it transparent for the integrator (bank) whether the broker is an Ambita broker or not. Banks can always use flow DOKUMENT_TIL_OPPGJOER when generating the pantedokument and the new method sendToRealEstateBrokerwhen sending it to the broker.
If the signed document is set in Etinglysing, it can be sent to broker with the sendToRealEstateBroker service where only the documentId and broker’s organization number is needed. Any associated prerequisite letter will be sent together with the pantedokument.
<dok:sendToRealEstateBroker>
<documentId>123456</documentId>
<brokerOrganizationNumber>111222333</brokerOrganizationNumber>
</dok:sendToRealEstateBroker>It is also possible to set the signed document (and optionally prerequisite letter) and send it to the broker in one action:
<dok:sendToRealEstateBroker>
<documentId>123456</documentId>
<brokerOrganizationNumber>111222333</brokerOrganizationNumber>
<pantedokumentSdo>"Base64 encoded signed pantedokument"</pantedokumentSdo>
<prerequisiteDocument>"Base54 encoded prerequisite letter"</prerequisiteDocument>
<prerequisiteDocumentMimeType>PDF</prerequisiteDocumentMimeType>
</dok:sendToRealEstateBroker>Input:
Parameter | Required | Description |
|---|---|---|
documentId | true | The unique id returned from the generatePantedokument action |
brokerOrganizationNumber | true | This is the organization number of the broker that the pantedokument should be sent to.. |
pantedokumentSdo | false | The Signed Data Object representation of the pantedokument. Only needed if it is not set previously using setSDO or setSDOList actions. |
prerequisiteDocument | false | The terms from the bank to the broker as PDF or as an XML document according to the standard defined by DSVE If the |
prerequisiteDocumentMimeType | false | Format of prerequisite document. Must be set if prerequisiteDocument is present. Supported types are “XML” and “PDF”. |
This service requires the documentID from the generatePantedokument call and the broker’s organization number. When called www.etinglysing.no will push the signed document to the relevant EPS settlement, if found (for Ambita’s brokers). If no settlement process is found when sendToRealEstateBroker is called, the pantedokument (and prerequisite letter, if any) will be sent to the broker using the Afpant channel (Non-Ambita brokers).
Note that there is no need to generate a foelgebrev for a document that is to be sent to the broker, as this will be done by the broker.
If a prerequisite document is generated beforehand using generatePrerequisite method, it will be sent to the broker along with the pantedokument, no need to include it when calling sendToRealEstateBroker. Include prerequisite document in sendToRealEstateBrokeronly if:
You want to override the previously generated one.
You want to send a custom prerequisite letter.
If the document status is “SAMHANDLING_FEILET”, the document can be resent
See here for more info about document flow and statuses
The pantedokument will get the status “SAMHANDLING_FEILET” if:
Cant find any matching settlement for the given property
There is a buyers mismatch to the settlement for given property
The pantedokument is rejected by the broker
To find out why the pantedokument has the status “SAMHANDLING_FEILET” you can get an explanation by:
Get the status for the document. How to get status.
Then in documentMessages the errorCode will be “9999” and in detail you will find the reason for failure.
Example of a get status response xml where the pantedokument has mismatch in buyer:<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <ns2:getStatusResponse xmlns:ns2="http://dokument.ws7.etinglysing.no/"> <return> <status> <created>2020-12-17T15:00:00.306+01:00</created> <documentStatusTinglysing/> <id>15759414</id> <statusCode>SAMHANDLING_FEILET</statusCode> <description>Pant - 4601/121/45// [G]</description> <reference>Mona 167</reference> </status> <type>PANTEDOKUMENT</type> <documentVersion>KARTVERKET</documentVersion> <documentMessages> <documentMessage> <detail>Kjøper mangler: Fant ikke oppgjør for angitt kjøper</detail> <errorGroup>EKSTERNFEIL</errorGroup> <message>Samhandling feilet</message> <errorCode>9999</errorCode> </documentMessage> </documentMessages> </return> </ns2:getStatusResponse> </soap:Body> </soap:Envelope>or if you are monitoring events. How to monitor events.
Read the events of type “STATUSOVERGANG” for the document where ny_status is “SAMHANDLING_FEILET” and you will find out the reason for failure in beskrivelse.
Example of listHendelser response xml for event type “STATUSOVERGANG”. This is an event for dokument with id 15759414 where ny_status is “SAMHANDLING_FEILET”: