Restricting Payment of Violations in Court Requested Conviction (CRC) Status

The Court Requested Conviction (CRC) payment restriction feature allows administrators to block users from paying for parking tickets that have been escalated to court or a collections agency. Its primary purpose is to ensure that escalated violations are handled through the proper legal or administrative channels, while still allowing authorized staff to override the block if necessary. This article is intended for OPS-COM administrators responsible for system configuration and collections management.

Setup and Configuration

Configuring this feature requires adjusting global system settings to restrict the users, followed by updating role permissions to grant specific administrators override capabilities.

Configuring Global Restrictions

1. Click

   Hover over System Configuration, and click System Settings.

   to
ensure

2. Locate the settings that pertainpertaining to Collectionscollections.

   are
set
3. to disallow payments while violations are under

   Enable the CRC status.
   

   

   
   
4. Ensure that the following settings are enabled and save the settings:
    - Prevent Violation Payment
    checkbox to stop users from paying escalated fines.

5. Enable the  - Prevent Purchases
   
   

   checkbox to stop users with escalated fines from buying new permits.

   
   
   
6. There are

   Save twoyour permissionssettings.
   

   that
deal

with

Configuring theAdministrative treatmentOverrides

of

payments
1. for

   Hover over System CRCConfiguration items. To setup these permissions,and click System Configuration, ManageManage Roles.  
   

   

   
   

2. Select the role you wish to addgrant theseoverride abilities to. In this example we will add them to (e.g., Primary AdminAdmin).

3. Click on Permissions to access the role settings.
   
   

   

   
   
4. Under

   Click the violationsViolations Tabtab.

   ensure
that
5. these

   Enable two settings are enabled:
   (A)the Pay Violations In Collections. (Allowscheckbox. This allows the Adminadministrator to manually process payments on violations that are in collections.)
    (B)A)

6. Enable the Purchase While Outstanding (Allowscheckbox. This allows the Adminadministrator to purchaseprocess itemspurchases (like permits) for thea useruser, whileeven theif userthey hashave a violation thatsent to collections. (B)

7. Save your role changes.

The Purchase While Outstanding administrative permission is only necessary if the Prevent Purchases setting has been enabled in the global system settings.

Using this Feature

Once configured, the system automatically handles how CRC and collections violations are presented to different user types.

End User Experience

When a user views a violation with the "Sent to CRC" status in their portal, they will see a notice indicating the violation has been sent to collections. This is only necessary while Prevent Purchases is turned on in the settings.

The followingsystem two screens show how this functionality appears to the End User and the Admin:

This is what the User will seeremove iftheir they have violations with the 'Sent to CRC' status. Note the notices indicating the violation has been Sent to Collections.

Here is what the Admin sees if they have the permission to pay these violations while in collection status. Note the notices indicating the violation has been Sent to Collections.



Here's the Admin view with the permission to pay these violations while in collection status enabled. Note the fact that the violation is still shown as Sent to Collections yet is still payable by the Admin.

In addition, if the User triedability to pay the violationfine throughonline. OPSCOMIf the user attempts to bypass this by using the OPS-COM Quick Pay/Pay or Guest Payments portal, they wouldwill seereceive the same message disallowing the transaction.

 

Administrator Experience

Administrators viewing the same user profile will see the "Sent to Collections" status. However, if the administrator's role has the override permissions enabled, the payment fields and buttons will remain active, allowing them to manually collect and process the payment on behalf of the violation.

user.

---

Best Practices and Considerations

• 
  Business Rules for Overrides: Organizations should develop a clear business rule detailing exactly when an administrator is allowed to use their override permission to accept a payment for a CRC violation, versus when they must direct the user to the court or collections agency.

• Clear Communication: Consider updating your notice letters and email templates to clearly inform repeat offenders that once a ticket reaches CRC or collections status, their portal payment privileges will be suspended.