Unregistered Registered Manually Registered Dead Registered Dead Cancelled General Law Easement Only Fee Farm Title Fee Simple (incl Share Titles) Life Title Leasehold Title Share Title Strata Unit Folio Text Historical Folio Folio Plan Schedule of Easements Survey Notes Short URDS Report Long Urds Report Change of By-Laws Council Certificate Other Council Document Torrens Dealing General Law Dealing Power of Attorney Dealing Notice of Sale Report Survey Information Report Folio Text for Common Lot Historical Folio 1-1115 Historical Purchase Grant Historical Folio 1116-4999 Unregistered Registered Dead Folio Dealing Notation Production Watch Sale Development "Acquisition" Unregistered Registered Manually Registered Dead Registered Dead Cancelled Sent by fax Attached file Sent by courier Email attachment Portable Network Graphics (PNG) Graphics Interchange Format (GIF) Joint Photographic Experts Group (JPEG) Save and lodge a dealing. Save the dealing (do not lodge). Joint Owners Tenants in Common Ownership defined by shares Schedule 1 Schedule 2 Unregistered Dealings and Notations Produced Held on behalf of client Dispatched Non-existent Search Folios Search Dealings Search Plans Ascending Descending Lodgement Register Remove Created Updated Deleted Created and/or updated Folio Notification identifier Folio LIST Client Folio Notification Type (eg Lodgement) Last Triggered date/time Summary of Changes Discontinued date/time An name identifying the notification to the client Date the notification is to commence Number of months the notification should be active How often should the we check for changes? Daily Weekly Monthly Dealing execution type code Dealing execution type title Text in the top (north) block Text in the left (west) block Text in the right (east) block Text in the bottom (south) block A legitimate value Sequence in relation to dealing-extra-type Code identifying an extra (i.e. additional) piece of information Dealing extra-type title Data-type e.g. string, number, date The Extra type Mandatory for encompassing dealing type? Maximum value for number data types Minimum value for number data types Dealing party-type code? Dealing party-type title? Can a name be supplied? Can an address be supplied? Can an occupation be supplied? Do we need to know in what capacity the party acts? The Party type Mandatory for encompassing dealing type? Dealing type code Dealing category code - used when creating PNs Dealing type (category) public title Section of Land Titles Act Current lodgement fee at time of request Has schedules? Has affected dealings? Has owner-shares? Has priority notices? Has extra name/value pairs? Has parties to the dealing? Has executions? Has attachments? Can dealings of this type be lodged electronically? Can dealings of this type be registered electronically? Field to order by Locality code Sequence in relation to folio Text describing one aspect of land parcel. When submitting Folio elements to TOLD (e.g. in specifying the title reference in a SubmitDealing service), you need only supply the Volume and Folio elements. For Share Titles, you must also supply the ShareNo; for ordinary titles, ShareNo defaults to zero. Any other elements may be supplied but will be ignored. Volume (plan) Folio (lot) First share, second etc Title type Folio status Edition Edition timestamp Location of Certificate of Title Unique, immutable identifier of Title Date on which the Title ceased to be valid Plan Number Previous Plan Number (for renumbered plans) Plan Type Dealing Type Surveyor Firm Surveyor Person Surveyor Reference Lot Count Status (tracking) Date lodged Date registered Location Type Date on which the Certificate's location changed Client who Produced the Certificate. Client for whom the Certificate has been Produced. Client on whose behalf the Certificate has been held. Client to whom the Certificate has been dispatched. Schedule number (1 for ownership etc). Schedule status Dealing number Dealing category BP number Client who lodged this BP. Lodgement timestamp Registration timestamp. Text appearing on a line of the folio of the register. The volume/folio this schedule relates to - only relevant for dealings. The dealing this schedule relates to - only relevant for folios. Schedule status - set to U for new dealings Schedule status in human-readable form Schedule number (1 for ownership etc). TODO Description of part of land (if any) TODO Registration timestamp. Timestamp for schedule ceasing to be current. Print sequence in relation to folio This dealing confers (or not) a Life Interest on this Title A PDF revision of a folio document. Document type code Document type description Number of pages (images only) Latest revision Revision date PDF of scanned images An activity that occurred in relation to this title. The entity that recorded the activity The entity type code (e.g. dealing type code). The entity type name (e.g. dealing type name). The business key of the entity that was affected. The status (description) of the entity that was affected. The time the activity occurred. A textual description of the activity. Proprietor (owner). Proprietor name/address TODO Fraction in text e.g. 1/2 - use 1 for total ownership Dealing no of dealing affected by this Sequencing of affected dealings Volume/folio for PN Category which PN relates Priority notice text Miscellaneous pieces of data required for form production, but not forming a permanent part of the register - basically key-value pairs. The key The value TODO Sequence in relation to dealing Party to a dealing - the role is determined by dealingPartyTypeCode. The role The participant type code Human-readable party type Party name/address Capacity in which party acts Sequence in relation to dealing An execution on the dealing by one of the parties. The type of execution For which party The top block of text The left block of text The right block of text The bottom block of text Sequence in relation to dealing An attachment to support a dealing or an indication that one is coming by some other means. Description of attachment Mode of delivery (e.g. fax) Type of attachment Name of file on TOLD machine Name of file on client machine Base64-encoded attachment Sequence in relation to dealing General Law Dealing details. Business Paper details. Invoice details. Search details. Product details. Plan Reference File Reference Map Reference A Tasmanian land dealing. dealing number allocated by TOLD dealing type dealing type description/title text dealing number or alternate dealing no dealing category code - more descriptive than type dealing status - set to U for new dealings dealing status - human-readable version Status (tracking) TODO check list output monetary consideration e.g. sale price type of ownership (joint, tenants in common etc) BP number allocated by TOLD Client reference for BP SRO Duty Assessment Number Lodgement timestamp for BP - set by TOLD. Registration timestamp Client who lodged this BP - set by TOLD. Dealing Category Finance One item code. Dealing Payment Status Dealing Fee Dealing Exception Reason Dispatch Number Security Code Last Dispatch Notice of Sale Notice of Sale Name of the Client dispatched to Dispatch Date and Time Notice of Sale Vendor Party Purchaser Address Purchaser ACN Date of Contract Date of Settlement Chattels Price Goodwill Price Non-Proportional? Whole of Land? Purchaser In Trust? Principal Residence? Comments NOS Status code NOS Status description Properties A PDF image of a Tasmanian land dealing. Document type code Document type description Number of pages (images only) Base64-encoded dealing image A PDF document containing plans, survey notes etc. Base64-encoded dealing image Survey Information Document. Document type code Document type description Number of pages (images only) Base64-encoded dealing image Provides identifiers and page counts for scanned plans and historical scanned plans Volume/Plan number Plan number of the 'child' plan that this one is historical to The number of pages of a scanned folio plan document (zero if no document exists) The number of pages of a scanned survey notes document (zero if no document exists) Document type code Number of pages (images only) Estimated number of bytes (images only) Data available as text in XML? Data available as PDF encoded in XML? Identifier of a related entity (such as Plan or Dealing No) Identifies this particular document within the response Document type code Data requested as text in XML? Data requested as PDF encoded in XML? Order by instruction Order by instruction Return result count only Indicates whether Certificate Location should be included in the response System Parameter Parameter Name String parameter value Date parameter value Numeric parameter value LIST Client Client Name LIST login Contact Name Debtor Name Client Name Fax Number Email Address Postal Address Control data for auto-generated datasets. Incrementing file sequence number. Creation date Is production data Include Torrens dealings Include GL dealings Include PoA dealings Include unpublished sales Include notices of sale Denotes a PurchasersIndex query Include prepared (saved) dealings that have not been lodged. Include dealings that have been lodged. Include only dealings that have been scanned. Include only dealings that are unregistered or have been recently registered. DEPRECATED - use ResultsInstructions element instead. Volume (plan). Start of folio (lot) range. End of folio (lot) range - defaults to FolioFrom. First share, second etc Dealing number of any dealing applied to the folio. Surname of current owner. Given name (or part of name) of current owner. Organisation name (e.g. company name) of current owner. DEPRECATED - use ResultsInstructions element instead. Vistas Property Id. Include Registered Folios Include Unregistered Folios Include Dead Folios Include only direct ownership in results Plan number - either old or new for renumbered plans Volume (plan). Start of folio (lot) range. Surveyor Firm Surveyor Person PID Street number of address Street name of address Street type of address Locality of address Invoice ID Client Code Date from which the invoice was created Date to which the invoice was created Invoice ID Client Name Date from which the search was created Date to which the search was created Selected Folio List of registered Plan References. List of unregistered Plan References. List of Survey Information Only References. List of Central Plan Office References. List of Deeds Office References. Add LIST branding to requested documents Required documents PDFs of scanned images Volume (plan) Folio (lot) First share, second etc Required documents Indicates whether Certificate Location should be included in the response Add LIST branding to requested documents Should we print a dead folio - if not throw a fault Folio - complete details PDFs of scanned images Extract timestamp Volume (plan) Folio (lot) First share, second etc Look for activity after this time timestamp The reason (i.e. business function) for which this request is being made. Has any activity occurred on this Folio since the FromDateTime? The timestamp of this response. In the next request, ActivityFromDateTime should be set to this value. A list of activities that occurred on the title. List Client Special Instructions URL to retrieve a map of the selected titles Ignore warnings - if false or unset, warnings will be returned as faults. Includes titles updated until this date. Use this date as the Since Date in the next request.