Before you open RPD
Confirm the reporting organisation, producer size and period first. Use the current GOV.UK reporting-file specification because accepted fields and codes can change. Assign a person who can make the declaration and keep their approval with the final file.
Large producer file
Includes organisation data and detailed packaging rows for the relevant half-year period.
Small producer file
Uses the small-producer structure and annual reporting route.
RPD walkthrough
This walkthrough shows the service screens and submission flow. Check the current GOV.UK specification alongside the video because Defra can update the service.
Build the reporting file
| Check | Action | Common failure |
|---|---|---|
| Header | Use the exact fields in the current specification | Old template or renamed column |
| Period | Select the code for the data being reported | Dates do not match the code |
| Classification | Use accepted activity, type, class, material and nation codes | Labels used instead of codes |
| Mass | Aggregate source records into the required unit | Grams entered where kg is expected |
| RAM | Use the accepted rating where required | Missing evidence or wrong RAM year |
Resolve errors before submission
Run structural checks for required columns, accepted codes, number formats and blank mandatory values. Then check impossible category combinations, duplicate rows and RAM gaps. A valid file can still contain the wrong tonnage, so reconcile totals against sales, purchasing and import records.
Submit and archive
- Upload the controlled file through RPD.
- Review service warnings and rejected records.
- Correct source data before generating a replacement.
- Complete the declaration with the authorised approver.
- Save the file, confirmation, reconciliation and correction log.
Error triage table
| Error type | Likely cause | Fix at source |
|---|---|---|
| Unknown code | Outdated mapping or free text | Update the controlled code table |
| Missing value | Incomplete product record | Assign it to the data owner |
| Unexpected total | Duplicate join, wrong unit or period | Reconcile by SKU and month |
| RAM gap | Missing component detail | Collect evidence and complete the assessment |
Remedy EPR automates data imports and report preparation, detects missing fields and inconsistent classifications, and keeps corrections with the reporting record.
Reconcile before upload
Compare packaging quantities with the sales, import or purchasing source that drives them. Review totals by material and activity, then compare the result with the previous reporting period. Explain movements caused by new products, corrected weights or classification changes.
| Reconciliation | Expected result | Investigate |
|---|---|---|
| Order coverage | Every in-scope transaction matches a product version | Unknown SKU or date gap |
| Packaging mass | Units multiplied by approved component weights | Duplicate join or wrong unit |
| Material bridge | Movement agrees with products and volumes | Unexpected category shift |
| File total | Generated rows equal approved working totals | Aggregation or rounding difference |
Control corrections and resubmissions
Correct the packaging record or transaction mapping that caused the error. Do not edit only the upload file, because the next report will recreate the same problem. Generate a new controlled version and retain the rejected file.
Record the reason, affected rows, change owner and approval. Check the current RPD guidance before resubmitting and preserve the new service confirmation with the original submission history.
Prepare accurate EPR reports without rebuilding spreadsheets
Remedy EPR automates data imports and calculations, detects compliance errors and keeps evidence ready for review.
Use the current GOV.UK reporting-file specification and reporting deadlines.