How do I correct transactions incorrectly categorised for regulatory reporting?
During the regulatory submission process it may become necessary to change the classification for a number of transactions. This can be for various reasons like:
- Incorrect vehicle setup
- Incorrect product setup
- Incorrect location setup
Setting up a vehicle, product or location incorrectly could impact the way a transaction is recorded at the weigh bridge. If the issues is not identified immediately then a number of transaction could be recorded incorrectly. The existing Mandalay CS Submission module in Administration has a feature that can make correcting these issues relatively easy.
This guide explains how to use the bulk ticket editing feature in Mandalay CS.
Submissions in Administration
The Mandalay CS Administration has a tab available to central administration users, that has historically been used to manage the QLD Regulatory Levy submissions since the introduction of the original levy in 2011. With the new QLD levy implementation in 2019 the submission process will move to a new naus application called Regulatory Management. However, one of the main features of this section of the system is to allow the correction of the regulatory classification of a transaction and if necessary multiple transactions. Since this functionality will not initially be available in the new naus application it will be necessary to use this existing feature in submission will still be required.
For customers in NSW it is also possible to utilise this feature for correcting NSW OEH data classification mistakes.
To use the bulk transaction editing feature a submission record must first be created. Use the following steps to setup submission for bulk transaction editing usage.
- Press the Add button
- Set the submission type (see the Submission Types section below for details on the correct submission to use)
- The start and end date will default to a submission period. The dates set are not important if you are just bulk editing transactions so they can stay as they are.
- Press the apply button
Submission Types
Since the release of 3.6.3.x a new submission type called Generic has been made available. This submission type is recommended for all users as other submission types will update all transactions since the date of the specific legislation introduction, which could be 5 years worth of transactions in some cases.. The generic Submission Type will just affect transactions within the date range of the submission.
Editing a Transaction
To edit a transaction's regulatory classification you will need to use the ticket number as displayed ticket history, including any revision number (e.g. 739-LF.2).
Select a submission from the list and then enter a ticket number in the Ticket Number field in the Edit Transaction section of the submission tab.
Pres edit to open up the ticket editor.
Missing or incorrect classifications should be replaced with valid data presented in the drop downs. This data will be from the current regulatory data pack deployed to your database.
Select apply once all the corrections have been made.
Bulk Changes
After pressing apply the system will scan the data base for other transactions that matched the key data in the transaction and then present options for applying a bulk change to all transaction after the effective date for the submission type (see submission type section above for more details)
You do not need to pick all options but reviewing all the suggestions is recommend as it may reduce instances of of errors. The end of the listed option shows the number of transactions that are expected to be updated as part of this change.
Auditing
At this stage the bulk editing process does not contain any auditing and all transactions edited directly. However it will only affect regulatory classification data. No pricing or business specific data is affected when making corrections with this process.
Naus Regulatory Management Users
If you are using the Naus Regulatory Management to generate submissions you should be aware that the bulk update process should only be used to adjust transactions for the submission period you are currently trying to generate. Changing transactions form previous submission period will not trigger an update to be submitted in the submissions, only a transaction replacement can trigger an update to a previously submission transaction.