Generate forutsetningsbrev
Forutsetningsbrev
Available in Etinglysing 51.69.0 (end of May 2024).
History
Etinglysing has for a long time had the webservice generatePrerequisite that generate a prerequisite letter to the broker. This first version (generatePrerequisite) had several free text input field for the bank’s conditions/requirements. Since then, DSVE has defined a second version of this letter that has a set of standardized texts requirements so that it will be easier for the broker to understand and interpret. This new webservice, generateForutsetningsbrev, will generate a document to the broker according to the news specification. The term Forutsetningsbrev has been agreed upon, som the new webservice is named using this common name instead of prerequisite V2.
About the Forutsetningsbrev
Forutsetningsbrev (en: prerequisite letter) is a document sent from the bank to the real estate broker with terms and conditions for the mortgage document (pantedokument). It is the broker’s responsibility to make sure that the conditions can be met before sending it to registration (tinglysing). It can specify:
The bank's required priority for the Pantedokument.
Payment details.
The broker’s name and organization number.
Bank’s contact information.
Work flow
When generateForutsetningsbrev
is invoked, the document ID from the generatePantedokument
call is required, hence the Pantedokument must be generated before the Forutsetningsbrev.
Rules for when you can generate forutsetningsbrev for a pantedokument
Forutsetningsbrev only makes sense when pantedokument will be sent to a broker (the pantedokument has document flow DOKUMENT_TIL_OPPGJOER.
Format of the generated Forutsetningsbrev
Ambita will generate a forutsetningsbrev formatted according to the DSVE standard (version 2). For more information about the standardization process and format, including an XSLT for presentation, can be found on the official DSVE github account: https://github.com/bitsnorge.
This version is pretty much the same as version one (generatePrerequisite) but the free text fields and return information is removed. Some XML elements are renamed slightly to improve the Norwegian spelling.
Example generateForutsetningsbrev:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:dok="http://dokument.ws7.etinglysing.no/">
<soapenv:Header/>
<soapenv:Body>
<dok:generateForutsetningsbrev>
<pantedokumentId>?</pantedokumentId>
<forutsetningsbrev>
<prioritet>
<foersteprioritet>?</foersteprioritet>
<!--Optional: only if NOT first priority-->
<prioritetsangivelser>
<!--1 or more repetitions:-->
<prioritetsangivelse>
<!-- PRIORITET_ETTER or PRIORITET_LIKESTILT_MED -->
<rekkefoelge>?</rekkefoelge>
<panthaver>
<offisiellId>?</offisiellId>
<navn>?</navn>
</panthaver>
<beloep valuta="?" verdi="?"/>
</prioritetsangivelse>
</prioritetsangivelser>
</prioritet>
<overfoerselsdetaljer>
<dato>?</dato>
<beloepTilMegler>?</beloepTilMegler>
<kontonummer>?</kontonummer>
<!--Optional:-->
<kid>?</kid>
</overfoerselsdetaljer>
<avsender>
<!--Optional:-->
<navn>?</navn>
<!--Optional:-->
<epost>?</epost>
<!--Optional:-->
<telefonDirekte>?</telefonDirekte>
<!--Optional:-->
<telefon>?</telefon>
<!--Optional:-->
<saksnummer>?</saksnummer>
</avsender>
<megler>
<navn>?</navn>
<organinsasjonsnummer>?</organinsasjonsnummer>
<!--Optional:-->
<saksnummer>?</saksnummer>
</megler>
</forutsetningsbrev>
</dok:generateForutsetningsbrev>
</soapenv:Body>
</soapenv:Envelope>
Data fields in input
Field name | Description | Example |
---|---|---|
overfoerselsdetaljer.dato | This is the date (in the future) when the bank will transfer the money to the broker. |
|
avsender.saksnummer | A reference or other value that identifies the bank’s loan case. The bank should (if possible) use the same reference for requesting purchase contract, sending the bank’s intention, when creating the mortgage (pantedokument) and creating the forutsetningsbrev. |
|
megler.saksnummer | The reference or other value that identifies the broker’s assignment/case number. In the |
|
|
|
|
How to fill out priority when forstePrioritet is false
The element <foersteprioritet>
is a mandatory field.
When this element has the value true: <foersteprioritet>true</foersteprioritet>
, then you do not fill out <prioritet>
.
But when the value is false: <foersteprioritet>false</foersteprioritet>
, you have to fill out priority.
Here is an example of how the priority can be filled out. The element <rekkefoelge>
needs to have one of two possible values PRIORITET_ETTER
or PRIORITET_LIKESTILT_MED
.
Note that for panthaver
you must specify at least one of offisiellId
or name
, both cannot be empty.
<forstePrioritet>false</forstePrioritet>
<prioritet>
<prioritetsangivelser>
<prioritetsangivelse>
<rekkefoelge>PRIORITET_ETTER</rekkefoelge>
<panthaver>
<offisiellId>987412548</offisiellId>
<navn>Husbanken</navn>
</panthaver>
<beloep valuta="NOK" verdi="1000000"/>
</prioritetsangivelse>
<prioritetsangivelse>
<rekkefoelge>PRIORITET_LIKESTILT_MED</rekkefoelge>
<panthaver>
<offisiellId>921345687</offisiellId>
<navn>Sparebanken Vest</navn>
</panthaver>
<beloep valuta="NOK" verdi="2000000"/>
</prioritetsangivelse>
</prioritetsangivelser>
</prioritet>