Key takeaway
A corrected manifest and a reconciled shipment are separate evidence states.
Separate the shipment from its versions
A hazardous-waste archive often contains a shipment identifier, signed shipping quantity, facility receipt and later corrections. A downstream reviewer needs to know which event each value represents. Replacing the original quantity with the latest corrected value can hide why staff investigated a discrepancy or whether the material actually arrived as described. Start by reconstructing the version chain rather than accepting the most recent export as the entire record.
EPA's e-Manifest guidance distinguishes submitted-data corrections from receipt certification. Its FAQ states that corrections retain an audit history and do not change separate discrepancy-reporting responsibilities. The original signed information and subsequent corrections can both matter. This guide concerns US manifest evidence as checked on 10 October 2026. Applicable facility, generator, transporter, waste and state requirements still need a responsible compliance review.
Work the discrepancy without inventing its cause
In this hypothetical shipment H17, the signed record shows 1,000 kilograms of one bulk waste stream and ten drums of another. The receiving record shows 880 kilograms and nine drums. The bulk difference is 120 kilograms, or 12% of the shipping quantity; the drum difference is one container. These are arithmetic observations. They do not establish leakage, fraud, weighing error or the actual legal reporting consequence.
The shipping party later submits a correction citing a newly located scale ticket. A reviewer should retain its reason, supporting evidence, author and certification history. The presence of that correction does not establish that the receiving measurements were wrong or that a required discrepancy process was completed. A separate compliance owner resolves what must be investigated or reported under the applicable rules. Keep that determination beside the arithmetic rather than deriving it from an export's corrected flag.
| Evidence layer | Illustrative H17 observation | Review result |
|---|---|---|
| Signed bulk shipping value | 1,000 kg | Original basis retained |
| Final receipt bulk value | 880 kg | 120 kg difference; cause unresolved |
| Container counts | 10 shipped; 9 received | One-container difference remains separate |
| Later correction | New scale-ticket reference recorded | Evidence and certification need review |
| Reporting and resolution | No linked decision retained | Do not label case closed |
Create a field-level correction ledger
For each changed field, retain the prior value, replacement value, reason, correction time and supporting document reference. Identify whether the party changed its own information, corrected another field using the permitted process or merely attached an internal comment. Keep an internal data-quality ticket separate from an actual submitted correction. A ticket marked complete is not evidence that the regulated record changed.
Validate waste-stream identity, quantity units, container measures and the parties before comparing totals. Gross and net weights, different units or an aggregated export can create an apparent difference that the underlying records explain. Preserve the original observations even after normalization. If the archive lacks a unit or waste-line relationship, classify the comparison as unavailable instead of substituting zero or distributing totals across lines.
Keep reporting evidence beside the operational status
Build a reconciliation row that links the manifest version chain, actual receipt evidence, internal investigation, the compliance decision and any applicable submitted report. Distinguish a receipt discrepancy from a missing returned manifest or other exception. They answer different questions and should not share a generic resolved status without an explanation.
For H17, the completed internal review stops at unresolved receipt differences because neither the cause nor the reporting decision is supported in the fictional archive. The next action is to obtain those records from the authorized compliance owner. It is not to change the quantity so two systems agree. A later supported resolution becomes another dated event; the historical discrepancy remains visible to someone studying process failures or correction timing.
Describe coverage before sharing a manifest
The useful deliverable is a period-level count of linked signed records, certified receipts, corrections and unresolved decisions, with a small internal sample replay. Specify whether the archive includes rejected loads, alternate facilities and corrected versions. Those are coverage questions, not evidence of a buyer's appetite for hazardous-waste data. Facility relationships, precise locations and waste profiles may also reveal commercially sensitive operations.
Inventory can record the event categories; Rights & privacy review can identify agreement and disclosure questions. Use a fictional version chain for an initial conversation. VOID charges no upfront seller referral fee and may receive conditional compensation from a receiving program. Permission must name the recipient and metadata scope. Sending a real manifest, enabling evaluation and licensing the archive each require their own decision; recordkeeping access does not establish permission for commercial redistribution.