Do I need a weighbridge to comply with Digital Waste Tracking?

No — a weighbridge is not legally required to submit a Receipt of Waste. You need an accurate weight for each arriving load, but how you obtain it is up to you. Sites with a weighbridge naturally use it as the data capture point; smaller sites may use manifests or supplier-declared weights. What matters is that the weight and other required fields reach the DWT service within 48 hours of arrival.

Can I use my existing weighbridge software for Digital Waste Tracking?

Only if it can connect — directly or via bridging middleware — to the DEFRA Receipt of Waste API. Legacy weighbridge systems that produce only printed tickets or local spreadsheet exports will need either an upgrade or a bridging layer to push each completed transaction into the DWT service automatically.

What is weighbridge bridging software?

Weighbridge bridging software sits between your weighbridge management system and the Digital Waste Tracking API. It reads each completed weighbridge transaction, maps the fields to the Receipt of Waste data model, and submits the movement to DEFRA — returning a Waste Tracking ID that is stored against the original ticket. The goal is to avoid re-keying weighbridge data into a separate compliance portal.

What happens if my weighbridge ticket has the wrong EWC code?

DEFRA's DWT service validates each submission against the published European Waste Catalogue. If the EWC code is invalid or does not match the hazardous flag on the load, the submission is rejected and no Waste Tracking ID is returned. The receipt stays in a 'not submitted' state until the error is corrected and the movement is resubmitted — meaning a clean master list of EWC codes in your weighbridge system is critical.

Weighbridge tickets and waste records: getting receipt data right

Last updated 14 August 2026

In short

A weighbridge ticket is the gate-level record of each load arriving at a permitted waste site — capturing weight, EWC code, carrier and container type. From October 2026, the data on that ticket must flow into DEFRA's Digital Waste Tracking service as a Receipt of Waste within 48 hours of arrival. Getting the ticket data right at the point of capture is the fastest path to clean, compliant submissions.

At most permitted waste sites the weighbridge is where every arriving load is first measured and recorded. From October 2026 that moment doubles as the start of a Digital Waste Tracking submission — the data captured at the gate must reach DEFRA's service within 48 hours as a Receipt of Waste. Here is what the ticket must contain, how it maps to the DWT fields, and what to fix before the deadline.

What is a weighbridge ticket in the waste context?

A weighbridge ticket is the gate-level record printed or generated when a vehicle is weighed on arrival at a permitted waste site. It records the gross, tare and net weights alongside the load's key details — waste type, carrier, and vehicle — and acts as the primary source of truth for every Receipt of Waste submission.

For decades the weighbridge ticket served two purposes: an internal record for site management and a reference line on the invoice. From October 2026 it gains a third: it is the raw material for a statutory submission to DEFRA's Digital Waste Tracking service. Every field on the ticket that the DWT receipt requires must be correct at the point of capture, or the submission will fail validation.

What data must a weighbridge ticket capture for DWT compliance?

At minimum: the EWC code, net weight and unit, carrier name and registration number, a waste description, and the container or vehicle type. The disposal or recovery code (R-code or D-code) and arrival date and time are also required in the Receipt of Waste submission.

Weighbridge ticket fields mapped to Receipt of Waste requirements

Ticket field	DWT receipt field	Notes
EWC code(s)	Waste classification	Six-digit code from the European Waste Catalogue. Hazardous codes carry an asterisk (*). Must be valid — DWT rejects unrecognised codes.
Net weight & unit	Quantity received	Typically tonnes. How the weight was determined (weighbridge, estimate) is also recorded.
Waste description	Waste description	Plain language description alongside the EWC code. Brief but specific enough for a regulator to trace the material.
Carrier name	Carrier details	The company that delivered the load. Cross-referenced against the carrier registration number.
Carrier registration number	Carrier registration	The Environment Agency, SEPA, or NIEA waste carrier registration number. DWT validates this is an active, correctly-tiered registration.
Container / vehicle type	How received	Skip, bulk tipper, roll-on/roll-off, walking floor, drums, etc. Maps to the container type code in the DWT schema.
Date & time	Date of receipt	The arrival time the receipt is logged against; drives the 48-hour submission clock.
Disposal / recovery code	R-code or D-code	What the site will do with the waste. R-codes = recovery operations; D-codes = disposal. Required at submission.

Many sites already capture most of these fields informally. The shift Digital Waste Tracking demands is making every field structured and validated — not free-text that a person interprets later, but a code or value the API can check on arrival.

How does weighbridge data feed into a Receipt of Waste?

The weighbridge transaction completes, and the data — EWC code, weight, carrier, container type and disposal code — is submitted to the DEFRA Receipt of Waste API. DEFRA validates the fields and, if accepted, returns a Waste Tracking ID that is stored against the original ticket.

The submission path depends on how your site is set up:

Direct API integration — your weighbridge or site management software connects to the Receipt of Waste API. Each completed transaction is submitted automatically; the Waste Tracking ID comes back in seconds and is printed on the ticket or stored in the system. No re-keying, no portal login.
Bridging middleware — a bridging layer reads completed weighbridge transactions from your existing system (via export file, database query, or local API) and forwards them to DEFRA. Used when the weighbridge software cannot be upgraded to call the DWT API natively.
Manual portal entry — DEFRA provides a web portal for sites that cannot integrate programmatically. Operators re-enter each load's details manually. Workable for very low volumes; error-prone and slow at scale.

Every Receipt of Waste must be submitted to Digital Waste Tracking within 48 hours of the load arriving at the site. The 48-hour clock starts at the moment of receipt — not the end of the working day. Mandatory for receivers in England, Wales & Northern Ireland from 1 October 2026; Scotland from January 2027.

What are the most common data quality problems at the weighbridge?

The three most common causes of failed DWT submissions are: an incorrect or legacy EWC code, a missing or invalid carrier registration number, and a free-text container description that does not match a valid DWT container type code.

Each of these is a validation the DEFRA API applies on every submission. A rejected receipt stays in a 'not submitted' state until corrected — meaning the error must be found and fixed within the 48-hour window, or the site is in breach of the submission deadline.

EWC code errors — stale or incorrectly typed codes in the weighbridge system's lookup table. Fix: audit your EWC code list against the current 842-code catalogue before go-live and lock the field to a validated dropdown rather than free text.
Carrier registration mismatches — the carrier's registration number is missing from the ticket, recorded in the wrong format, or belongs to a lower-tier registration that doesn't cover the waste being moved. Fix: capture the registration at gate-in, not retrospectively, and verify against the public register.
Container type free text — weighbridge systems often store container descriptions as plain text ("skip", "tipper", "ro-ro"). The DWT schema uses coded values. Fix: map your existing container descriptions to the DWT container type codes in your bridging layer or software configuration before go-live.
Missing disposal or recovery code — R-codes and D-codes are rarely captured at the weighbridge today because they weren't needed on the ticket. From October 2026 they are required in the receipt. Fix: add an R/D code field to the weighbridge transaction screen and populate the default for each waste stream accepted at your site.

Do I need to replace my weighbridge software before October 2026?

Not necessarily. If your weighbridge system can export transaction data in a structured format (CSV, XML, database), a bridging layer can read those exports and submit them to the DWT API without replacing the core system. A full replacement is only needed if the system cannot be integrated at all.

This guide is general information about weighbridge data and Digital Waste Tracking, not legal or regulatory advice. Confirm your specific obligations with your environmental regulator (Environment Agency, SEPA, NIEA, or Natural Resources Wales) and the primary sources below.

Primary sources

Frequently asked questions

Do I need a weighbridge to comply with Digital Waste Tracking?: No — a weighbridge is not legally required to submit a Receipt of Waste. You need an accurate weight for each arriving load, but how you obtain it is up to you. Sites with a weighbridge naturally use it as the data capture point; smaller sites may use manifests or supplier-declared weights. What matters is that the weight and other required fields reach the DWT service within 48 hours of arrival.
What data must a weighbridge ticket capture for DWT compliance?: At minimum: the EWC code(s) for the waste, the net weight and unit of measurement, the carrier's name and waste carrier registration number, a waste description, and the container or vehicle type. Date and time of arrival and the disposal or recovery code (R-code or D-code) are also required in the Receipt of Waste submission.
Can I use my existing weighbridge software for Digital Waste Tracking?: Only if it can connect — directly or via bridging middleware — to the DEFRA Receipt of Waste API. Legacy weighbridge systems that produce only printed tickets or local spreadsheet exports will need either an upgrade or a bridging layer to push each completed transaction into the DWT service automatically.
What is weighbridge bridging software?: Weighbridge bridging software sits between your weighbridge management system and the Digital Waste Tracking API. It reads each completed weighbridge transaction, maps the fields to the Receipt of Waste data model, and submits the movement to DEFRA — returning a Waste Tracking ID that is stored against the original ticket. The goal is to avoid re-keying weighbridge data into a separate compliance portal.
What happens if my weighbridge ticket has the wrong EWC code?: DEFRA's DWT service validates each submission against the published European Waste Catalogue. If the EWC code is invalid or does not match the hazardous flag on the load, the submission is rejected and no Waste Tracking ID is returned. The receipt stays in a 'not submitted' state until the error is corrected and the movement is resubmitted — meaning a clean master list of EWC codes in your weighbridge system is critical.

Related guides

This guide is general information from ComplyWaste, not legal advice. Always check the primary sources for your situation.