Skip to main content

Negative Payment - Remove Finerror/ordamend/pdamend events - Knowledgebase / Older Knowledgebase Items - Vermont Judiciary Technology Service Center

Negative Payment - Remove Finerror/ordamend/pdamend events

Authors list

Negative Payment - Remove Finerror/ordamend/pdamend events

Example Ticket: 36726

For this ticket, the user is asking to have a 'finerror' event removed. (This process will work for any amended fine) 

Search the docket in VTADS and find the finerror event:

Press F2 to open the details of it and take note of the fine#:

Press  F7 + enter and type "evekill" to delete the event. F1 up to the header of the docket and press  Shift + F4 to run a form and type "payord" over "docket" and choose 's' for Narrow Output:

Press F9  to bring up the form on the screen:

Find the entry that has the same fine # as the 'finerror' event and see the correction is still present. Take a screenshot or write down the Fine ID & Agree IDs. Press to exit the form and return to the docket.

Press F1 again to close the docket out completely and navigate to the Direct Table Access List.

Option 23. System Administration Reports -> Option 4. Direct Table Access

These are the tables you have to work with for all payments, fees & fines:

*********************************************************************************************************************************

You need to work from the bottom table to the top. 

Start at the Credit Table, then the Payment Table, Debit Table, etc. The Agree Table should be the last you search/work in. This is especially important as VTADS will not let you delete anything unless you work in this order.

*********************************************************************************************************************************

Working from the bottom (the credit table) the first table I found the Fine  error in was the debit table:

Press Shift + F2  to delete the entry and then return to the docket and run another 'payord' form like before:

And the fine error is no longer present.