By WasteSignal · England, Scotland and Wales
On this page
Reporting receipt of waste starts with the information recorded when the waste arrives. Your team needs to connect the actual load to the receiving facility and the people involved, then submit the required details and check the result. A reporting process should make those steps manageable during an ordinary working day.
This guide is for businesses organising receipt reporting at facilities within scope. It offers a practical workflow, without assuming that every business producing or collecting waste must upload its own collections. Confirm your role using who needs digital waste tracking, and read the waste data and digital tracking guide for the wider context.
As at 12 October 2026, in-scope receivers in England and Wales must report. Scotland’s first phase starts on 1 January 2027. Use the current national rules for your facility, including the applicable exclusions and any special arrangements. The organisational suggestions in this article can be adapted to your site; they do not replace those rules.
What should I check before setting up receipt reporting?
Identify the legal operator and receiving facility first. Establish the activity covered by its authorisation and the country in which the receipt takes place. Record why you consider it in scope, or the reason you need clarification. A brand name or a group-wide contract may not identify the organisation that must report a particular site’s receipts.
The official scope guidance describes the English and Welsh requirements. SEPA’s Scottish guidance explains the Scottish position. Read the detailed scope for your activity rather than assuming that any permission bearing the word waste creates an identical reporting duty.
List the receipt arrangements your team handles, including unusual ones. A regular vehicle delivery, a movement involving a broker and a piped receipt may require different questions. Record where the necessary information currently sits and who can explain it. This helps you organise the process around the actual operation instead of asking one administrator to interpret every unfamiliar load alone.
Before configuring software, agree the internal names used for the operator and site. Staff may use an old trading name for a facility while the official record uses a different legal name. Resolve that relationship and maintain a clear reference list. It can save repeated uncertainty when a colleague encounters unfamiliar wording in a submission or supplier document.
How do I access the government service?
Start from the government’s Report receipt of waste page. It explains registration and organisational account access. Follow its instructions for the organisation’s credentials rather than using a personal Government Gateway account. Keep account administration with an authorised colleague who understands which organisation is being registered. Decide who will manage access and who will perform routine reporting. These may be the same person in a small business, but provide cover for absence. Record the support route and the account owner in a location colleagues can find. Avoid making the only working procedure dependent on someone remembering how they registered months earlier.
Where an account covers several organisations, keep their operational responsibilities distinct. A person working across the group should know which organisation’s receipts they are handling at each stage. Check this during training with realistic examples, especially when two sites have similar names or the same administrative team processes both.
For software connections, follow the government’s instructions for the organisation’s API code and the provider’s setup process. Treat codes and access details as operational credentials: share them through the authorised route and keep them out of public documents. Ask the provider to demonstrate the correct organisation mapping before live reporting begins.
Should I use software or a spreadsheet?
The service offers an API route through compatible waste software and an official spreadsheet route. It also allows a combination. Choose a process you can operate reliably and reconcile; the existence of two routes should not result in the same receipts being sent twice by different colleagues.
For a small number of straightforward receipts, the spreadsheet may suit your immediate operation. A busier site may need software that connects existing weighbridge or administration records to reporting. Assess the work involved in gathering and checking the information, including corrections. Counting only the time taken to click an upload button can give a misleading estimate.
Ask the person doing the daily work to test the proposed process. Can they find the receipt information, identify anything missing and see the result afterwards? Include a colleague covering for them. A process that works for the supplier’s demonstrator may still need changes to fit your staffing and source records.
Our guides to spreadsheet uploads and choosing digital waste tracking software examine the alternatives. If you mix routes, write down which movements belong to each and how you will spot a duplicate. Review that allocation when a new site or software connection is added.
What information should the receiving team collect?
Use the specified information in the applicable regulations and the current service instructions as your checklist. The requirements cover the receiving facility and movement, the relevant parties and the waste. There are additional particulars for circumstances such as hazardous waste or persistent organic pollutants. Read digital waste tracking receipt information for a closer explanation of the data.
Make an information map before building a form. For each item, identify its source and the person who can answer a query. The site record may establish when the load arrived; supplier information may explain its origin and composition. Where a value comes from a standing record, establish when it needs checking again rather than copying it indefinitely.
Separate actual observations from estimates. Record the basis of a quantity so the reporting colleague can use it correctly, and keep the unit clear. An unexplained figure taken from an invoice may represent a chargeable amount or several deliveries. Investigate that difference before treating it as the quantity for a particular receipt.
Ask about missing information while the relevant people can still identify the delivery. A question raised promptly with a precise ticket reference is easier to answer than a general request at month end. Keep the answer connected to the receipt and update any standing instructions if the same gap affects future loads.
How should I check waste codes and specialist information?
Use the waste’s classification and supporting information. Do not select a code simply because it appears in a software menu or a site’s permit. The official waste classification guidance explains the assessment framework. Reporting a code accurately depends on the underlying classification being appropriate for the waste.
Give staff a route for questions outside their knowledge. If a delivery’s description conflicts with its code, someone needs to resolve the inconsistency. Record the question, ask the appropriate person for evidence and ensure the answer reaches the reporting team. A technically acceptable field format cannot settle a question about what the waste actually contains.
For Scottish operations, SEPA’s specified-information page describes details including hazardous properties and POPs information. Check the relevant national schedule for the actual movement.
Where rules require an explanation for unavailable information, make that explanation truthful and specific; do not use a stock phrase to avoid making reasonable enquiries.
Keep specialist source material identifiable. A laboratory report or classification assessment should be connected to the material it describes, including its scope. If the process producing the waste changes, ask whether the previous information still applies. Explain which assessment governs the load so the reporting colleague can select the appropriate information from the supporting documents.
What is a sensible daily reporting workflow?
Create a receipt list from the site’s operational records and check that every relevant arrival is represented. Assign a working reference that lets colleagues locate the source material. Add the reporting due date and identify any questions needing attention. The list can be simple, provided its status labels mean the same thing to everyone using it.
For ordinary receipts, the reporting period is two working days, starting on the day after receipt. Complete the submission and obtain its unique reference within that period; an initial validation failure needs correcting within the same window.
Review missing information early in the working day. Send specific enquiries and assign an owner for each unresolved point. If a question affects several movements, identify the affected records together. This prevents staff asking the same supplier several slightly different questions while an older receipt remains overlooked.
Prepare the submission through the chosen route, then inspect the response. Record the resulting reference against the movement and distinguish confirmed records from failures or uncertain results. A colleague should be able to follow the link from a receipt to its submitted record without relying on a filename that happens to contain the word final.
Before handing over, tell the next person which receipts remain open and why. Include any promised supplier response or support enquiry. Completed submissions can remain in the record, but the handover should make pending work easy to find. Our deadline guide explains how to fit that workflow around reporting periods.
How do I know the submission has succeeded?
Check the service or connected software result for the relevant movement. The English and Welsh guidance requires a unique reference within the reporting period. SEPA tells operators to check that the details were submitted correctly and that they received a digital waste record number. Keep that confirmation connected to your local receipt record.
Ask the software provider what each displayed status means. An item can be ready for sending locally without having reached the government service. A connection can return a response that still requires action. Staff should understand which status confirms success and which means they need to investigate, using the provider’s documented explanations.
If a result is ambiguous, preserve the response and seek help before resending. Identify the receipt, the time of the attempt and the route used. For batches, find out which records were confirmed and which remain unresolved, then compare those results with the movements you intended to report. Investigate any movement that still lacks a clear result.
A digital reference also has limits as evidence. It connects to a reporting event; it does not prove every statement in the underlying data or establish that a site was authorised for the waste. Continue digital tracking and supplier checks as a separate part of your waste arrangements.
What should I do if a record is rejected or wrong?
Distinguish an initial submission failure from a later error in a successfully submitted record. The initial failure needs resolving within the original reporting window. Later-discovered errors must be corrected as soon as possible and within one month of discovery under the published guidance. Keep the discovery date and issue description so the follow-up is clear.
Read an error message against the source information. If it identifies a missing or invalid value, find out what that value should be before changing it. Where the problem concerns a technical connection, involve the provider or service support. The colleague investigating the issue should record the result so another person does not repeat the same failed attempt.
For an outage, use the applicable national instructions. Government guidance and the English legislation describe the post-outage period differently, so obtain regulator clarification where necessary. Meanwhile, organise the required written information and preserve outage evidence. Our submission errors guide provides a practical way to manage the investigation and recovery queue.
Once resolved, consider whether the issue could recur. A corrected movement may leave a faulty standing record or software mapping unchanged. Assign that underlying improvement separately and check a later receipt to see whether it worked. Keep corrective actions proportionate to the problem; a clear local instruction may be enough for an isolated handover mistake.
Do transfer notes and waste returns still continue?
Yes. The current receipt-reporting arrangements run alongside existing documentation and returns. Follow the relevant requirements for transfer notes, consignment documents and other movement forms, and continue returns required by your authorisation. The official reporting guidance explains this continuing work.
Keep those activities visible in your procedure. If the same information feeds reporting and a return, staff may be able to reduce repeated typing, but each required output still needs checking. A saved receipt reference should not cause a colleague to assume the consignment paperwork or a separate return has been completed.
For a fictional receiving site, consider a load supported by several documents. The administration team identifies which information belongs to the digital entries and separately checks the required movement records. A handover records both results. If one task remains open, it stays visible even though the other has finished successfully.
Before signing off your setup, trace an ordinary receipt through the whole process with a colleague. Check its source, submission result and continuing documents. Repeat the exercise with an unfamiliar arrangement that your site genuinely handles. Use any gaps to improve the instructions, and keep the official links available for the person who will maintain them.
Review the first handover after a staff absence or responsibility change. Check whether the replacement colleague could find the open receipts and understand the next action without contacting someone on leave. If a source document or result was difficult to locate, improve its connection to the working list. A useful procedure should support the person who follows it occasionally as well as the administrator who knows every supplier by name.
Keep a dated record of important procedural changes, particularly where they follow regulator clarification. This helps colleagues identify which instructions apply to current work and which were used for earlier receipts.