Mandalay CS 3.2Regulatory ReportingQueenslandHow do I implement version 4 of the QLD Levy DDF Specification?

How do I implement version 4 of the QLD Levy DDF Specification?

The QLD Department of Environment and Sciences (DES) has recently released a new version of the detailed data file specification that will take affect from the 1st of July 2022. The changes to the specification require the following new classification codes be used:

  • Waste Classes - RDRWC1 and RDRWC2 have been added to the specification and related to regulated waste as residue where a discount is available.
  • General Exemption - NIRC has been added for waste that has been received from Norfolk Island.
  • Waste Source - MLZ and RLZ have been added to allow the separation levy-able waste based on if the region the waste was source from was a Metro or Non Metro levied region.

The specification also includes the deprecation of the LZ code as this has now be split into the MLZ and RLZ codes.

Mandalay will deploy a new data pack for QLD and this data pack will include these new codes and will also mark the Levy Zone (LZ) Waste Source code as DEPRECATED. The LZ code does not need to be deactivated as the naus Regulatory system will ensure it is only used when valid.

Regulated Waste Residue Discount Waste Classes

The following is an excerpt from the new specification that explains the new waste classes.

It is Mandalay's understanding that these waste classes are only used in rare situations and for most Mandalay customers will not be relevant. However if you need to implement these waste classes then you can use the following method to ensure you data us classified to report transactions against these code.

The setup for these classifications is essentially the same as the existing Residue Waste Class (RESDISC) and will require both a waste class to be defined and an exemption with a valid exemption code.

Product Setup

Ensure a product is available for the specific waste movement that needs to be classified this way and then link the waste class as a favorite to the product.

Exemption

The product will also need to have an exemption applied to it. Any levy non general levy exemption event can be used but it is recommended that specific levy exemption event be created for the required waste category.

  1. Set the name of the event to be relevant to the waste class.
  2. Make sure to set the type to Levy Exemption.
  3. No default code is required as that will be set on the product.
  4. Leave these options as default.

Link this exemption to the product and apply the valid exemption code.

Norfolk Island General Exemption

The following is an excerpt from the new specification that explains the new general exemption.

The deployment of the new data pack will generate a new general levy exemption event that can be used against either a product, client or location to determine if a ticket should be considered exempt as the waste was received from Norfolk Island.

Metro and Regional Levy Zone Waste Sources

The following is an excerpt from the new specification that lists the new source codes.

These waste source codes relate specifically to waste received at a facility and therefore should only be applied to external locations.

Any external location that currently has the Levy Zone (LZ) as the Waste Source will need to be changed to either of these source code. The code that is used will be determine by regional the facility operates under. (Refer to DES for details on which code you should be using)

If you are in a location that could receive waste from either a Metro Levy Zone or a Regional Levy Zone then separate external locations will need to be defined and additional data setup required to allow the source to be easily set by an operator at the time of the transaction. Please contact Mandalay or Resource Hub for assistance if you feel you require this setup.