This is the effective date of the record in question for a completed transaction is will be the Date Out, for an incomplete transaction the Date In will be presented, for any transaction where the operator aborted the transaction capture process the transactions time stamp will be presented.

This is the field that is used when setting the date filter for the export.

This is the system unique identification for the transaction and is set when the transaction capture process is first initiated by an operators.

Note: This is not the ticket number that appears on the dockets see Docket Number

Where a transaction was not aborted the docket number is the Ticket Number generated for the vehicles movements into the facility. This will be blank if the transaction was aborted by the operator.

This will be the code defined for the facility linked to either source location for outbound deliveries or the destination location for inbound deliveries. If the location does not have a facility allocated then the system will check for the next parent location with a facility defined and report that facility.

For single weigh transactions the In and Out Date/Time will be the same. For dual weigh situations the In Date/Time will be when the vehicle is first weighed and the Out Date/Time is when the transaction is complete.

Note: Any manually back dated tickets will display the date and time entered by the user.

For vehicles recorded in Mandalay this will be either the License Plate or the Actual License Plate field, if it exists, from the vehicle record. If a transactions was captured with a vehicle record set to 'record alternate license plate' then the license plate entered will be displayed.

This will display N/A if a weight was captured or will show the Vehicle Type allocated the vehicle used to record the transaction.

If the client used for a transaction is and account customer then the Name, Address and ABN fields will be populated with the details from the record in Mandalay. The billing address is used for the full address.

If the destination is an Other Waste Facility then the notes information recorded against the Facility item will be displayed. The notes recorded against the Facility should be the address for the facility recorded against the EPA license number.

The purpose of entry is a derived field based on the following rules:

• If Service Vehicle exemptions exists for transaction then Service Vehicle
• If Visitor exemption exists for transaction the Visitor
• If the transaction direction is outbound then Waste Removal
• If the transaction direction is inbound then Waste Delivery
• If the transaction is an internal movement (i.e. source and destination site ID are the same) then Internal Waste Movement (Note: This is provided for reconciliation purposes as internal movements are not required in the Benchmark Requirements.

If the destination is external or to another site then Out is displayed. If the source is external or from another site then In is displayed. If the transaction is an internal movement within the same site then N/A is displayed.

These field will show the transaction weight values captured. The Net weight is the Gross weight minus the tare weight. These fields are only populate for the main weighed product in a transaction any subsequent non weighed items included in the transaction will not include any values in these fields.

This value is the calculated net weigh for a non weighed product. It be calculated at the quantity x the product nominal weight value. It is not required by the EPA but is provided to assist with WARRP reporting reconciliation.

For the main weighed product the Adjusted Net represents the adjustment that occurred in the Mandalay Ticketing system when non weighed items with nominal weights are added to a transaction, to ensure the customers is not charged for the weight of separately charged items. For the non weighed products it will represent the nominal weigh calculation.

The sum of this value for all items on a ticket should equate to the Gross - Tare net weight calculation, however if the nominal weight for a non weighed product is larger than measured net weight then it will reporting as greater then the weighbridge measured net weight.

This field is the equivalent to the NettWeightTonnes value found through out the majority of Mandalay reporting systems. It has been provided to assist with the reconciliation of the WARRP summary report as this report uses this value as the reportable tonnes.

If a stored tare was used in a transaction then then Yes will be shown in the Stored Tare field. This will then result in the Last Tare date being populated in the Date Of Effect field.

If Service Vehicle or Visitor exemptions are active then N/A will be displayed, other wise the description of the product as recorded in Mandalay CS will be displayed.

This field is based on the Waste Type recorded against the transaction. Generally this will come from the setup of the product but potentially can just be applied by the operator.

If a levy exemption is recorded then N/A will be displayed, this includes the Service and Visitor exemptions.

This field is based on the Waste Stream recorded against the transaction except in the following scenarios

• The transaction is a Service Vehicle or Visitor then N/A is displayed.
• Its an approved operational usage then it will be shown as Record Not Reportable (RNR).
• The Waste Type is N/A then N/A is displayed.
• The transaction has come from another waste facility and the waste stream is neither CI, CD or MSW then the system will display the Other Waste Facility code (OWF).

If the Waste Stream is Municipal then the Sub Stream collected against the transaction is shown otherwise N/A is shown.

This will be the short name or full name of the destination and source locations for the transaction item being reported. The full name will be used if no short name exists for the location. If the destination or source location is external and it has an EPL number recorded then the name and address recorded against the facility category created for the other facility, will be reported.

For waste leaving

For all outbound transaction the system will display the destination purpose code set against the destination location. This could be either Recycling, Re-Use, Disposal or Recovery. If the transaction item has no destination purpose recorded against it then the parent locations will be recursively searched for one. If no code is found then the field will show N/A

If a transaction is destined (for outbound) or sourced (for inbound) from a location with a Facility configured then the code will be displayed. Otherwise N/A will be used.

If either the first weigh or second weigh were manually entered rather than captured from the weighbridge then Yes will be displayed otherwise No.

If the transaction is reported as a manual entry then the time stamp recorded against the transaction will be displayed.

The approval code recorded against a levy exemption or the EPA Permit value of the contract recorded against the transaction.. This will generally be a DIN number for approved usages or an EPA approval number for Community Services.

This shows either Yes or No:

No

• Canceled incomplete ticket that has been replaced.
• Incomplete ticket.
• Canceled ticket
• Internal movements (source and destination within the same site)

Yes

• Canceled or incomplete transaction that has not been replaced.
• All other transactions.

The Mandalay system does not currently keep track of your levy liability so this value will be returned as blank.

This field will show the following options:

• Reversed - If the ticket was reversed
• Reversal - if the ticket is the reversal transaction.
• Incomplete Canceled - An incomplete ticket that was canceled but was not replaced.
• Replaced - An incomplete ticket that was canceled and has been replaced.
• Canceled - The ticket was Canceled.
• No - If the transaction is active but incomplete (no Date Out recorded)
• Yes - If not covered by the above options.

If a transaction has been replaced or is the replacement for an other transaction then then comments field will provide information on this including any notes collected when the operator recorded the event.

This field will provide any information related to events captured for a transaction. E.g. notes for a replaced ticket event. It will also identify if the transaction is the result of the operator aborting the transaction.

This field will show the date and time the record for this transaction was recorded. It can help with identifying backdated or corrected transactions.