For the majority of transactions recorded as non weighed over a weighbridge or at facilities without a weighbridge the resulting transaction will show the 0 for either weights or just the tare weight. The Regulatory system would use this tare weight to determine when to report a deemed load. The tare weight must be 0 and hence why the follow are reported correctly in the detailed data file.

Standard hotkey over a weighbridge will show 0 for both weights.

Transaction at a deeming non weighbridge facility where a weighed product is used and stored tares are turned off. The deemed weight is recorded as gross but the tare will always be 0. This includes to ticket weights but one of them is zero.

Non weighed transaction processed over a weighbridge. Nominal weight of the tyres is recorded as a gross weight but the tare will always be 0.

The majority of scenarios that result in an incorrectly reported deemed transaction are based on the use of the Always Use Weight Conv setting on the vehicle record (see below). This setting tells ticketing to use the deemed weight for a transaction regardless of it the product is weighed or non weighed. This would mean if the vehicle had a weighed product and the deemed weight was 5t then the price would be charged against this weight. Additional if a weighbridge is connected and there is weight on the bridge then that weight will be captured as the tare weight and the deemed weight added to it to make the gross weight.

This is the same hotkey used in the Reported Correctly section but with the Always Use Weigh Conv setting active. In this case the transaction has a gross weight and also a tare weight greater than 0. This means the Regulatory system will not try and report this transaction as a deemed load. The resulting net weight is the deemed weight for the load and will therefore not impact your QWDS summary reporting and subsequently levy liability. This issue only impacts how the data is reported in the detailed data file. This transaction would look as follows in a detailed data file.

Removing the Always Use Weight Conv will ensure that transactions recorded against the vehicle won't appear incorrectly in the detailed data file. The Regulatory system will try and calculate the deemed weight if no deemed weight is recorded in the transaction but if you still wish to have the gross weight set to the deemed weight, which will result in the transaction having a net weight equal to the deemed weight but will still be reported correctly, then you will need to make sure your site is configured to Always Capture Deemed Weight for Non Weighed Tickets. This is a setting available in Configuration Manager and if you would like assistance with this then please contact the application support team.

In order to assist customers with this issue the Regulatory Management system is being changed so that it will no longer use a 0 tare weight to determine if a deemed weigh would be recorded. Instead is will look at the number of non zero ticket weights. If there is more than 1 non zero ticket weights recorded against the transaction then the transaction will assumed to have been weighed over a bridge and will therefore be reported as weighed. If there is 1 or no non-zero ticket weights then the system will report the transaction as deemed.

With this change in place you would not need to remove the Always Use Weigh Conv setting from your vehicles as no ticket weights are recorded in these scenarios or if they do there is only one non zero weight.

Even with the change to the Regulatory Management system there will still be one scenario where a transaction could be reported as weighed instead of deemed. If you have a non weighbridge site setup to use stored tares recorded against a vehicle, then its possible for a deemed transaction to have 2 non zero ticket weights.

The vehicle in this transaction had a stored tare and the system has then added the deemed weight to get a gross weight. However instead of have one of these recorded with a 0 tare and 0 ticket weight the system has recorded 2 non zero ticket weights. In order to prevent this scenario the use of stored tares should be tuned off at the site. This can be done through configuration manager and if you need assistance with this then please reach out the the application support team.