When Shipments have been successfully delivered, you may have generated a Proof of Delivery document which records the fact that the Customer has received the goods successfully.  This information can be stored within Business Central where required.

Proof of Delivery record can be created in one of two ways:

  - Automatically via an API. This method would normally be used when you are integrating with a Third-Party Provider or System. Currently the following Third-Party systems are supported:

  - Manually against the Drop on a Shipment Management Route.

 

Creating a Proof of Delivery Record Manually

Proof of Delivery documents can be manually created from the Shipment Management Route by selecting the required Drop and then clicking on Functions > Create Proof of Delivery.  

The information can then be entered as required.  This includes entering in a Proof of Delivery Reason Code explaining why the delivery could not be completed. 

Note - If you are using an Integration with a Third-Party Product such as PODFather, then this option will not be displayed.  In addition, not all Proof of Delivery features will be available to populate when creating them manually such as Pictures and Signatures etc.

 

Viewing Proof of Delivery Documents

Proof of Delivery documents can be viewed within Business Central from a number of different areas which are explained below:

If you would like to view the documents for a specific Customer, then this can be completed from the Customer Card.

 

If you would like to view all documents for a specific Shipment Management Route, then this can be achieved by selecting the below option from the Shipment Management Route Card:

 

If you would like to view the document for one Drop on a Shipment Management Route, then this can be achieved by selecting the below option from the Shipment Management Route Card:

 

If you would like to view all Proof of Delivery documents created, then you can do this from the Proof of Delivery Page:

 

Proofs of Delivery can also be viewed from the relevant Posted Source Document: