Reconcile waste dispatches with vendor records before closing the period
Match each physical waste movement to its dispatch, receipt and supporting vendor records before adding statement totals. Keep the quantity, material and date differences visible. A paid invoice confirms a commercial transaction; it may leave the waste quantity or final treatment unresolved.
This guide is for reporting, procurement and EHS teams checking waste documentation. It assumes the waste stream already has an identity and an appropriate classification review. The task here is to connect records and resolve mismatches, not to classify or handle the material.
Define the question the documents must answer
Decide whether you are checking waste generated, dispatched from the site, received by another facility or directed to a documented recovery or disposal operation. These are different events. Give the reconciliation a site boundary, period, stream list and quantity basis.
GRI 306: Waste 2020 addresses third-party management checks and data processes under 306-2(b)/(c). Guidance for 306-3(b) recognises that generated and managed weights can differ. No individual document automatically satisfies a disclosure.
Ask the responsible specialist which authorisations, transfer documents and destination evidence apply to the actual stream and location. Keep those checks alongside the numerical reconciliation. This guide does not replace the site's legal or technical compliance review.
Match movements before matching totals
Start from the site movement list. Give each dispatch a unique ID linked to its stream, date, vehicle or container reference where available, and site record.
Find the corresponding receipt. Compare supplier references, movement dates, material descriptions and quantities. One invoice may cover several loads, while one load may appear in several documents.
Keep both measurement bases. Record site and receiver weights separately, with gross, tare and net values where used. Preserve original units and any wet/dry basis stated.
Identify duplicate entries. Mark repeated statement lines or reissued documents against the original movement. Retain the reference so the adjustment can be reviewed.
Investigate differences. Ask for the specific weighing, timing, correction or routing evidence needed. Do not average incompatible weights merely to close a row.
Record the reporting decision. Name the accepted quantity basis, its evidence and the reviewer, or leave a bounded question open.
A useful reconciliation row contains movement ID, stream ID, dispatch date, site net weight, receipt date, receiver weight, invoice/statement references, difference, explanation, destination evidence status and reviewer decision. This is an optional working aid, not a replacement for a required statutory document.
A fictional duplicate and an unresolved weight difference
A site has two dispatches during the month. D-01 records 1,000 kg and D-02 records 500 kg, giving a site total of 1,500 kg. The receiver records 980 kg against D-01 and 500 kg against D-02.
The vendor's monthly statement contains three lines: 980 kg for D-01, 500 kg for D-02 and another 980 kg for D-01. Its apparent total is 2,460 kg. Suppose the reference check confirms that the last line repeats the first movement and is not a separate load.
Removing that confirmed duplicate gives 2,460 − 980 = 1,480 kg, matching the two receiver records. The remaining difference is 1,500 − 1,480 = 20 kg, all associated with D-01. The duplicate adjustment and the weight variance are separate issues.
The team retains both original weights and asks for the weighing basis and relevant correction records. It does not invent a moisture loss, choose the larger figure automatically or call the difference immaterial without a review basis. All values and documents in this example are fictional.
Neither 1,500 kg nor 1,480 kg is automatically the month's waste generated. That further calculation needs the applicable generation records, opening and closing stocks, transfers and other documented movements. The reconciliation has established a document relationship and one open variance.
Check what the destination record establishes
Keep collection, receipt and treatment evidence separately identifiable. If a record confirms that a collector received a load, describe that event accurately. A recovery claim needs suitable evidence for the claimed operation, scope and quantity, including downstream information where relevant.
Check whether a treatment statement covers your stream and reporting period, or merely describes the vendor's general activities. Record any quantity that is awaiting confirmation. An unanswered request is an evidence gap; it is not proof that the vendor acted improperly.
Close the period with an exception list
Before release, review movements spanning the period end, combined collections from several sites, reissued tickets and quantities reported in different units. Keep the date of generation, dispatch and treatment distinct so the reporting basis can be explained.
For each remaining mismatch, retain the affected quantity, missing evidence, responsible person and intended follow-up. Make approved adjustments traceable to the original document. If a later receipt changes a released figure, issue a controlled correction rather than silently replacing the earlier file.
Nitium's sustainability and GRI reporting support can help organise records, disclosure narrative and information gaps within an agreed scope. Discuss your waste evidence handover or email contact@nitium.in.
Reviewed 10 October 2026. Document reconciliation does not certify a vendor, establish lawful treatment or provide independent assurance. Site-specific compliance and physical handling decisions require their own qualified review.
Comments