API or Spreadsheet? Choosing How You Submit to DEFRA’s Digital Waste Tracking Service

Quick Answer: GOV.UK allows two routes for reporting to the report receipt of waste service: submitting through receipt of waste API software or completing and uploading a spreadsheet. Neither route is automatically “better”. The right choice depends on your movement volumes, your systems and, above all, whether you keep a structured, auditable source record behind whichever route you choose.

From 1 October 2026, permitted and licensed waste sites in England and Wales must report the waste they receive digitally through DEFRA’s report receipt of waste service, with Northern Ireland and Scotland following from 1 January 2027. That leaves operations and document control teams with one practical decision to make now: do you submit via receipt of waste API software or spreadsheet upload?

This article compares both routes honestly and shows why the submission method matters less than the quality of the record behind it.

What Is the Report Receipt of Waste Service?

The report receipt of waste service is DEFRA’s digital waste tracking system for recording waste movements arriving at permitted or licensed receiving sites. Reporting becomes mandatory for sites in England and Wales from 1 October 2026, and for Northern Ireland and Scotland from 1 January 2027, according to GOV.UK guidance published in 2026.

Under the service, each waste movement arriving at a receiving site must be reported digitally. GOV.UK’s guidance specifies exactly two ways to do this: using an application programming interface (API) or completing and uploading a spreadsheet. You are not locked into one method exclusively either: GOV.UK confirms you can submit using a combination of both routes, which matters if, for example, one of your sites already runs connected software while another does not yet.

The receipt of waste data is the same either way. It includes waste descriptions, hazardous waste codes (called Special Waste Codes in Scotland), disposal or recovery codes, carrier details and quantities. The routes differ only in how that data travels from your site to DEFRA.

The Two Routes at a Glance

Two mechanical details are worth knowing before you commit to either route. DEFRA’s spreadsheet must be used exactly as provided: you cannot submit your own format or modify the template’s structure. It also works as a single-use batch rather than a running log, so once a spreadsheet has been submitted, the next movement goes into a fresh copy rather than being appended to the same file.

When Can Spreadsheet Submission Work Well?

Spreadsheet upload is a legitimate route sanctioned by GOV.UK and, for many receiving sites, the sensible choice; it deserves a fair assessment rather than treatment as the “lesser” option.

Spreadsheet submission tends to work well when:

• Movement volumes are modest. A site receiving a handful of loads per day can prepare and upload a spreadsheet in minutes. Building or buying API integration for that volume is hard to justify.
• Your waste streams are consistent. If the same carriers deliver the same waste types on a predictable schedule, most fields barely change between reports. The manual overhead stays small.
• You have no existing site software to connect. The API route assumes a system on your side generating receipt data; if your records live in a weighbridge notebook and a shared drive, there is nothing yet for an API to connect to.
• You want to start simply. The regulations set a reporting obligation, not a technology mandate. Starting with spreadsheets and moving to API submission later is a reasonable path, particularly while the API remains in beta.

There is no compliance penalty for choosing it: a correctly completed spreadsheet upload satisfies the obligation just as an API submission does.

Where the Spreadsheet Route Breaks Down

The spreadsheet route strains under volume, complexity and human error, largely because of manual re-keying, which becomes difficult to manage at scale.

The pressure points are predictable:

• Volume. A transfer station handling dozens of movements a day turns spreadsheet preparation into a daily job, and every row typed or copied by hand is another chance to transpose a code or misread a ticket.
• Multiple sites. Separate reporting by each site multiplies the manual workload and fragments oversight, so head office loses a single view of what has been submitted.
• Timeliness. DEFRA’s policy expectation is that a record reaches the service within two working days of the waste being received. Data prepared in batches at the end of the day or week comes close to that limit even when nothing goes wrong, and reconciling the spreadsheet against weighbridge tickets and transfer documentation adds a separate task before submission.
• Corrections. When an upload is rejected or a field is wrong, someone must trace the error back to its source, fix it and resubmit. Without a controlled source record, “back to source” often means returning to an email thread.

The spreadsheet route is still valid, but it has a ceiling. Each operator should assess honestly how close they already are to it.

What Does Receipt of Waste API Software Actually Involve?

Receipt of waste API software is any system that has integrated with DEFRA’s Receipt of Waste API, passed the production approval tests, and can submit waste receipt records directly to the service. GOV.UK maintains a published list of compatible providers and products.

Based on DEFRA’s developer documentation for the current public beta, the API route involves:

• Registration and API codes. After onboarding, receivers receive an API code that uniquely identifies their organization. They share this code with their software provider, which uses it to indicate the operator for which each record is being reported.
• OAuth 2.0 authentication. The submitting software system authenticates using OAuth 2.0. DEFRA’s FAQs state that on-premises deployments without a connection to a centralized company API each need their own credentials.
• Per-record validation. The core POST endpoint creates a record for a waste movement arriving at a receiving site and returns a waste tracking ID with a validation result. GET endpoints retrieve reference lists such as hazardous waste codes and disposal or recovery codes.
• Production approval tests. Before submitting live records, software must pass DEFRA’s production approval tests, which comprise 14 test scenarios at the time of writing. GOV.UK lists two requirements for compatible software: integration with the receipt of waste service API and successful completion of these tests. Some providers carry exemptions for specific scenarios, such as certain hazardous waste movements, so confirm exactly what a prospective provider is certified to handle rather than assuming full coverage.
• Operational limits. The documented soft rate limit is 200 hits per second. Free-text fields such as waste description have a maximum length of 5,000 characters.

If you choose this route, you are effectively choosing a software provider. GOV.UK’s compatible provider list already includes weighbridge, ERP and waste management platforms, and the right fit depends on the systems already operating at your gate.

The Real Question: Where Does Your Source Record Live?

Whichever submission route you choose, compliance depends on a structured, controlled source record behind it. The API-versus-spreadsheet debate often overlooks this point.

Both routes share the same dependency: the spreadsheet must be populated from somewhere, and the API software must receive its data from somewhere. The underlying inputs are the same either way: weighbridge tickets, waste transfer notes, carrier registration details, permits, quantities and codes. If those inputs live in inboxes, paper trays and personal drives, the submission route cannot fix the problem. A clean API pipeline fed by messy records produces confidently submitted errors; a spreadsheet built from messy records produces the same errors more slowly.

A structured source record means:

• Every waste receipt document is captured in one controlled system, with metadata such as site, carrier, waste code and date that makes it findable in seconds instead of minutes.
• Versions and changes are tracked, so a corrected quantity or amended code leaves a visible trail without silently overwriting the original.
• An audit trail records who touched what and when. This matters as soon as a regulator or internal reviewer asks how a submitted figure was derived.
• Retention rules keep records for the required period and flag them when that period ends.

This is document control discipline, the same discipline that separates registers that pass audits from those that prolong them. The approach we describe for maintaining an ISO document register that passes every audit applies almost unchanged to waste receipt documentation: one authoritative record, controlled changes and evidence on demand.

How Folderit Supports Either Submission Route

Folderit is a document management system that gives waste operators the structured source record both submission routes depend on. It is also listed on GOV.UK as a compatible software provider for the Report Receipt of Waste service, so it can submit records to DEFRA through the API and keep the returned Waste Tracking ID with each one. It does not replace a weighbridge system or other waste-specific operational software.

For spreadsheet users, Folderit’s eForms let staff record receipt details in defined fields rather than free-form notes, keeping the data feeding your upload template consistent from day one; metadata search means the transfer note behind any submitted row is retrievable without digging through folders.

For teams using or moving towards the API route, Folderit can be the submitting software: an authorised user reviews the structured record and sends it to the Digital Waste Tracking service from Folderit. Teams that already use another provider’s software still benefit, because the fields the API expects already exist in their records rather than needing reconstruction.

Across both routes, Folderit provides the document management compliance foundations required for regulated record-keeping: audit trails on every document and folder, version control, granular access permissions, approval workflows and automated retention periods. Some waste operators also run site systems locally, so Folderit is available as a cloud or on-premises deployment; our glossary entry on hybrid storage (cloud and on-prem) explains the trade-offs.

Folderit is deliberately simple to run, which matters here. Digital waste tracking adds an administrative obligation for teams that already have full days. The source record system should reduce that load without creating a second implementation project alongside your submission software. See how Folderit supports DEFRA Digital Waste Tracking for the fuller picture of how the source record and submission routes fit together.

How to Decide: A Short Checklist

This checklist is scoped to the submission-route decision only. For the fuller pre-deadline readiness process, covering permits, carrier checks and internal training, see our guide on how to prepare for UK digital waste tracking.

Work through these questions with your operations and document control leads:

1. How many movements do you receive per day, per site? Under roughly ten consistent movements a day, spreadsheets are usually workable; well beyond that, manual preparation becomes a standing cost.
2. Do you already run software at the gate? If a weighbridge or waste management system captures receipt data today, check whether your provider appears on GOV.UK’s compatible software list before considering anything new.
3. Can you trace any submitted figure back to its source document in under a minute? If not, fix the source record first; it matters more than the submission route.
4. Who corrects errors, and how? Define the correction workflow now, including how you will preserve both the original and amended records.
5. What happens when guidance changes? The API is in public beta, and requirements may shift. Choose arrangements for either route that you can adjust without starting over.

FAQs

Which software providers offer digital waste tracking software?

GOV.UK publishes a list of compatible software providers whose products have integrated with the receipt of waste API and passed the production approval tests. It includes weighbridge, ERP and waste management platforms such as AMCS Platform, Weighman 8 and WasteMatrix, with new providers added as they complete approval.

Can I use Excel to report receipt of waste instead of an API?

Yes. GOV.UK confirms two approved routes: API submission or completing and uploading a spreadsheet. The spreadsheet route fully satisfies the reporting obligation and suits sites with lower movement volumes. It becomes harder to sustain as daily volumes and site counts grow because staff must prepare every record manually.

How do I prepare waste receipt records for digital reporting?

Capture each movement’s details, including waste codes, carrier, quantity and disposal or recovery codes, in a structured, controlled system as the waste arrives, so nothing needs reconstructing later. Keep supporting documents such as transfer notes attached to the record, with version control and an audit trail, so you can provide evidence for any submitted figure on demand.

When does digital waste tracking become mandatory?

Permitted or licensed sites in England and Wales must report waste receipts digitally from 1 October 2026, according to GOV.UK guidance. In Northern Ireland and Scotland, the requirement takes effect from 1 January 2027. Both the API and spreadsheet routes are accepted from those dates.

Is Folderit right for managing digital waste tracking records?

Folderit suits waste operators that need a controlled source record behind their submissions, whichever route they use, with eForms for structured capture, metadata search, audit trails, approval workflows, retention automation and cloud or on-premises deployment. It can submit Receipt of Waste records to DEFRA directly, or sit alongside another provider’s submission software.