How do I record non waste movements that are compatible with the QWDS 2019 reporting requirements?
The reporting requirements for the 2019 QLD Levy, require that non-waste movements be reported in certain circumstances. The Levy Detailed Data File Specification outlines the different non waste movements in Appendix J. This specification does not cover scenarios where an OSOP (On Site Operational Purpose) exemption is being claimed so for these scenarios you will need to refer to section 3.4.2 of the data file specification.
The following article explains how the different scenarios should be recorded in Mandalay CS for accurate reporting to the QLD Government.
UPDATE: April 2024 - 2 new Non Waste types are available for customers to use. These are Non Waste - Not Delivered and Non Waste - Machinery. These waste types will not be reported in the detailed data even if they are over 1 tonne. See the Visitors and Machinery sections for details. (Please contact the support team if required these new waste types)
Non Waste vs OSOP Exemption
The regulatory requirements around movement of material for use on site is a bit confusing. Specifically the movement of material to a levyable area for operational usage.
OSOP specific products are any waste material that will be used for operational purposes within the levyable area of the site and will be managed using the On-site Operational Use scenario. Waste material is deemed to be any material that a site did not financially purchase.
Any material that has been purchased for operational use and taken into the RRA or Levyable Area will be covered under the Non Waste scenarios.
On-site Operational Use
On-Site Operational use exemptions are recorded against a transaction when the waste product has been setup with a specific levy exemption. See this article for instructions on how to setup an approved levy exemption.
Site Access Transaction
With the release of version 3.6 of Mandalay CS, a new feature was added that allowed transactions that are being used for the sole purpose of accessing a site to be identified. See this 3.6 release notes for further information.
All transactions recorded against a product category with the Site Access flag will be ignored by the submission process. This means even if the net weight for the transaction is over a tonne it will be excluded. This can be helpful if large vehicles are accessing the site without being weighed and they do not fall into the reportable non waste categories.
Non Waste
Non Waste movements are separated into 3 distinct categories. Only one of these categories needs to be reported and then only if the net weight of the transaction is over 1 tonne.
A non waste transaction is any transaction where the Waste Stream, Waste Class and Material Type are all Non Waste and the Source or Destination is Non Waste - Levayable Waste Disposal Site or an RRA.
Visitors and Public Weigh (Not Delivered)
For vehicles that are entering the facilities and are not moving material then they can be considered a visitor. This also includes vehicles using any public weighbridge services.
Any non waste transaction in this category does not need to be measured or reported in the submission process and will be ignored by the Regulatory Management submission process.
A public weighbridge transaction recorded using the specific Public Weighbridge module in Mandalay CS will automatically be ignored by the submission generation process.
To ensure these transactions are not reported regardless of the net or deemed weight, the Non Waste - Not Delivered material type should be used.
To ensure you are aware of any case a transaction is not reported because its classified as non delivered, a warning message will be presented in the submission log file. This is is to ensure you are aware of any data setup that may be invalid and potentially making you in breach of the legislation.
Deliveries
Vehicles delivering non waste material to a facility will result in a net weight. If this net weight if over 1 tonne then it will need to be reported in the submission process. If the vehicle is not weighed then the deemed weight will be calculated and used to determine if the transaction should be reportable.
To ensure you are aware of any case a transaction is not reported because it doesn't meet the criteria, a warning message will be presented in the submission log file. This is is to ensure you are aware of any data setup that may be invalid and potentially making you in breach of the legislation.
Operational Machinery
Any movement of machinery, that is not transporting waste does not need to be reported in the submission process
To ensure these transactions are not reported regardless of the net or deemed weight, the Non Waste - Machinery material type should be used.
To ensure you are aware of any case a transaction is not reported because its classified as non delivered, a warning message will be presented in the submission log file. This is is to ensure you are aware of any data setup that may be invalid and potentially making you in breach of the legislation.
Deeming Non Waste Movements
The requirements for recording and reporting non waste movements allow for the use of deemed weights. However this will mean the deemed weight is used to determine if the net weight of the transaction is greater than the 1 tonne requirement for reporting non waste movements.
If recording visitors or operational machinery then you should be using the Site Access Transaction feature shown above. This non waste movement is completely ignored by the submission process and therefore the deemed weight will not matter. This is best for large vehicles accessing the site as a visitor or moving operational machinery, as they would generally have a deemed weight higher than 1 tonne.
Non Waste Fees and Charges
In some cases it may be necessary to add an additional cost on top of the charge for a waste product. E.G. Burial fees . These would be added to the ticket as an additional each item product. These products are configured like any other non waste product and have the waste class, stream and material type all set to Non Waste. The default source and destination should also be setup according to non waste requirements and have the destination set NW-LWDS or RRA.
As this is a product that has no actual weight the stock unit should be each and the nominal weight set to 0. Since the nominal weigh is zero the submission process will ignore these products in the transaction and will only report the waste products in the transaction. A previous process exists where some customers have been noted to have a small nominal weight against these fees of 0.01kg. Please remove the nominal weight in these instances.
End of Waste
Effective 1st of October 2022 a new material type of EOW (End of Waste) will be available to report on non waste movements out of the facility that meet the requirements for and End of Waste code as outlined here . When these movements are reported they will follow the existing non waste requirements of only reporting movements over a tonne. When these records are reported in the detailed data file the the valid code will need to be provided in the permit column.
To allow for this code to be reported in the DDF a Levy Exemption Event will need to be created and the applicable code applied to the product or location being used. See this article for details on how to setup product exemption.
The Regulatory system will check for the existence of a code and report an error if it is missing. It will not check if the code provided is valid, this will be performed by QWDS.
Below is an example of a Levy Exemption Even and product setup that will allow the EOW code to be reported.
Note: The code can either be added as default code to the levy exemption event or against the product.
