Defra's receipt-of-waste guidance requires a report within two working days from the day after the waste is received. Sites need a workflow that exposes incomplete records early enough to meet that deadline.
How the reporting window works
The official guidance states that waste receipts must be reported within two working days from the day after receipt. The exact calculation can be affected by weekends and public holidays, so operational teams should use the current Defra guidance as the authority for individual cases.
The safest approach is not to treat two working days as an administrative target. Capture the full record at the point of receipt and send an eligible record promptly, leaving time to resolve exceptions before the legal deadline.
Where delays usually begin
Delay often starts with missing reference information rather than the API itself. A vehicle arrives with an unfamiliar carrier, the source address is incomplete, the waste description is too vague or the operational system uses a code that is not mapped to the required reporting value.
If those gaps are discovered only during a later batch process, the compliance team inherits a backlog. Pre-validation at the movement stage gives the operator an opportunity to correct information while the driver and paperwork are still available.
Build a visible exception queue
Every unsent or rejected record should have an owner, a reason and a next action. Teams need to distinguish a record waiting for normal submission from one that cannot be sent, one rejected by the service and one changed after it was previously accepted.
A dashboard should show ageing as well as volume. The practical priority is the record closest to its deadline, not simply the oldest ticket number or the latest error message.
Retain the audit trail
Keep the submission date, response, identifier, corrections and later resubmissions connected to the original operational movement. This reduces the work required to explain what happened and supports internal review.
Merlinium Connect is designed to make the submission pipeline and exceptions visible while keeping the response with the underlying record. The exact connection route is agreed against the existing system and site process.
Practical checklist
Actions to take
- Capture complete receipt information at the point of movement
- Validate before the record enters a submission queue
- Show unsent, rejected and changed records separately
- Prioritise exceptions by reporting deadline
- Assign an owner and next action
- Retain every response and correction
Common questions
What operators ask
Does the two-day period start on the receipt date?
Defra guidance describes the deadline as two working days from the day after the waste is received. Check the official guidance for the precise calculation.
Should sites wait and submit in batches?
The service may support different operational routes, but delaying complete records unnecessarily reduces the time available to resolve errors.
What if Defra rejects a record?
The reason should remain visible, the underlying data should be corrected and the response history retained with the original movement.
Official sources and review note
This guide was last reviewed on 12 August 2026. Official guidance remains the source of truth and may change as the service develops.
Defra: Digital Waste Tracking serviceDefra: Report receipt of waste