TransVirtual Standard POD Import (XML V1.0)

TransVirtual Standard POD Import (XML V1.0)

POD Import

Supplying your POD's in this format provides easy and detail format for integration. This can be accepted in FTP or Email. Advise your integration contact of your preferred method.


<PODs>
<PODEvent>
<ConsignmentNumber>ABC123456</ConsignmentNumber>
<UniqueID>123456</UniqueID>
<PODReceivedTime>29/05/2020 12:02</PODReceivedTime>
<PODDriverName>Fred</PODDriverName>
<PODReceivedBy>Willmar</PODReceivedBy>
<PODRejectedNotes></PODRejectedNotes>
<PODDriverNotes>Missed Booking time, but receiver was happy to receive item</PODDriverNotes>
<PODType>Complete</PODType>
<SignatureBase64>iVBORw0KGgoAAAANSUhEUgAAA...kYwAAAABJRU5ErkJggg==</SignatureBase64>
<PODImageBase64>iVBORw0KGgoAAAANSUhEUgAAA...kYwAAAABJRU5ErkJggg==</PODImageBase64>
<PODGeoLatitude>-32.7694396</PODGeoLatitude>
<PODGeoLongitude>151.6177344</PODGeoLongitude>
<PODGeoReadTime>29/05/2020 12:02</PODGeoReadTime>
<PODQtySignedFor>3</PODQtySignedFor>
<ArrivalTime>29/05/2020 11:52</ArrivalTime>
</PODEvent>
</PODs>

Notes


XML Element
Manatory (Y/N)
Notes
<PODs>
Y
Defines the start of the Manifest of POD's
<PODEvent>
Y
Defines the start of the POD event
<ConsignmentNumber>
Y*
Defines the Consignment Number the POD information is for
<UniqueID>
N*
Defines the UniqueID the POD information is for
<PODReceivedTime>
Y
The date and time of the delivery. Format should be UTC Time** dd/MM/yyyy HH:mm, if not please advise the integration specialist of your format. 
<PODDriverName>
N
Name of the driver delivering the items
<PODReceivedBy>
Y
Name of the receiver signing for the goods
<PODRejectedNotes>
N
Any notes on a failed delivery
<PODDriverNotes>
N
Any driver notes about the delviery
<PODType>
Y
One of the delivery types below;
Complete - Full SOG Delivery
Left as Instructed - LAI/ATL Delivery
Short - Short Delivery
Signed on Paper - Receiver required SOP delivery
Card Left - Receiver Unavaliable, card left
Rejected - Delivery Rejected
Out of Time - Driver ran out of time to delivery freight
Location Drop - Items delivery to drop location
Declined Reattempt - Receiver declined a reattempted delivery
Booking Required - Arrived on site and location requires a Booking
Check Address - Address provided appears to be wrong.
No Parking - No parking avaliable to perform the delivery
Unsafe to Leave - Unsafe to leave freight in ATL/LAI situation
Closed - Receiver closed
<SignatureBase64>
Y ***
Base64 value of the Signature collected
<PODImageBase64>
Y ***
Base64 value of the POD collected
<PODGeoLatitude>
N
GPS Latitude value
<PODGeoLongitude>
N
GPS Longitude value
<PODGeoReadTime>
N
GPS Readtime of the above co-ordinates.Format should be UTC Time** dd/MM/yyyy HH:mm, if not please advise the integration specialist of your format. If this is more than 30mins befor the delivery, it is not displayed in TransVirtual.
<PODQtySignedFor>
N
Number of items signed for as part of the delviery
<ArrivalTime>
N
The arrival time onsite for the delivery
* There must be either the Consignment Number of the UniqueID for the POD to be allocated. Generally this is ConsignmentNumber
** Providing the date and time in UTC allows us to seemlessly work across timezones.
*** There must be a PODImage or a Signature attached to the POD template






    • Related Articles

    • Proof of Delivery EDI Import

      Proof of Delivery EDI Import In TransVirtual there is the ability to create EDI (Electronic Data Interchange) Import rules that allow you to upload PODs and attach them to a consignment. This process would typically be used where an outside system is ...

    • TransVirtual Standard XML Import V1.0

      XML Import  Sending XML consignment data to TransVirtual using the following format is the most efficient and cost effective option.  <Consignments>      <Consignment>            <ConsignmentNumber>ABDEM90241Aasdasdas</ConsignmentNumber>           ...

    • Standard Consignment Process

      This article will detail the standard process used from the point of consignment creation, up until consignment completion. If you are new to TransVirtual this article may help provide you with a better understanding of the best way to run your ...

    • TransVirtual Standard Status Update Import (XML V1.0)

      Status Update Import Supplying your Statuses in this format provides easy and detail format for integration. This can be accepted in FTP or Email. Advise your integration contact of your preferred method. <Statuses> <StatusEvent> ...

    • Consignment EDI Import

      Consignment EDI Import In TransVirtual there is the ability to create EDI (Electronic Data Interchange) Import rules that allow you to create consignments without the need to use the consignment creation page in the TransVirtual Web Portal. This is ...