Defra Waste Tracking API Integration: How to Tell If Your Skip Hire Software Actually Works
Updated

Phase 1 reporting is live for permitted and licensed receiving sites in England and Wales. When choosing software, check what its DEFRA connection actually supports and how your team will verify accepted reports.
An internal digital WTN, a product roadmap and an accepted government receipt report are different things. A software demonstration should make those distinctions clear.
Confirm the Phase Before Testing a Connection
- 1 October 2026 — live: Permitted and licensed receiving sites in England and Wales must report in-scope waste receipts.
- 1 January 2027: The receiving-site requirement follows in Scotland and Northern Ireland.
- Spring 2027 — planned: Public beta for waste collectors, including carriers, brokers and dealers.
- October 2027 — planned: Mandatory use for those collectors.
See the government rollout timetable for the current dates. A business can have both receiving-site and collector responsibilities. Do not assume that the later collector phase postpones an obligation at your own permitted yard.
A receiving-site API connection does not prove that collector reporting is live. Ask a provider which role, location and waste scenarios its product supports today.
Check Production Approval
DEFRA's software-provider guidance explains that API products must meet the reporting requirements and pass production approval tests. Some providers have exemptions for particular scenarios, so check whether the product covers the waste your site receives.
Look up the product on the official list and ask the provider about supported scenarios. Then confirm that your organisation and site have been configured for the production service. Being listed does not configure an individual customer's connection automatically.
Five Checks for the Actual Workflow
1. Required Information
Use the current receipt specification and guidance to check waste details, carrier and origin information, quantities and site identification. Test how staff see missing or invalid fields before submission.
2. Submission and Acceptance
Ask the provider to explain how a receipt moves from a local record to a submission and an accepted service response. The system should let staff identify records still waiting, rejected records and accepted references without confusing those states.
Use an appropriate test environment for demonstrations. Only submit real production receipts through an authorised, configured site workflow; demonstration screenshots are not evidence of your own reporting.
3. Errors and Corrections
Check who sees a validation failure and who is responsible for correcting it. Ask how the system handles amendments, avoids duplicate reporting and records the history of changes.
4. Interruptions and Outstanding Reports
Ask how service interruptions, retries and pending submissions appear to staff. A local record waiting to synchronise has not necessarily reached DEFRA. Keep source records and follow current government service guidance if reporting is interrupted.
5. Records and Retrieval
Check how you retrieve receipt details, accepted references and supporting documentation for a particular load. Keep the WTNs and other documents required alongside reporting.
Reporting Methods and Timing
Receiving sites must submit in-scope receipts within two working days, starting on the day after receipt. Check the receiving-site guidance for the activities, waste types and exceptions that apply to your operation. Waste exemption holders are outside Phase 1, and household waste recycling centres have specific rules.
The service accepts the government spreadsheet upload or software connected to its API. See how to report receipt of waste. If you choose software, check production approval and any exemptions for scenarios your site handles.
Continue waste transfer notes, hazardous waste consignment notes, Annex VII forms and permit returns where required. Phase 1 reporting runs alongside that documentation. Paper WTNs have not been banned by the launch; electronic WTNs are an operational choice subject to the same duty-of-care requirements.
A spreadsheet can be a supported reporting route. An API is an option for integrating software with the government service; it is not the only route available to every receiving site.
PaperRoute Skips and PaperRoute
PaperRoute Skips runs on PaperRoute, which DEFRA lists as compatible software for reporting receipt of waste. You can check the official software-provider list, where PaperRoute appears under Saunders Simmons Ltd.
For an eligible receiving site, we configure and check its connection before live reporting. The waste-receipts table and receipt register bring together the waste details, field checks and reporting status so staff can review what needs attention. Check the service response and keep accepted references with the source records.
Digital WTNs remain part of the job workflow and are separate from receipt reports. Collector reporting is a later phase; generating a WTN or completing a collection does not itself mean a collector report has been sent to DEFRA.
PaperRoute Skips also keeps digital WTNs, job information and driver records together. Those operational records support the workflow, but are distinct from a statutory submission.
Questions for Your Provider
- Which phase and waste scenarios does the connection support today?
- Has the product passed production approval, and are there any relevant exemptions?
- Is our receiving site configured for production reporting?
- How do staff distinguish pending, rejected and accepted reports?
- Who handles corrections and monitors outstanding submissions?
- How do we retrieve source records and acceptance references?
Book a demonstration to review the PaperRoute Skips receiving-site workflow. For the wider timetable and obligations, read our Digital Waste Tracking guide.