The portal has been available since 1 July 2017.
Practitioners have been encouraged to commence entering data into the Portal from 1 July 2017. Entering data from this date will develop familiarity with new practices prior to mandating of the data collection, however it is acknowledged that this may not be feasible for all practitioners immediately from 1 July 2017. Therefore, practitioners will have the option of either accessing the Portal to provide additional data or continue to only provide existing data through RevNet.
From 4 September 2017 the additional Portal data will become a pre-requisite for the purchaser’s representative when stamping a self-determination document via RevNet.
Once legislative amendments have been passed reporting of information in the Portal for both vendors and purchasers will be required.
These key dates and how they impact on both purchaser and vendor requirements to access the data are represented in the table below. Refer to the Commonwealth Reporting Data Fields to determine what fields will be mandatory in the Portal once you are required to access the Portal based on this table.
|Date||Portal Data Requirement (based on role)|
|1 July 2017||Purchaser: Optional||Vendor: Optional|
|4 September 2017||Purchaser: Mandatory||Vendor: Optional|
|1 January 2018 (TBC)||Purchaser: Mandatory||Vendor: Mandatory|
All real property transactions. Please refer to the following list of RevNet documents that are impacted by the new data requirements:
RevNet users will be automatically prompted by the system upon selecting a relevant document.
Please refer to the following document for a list of required data:
Much of the new information is provided by an individual to their conveyancing agent as part of the Verification of Identity (VOI) process.
Data will be reported by the person conducting the transaction. For example, where a conveyancing agent (or similar representative) is employed, the agent will report the data. If a party is self-representing, they will report the data.
Existing RevNet Stamp Duty clients can log into the Portal using their existing RevNet credentials:
If you are not an existing RevNet user then you can register for the Portal online:
Agents will commence entering data into the Portal before accessing RevNet. The nature of some data lends itself to being captured, and entered into the Portal, around the time of VOI. Information which is not known at this point in time can be added or edited at a later date.
Once your Portal data is finalised you would follow the existing RevNet process: create a batch, add a document, complete the document details, calculate the duty, stamp the document, end and submit the batch.
Confirmation of the batch would immediately lock some Portal data from being added/edited. The locked data will be any data related to duty calculation, such as consideration and document date.
All Portal data will be locked from editing seven days after the provided settlement date. Amendments required after such time must be submitted to RevenueSA.
See Can details be added or modified after a workspace is submitted? for more details of when fields are locked.
RevNet batches and documents, stamping and payment remains unchanged. Only the purchaser’s agent is required to submit transaction details via RevNet.
No, the nine-day batch expiry will continue to work as it currently operates. Reporting of data via the Portal should not impact the RevNet batch process. Practitioners can commence and finalise the Portal data entry as soon as practical in the settlement process.
Upon completion of the purchaser’s data entry, the portal will send the vendor’s agent an invitation, via email, to provide the data into the workspace for the vendor. From 4 September 2017 this will not be required to be completed and the purchaser’s agent can complete their stamping in RevNet without the additional information. If the legislation is passed to mandate the additional data then it will be a requirement that the vendor provide this data prior to stamping.
The scheduled settlement date should act as an incentive for both parties to fulfil their obligations to provide all data that is required. The Portal will be flexible to allow this data collection to commence as early in the settlement process as either party wishes to initiate it. RevenueSA will build functionality to remind both parties (the complying and non-complying) that there is incomplete data.
Under extenuating circumstances whereby the purchaser cannot complete the stamping due to non-compliance of the vendor to provide the data, the Commissioner can exercise discretion in relation to the collection of the vendor’s data and allow the purchaser to stamp the document. Such cases would be followed up with the vendor’s agent as post-settlement Compliance activities. This will not be an issue until 1 January 2018 but RevenueSA would expect the overwhelming majority of transactions to be compliant by this time if the enabling legislation is passed. RevenueSA will endeavour to make this transition as easy as possible for practitioners and taxpayers.
To ensure complete data either party to a transaction will be able to initiate the Portal data collection process. Upon completion of the data in the Portal a user will invite the other party to complete the data that relates to their role.
Invitations will be generated from the Portal and sent via email.
RevenueSA believes that flexibility in this process is a key to a successful transition for practitioners and taxpayers.
The log in from the invitation process will match the two sides of the workspace together. In addition RevenueSA will perform a matching exercise in the event that both parties commence their data entry in the Portal independently.
The other party to the transaction or their agent will not be able to view your specific Portal client data.
The information is proposed to be used by the ATO for the purpose of information-matching and ensuring compliance with the taxation laws of the Commonwealth. In addition, the information (which will include information about the nationality and residency of vendors and purchasers) is to be used for the purposes of a National Register of Foreign Ownership of Land Titles to be administered by the ATO.
The ATO also intend to make this data available to taxpayers for prefill and preparation of returns and activity statements.
RevenueSA conduced a two webinars in July. A recording is available. You need to register your name and email to view the recording.
A number of self-paced tutorials are also available.
RevenueSA is replacing the existing RevNet platform with an integrated, modern, mobility friendly platform. This is planned to be implemented to coincide with the new legislative amendments, around 1 January 2018.
This solution will integrate the additional Commonwealth data collection with the processing of stamp duty documents, for Commissioner based assessments and self-determination documents. The Commissioner based opinions will be submitted electronically following the completion of all mandatory data and will be able to be stamped in your office. Legislative amendments, if successfully passed, will change the stamping requirements – removing the burden of using either the manual rubber stamps or ageing technology slip printers.
This process will ensure that all stamp duty transactions can be processed through eConveyancing, unlike the current eConveyancing process which is limited to self-determined RevNet documents.
As this stage of the implementation progresses, RevenueSA will continue to provide updates to practitioners and consult with them to ensure their requirements are met. Our goal is to deliver a fully integrated system for all stamp duty lodgments and in doing so make the process as automated and user friendly as possible.
If a document is voided in RevNet there is no requirement, or functionality, to void in the Portal.
If a document is voided in RevNet due to settlement being delayed, assuming no details other than date of settlement have changed, the same Workspace ID can be reused when the document is re-entered into RevNet. You should then return to the Workspace and modify the Settlement Date.
Details should be provided for the entity being registered on title. In a majority of circumstances that would be the trustee. In the scenario of a trustee purchasing on behalf of a trust the bulk of the data should be provided for the trustee: Trustee Name, Address for Future Notices, Contact Details etc. The only details required for the trust is Trust Name.
The below table indicates when fields are locked from editing in the Portal:
|Portal Fields||Locked from editing when the document is confirmed in RevNet||Locked form editing 7 days after settlement|
|Interest Transferred as a Percentage||X|
|New Building or Housing Indicator||X|
|Residential off-the-plan Purchase Indicator||X|
|Purchaser & Vendor Relationship: Related/Not Related||X|
|Property Type: Residential/Non-Residential||X|
|Purchaser/Vendor Details: all details of purchaser(s) and vendor (s) such as name, ABN, nationality, address etc.||X|
Note: Any changes required after settlement must be emailed to email@example.com
Not currently, however if the document transaction does not settle it will not be reported to the ATO. A request to delete Draft or Submitted Workspaces can be sent to firstname.lastname@example.org.
Data should be provided for the person(s) going on or off title where reasonable. For example, if a deceased vendor is returned on title you would enter the personal details of the deceased and contact details/address for futures notices of the executor.
This FAQs document will be updated as required. Please check back here periodically.
See our overview page of Commonwealth Reporting.
Contact Phone Number – RevNet Enquiries 08 8207 2333
Email – RevSupport@sa.gov.au
Draft Bill for these amendments
ATO resources relevant to the reporting initiative: