Over the past 12 months Mandalay has been working with the QLD Department of Environment and Science (DES), our customers and industry consultants to understand some of the concerns and areas of risk that have been raised during recent DES audits of facilities within the levy zone. Following these discussions, we have designed a set of updates that will be made to the naus Regulatory Management system to assist users in managing these risk areas.

The following provides a list of changes that we are planning to make within naus Regulatory Management. These updates will be delivered periodically with the first round of updates due to be released early in the New Year.

As each specific update is deployed, users will be advised through our standard fortnightly release notifications prior to an update being released. If you do not currently receive these emails please submit a support request and we will add you to the mailing list.

Refer below for a full list of planned updates.

To assist users with identifying possible errors, incorrect data entry or business processes which may need review we will be adding more validations to the submission process.

A warning will be raised in the submission log file for the following scenarios:

• Any deemed transaction is assigned the Disposed to Landfill destination code
• Any transaction with different destination codes. E.g. Landfill for material A and RRA for Material B.
• Any Asbestos transactions with an MSW waste stream and the Asbestos exemption is being claimed, will be reported as warning if the net weight of the load is over 175kg and no TCN has been provided.

An error will be raised in the submission log file for the following scenarios:

• Any Asbestos transactions with either CI or CS waste streams and the Asbestos exemption is being claimed will be reported as an error and require correction if there is no TCN recorded.
• Any site to site transfer where the source location is another site location and the resulting source code of RRA is used will be considered invalid and require adjustment. Currently DES requires this to be treated as an internal movement within the site and not as an inbound waste movement into the facility.

An information alert will be raised in the submission log file:

• When a waste class is transformed to EXGEN or EXAPP because an exemption has been recorded but the waste class recorded is not compatible with exemptions, an information alert will be reported.

Additionally all errors, warnings and information alerts will include the Date Out of the transaction.

Improvements to the submission processing workflow have bene designed in consultation with our customer base and feedback from DES. The following system improvements will be made:

• Any transactions with an exemption code that begins with RESE and the waste class is not EXAPP will have the waste class transformed to EXAPP. This currently occurs with other types of exemptions.
• Where a transaction includes both exempt and non-exempt material and was not part of a bulked up load process, the items will be rolled up to the non-exempt waste class as per the DES Detailed Data File specification (v4.1) where the transaction includes 2 different levy rates.
• Any transaction to an RRA that includes an exemption will not have the exemption reported in the detailed data file. This will not change the EXGEN or EXAPP waste classes if already defined on this product, which will mean that products should be set with the non-exempt waste class and allow the submission process to apply the correct exemption waste class if applicable.
• Where a transaction includes a waste material item and items that relate to a fee, the material type roll up will ignore the non-waste material type of the fee item.
• Bulked up load expansions that result in a 0 net weight for one of the items will not have that item reported in the detailed data file.
• Movements from Landfill to RRA will be reported in the detailed data file. Currently these are classed as internal movements and therefore ignored.
• Movements between 2 different RRAs on the same site will be reported in the detailed data file. Currently these are classed as internal movements and therefore ignored.

The naus Regulatory system was developed to assist customers in QLD in preparing and submitting their reporting obligations to the state regulator. We are continuing to work with our customers, industry consultants and DES to ensure emerging risk areas and changes in the legislative environment are incorporated into the naus Regulatory Management product. Please feel free to provide any feedback on other improvements to the naus Regulatory application.