1.9.0.35.2300 Release Limited #

Fixes

ID

Description of Update

Letter Processing

23133/
HS 120757

Users could not print inquiry and protest letters for a specific year by Case ID because the Year drop-down list menu had been removed (in BOE role, choose Activities > BOE > Individual Letter, choose Case IDs method, set Mailing Date and Print). When printing, the system was automatically assuming the current assessment year (2013-2014), but the protests were typically recorded for previous years and Case IDs are reset each year, causing problems for users. The Year menu option had been removed to make the Print BOE Letters dialog box consistent with other letter printing dialogs. This option has now been restored. Also, any letter printing dialog which had the Year menu option prior to release 9.0.35.2000 now has it again, including the dialog for printing property letters.

Payment Processing

23023/
HS 119953

Penalty and interest on delinquent taxes did not calculate using the expected posting date until you changed the posting date with the property record open (Penalty and Interest values are displayed in the Tax Due panel; change the posting date by double-clicking the time/date stamp displayed at the bottom right of the PACS application window). The system was basing calculations on today’s date rather than the payment cart’s posting date. The calculation has been modified to calculate P&I using the posting date set in the payment cart, resolving the issue.

Payout Agreements

23013/
HS 119946

The payout agreement statement included payout agreements in defaulted status (Activities > Payout Agreements > Generate Special Assessment Payout Statement). At the time this issue was recorded, the stored procedure allowed inactive and defaulted payout agreements to be included in the printed statement. Moreover, a single statement could include the same property more than once. The stored procedure has been slightly modified to prevent these unexpected results.

Refunds

23007/
HS 119922

When issuing refunds, the taxpayer account for bills was the bill.owner_id and the taxpayer account for fees was the fee.owner_id (open a property, expand the Tax Due panel; in the Statement Amounts section, select an item and click Refund). Property overpayment credits were issued to [owner.owner_id] for the property, and account overpayment credits were issued to [overpayment_credit.acct_id]. This was not what was expected. So, now refunds are issued to the property collections owner [property.col_owner_id] instead (except for refundable items with no associated property). Account overpayment credits continue to use their account ID, and non-property fees will use fee.owner_id.

Reports – Treasurer

23037/
HS 120017

An unexpected error occurred when trying to print the Outstanding Balances Report (Reports > Outstanding Balance Report). A syntax error in the report’s SQL query has been corrected, resolving this issue.

Suggest edit
Last updated on December 8, 2018

2.9.0.35.2200 Release Limited #

Fixes

ID

Description of Update

Improvements

23000/
HS 119852

While updating a commercial property using Marshall & Swift, value from Additions on Improvements did not calculate as expected (from Property view, expand Improvements panel, open M&S Improvement Detail (the Marshall & Swift option is selected in the Values section of the dialog box), add an entry with units and unit cost to the Additions grid in the Marshall & Swift Commercial Details Dialog box, click Recalculate). Changes to the Marshall & Swift engine prevented communication with PACS regarding Additions. Setting the fields AdditionCostSpecified and QuantitySpecified to True has resolved this issue.

Suggest edit
Last updated on December 8, 2018

3.9.035.2100 Release Limited #

Fixes

ID

Description of Update

Improvements

22984/
HS 119717

The This is the base UP option was automatically deselected on Main Area Improvements after recalculating, causing all other Improvements on the property to have zero value (from Property view, open Improvements panel and click Details on MA Improvement and note This is the base UP option selected in General section; reopen the dialog, change the Class/Sub option, save and then recalculate). This issue, which existed in releases prior to 9.0.35.2000, has been resolved.

Suggest edit
Last updated on December 8, 2018

4.9.0.35.2000 Release GA #

Important!

Before running PACS 9.0.35.2000 (or any iteration/version of 9.0.35.x), your office server(s) and all workstations need the following updates:

  • Microsoft .NET 4.0 Framework 4 (full/extended edition)
  • Microsoft Visual C++ 2010 Redistributable Package (x86 for 32 bit workstations and x64 for 64 bit workstations)
    • Your IT department can find the redistributable package in the PACSINSTALL share directory.
  • True Automation Systems professionals will perform the updates on your server(s) when the 9.0.35.2000 release is deployed on your system (or by request).
  • You are responsible for updating your individual workstations. Your local IT department can run the client update utility TA_Client_PrepTool_v2.exe, which checks for and installs the required prerequisites.

Workstations that use PACS Letter Processing need to run the letter processing patch found in the local PACSINSTALL directory. The patch is named TALetterProcessingOfficeAddInSetup.msi

New Features

PACS Data Entry

  • With PACS Data Entry, users can build customized dialogs for fast and easy data entry.

    Here’s how it works: First, choose Tools > PACS Data Entry Template Maintenance in PACS.ADMIN, and click Add in the PACS Data Entry Template Maintenance window. Then build a data entry dialog template that includes the data fields you wish to edit.

    Data Entry, PACS Data Entry Maintenance, ADMIN, portions, 9034x, 001

    Your template is then accessed in PACS, allowing users to enter or modify data on commercial and residential Property records, Improvements, and Land details. Choose Activities > Mass Maintenance (Property) > PACS Data Entry or use the Property Commands menu to access the usable template dialog.

    Data Entry, PACS Data Entry Land type dialog, choosing grid, 001

    Users can quickly Tab through the fields, entering data and even adding new Improvement and Land records on the Property. After saving, the cursor automatically refocuses in the Property ID field so data entry on the next record can begin. Hotkeys are also set to aid navigation.

    Note The dialog depicted above is for entering Land Detail data. The dialog options are different when working with Property or Improvement Record Types.

    The following three user rights are relevant to PACS Data Entry:

    • PACS Administrator > PACS Data Entry Template Maintenance
    • PACS Administrator > PACS Data Entry Administrator
    • Mass Maintenance > Mass Maintenance PACS Data Entry

    The options to add Land Miscellaneous Codes and add Improvements through data entry can be enabled/disabled in PACS.ADMIN through the System Configuration options (Tools > System Configuration > PACS Data Entry Options) Disable Addition of Land Miscellaneous Codes and Disable Addition of New Improvements. Set these options to False to enable these options for data entry users with the appropriate user rights.

    Data Entry, System Config, Data Entry options, PACSADMIN, 001

  • As part of development for the PACS Data Entry project, the following three Land-related code files have a new attribute allowing users to designate them as exclusively eligible for Residential or Commercial Land Real Property:
    • Land Influence Codes
    • Land Adjustment Codes
    • Land Type Codes

    The code files are accessed in PACS.ADMIN through Tools > Code File Maintenance > Land.

Escrow

Functionality related to escrow and advance taxes has been expanded with this release. Previously, users determined a property’s escrow. The new worksheet functionality automatically estimates the amount of escrow needed to pay the taxes due (or future taxes due) on a property. Additions and modifications in this area include the following:

  • Escrow Type Code files now include calculation elements and start dates. Users can enter the percentages of assessed value of Land, Improvements/Personal Property, and Special Assessments on which to calculate escrow and advance/future taxes. When fields for these values remain empty in the selected type code file, then values for those elements are omitted from escrow calculations. For example: If the user chooses an escrow type code file with no Land calculation element, then the property’s land value is omitted from the property’s advance tax calculation. Also, a Lock Value option allows the assessed value to be locked automatically after an escrow is paid. (More info on value locking can be found below.)

    Escrow, Set Escrow Codes, 9035x, 001

    The escrow code file may be assigned an escrow Start Date–this is the date from which the code file is eligible for selection in PACS. And, when the Print Plat Certification option is selected and that escrow type code file is used, the Certification Report is automatically generated at the time of posting. Access the code file in PACS.ADMIN through Tools > Code File Maintenance > General > Escrow Type Codes.

  • Functionality in the Escrow/Overpayment Credits panel of the Property view has been enhanced. Look for the following additional menu items in the Escrow(s) grid within this panel:
    • Print Plat Certification button located in the Escrow(s) grid – Generates documentation certifying that all taxes, assessments, and fees have been paid through a given tax year, with the amount and with plat and property information

      Note Printing the Plat Certification generates an event from which the certification can be reprinted.

    • Print Worksheet button located in the Escrow(s) grid – Generates the Escrow Worksheet, which organizes and presents the values listed in the worksheet
    • Print Receipt button located in the Escrow(s) grid – Prints the receipt; this option is enabled for paid accounts only
    • Tax Year and Escrow Type filters – These drop-down lists displayed above the Escrow(s) grid can be used to filter the records displayed in the grid to those from certain tax years or types of escrows
    • Split/Merge column – This new column in the grid displays a Yes or No to indicate whether a split or merge has occurred

      Escrow, Escrow Overpymnts panel, Escrows grid, 9035x, 001

    When an escrow worksheet with a status of Created (aka Unpaid), then PACS 9.0 informs the user of this via a pop-up notification when the property is first opened.

  • An array or functionality has been added to the Escrow Worksheet dialog box, opened by clicking Add or Details from the Escrow(s) grid of the Escrow/Overpayment Credits panel. Users can now do the following when working with worksheets:
    • Assign a taxpayer
    • Set the calculation date, which ultimately affects penalty and interest charges; this date must be on or later than the start date set in the Escrow Type Code file (mentioned above)
    • Opt to have the system calculate Escrow Due or enter the values manually

      Note Manually entering Escrow Due requires the Receipting > Escrow > Override Escrow Due Amount user right.

    • View values for Property Taxes Due and Special Assessments & Fees Due, and a Total Amount Due
    • Assign an additional fee amount and type
    • Print the Escrow Worksheet, which organizes and presents the values for internal record keeping or for taxpayer presentation (the worksheet cannot be printed for escrows created prior to this functionality)

      Note This worksheet report displays the Levy Advance Tax, Special Assessment Advance Tax, and the Previous Year Taxes Due when these values exist. If the escrow due is manually entered, Advance Year and Advance Tax values replace the aforementioned values.

      When paying escrow, each item selected in the worksheet is added separately to the payment cart (itemized) for processing.

      Escrow, Escrow Worksheet, 001, 9035x

    This new Escrow worksheet functionality cannot be accessed unless a PACS Administrator enables it in PACS.ADMIN by choosing Tools > System Configuration > System (category) > Escrow and setting the new Enable Escrow Worksheet and Value Locking option to True. When this setting is not enabled, the existing Escrow Worksheet is displayed.

    Escrow, System Config ,Enable Escrow Worksheet, 9035x, 001

  • The Mass Apply Escrow Wizard has also been enhanced. Previous and current Escrow runs are now organized and stored in the new Mass Apply Escrow view opened through the previously existing menu path Activities > Mass Maintenance (Escrow) > Mass Apply Escrow.

    Escrow, Mass Apply Escrow, 9035x, 002

    From the Mass Apply Escrow view, users can view mass applied escrow run details including values for Amount Applied, Amount Overpaid, and Over/Under amounts. Furthermore, receipts and the Collected Escrow Applied Report (Reports > Escrow > Collected Escrow Applied) and Escrow Value Listing Report (Reports > Escrow > Escrow Value Listing) can be generated.

    When navigating the Mass Apply Escrow Wizard after clicking Add in the Mass Apply Escrow view, use or note the following new features:

    • Apply escrow to properties that have been split by choosing the Select Escrow with Split/Merge Indicator Only
    • Select the Escrow Type, Tax Year, and Properties
    • For selected properties with a difference between amount due and escrow amount that is within the under/overpayment variance, select the Modify to Zero column option to modify the bill to the amount paid
  • Access to some of the functionality described above requires the Receipting > Escrow > Edit Segregation Status and/or Receipting > Escrow > Override Escrow Due Amount user rights.
  • A property’s appraised values can now lock automatically when processing escrow and advance taxes. The act of locking preserves the value assessed through the current valuation method. This locked value is displayed and used even after changes are made to property elements and the property is recalculated. Locked values for Improvements, Land details, and Personal Property Segments are also preserved and used when the applied escrow type code allows.

    The system permits locking taxable values on the property if (1) the escrow type code attached to the escrow record is configured for value locking (discussed above), (2) the escrow worksheet system setting (also discussed above) is set to True in PACS.ADMIN (Tools > System Configuration > System > Escrow), and (3) the escrow was paid in full.

    For the various property types, locking works as follows:

    • On a Real property, all Land details are locked; individual improvements may be locked separately.
    • Individual Improvements may be locked on a Mobile Home property.
    • When locking a Personal property’s value, all segments are locked.
  • In addition to automatically locking values through escrow processing, a property’s values can also be locked manually by opening the property view in the Assessor role and choosing Commands > Lock Property Values. When working with a Real or Mobile Home property, this action opens the Lock Property Values dialog box, from which individual Improvements and all land details may be locked. For Real, non-Mobile Home properties, you can also choose not to lock Land value from this dialog.

    Escrow, Lock Property Values, 9035x 001

    Note the following:

    • When the user attempts to lock an improvement designated as Homesite and assigned a Senior Exemption, a warning displays that instructs the user to create a new property with the Senior Exempt Homesite Improvement. This new property may be locked.
    • When Improvement Details are viewed from this dialog, the detail opens in a read-only state.
    • When working with a Personal property, all segments are locked, so the user is simply asked to confirm the selection.
    • To lock an element, the property must have a current recalculation status free of errors.
    • Locked properties cannot be part of a split or merge.
    • The Lock Property Values user right is required (Property > Edit Property > Recalculate Property > Lock Property Values).
    • Exemptions cannot be added or removed from a locked property.
    • Properties with Income Approach valuations cannot be locked; properties with locked values cannot have their valuation method switched to Income Approach. Furthermore, advance taxes cannot be calculated for income properties, but advance tax value can be entered manually using the override option in the Escrow Worksheet.
  • To unlock, simply choose Commands > Unlock Property Values. To lock and unlock, the user must be assigned the Property > Edit Property > Recalculate Property > Lock Property Values & Property > Edit Property > Recalculate Property > Unlock Property Values user rights.
  • When an element’s values are locked, the element is still editable. For example, a locked Improvement detail may be opened to modify its Class and Condition. Land Details cannot be added to locked properties, and existing Improvement Details, Land Details (and Segments) cannot be deleted. Locked elements are identified as follows:
    • Properties with locked elements feature a warning on the Values panel.

      Notice Processing, Values panel, Locked Values, 9035x, 001

    • For Improvements with locked values, the Adjustments and Values panel of the Improvement Detail dialog box now features a populated Locked Value field.

      Notice Processing, Imp, Adj Values panel, Locked Value, 9035x, 001

    • Land details with locked values feature a populated Locked Value field in the Land Detaildialog box Market Valuation panel.

      Notice Processing, Land, Market Valuation panel, Locked Value, 9035x, 001

      Additionally, to accommodate properties with agricultural use value, a Locked Productivity Value field has been added to the Productivity Valuation panel in the Land Detail dialog box.

      Notice Processing, Land, Productivity Valuation, Locked Prod Value, 9035x, 001

    • Personal property segments with locked values feature a populated Locked Value field in the Details Segment dialog box Appraised Value panel.

      Notice Processing, Personal Prop, Details Segment, Appriased Value panel, Locked, 9035x, 001

      Note When locking properties whose valuation method is BOE Value, Land and Improvement locked value fields display a value of 0$ .

  • Values may only be locked in the current year, and the lock applies for that year only. After the year is certified, the locked values may then be modified through supplement processing as always.

Mass Maintenance

  • The Mass Create New Properties process now allows user to create properties in multiple years–both certified and uncertified (Activities > Mass Maintenance (Property) > Mass Create). Users choose an assessment year and number of prior years in which the property is being created. Selected years must be consecutive. Note that the year(s) which are selected by the user may affect which menu options are available in other fields in the rest of the procedure (i.e., Township) because some options are year-specific. Furthermore, after an initial Assessment Year is selected, the availability of previous years for property creation depends on whether values exist in those years for the following fields: Abstract / Subdivision, Township, State Code, and Land Type. For example, if the user chooses Assessment Year 2012 – 2013, and one Abstract / Subdivision code exists for the previous 5 years, one Township code exists for the previous 4 years, and one State code and one Land Type code exist for the previous 3 years, then the Number of previous Years available is 3, 2, or 1.

    When supplementing, the user chooses to place the property(ies) in a new, pending, or available supplement group.

    Mass Create Props dialog top, 2043, 9035x 001

Mobile Homes

The 9.0.35.2000 release introduces functionality for tracking and processing taxes on Mobile Home moves. When a MH is sold and moved out of the county, taxes are due for the entire year that the MH would have been in the county. The taxpayer must pay these advance taxes and the excise tax for the sale.

When a MH is on an account with land at the time of sale, advance taxes are only calculated on the MH. Treasurer offices may create a new property for just the MH but, generally, they process the escrow first. Because the new MH account does not yet exist until after the supplement is accepted, the escrow is processed on the existing/current account with MH & land.

New functionality includes the following:

  • Three new code files that enhance record keeping: (1) Mobile Home Movement Type Codes, (2) Mobile Home Movement Status Codes, and (3) Mobile Home Movement Transporter Codes. Access and maintain these codes in PACS.ADMIN through Tools > Code File Maintenance > Mobile Home Movement. Editing these codes requires the Code File Maintenance > Mobile Home Movement Types user right for Status Code, Transporter Code, and Type Code.
  • A new Mobile Home Movement panel is now displayed for properties having at least one Mobile Home-type Improvement (i.e., the Improvement’s selected Type Code has the Mobile Home attribute selected). The panel features a General grid with standard Add/Remove/Details functionality and a Print option for generating the Tax Certificate for Mobile Home Movement, the Proof of Taxes Paid letter, and/or the Mobile Home Movement Decal (read more about these documents below). The grid displays the Mobile Home Movement ID, Type, Status, name of the user who created the record, record creation date, and record update information. (Users need the Property > View Property > View Mobile Home Movement user right.)

    Mobile Home Mvmnt Movement panel, Movement grid, 9035x, 001

    From this grid users with the Property > Edit Property > Mobile Home Movement user right can add a Mobile Home Movement to the property. The movement data is recorded in the Mobile Home Movement view. This view offers escrow and MH tax calculation and payment functionality, and displays these values and assessments. Users may also add general and detailed info about the MH movement and about the purchaser and new address. This view includes the MH Movement Information panel and the Purchaser/New Address panel.

    Mobile Home Mvmnt view, 9035 rn, 001

    Edited fields are tracked in the change log.

  • A system configuration option has been added: Allow modification to Assessed Value. Access through Tools > System Configuration > System > Mobile Home Movement.
  • Bill/Fee Codes now have the MH Movement Code attribute (in PACS.ADMIN, choose Tools > Code File Maintenance > General > Bill /Fee Code). When a code having this attribute selected is on a Mobile Home Movement record, a message displays on the Mobile Home Movement module.

    Bill-Fee Code, MH Mvmnt, 9035x rn, 001

    Property Group Codes also have an attribute now which, when selected, causes a message to display in the Mobile Home Movement module for records with that code (in PACS.ADMIN, choose Tools > Code File Maintenance > General > Property Group Codes).

    Property Group Codes, MH Mvmnt, 9035x rn, 001

    Bill/Fee Codes and Property Group Codes are added to records from the Mobile Home Movement view.

  • When calculating Escrow from the Mobile Home Movement record, the simple Escrow Worksheet dialog box is displayed. This version of the dialog, which is also accessible from REET records, now includes a Property Split/Merge option which acts as an indicator (currently this plays no role in the calculation).

    Escrow, Worksheet (simple), 9035x rn, 001

    Note This version of the dialog is displayed when escrow worksheet functionality is disabled in PACS.ADMIN. When enabled, the new, extended worksheet (see above) displays.

  • The following Mobile Home movement-related documents can be generated from the Property view Mobile Home Movements panel or from the Mobile Home Movement view:
    • The Mobile Home Movement Decal, which includes the Mobile Home make, model year, serial number, transporter’s name, WUTC permit number, Department of Transportation motor vehicle permit number, date issued, issuer, and expiration date.
    • The Mobile Home Movement Tax Certificate Report, which includes the sale price, property ID, tax area, the current owner’s and new owner’s/purchaser’s name and address, transporter name, make, model year, serial number, Mobile Home size, tip out value, original location and new location/destination, tax year and assessment.
    • The Proof of Taxes Paid letter, which includes the date, property ID, reason for issuance of letter (i.e., the “letter is being issued due to sale”), current and new owner information, new situs, mobile home description (i.e., yea, make, model), and receipt number.

      Mobile Home Movement, MH Mvmnt Forms dialog, 9035x rn, 001

  • Users can search for mobile home property movement records from the Mobile Home Movement band of the Search view. Search fields include Property ID, MH Movement ID, Property Group Code and/or Bill/Fee Code (codes having the new MH Movement Code attribute), Mobile Home Movement Status and Type.

    Mobile Home Mvmnt Search, 9035x, 001

    Search results display MH Movement ID, Property ID, MH Movement Type, Mobile Home Movement Status, the date the movement record was created, and the Legal Description.

  • The new Mobile Home Movement Report assembles Mobile Home movement records meeting your criteria, and displays the dates, property IDs, and movement type code for each record. Generate the report by choosing Reports > Mobile Home Movement Report.
  • A Year field and Tip Out field are now displayed in the Mobile Numbers panel of the Improvement dialog box (open from the Improvements grid in the Property view Improvements panel). The user enters the year in which the Mobile Home was built in the Year field, and the value of the tip out addition on the property in the Tip Out field.

    Improvement, Improvement dialog, Mobile Numbers panel, 9035x, 001

Notice Processing

  • A new setting in PACS.ADMIN System Configuration (Tools > System Configuration > Personal Property) allows users to display different Assessor addresses on the Notice of Value according to which property type is described in the notice:
    • Use System Address – If set to True, the Notice of Value for all property types displays the address set in the System Configuration System Address in PACS.ADMIN.

      Value Notification, System Config, PP Use System Address, RN 9035x, 001

    When the Use System Address setting above is set to set to False, then a new Assessor Address Information section displays in the Appraisal Notice Configuration Maintenance dialog box (Activities > Appraisal Notices > Appraisal Notice Maintenance, click View Configuration Information button and choose Personal or Master Lease from the Property Type field drop-down list). The address recorded here displays on the notice.

    Notice Processing, Configuring Notice, 9035x, 001

    The Appraisal Notice Configuration Maintenance dialog box also has a new No File text field and Penalty text field allowing users to customize the text addressing Personal property owners about failing to file rendition notices.

  • Options covering Master Lease accounts have been added to the appraisal notice selection process (Activities > Appraisal Notices > Appraisal Notice Maintenance and click Add in the Appraisal Notices window). On the first page of the Appraisal Notice Selection Process Wizard, users can choose to Include All Properties in Master Lease accounts, Include Based on Selection Criteria, or Exclude All Properties in Master Lease accounts.

    Value Notification, Appraisal Notice Selection Process Wizard pg001, 9035x, 001

    The Appraisal Notice Selection Process Wizard Notice Options page for Master Lease Accounts offers a portion of the options available for other property types.

    Notice Processing, Appraisal Notice Selection Wiz, Master Leasse options, 001, 9035xRN

    For printing Personal property notices, the Notice Options selection criteria page of the Appraisal Notice Selection Process Wizard now includes a Review Date option that, when selected, includes properties according to the range of dates during which personal property rendition reviews are due.

    Value Notification, Appraisal Notice Selection Process Wizard PP pg002, 9035x, 001

  • Additionally, a # Master Lease column has been added to the Appraisal Notices window. This column displays the number of master lease accounts included in an appraisal notice run (Activities > Appraisal Notices > Appraisal Notice Maintenance or Activities > Supplement > Print Supplement Appraisal Notices).
  • When printing appraisal notices, users can now choose Print Legal Description and/or Print Appraiser Name in the Print Appraisal Notices dialog box (Activities > Appraisal Notices > Appraisal Notice Maintenance, right-click and choose Print Appraisal Notices). The default selection/unselection of the legal description option can be set with the Print Legal Descriptions on BPP Appraisal Notices by Default option in User Settings in PACS (Settings > User Settings).

    Value Notification, Print Appraisal Notice PP, rn 9035x, 001

  • Personal Property notices now include the following:
    • Assessor information (depends on configuration)
    • The Listing Postmarked date; if the late filing fee has not been imposed, then this field displays the word Timely
    • The Penalty %
    • A notification similar to the following, adjusted to your penalty configuration (in PACS.ADMIN, choose Tools > Personal Property Rendition Maintenance > Configure Penalties): Penalty for failure to file on or before April 30th is 5% per month (or fraction thereof) that the filing is late, up to 25% of the following years’ tax amount.
    • A customizable notification; the intention is that this notification addresses non-filings
    • Appraiser’s name (this is the last appraiser listed on the record in PACS)
    • Brief legal description (depends on configuration)

    When the Notice of Value is generated for a Master Lease Account, the text “Leased / Distributed / Rental Personal Property” displays at top. The current Asset Detail Listing page groups the sub properties by their Master Lease account, and includes their tax area, market value, and their total cumulative total value. A separate Sub Accounts page generates for Master Leases, displaying each sub account’s ID, total assessed value, and tax area.

    The Exemptions section on printed notices now indicates when an Improvement or Improvement Detail has a Historic exemption adjustment or Remodel exemption adjustment. (Improvement and Improvement Detail Adjustment Code Files are designated in PACS.ADMIN and added to Improvements or Improvement Details.)

Property Record Options

  • (20595) When setting up Property Sub Type code files, Mobile Home is now included with Real when choosing the sub types corresponding primary Property type (Tools > Code File Maintenance > Property > Property Sub Type).

    Property Sub Type code file, 9035x, 001

    This change allows users to choose a Property Sub Type on Mobile Home type property (open Mobile Home type property and expand Identification panel).

    Mobile Home Prop, Identification panel, Prop Sub-type, 9035x, 001

Rendition Processing

  • The Clear Rendition Penalty Flag option is now available (Activities > Rendition Processing > Clear Rendition Penalty Flag). This process clears the Impose Late Filing option in the Rendition Penalty Dialog (expand Personal Property view Rendition panel and click Penalty button). The Import Fraud Penalty option remains unchanged.

    Rendition Processing, Clear Rendition Penalty Flag dialog, 001, 9035x

Fixes

ID

Description of Update

Accounting

22841

Attempting to close out a revenue account that had a long account description caused an unexpected error (Activities > Accounting > Close Out Revenue Accounts). Descriptions longer than 100 characters are now truncated, resolving the issue. (This was discovered during beta testing but was an existing issue.)

Bill Adjustments

21225/
HS 108867

When adjustment credits were applied to bills, credit amounts unexpectedly included amount for delinquent P&I (on a property with a paid up prior-year statement, supplement the property in that year, lower the property’s value, accept the supplement and create and activate bills, applying the newly-created credit to the remaining bills due on the statement). The coded calculations for delinquent penalty, delinquent interest, and bond interest on adjustment credit bills and fees has been modified to correct the issue.

Concerning adjustment credits, delinquent P&I applies when a taxpayer pays toward the base due and delinquent P&I, but adjustments have eliminated or reduced the delinquent amount. In this instance, some or all of the delinquent P&I is refunded to the taxpayer with the base amount.

Change Log

22760

The change log now records when and who made changes to the chg_log_columns table (Tools > Change Log > Administration). This data can be viewed in the database. (Tracking this data cannot be turned on/off through the user interface.)

Code Files

20595*

The Property Type drop-down list in the Property Sub Type code file dialog box now displays the Mobile Home type as Real/Mobile Home (in PACS.ADMIN, choose Tools > Code File Maintenance > Property). Also, Sub Type code files with the Real / Mobile Home Property Type selection are now available when editing MH type property records (the Property Sub-Type option on the record can be found on the Identification panel).

22434/
HS 116137

The design and function of the code chooser used for adding and removing property group codes to properties has been modified (click Add in the Property Group Codes section of the Property Codes panel of the Property view). Previously, using the code chooser to change codes resulted in the removal of any codes previously assigned to the property; users can now choose to add codes by selecting the List selection appends items option in the Property Group Codes Selection dialog box/code chooser.

22494/
HS 116726

The user had to assign a letter type when creating Inquiry Status and BOE Inquiry Additional Status code files (Tools > Code File Maintenance > BOE Maintenance). Doing so is no longer required.

Comparable Sales

21239/
HS 111539

The Residential Time Adj PCT/MO, Commercial Time Adj PCT/MO, and Land Time Adj PCT/MO fields now accommodate up to four decimal places. These fields are displayed in the Miscellaneous section of System Wide Configuration in PACS.ADMIN (Tools > Comparable Property > System Wide Configuration).

Current Use

11753

The following functionality has been added to PACS Current Use module:

  • Current Use Code files now include the attribute option Public Benefit Rating System. (Tools > Code File Maintenance > Current Use)
  • The Land Detail dialog now includes the Public Benefit Rating System % field in the Productivity Valuation panel. This field is set to 100% by default, and is enabled for land details that have a Current Use Code file with the Public Benefit Rating System attribute selected in the Use Code field

When a Land Detail is assigned a Current Use Code file with the Public Benefit Rating System attribute selected,

  • In the Land Detail dialog box’s Productivity Valuation panel, the Calculated Value option is selected and its value = [Market Value * PBRS Percent]
  • The user can modify the Public Benefit Rating System %, which causes the Calculated Value to change
  • The Appraisal Method field, Table field, Unit Price field and Show Schedule button are all disabled

Note The Change Log records the code selection, and the PBRS % value is copied to new year layers.

Events

22125/
HS 115392

An unexpected error occurred when modifying an event object (in property Events panel, select event and click Details, click Open in Event Objects panel). The system now handles instances when no date is entered, resolving the issue.

Exemption Processing

20999/
HS 109725

After a change to the dialog box type, the Permit # field in the Permit Information section of the Remodel Information Detail Dialog box now accommodates both numeric and letter entries (from the Property view, expand the Values panel and click Remodels).

21376

Opening an existing total exemption detail through the Property view Tax Area, Exemptions & Special Assessments panel and then cancelling out of the detail dialog resulted in the user being prompted to save, though no actual changes had been made. This occurred because PACS tried to write a default income record (which only senior/disabled exemptions should have), leaving an indicator that a change had been made. (This did not cause any data errors.) The exemption Income Information grid in the Property Exemption Details dialog box no longer attempts to write a default record unless the grid is displayed, as is the case for senior/disabled exemptions.

General

19580/
HS 103940

After deselecting Exact Match in the User Settings dialog box, the option was automatically selected again on reopening the dialog box (Settings > User Settings). The controls for the menu options in this dialog have been modified, correcting the issue.

22346/
HS 115033, 22302/
HS 116214

The GISUpdatePACSImage stored procedure, which adds images to properties, did not include imprv_id as expected. This stored procedure did not call the Middle Tier. Now it has been modified to look and work as expected. Also, an inconsistency in how images are stored has been reconciled. Additionally, Ref IDs are now set to 0 as follows: (a) for Property-level Images, Ref ID# is 1, 2 and 3; (b) for Improvement-level Images, Ref ID# is 2 and 3 (Ref ID 1 is used for the Improvement ID).

22666/
HS 117607

Scripts that run during PACS’s installation have been updated to ensure nothing is missing.

Importing & Exporting

16749/
HS 93505

Users can now redo a REET export (Export > Export REET Recorded Information). After initially performing an export for a given date and being notified of errors, the user can rerun the export for the same date after correcting the errors. Attempting to do so causes a confirmation message to display, asking if the user would like to redo the export.

21998/
HS 114263

An unexpected error was produced while performing the NCOA Import (Imports > NCOA). The error was the result of the system being unprepared for parts of the import file’s formatting and content. The fix required a few changes: the import process now (1) discards lines that do not have a numeric owner ID or year, such as the header row, (2) handles instances where the address is an exception instead of a real address (exceptions are still listed in the import), and (3) discards records with duplicate owner IDs. These fixes resolve the issue.

22208/
HS 115705

Importing a payment file caused an unexpected error (Import > Import Payment Run). The import file included at least two property IDs that were recorded as the number 0, which is invalid. The database to which this data was being imported had bad data issues as well, which affected the import performance. As a resolution, the system’s payment import code has been modified to prevent issues like this by rejecting the import with an error message when they contain zero or negative number statement IDs. Additionally, the system displays a specific error message when a user attempts to import and process an unassociated fee.

Income Valuations

22636/
HS 117535

Income information displayed in the Income Information grid of the Land Segment detail whether or not the Include option was selected on the same Land Detail displayed in the Land Details grid of the Improvement & Land Designations panel of the Income Detail view (open the Income Detail view by choosing the Details button of an Income Valuation record in the Property view Income Valuations & Characteristics panel). This issue has been resolved by fixing the way Land Details are filtered for display.

22807/
HS 118235

Adding a Land segment from a different PID to an income valuation generated an unexpected exception error (from Property view, expand Income Valuations and Characteristics panel, go to Improvement and Land Designations panel, click Add in the Land Details grid). The grid toolstrip has been fixed, correcting the issue.

Letter Processing

21360/
HS 109266

Property-type letter details such as the letter’s Name and Description could not be edited when Enable Event was selected (create new letter from Word Letter Processing Maintenance menu). The details dialog is now enabled as expected regardless of event status.

Levy Certification

21006/
HS 110900

During Levy Certification, as evident from the Levy Calculation Summary Report, New Construction Values were excluded for properties that were involved in an active Tax Area annexation in the current year (Activities > Levy > Levy Certification, select a levy certification run and click Details, then expand the Tax District Summary panel; from there, select a levy or levies in the grid and click Print). This issue has been corrected.

Litigation

22899/
HS 119111

An unexpected error occurred when removing a property from a litigation record (from the Litigation view Properties panel, Properties grid). This error was not reproduced internally. However, a related error that occurred while using the arrow key to navigate through properties in this grid was discovered and corrected.

Marshall & Swift

21307/
HS 111674

The default Base Date for commercial M&S is 01/01 in the property’s year. A validation error displayed unexpectedly when the current date (according to the system clock–not the PACS posting date) was earlier than the default base date. Now, when this occurs, the default base date is set to the current posting date.

22901

Various issues tied to Marshall & Swift have been resolved. Development made changes allowing support for the .NET framework 4.0 with the Marshall & Swift engine, and they addressed a number of other conflicts.

Mass Maintenance

22537/
HS 117157

When mass updating Land new construction values, PACS did not retain the value because the New Construction Value Override was not being automatically selected in the process (Activities > Mass Maintenance (Property) > Mass Maintenance > Mass Update). This issue has been corrected.

Notice Processing

22446

The appraiser name displayed on personal and master lease account property appraisal notices is now the name of the Review Appraiser listed on the Personal Property panel instead of the Last Appraiser from the Appraiser Info panel. This is partially a change from functionality in 9.0.34.2109 (and prior).

22756

The Filing Status was not retained on Appraisal Notice runs (Activities > Appraisal Notices > Appraisal Notices Maintenance, perform the notice selection process with a Filing Status selection, then close out and return to Appraisal Notice Maintenance and view details of same run). This issue has been resolved.

Payment Processing

22848/
HS 118535

An unexpected error was generated after entering an invalid property ID in the quick post dialog boxes, receiving an invalid ID warning, and then entering a valid Property ID (Activities > Posting > Quick Post: Single Payment). An issue with the search text box retaining info incorrectly has been resolved.

Payout Agreements

22110/
HS 111804

An unexpected error occurred when generating payout statements because defaulted agreements were included, causing the system to count properties twice when collecting data for the statement (Activities > Payout Agreements > Generate Special Assessment Payout Statement). Payout agreement statement runs now include only Active payout agreements.

Property Record Options

21540*

Existing depreciation schedules were not available for selection in the New Property Wizard (import schedule in PACS.ADMIN through Tools > Schedule Maintenance > Depreciation Schedule Maintenance; File > New > Property, select Personal property type, navigate through the Wizard and then, after adding sub-segments, click Depreciation). The issue preventing schedules from populating the grid has been resolved.

21324*

An Asset ID column now displays in the Sub Segments grid in the Personal Property panel of the Property view, and on the Sub Segments panel in the Segment Detail dialog.

Property Search

21308/
HS 111831

Non-mailing address types did not display in the Property Search Results list because the system sought main addresses only. Now the mailing address is sought out first, and any secondary address is displayed when no mailing address can be identified. Note that the property search results display the collections owner’s address when performed by a user in the Treasurer role, and the property owner’s address when performed in the Assessor role.

22704

Using the Recheck Date option in the Property Search view Other Search Criteria extended panel did not return the expected results. Though it had not been previously, this field criterion is now included in the query.

Receipting

20965/
HS 110858

Overpayment credit receipts did not display the account to which the payment was posted (from Property view, expand Payment History panel, select refund payment and click Details, then click Reprint Receipt in the Refund Detail dialog box). This issue has been corrected.

21436/
HS 112338

When Require Ref. Number for Check or MO Tendered was set to False in PACS.ADMIN System Configuration, not all expected checks displayed on receipts (Tools > System Configuration > Post Payment > Require Ref. Number for Check or MO Tendered). Without the reference number, the query that gathers receipts pared down results by ignoring results with identical values. This query has been modified to include all checks.

REET

19814/
HS 105267

Entering a future Date of Sale (later than the current date) is now permitted when creating a new REET record (File > New > REET). When doing so, a warning is displayed. Note that entering a future date of sale can potentially cause issues with the REET export (Export > Export REET Recorded Information).

21178/
HS 110398

The Electronic REET Import failed because the process was not correctly assigning the REET IDs from the import file (Activities > REET > Electronic REET Processing). This issue has been resolved.

22106/
HS 115327

The REET import via Electronic REET Processing failed unexpectedly (Activities > REET > Electronic REET Processing, choose Import File). Part of the issue was that the import brought a decimal value to a field the system had formatted for integers; also, the import file included a date foreign to SQL. The system field is now prepared for decimal values; and a graceful error will be issued when an incoming year value is unreadable (i.e., prior to 1900). In case of the second event, import files must be corrected before processing successfully.

Refunds

21658*

When moving from the Payout Agreement Wizard to the Payment Cart, the payoff amount displayed in the cart was incorrect (Activities > Payout Agreements > New Payout Agreement). This amount calculated based on the schedule, and included bond interest accrued on payments with due dates after the payment date. The Payoff Statement Report also displayed the unexpected values (from the Payout Agreement view, choose Commands > Print Payoff). This calculation issue has been resolved.

Rendition Processing

21282*

A user opened multiple copies of the Rendition Penalty Dialog box (expand Rendition panel in Property view and click Penalty). This issue has been resolved by disabling the Penalty button when the Rendition Penalty Dialog box is open.

21313*, 21995*

In 9.0.34.2108, ticket 21313 developed functionality allowing users to automatically set a penalty fee on Properties for which taxpayers did not return a rendition. However, the expected penalty info was not being displayed in the Rendition Penalty Dialog on the property (from the Property view Rendition panel, in the Rendition section, select the rendition and click Penalty).

Further development to correct these issues and meet user expectations has resulted in the following changes to the Rendition Penalty Dialog (when a penalty is applicable):

  • For properties whose owners have filed, but filed late, when opened, the Rendition Penalty Dialog now updates and displays the appropriate rendition penalty according to the scheduled if there is no override.
  • If the user chooses to undo a previous override, and the scheduled penalty is different from the penalty previously set via the override, a message is displayed.
  • For properties whose owners have not filed, no penalty is selected or displayed (until the set rendition penalty process is run).

Note the following:

  • Events for rendition penalties and waivers are now more detailed. Events are generated for adding or changing the penalty (with the penalty value included), or for removing the penalty, and for adding or removing waivers. These events are Assessor system-type events, and the responsible user is recorded and displayed instead of System. No event is generated simply because the Rendition Penalty Dialog was opened and closed.
  • The mass functions for setting and clearing rendition penalties also generate the revised events.
  • The user can no longer open two copies of the Rendition Penalty Dialog.
  • A different, earlier version of the Rendition Penalty Dialog is shown for years 2004 and earlier, and it displays the expected data.
  • Choosing Override allows the penalty to be freely changed, regardless of waivers or schedules.
  • Absent an override, choosing a Waiver that grants a waiver clears and disables the rendition Penalty field.
  • Absent an override, waiver, or scheduled penalty percentage value, the user can freely impose, change, or remove a penalty.

21339*

The Notice Penalty field displayed in the Personal Property Rendition Maintenance Penalties dialog box has been removed (Tools > Personal Property Rendition Maintenance > Configure Penalties). The value entered/recorded in this field played no role in calculating and assigning penalties.

21351*

The Print Duplex option displayed in the Print Personal Property Rendition Application dialog box was selected by default (from Property view, Commands Menu > Print Personal Property Rendition Application). This would cause two copies of each rendition to print. Print Duplex is now unselected by default.

21375*

The Both Non-Farm and Farm option in the Print Personal Property Rendition Application dialog box was selected by default (Commands > Print Personal Property Rendition Application). For convenience, the Non-farm option is now the default print option.

21428*

The user was unable to add Group Codes while navigating the Personal Property Rendition Wizard (Activities > Rendition Processing > Personal Property Rendition). The toolstrip’s association with the Group Codes grid has been restored, resolving the issue.

21542*

Attempting to save a depreciation table without choosing a DOR Schedule code file caused an exception error (Tools > Schedule Maintenance > Depreciation Schedule Maintenance, click Add). A more graceful error is now displayed in this instance.

22017*

When printing rendition penalty letters, using the Query option did not produce the expected results because the dialog box checked for specific syntax in the query and often did not find it. This overly sensitive syntax check has been corrected in the following functional locations: (1) Print Rendition Penalty Letters (Activities > Rendition Processing > Print Rendition Penalty Letters); (2) print BPP Penalty Waiver Letter (Activities > Rendition Processing > Penalty Waiver Letter); (3) Print Property Rendition Applications (Activities > Rendition Processing > Print Personal Property Rendition Applications); (4) Print Request for Supporting Documentation (Activities > Rendition Processing > Request for Supporting Documents Letter).

22062*

Personal Property Rendition Applications printed with a single line of text on one page (Commands > Print Personal Property Rendition Application; Activities > Rendition Processing > Print Personal Property Rendition Applications). The text has been rearranged to correct this issue. Note that, due to pagination issues, choosing Print Duplex may result in a blank page printing out at the end of the application.

22079*

When printing BPP rendition penalty letters, the Skip Letters Already Printed option failed (Activities > Rendition Processing > Print Rendition Penalty Letters). On initial printings, the system did not update itself properly. The updating mechanism has been corrected.

22081*, 22548

Users can now generate a preview from the Print Rendition Penalty Letters dialog box (Activities > Rendition Processing > Print Rendition Penalty Letters). Additionally, when printing, users can select their printer.

22659/
HS 117460

The barcode on the Personal Property Rendition Application has been suppressed, and will no longer display (open property, choose Commands > Print Personal Property Rendition Application).

Reports – Assessor

19615

For each sale listing, a new Document Type column has been added to the DOR Invalid and Valid Sales reports (populated from deed_type.deed_type_desc joined on chg_of_owner.deed_type_cd) (Reports > DOR > Sales > Invalid Sales Report, Reports > DOR > Sales > Valid Sales Report). These reports are now formatted in landscape to best fit in all required info. This change comes in response to a legislative change.

21020/
HS 111004

Properties that were part of multi-property sales displayed more than once in the Valid Sales Report (Reports > DOR > DOR Sales Report). Additional filtering measures for handling multi-property sales have been added to the report’s generation.

Reports – Treasurer

21136/
HS 111074

The Certificate of Delinquency displayed the property owner’s name rather than the collections owner’s name (Commands > Generate Certificate of Delinquency). The information is now drawn from the account owner and not the property owner, resolving the issue.

21137/
HS 111098

Formatting on the Certificate of Delinquency has been improved (from Property view, Commands > Generate Certificate of Delinquency).

21272/
HS 111715

Formatting on the Petition for Refund has been improved (from Property view, Commands > Petition for Refund).

21370/
HS 112170

Formatting on the Excise Detail Report has been improved (Reports > Excise Detail Report).

21649*, 21650*

Expected property and tax information did not populate on the Certificate of Delinquency when it was generated from a Personal property (from Property view, Commands > Generate Certificate of Delinquency). Personal properties were previously excluded; this has been corrected. Additionally, the Late Filing column was removed and some formatting enhancements were made.

21685

The Collected Escrow Applied Report was improved; this includes setting the report to generate landscape, adding the county name and version, inserting a box around the header, expanding the Property ID column, modifying Total label to Grand Total, plus remedying other minor issues (Reports > Escrow > Collected Escrow Applied).

21747

The Escrow Value Listing Report was improved; this includes adding the county name to top of page with a full header, sorting on Property ID then tax year then difference, and aligning data carefully (Reports > Escrow > Escrow Value Listing).

22265/
HS 115845

Just prior to release 9.0.34.2108, issue 21744/HS 113719 stated that, on the REET Collections Daily Recap Report, values representing the amounts collected on a given day were inconsistent between reports run per day and reports run for the month (Reports > Daily > Daily Summary). To resolve the issue, values for each day in the report period were set to calculate separately, with daily values summed together at the end.

Subsequently, interest and penalty amounts were reported as no longer being separated out into individual line items on the report anytime Group by Tax District was not selected. To fix this issue, the non-grouped version of the report again shows only base values. Also, for non-Tax Districts, the Amount Collected column is now titled Base Amount Collected, clarifying that P&I are intentionally not included.

22806/
HS 118187

An unexpected error occurred when trying to generate the Annual Financial Report (Reports > Monthly > Annual Financial Report). The report’s unique ID entry has been restored, resolving the issue.

Sketches

22257/
HS 115911

Users had to take the unexpected step of right-clicking and associating the sketch to an Improvement Detail because, when the sketch drawing was opened from the Improvement Detail, the automatic association was scrapped to allow expansion of Non-Associated areas during the drawing session. Now, the association is restored once the expansions are complete, so users can select any Improvement Detail and associate a sketch with that element.

22487/
HS 116837, 22488/
HS 116846

Instances of creating, modifying, and deleting sketches did not record in the expected PACS database images tables. Changes to the recording of these actions in the database now mean the following: (1) creating a sketch from the Property view (Commands menu) adds the entry to the property_sketch table and the pacs_image table with the pacs_user_id of the updating user; (2) deleting a sketch from the Property view (Commands menu) removes the entry from the property_sketch table and the pacs_image table; (3) creating a sketch from the Improvement dialog (Sketches button) adds the sketch entry to the imprv_sketch table and the pacs_image table with the pacs_user_id of the updating user; (4) deleting the sketch from the Improvement dialog (Sketches button) removes the sketch entry from the imprv_sketch table and the pacs_image table.

Note that the entries in the pacs_image table for both the property and the property improvement have two entries–one for the image itself and one for the thumbnail.

Split-Merge

22349/
HS 115786

Expanding either a Land or Improvement Detail from the Wizard that processes property splits resulted in an expected exception error (Activities > Split Property). This occurred because the split process code was not current and compliant with changes to how the system handles the number of lots values. This issue has been corrected.

22366/
HS 116447

Attempting to perform a property split that included multiple properties with Current Use resulted in an unexpected error (Activities > Split Property). The code for selecting Land details was copying those details too much. Furthermore, in some cases an integer was expected in the Number of Lots field, and decimal values caused errors. These issues have been resolved.

Special Assessments

20926

The Exemption Amount field incorrectly displayed as zero (0$) in the General panel of the Special Assessment Bill dialog box (in Tax Due panel of Property view, select a statement in the Special Assessment Bills grid and click Details); this occurred on imported special assessments with exemptions (Import > Special Assessment, process the import, then create and activate bills). A calculation problem with flat fees has been corrected, resolving this issue. (This issue stemmed from project testing for a prior release (33.x) and is included here because it was an existing functionality issue.)

Supplement Processing

21004/
HS 110586

The user name displayed in the Prepared By field in the Supplement History panel was cleared after a property was moved from a pending supplement group to an active supplement. This info is now preserved when moving a property between non-zero supplements within the same year.

22937

A supplement and change of value were not reflected on the property’s notice. In this instance, the property was put into the pending supplement from a coding supplement group. A subsequent attempt to move the property back into the coding supplement prompted a warning that the property was already in the supplement group, at which point the property appeared to be in both supplement groups. This issue, which was discovered during beta testing but appears to have been pre-existing, was resolved by resorting and prioritizing the multiple threads of property data copying executed during the the supplement process.

Tax Statements

21357

The code that generates tax statements has been improved. The time required to generate statements should be down from around 1.5 seconds to less than 1/4 second per statement.

22099/
HS 114961

A property’s prior year levy bill value was missing when the same levy’s current year rate was 0 with no bills created; this error also required the levy’s district to include multiple levies–at least one being a voted levy and another non-voted. The code has been modified to gather the expected values.

22200/
HS 115670

Messaging configurations on corrected tax statements did not work as expected (Commands > Create New Tax Statement). Development has made the following changes to the Important Information section:

  • First, the default message has been changed to “If your mortgage company pays your taxes, this statement is only informational. Delinquent payments received without correct interest and penalty will be returned. Postal service cancellation mark by the due date is the only proof of timely payment.” (The issue calling for this change–some of the text was omitted–was a result of a conflict between statement character lengths and Crystal report thresholds.)
  • Second, the supplement reason did not display when expected. When gauging whether to show this message, the system now checks if tax_statement_config.supplement_reason is True (a value of 1 in the database) and wa_tax_statement.supp_reason is Not Null.
  • Finally the system now gives the message display the following priority: (1) delinquent notice comment, (2) supplement reason, (3) tax statement configuration message, (4) default text. (Previously, it was (1) supplement reason, (2) tax statement configuration message, (3) delinquent notice comment, (4) default text.)

22415/
HS 116319

The second half-payment tax amount due did not display on the second payment coupon when the statement for the second half was generated from the Commands menu and/or taxes were delinquent. An issue with the time stamp complicating matters has been resolved.

22551/
HS 117221

Tax statement 1st half payment coupons printed on a second page, causing the whole statement to require three pages (Commands > Create New Tax Statement). The payment coupon portions of the statement have been reformatted, the primary change being to move white space from the top of the coupon. This resolves this issue.

22767/
HS 117950

The generic Real tax statement message was not displayed on notices as expected (in PACS.ADMIN, choose Tools > Code File Maintenance > General > Tax Statement Messages, give highest priority to a delinquent message code followed by one for owner messages on which the only criteria is that it be for Real property types, then open a property with current year taxes due and none delinquent and choose Commands > Generate Corrected Tax Statement). This issue has been resolved. The default message is: If your mortgage company pays your taxes, this statement is only informational. Delinquent payments received without correct interest and penalty will be returned. Postal service cancellation mark by the due date is the only proof of timely payment.

* Discovered during client beta testing of a previous release

Suggest edit
Last updated on December 8, 2018
Suggest Edit
%d bloggers like this: