...
| Note |
|---|
A client must be setup beforehand to use the MTO Lookup and the Court Requested Conviction status and workflow. This could require custom development fees to handle the client’s setup. Currently, this process is only available for use within the Ontario court system. In addition to the OPS-COM setup, the client must work with the MTO to become an Authorized Requester of the MTO information. The process can be started by contacting ARIS@ontario.ca and requesting a RAW data account. Please contact your sales representative for more information. |
An Example
For this example, our Municipal client Consider a municipal client that has the following violation life-cycle:
A violation is issued with 7 days to pay during which the fine amount may be discounted.
On the 8th day, the fine is no longer discounted.
Weekly, all tickets that have reached their 15th day of non-payment are sent to the MTO to do a lookup of relevant driver info.
Once the MTO information comes back, we will have driver infoThe MTO will send a return file containing the driver information for the vehicle involved in the violation, including address and driver's license number, to store be stored temporarilyin our the database. Notices of impending conviction (NIC letters)
Notice letters can be issued to drivers who have not paid their violations. This is done using the letter report.
If the violation is still outstanding on day 65 it will be sent to court and an additional court fee can be applied to the violation.
A file can be generated that is compatible with the Ontario
court system if upload is available. In addition, a summary file can be generated to include all cases submitted to court in a particular timeframe.
When the ticket has been paid, the Court court will send a report back to the parking manager to let them know what the outcome was. OPS-COM Admins can then use the information in the report for information to process the payment on the violation within the OPS-COM system.
| Info |
|---|
Important Note about MTO InformationARIS rules dictate the use of MTO information, requiring the information from the MTO is only temporarily stored within the OPS-COM system. Once a violation has been cancelled, paid, or sent to collections, all information from the MTO related to the violation will be purged from the system. |
Starting the Process
Up to the 15th day, the violation is following the typical rules of OPS-COM. We will start the process at day 15 when the The interaction with the MTO begins after a violation is past due.
The admin will run a weekly report to determine if there are outstanding violations in the system that have passed the 15 day mark. This would be gone unpaid for 7 days after they were marked as due. This is done using the ' Vehicle Lookup Export ' in OPS-COMpage.
This page can be found by following this menu tree:
...
Vehicle Lookup Export Tool
The Vehicle Lookup Export Tool opens. In our example the search parameters areSeveral search options are present on the page:
Minimum number of violations
Vehicle province or state
Issue To search by issue date or by due date
Date range of the lookup
...
Send for Lookup
This search returns 3 results.
To generate the required report click on Export.
...
Clicking on export will generate a file to be sent to the MTO containing the license plate number of the vehicle that additional information is being requested for.
Notice there are various formats for this export:
Aris Raw Data Account: Used if you are with an ARIS client using raw format lookups.
Aris Abstract Account: Used if you are with an ARIS client using abstract format lookups.
Send to Collections: Used to send a report to a typical collections agency outside of the MTO process.
...
A text file will be generated with the filename as SentToMTOSendToMTO-XX-XX-XX.txt, with the Xs X's acting as placeholders for the timestamp at the time of file creation.
...
MTO Processing
This section details the MTO export and import back into the OPS-COM system process.
MTO Export File
Here is a small sample of what the exported text file will look like.
The file is formatted in a custom format required for the MTO to lookup driver information.
...
MTO Response File
The file that is returned from MTO Lookup will include driver information such as the registered vehicle owner's name and home address.
This information is temporarily stored in the OPS-COM system. As governed by ARIS rules, the information will be purged from the system after it is no longer needed.
The document return returned from the MTO will look like the following:
...
| Show if | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Simulated Response FileThere is an option to generate a mock version of an MTO response file using the file previously exported. This can be done using the Third Party Simulator page, located under the menu tree:
|
Importing the MTO Response File
To import the information received back from the MTO into the OPS-COM system, navigate to the vehicle lookup import Vehicle Lookup Import page found under the menu tree:
...
A confirmation message will appear in the top right of the page.
...
Generating Notice Letters
Once the information has been imported, the data will be used to populate any missing notice letter information.
...
After the notice letters have been printed, they must be sent to the drivers of the vehicles by mail.
Sending to Collections
If the ticket still remains unpaid after the notice letter has been sent, it is eligible to be sent to the Ontario court system for collections.
...
The page will then generate a file to be sent to the Ontario court system, named in the format of SendToCRC-XX-XX-XX.txt, with the Xs X's acting as placeholders for the timestamp at the time of file creation.
It will look something like this:
...
...
The report generated by the system is in a format specified by the Ontario court system for processing, and must be customized for each municipality.
A file can be generated and exported to Excel, containing a summary of all violations being sent to court in a particular time frame.
...
Important Note
...
It will look something like this:
...
| Show if | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Client MTO CodesFor each client sending information to the MTO, there are 4 codes required by the Ontario court system that must be |
...
set up on the client’s site. NOTE - The client must request a RAW Data account from the MTO to use this |
...
process. This system will not work otherwise. Here's a reference for all the provincial forms: https://ontariocourtforms.on.ca/en/provincial-offences-act-forms/ The provincial forms are:
|
...
|
...
|
...
|
...
|
...
|
...
To set these codes up within the site, go to System Settings and select the Collections Component. Enter the values in the designated fields, and then click on save settings. |
...
For municipalities using the extra-detailed version of the notice letter where one notice is sent out for each violation rather than in bulk, the "Include All Unpaid Violations" setting must be disabled. |
...
Generating the Ontario Court Report
A file can be generated and exported to Excel, containing a summary of all violations being sent to court in a particular time frame.
The page can be found under the menu tree:
...
Note the vehicle shows there are no associated drivers.
...
| Show if |
|---|
...
| Show if | |
|---|---|
|
...
Important
For instructions on bypassing the complete Collections process and sending the item directly to Collections/Court, refer to the article here:
| |||||||
Support Agent NotesSupport Notes
It is important to gather custom information from clients so the specific client can be identified in the export to court report. For each client sending information to the MTO, there are 4 codes that must be set up for the client site. IT MUST BE A RAW DATA REQUEST from the MTO Here's a reference for all the provincial forms: https://ontariocourtforms.on.ca/en/provincial-offences-act-forms/ Case Court: starts at character 3 - a 4 digit number (Parry Sound is 3060, Perth's is 1860). This is repeated starting at character 57 and again at character 186. Case Jurisdiction: starts at character 7 - a 3 digit number (Parry Sound is 658, Perth's is 073). This is repeated starting at character 61 and again at character 190. The Agency Code: 3 alphanumeric characters followed by 3 numbers (Parry Sound is BYL390, Perth's is BYL658). |