Advance Management Layout

 

The Advance Management interface allows a user to Add or Void an advance for a selected driver (depending on their Security Profile settings defined within Security Access to Driver Advances Functionality section).   Data is also displayed for all advances created for a driver, including voided advances.

 

A user can sort and filter the data that displays within this grid, as well as rearrange the data columns. 

 

The interface itself can be reduced or expanded in size to accommodate a user’s need.

 

Figure 4: Advance Management features

 

The table below describes the features contained within the Advance Processing interface.

 

Ref.

Feature Description

A

The name of the vendor-defined driver that is the recipient of the advances listed in the selection grid.

B

Option to refresh the application with the latest administrative changes.  This option is only necessary if administrators are actively making changes to the setup table for advances while the user is working within Mover’s Suite.

C

Selection grid displays all pending advance transactions. Data fields included in the grid are as follows:

Trip Number – The trip that the advance was placed under

Order Number – The order that the advance was placed under

Date – Date that the advance was issued

Amount – The dollar amount of the advance

Reason – Description for advance entered when the advance was created

Authorized By – The application user that created the advance in Advance Management

Reference Number -

Manual Banking Service Send flag – Flag indicating that the record will not be included in an upload to the banking service provider (when checked)

Posted Date – The date that transactions were posted for this record through Advance Processing

Posted By – The user that processed the record in Advance Processing

Voided Date – The date that the record was voided in Advance Management

Voided By – The user that voided the record in Advance Management

 

D

Opens the Add/Edit Advance dialog to allow a user to define an advance for the driver.

E

Voids the selected record from being further processed.  This can only occur on non-posted advances.  Important: There is no warning dialog that appears when the Void button is pushed; the record will automatically be voided unless it is being posted or has already been posted. 

F

Closes the Advance Management interface.

 

Access to the Add/Edit Advance dialog is available through the Add button to users with appropriate access privileges.

 

Figure 5: Add/Edit Advance dialog from within Long Distance Dispatch

 

 

The Add/Edit Advance interface is the same for both Local Dispatch and Long Distance Dispatch except that in Local Dispatch a user cannot base an advance on a trip (no Trip Number field).

 

Figure 6: Based On section within Local Dispatch