Reviewing the Audit Postal Compliance Report

Reviewing the Audit Postal Compliance Report


Purpose & Scope


Users can identify discrepancies between the database and the spreadsheet, investigate the cause and take corrective action.


To View the Audit Postal Compliance Report LoadTrek.net users should follow the steps below. Determine proper setup, execution and reporting of postal trips with this reporting tool comparing the selected spreadsheet from the USPS ( No Ping Report) with the data in the LoadTrek database.


Procedure


  1. From the top toolbar, left click Reports->Audit Postal Compliance


  1. Choose the appropriate file provided by the USPS (No Ping Report) by clicking on the file and then clicking 'Open'. This file should be in the .xlsx format.


  1. Use the pull down menu to select the correct tab of the file. You will choose the tab that contains the listing of the segments and the 'ping' or 'no ping' entries. This tab is often labeled Weekly Compliance Report.


  1. Use the pull down calendar or enter the date you wish to review, then click 'Submit' to display the report. Note: the Audit Postal Compliance report tool is currently limited to one day.


  1. Each row of the report represents a segment of a trip. A segment is made up of 2 postal locations, an origin location and a destination location. A complete trip may contain multiple segments, for example: a trip with 4 postal locations (A,B,C,D) will consist of 3 segments (A to B, B to C, C to D).


The report consists of 15 columns, explained below:


  1. Route: Postal Contract Name


  1. Trip: Trip Number


  1. Origin: NASS code of location that represents start of the segment


  1. Origin Name: Name of location


  1. Destination: NASS code of location that represents end of the segment


  1. Destination Name: Name of location


  1. Depart: True = Loadtrek database contains a record of departure from the origin of the segment, False = LoadTrek database does not contain a record of departure from the origin of the segment.


  1. Enroute: True = LoadTrek database contains a record of travel between the origin and destination of the segment. False = LoadTrek database does not contain a record of travel between the origin and destination of the segment


  1. Arrive: True = Loadtrek database contains a record of arrival to the destination of the segment, False = Loadtrek database does not contain a record of arrival to the destination of the segment


  1. Segment in Loadtrek: True = Trip segment exists in the LoadTrek database, False = No matching trip segment in the LoadTrek database


  1. Segment on Worksheet: True = Trip segment exists on the spreadsheet provided by the USPS, False = No matching trip segment on the spreadsheet provided by the USPS


  1. PING: True = Spreadsheet from USPS shows a successful ping for this segment, False = Spreadsheet from USPS does not show a successful ping for this segment


  1. Description: Compliant = This segment is compliant, Non-Compliant = This segment is non-compliant, Segment in LoadTrek = This segment is in the LoadTrek database, but not on the spreadsheet provided by the USPS, Absent from LoadTrek = This segment is on the spreadsheet provided by the USPS, but not in the LoadTrek database


  1. Load ID: The LoadTrek load number containing the segment


  1. Master Start: The start time of the trip (planned arrival time at first location)



Suggested Review: Sort the report by clicking on the 'Ping' column header. This will re-order the report based on the presence or absence of a ping on the USPS spreadsheet. Locate and review all the 'False' entries to determine if they are due to driver execution ('False' depart, Enroute, or Arrived Data) or setup (segment not in LoadTrek). Take the necessary corrective action (driver training, static load edit, NASS code edit).


Additional Recommended Steps: Compare the columns labeled 'Segment in LoadTrek' and 'Segment on Worksheet'. An ideal report will show 'True' in both columns for all rows. The 'True' value in both columns indicates the listed segment is set up properly in LoadTrek and has a corresponding segment on the USPS Spreadsheet


The 'True' value in both columns indicates the listed segment is set up properly in LoadTrek and has a corresponding segment on the USPS Spreadsheet


    • Related Articles

    • Reviewing the Audit Postal Compliance Report

      Reviewing the Audit Postal Compliance Report Purpose & Scope LoadTrek.net users should follow the steps below to view the Audit Postal Compliance Report. This reporting tool compares the selected spreadsheet from the USPS (No Ping Report) with the ...

    • Auditing Postal Routes to ensure Postal Compliance

      Purpose Compliance personnel may reference this document as a guide to discover reasons for poor PING reporting. The most common causes for poor reporting are either a result of a missed step in setup, or poor driver execution. If these factors are ...

    • Accessing and Understanding the Postal Notifications Report

      What is the Postal Notification Report? Postal Notification report displays the top 1000 records before the selected date of the data collected and submitted to the USPS for the GPS reporting requirement. This report displays information relevant to ...

    • Permission Grouping Postal

      Permission Grouping Postal Purpose & Scope LoadTrek users should reference the information below for information about using Permission Grouping, and definitions of primary user groups and recommended permissions. Procedure Download the attached PDF.

    • Understanding the Equipment Troubleshooting Report

      Understanding the Equipment Troubleshooting Report Purpose LoadTrek users may reference the information below for an introduction to using the Equipment Troubleshooting Report. This report can serve as an effective starting point for internal ...