By WasteSignal · England, Scotland and Wales
On this page
When a digital waste tracking record fails or looks wrong, first establish what happened to that particular movement. An initial rejection, an uncertain submission result and a mistake found later need different handling. Keeping those cases separate helps the team find the right information and act within the applicable reporting period.
This guide offers practical advice for receiving organisations using the government’s receipt service, through software or the official spreadsheet. It complements the waste data and digital tracking guide and the workflow in how to report receipt of waste. Confirm your operation’s scope and national rules before applying a procedure.
As at 12 October 2026, the receiver requirement applies to in-scope facilities in England and Wales. Scotland’s first phase starts on 1 January 2027. The advice below distinguishes the published reporting rules from suggested internal controls, such as a correction log or daily review of unresolved records.
Is this a rejected submission or a later correction?
Find the movement’s result and any reference returned by the service. A local software record marked ready, queued or sent may describe a different stage from a confirmed government record. Ask the provider what its status labels mean if that is unclear. Preserve the response before changing or repeating the attempt. The official reporting guidance distinguishes errors identified during submission from errors discovered later in submitted information. An initial error must be corrected within the original two-working-day reporting period. A later-discovered error must be corrected as soon as possible and within one month of discovery.
An uncertain result deserves its own investigation. If the browser closed before displaying a response, you may not yet know whether the movement was created. Record what you attempted and when, then use the available service or provider support to establish the outcome. Do not label it rejected solely because your local screen failed to update.
Give the cases separate statuses in your working list, with a named owner. That lets a deputy see which records need completion, which need amendment and which need a result checked. Use plain explanations alongside any shorthand so colleagues can follow the queue without learning a private vocabulary from the person who created it.
What information should I keep when an error appears?
Record the local receipt reference and the relevant service reference, if one exists. Save the error wording or response in a form that lets support understand it. Include the time of the attempt and the reporting route used. A message saying the system failed, without a movement or result, gives the next person little to investigate.
Keep a connection to the source information. The investigator may need the arrival record, waste description or a particular supplier answer. Identify where those records are saved rather than copying unrelated attachments into every enquiry. Where several receipts are affected, create a movement list so the scope of the task stays clear.
Note the reporting deadline or, for a later error, when it was discovered. Assign an internal follow-up date that allows time for further questions. If the issue has already been passed to someone, record the recipient and the question asked. This avoids a second colleague starting the same enquiry without knowing that an answer is due.
Share information through an appropriate support route. Include enough detail to identify the fault, while keeping credentials and unrelated business information out of a general email. Follow your organisation’s policy for customer and supplier data. If support needs a file, establish which file they require and how it should be provided.
How do I investigate a missing or invalid field?
Read the error against the current service instructions or your provider’s documentation. Determine whether it concerns format, missing information or a value that does not fit the required field. Then return to the source record.
Editing the visible cell without establishing the correct information can replace a clear failure with a plausible-looking mistake.
For an identity question, check the actual party involved in the movement and its relationship to any brand shown on the paperwork. A carrier, broker and receiving operator perform different roles. If the records use inconsistent names, resolve the relationship before changing standing data. Our supplier checks guide explains those distinctions.
For quantities, verify the unit and whether the amount is actual or estimated. Check that a total has not been copied from several movements into one receipt. For dates, establish the actual arrival information rather than using the day an invoice was processed. Keep a note of any source discrepancy and who resolved it.
If the error concerns waste classification or specialist information, involve the colleague with the appropriate knowledge. The waste classification technical guidance provides the assessment framework. An available menu option is not evidence that a code fits the waste, and a form accepting a value does not settle a classification question.
Does correcting an initial error restart the reporting period?
The published instructions require initial submission errors to be corrected within the same two-working-day period, starting on the day after receipt. Plan the first attempt early enough to leave time for investigation. Our deadline guide explains how to organise working-day calculations and internal targets.
Review failure notifications when they arrive, including messages returned through connected software. Give the monitoring task to a named person and arrange cover. A process that sends failures to an unattended mailbox may leave the team unaware that its submitted file needs action while the original deadline continues to approach.
Escalate an unresolved issue with a precise summary. Identify the movement and the information needed, then tell the recipient when the answer is required for your reporting process. If a supplier cannot answer, keep the uncertainty visible and seek appropriate advice. Do not invent a value to close the work item.
When the problem is resolved, check the new result. Record the successful reference and connect it to the source receipt. A local change followed by another attempt does not establish the outcome until you inspect the response. If a further error appears, keep it with the same investigation so another colleague can understand the sequence.
How should I correct a mistake found after successful submission?
Identify the confirmed movement and the incorrect information, then establish the replacement value from a reliable source. Record when the error was discovered. The requirement to act as soon as possible means the one-month outer limit should not be treated as a routine delay before starting the work.
Follow the current service process or your software provider’s instructions for changing an existing record. For spreadsheets, the government guidance says an update requires a waste tracking reference for the movement. Keep that reference available and ask technical support if you cannot establish how the record should be amended.
Write a short correction note explaining the issue, its evidence and the completed action. You do not need an elaborate report for every typing error, but someone reviewing the movement should be able to understand why the current value differs from an earlier copy. Preserve the link to any supplier clarification used.
For a fictional receiving business, imagine that a confirmed receipt later turns out to contain an incorrect vehicle registration copied from a standing record. The administrator identifies the movement, obtains the correct source information and follows the amendment process. They also correct the standing record used for future loads, so resolving the historical entry does not leave the same error in place.
What if one mistake affects many receipts?
Establish how the error entered the process and what records may share it. A copied party reference or faulty mapping can affect more than the movement where the problem was first noticed. Use a defined period or source-data change to guide your review, and record the basis for the set you investigate.
Separate affected records from those checked and found correct. Keep a clear list of movements requiring action, with their references and progress. If several colleagues help, assign parts of the work explicitly. That prevents duplicate amendments and makes it easier to see what remains when someone is absent.
Ask the provider for help if the issue concerns how software transforms or maps data. Explain which source value was used and what appeared in the submitted record. Request an explanation of the cause and proposed fix. A promise that the latest screen looks right may leave previously submitted movements unresolved.
After correcting the affected records, check a new representative movement. Keep the historical correction task separate from the change intended to prevent recurrence. Our guide to checking waste data quality explains practical sampling and source checks that can help find a repeated problem earlier.
Should I upload the same file again after an error?
Check the outcome for the movements involved before deciding what to repeat. A batch may leave you with confirmed records and items still needing attention, depending on the response. Follow the service’s instructions for that result. If you cannot tell what was created, preserve the response and ask support how to proceed.
Keep the submitted copy identifiable and separate from a new working file. The government service page instructs users to start a new spreadsheet after submission. The guide to spreadsheet uploads explains file ownership and reconciliation without changing the required template format.
For API reporting, ask your provider how retries and duplicate detection work in the actual product. Staff should understand what happens after an interruption or an ambiguous response. Avoid manually repeating submissions while automated recovery is still running unless the provider’s procedure specifically calls for that action.
Reconcile the movements after recovery. The count of files sent is not enough: several attempts could concern the same receipts, while one omitted movement remains unreported. Compare confirmed references against the receipt list and keep unexplained gaps open until they are investigated. Record any duplicate problem for the appropriate correction or support process.
What if the service or our connection is down?
Distinguish the government service being unavailable from a local problem affecting your access. Retain outage notifications, support responses and the times recorded by your team. Contact the regulator where the applicable rules require it, and organise the receipt information needed for the outage record. Technical support and the regulator answer different questions.
Read the relevant national recovery provisions carefully. GOV.UK guidance describes transferring written records within seven working days after an outage, while the English regulations say seven days. SEPA’s Scottish guidance also uses seven days. Seek national regulator clarification where needed; do not apply an assumed universal Great Britain period.
Assign someone to maintain the temporary receipt list during the interruption. The list should connect each load to the required written information and show whether any earlier attempt has an uncertain result. Preserve the source records so they remain available when the team is ready to submit or reconcile them.
When service returns, check which movements still need reporting and which need their previous results established. Work through the recovery queue with confirmation at movement level. Keep the outage evidence and the completed recovery record together under your records policy, so a later enquiry can follow what happened without relying on staff memory.
Who should I contact for help?
For access or government-service problems, use the technical help route on the official service page. For faults in connected software, contact the provider with the relevant movement and response details. Questions about your reporting obligations or the application of national rules belong with the appropriate environmental regulator.
Make the question specific. Explain the country and facility involved, the receipt arrangement and the point you need clarified. A regulatory question about an outage period differs from a technical question about how to retrieve a response. Sending the same vague request to several teams can delay the answer you actually need.
Keep the support enquiry connected to the unresolved movement or batch. If advice changes the action required, record that clearly for the colleague carrying it out. Avoid treating an open support ticket as evidence that the reporting task is complete. Continue monitoring the issue and escalate through the relevant route when time is short.
For recurring software problems, ask for a documented procedure and test it with the reporting team. Read choosing digital waste tracking software when reviewing support arrangements or considering another product. The practical question is whether staff can recognise the problem and obtain useful help in time.
How can I reduce avoidable errors?
Review a small selection of receipts from source record to reporting result. Include a movement with an unusual feature that your operation genuinely handles. Ask where each value came from and whether another colleague could find the same evidence. That exercise can reveal a missing handover or unreliable standing value before it affects a larger batch.
Keep an issue list that records causes as well as individual fixes. If staff repeatedly ask the same supplier for a missing detail, improve the agreed information exchange. If errors arise from copied files, clarify which template or reference record should be used. Choose the improvement that addresses the actual cause.
Train deputies to handle errors, not only successful submissions. A fictional practice exercise can show whether they can identify a movement’s status, locate its source and decide whom to ask. Keep practice data separate from live reporting. Review the instructions when service requirements or local responsibilities change.
Continue checking existing movement documents and returns. Receipt reporting does not remove those obligations, and a correction may also reveal inconsistent information elsewhere in your records. Establish which other records need reviewing rather than assuming a digital amendment fixes everything automatically. Keep unresolved questions visible until the relevant work is completed.