When a listing is uploaded to Box+Dice, the current Enterprise Importer logic is as follows:

Find a Property from a XML file by its address (doesn't support lot numbers).

Update the Property information (if something changed, e.g. beds/baths, house/land sizes, etc).

Find a Sales Listing by uniqueID. If not found - try to find it by the Property address (like in step 1).

Update the Sales Listing information (e.g. prices, office, external reference ID, etc).

This can (and has) caused issues in a multi-office/office group system environment.
For example if the Listing was found by address, it may already contain some external reference ID. That external reference will be overwritten by a different uniqueID from the XML file, as well as agent/price/office details of some other office's previous listing.

Outcome
Can the logic be reviewed/amended to search for a listing by its uniqueID first, and then by property address as a secondary option.
It is also desirable that if a listing is found on a matching address with a different uniqueID, that this is not updated. An example of why: OfficeGroupA sold this listing 2 years ago, and left it as Not Settled in Box+Dice (because they use a 3rd-party CRM and don't fully manage their sales in B+D; they just want it on their GRAB website as a sold listing). But now Office-Group_B are selling the property, so a new listing should be created independent of the previous listing.