The Batch Ticket Processing Report is used to:

• Efficiently process multiple traffic ticket/toll records from an input batch file created from a spreadsheet.
• This program does involve screen interaction with a user. This is not designed to be run without attention.
• Another version of this program does NOT involve screen interaction with a user; it runs automatically.

I. SET-UP STEPS

A. The control record for Sundry Invoicing must be set up with the next invoice number. Use the program Edit Next Invoice Number.

B. Records need to be set up in the Edit Ticket Charge Codes file. As stated above, this file allows the user to configure how this program will behave for the various types of vendors that issue citations.

C. The Charge Codes defined above must be assigned to each vendor (in the Vendor file) whose citations are to be processed by this program.

D. Hertz users (these steps may be skipped by all other users),

1. The Edit TICGAR Control Record should be set up. Refer to the chapter Edit TICGAR Control Record for more information.

2. Prior to using this program, the next "ticket reference number" must be defined. This is done using the program Edit Next TICGAR Number. Since this is typically a "run once" program, it is not on a menu. It can be accessed by typing RUN at any menu "OPTION" field, then typing EDNTGR in the "Name of Program" field. (Note: The user's menu security level must include the "Run A Program" item on the System Management Menu in order to perform this step.) The screen will then display:

OPTION: __ EDIT NEXT TICGAR NUMBER 1 Next TICGAR # 1SAVE 2 3 4 5BACKUP 6 7HELP 8

Enter the next reference number in field 1.

Press (RET) to return to the OPTION field. Press F1 to save the record.

E. For clients using integrated payment processing (EDC) in CARS+:

By default, CARS+ will process credit card charges through the EDC system and obtain an auth code for each one. (When in this mode, the number of transactions are throttled so as not to overwhelm the authorization servers.)

Some payment services, most notably MIGS, aren't able to handle this type of automated processing. In this case, CARS+ can be configured to process credit card charges with the value "NOAUTH" in the auth. field. To have the system configured this way, ask Thermeon's Customer Support Dept. to set up GVT record TICAUTH. Note that this will cause settlements to be done without having an autorization, thus taking the risk that some transactions will be rejected. This mode should only be used when the payment service cannot handle the automatic auth requests.

F. There are three methods for obtaining the location and cash drawer to be used for the Invoice and corresponding payments:

II. SPREADSHEET FORMAT

The following table lists the required column headers to be used in the spreadsheet. After entering data, export the data as a comma delimited file and place it on your CARS+ server for processing.

Warning: The column headings must be character by character as they are illustrated in the chart below, and the format instructions must be followed. Additional columns may be added to the spreadsheet,but they will be ignored by the processing program.

Required Column Header	Format	Notes
Date	The following can be used: DDMMYY MMDDYY DD-MM-YY YYYY-MM-DD	date the ticket was received by the rental company
Vendor-no	8 character Vendor number	this is the Vendor number of the ticket issuer
Offense-type	2 character code	Leave this column blank. The Ticket Charge Code record that is to be used for the admin fee and taxes charged comes from the Charge Code on the Vendor in the previous field will be used. NOTE: This field is still used for one client in Australia.
Citation	up to 20 alphanumeric characters	Ticket citation number
Amount	nnnnnn.nn	The amount of the ticket or toll charge without any administration fees
License	11 character vehicle license number	License plate number of the vehicle involved
Ticket-date	The following can be used: DDMMYY DD-MM-YY YYYY-MM-DD	Date the ticket/infraction occurred
Ticket-time	HHMM (using a 24 hour clock [2pm = 1400))	Time the ticket/infraction occurred
Toll-Id	up to 40 alphanumeric characters	In this case of road or bridge toll charges, the id code sent by the toll company

III. TRANSMITTING THE FILE FROM A PC TO THE CARS+ SERVER

Create the spreadsheet on a computer that is also used to access CARS+. Once the spreadsheet is done, save it in the csv format.

User tip: When saving the spreadsheet, the name assigned should be no more than 30 characters with no spaces or slashes in the name e.g. "ticket-082515.csv" but not "ticket 08/25/15.csv".

On the same computer, sign into and access CARS+. Go to the Batch Ticket Processing Report program and with the cursor at the "OPTION" field, press F4 to upload the file. A browser window will appear. Select the csv file from your PC and click "Send".

IV. RUNNING THE PROGRAM

User tip: It is recommended that this program is not run while your session is being shadowed by another user.

If the file has been previously imported (using the above instructions), the file can be loaded for processing by either typing the file name in Field 1 or searching for it. To search, place the cursor in Field 1 and press F6. A search window will appear on the lower half of the screen. An example is shown below.

OPTION: __ BATCH TICKET PROCESSING REPORT 1 Batch file name 2 Payment Date 12-28-15 3 Ticket Received RA/NRV# 4 Ticket No. 11 Last Name 5 Ticket Issuer 12 First Name 6 Ticket Date 13 Address1 7 Ticket Time 0000 14 Address2 8 Offense Type 15 City 8 Ticket Amt 16 State 10 License No. 17 ZIP NOTE: DATE FORMATS HAVE CHANGED. ACCEPTABLE FORMATS ARE: MM-DD-YY YYYYMMDD DDMMYY Option: _ TICKET FILE SEARCH F2=NEXT 8 F4=PREV 8 File Name Create Date 1 ticket-082515.csv Aug 25 2015 2 ticket-081515.csv Aug 15 2015 ** No More Records **

Select the appropriate file by typing the row number.

Place cursor in the "OPTION" field, and press F1 to begin.

The Batch Ticket Processing Report program can be run in 'interactive mode" or "automatic" (non-interactive) mode. A section on each mode follows.

INTERACTIVE MODE

A. All records in the spreadsheet are sorted by Vehicle License Plate number and then citation issue date/time. This is done in order to discover if multiple tickets were written for a single rental. As a result, the transactions may be processed on the screen in a different order than the order expected.

For each line in the spreadsheet:

B. If the vendor number doesn’t match an existing vendor record in CARS+, an error is displayed and the record is skipped.

C. If the vendor does not have a Ticket Charge Code assigned to it and the Offense Type column in the spreadsheet is blank, an error is displayed and the record is skipped.

D. If the vehicle license number does not match an existing license number in the Vehicle file, an error is displayed and the record is skipped.

E. Next, the Vehicle History file is checked to see if this ticket has already been processed. If the ticket is found, an error is displayed, and the record is skipped.

F. If the vendor number and vehicle number are validated, the RA file (and optionally the Non-Rev file) are examined for records in accordance with the date of the infringement.

The RA is displayed on the main window for customer editing.

Press F1 to proceed with processing.

When more than one record is found, the possibilities are displayed in the subwindow on the screen. The user must select the line number for the correct record. Or the user may press ESC to exit the subwindow without selecting a line.

If no records are found in the RA or Non-Rev files, the vehicle history file is examined for Service Code records number 00 (RAs) and 93 (Non-Revs) in case the RAs or Non-Revs have already been purged off the system.

At any time, the user can press F2 to skip the record displayed and move on to the next record in the file. If a record is skipped it will appear on the error report at the end of the run.

G. Pressing F1 for each ticket displayed causes the ticket to be processed and the following occurs:

1. Edits made to the renter’s address are saved to their customer record.

2. Edits made to the displayed name are saved to their customer record.

3. A Sundry Invoice record is created against the renter or, if there is one, the bill-to account.

If liability is accepted by the rental company, the invoice is for both the ticket amount and any administration fees defined in the vendor's Ticket Charge Code record.

If liability is NOT accepted, the invoice is for just the administration fee, if any.

In either case, if the rental has a credit card for the renter and the card can be authorized via CARS+ EDC, the invoice will be paid by charging the renter's credit card. The date entered into Field 2 will be used as the payment date on the credit card transaction.

If the Ticket Charge Code indicates that renters are to be invoiced when a credit card cannot be authorized and processed via CARS+ EDC, a Sundry Invoice (which generates a receivable) will be created.

If the Ticket Charge Code indicates that renters are NOT to be invoiced and a credit card cannot be authorized and processed via CARS+ EDC, a Sundry Invoice will not be created.

4. Depending on the Ticket Charge Code involved, a renter's letter and or a statutory declaration letter will print for the parties involved.

5. The fact that the ticket was processed is recorded in the Vehicle History File by the writing of a Service Code 91 record with the ticket number in field Vehhst-text.

6. The "Ticket" count field in the customer file is updated.

7. The next ticket from the spreadsheet file is then displayed.

AUTOMATIC MODE (NON-INTERACTIVE)

Thermeon's Customer Support Dept. can configure the system to process tickets automatically by creating the GVT record QUICKTKT.

Under this configuration once the program is started, pressing F1 or selecting row numbers is not required. If a ticket and matching RA or Non-Rev is found, it is processed automatically, and the program moves to the next row in the csv file. If multiple records are found, rather than pausing to allow the user to select the correct transaction, the ticket is marked as an error and the program moves on to the next row in the csv file. Contact your Thermeon Customer Support representative if this set-up is desired.

AUDIT REPORTS

Under either interactive or automatic mode, once all records have been processed, two audit files are produced:

• The first lists all tickets which were successfully matched to a transaction and were processed. The Sundry Invoice number of the record created will appear in this file.
• The second lists all tickets that erred out.

These reports as well as a 3rd output file (details below) can also be produced in csv format as an additional output - ask Thermeon's Customer Support Dept. to configure the GVT record QUICKTKT with this additional feature.

Additional output file headings

License#,Vendor-no,Vendor-name,Ticket#,Ticket date,Ticket time,Ticket Amt,RA#,vehicle#,Admin Fee,Cust#,cust,ame,cust address,cust city,cust state,cust zip,employer name,employer address,employer city,employer state,employer zip,DL number,DL state,FOP,FOP No,FOP Expiry

To access this program: To access the Ticket Processing Report, type BCHTKT (RET) at any menu "OPTION:" field or the appropriate line number on the Ticket Processing Sub-Menu of the History/Maintenance Menu. The screen will then display:

OPTION: ____ BATCH TICKET PROCESSING REPORT 1 Batch file name 2 Payment Date 12-28-15 3 Ticket Received RA/NRV# 4 Ticket No. 11 Last Name 5 Ticket Issuer 12 First Name 6 Ticket Date 13 Address1 7 Ticket Time 0000 14 Address2 8 Offense Type 15 City 9 Ticket Amt 16 State 10 License No. 17 ZIP /dev/tty 1SAVE 2SKIP 3ERASE 4UPLOAD 5BACKUP 6 7HELP 8

Enter data as follows:

1. BATCH FILE NAME	Enter the name of the ascii comma delimited file containing the ticket data. Press F1 to begin processing the records.
2. PAYMENT DATE	If the ticket amount and/or an administration fee is to be charged to the renter of the vehicle, either to his credit card or against him personally, enter the date for that payment. This field will default to today's date. It can be set to any date in the future, it cannot be back dated.
3. TICKET RECEIVED	This field displays the date the ticket was received.
4. TICKET NO.	This field displays the ticket number of up to 20 alphanumeric characters.
5. TICKET ISSUER	This field displays the Vendor number of the entity that issued the ticket.A valid Vendor number must be used.
6. TICKET DATE	This field displays the date the ticket was issued.
7. TICKET TIME	This field displays the time the ticket was issued.
8. OFFENSE TYPE	This field displays the Ticket Charge Code from the vendor record.
9. TICKET AMT	This field displays the amount of the ticket.
10. LICENSE#	This field displays the license number of the vehicle stated on the ticket.
11. LAST NAME 12. FIRST NAME	These fields display the first and last name of the renter.
13. ADDRESS 1 14. ADDRESS 2 15. CITY 16. STATE 17. ZIP	If the customer’s address needs to be updated (obvious typographical errors done at the counter), enter the new information in these fields. Upon pressing F1 to save, the data entered will update the customer record.