Previously, processed check payments did not display in the Check Register Report (20748). To fix this, the existing SQL code that read and updated IDs was replaced with a stored procedure. However, an unintended side effect of this assigned voided payments only a tender ID of 0, so that each void overwrote the previous void (open the bill Transaction History view and click Details, view the Payment Info and click Void). These issues have been resolved.
Some check payments processed and validated using Quick Post (All Items) were not processed as expected. The issue was discovered after payments did not display in the Check Register Report and drawers failed to balance at the end of the day (Activities > Quick Post (All Items); Activities > Daily Collections > Daily Check Register Report). The problem: While multiple users were processing payments, the system failed to retrieve all tender IDs–an identifier assigned to payments entered in the system. The SQL code previously used to read and update IDs has been replaced with a stored procedure, which is a more reliable, self-contained measure for data validation. Additionally, the procedure now occurs earlier during processing.
The Homestead application and Order Determining Protest Letters have been updated and are now compliant with the most recent legislative requirements changes/additions.
The Commercial Comparable Equity Search previously retrieved data going back up to four years, and displayed that data with the current year’s (File > Open > Comparables – Commercial, select Equity Comparables). Residential and Commercial comparable grid searches now include any and all years for which the system has relevant records. Configure comp grids through Tools > Comparable Property > System wide configuration.
The Owner/Agent Import and Appraisal Data Import procedures resulted in an unexpected error (File > Import > Appraisal Data, right-click in the import list and choose New Owner/Agent Import). These procedures has been updated for this release.
The Credit Card Convenience Charge did not display when a single tender payment is posted. A Total Swipe Amt field has been added to the dialog; when users select Credit Card as the tender type, the credit card fee is included in the amount displayed in this field.
Field locations within the Quick Post (All Items) Post Payments dialog box have been rearranged for better use of space (Activities > Quick Post (All Items)).
This release includes the following additions and modifications to functionality.
The Appraisal Export generated from PACS Appraisal now includes the Omitted Property marker (an attribute on the supplement code: Tools > Code File Maintenance > General > Supplemental Codes) and TIF Zone Codes with Descriptions (Tools > Code File Maintenance > General > TIF Zone). Generate the export file by choosing File > Export > Appraisal Information.
In PACS Appraisal, the following codes may now be marked Inactive:
Improvement Detail Class Codes (Tools > Code File Maintenance > Improvements > Details > Class Codes)
Improvement Detail Type Codes (Tools > Code File Maintenance > Improvements > Details > Type Codes)
Land Detail Type Codes (Tools > Code File Maintenance > Land > Type Codes)
To mark a code Inactive, open the code file dialog box and select the Inactive option.
After a code is marked inactive, details and schedules that remain associated with the code are not changed; these inactive codes also carry over when copying details and schedules.
Users are warned when they attempt to inactivate a code that is currently assigned to a land or improvement detail.
Inactive codes do not display as a choice or option in drop-down lists or code choosers. However, if you are working with a land or improvement detail that is currently assigned an inactive code, that code does display as an option within any drop-down list or code chooser associated with that detail.
When processing payments in PACS Collections, it is now possible to handle multiple tender types in a single transaction. This affects the following instances of the Payment Cart:
The Payment Cart used for processing property and taxpayer payments.
Previous version of the Post Payment dialog (below)
New version of the Post Payment dialog (below)
Open this Payment Cart from property search results Property List by highlighting property, right-clicking and choosing Move to Payment Cart, or, from the Property view by clicking the Tax Due tab, highlighting a Statement ID and clicking Move to Payment Cart. Or, open this Payment Cart from taxpayer search results Taxpayer List by highlighting property, right-clicking and choosing Move to Cart, or from the Taxpayer view by clicking the Properties tab, highlighting a Property ID and clicking Move to Payment Cart.
The Quick Post (All Items) Payment Cart (Activities > Quick Post (All Items)). Additionally, this Post Payment dialog box now includes the option to pay by credit card.
Previous version of the Quick Post (All Items) Post Payment dialog (below)
New version of the Quick Post (All Items) Post Payment dialog (below)
The Post Statement dialog box. Open this option through Activities > Post Statement.
Previous version of the Post Statement dialog (below)
New version of the Post Statement dialog (below)
Note that the Credit Card Convenience Charge column in the new tender grid now indicates if a CCCC has been applied; this column does not reflect the charge amount. In addition, the CCCC is no longer reflected in the Total Paid amount. Modify Credit Card settings through Tools > Code File Maintenance > Credit Cards > Charge.
The tender types allowed are the following:
Check(amount, check #, DL#, expiration date and state)
Money order (amount, money order #)
Credit Card (amount, credit card type, last 4#, authorization code, CCCC (convenience charge) and swipe (amount charged to card including fee))
Note that Quick Post (Single Item) option has not changed (Activities > Quick Post (Single Item)).
Payments made using multiple tenders can still be refunded. However, the refund cannot be generated in the system as multiple tender types.\
When multiple checks are processed, each check is validated individually.
Receipts and reports detailing payments now also reflect the various tender types when multiple tender types are processed. These include the Fee Receipt, Tax Receipts, the Daily Check Register, Daily Balance Detail Report, and the Daily Balance Summary Report.
(98520) Supplement processing has been expanded for Collections users. The new Create New Supplement Group user right enables the Create New Supplement Group option in the Supplement Wizard.
What’s New in Appraisal and Collections Documentation
The system did not retain updated values in an Arbitration record. This occurred partly because some enhancements in the Arbitration module from 8.1.08.x did not successfully transfer to subsequent releases. This issue has been corrected.
Appraisal Notice Procedures
Attempting to print appraisal cards for parent properties also printed cards for child properties (Activities > Appraisal Cards > Print User Defined, select Print Only Parent Property in the UDI Options drop-down list). The Print Only Parent Property UDI option now functions as expected.
Attempting to print/preview Exemption Applications through End of Year Processing generated an unexpected error (Activities > End of Year Processing > Print Exemption Applications). This issue, which stemmed from a maximum number of allowable print jobs in Crystal Reports, has been resolved.
Commas did not display in certain values with more than three digits. The following values now include commas: Appraiser Assigned Value, ARB Assigned Market, ARB Assigned Equity, Current Market Value, and Current Appraised Value.
Unexpected characters displayed after pressing Enter multiple times in the Description field of a Personal Property type Detail Segment (click Personal Prop tab, choose Segment Detailed View, highlight a segment and double-click to open). The issue occurred for users with the Windows XP operating system and has been resolved.
Because the required font was missing, another font was unexpectedly substituted when generating an Ag application (with a property record open, choose Property > Print Property Applications). The missing font has been restored.
Field boxes did not print when generating a blank customized Ag application (Activities > Print Property Applications). The expected field boxes have been drawn and now display as expected.
During the appraisal notice selection run, addresses not explicitly coded as deliverable were being deemed undeliverable (Activities > Appraisal Notices > Appraisal Notice Maintenance, right-click and choose New Appraisal Notice Selection). This default has been reversed, and the system now assumes an address is deliverable unless otherwise indicated.
An unexpected error sometimes occurred on attempting to view Shared Property Details from the RBack-ShProp tab of a property record. A coding issue causing memory corruption within the Value tab of the Detail has been corrected. The same coding issue was located and corrected elsewhere in the application, stopping or preventing similar errors from occurring.
When creating a new property from a reference property in a certified year, users were not required to enter the Supp Code (File > New > Property, choose From Reference, select a certified year). The Supp Code field is now required, as indicated in the dialog box.
Image and Document Processing
Main images were not consistently marked as such (see Main Image option when an image is selected in the Image tab). This issue has been corrected.
Some fields in the Improvements dialog box did not accept negative values (choose Improvements view, click New, select and enter negative Flat Value). This issue has been corrected.
Marshall & Swift
The Marshall & Swift Report displayed the same situs more than once for a single property (Improvements view, click Details > Details (Marshall & Swift), click Print). The report now displays the primary situs only. No situs information displays when a property has no designated primary situs.
AutoBuildLegal failed when a Condo-type Abstract/Subdivision/Mobile Home/Condo (Abs/Subdv/Mobile/Condo) Code was selected (to make the Code Files, choose Tools > Code File Maintenance > General > Abstract/Subdivision/Mobile Codes; to create new properties, choose Activities > Mass Create New Properties, then select the code from the Abs/Subdv drop-down list). The issue has been corrected.
An unexpected error occurred during a mineral import because a lease ID number was longer than what the system allowed (File > Import > Mineral/Personal Property). The system is now prepared for IDs of up to 12 characters.
An incorrectly named column in a system table led to issues with a query. The column name has been corrected.
Assessed Value has been renamed Taxable Value in the Entity Summary box displayed at the bottom of the Tax Statement (Activities > Assessment > Levy Functions > Levy Statement Maintenance, select run, right-click and choose Print).
The Collection Owner on a UDI child property could not be updated in supplement because an override flag was set in the code (with property record opened, choose Property > UDI – Create Property Group). This default has been reset so that the override is no longer enforced when creating new child properties.
The system failed to make an expected historical match on a property record during an appraisal data import; attempts to match by GEO ID also failed because the ID in the system had already been matched to a different imported property record (File > Import > Appraisal Data, highlight run, right-click and choose Match Unmatched Properties). The prerequisites for historical matches have been modified; a property is eligible for a historical match if all of the following are true: (1) The importing site is a system-type B (shared appraisal and collections database); (2) the property has been imported before in a previous year; (3) the property does not exist in the current year layer at the tax office.
The Daily Balance Summary Report and the Daily Balance Details Report displayed the tendered amount as the amount paid, preventing the report totals from balancing as expected (Reports > Collections > Daily > Daily Balance Summary Report & Daily Balance Detail Report). Incorrect amounts displayed because the change due amount was not being subtracted from cash tender amounts. The change is now being subtracted, leaving the a correct value for total paid.
PACS failed to assign Geo IDs when importing Pritchard and Abbott files (File > Import > Appraisal Data, right-click and choose New Appraisal Import, then choose Pritchard & Abbott from the Software Vendor drop-down list). This issue has been corrected.
The Daily Check Register Report displayed voided payments in addition to routine received payments (Reports > Collections > Daily > Daily Check Register Report). This issue–an unintended effect of multiple tender development–has been corrected.
Delinquent Notice Processing
Notices printed double-sided (duplex), with separate properties printing on the same page (Activities > Assessment > Delinquent Tax Functions > Print Delinquent Notices, choose Prop ID – Comma Separated and enter Property IDs separated by commas and then click Print). A default setting related to Crystal Reports has been modified such that now the Duplex printing condition is no longer the default.
Mortgage Companies were not sorted as expected in the Mortgage Company Accepted Report and the Mortgage Company Rejected Report (File > Import > Mortgage Payment File, click View Imports, highlight run, right-click and choose Print). Sorting is now alphabetical.
A Mortgage Payment Import failed because the system was not prepared to handle blank spaces in place of the lender ID (File > Import > Mortgage Payment File). This issue has been corrected.
The Mortgage Company List did not display the expected mortgage companies (Reports > General > Mortgage Company List). The required data fields are now formatted in such a way that Crystal Reports can read them.
When printing multiple copies of receipts from the Quick Post (All Items) Post Payments dialog box, the pages were not collated as expected (Activities > Assessment > Delinquent Tax Functions > Print Delinquent Notice). This issue has been corrected.
Underage allowances were ignored in the Payment Cart when using the Pay All option on quarterly bills (from Property Tax Due tab, choose Quarterly Bills from the Views drop-down list and click Pay All, then navigate to the Payment Cart and choose Under Payment from the Code drop-down list and post a payment less than the balance but within the underage allowance). Now, no balance remains after posting a payment within the underage allowance.
Amounts displayed in the M&O Due and I&S Due fields of the Bill Summary dialog box did not round as expected. The rounding issues have been corrected.
Amounts due were being omitted and/or inaccurately reported on delinquent notices because the executing code was constructed in such a way that the amount and payment type (Full, Quarterly, etc.) of the last bill processed led to unexpected modifications to previous bills (Activities > Assessment > Delinquent Tax Functions > Print Delinquent Notice). The relevant code has been modified to process bill amounts due without compromising other bills.
On properly configured workstations, the cash drawer did not open as expected when posting a cash transaction. This issue–an unintended effect of multiple tender development–has been corrected.
A refund was unexpectedly omitted from the Refunds Due Report (Reports > Collections > Refund Due Report). A previous change intended to correct discount amounts resulting from over-payment refund transactions also inadvertently prevented relevant values from being set. Values are now initialized to 0.0 during refund-related calculations, thereby allowing the expected transactions to be included in reporting. This corrects the issue.
Supplement processing has been expanded for Collections users. The new Create New Supplement Group user right enables the Create New Supplement Group option in the Supplement Wizard.
Tax Statement Processing
The second barcode, which is coded to display the amount due, has been removed from the Tax Statement for all clients (Activities > Assessment > Levy Functions > Levy Statement Maintenance, right-click and choose Print Levy Statements).
Printing some owner levy statements unexpectedly generated events for all owner statements in the run (Activities > Assessment > Levy Functions > Levy Statement Maintenance, right-click and choose Print Levy Statements). Now, events are only generated for owners whose statements are printed.