Bounced Valuation

When bouncing a Valuation from Compliance, ValEx will send the following Web Services message, to be parsed by the Valuation Firms for notification to review the report.

Valfirms should implement the following new method:
bouncedFromCompliance(ValEx_id, comment).

Fee Updated Message

A notification is required to be sent each time a fee has been amended/updated on a job request via the edit tab and the job has already been accepted by a Valuation Firm (ValEx will utilise the ValFirm Fee Field being actually changed from one value to another, to determine whether this notification should be sent).

ValEx will simply resend this as a standard order() with new details.

Re-Allocation Advice

A notification will be sent to the ValFirm when a job that is currently assigned to the incoming status (not yet assigned to a Valuer) and is reallocated to an alternate ValFirm.

This will utilise existing functionality (call to cancel()), with the addition of adding a reallocation comment to firms.

Re-engineered Valuation Process through ValEx

Please be aware that we will be rolling out the changes related to the improvements being made to the Communications and Process from Valuation Firms to ValEx and Clients with the view to create greater transparency of the Valuation Process. This is scheduled to be released on 17th March 2013.

The changes will encompass the ability for Valfirms being able send/receive the following messages via Web Services:


Recommendation is a field within ValEx which will allow the valuer to indicate whether the property is appropriate to be considered as security for lending purposes.

Recommendation is generally an optional field for Valuers. Some clients may select (due to their Mortgage Insurer’s requirements) that this is a mandatory question to answer (please refer to the 'RequiresRecommendation' section below for more detail on this).


Recommendation actually encompasses the following three fields in Lixi (these will be described in the following sections):

  • //ValueComponent/@RequiresRecommendation
  • //ValueComponent/@RecommendedSecurity
  • //ValueComponent/@RecommendationReason


From a ValEx perspective there are settings which stipulates whether Recommendation is a mandatory field for valuers to answer for each Client or Funder. This will be sent from ValEx to the LIXI Firms via setting the RequiresRecommendation as “Yes” in the request when required:

<ValueComponent ... RequiresRecommendation=”Yes”> 

In turn, it will then be up to the valfirms to implement on their system to determine whether the Recommendation is required to be provided, based on what they receive from RequiresRecommendation.


This is the actual field for indicating whether the Security is an acceptable security to be considered for Lending Purposes.

There are currently 3 outputs for this field in Lixi:

When the Valuer is indicating that the Security is an acceptable security to be considered for Lending Purposes:

<ValueComponent ... RecommendedSecurity=”Yes”> 

When the Valuer is indicating that the Security is not an acceptable security to be considered for Lending Purposes:

<ValueComponent ... RecommendedSecurity=”No”> 

When the Valuer is not indicating either way (due to the setting being optional in ValEx per client/funder):

<ValueComponent ... >


When the Valuer indicates that the Security is not an acceptable security to be considered for Lending Purposes (i.e. RecommendedSecurity="No"), we will require comments to support this, at least 5 words will be required:

<ValueComponent ... RecommendedSecurity="No" RecommendationReason="This is not an acceptable security to be considered">

Environmental & Heritage Issues

As per the new API Rewrite implementation post July 1st 2012, there have been changes in relation to the parsing of the values in Lixi for the Environmental and Heritage Issues under the RiskAnalysis node:

  • //RiskAnalysis[@EnvironmentIssues]
  • //RiskAnalysis[@HeritageIssues]

The following is how the fields are parsed by ValEx from Lixi into the report:


will simply populate as a blank option in the report.


will indicate as the 'None' option in the report.

On the other hand, if these fields are neither set to blank or None:

//RiskAnalysis[@EnvironmentIssues="There are Environmental Issues"]
//RiskAnalysis[@HeritageIssues="There are Heritage Issues"]

these will basically populates as actual comments in those fields.


RequestDate is when the valuation was ordered by the client. Valex sends this.

Submitting Job Notes

Valex now supports a solution for sending job notes via LIXI without removing delays. Previously, using an InProgress workflow was the only way to send job notes, but that is coupled to the functionality of removing delays.

We invite you to test and deploy our submitJobNotes(string valuationMessage) SOAP operation.


  • A ValuationType node is not allowed (including ValuationType/Workflow)
  • A MessageBody/Status is equally not allowed.
  • Job Notes are to be sent in MessageBody[@Type=”Information”]/MessageAnnotation[@Type=”EndUserMessage”]
<?xml version="1.0" encoding="utf-8"?>
<ValuationTransaction ProductionData="Yes"
<RevisionNumber LIXIVersion="1.4" LenderVersion="1.0" UserVersion="1.0" UserType="Valuer"/>
<Identifier UniqueID="VXJ-000001000000" Type="VPMAssigned" Description="Valex Reference Number"/>
<RelatedEntityRef RelatedID="VXV-100000"/>
<Identifier UniqueID="Dummy_Value" Type="VPMAssigned"/>
<Identifier UniqueID="VXJ-000001000000" Type="VPMAssigned"
Description="Valex Reference Number"/>
<MessageBody Type="Information">
<MessageAnnotation Type="EndUserMessage"><!--ENTER YOUR JOB NOTES HERE--></MessageAnnotation>
<RelatedParty RelPartyType="ValuationFirm">
<Identifier UniqueID="VXV-100000" Type="VPMAssigned"/>
<CompanyName BusinessName="John Smith Valuations"/>

Ordering an EVR (Electronic Valuer Review)

RP Data's EVR Reports may be ordered and managed within Valuation Exchange.

To order an EVR, select the service type as follows:

<FullRegistered ValSubType="ShortForm" ...>

Apart from the obvious fields that are included in standard valuation requests, some important fields include:

Inbound Reject Quote

rejectQuote() is a SOAP operation that may be optionally implemented as part of our LIXI Quote Process.

If the valuation firm decides to reject the quote request, the following SOAP operation should be called:

int rejectQuote(string valuationMessage)

We expect a standard LIXI message containing the following:

  • ValEx VXJ Identifier (VPMAssigned)
  • ValuationTransaction/Message/MessageBody/Status/@Name = Inquiring
  • //Workflow[@Type="FeeNegotiation"]/@FeeNegotiationStatus = Rejected
Syndicate content