AU2004244648B2 - Quotation data exchange - Google Patents

Abstract

This invention concerns a quotation data exchange for the control of an insurance repair process utilising a host computer to create a communication path between an insurer's computer system and multiple repairer's computer systems. The communications are selected from a set of predefined messages having predefined possible order of communication and predefined content fields in which data is entered into. Each computer system may have a relational database in which the relevant quotation data is stored. This data is used to automatically populate the messages content fields before transmission. In another aspect the invention concerns a method of controlling an insurance repair process using the quotation data exchange message set. In further aspect, the invention concerns a protocol for a standard procedure of regulating the data transmission between insurer and repairer computer systems during the insurance repair process. I--- -- i Co kJZz F~ I~ ~I 4 ti II II ri ii 1&.J e~) L~J ('r)

Description

1 AUSTRALIA Patents Act 1990 INSURANCE AUSTRALIA LIMITED COMPLETE SPECIFICATION PATENT OF ADDITION Invention Title: Quotation data exchange The following statement is a full description of this invention including the best method of performing it known to us:- 2 Title Quotation Data Exchange Technical Field 5 This invention concerns the control of an insurance repair process. In one aspect it is a quotation data exchange for the control of an insurance repair process, and in another aspect it is a protocol for the control of an insurance repair process. Background Art 10 Motor vehicles need to be repaired after they are damaged for example, as a result of traffic accidents, malicious acts or hailstorms. The repair is typically not a simple transaction between the vehicle owner and a repairer, but will often involve a vehicle insurer. The insurer will generally wish to exercise some control over the repair, for instance in selection of the repairer and authorisation of repair items and 15 their cost. Summary of the Invention In a first aspect, the invention is a quotation data exchange for the control of an insurance repair process, including: 20 A host computer operating to enable communications between an insurer and a repairer where the communications are selected from a set of electronic messages having predetermined content fields in which data is entered, the message set including: A scope of works message, sent from insurer to repairer, containing details of the accident, insurance and vehicle information, expected repair details and vehicle 25 images; A quotation sent between repairer and insurer for repair of the damage specified in the scope of works message and including details of the repair, quote items and a status in respect of the quote. A tax invoice (request for payment) from repairer to insurer in respect of an 30 authorised repair; A payment authority from insurer to repairer in response to a request for payment. The status in respect of the quote may be selected from a list including "quoted", "repair authorised" and "repair not authorised". 35 The set of messages may also include: A message declining a repair (rather than a quote).

3 The insurer may send a message to the repairer declining payment. Other notifications and error messages may also be exchanged. The quote message may also include: A request for an inspection. 5 A request for total loss. The host computer may reside at the insurer's premises, and the system will typically involve a communications network, such as the Internet, and remote computers at the repairers. The host and remote computers may have relational databases in which the quotation data is stored. When a message is sent from one party 10 to the other, this data is gathered together and used to populate the messages before transmission. The electronic messages enable a vehicle re-instatement lifecycle to be communicated between the repairer and insurer in a common format. There is no specific processing dependent on a repairer. The messages are sufficiently flexible that 15 they can drive different repair models. The data requirements may be expressed in a specific implementation of eXtensible Markup Language. This is a self-describing data protocol with syntactical facilities for mandatory fields, field grouping and allowable values. Each message is described in an XML Schema Definition (xsd) which describes each element and its 20 attributes plus the tags required to identify the element. For a specific occurrence of a message, each data element value is enclosed in the defined tags. A new message has been incorporated into the message set: Reference such that changes in the reference set do not force a change to the standard. The xsd is a de-normalised data definition that contains syntax and nesting of 25 elements such that complex relationships and data categorisation of the target relational database are implied in the message. It should be noted that although the result has an appearance of being simple because of its flat structure, there may be equivalent intelligence embedded in the message definition to the databases, and their complex relationships, where the 30 messages originate and terminate. The system aims to streamline current paper and fax-based processes, thus increasing efficiency and accuracy of data transfer. Enforcement of data integrity is achieved by use of an electronic record. Efficiency is achieved through easier storage of the quotation data for statutory requirements and also electronic records will allow 35 robotic checking for Parts and Hours submissions. The system also offers an opportunity for expansion to support richer and more powerful forms of 4 communication. In particular, more detailed information may be passed between the two parties, allowing better informed decisions to be made. One example of a process enhancement is the support for digital photos. By building an infrastructure for the communication of digital images, sufficient information can be gained by assessors 5 while reducing the need for on-site visits. In a further aspect, the invention is a method for controlling an insurance repair process using a quotation data exchange described above, comprising the steps of: entering and storing the required quotation information into an insurer's computer system in response to a claim; 10 sending a scope of works message, from insurer to repairer, containing details of the accident, insurance and vehicle information, expected repair details and vehicle images; that is automatically populated with stored quotation information in respect of specified damage; receiving a quotation for the repair of the specified damage; 15 automatically retrieving information contained within the quotation and storing the information on the insurer's computer system; sending further scope of works message that is automatically populated with quotation information stored on the insurer's computer system, that may or may not contain an authority to proceed with the repair; 20 receiving a tax invoice (request for payment) in respect of an authorised repair; automatically retrieving information contained within the tax invoice (request for payment) and storing the information on the insurer's computer system; sending a payment authority in response to a request for payment that is automatically populated with quotation information stored on the insurer's computer 25 system. In another aspect, the invention is a protocol for the control of an insurance repair process, involving the steps of exchanging communications between an insurer and a repairer the protocol defining the following message set having predetermined 30 content fields in which data is entered: a scope of works message, sent from the insurer to repairer, containing details of the accident, insurance and vehicle information, expected repair details and vehicle images; 4a a quotation sent between repairer and insurer for repair of the damage specified in the scope of works message and including details of the repair, quote items and a status in respect of the quote. 5 Brief Description of the Drawings An example of the invention will now be described with reference to the accompanying drawings, in which: 10 Fig. 1 is a schematic diagram showing the architecture of a data quotation exchange. Fig. 2 is a block diagram of the operation of the exchange. Fig. 3 is a flowchart of the workflow. Fig. 4 is all elevations of a vehicle with the sections identified by numbers. 15 Best Modes of the Invention The quotation data exchange (QDE) I facilitates communications between an insurer 2 and a number of repairers 3. The insurer has a software solution that integrates with its overall claims 20 process, while the repairers are using software packages developed by third-party vendors. The two parties communicate via the Internet 4, using a protocol, with the content of the communications encapsulated in messages 5. This is summarised in Fig. 1. 25 Quotation Data Exchange Architecture The exchange consists of the following key components: e Messaging architecture e Quotation Markup Language (QML) 30 35 5 The Messages The system provides an "interface" between the insurer's and repairers' systems. It allows either party to implement their internal systems to meet their internal business needs, while retaining the confidence that other parties can be communicated with, in a 5 standard way. Both the insurer and repairer systems store the quotation information in a database. When a message needs to be sent to the other party, this information is gathered together, and used to populate a message for transmission. When a message is received, another process of conversion will occur, to map 10 the data into the internal database model of the software system. As can be seen, the messages are only used during the communication of quotation information, and therefore only have to capture the information needed for this process. The storage of quotation information is the responsibility of the systems designers, and can be done using any method that meets the overall functional 15 requirements. This model of operation can be seen in Fig. 2. Request for Quote The Request for Quote message is sent from the insurer to the repairer, and 20 contains: e Details on the accident. * Insurance information such as: sum insured, insurance excess, etc. * Vehicle details, such as: make, model, VIN etc " Customer contact name and numbers. 25 The message also specifies: * The repair model that should be used for this job. * Whether the request is for comparison quotation purposes only, and repairs will not be conducted by the quoter. Once a request has been received by the repairer, a quotation is compiled and is 30 sent in QML format to the insurer. Alternatively, the repairer may decline the job or request a Total Loss.

6 Scope of Works The Scope of Works message is sent from the insurer to the repairer when the Tendering Repair model is in effect and contains the following data with an implicit invitation to tender for the job: 5 o Details on the accident. " Insurance information such as: sum insured, insurance excess, etc. e Vehicle details, such as: make, model, VIN etc " Expected repair details " Vehicle Images 10 Declined Repair The repairer sends this message to the insurer, indicating that they have declined the job, and provides a reason. 15 Quote The Quote message is the primary mechanism for communicating details between the two parties and is passed both from Repairer to Insurer and Insurer to Repairer. It is used in the following cases: " Initial quote, 20 e Adjustment by the assessor, " Variation by the repairer. * Total Loss request by the repairer " Total Loss determined by the assessor e Authorities by the Assessor 25 This message type contains: * General details on the repair, including: repair dates, updated incident reports, etc. " Extensive vehicle details, including: make, model, paint colour, options, etc. e Hourly rates for work, such as: painting, repairs, etc. 30 e Quote items with hours and/or costs providing details on the actual work to be completed.

7 " Optional request for a Total Loss implemented as a status " The status of this quotation eg. Repair Authority, Authority Withheld, Authority Withdrawn, Total Loss Request, Total Loss Determined, Cash Settlement 5 * Optional request for an On-site Inspection Job Cancelled This message is sent if the insurer does not wish to proceed with his original request. There may be a variety of reasons, from the insured wishing to have another 10 repairer allocated to the submission of a totally unacceptable quotation. Job Cancelled Reasons include " Unacceptable Quotation e Another Repairer allocated either by the Customer or Insurer e Unsuccessful Tender 15 o Technical problems have caused the Insurer & Repairer to be out of sync and unrecoverable Payment Request A payment request message is sent from the repairer to the insurer to indicate that 20 the job has been completed, and to request payment. Additional information needed to manage the GST is also included. Statutory requirements pertaining to GST have caused a payment request to be split into 3 differing message formats. " Tax Invoice 25 e Adjustment Note e Re-activate Invoice Tax Invoice This message is sent by the Repairer to the Insurer as the original request for payment. 30 Adjustment Note This message is sent by the repairer to the insurer to adjust a previously submitted Tax Invoice. This message is an increment or decrement to what has been sent previously.

8 Re-Activate Invoice This message is sent by the repairer to the insurer to re-activate a previously submitted Tax Invoice. This implies that the amounts requested are as originally 5 submitted and some variation has been made to the quotation to make the authorised quotation balance with payment requested. Payment Authorised The insurer uses this message to notify that payment has been made, and 10 includes payment details such as invoice number, and actual payment date. Payment Declined The insurer uses this message to notify the repairer that a requested payment will not be made as requested and provides a reason. 15 Error The new method of transport of QDE messages, means that some errors previously notified to the repairer through a QDE message will now be notified through a transaction report. Errors notified in this way are those found by the xml parser which 20 utilises the often mentioned xsd. The transaction report is also used for positive acknowledgement. This message is used by either party to signal any errors encountered in incoming messages. 25 An error message will have 1 of 4 severities: e Informational - Information for the Repairer. * Warning - Warning for the repairer, but Inbound Message still processed. * Critical - Critical error for Repairer. Inbound Message not processed. Needs response by quotation application. 30 * System - Errors indicating that the system is not working. Eg database is down. System errors are not sent to the repairer. An Error message will have 1 of 5 types: * DataContent - The content of an element is not valid according to the defined 35 business rules. e Miscellaneous - An error that does not belong to any of the other types.

9 e Message Order - The Inbound Message has an invalid Message Number. * Validity - The Inbound Message fails to parse correctly against the appropriate XSD. 5 Image Any other message may be accompanied by one or more images .in a predefined format. These images may be annotated. Variations and adjustments 10 A Quote message consists of general information on the repair, and a number of quote items. These items specify the work to be completed, for example: repair and replace, part, painting, sundry, etc. A quote is always shipped in its entirety, viz. unchanged items are included in the message. For each quote item, there is a status that carries one of the following values: 15 e added " changed " deleted e acknowledged delete The values are used in the following manner: 20 * When a new quote is generated, all the items are marked as 'added'. * The 'added' flag is also used if a new item is added as part of a variation or adjustment. * If an adjustment or variation needs to be made, the quote items details are changed to the new values, and each modified quote item is marked as 25 'changed'. The updated Quote is then sent to the other party. * If an item is to be removed from the quote, it is marked as 'deleted'. It is not, however, omitted from the Quote message, such that an audit trail is maintained. Such an item should be shipped as 'acknowledged delete' in subsequent quote messages. 30 Quotation Markup Language (QML) The Quotation Markup Language (QML) defines a specification for all messages passed between the insurer and repairers. This specification is defined using the 10 eXtensible Markup Language (XML), an open standard for the development of industry-specific data formats. Use of XML brings with it a number of important benefits: e It is an open, vendor-neutral standard. 5 e It is platform-independent. e Many software vendors are providing support for XML. e It allows complex data to be stored in a simple format. * It is self-documenting: QML can be read and understood directly from the file without needing complex supporting documentation. 10 * Future extensions can be made to the business processes, while minimising the need for systems re-engineering. e Validity can be easily checked, and integrity ensured. To a large extent, the XML is self-explanatory, when read in conjunction with the following basic design principles: 15 e XML consists of tags, which are surrounded by angle brackets. An example of a tag: <QuoteDetails>. * In general, an element consists of a start and end tag. The content of the element is then located between these tags, and can consist of either text, or more elements. For example: 20 <RegistrationNo>UAA 169</RegistrationNo> or: <Vehicle> <BuildDate> 199001 </BuildDate> <KilometresTravelled>25000</KilometresTravelled> 25 </Vehicle> " An element may also have attributes, which define additional information about the element. For example: <Transmission Value="Automatic"/>. e The rules that define the names of the elements, and how they can be used are stored in a XML Schema Definition (XSD). 30 The simplest way of explaining a XSD is to work by example: e In the XSD, lines such as the following can be found: <!ELEMENT Vehicle (BuildDate, KilometresTravelled, EngineSize)> This defines the element Vehicle, and indicates that it contains BuildDate, followed by KilometresTravelled and EngineSize. 35 In the XML file, this would allow the following to be used: <Vehicle> '11 <BuildDate>199001 </BuildDate> <KilometresTravelled>25000</KilometresTravelled> <EngineSize>2.6</EngineSize> </Vehicle> 5 e These lines are also common: <ELEMENT BuildDate (#PCDATA)> This is just a complex way of saying the content of the element is text. For example: <BuildDate>199912</BuildDate> 10 e It is also possible to create more complex rules: <!ELEMENT Model (Make, ModelID, Description?, DateManufactureStart?)> This means that the Model must contain a Make, ModelID, optionally a Description, and optionally a DateManufactureStart. The question mark is an example of an operator in XML that specifies when an 15 element may appear. The full list: ?=may optionally be used *=may appear 0 or more times +=must appear at least once An XML file must meet the rules defined in its matching XSD. If it does so, it 20 is considered valid, otherwise an error is generated. The XSDs specify the structure of QML, but they do not detail the meaning of the elements. For example, an XSD can specify that an element contains text, or that it may contain a five digit number. This document therefore provides a detailed data definition for QML, along with 25 some brief explanatory information about each element. Note that: " There is one definition for each XSD. " The tag names in the definitions match exactly those defined in the XSDs. In this example the columns in the data definitions are used as follows: 30 e Tag name - the name of the element in the XSD " Lv (Level) - the hierarchical level at which the element exists. This is used to specify the parent child relationships between fields and which elements are grouped together. e Content type - "Group" for an element that only contains other elements; 35 "Char" for character data (text); "Flag" for an empty element; "Attr" for a 12 character attribute assigned to another element; "List" for a list of valid values; and "Numeric" for a decimal or floating point number. For "Char", "Attr", and "List" types, the maximum allowable length of the data is currently restricted to 4000 bytes due to technical limitations 5 In the case of "Numeric", the required format for the data is defined in the description column. This is in the form "zz99.99", where "z" and "9" denotes a single digit. For example, "zz9.99" means that there may be up to three digits, which can be followed by a decimal point and up to two decimal places. The use of "z" indicates that the digit is optional and does not have to be zero 10 padded. Any decimal places specified in the format description are optional and only need to be included in the data if necessary. Valid examples: "999":987;001;015 "zz9":987;l;15 15 "zz9.99":2.00,l.7;999.98;15 * Content Length - the length defined for an element is the maximum length expected by the recipient. e Req (Requirement) - the requirement specification for a field. This is defined by a set of codes as follows: 20 = M - Mandatory. For a Group, must always be present. For an element, if the group the element belongs to is present, the element must be present. Note: if a field is marked as mandatory it may not appear if its parent group is marked as optional. In addition, a mandatory field may not be blank or zero unless specifically described as such. 25 = 0 - Optional Element. Does not need to be sent with every message. -> MS - Mandatory Select of Element. This requirement is specified for a group of elements, from which there must always be one and only one of the elements specified in the report. = OS - Optional Select of Element. This requirement is specified for a 30 group of elements, from which there can either be none or only one of the elements specified in the report. o OL - Optional Linked Element. This requirement is specified for an element that is linked to another element(s) where either both (all) must be specified or none of them can be present.

13 => M+ - Mandatory List. This indicates that the element can be specified multiple times but there must always be at least one instance of it in a message. -> 0+ - Optional List. This indicates that the element can either be specified 5 multiple times or not at all. => MS+ - Mandatory Select List. This requirement is specified for a group of elements and it indicates that at least one of the elements from the group must be specified but there can be multiple instances of one or more of the elements. 10 All QML files created must use 7-bit ASCII. That is, no special characters must appear in the documents, beyond alphanumeric characters and punctuation. If high-order characters are required, they must appear in the form: 15 &#zzz; For example, character number 151 would be written as "&#151;". Furthermore, there are a number of special characters that must not be directly used in XML. Instead, the "escaped" form should be used, as follows: 20 Character Use instead &lt; > &gt; & &amp; &quot; &apos; Note: these requirements are part of the XML specification, and are not particular to QML.

14 Request for Quote This message is sent by the insurer to the repairer once only. Any information sent that requires updating will be contained in another message. Tag name Lvl Content Data Req Description type Size QML RequestForQuote 0 Group M Version 1 Group M QDEVersion 2 Char 5 M Version of QDE that this message complies with Source 1 Group M OrgType 2 Char 20 M The type of organisation. (Ref) Permissible values: Insurer, Repairer. AppVersion 2 Char 8 M The version number of the software used to create this message. AppName 2 Char 20 M The name of the software used to create this message. TimeStamp 2 DateTim 19 M The creation date and time e of this message, as generated by the system. Destination 1 Group M OrgType 2 Char 20 M The type of organisation. (Ref) Permissible values: Insurer, Repairer. MessageNo 1 Numeric 3 M Message No See Implementation doc for uses. Format: "zz9" 15 Tag name Lv Content Data Req Description type Size Insurer 1 Group M UnderwriterName 2 Char 45 M InsurerDetail 2 Char - M+ This tag(s) will contain Insurer Details. Eg ABN, AFS Licence No. FieldName 3 Attr 45 M This tag will name the field that it is an attribute of. Eg 'ABN' Repairer 1 Group M RepairerID 2 Char 8 M The Insurer allocated code for the repairer. RepairerName 2 Char 45 M The full name of the repairer RepairerDetail 2 Char - M+ This tag(s) will contain Repairer Details. Eg ABN. FieldName 3 Attr 45 M This tag will name the field that it is an attribute of. Eg 'ABN' Claim Header 1 Group M VehiclelD 2 Char 9 M Identifier for vehicle that will not change for the life of the repair. InsuranceClaimNo 2 Char 15 M The IAG claim number ReinstatementNo 2 Numeric 10 M Identifier of a vehicle repair within a specific Claim. Note: a claim may be lodged on behalf of the insured or other parties and give rise to multiple 16 Tag name Lv Content Data Req Description type Size iterations of repair. Eg Temporary, Repair, Rectification. Multiple quotes will be received per vehicle in the tendering model. Format: "zzzzzzzzz9" RequestDetails 1 Group M RequestType 2 Char 20 M Indicates aspects of the repair model eg. Assessed, Allocated, Comparison RequestDate 2 Date 10 M The date on which the request was made. ContractText 2 Char -- M Contractual text required for statutory reasons. This field is not length limited. IncidentDateTime 2 DateTim 19 0 The date and time when e the incident occurred. IncidentDescription 2 Char -- 0 A free text description of the incident. This field is not length limited. VehicleTowed 2 Flag -- 0 Flag if the vehicle has been towed, otherwise, the element is omitted. DamagedAreas 2 Group 0 Contains the list of damaged areas. DamagedArea 3 Char 2 0+ The IAG damaged area code. See Appendix 1 for coded values. ClaimDetails 2 Group M Claimant Type 3 Group OtherParty 4 Flag -- MS 17 Tag name Lv Content Data Req Description type Size Insured 4 Flag -- MS PolicyType 5 Char 20 M QDE Reference values: (Ref) Agreed Value, Market 1 Value, Limit of Cover SumInsured 5 Numeric 10 M The sum insured for the vehicle. Format: "zzzzzz9.99" ClaimThreshold 5 Numeric 10 0 Optional, may be zero. Format: "zzzzzz9.99" ExcessToCollect 5 Numeric 10 0 Optional, can only be positive or zero if specified. Format: "zzzzzz9.99" EstimatedQuoteDate 2 Date 10 0 The date booked with the customer for the quoting of the repair. HireCarIndicator 2 Flag -- 0 The presence of this tag indicates that the customer, will require a hire car. ClaimStatus 2 Char -- M The Status of the claim as at the R4Q Date. Used by Repairers who have authority for immediate start on repairs. This field I is not length limited. Vehicle 1 Group M RegistrationNo 2 Char 9 M The registration number of the vehicle to be repaired. EngineNo 2 Char 30 0 VIN 2 Char 30 0 This information will be sent if applicable to. the vehicle.

18 Tag name Lvl Content Data Req Description type Size BuildDate 2 Char 8 M This is of the format: yyyymm(dd) Make 2 Char 20 0 This information will be sent where available. ModelID 2 Char 20 0 Series 2 Char 20 0 Equipment Level 2 Char 20 0 BodyStyle 2 Char 20 0 Permissible Values to be supplied via QDEReferenceData: " Sedan4Door, " Hatch3Door, " Hatch5Door, " Wagon, * Coupe2Door, * Convertible2Do or, * 4wd2Door, * 4wd2DoorSoftT op, * 4wd4Door, * Utility2Door, * Utility4Door, SVan, * Commercial Note: Validation moved from QDE to application. Subject of Reference Set. Description 2 Char 30 0 VehicleMods 1 Group 0 VehicleMod 2 Char 20 0+ 19 Tag name Lvl Content Data Req Description type Size Customer 1 Group M PersonalName 2 Group MS Title 3 Char 25 0 Forname 3 Char 25 0 Surname 3 Char 25 M HomePhone 3 Char 20 0 This information will be sent where available. CompanyName 2 Char 45 MS BusinessPhone 2 Char 20 0 This information will be sent where available. Fax 2 Char 20 0 This information will be sent where available. MobilePhone 2 Char 20 0 This information will be sent where available.

20 Scope of Works This message is sent by the insurer to one or many repairers once only. Any information sent that requires updating will be contained in another message. Vehicle Images may 5 be sent in conjunction with this message. Tag name Lv Content Data Req Description type Size QML ScopeOfWorks 0 Group M Version I Group M QDEVersion 2 Char 5 M Version of QDE that this message complies with Source 1 Group M OrgType 2 Char 20 M The type of organisation. (Ref) QDE Reference data. AppVersion 2 Char 8 M The version number of the software used to create this message. AppName 2 Char 20 M The name of the software used to create this message. TimeStamp 2 DateTime 19 M The creation date and time of this message, as generated by the system. Destination 1 Group M OrgType 2 Char 20 M The type of organisation. (Ref) QDE Reference data. MessageNo 1 Numeric 3 M Message No See Implementation doc for uses. Format: "zz9" 21 Tag name Lvl Content Data Req Description type Size Insurer 1 Group M UnderwriterName 2 Char 45 M InsurerDetail 2 Char - M+ This tag(s) will contain Insurer Details. Eg ABN, AFS Licence No. FieldName 3 Attr 45 M This tag will name the field that it is an attribute of. Eg 'ABN' Repairer 1 Group M RepairerID 2 Char 8 M The Insurer allocated code for the repairer. RepairerName 2 Char 45 M The full name of the I repairer RepairerDetail 2 Char - M+ This tag(s) will contain* Repairer Details. Eg ABN. FieldName 3 Attr 45 M This tag will name the field that it is an attribute of. Eg 'ABN' Claim Header 1 Group M VehicleID 2 Char 9 M Identifier for vehicle that will not change for the life of the repair. InsuranceClaimNo 2 Char 15 M The IAG claim number ReinstatementNo 2 Numeric 10 M Identifier of a vehicle repair within a specific Claim. Note: a claim may be lodged on behalf of the insured or other parties and give rise to multiple 22 Tag name Lvl Content Data Req Description type Size iterations of repair. Eg Temporary, Repair, Rectification. Multiple quotes will be received per vehicle in the tendering model. Format: "zzzzzzzzz9" ScopeOfWorksDetails 1 Group M TenderCloseDateTime 2 DateTime 19 M The date and time when the tender closes. RequestType 2 Char 20 M Indicates aspects of the repair model and authorities to be applied to this repair. eg. Tendered ContractText 2 Char -- M Contractual text required for statutory reasons. This field is not length limited. IncidentDateTime 2 DateTime 19 0 The date and time when the incident occurred. IncidentDescription 2 Char -- 0 A free text description of the incident. This field is not length limited. VehicleTowed 2 Flag -- 0 If the vehicle has been towed, this element is used in the message; otherwise, the element is omitted. DamagedAreas 2 Group 0 Contains the list of damaged areas. DamagedArea 3 Char 2 0+ The IAG damaged area 23 Tag name Lv Content Data Req Description type Size code. See Appendix 1 for coded values. ClaimDetails 2 Group M Claimant Type 3 Group OtherParty 4 Flag -- MS Insured 4 Flag -- MS PolicyType 5 Char 20 M Values: Agreed Value, (Ref) Market Value, Limit of Cover SumInsured 5 Numeric 10 M The sum insured for the vehicle. Format: "zzzzzz9.99" ClaimThreshold 5 Numeric 10 0 Optional, may be zero. Format: "zzzzzz9.99" ExcessToCollect 5 Numeric 10 0 Optional, can only be positive or zero if specified. Format: "zzzzzz9.99" OwnersContribution 2 Group 0 ToCollect Value 3 Numeric 10 M Value set by the assessor and may not be revised by the repairer. It is inclusive of Tax. Format: "zzzzzz9.99" Reason 3 Char -- M The reason for the owner's contribution amount. This field is not length limited. PreferredStartDate 2 Date 10 0 Date nominated by the 24 Tag name Lv Content Data Req Description type Size customer as the preferred start of the repair. HireCarIndicator 2 Flag -- 0 The presence of this tag indicates that the customer will require a hire car. OpenText 1 Char - 0 Free form text supplied by the assessor Vehicle 1 Group M RegistrationNo 2 Char 9 M The registration number of the vehicle to be repaired. EngineNo 2 Char 30 0 VIN 2 Char 30 0 This information will be sent if applicable to the vehicle. BuildDate 2 Char 8 M This is of the format: yyyymm(dd) Make 2 Char 20 0 This information will be sent where available. ModelID 2 Char 20 0 Series 2 Char 20 0 Equipment Level 2 Char 20 0 BodyStyle 2 Char 20 0 Permissible Values to be supplied via QDEReferenceData: " Sedan4Door, * Hatch3Door, " Hatch5Door, e Wagon, e Coupe2Door, 25 Tag name Lvl Content Data Req Description type Size * Convertible2D oor, * 4wd2Door, * 4wd2DoorSoft Top, * 4wd4Door, 0 Utility2Door, Utility4Door, SVan, * Commercial Note: Validation moved from QDE to application. Subject of Reference Set. Description 2 Char 30 0 VehicleDetails 1 Group M Odometer 2 Group 0 OdometerReading 3 Char 7 M Format of 'zzzzzz9' OdometerUnitKm 3 Flag -- MS OdometerUnitMiles 3 Flag -- MS EngineSize 2 Char 4 0 This is in units of litres. Format 'z9.9'. NoOfCylinders 2 Char 2 0 Format '9' or '99'. Transmission 2 Char 9 0 Values: Automatic, (Ref) Manual Colour 2 Char 20 0 ManufacturerPaintGro 2 Char 2 M Values: S1, S2, M1, M2, up M3 Note validation removed from xsd to application ManufacturerTrimCode 2 Char 10 0 PaintCode 2 Char 10 0 OptionCode 2 Char 13 0 1 26 Tag name Lv Content Data Req Description type Size VehicleLocation 2 Char 20 M The location of the (Ref) vehicle at the time the insurer will receive the quote. Values: 'Repairer', 'Customer', 'RMC' VehicleMods 1 Group 0 VehicleMod 2 Char 20 M+ ScopeItems 1 Group 0 Group containing a list of damaged items with no implied method of repair. ScopeItem 2 Char 40 M+ Free format description of I unspecified item QuoteItems 1 Group 0 Group containing specific damaged items with repair category and item no that must be adhered to in the resulting quotation. QuoteItem 2 Group M+ ItemNo 3 Numeric 4 M A sequentially generated unique ID for the quote item. Format: "zzz9" Code 3 Char 9 M A generic description code for the item. Valid codes will be specified in the QDEReferenceData message Description 3 Char 60 M A full description of the item. The description is 27 Tag name Lvl Content Data Req Description type Size expected to be limited to 40 characters. The xml allows for 60 to accommodate escape sets in the case of special characters. QuoteItemValue 3 Numeric 10 M Mandatory but may be zero. Will be zero unless Hours & Hourly Rate are populated in the category group. Must be zero for Miscellaneous: Sublet type direct bill. This is a calculated value, determined as follows: QuoteltemValue = (Hours * DefaultHourlyRate) or (Hours * HourlyRate) or (PaintValue) or (Quantity * PartValue) or (MiscellaneousValue) Format: "zzzzzz9.99" RemoveReplace 3 Group MS Hours 4 Numeric 6 0 Mandatory but may be zero eg Report Item Format: "zz9.99" HourlyRate 4 Numeric 6 0 If specified, overrides the RemoveReplaceHourlyRa 28 Tag name Lvl Content Data Req Description type Size te in the HourlyRates group. Format: "zz9.99" Repair 3 Group MS Hours 4 Numeric 6 0 Mandatory but may be zero eg Report Item Format: "zz9.99" HourlyRate 4 Numeric 6 0 If specified, overrides the RepairHourlyRate in the HourlyRates group. Format: "zz9.99" PaintLabour 3 Group MS Hours 4 Numeric 6 0 Mandatory but may be zero eg Report Item Format: "zz9.99" HourlyRate 4 Numeric 6 OL If specified, overrides the PaintLabourHourlyRate in the HourlyRates group. If used then OtherPaintGroup is mandatory. Format: "zz9.99" OtherPaintGroup 4 Char 2 OL Permissible Values: Sl, S2, Ml, M2, M3 If this tag is used then the HourlyRate tag is mandatory. PaintMaterials 3 [ Group MS 29 Tag name Lv Content Data Req Description type Size PaintValue 4 Numeric 10 0 Paint material costs specified as a value. Format: "zzzzzz9.99" Part 3 Group MS PartValue 4 Numeric 10 0 Unit Price for this quote item. Mandatory but may be zero eg Report Item Format: "zzzzzz9.99" PartQuantity 4 Numeric 3 M Format: "zz9" PartOrientation 4 Char 5 M QDE Reference data. (Ref) Values: Left, Right, Other PartSource 4 Group 0 Aftermarket 5 Flag -- MS PartNumber 6 Attr -- 0 Exchange 5 Flag - MS PartNumber 6 Attr -- 0 Used 5 Flag -- MS PartNumber 6 Attr -- 0 OEM 5 Flag -- MS PartNumber 6 Attr -- M Miscellaneous 3 Group MS MiscellaneousValue 4 Numeric 10 M Mandatory but may be zero eg Report Item Format: "zzzzzz9.99" Sublet 4 Group 0 This group is used to indicate that this item will be sublet. SubletType 5 Char 45 M Values: Direct Bill, Paid (Ref) through Repairer SubletRepairer 5 Char 45 M The name of the business Name that the work has been sublet to.

30 Tag name Lvl Content Data Req Description type Size Mechanical 3 Group MS Hours 4 Numeric 6 M Mandatory but may be zero eg Report Item Format: "zzzzzz9.99" HourlyRate 4 Numeric 6 0 If specified, overrides the MechanicalHourlyRate in the HourlyRates group. Format: "zz9.99" Comment 3 Char -- 0 An option comment, providing more information about the item. UpdateStatus 3 Char -- M Update Status for this Item. This field is not length limited. The different statuses can change via QDEReferenceData messages. The original set of statuses will be: * Added - This indicates that the item details have been added since the last message ReportOn 3 Flag -- 0 This tag indicates that the 31 Tag name Lv Content Data Req Description type Size validity of this item in the quote is an outstanding issue. If this flag is set, any value associated with the item will not be included in the quote totals.

32 Declined Repair This message is sent by the repairer to the insurer once only and is an end state for the referenced Request.for Quote. 5 Tag name Lvl Content Data Req Description type Size QML Declined 0 Group M Version 1 Group M QDEVersion 2 Char 5 M Version of QDE that this message complies with Source 1 Group M OrgType 2 Char 20 M The type of organisation. (Ref) QDE Reference data. AppVersion 2 Char 8 M The version number of the software used to create this message AppName 2 Char 20 M The name of the software used to create this message TimeStamp 2 DateTim 19 M The creation date and time e of this message, as generated by the system. Destination 1 Group M OrgType 2 Char 20 M The type of organisation. (Ref) QDE Reference data. MessageNo 1 Numeric 3 M Message No See Implementation doc for uses. Format: "zz9" Insurer 1 Group M 33 Tag name Lvl Content Data Req Description type Size UnderwriterName 2 Char 45 M InsurerDetail 2 Char - 0+ This tag(s) will contain Insurer Details. Eg ABN, AFS Licence No. FieldName 3 Attr 45 M This tag will name the field that it is an attribute I of. Eg 'ABN' Repairer 1 Group M RepairerID 2 Char 8 M The Insurer allocated code for the repairer. RepairerName 2 Char 45 M The full name of the repairer RepairerDetail 2 Char - M+ This tag(s) will contain Repairer Details. Eg ABN. FieldName 3 Attr 45 M This tag will name the field that it is an attribute of. Eg 'ABN' Claim Header 1 Group M VehiclelD 2 Char 9 M Identifier for vehicle that will not change for the life of the repair. InsuranceClaim 2 Char 15 M The IAG claim number No ReinstatementNo 2 Numeric 10 M Identifier of a vehicle repair within a specific Claim. Note: a claim may be lodged on behalf of the insured or other parties and give rise to multiple iterations of repair. Eg Temporary, Repair, 34 Tag name Lvl Content Data Req Description type Size Rectification. Multiple quotes will be received per vehicle in the tendering model. Format: "zzzzzzzzz9" QuoteNo 1 Char 10 M Unique ID for quote, allocated by repairer. Note that a unique value is expected in this field whether a full quote has I__Ibeen generated or not. DeclinedDetail 1 Group M DeclinedDate 2 Date 10 M When the repair was declined. ReasonText 2 Char -- M The reason for declining the repair. This field is not length limited.

35 Quote This message may be sent by the repairer to the insurer and vice versa multiple times. Note that where there is a difference between the Required by Insurer and Required by 5 Repairer columns, the xsd will reflect the Required by Repairer column. Any implied requirement in the Insurer column will be policed by the application rather than the QDE standard. Tag name Lv Content Data Req Req Description type Size Ins Rep QML Quote 0 Group M M Version 1 Group M M QDEVersion 2 Char 5 M M Version of QDE that this message complies with Source 1 Group M M OrgType 2 Char 20 M M The type of organisation. (Ref) QDE Reference data. AppVersion 2 Char 8 M M The version number of the software used to create this message AppName 2 Char 20 M M The name of the software used to create this message TimeStamp 2 DateTim 19 M M The creation date & time e of this message. Destination 1 Group M M OrgType 2 Char 20 M M The type of organisation. (Ref) QDE Reference data. MessageNo 1 Numeric 3 M M Message No See Implementation doc for uses.

36 Tag name LvI Content Data Req Req Description type Size Ins Rep Format: "zz9" Insurer 1 Group M M UnderwriterName 2 Char 45 M M InsurerDetail 2 Char - M+ 0+ This tag(s) will contain Insurer Details. Eg ABN, AFS Licence No. Note that this field set will always be populated for Insurer occurrences. FieldName 3 Attr 45 M M This tag will name the field that it is an attribute of. Eg 'ABN' Repairer 1 Group M M RepairerID 2 Char 8 M M The Insurer allocated code for the repairer. RepairerName 2 Char 45 M M The full name of the repairer RepairerDetail 2 Char - M+ M+ This tag(s) will contain Repairer Details. Eg ABN. FieldName 3 Attr 45 M M This tag will name the field that it is an attribute of Eg 'ABN' Claim Header 1 Group M M VehicleID 2 Char 9 M M Identifier for vehicle that will not change for the life of the repair. InsuranceClaimNo 2 Char 15 M M The IAG claim number 37 Tag name Lvi Content Data Req Req Description type Size Ins Rep ReinstatementNo 2 Numeric 10 M M Identifier of a vehicle repair within a specific Claim. Note: a claim may be lodged on behalf of the insured or other parties and give rise to multiple iterations of repair. Eg Temporary, Repair, Rectification. Multiple quotes will be received per vehicle in the tendering model. Format: "zzzzzzzzz9" QuoteNo 1 Char 10 M M Unique ID for quote, allocated by repairer QuoteDate 1 Date 10 M M The date on which the quote was made. Note: IAG validates as > 1 Jul2000 QDEStatus 1 Group M M The Status of the quotation at the time of transmission. Status 2 Char -- M M Status for the Quote. This field is not length limited. The different statuses can change via QDEReferenceData messages. The original set of statuses will be: 38 Tag name Lv Content Data Req Req Description type Size Ins Rep Repairer: * Quoted - Default setting by the repairer e TotalLossRequeste d - Optional setting by the repairer. Note that the item content of a Quote with such a status will probably be incomplete. Insurer: e Authorised Authority is given to enact repairs based on this quotation e AuthorityWithheld - This quotation has been assessed but authority to proceed is temporarily withheld e AuthorityWithdra wn - This quotation has been authorised but authority to proceed is temporarily withdrawn * TotalLossDetermin 39 Tag name Lv Content Data Req Req Description type Size Ins Rep ed - The Insurer has determined the claim to be a total loss CashSettlement This claim will be settled via a cash settlement with the insured. The client may opt to have the vehicle repaired for this assessed quotation amount. Reason 2 Char -- 0 0 Text pertaining to the status. This field is not length limited. Inspection 1 Flag -- 0 0 Optional setting by the Requested repairer Inspection 2 Attr -- M M The reason for Reason requesting an inspection. This field is not length limited. QuoteDetails 1 Group M M QuoteType 2 Char 20 M M For insurer solicited quotes value to be mirror of RequestType value from R4Q, Scope of works eg. Assessed, Allocated, Comparison, Tendered 40 Tag name Lvi Content Data Req Req Description type Size Ins Rep (Translates to RepairModel in ORM) EstimatedStart 2 Date 10 M M Date is specified in the Date initial quote, but may be updated in later quote messages. EstimatedEnd 2 Date 10 M M Date is specified in the Date initial quote, but may be updated in later quote messages. Excessto 2 Numeric 10 M M Mandatory & positive Collect but may be zero. This value is set by the insurer & may be revised by the insurer at any time prior to payment. It cannot be amended by the repairer. Format: "zzzzzz9.99" Owners 2 Group -- 0 0 Contribution ToCollect Value 3 Numeric 10 M M This value is set by the assessor and may not be revised by the repairer. It is ex Tax. Format: "zzzzzz9.99" Reason 3 Char -- M M The reason for the owner's contribution amount. This field is not length limited. OpenText 2 Char -- 0 0 Comments by the repairer or assessor.

41 Tag name Lv Content Data Req Req Description type Size Ins Rep Comments from previous iterations of the quotation should not be repeated or returned. QuoterName 2 Char 45 0 0 This is the name of the staff member who conducted the quote at the repairer. Vehicle 1 Group M M Note: vehicle changes will not be automatically mapped into ORM from a variation. RegistrationNo 2 Char 9 M M The registration no of the vehicle to be repaired. EngineNo 2 Char 30 0 0 VIN 2 Char 30 0 0 This information will be sent if applicable to the vehicle BuildDate 2 Char 8 M M Format: yyyymm(dd) Make 2 Char 20 0 0 ModelID 2 Char 20 0 0 Series 2 Char 20 0 0 Equipment 2 Char 20 0 0 Level BodyStyle 2 Char 20 0 0 Permissible Values to be supplied via QDEReferenceData: * Sedan4Door, e Hatch3Door, * Hatch5Door, * Wagon, 42 Tag name Lv Content Data Req Req Description type Size Ins Rep e Coupe2Door, * Convertible2Door, 0 4wd2Door, 0 4wd2DoorSoftTop, e 4wd4Door, 0 Utility2Door, * Utility4Door, e Van, * Commercial Note: Validation moved from QDE to application. Subject of. Reference Set. Description 2 Char 30 0 0 VehicleDetails 1 Group M M Odometer 2 Group 0 0 OdometerRea 3 Char 7 M M Format of 'zzzzzz9' ding OdometerUnit 3 Flag -- MS MS Km OdometerUnit 3 Flag -- MS MS Miles EngineSize 2 Char 4 0 0 This is in units of litres. I__ Format 'z9.9'. NoOfCylinders 2 Char 2 0 0 Format '9' or '99'. Transmission 2 Char 9 0 0 Values: Automatic, (Ref) Manual Colour 2 Char 20 0 0 Manufacturer 2 Char 2 M M Values: S1, S2, M1, M2, Paint M3 Group Note validation removed from qde to ORM 43 Tag name Lv Content Data Req Req Description type Size Ins Rep Manufacturer 2 Char 10 0 0 TrimCode PaintCode 2 Char 10 0 0 OptionCode 2 Char 13 0 0 Vehicle 2 Char 20 M M The location of the Location (Ref) vehicle at the time the insurer will receive the quote. Values: 'Repairer', 'Customer', ____ ____ __ _ _ __ ___ ___'RMC' HourlyRates 1 Group M M Mechanical 2 Numeric 6 M M Format: "zz9.99" May HourlyRate be zero PaintHourly 2 Numeric 6 M M Format: "zz9.99" May Rate be zero RepairHourly 2 Numeric 6 M M Format: "zz9.99" May Rate be zero RemoveReplace 2 Numeric 6 M M Format: "zz9.99" May HourlyRate be zero Defines 1 Char -- R 0 These are used to include information that is of value to the sender, but is not defined by the XSD. The receiver of the message must echo back any data in these tags unchanged. See elsewhere for a discussion of how this system may be used to 44 Tag name Lvl Content Data Req Req Description type Size Ins Rep implement cycle numbers, for example. QuoteItems 1 Group 0 0 QuoteItem 2 Group M+ M+ ItemNo 3 Numeric 4 M M A sequentially generated unique ID for the quote item. Format: "zzz9" Code 3 Char 9 M M A generic description code for the item. A full list of valid codes will be specified in the QDEReferenceData message. Description 3 Char 60 M M A full description of the item. The description is expected to be limited to 40 characters. The xml allows for 60 to accommodate escape sets in the case of special characters. QuoteItem 3 Numeric 10 M M Mandatory but may be Value zero This is a calculated value, determined as follows: QuoteItem Value = (Hours * DefaultHourlyRate) or (Hours * HourlyRate) or (PaintValue) or (Quantity * 45 Tag name Lvi Content Data Req Req Description type Size Ins Rep PartValue) or (MiscelaneousValue) Format: "zzzzzz9.99" Remove 3 Group MS MS Replace I Hours 4 Numeric 6 M M Mandatory but may be zero eg Report Item Format: "zz9.99" Hourly 4 Numeric 6 0 0 If specified, overrides Rate the RemoveReplaceHourly Rate in the HourlyRates group. Format: "zz9.99" Repair 3 Group MS MS Hours 4 Numeric 6 M M Mandatory but may be zero eg Report Item Format: "zz9.99" Hourly 4 Numeric 6 0 0 If specified, overrides Rate the RepairHourlyRate in the HourlyRates group. Format: "zz9.99" PaintLabour 3 Group MS MS Hours 4 Numeric 6 M M Mandatory but may be zero eg Report Item Format: "zz9.99" Hourly 4 Numeric 6 OL OL If specified, overrides 46 Tag name Lvi Content Data Req Req Description type Size Ins Rep Rate the PaintLabourHourlyRate in the HourlyRates group. If used then OtherPaintGroup is mandatory. Format: "zz9.99" Other 4 Char 2 OL OL Permissible Values: Si, PaintGroup S2, M1, M2, M3 If this tag is used then the HourlyRate tag is mandatory. PaintMaterials 3 Group MS MS PaintValue 4 Numeric 10 M M Paint material costs specified as a value. Format: "zzzzzz9.99" Part 3 Group MS MS PartValue 4 Numeric 10 M M Unit Price for this quote item. Mandatory but may be zero eg Report Item 47 Tag name Lv Content Data Req Req Description type Size Ins Rep Format: "zzzzzz9.99" PartQuantity 4 Numeric 3 M M Format: "zz9" PartOrientation 4 Char 5 M M Values: Left, Right, (Ref) Other PartSource 4 Group M M Aftermarket 5 Flag -- MS MS PartNumber 6 Attr -- 0 0 Exchange 5 Flag -- MS MS PartNumber 6 Attr -- 0 0 Used 5 Flag -- MS MS PartNumber 6 Attr -- 0 0 OEM 5 Flag -- MS MS PartNumber 6 Attr -- M M Miscellaneous 3 Group MS MS Miscellaneous 4 Numeric 10 M M Mandatory but may be Value zero eg Report Item Format: "zzzzzz9.99" Sublet 4 Group -- 0 0 This group is used to indicate that this item is a sublet. SubletType 5 Char 45 M M Values: Direct Bill, Paid (Ref) through Repairer SubletRepairer 5 Char 45 M M The name of the Name business that the work has been sublet to. Mechanical 3 Group MS MS Hours 4 Numeric 6 M M Mandatory but may be zero eg Report Item Format: "zzzzzz9.99" HourlyR 4 Numeric 6 0 0 If specified, overrides ate the MechanicalHourlyRate in the HourlyRates 48 Tag name Lvi Content Data Req Req Description . type Size Ins Rep group. Format: "zz9.99" Towing 3 Group 0+ 0 Towing 4 Numeric 10 M M Format: "zzzzzz9.99" Value Comment 3 Char 100 0 0 An option comment, providing more information about the item. UpdateStatus 3 Char -- M M Update Status for this Quote Item. This field is not length limited. The different statuses can change via QDEReferenceData messages. The original set of statuses will be: * Accepted - This indicates that the item details have been accepted and not changed since the last message 0 Added - This indicates that the item details have been added since the last message * Changed - This indicates that the 49 Tag name Lvl Content Data Req Req Description type. Size Ins Rep item details have been changed since the last message. This includes if the ReportOn has been changed e Deleted - The item detail has been deleted by either the Repairer or Assessor * AcknowledgedDelet e - The item detail has been deleted & acknowledged and requires no more action. The item is present for information & completeness only. This setting is required on subsequent cycles of deleted items ReportOn 3 Flag -- 0 0 This tag indicates that the validity of this item in the quote is an outstanding issue. If this flag is set, any value associated with the item will not be included in the quote totals. Defines 3 Char -- R 0 These are used to include information that 50 Tag name Lv Content Data Req Req Description type Size Ins Rep is of value to the sender, but is not defined by the XSD. The receiver of the message must echo back any data in these tags unchanged. See elsewhere for a discussion of how this system may be used to implement cycle numbers, for example. Totals 1 Group M M GrandTotalEx 2 Numeric 10 M M A calculated value Tax consisting of the sum of all the QuoteltemValues. Format: "zzzzzz9.99" TaxRate 2 Numeric 6 M M Set by the repairers system Format: "z9.99" TaxAmount 2 Numeric 10 M M Calculated as GrandTotalExTax * TaxRate. Format: "zzzzzz9.99" Assessment 1 Group 0 0 AssessmentDat 2 Date 10 M M e 51 Tag name Lvl Content Data Req Req Description type Size Ins Rep AssessorName 2 Char 45 M M This is of the form: first name, last name. AssessorPhone 2 Char 20 M M AssessorMobil 2 Char 20 0 0 This information will be e sent where available. AssessorFax 2 Char 20 0 0 AssessorEmail 2 Char 40 0 0 Customer 1 Group M M PersonalDetail 2 Group MS MS Title 3 Char 25 0 0 Forname 3 Char 25 0 0 Surname 3 Char 25 M M HomePhone 3 Char 20 0 0 This information will be sent where available. CompanyName 2 Char 45 MS MS BusinessPhone 2. Char 20 0 0 This information will be sent where available. Fax 2 Char 20 0 0 This information will be sent where available. MobilePhone 2 Char 20 0 0 This information will be sent where available.

52 Job Cancelled This message is sent by the insurer to the repairer and is an end state. Note that it may 5 be sent prior to the receipt of a quotation. Tag name Lvl Content Data Req Description type Size QML JobCancelled 0 Group M Version 1 Group M QDEVersion 2 Char 5 M Version of QDE that this message complies with Source 1 Group M OrgType 2 Char 20 M The type of organisation. (Ref) QDE Reference data. AppVersion 2 Char 8 M The version number of the software used to create this message AppName 2 Char 20 M The name of the software used to create this message TimeStamp 2 DateTime 19 M The creation date and time of this message, as generated by the system Destination 1 Group M OrgType 2 Char 20 M The type of organisation. (Ref) QDE Reference data. MessageNo 1 Numeric 3 M Message No See Implementation doc for uses. Format: "zz9" 53 Tag name Lvl Content Data Req Description type Size Insurer 1 Group M UnderwriterName 2 Char 45 M InsurerDetail 2 Char - M+ This tag(s) will contain Insurer Details. Eg ABN, AFS Licence No. FieldName 3 Attr 45 M This tag will name the field that it is an attribute of. Eg 'ABN' Repairer 1 Group M RepairerID 2 Char 8 M The Insurer allocated code for the repairer. RepairerName 2 Char 45 M The full name of the repairer RepairerDetail 2 Char - 0+ This tag(s) will contain Repairer Details. Eg ABN. FieldName 3 Attr 45 M This tag will name the field that it is an attribute of. Eg 'ABN' Claim Header 1 Group M VehicleID 2 Char 9 M Identifier for vehicle that will not change for the life of the repair. InsuranceClaimNo 2 Char 15 M The IAG claim number ReinstatementNo 2 Numeric 10 M Identifier of a vehicle repair within a specific Claim. Note: a claim may be lodged on behalf of the insured or other parties and give rise to multiple iterations of repair. Eg Temporary, Repair, 54 Tag name Lvl Content Data Req Description type Size Rectification. Multiple quotes will be received per vehicle in the tendering model. Format: "zzzzzzzzz9" QuoteNo 1 Char 10 0 Unique ID for quote, allocated by repairer. Will always be populated subsequent to a Quotation supply. Reason 1 Char -- M The reason for the job cancellation, in words. Not length limited. Reasons may include and are not limited to: * Tender Unsuccessful * Quotation Unsatisfactory e System Exception to data exchanged 55 Tax Invoice This message is sent by the repairer to the insurer to request payment on an authorised quotation Multiple payments per repair are permissible and each should carry their own 5 unique Tax Invoice. Secondary and subsequent payment requests may occur because of items on back order or variations after original payment. Tag name Lv Content Data Req Description type Size QML TaxInvoice 0 Group M Version 1 Group M QDEVersion 2 Char 5 M Version of QDE that this message complies with Source 1 Group M OrgType 2 Char 20 M The type of organisation. (Ref) QDE Reference data. AppVersion 2 Char 8 M The version number of the software used to create this message AppName 2 Char 20 M The name of the software used to create this message TimeStamp 2 DateTim 19 M The creation date and time e of this message, as I generated by the system Destination 1 Group M OrgType 2 Char 20 M The type of organisation. (Ref) QDE Reference'data. MessageNo 1 Numeric 3 M Message No See Implementation doc for uses. Format: "zz9" 56 Tag name Lv Content Data Req Description type Size Insurer 1 Group M UnderwriterName 2 Char 45 M InsurerDetail 2 Char - 0+ This tag(s) will contain Insurer Details. Eg ABN, AFS Licence No. FieldName 3 Attr 45 M This tag will name the field that it is an attribute of. Eg 'ABN' Repairer 1 Group M RepairerID 2 Char 8 M The Insurer allocated code for the repairer. RepairerName 2 Char 45 M The full name of the repairer RepairerDetail 2 Char - M+ This tag(s) will contain Repairer Details. Eg ABN. FieldName 3 Attr 45 M This tag will name the field that it is an attribute of. Eg 'ABN' Claim Header 1 Group M VehiclelD 2 Char 9 M Identifier for vehicle that will not change for the life of the repair. InsuranceClaimNo 2 Char 15 M The IAG claim number ReinstatementNo 2 Numeric 10 M Identifier of a vehicle repair within a specific Claim. Note: a claim may be lodged on behalf of the insured or other parties and give rise to multiple iterations of repair.

57 Tag name Lvl Content Data Req Description type Size Eg Temporary, Repair, Rectification. Multiple quotes will be received per vehicle in the tendering model. Format: "zzzzzzzzz9" QuoteNo 1 Char 10 M Unique ID for quote, allocated by repairer Vehicle 1 Group M RegistrationNo 2 Char 9 M The registration number of the vehicle to be repaired. EngineNo 2 Char 30 0 Format of 'zzzzzz9' VIN 2 Char 30 0 This information will be sent if applicable to the vehicle. BuildDate 2 Char 8 M This is of the format: yyyymm(dd) Make 2 Char 20 0 This information will be sent where available. ModelID 2 Char 20 0 Series 2 Char 20 0 Equipment Level 2 Char 20 0 58 Tag name Lvl Content Data Req Description type Size BodyStyle 2 Char 20 0 Permissible Values to be supplied via QDEReferenceData: * Sedan4Door, e Hatch3Door, e Hatch5Door, " Wagon, * Coupe2Door, * Convertible2Door, * 4wd2Door, " 4wd2DoorSoftTop, * 4wd4Door, * Utility2Door, " Utility4Door, * Van, * Commercial Note: Validation moved from xml definition to application. Description 2 Char 30 0 TaxlnvoiceDetail 1 Group M TaxInvoice 2 Flag -- M To satisfy the statutory literal requirement CompletionDate 2 Date 10 M When the repair was I completed. Description 2 Char 100 M A description of the 59 Tag name Lv Content Data Req Description type Size services. This text is a Tax statutory requirement & is required to describe the reason for the payment. Preferably generated by the QSV package. Example: Repairs to vehicle {Rego} as per authorised quote for claim {Claim Number} . Note that where multiple invoices are sent, the 2 "d and subsequent description should be definitive and describe what the additional invoice is for. PaymentDetails 1 Group M RepairerTaxInvoiceNo 2 Char 20 M Repairer's Tax Invoice Number, allocated by repairer. Note that this number should be unique for a given Repairer, Tax Invoice. It will be carried through to any Adjustment 60 Tag name Lvl Content Data Req Description type Size Notes or Re-activate Invoice messages but a new number is required for second and subsequent Tax Invoices. TaxInvoiceDate 2 Date 10 M The date of this invoice was created. TotalExcludingTax 2 Numeric 10 M Format: "zzzzzz9.99" TotalTaxAmount 2 Numeric 10 M Format: "zzzzzz9.99" TotalIncludingTax 2 Numeric 10 M Should balance to TotalExcludingTax + TotalTaxAmount Format: "zzzzzz9.99" ExcessToCollect 2 Numeric 10 M Mandatory but may be zero. Value expected to be as per authorised quote. Format: "zzzzzz9.99" OwnersContributionToCollect 2 Group 0 Value 3 Numeric 10 M Value expected to be as per authorised quote. Inclusive of Tax. Format: "zzzzzz9.99" Reason 3 Char -- M The reason for the owner's contribution amount. This field is not length limited. TotalPayableAmount 2 Numeric 10 M Should balance to TotalExcludingTax + TotalTaxAmount ExcessToCollect OwnersContributionToCol lect.Value 61 Tag name Lvl Content Data Req Description type Size Format: "zzzzzz9.99" TaxRate 2 Numeric 6 M Mandatory but may be zero. Format: "zz9.99" OpenText 1 Char - 0 Comments by the repairer 62 Adjustment Note This message is sent by the repairer to the insurer to adjust a previously submitted Tax Invoice. This message is an increment or decrement to what has been sent previously. 5 Tag name Lvl Content Data Req Description type Size QML AdjustmentNote 0 Group M Version 1 Group. M QDEVersion 2 Char 5 M Version of QDE that this message complies with Source 1 Group M OrgType 2 Char 20 M The type of organisation. (Ref) QDE Reference data. AppVersion 2 Char 8 M The version number of the software used to create this message AppName 2 Char 20 M The name of the software used to create this message TimeStamp 2 DateTime 19 M The creation date and time of this message, as I generated by the system. Destination 1 Group M OrgType 2 Char 20 M The type of organisation. (Ref) QDE Reference data. MessageNo 1 Numeric 3 M Message No See Implementation doc for uses. Format: "zz9" Insurer 1 Group M 63 Tag name Lv Content Data Req Description type Size UnderwriterName 2 Char 45 M InsurerDetail 2 Char - 0+ This tag(s) will contain Insurer Details. Eg ABN, AFS Licence No. FieldName 3 Attr 45 M This tag will name the field that it is an attribute of. Eg 'ABN' Repairer 1 Group M RepairerID 2 Char 8 M The Insurer allocated code for the repairer. RepairerName 2 Char 45 M The full name of the repairer RepairerDetail 2 Char - M+ This tag(s) will contain Repairer Details. Eg ABN. FieldName 3 Attr 45 M This tag will name the field that it is an attribute of. Eg 'ABN' Claim Header 1 Group M VehicleID 2 Char 9 M Identifier for vehicle that will not change for the life of the repair. InsuranceClaimNo 2 Char 15 M The IAG claim number. ReinstatementNo 2 Numeric 10 M Identifier of a vehicle repair within a specific Claim. Note: a claim may be lodged on behalf of the insured or other parties and give rise to multiple iterations of repair. Eg Temporary, Repair, Rectification.

64 Tag name LvI Content Data Req Description type Size Multiple quotes will be received per vehicle in the tendering model. Format: "zzzzzzzzz9" QuoteNo 1 Char 10 M Unique ID for quote, allocated by repairer Vehicle 1 Group M RegistrationNo 2 Char 9 0 The registration number of the vehicle to be repaired. EngineNo 2 Char 30 0 VIN 2 Char 30 0 This information will be sent if applicable to the vehicle. BuildDate 2 Char 8 M This is of the format: yyyymm(dd) Make 2 Char 20 0 This information will be sent where available. ModelID 2 Char 20 0 Series 2 Char 20 0 Equipment Level 2 Char 20 0 65 Tag name Lvl Content Data Req Description type Size BodyStyle 2 Char 20 0 Permissible Values to be supplied via QDEReferenceData: * Sedan4Door, 0 Hatch3Door, * Hatch5Door, * Wagon, e Coupe2Door, * Convertible2Door, * 4wd2Door, * 4wd2DoorSoftTop, * 4wd4Door, * Utility2Door, * Utility4Door, * Van, * Commercial Note: Validation moved from xml definition to application. Description 2 Char 30 0 AdjustmentNoteDetails 1 Group M AdjustmentNote 2 Flag -- M To satisfy the statutory literal requirement AdjustmentNoteDate 2 Date 10 M The date of this adjustment note. SupplyDifferenceA 2 Numeric 10 M Mandatory but may be 66 Tag name Lvi Content Data Req Description type Size mount zero. The value is expected to be signed viz. A decrease will be negative. This field is a statutory value containing the difference in the taxable amount. It could be zero if the adjustment is in the ExcessToCollect. Should balance to: TaxInvoice.TotalIncluding Tax AdjustmentNote.Totallncl udingTax Format: "zzzzzz9.99" StatutoryStatement 2 Char -- M eg 'The difference in the taxable supply includes GST'. Required statement by GST legislation in Australia. PaymentDetails 1 Group M RepairerTaxInvoice 2 Char 20 M Repairer's Tax Invoice No Number, allocated by repairer. Should match the associated TaxInvoice. TaxInvoiceDate 2 Date 10 M The date the original tax invoice was created.

67 Tag name Lvl Content Data Req Description type Size TotalExcludingTax 2 Numeric 10 M Format: "zzzzzz9.99" TotalTaxAmount 2 Numeric 10 M Format: "zzzzzz9.99" TotalIncludingTax 2 Numeric 10 M Format: "zzzzzz9.99" ExcessToCollect 2 Numeric 10 M Mandatory but may be zero. Value expected to be as per authorised quote. Format: "zzzzzz9.99" OwnersContribution 2 Group 0 ToCollect Value 3 Numeric 10 M Value expected to be as per authorised quote. Inclusive of Tax. Format: "zzzzzz9.99" Reason 3 Char -- M The reason for the owner's contribution amount. This field is not length limited. TotalPayableAmount 2 Numeric 10 M Format: "zzzzzz9.99" TaxRate 2 Numeric 6 M Mandatory but may be zero. Format: "zz9.99" OpenText 1 Char - 0 Comments by the repairer 68 Re-Activate Invoice This message is sent by the repairer to the insurer to re-activate a previously submitted 5 Tax Invoice. This implies that the amounts requested are as originally submitted and some variation has been made to the quotation to make the authorised quotation balance with payment requested. Tag name Lvi Content Data Req Description type Size QMLReActivateInvoice 0 Group M Version 1 Group M QDEVersion 2 Char 5 M Version of QDE that this message complies with Source 1 Group M OrgType 2 Char 20 M The type of organisation. (Ref) QDE Reference data. AppVersion 2 Char 8 M The version number of the software used to create this message AppName 2 Char 20 M The name of the software used to create this message TimeStamp 2 DateTime 19 M The creation date and time of this message, as generated by the system. Destination 1 Group M OrgType 2 Char 20 M The type of organisation. (Ref) QDE Reference data. MessageNo I Numeric 3 M Message No See Implementation doc for uses.

69 Tag name Lv Content Data Req Description type Size Format: "zz9" Insurer 1 Group M UnderwriterName 2 Char 45 M InsurerDetail 2 Char - 0+ This tag(s) will contain Insurer Details. Eg ABN, AFS Licence No. FieldName 3 Attr 45 M This tag will name the field that it is an attribute of. Eg 'ABN' Repairer 1 Group M RepairerID 2 Char 8 M The Insurer allocated code for the repairer. RepairerName 2 Char 45 M The full name of the repairer RepairerDetail 2 Char - M+ This tag(s) will contain Repairer Details. Eg ABN. FieldName 3 Attr 45 M This tag will name the field that it is an attribute of. Eg 'ABN' Claim Header 1 Group M VehicleID 2 Char 9 M Identifier for vehicle that will not change for the life of the repair. InsuranceClaimNo 2 Char 15 M The IAG claim number ReinstatementNo 2 Numeric 10 M Identifier of a vehicle repair within a specific Claim. Note: a claim may be lodged on behalf of the insured or other parties and give rise to multiple 70 Tag name Lvi Content Data Req Description type Size iterations of repair. Eg Temporary, Repair, Rectification. Multiple quotes will be received per vehicle in the tendering model. Format: "zzzzzzzzz9" QuoteNo 1 Char 10 M Unique ID for quote, allocated by repairer Vehicle 1 Group M RegistrationNo 2 Char 9 0 The registration number of the vehicle to be repaired. EngineNo 2 Char 30 0 VIN 2 Char 30 0 This information will be sent if applicable to the vehicle. BuildDate 2 Char 8 M This is of the format: yyyymm(dd) Make 2 Char 20 0 This information will be sent where available. ModelID 2 Char 20 0 Series 2 Char 20 0 Equipment Level 2 Char 20 0 71 Tag name Lvl Content Data Req Description type Size BodyStyle 2 Char 20 0 Permissible Values to be supplied via QDEReferenceData: e Sedan4Door, e Hatch3Door, * Hatch5Door, e Wagon, * Coupe2Door, e Convertible2Door, * 4wd2Door, e 4wd2DoorSoftTop, a 4wd4Door, * Utility2Door, * Utility4Door, e Van, * Commercial Note: Validation moved from xml definition to application. Description 2 Char 30 0 ReActivateInvoiceDate 1 Date 10 M The date of this Re activation. PaymentDetails 1 Group M 72 Tag name Lv Content Data Req Description type Size RepairerTaxInvoiceNo 2 Char 20 M Repairer's Tax Invoice Number, allocated by repairer TaxInvoiceDate 2 Date 10 M The date of the associated tax invoice. TotalExcludingTax 2 Numeric 10 M Format: "zzzzzz9.99" TotalTaxAmount 2 Numeric 10 M Format: "zzzzzz9.99" TotallncludingTax 2 Numeric 10 M Format: "zzzzzz9.99" ExcessToCollect 2 Numeric 10 M Mandatory but may be zero. Value expected to be as per authorised quote. Format: "zzzzzz9.99" OwnersContributionTo 2 Group 0 Collect Value 3 Numeric 10 M Value expected to be as per authorised quote. Inclusive of Tax. Format: "zzzzzz9.99" Reason 3 Char -- M The reason for the owner's contribution amount. This field is not length limited. TotalPayableAmount 2 Numeric 10 M Format: "zzzzzz9.99" TaxRate 2 Numeric 6 M Mandatory but may be zero. Format: "zz9.99" OpenText 1 Char - 0 Comments by the repairer 73 Payment Authorised This message is sent by the insurer to the repairer once only per Tax Invoice and serves 5 to confirm that payment will be made as requested. Tag name Lv Content Data Req Description type Size QML PaymentAuthorised 0 Group M Version 1 Group M QDEVersion 2 Char 5 M Version of QDE that this message complies with Source 1 Group M OrgType 2 Char (Ret) 20 M The type of organisation. QDE Reference data. AppVersion 2 Char 8 M The version number of the software used to create this message AppName 2 Char 20 M The name of the software used to create this message TimeStamp 2 DateTime 19 M The creation date and time of this message, as generated by the system. Destination 1 Group M OrgType 2 Char (Ref) 20 M The type of organisation. QDE Reference data. MessageNo 1 Numeric 3 M Message No See Implementation doc for uses. Format: "zz9" 74 Tag name Lv Content Data Req Description type Size Insurer 1 Group M UnderwriterName 2 Char 45 M InsurerDetail 2 Char - M+ This tag(s) will contain Insurer Details. Eg ABN, AFS Licence No. FieldName 3 Attr 45 M This tag will name the field that it is an attribute I of Eg 'ABN' Repairer 1 Group M RepairerID 2 Char 8 M The Insurer allocated code for the repairer. RepairerName 2 Char 45 M The full name of the repairer RepairerDetail 2 Char - 0+ This tag(s) will contain Repairer Details. Eg ABN. FieldName 3 Attr 45 M This tag will name the field that it is an attribute of. Eg 'ABN' Claim Header 1 Group M VehiclelD 2 Char 9 M Identifier for vehicle that will not change for the life of the repair. InsuranceClaimNo 2 Char 15 M The IAG claim number ReinstatementNo 2 Numeric 10 M Identifier of a vehicle repair within a specific Claim. Note: a claim may be lodged on behalf of the insured or other parties and give rise to multiple iterations of repair. Eg Temporary, Repair, 75 Tag name Lvl Content Data Req Description type Size Rectification. Multiple quotes will be received per vehicle in the tendering model. Format: "zzzzzzzzz9" QuoteNo 1 Char 10 M Unique ID for quote, allocated by repairer Vehicle 1 Group M RegistrationNo 2 Char 9 M The registration number of the vehicle to be repaired. EngineNo 2 Char 30 0 Format of 'zzzzzz9' VIN 2 Char 30 0 This information will be sent if applicable to the vehicle. BuildDate 2 Char 8 M This is of the format: yyyymm(dd) Make 2 Char 20 0 This information will be sent where available. ModelID 2 Char 20 0 Series 2 Char 20 0 EquipmentLevel 2 Char 20 0 76 Tag name Lyi Content Data Req Description type Size BodyStyle 2 Char 20 0 Permissible Values to be supplied via QDEReferenceData: 0 Sedan4Door, * Hatch3Door, * Hatch5Door, * Wagon, 0 Coupe2Door, e Convertible2Door, * 4wd2Door, 0 4wd2DoorSoftTop, * 4wd4Door, * Utility2Door, * Utility4Door, SVan, * Commercial Note: Validation moved from xml definition to application. Description 2 Char 30 0 PayAuthorityDetails 1 Group M RepairerTaxInvoiceNo 2 Char 20 M Repairer's Tax Invoice Number, allocated by I repairer PayAuthorisedDate 2 Date 10 M When the payment authority was made.

77 Tag name Lvl Content Data Req Description type Size PaymentAmount 2 Numeric 10 M Format: "zzzzzz9.99" 78 Payment Declined This message is sent by the insurer to the repairer and serves to inform him that the requested payment will not be made for the given reason. 5 Tag name Lvl Content Data Req Description type Size QML PaymentDeclined 0 Group M Version 1 Group M QDEVersion 2 Char 5 M Version of QDE that this message complies with Source 1 Group M OrgType 2 Char 20 M The type of organisation. (Ref) QDE Reference data. AppVersion 2 Char 8 M The version number of the software used to create this message AppName 2 Char 20 M The name of the software used to create this message TimeStamp 2 DateTime 19 M The creation date and time of this message, as I__ I__ generated by the system. Destination 1 Group M OrgType 2 Char 20 M The type of organisation. (Ref) QDE Reference data. MessageNo 1 Numeric 3 M Message No See Implementation doc for uses. Format: "zz9" Insurer 1 Group M 79 Tag name Lvl Content Data Req Description type Size UnderwriterName 2 Char 45 M InsurerDetail 2 Char - M+ This tag(s) will contain Insurer Details. Eg ABN, AFS Licence No. FieldName 3 Attr 45 M This tag will name the field that it is an attribute of. Eg 'ABN' Repairer 1 Group M RepairerID 2 Char 8 M The Insurer allocated code for the repairer. RepairerName 2 Char 45 M The full name of the repairer RepairerDetail 2 Char - 0+ This tag(s) will contain Repairer Details. Eg ABN. FieldName 3 Attr 45 M This tag will name the field that it is an attribute of. Eg 'ABN' Claim Header 1 Group M VehiclelD 2 Char 9 M Identifier for vehicle that will not change for the life of the repair InsuranceClaimNo 2 Char 15 M The IAG claim number ReinstatementNo 2 Numeric 10 M Identifier of a vehicle repair within a specific claim. Note: a claim may be lodged on behalf of the insured or other parties and give rise to multiple iterations of repair. Eg Temporary, Repair, Rectification.

80 Tag name Lvl Content Data Req Description type Size Multiple quotes will be received per vehicle in the tendering model. Format: "zzzzzzzzz9" QuoteNo 1 Char 10 M Unique ID for quote, allocated by repairer Vehicle 1 Group M RegistrationNo 2 Char 9 M The registration number of the vehicle to be repaired. EngineNo 2 Char 30 0 Format of 'zzzzzz9' VIN 2 Char 30 0 This information will be sent if applicable to the vehicle. BuildDate 2 Char 8 M This is of the format: yyyymm(dd) Make 2 Char 20 0 This information will be sent where available. ModelID 2 Char 20 0 Series 2 Char 20 0 EquipmentLevel 2 Char 20 0 BodyStyle 2 Char 20 0 Permissible Values to be (Ref) supplied via QDEReferenceData: e Sedan4Door, e Hatch3Door, * Hatch5Door, * Wagon, * Coupe2Door, * Convertible2Door, 0 4wd2Door, * 4wd2DoorSoftTop, 81 Tag name Lvl Content Data Req Description type Size * 4wd4Door, 0 Utility2Door, * Utility4Door, 0 Van, * Commercial Note: Validation moved from xml definition to application. Description 2 Char 30 0 LastlnvoiceDetails 1 Group M RepairerTaxInvoiceN 2 Char 20 M Repairer's Tax Invoice 0 Number, allocated by repairer TaxInvoiceDate 2 Date 10 M The date of the invoice or adjustment being rejected. TotalExcludingTax 2 Numeric 10 M Format: "zzzzzz9.99" TotalTaxAmount 2 Numeric 10 M Format: "zzzzzz9.99" TotallncludingTax 2 Numeric 10 M Format: "zzzzzz9.99" ExcessToCollect 2 Numeric 10 M Mandatory but may be zero. Value expected to be as per authorised quote. Format: "zzzzzz9.99" OwnersContributionT 2 Group 0 oCollect Value 3 Numeric 10 M Value expected to be as per last payment request. Inclusive of Tax. Format: "zzzzzz9.99" Reason 3 Char -- M The reason for the owner's contribution amount. This field is not length limited. TotalPayableAmount 2 Numeric 10 M Format: "zzzzzz9.99" 82 Tag name Lvl Content Data Req Description type Size TaxRate 2 Numeric 6 M Format: "zz9.99" ExpectedPaymentDetails 1 Group M TotalExcludingTax 2 Numeric 10 M Format: "zzzzzz9.99" TotalTaxAmount 2 Numeric 10 M Format: "zzzzzz9.99" TotallncludingTax 2 Numeric 10 M Format: "zzzzzz9.99" ExcessToCollect 2 Numeric 10 M Format: "zzzzzz9.99" OwnersContributionTo 2 Group 10 M Collect Value 3 Numeric 10 M Value expected to be as per authorised quote. Inclusive of Tax. Format: "zzzzzz9.99" Reason 3 Char -- M The reason for the owner's contribution amount. This field is not length limited. TotalPayableAmount 2 Numeric 10 M Format: "zzzzzz9.99" TaxRate 2 Numeric 6 M Format: "zz9.99" Reason 1 Char -- M The reason the payment was declined.

83 Image This message accompanies any image sent from the repairer to the insurer and from the insurer to the repairer. A QML Image xml document is associated with one image file. 5 Tag name Lvl Content Data Req Description type Size QML Image 0 Group M Version 1 Group M QDEVersion 2 Char 5 M Version of QDE that this message complies with Source 1 Group M OrgType 2 Char 20 M The type of organisation. (Ref) QDE Reference data. AppVersion 2 Char 8 M The version number of the software used to create this message. AppName 2 Char 20 M The name of the software used to create this message. TimeStamp 2 DateTime 19 M The creation date and time of this message, as generated by the system. Destination _ Group M OrgType 2 Char 20 M The type of organisation. (Ref) QDE Reference data. RelatedMessageNo 1 Numeric 3 M Message No that the associated image relates to.. Format: "zz9" 84 Tag name Lv Content Data Req Description type Size Insurer 1 Group M UnderwriterName 2 Char 45 M InsurerDetail 2 Char - M+ This tag(s) will contain Insurer Details. Eg ABN, AFS Licence No. FieldName 3 Attr 45 M This tag will name the field that it is an attribute of. Eg 'ABN' Repairer 1 Group M RepairerID 2 Char 8 M The Insurer allocated code for the repairer. RepairerName 2 Char 45 M The full name of the repairer RepairerDetail 2 Char - M+ This tag(s) will contain Repairer Details. Eg ABN. FieldName 3 Attr 45 M This tag will name the field that it is an attribute of. Eg 'ABN' Claim Header 1 Group M VehicleID 2 Char 9 M Identifier for vehicle that will not change for the life of the repair. InsuranceClaimNo 2 Char 15 M The IAG claim number ReinstatementNo 2 Numeric 10 M Identifier of a vehicle repair within a specific Claim. Note: a claim may be lodged on behalf of the insured or other parties and give rise to multiple iterations of repair.

85 Tag name Lv Content Data Req Description type Size Eg Temporary, Repair, Rectification. Multiple quotes will be received per vehicle in the tendering model. Format: "zzzzzzzzz9" QuoteNo 1 Char 10 M Unique ID for quote, allocated by repairer. Note that a unique value is expected in this field whether a full quote has been generated or not. RegistrationNo 1 Char 20 M Registration number of the vehicle ImageNo 1 Numeric 3 M Unique image sequence number for this reinstatement. Eg the first image sent with for this claim will be "1", the second, "2" and so on. Note that images may be incoming eg tendering repair model as well as outgoing and the QSV package is expected to track Image Nos to retain unique values Format: "zz9" Open Text 1 Char - Any comments 86 Tag name Lvl Content Data Req Description type Size accompanying the image 87 Error This message is sent by the insurer to the repairer for the purpose of reporting an error with an associated repairer message. There may be multiple error messages generated 5 for the same original message. Upon receiving one of these error messages, the repairer's system should report the error to the user and if the message has a severity of "Critical" then it should update their system to reflect that the insurer has not accepted their original message. 10 Note that from QDE v3.0, xml parsing errors against the associated xsd will be notified via a Transport Report as detailed in the Error Handling separate document. Tag name Lv Content Data Req Description type Size QML Error 0 Group M Version 1 Group M QDEVersion 2 Char 5 M Version of QDE that this message complies with Source 1 Group M OrgType 2 Char (Ref) 20 M The type of organisation. QDE Reference data. AppVersion 2 Char 8 M The version number of the software used to create this message AppName 2 Char 20 M The name of the software used to create this message TimeStamp 2 DateTime 19 M The creation date and time of this message, as generated by the system. Destination 1 Group M OrgType 2 Char (Ref) 20 M The type of organisation.

88 Tag name Lv Content Data Req Description type Size QDE Reference data. RelatesToMessageNo 1 Numeric 3 0 The number of the message which caused the errors Format: "zz9" Insurer 1 Group - M UnderwriterName 2 Char 45 M InsurerDetail 2 Char - M+ This tag(s) will contain Insurer Details. Eg ABN, AFS Licence No. FieldName 3 Attr 45 M This tag will name the field that it is an attribute of Eg 'ABN' Repairer 1 Group M RepairerID 2 Char 8 M The Insurer allocated code for the repairer. RepairerName 2 Char 45 M The full name of the repairer RepairerDetail 2 Char - 0+ This tag(s) will contain Repairer Details. Eg ABN. FieldName 3 Attr 45 M This tag will name the field that it is an attribute of. Eg 'ABN' Claim Header 1 Group 0 VehiclelD 2 Char 9 M Identifier for vehicle that will not change for the life 89 Tag name Lv Content Data Req Description type Size of the repair. InsuranceClaimNo 2 Char 15 M The IAG claim number. ReinstatementNo 2 Numeric 10 M Identifier of a vehicle repair within a specific Claim. Note: a claim may be lodged on behalf of the insured or other parties and give rise to multiple iterations of repair. Eg Temporary, Repair, Rectification. Multiple quotes will be received per vehicle in the tendering model. Format: "zzzzzzzzz9" QuoteNo 1 Char 10 0 Unique ID for quote, allocated by repairer ErrorDetails 1 Group M+ Contains the errors encountered, with one entry per error Severity 2 Char 20 M Permissible Values provided through __ _QDEReferenceData DataContentError 2 Group MS The contents of an element are not meaningful 'according to the defined business rules. Description 3 Char 4000 M A human-readable description of the 90 encountered problem, giving sufficient detail to allow the problem to be diagnosed and resolved ElementName 3 Char 100 M The name of the element where the problem occurred Value 3 Char 4000 M The contents of the element that was in error. MessageOrderError 2 Group MS The received message has an invalid message number (out of order) Description 3 Char 4000 M A human-readable description of the encountered problem, giving sufficient detail to allow the problem to be diagnosed and resolved ExpectedMessageNo 3 Numeric 3 M The message number that was expected to be received Format: "zz9" ReceivedMessageNo 3 Numeric 3 M The actual message number of the received message Format: "zz9" MessageTypeError 2 Group MS The message type cannot be used at this point in the conversation (eg. Payment request before initial quote, etc) Description 3 Char 4000 M A human-readable description of the 91 encountered problem, giving sufficient detail to allow the problem to be diagnosed and resolved MiscellaneousError 2 Group MS A general error that does not belong to any of the other types. Description 3 Char 4000 M A human-readable description of the encountered problem, giving sufficient detail to allow the problem to be diagnosed and resolved 92 Glossary Term Definition Damaged Area Coded part of vehicle that is damaged as specified by the claimant Impact Area Coded part of vehicle that is damaged as specified by the assessor. Usually accompanied by a level of severity. Markup An insurer allowed percentage the repairer adds to the value of materials for storage & handling (and pre GST, WST) OEM Original Equipment Manufacturer QDE Quotation Data Exchange QML Quotation Markup Language QSV Quotation Software Vendor Re-instatement Generic term used to signify settlement of a claim, including Repair, Total Loss & Cash Settlement. Report On Items of the repair on which some issue exists that could not be resolved at the time of compilation or assessment of the quote message. VCP Virtual Claims Pocket 93 Workflow Referring to Fig. 3 the workflow can be seen to begin after a vehicle has been damaged and when a claim 31 is lodged. First a decision is made as to whether repair is to be allocated directly to a repairer for assessment or sought via a tendering process. 5 If the assessment route is chosen, a repairer is allocated 33 and a request for quote 34 is sent to the repairer 35. The repairer may decline the job 36 or quote for the job 37. If the tender route is chosen an appointment is booked 40 and a scope of work 10 document is constructed 41. The scope of work document 42 is initially accessed by the repairer through a web interface and then transmitted 43 to the repairer 35 on request. Again after considering the scope of works 42, the repairer may decline 36 or quote 37 for the repair. 15 The quote message is initially completed by the repairer and sent to the insurer, and thereafter that document is transmitted back and forth with adjustments by the insurer and variations by the repairer until the repair is resolved. The initial quote is considered differently depending on whether the tendering or 20 assessing route has been selected 50. If the tender route is chosen then the tender quote is evaluated 51 and.if accepted at 52 the repairer is allocated the job at 53 and a quote authority is issued 54 to the repairer 35. The tender may be declined or the job is cancelled at 55. If the assessment route is taken and the quotation is assessed at 60 an onsite inspection may be requested at 61 and if this is accepted the inspection takes 25 place at the repairer 35/62. If the inspection request is not granted then the full quote may be requested and quoted at 63. At the quotation and assessment stage another outcome could be that the repairer requests a total loss to be notified 64. If this is not accepted then a full quote may be 30 requested at 63, however if it is accepted, then the quote is given a total loss status at 65. Alternatively the assessment may result in a cash settlement being offered at 66. When the quote is accepted an assessment summary is provided to the claim system 53 and a quote authority is issued at 54 allowing the repairer to proceed with the repair. During the repair the repairer may vary the quote, using the quote message at 70. This 35 will be assessed at 71 and a new quote authority could be issued at 72.

94 When the repair is complete the repairer issues a tax invoice at 75 and payment is assessed 76 and either declined 77 or authorised 78. If the payment is authorised the repairer is paid and the claim system updated. If payment is declined the repairer is notified and has three options. The first option is to vary the authorised amount of 5 repair using the quote message at 80. The quote is assessed at 81 and a new quote authority is given at 82. If the authorised repair total now equals the original Tax Invoice, the initial invoice may be reactivated at 84 and resubmitted for assessment. Alternatively, the repairer may issue an adjustment note with a changed payment amount at 83. 10 It will be appreciated by persons skilled in the art that numerous variations and/or modifications may be made to the invention as shown in the specific embodiments without departing from the spirit or scope of the invention as broadly described. The present embodiments are, therefore, to be considered in all respects as illustrative and 15 not restrictive.

Claims (37)

1. A quotation data exchange for the control of an insurance repair process, including: 5 a host computer operating to enable communications between an insurer and a repairer where the communications are selected from a set of electronic messages having predetermined content fields in which data is entered, the message set including: a scope of works message, sent from insurer to repairer, containing details of the accident, insurance and vehicle information, expected repair details and vehicle images; 10 a quotation sent between repairer and insurer for repair of the damage specified in the scope of works message and including details of the repair, quote items and a status in respect of the quote; a tax invoice (request for payment) from repairer to insurer in respect of an authorised repair; 15 a payment authority from insurer to repairer in response to a request for payment.

2. A quotation data exchange according to claim 1, wherein the quotation contains a request for an inspection from repairer to insurer to cause the insurer to inspect the 20 damage.

3. A quotation data exchange according to claim 1 or 2, wherein the quotation contains settlement information in respect of the specified repair. 25

4. A quotation data exchange according to any of claims 1, 2 or 3 wherein the message set includes a further tax invoice (payment request) in the form of an adjustment note or a re-activate invoice based on a previously communicated tax invoice. 30

5. A quotation data exchange according to any of claims I to 4, wherein the message set includes a cancel job message from insurer to repairer at any time after a request for quotation has been received by the repairer.

6. A quotation data exchange according to any of claims 1 to 5, wherein the 35 message set includes a decline payment message from insurer to repairer upon receipt of any tax invoice (request for payment). 96

7. A quotation data exchange according to any of claims 1 to 6, wherein the message set includes a decline job message from the repairer upon receipt of a request for quotation, and once included into the message set, prevents the communication of 5 further messages in relation to the specified damage.

8. A quotation data exchange according to any of claims I to 7, wherein the message set includes an error message from either the insurer or repairer on the receipt of any message containing invalid fields or is received in an invalid sequence. 10

9. A quotation data exchange according to claim 1, wherein the host computer resides at the insurer's premises, and the system will typically involve a communications network, such as the Internet, and remote computers that reside at the multiple repairer's premises. 15

10. A quotation data exchange according to claim 9, wherein the host and remote computers contain relational databases in which their respective quotation data is stored. 20

11. A quotation data exchange according to claim 10, wherein the data collected and stored within the relational database is used to populate the messages before transmission.

12. A quotation data exchange according to any of claims 1 to 11, wherein the 25 predetermined content fields for each message are expressed in a specific implementation of eXtensible Markup Language (XML).

13. A quotation data exchange according to any of claims 1 to 12, wherein syntactical facilities of the predetermined content fields are described in an XML 30 Schema Definition (xsd) that is a de-normalised data definition that contains syntax and nesting of elements such that complex relationships and data categorisation of the target relational database are implied in the message and the Document Type Definition defines each message, mandatory fields, field grouping, limited data reference sets and allowable values. 35 97

14. A quotation data exchange according to claim 13, wherein the syntactical facilities within the XML Schema Definition (xsd) are translated to predefined identifying tags that surround each specific occurrence of a message and individual fields during transmission. 5

15. A method for controlling an insurance repair process using a quotation data exchange according to claim 1, comprising the steps of: entering and storing the required quotation information into an insurer's computer system in response to a claim; 10 sending a scope of works message, from insurer to repairer, containing details of the accident, insurance and vehicle information, expected repair details and vehicle images; that is automatically populated with stored quotation information in respect of specified damage; receiving a quotation for the repair of the specified damage; 15 automatically retrieving information contained within the quotation and storing the information on the insurer's computer system; sending further scope of works message that is automatically populated with quotation information stored on the insurer's computer system, that may or may not contain an authority to proceed with the repair; 20 receiving a tax invoice (request for payment) in respect of an authorised repair; automatically retrieving information contained within the tax invoice (request for payment) and storing the information on the insurer's computer system; sending a payment authority in response to a request for payment that is automatically populated with quotation information stored on the insurer's computer 25 system.

16. A method for controlling an insurance repair process according to claim 15, further comprising the step of inspecting the damage upon receiving such a request from the repairer within the quotation. 30

17. A method for controlling an insurance repair process according to claim 15 or 16, further comprising the step of including settlement information in the quotation.

18. A method for controlling an insurance repair process according to claim 15, 16 35 or 17, further comprising the step of sending or receiving a total loss request, 98 automatically retrieving information contained within the total loss request and storing the information on the insurer's computer system.

19. A method for controlling an insurance repair process according to any of claims 5 15 to 18, further comprising the step of receiving an additional tax invoice (payment request) in the form of an adjustment note or re-activate invoice, automatically retrieving information contained within the additional tax invoice (request for payment) and storing the information on the insurer's computer system. 10

20. A method for controlling an insurance repair process according to any of claims 15 to 19, further comprising the step of withdrawing authority at any time after a quotation has been sent containing an authority.

21. A method for controlling an insurance repair process according to any of claims 15 15 to 20, further comprising the step of cancelling a job at any time after a request for quotation has been received by the repairer.

22. A method for controlling an insurance repair process according to any of claims 15 to 21, further comprising the step of declining a payment upon receipt of any tax 20 invoice (request for payment).

23. A method for controlling an insurance repair process according to any of claims 15 to 22, further comprising the step of receiving a decline job message from the repairer and sending the request for quotation to an alternate repairer. 25

24. A method for controlling an insurance repair process according to any of claims 15 to 23, further comprising the step of receiving or sending an error message based on any message containing invalid fields or is delivered in an invalid sequence. 30

25. A protocol for the control of an insurance repair process to be employed by a computer operating to enable the exchange of electronic communication between an insurer and repairer, the protocol defining the following message set having predetermined content fields in which data is entered: a scope of works message, sent from insurer to repairer, containing details of the 35 accident, insurance and vehicle information, expected repair details and vehicle images; 99 a quotation sent between repairer and insurer for repair of the damage specified in the scope of works message and including details of the repair, quote items and a status in respect of the quote; a tax invoice (request for payment) from repairer to insurer in respect of an 5 authorised repair.

26. A protocol for the control of an insurance repair process according to claim 25, wherein the protocol is expressed in a specific implementation of eXtensible Markup Language (XML) containing syntactical facilities for mandatory fields, field grouping 10 and allowable values for the specific set of allowable messages within the transmissions.

27. A protocol for the control of an insurance repair process according to claim 25 or 26, wherein each message is described in a XML Schema Definition (xsd) detailing the 15 syntax and nesting of each element including limited data reference sets and allowable values for each element and its attributes.

28. A protocol for the control of an insurance repair process according to claim 25, 26 or 27, wherein each message is regulated during transmission through the use of 20 predefined tags that enclose each message and each specific occurrence of a field contained within a message transmission.

29. A protocol for the control of an insurance repair process according to any of claims 25 to 28, wherein the possible transmission order of the allowable messages is 25 predefined.

30. A protocol for the control of an insurance repair process according to any of claims 25 to 29, wherein the status in respect of the quote is selected from a list including "quoted", "repair authorised" and "repair not authorised". 30

31. A quotation data exchange according to any of claims 1 to 14, wherein the status in respect of the quote is selected from a list including "quoted", "repair authorised" and "repair not authorised". 35

32. A quotation data exchange according to any of claims I to 14, as substantially herein described with reference to the accompanying drawings. 100

33. A method of controlling an insurance repair process according to any of claims 15 to 24, as substantially herein described with reference to the accompanying drawings. 5

34. A protocol for the control of an insurance repair process according to any of claims 25 to 30, as substantially herein described with reference to the accompanying drawings. 10

35. A quotation data exchange substantially as hereinbefore described with reference to the accompanying Figs. 1 to 3.

36. A method for controlling an insurance repair process substantially as hereinbefore described with reference to the accompanying Figs. I to 3. 15

37. A protocol for the control of an insurance repair process substantially as hereinbefore described with reference to the accompanying Figs. I to 3.