# Performing Permit Rollovers

## When to Rollover Permits

Patrons who pay by payroll deduction or through credit card purchases can also have their payments processed automatically as part of the rollover process.

Before attempting rollovers, please follow the steps in these wiki articles to ensure you have activated the correct Sales Window and that you have your information correctly set up for automatic payments.

Read Sales Window Management and Credit Card Management in OPS-COM

<span data-colorid="h4so870hd4">Performing Permit Rollovers</span>

To begin a rollover hover over **Permits** and click **Permit Renewals.** Click **Rollover Users** to launch the **Rollover Wizard utility.**

[![image.png](https://opscom.wiki/uploads/images/gallery/2024-06/scaled-1680-/FJbimage.png)](https://opscom.wiki/uploads/images/gallery/2024-06/FJbimage.png)

***Important***

Before a rollover can be performed you must make sure that the new sales window you are rolling into has a start date that is equal to or greater than the end date of your previous sales window.

You may perform the steps outlined in the Sales Window Management and Credit Card Management in OPS-COM articles, to show you how you can set up sales windows before performing a rollover.

### Select Rollover Options

From the permit Renewal window select the current sales window you are rolling over **from** (From Sales Window) on the left side of the form.

[![image.png](https://opscom.wiki/uploads/images/gallery/2024-06/scaled-1680-/EZ2image.png)](https://opscom.wiki/uploads/images/gallery/2024-06/EZ2image.png)

  
Then select the Sales Window you wish to roll the permits into. In our example we are rolling permits from the October Sales Window to the November Sales Window.  
At this point, we have the ability to select what user types we wish to roll over, or simply leave it as the default of **All User Types.**

[![image.png](https://opscom.wiki/uploads/images/gallery/2024-06/scaled-1680-/KUpimage.png)](https://opscom.wiki/uploads/images/gallery/2024-06/KUpimage.png)

We also have the ability to select what user types we wish to roll over, or simply leave it as the default of **All User Types.** Click on **Show Lots** to list all lots that can be rolled over in the selected Sales Window.

The list of lots will appear below the search form.

[![image.png](https://opscom.wiki/uploads/images/gallery/2024-06/scaled-1680-/7KQimage.png)](https://opscom.wiki/uploads/images/gallery/2024-06/7KQimage.png)

You may choose to include or excuse specific permits from the rollover. To see the list of permits that you can toggle for renewability click on either the **Holders** or the **Renewing** button.

[![image.png](https://opscom.wiki/uploads/images/gallery/2024-06/scaled-1680-/PLRimage.png)](https://opscom.wiki/uploads/images/gallery/2024-06/PLRimage.png)

A list of permits in this lot will appear where you can toggle whether you wish to have permits renewable or not. In our example below permits STAFF1000 and STAFF1001 are not renewing and therefore should not roll over.  
Be sure to click **Update Permits** to save your changes.

[![image.png](https://opscom.wiki/uploads/images/gallery/2024-06/scaled-1680-/tk9image.png)](https://opscom.wiki/uploads/images/gallery/2024-06/tk9image.png)

Here's the logic used for each column:

<div class="columnLayout single" data-layout="single" id="bkmrk-state-current-permit"><div class="cell normal" data-type="normal"><div class="innerCell"><div class="table-wrap"><table class="relative-table wrapped confluenceTable tablesorter tablesorter-default" role="grid"><colgroup><col></col><col></col><col></col><col></col><col></col></colgroup><thead><tr class="tablesorter-headerRow" role="row"><th aria-disabled="false" aria-label="State: No sort applied, activate to apply an ascending sort" aria-sort="none" class="confluenceTh tablesorter-header sortableHeader tablesorter-headerUnSorted" data-column="0" role="columnheader" scope="col" tabindex="0">State</th><th aria-disabled="false" aria-label="Current Permit Renewing(prevent_rollover = 0): No sort applied, activate to apply an ascending sort" aria-sort="none" class="confluenceTh tablesorter-header sortableHeader tablesorter-headerUnSorted" data-column="1" role="columnheader" scope="col" tabindex="0">Current Permit Renewing  
(prevent rollover = 0)</th><th aria-disabled="false" aria-label="User exists in target Sale Window: No sort applied, activate to apply an ascending sort" aria-sort="none" class="confluenceTh tablesorter-header sortableHeader tablesorter-headerUnSorted" data-column="2" role="columnheader" scope="col" tabindex="0">User exists in target Sale Window</th><th aria-disabled="false" aria-label="Permit exists in target Sale Window: No sort applied, activate to apply an ascending sort" aria-sort="none" class="confluenceTh tablesorter-header sortableHeader tablesorter-headerUnSorted" data-column="3" role="columnheader" scope="col" tabindex="0">Permit exists in target Sale Window</th><th aria-disabled="false" aria-label="Notes: No sort applied, activate to apply an ascending sort" aria-sort="none" class="confluenceTh tablesorter-header sortableHeader tablesorter-headerUnSorted" data-column="4" role="columnheader" scope="col" tabindex="0">Notes</th></tr></thead><tbody aria-live="polite" aria-relevant="all"><tr role="row"><td class="confluenceTd">Renewing</td><td class="confluenceTd">True</td><td class="confluenceTd">False</td><td class="confluenceTd">False</td><td class="confluenceTd">Neither the user, nor the permit exists, but the current permit is set to be renewed.</td></tr><tr role="row"><td class="confluenceTd">Blocked</td><td class="confluenceTd">True</td><td class="confluenceTd">False</td><td class="confluenceTd">True</td><td class="confluenceTd">The permit exists in the target sale window, but the user doesn't. This means anywhere for any permit in the lot. If the user has multiple permits and some of them renewed, then they technically are not blocked. If the user has been given a different permit, they also are not blocked.</td></tr><tr role="row"><td class="confluenceTd">Renewed</td><td class="confluenceTd">True</td><td class="confluenceTd">True</td><td class="confluenceTd">N/A</td><td class="confluenceTd">The user is considered renewed when they exist in the target sale window. Just like the note for blocked, it's not intended to be good for users with multiple permits.</td></tr><tr role="row"><td class="confluenceTd">Not Renewing</td><td class="confluenceTd">False</td><td class="confluenceTd">False</td><td class="confluenceTd">N/A</td><td class="confluenceTd">The user was not found in the target sale window and their permit is also not renewing. This is the expected scenario.</td></tr><tr role="row"><td class="confluenceTd">Not Renewing, but Exists</td><td class="confluenceTd">False</td><td class="confluenceTd">True</td><td class="confluenceTd">N/A</td><td class="confluenceTd">The user WAS found and their permit is not renewing. This could use some investigation to make sure that the user is supposed to have that permit or not.</td></tr></tbody></table>

</div></div></div></div>Once you have completed this process for all lots you wish to include in the rollover process click on **Renew Permits** to continue.

[![image.png](https://opscom.wiki/uploads/images/gallery/2024-06/scaled-1680-/2WIimage.png)](https://opscom.wiki/uploads/images/gallery/2024-06/2WIimage.png)

The screen will refresh and update the permit counts. As in our example here you can see in the Company Staff Lot the 3 permits we left toggled on for rollover have indeed rolled over and the 2 permits we toggled as not renewing remain in the **Not Renewed** column. These two permits will now be available to be purchased by new users once your sales window for November is active.

[![image.png](https://opscom.wiki/uploads/images/gallery/2024-06/scaled-1680-/xAFimage.png)](https://opscom.wiki/uploads/images/gallery/2024-06/xAFimage.png)

### Permit Processing

It is important to note how the permits can be processed after or during the rollover process. The system is set up to automatically roll over permits that have been paid through **gateway payment** types such as **Mastercard, Visa. Payroll Deduction** etc.  
  
In this example, Users will be rolled over but will need to make a payment in order to secure their Permit. However, if the user has a payment subscription setup they will be rolled over and the payment will be processed automatically.   
  
Note that the **Process Payment** will be automatically toggled on (will be processed) as well as the **Credit Card Type** appears in the button for users that can be processed automatically. If for any reason, the person is not continuing to park in a given lot, simply exclude them from the rollover by unchecking the corresponding checkbox under **Rollover.**

<div class="columnLayout single" data-layout="single" id="bkmrk-click%C2%A0rollover-permi"><div class="cell normal" data-type="normal"><div class="innerCell">1. Click **Rollover Permits** to complete the process.
2. You will need subscriptions set up for payroll deductions, EFT or credit card payments.

</div></div></div>You can prevent permits from rolling over by setting the renewable flag on the permit.

## Exporting Users to Rollover

After clicking the **Rollover Permits** we can also choose to export an excel spreadsheet of all the users that are associated with the lot we have selected. To do this we click **Export Users** on the **Permit Rollover** page.

[![image.png](https://opscom.wiki/uploads/images/gallery/2024-06/scaled-1680-/MyRimage.png)](https://opscom.wiki/uploads/images/gallery/2024-06/MyRimage.png)

This will open a new window that generates the excel document for us to open depending on the browser you are using. You may be warned that the file is corrupt in some way however you should still be able to view the output in Excel's protective view.

## Related Video

<iframe class="youtube-player conf-macro output-block" data-hasbody="false" data-macro-id="f5e659b8-dbe4-4c0f-896e-0e56beabc3d5" data-macro-name="widget" frameborder="0" height="268" src="https://www.youtube.com/embed/R02qrltP3RM?wmode=opaque" style="width: 536px; height: 268px;" width="536"></iframe>