Skip to main content

Movement Document Service

Movement documents are created per individual shipment within an approved notification. The notification must be in CONSENTED status before movements can be submitted.

🚀 DIWASS-Ready Software

Looking for shipment management software with built-in DIWASS integration? See Movemative.

Movement Document Lifecycle​

The following state diagram illustrates the movement document lifecycle.

SubmitMovementDocument​

Submits a movement document for an individual shipment under an approved notification.

Request (abbreviated)​

<SubmitMovementDocumentRequest>
  <notificationId>DIWASS-NOT-2026-HR-000123</notificationId>
  <movementDocument>
    <movementDocumentDueToTakeBack>false</movementDocumentDueToTakeBack>
    <movementDocumentsDueToIllegalActivity>false</movementDocumentsDueToIllegalActivity>
    <sequenceNumber>1</sequenceNumber>
    <actualDateOfShipment>2026-06-01</actualDateOfShipment>
    <actualQuantity>
      <massTonnes>3.5</massTonnes>
    </actualQuantity>
    <packageTypeCodes><code>DR</code></packageTypeCodes>
    <packageQuantity>4</packageQuantity>
    <specialHandlingRequired>true</specialHandlingRequired>
    <carrierPartyUUID>xxxxxxxx-...</carrierPartyUUID>
    <carrierOperatorInternalID>OP-55555</carrierOperatorInternalID>
    <carrierMeansOfTransportCode>T1</carrierMeansOfTransportCode>
    <notifierSignature>...</notifierSignature>
  </movementDocument>
</SubmitMovementDocumentRequest>

Response​

<SubmitMovementDocumentResponse>
  <movementId>MOV-DIWASS-2026-001</movementId>
  <movementReferenceId>MR-001</movementReferenceId>
  <status>SUBMITTED</status>
</SubmitMovementDocumentResponse>

SubmitCarrierTransfer​

Records a carrier-to-carrier handover during transit. Can be called multiple times per movement (multi-leg transport).

Request​

<SubmitCarrierTransferRequest>
  <movementId>MOV-DIWASS-2026-001</movementId>
  <carrierPartyUUID>yyyyyyyy-...</carrierPartyUUID>
  <carrierOperatorInternalID>OP-77777</carrierOperatorInternalID>
  <meansOfTransportCode>T1</meansOfTransportCode>
  <vehicleID>HR-AB-1234</vehicleID>
  <transferDate>2026-06-01T14:00:00Z</transferDate>
  <declarationCarrierPartyUUID>xxxxxxxx-...</declarationCarrierPartyUUID>
  <signature>...</signature>
  <attachmentIds/>
</SubmitCarrierTransferRequest>

Response​

<SubmitCarrierTransferResponse>
  <documentId>CT-DIWASS-001</documentId>
</SubmitCarrierTransferResponse>

SubmitConsigneeReceptionCertificate​

Submitted by the consignee upon receiving the waste at the destination.

Request​

<SubmitConsigneeReceptionCertificateRequest>
  <movementId>MOV-DIWASS-2026-001</movementId>
  <partyUUID>xxxxxxxx-...</partyUUID>
  <recipientPartyUUID>zzzzzzzz-...</recipientPartyUUID>
  <recipientOperatorInternalID>OP-88888</recipientOperatorInternalID>
  <receiptDate>2026-06-03</receiptDate>
  <signature>...</signature>
  <attachmentIds/>
</SubmitConsigneeReceptionCertificateRequest>

Response​

<SubmitConsigneeReceptionCertificateResponse>
  <documentId>CRC-DIWASS-001</documentId>
</SubmitConsigneeReceptionCertificateResponse>

SubmitFacilityReceptionCertificate​

Submitted by the treatment facility upon accepting waste, including quantity and classification confirmation.

Request (abbreviated)​

<SubmitFacilityReceptionCertificateRequest>
  <movementId>MOV-DIWASS-2026-001</movementId>
  <partyUUID>xxxxxxxx-...</partyUUID>
  <facilityTypeCode>R3</facilityTypeCode>
  <interimFacility>false</interimFacility>
  <actualSiteOfDisposalOrRecovery>true</actualSiteOfDisposalOrRecovery>
  <recoveryDisposalTypeCodes><code>R3</code></recoveryDisposalTypeCodes>
  <approximateDateOfProcess>2026-06-15</approximateDateOfProcess>
  <receiptDate>2026-06-03</receiptDate>
  <wasteClassifications>...</wasteClassifications>
  <recoveryDisposalDescription>...</recoveryDisposalDescription>
  <acceptedQuantity><massTonnes>3.5</massTonnes></acceptedQuantity>
  <rejectedQuantity><massTonnes>0</massTonnes></rejectedQuantity>
  <signature>...</signature>
  <attachmentIds/>
</SubmitFacilityReceptionCertificateRequest>

Response​

<SubmitFacilityReceptionCertificateResponse>
  <documentId>FRC-DIWASS-001</documentId>
</SubmitFacilityReceptionCertificateResponse>

SubmitFacilityCompletionCertificate​

Submitted by the treatment facility after recovery or disposal is complete. Closes the movement lifecycle.

Request (abbreviated)​

<SubmitFacilityCompletionCertificateRequest>
  <movementId>MOV-DIWASS-2026-001</movementId>
  <facilityTypeCode>R3</facilityTypeCode>
  <interimFacility>false</interimFacility>
  <actualSiteOfDisposalOrRecovery>true</actualSiteOfDisposalOrRecovery>
  <completionDate>2026-06-15</completionDate>
  <wasteClassifications>...</wasteClassifications>
  <reusedQuantity><massTonnes>0</massTonnes></reusedQuantity>
  <recoveredQuantity><massTonnes>3.5</massTonnes></recoveredQuantity>
  <disposedQuantity><massTonnes>0</massTonnes></disposedQuantity>
  <signature>...</signature>
  <attachmentIds/>
</SubmitFacilityCompletionCertificateRequest>

Response​

<SubmitFacilityCompletionCertificateResponse>
  <documentId>FCC-DIWASS-001</documentId>
  <notificationStatus>COMPLETED</notificationStatus>  <!-- if all movements complete -->
</SubmitFacilityCompletionCertificateResponse>

SubmitNotificationSignal​

Submits a signal on a notification or movement. Used by competent authorities to mark proper completion, proper carriage, or Annex VII cancellation. Commercial software may submit on behalf of an operator where permitted by the competent authority.

Signal type codes:

CodeMeaning
ProperlyCarriedOutNotified shipment was carried out properly
ProperlyCompletedRecovery/disposal was properly completed
Annex7CancelledLinked Annex VII document cancelled

Request​

<SubmitNotificationSignalRequest>
  <notificationId>DIWASS-NOT-2026-HR-000123</notificationId>
  <typeCode>ProperlyCompleted</typeCode>
  <userCADomainId>YOUR-CADOMAIN-ID</userCADomainId>
  <signature>...</signature>
  <attachmentIds/>
</SubmitNotificationSignalRequest>