1.9.0.40.2000 Release Notes #

New Features

DOR Stratification Real Property Report

The DOR submits a request to each county for their Real & Personal Property Stratification Reports each year; the DOR also gives the county strata to run the reports. Certain counties are required to submit reports not currently supported by the Real Property Stratification configuration.

The DOR Sales Reports will be affected by these new changes.

  • The ability to select the primary use codes included in each stratum of the DOR Stratification Real Property Report is needed to ensure each County can accurately report specific requests from the DOR.
    • The Primary Use codes currently mapped to DOR Use Codes when the release is deployed will provide a default selection for the stratification settings. This will allow clients to report in the same manner if they choose not to make any changes with the new functionality.
      • User will go to PACS.Admin > Tools > Stratification Settings Maintenance > Select Details or Add New.

40_1

  • Where ‘Use Separate Current Use Group’ is NOT checked
    • Single Family Residential – select ALL primary use codes mapped to DOR use Code with attribute ‘Residential’
    • Multi Family/Commercial/Manufacturing/CU-AG/Other – select ALL primary use codes mapped to DOR Use Code with attribute ‘Commercial’, ‘Industrial’, ‘Multi Family’, ‘Current Use’, ‘Other’, ‘MH Park’
  • Where ‘Use Separate Current Use Group’ is checked:
    • Single Family Residential – select ALL primary use codes mapped to DOR Use Code with attribute ‘Residential’
    • Multi Family/Commercial/Manufacturing – select ALL primary use codes mapped to DOR Use Code with attribute ‘Commercial’, ‘Industrial’, ‘Multi Family’

Because the Current Use indicator controls the use codes included in each stratum, changing the indicator requires user review. If the state of the ‘Use Separate Current Use Group’ check box is changed (checked or unchecked), the user will receive the following notification

40_2

  • In addition to the existing mapped primary use codes, each client office is able to include or exclude primary use codes from the default selection for each stratum through a NEW button ont he report configuration.

NOTE: This is intended to allow each office to meet the county specific DOR reporting requirements. The County is responsible for reviewing these situations.

  • If a Use Code is selected in an existing stratum and the new ‘custom’ stratum described below, a property with that Use Code is expected to display in only that exiting stratum. The property will not display in the custom stratum.
    • PACS.Admin > Tools > Code File Maintenance > Land > DOR Use Code
    • 40_3
    • PACS.Admin > Tools > Stratification Settings Maintenance > Details40_4
    • Select Use Codes
    • 40_5
  • To allow further flexibility in reporting, new functionality to add a ‘custom’ stratum to the Real Property Stratification report settings has been added.
  • 40_7
  • 40_8
    • The new custom stratum will populate the DOR Stratification report in the same manner as existing strata
      • The new ‘custom’ stratum will be available regardless of whether the ‘Use Separate Current Use Group’ is selected
      • The user is able to enter a label for the stratum. This will display in the Stratification settings dialog and print on the report as consistent with the other strata labels.
      • The user is able to select primary use codes to include in the stratum, similar to the functionality described above.
      • The primary use codes available for selection will NOT be limited by the DOR Use Code attribute.

NOTE: Special care should be taken when the custom stratum is used and all strata reviewed for duplicate use codes in the selection. This may cause property entries to not display as part of the custom stratum in the report. The user will be responsible for reviewing these situations.

  • The user indicates the following fields in the same manner as existing strata: Stratum Beginning Value, Stratum Ending Value, Sampling Frequency, Starting Point.
  • The DOR Real Property Property Stratification report will recognize and report only the Primary Use Codes selected as described above for each strata, including the custom strata
  • 40_9

NOTE: The Personal Property Stratification settings and report will NOT be modified for the changes above

 

DOR Sales Report

  • The DOR Sales report was modified to display the strata as configured
  • 40-10

40_11

40_12

DOR Composite Tax Rate Report

The DOR Composite Tax Rate report has been modified to render the appropriate land value correctly. Additional modifications were needed to limit how the value is selected for the report. This was a result of the selection including sales values in error.

The Composite Tax Rate Report lists the DFL value and taxes for each district, then shows the calculation of the composite tax rate, the total tax divided by the total DFL value. Originally the report used the sum of the DFL values in the table as the total, but since a single property falls into multiple tax districts, this counted the DFL values mulitple times. A separate query for the total was added to correct this in Release 9.0.37. Now the report has been updated to use only land detail records where sale_id = 0. Land detail records with sale_id > 0 are records associated with a sale and will not be included in the report.

 

DOR Assessor’s Certificate of Assessment Rolls

PACS has been calculating the values for the DOR Assessor’s Certificate of Assessment rolls using code shared with the DOR Sales Report. It was possible for value to be lost if the property did not fit into the stratification ranges defined for the DOR Sales Report

40_13

PACS now calculates the Assessor’s Certificate with a separate query with modifications:

  • Current use value is split between the first three lines
    • Designated Forest Land
    • Other Land
    • Improvements on Current Use Land
  • The senior amount on line 4 is the amount that can be taxed, after being reduced by productivity, frozen value caps, and senior exemption lists.
  • If a property has both current use and senior values, then some of the taxable senior value may also be current use value, which should be added to lines 1-3 instead of line 4
    • PACS does not store the frozen value of current use separately so the value must be estimated
    • The report estimates based on the percentage of current use value to the total SNR value multiplied by the frozen SNR value. The example below shows the calculation:
      • Total SNR = 100,000
      • Frozen Value = 25,000
      • Current Use Value = 5,000
      • Percentage CU – SNR = 5,000/100,000 = .05
      • Reported as appropriate current use value = .05 * 25,000 = 1,250
      • Reported as SNR value = 23,750
      •  

PACS Treasurer New Features

AP Import

A client request initiated changes to the AP Import. A process bar now displays for the import.

40_14

40_15

Destroyed Property

When a destroyed property is processed through a supplement on a property that has a senior exemption, it appears that the senior exemption is not being accounted for when looking at the final amount of tax due. PACS now recognizes the exemption and appropriate appraised value for a SNR property with destroyed property.

NOTE: Exemption proration and destroyed property together WILL NOT calculate. If both are on the same property/year, a warning message is displayed and only one proration has an effect.

DOR Report – Statement of Taxes Collected

The Statement of Taxes Collected report has been updatIn oded for the new distribution associated to the State technology fee. The enhancement is a temporary workaround until additional attributes can be added for REET fees. This is a Release 41 initiative.

We’ve broken line 12 into two elements:

  • Line 12 = (PACS REET State Fee x 2)
  • Line 12a = (PACS REET State Fee)
  • 40_16

 

Escrow

Recent legislation was introduced to address flexibility for taxpayer payment of property taxes. The senate bill referenced payment agreements between the Treasurer and a taxpayer for delinquent taxes and for current year taxes. Discussion has been had regarding how PACS will facilitate a method for the Treasurer’s office to accept payments outside of the standard due dates. Currently, tax bills are due on April 30th and October 31st. In order to address different interpretations supported by client offices and to account for reporting issues with the existing escrow module, the following enhancements have been developed:

Current escrow functionality, prior to enhancements in Release 40:

  • An escrow can be set to half pay or full pay up until a payment is made to escrow
  • Payments made to an escrow can be full or overpayment credit. Partial payments are not allowed
  • An escrow can be applied only when it is paid in full. Half pay escrow cannot be applied
  • Escrow can be applied individually or with Mass Apply escrow wizard
  • The entire amount of escrow credit must be applied
  • PACS compares the escrow to the amount due and chooses the payment type code (full, overpayment credit, etc) automatically
  • Escrow can be created to include property taxes due or delinquent and an additional collection fee. This was required by the legislation as part of a payment agreement.
  • Multiple escrow payments can be made to a property but these are kept separately. If applied they are applied separately which can affect penalty and interest calculation.

In order to meet the reported needs of our clients, we have designed the concept of escrow ‘credit’ or flexible escrow. This is intended to account for creating, maintaining, applying and posting escrow in the most flexible way possible:

  • Where a taxpayer may make payments toward an ending balance. This is similar to existing escrow where theuser can use the escrow worksheet or enter a value for escrow.
  • Where a taxpayer may make a payment as a credit balance for future use. This is similar to overpayment credits.
  • Where escrow can be applied without limitations. This is not year specific or necessarily full or half pay.
  • Where payments made as flexible escrow can be kept as a single balance, where new payments add to the total escrow credit and applied escrow reduces the total escrow credit.
    • Example: Escrow created for ending blance of $100, if escrow is applied before the full amount is paid, additional payments are due.

40_17

Using the new flexible excrow will allow a user to make partial payments to an escrow record, view all payments and applications of the escrow record and print receipts for each payment.

  • Escrow types can now be marked as “flexible escrow” in the escrow type code file in PACS.Admin.
  • Using the flexible escrow type coe, a record can be created on a property allowing multiple payments and application. Flexible escrow can be applied toward half, full, or installment items on any property in any year, similar to overpayment credits. Amounts in excess of the amount due will reamin available in the escrow record.
  • 40_19
    • Pay into Escrow (Partial Payment)
    • 40_20
    • Make a second payment into Escrow (Partial Payment)
    • 40-21
    • The Escrow records reflect the two payments in the paid column with a status of partially paid.
    • The NEW Escrow payment history shows an accurate audit trail for each payment
    • 40-23
    • From here, the Escrow can be applied
    • Apply Escrow credit
    • 40_25
    • Payment Cart View, select the appropriate items to pay. Notice the remaining Escrow Due of $25 displays as an option due, remove before proceeding
    • 40_26
    • 40_27
    • Post Payment
    • 40_28
    • The Escrow record reflects the application of Escrow, displays the remaining balance and indicates a status of Partially Applied
    • 40_29
    • The NEW Escrow Payment History continues to display the transactions
    • 40-30

For the dialogs, panels and reports associated with Escrow, the following modifications have been made:

  • The Escrow/Overpayment panels:
    • New Statuses for flexible escrow will display; i.e. Partially Paid, Partially Applied, and Paid
    • The toolstrip buttons will be enabled using the relative values of the amount fields. Allow escrows to be deleted only if they don’t have any transaction applied.
    • Change “Print Receipt” to “Print Receipts” and print receipts for all of the posting payments, not just the latest one.
  • Escrow Details dialog (non-worksheet)
    • The amount applied on escrow and new expanded status codes display
    • The options “View Posting Payment” and “View Applied Payment” have been removed and replaced with a “Payment History” panel. Payment details are available to view.
    • The details of the escrow can be edited only when the escrow’s amount paid is zero.
  • Escrow Worksheet dialog:
  • 40-31
    • The options “View Posting Payment” and “View Applied Payment” have been removed and replaced with a “Payment History” panel. Payment details are avaliable to view.
    • The details of the escrow can be edited only when the escrow’s amount paid is zero.
    • The amounts paid and due and the current escrow status are not shown in this version of the dialog.
  • When applying a single escrow to property or multiple properties from Activities> Mass Apply Escrow:
    • PACS will account for the NEW flexible escrow types while the non-flexible escrow types, will still be processed as expected
    • For flexible escrow types, the Property Apply Credit wizard has been modified to support escrows as well as overpayment credits and adjustment credits.
  • Escrow Reports
    • Escrow Plat Letter – Previously, the letter displays the receipt number of the single payment. Now, the letter will display the receipt number of the most recent payment.
    • Collected Escrow Applied
      • A row will display for each escrow transaction collected and applied.
      • The report will sort by property ID, then escrow ID
      • 40_32
  • Escrow Available Report
    • For the report, a row will display for each property ID having escrow available
      • Multiple escrow transactions available on a property for the same escrow ID will print as a single row on the report
      • If there are multiple escrow IDs per property, multiple rows will display in the report.
      • The report rows will display as a running total of escrow available, taking into account partially applied escrow.
      • 40-33
      • 40-34
  • Escrow Listing
    • For the report, a row will display for each escrow transaction collected and/or applied
    • 40-35
    • For Detail option of the report, a row will display for each escrow transaction collected and/or applied
    • For the Summary option of the report, a row should display for each property ID having escrow transactions meeting the report criteria.
    • 40-36

A warning will display to the user indicating that flexible and non-flexible escrows cannot be applied together.

40-37

A NEW configuration option has been added to allow a client office to disable the unpaid escrow warning

40_38

  • The System Setting ‘Display Unpaid Escrow pop-up warning for Property’ has been added under PACS.ADMIN > Systems Configuration > Property
    • When set to ‘False’, non pop-up warning is displayed for a property that has an unapplied escrow.
    • When Default is set to ‘True’, the following message will appear
    • 40-39

 

Payment Receipt

Previously, the payment receipt would suppress the property ID and/or geo ID for fees and REET transaction.

  • The change will now only suppress if:
    • the property ID is null (which would be the case if more than one property ID is involved with the fee) OR
    • the receipt is a fee associated with a REET.

 

Property Access

Previously, bills in Payout Agreement are displayed on the Taxes Due panel of Property Access without any indication that it is a Payment Agreement and not due entirely. Configuration has been added to Property Access Administration called “Toggle Payment Agreement Bills” with the option of True/False and the Help Text “Show Payout Agreement Bills”

  • When the configuration is set to False (unchecked)
    • Pay Tax Due – does not show a comment
    • Taxes and Assessments Due – does not show a comment
  • Set to True (checked)
    • Pay Tax Due
      • Displays an “*” by statement which is part of a payout agreement, and
      • This statement is part of a payment plan. Please contract Treasurer’s office for the payment schedule.”

 

Property Group Codes

As group codes become more popular and the uses more specific, a client requested the ability to filter the display of codes on a property by the role indicated is set up.

  • A property group code is configured with a “Notify Role” attribute. This can be used as a filter on the property code grids.
    • A NEW filter is available from the Property Group Codes grid.
    • a NEW column also displays the notify role used in the filter
    • 40-40

NOTE: Existing list functionality in PACS allows a user to create custom lists within the selection dialog. If the intent is to view only a few codes, a custom list can be created and codes removed from the list as appropriate. This is useful when applying the same codes to several properties without using Mass Update.

40-41

Modifications have been made to the code file maintenance of property group codes. Specifically, the comment has been enhanced to allow flexibility.

  • The “Comment” field in the grid has been relabeled “Notify Comment”
  • The Notify Comment can always be edited
  • The Notify Comment is no longer cleared when “Notify when present” is unchecked.
  • The Notify Comment is no longer a required field
  • 40-42

 

Daily Check Register Report

A client request initiated a change to the Daily Check Register report. The property ID will now display for each check payment. If multiple properties are associated with the payment, only the property with the MAX(prop_id) is printed.

40-43

Levy Rates by Tax Area Report

A client request initiated a change to the Levy Rates by Tax Area report. This will allow an option to display individual levies even when levies are linked. Previously, the linked levies were not displayed individually. The NEW checkbox will be selected by default. When the checkbox is checked, any links are ignored and the report lists all the levies individually.

40-44

Taxpayer Search

A client request initiated changes to the taxpayer search view. A NEW option to return only international addresses has been added to the taxpayer search.

40-45

 

Tax Statements

A client request has initiated a change to tax statement printing. Options have been added to allow the user to suppress statements based on criteria.

40-46

  • A NEW selection allows the user to enter an amount that will filter print statement output when selected:
    • [ ] Exclude Statements with Tax Due Less Than ________
      • This will allow a numeric value
      • This will only allow a 2 decimal places.
  • If selected, only statements with total Tax Due greater than or equal to the amount entered will print.
  • These option will display for the following:
    • Activities > Levy > Tax Statements
    • Activities > Levy > Supplement Statements
    • Activities > Delinquent Notices
    • Activities > Generate Corrected Tax Statement(s)
  • A NEW selection allows the user to print statements for properties having the SNR/DSBL exemption with zero tax due:
    • [ ] Include Statements with Zero Tax Due if SNR/DSBL
    • If selected, statements with total Tax Due equal to zero and having a SNR/DSBL exemption will print

NOTE: An option to include statements with zero tax due already exists; this is an addition to that option for only properties having SNR/DSBL exemption.

  • These options will display for the following:
    • Activities > Levy > Tax Statement
    • Activities > Supplement > Supplement Statements
    • Activities > Generate Corrected Tax Statement(s)
  • The following grid can be used as a reference if multiple options are selected:
  • 40-47

 

Tax Statements have also been modified to address value display for exemptions prorated off. If the exemption has a prorate end date, the exemption value will display as zero for multiple coupon, single coupon and taxpayer statement.

  • The Tax Statement value section will display as below values for each scenario:
    • A property with no exemptions – zero is seen
    • A property with exemption but without proration – exemption value is seen
    • A property with exemption but there are proration dates – zero is seen
    • 40-48

40-49

 

User Rights

A new user right has been added for receipting as a result of a discussion with the State Auditor’s office. This will allow separate control of limiting user ability to add fees.

40-50

  • The new user right is found in PACS.Admin > Tools > User Management > Details > Receipting
  • User set up should be verified following the release deployment

Fixes

ID

Description of Update

Assessor

20570/HS 107959

PACS was freezing during ownership transfer. The issue has been resolved.

 

 

22435/HS 116490

When adding additional properties to individual property events, errors occurred, resulting in cancellation. The issue has been resolved.

22707/HS 117649

Sketchpad default font setting saved in pacs.admin did not work in the pacs.net sketchpad application. This issue has been resolved.

22754/HS 117909

When using Quick Image scan, the effective year selected did not get pushed down to the property. This issue has been fixed.

23012/HS 119855

The DOR Composite Tax Rate was calculating off the total sum of all tax district DFL assessed value instead of the total sum DFL AV for the county. This is no longer an issue.

23349/HS 122163

When attaching event objects, users reported that the attachment indicator returned false information. This has been fixed.

23787/HS 125317

When a user created a new Property Group Code and checked the Notify when Present checkbox, PACS produced a Comment is Required message. (PACS Admin > Tools > Codefile Maintenance > General > Property Group Codes > Create New Group Code > Select Notify when Present Checkbox > Save).

24579/HS 127314

When printing Appraisal Cards with the box checked for Print Marshall & Swift Commercial Report, the cards did not print in order. This issue has been resolved.

24876/HS 129412

When an Open Space rollback estimate was completed, the Recording Fee did not save with the estimate. This issue has now been fixed.

25226/HS

120635

Land adjustments codes were not available in Mass Update. The issue has been resolved.

25354/HS 132361

PACS was not able to handle highly disputed properties and now has the mechanism to do so.

25379/HS 132937

PACS operated slowly when temporary tables were built. The issue has been resolved.

25559/HS 129675

When a new inquiry or BOE Protest Event was created and the user clicked Apply, the event details changed from what the user just inputted to the event details of the highlighted event in the Event History Grid. (Subject Property > Inquiries & BOE Protests > Protests > Highlight Protest and Click Details > Events Panel > New > Enter Type and Description > Click Apply). This is no longer an issue.

25068/HS 129832

In the sketching dialog, the Improvement Detail Grid Customization changes were not being saved. This has now been fixed.

25127/HS 130736

When the client ran the DOR Assessor’s Certificate of Assessment Rolls report, the Assessed Values were incorrect. (Application Menu > Reports > DOR > DOR Assessor’s Certificate of Assessment Rolls). The values are now reporting correctly.

25129/HS 130804

REET events were not consistently auto-generating on properties when the excise number was generated at the REET record level. This has now been fixed.

25132/HS 130848

Users were no longer able to enter or edit Comment on Property Group Codes. (PACS.Admin > Tools > Codefile Maintenance > General > Property Group Codes > Select Existing Group Code > Edit > Try to Enter Comment). This has been resolved by renaming Comment in the grid to Notify Comment.

25183/HS 131329

The DOR Stratification Report was including duplicate/multiple entries from properties that had been supplemented. (PACS.NET > Application Button > Reports > DOR > Stratification Report > Select 2013-2014 > Preview). This has now been fixed.

25881/HS 131600

Personal Property accounts were getting the penalty flag set when they should not have been. This is no longer an issue.

25882/HS 131917

A client was supplementing a property with multiple income valuations and did not have the option to set any of them as Active, causing the values to change. This has now been resolved.

25322/HS 132052

PACS was printing one page of the appraisal card when presented with more than seven lines of land segments. The issue has been fixed.

25396/HS 132963

Users reported land values disappearing when creating New Year Layer. This has now been fixed.

25410/HS 133214

When checking out properties to the penpad, the Land Detail Characteristics were not changed to what was entered. This has been resolved.

25617/HS 134954

When user would browse to PACS.Admin > Tools > Auto Build Legal Configuration, made changes, then was asked to update all legal descriptions, the legal descriptions were updated with lower case ‘s’ characters throughout the description on Mobile Home properties. This has been resolved.

25619/HS 135001

Users reported that the Land Mkt/SqFT was not returning a value. This has been fixed.

25882/HS 131917

Client was supplementing a property with multiple income valuations and did not have the option to set any of them as active, or change values. The issue has been resolved.

25891/HS 135434

When a destroyed property was processed through a supplement on a property that had a senior exemption, the senior exemption was being removed from the property from the date of destruction to the end of the year.

25951/HS 135750

Condo Property IDs were not linking. This issue has now been resolved.

25959/HS 135786

When user copied an improvement in the Schedule (Improvement Level) income grid, a Red Circle Warning remained even after the user typed in a number that fell within the required numeric range. This is no longer an issue.

26162/HS 135848

When printing a Personal Property Listing with an asset labeled Supplies, a gray box appeared over the cell. This is no longer an issue.

26385/HS 135169

Rollbacks were not consistent when moved between supplement groups. The issued has been fixed.

26443/HS 134964

Event objects related to Mobile Home Movement Module Documentation were being saved locally to the user’s PACS report folder rather than the global server. This issue has now been resolved.

26893/HS 136381

Sketches differing between appraisal cards and website. The issue has been fixed.

26894/HS 137838

Sketches were duplicating on the website when property was updated using the penpad. This issue was corrected.

27375/HS 140618

When the recording fee type was populated in the PACS.admin rollback configuration, the fee did not hold in the estimate or completed loss worksheet until the user finished the worksheet, went back into it, and reentered the dollar amount. This issue has been resolved.

Treasurer

15393/

HS 87033

Users did not have the ability to apply escrow to first half only. This option is now available.

18787/HS 100622

Bills in Payout Agreements were displayed on the Taxes Due panel of Property Access without any indication that is was a Payout Agreement. This issue has now been resolved.

18929/HS 101295

Users did not have the ability to post a partial payment to an escrow created. This option is now available.

21327/HS 83675

Users could not suppress printing statements if the amount due was less than a certain amount. New Print Statement Options have been added to the Print Levy Statement Wizard and Print Delinquent Notice dialog.

22357/HS 112472

When completing a taxpayer search, all international addresses were not returned. This has now been fixed.

22491/HS 114157

Statement IDs missing from payment import files carried over the preceding statement ID. The field is now clearing.

22979/HS 119597

Clients requested the ability to configure their system to prevent the Unpaid Escrow pop up from showing up when they opened a property that had unapplied escrow. This has now been fixed.

23475/HS 121705

When voiding out a partial payment, the cash drawer was out of balance. This issue has been resolved.

23480/HS 119421

The Levy Rates by Tax Area report did not show individual levies if the levies were linked. (Reports > Levy > Levy Rates by Tax Area > Choose Radio Button for Tax Districts- All). A checkbox field Ignore Levy Links has been added to Levy Rates by the Tax Area Report dialog.

23481/HS 123120

Agent enrollments did not show up on the Autopay Enrollment report. (Reports > Autopay > Enrollment Report). This has now been fixed.

23603/HS 124213

Clients requested the addition of a progress bar in the AP Import Module after clicking the Import button. (Activities > Accounting > AP Import > Click Green Plus > Choose Batch > Click Import).

23636/HS 124519

Prop Group Codes were not visible based on the role type (A/T/B). This has now been changed.

 

24564/HS 127166

The Exemption amount appeared on the Value Information paragraph of the Corrected Tax Statement on properties that had the exemption prorated off. This is no longer an issue.

24849/HS 128893

A new user right was created to manage fee creation.

25096/HS 130610

The Property ID associated with a fee did not appear on the payment receipt. This issue has now been resolved.

25140/HS 131005

The Supplemental Roll Report was printing the Include Tax Area Totals by Year after every property. This should have occurred after each year group. (Activities > Supplement > Supplement Group Maintenance). This has now been fixed.

25319/HS 131252

The refund amount displayed in the refund card did not always equal the amount of the actual refund or what was printed on the refund receipt. This has been resolved.

25380/HS 132933

DOR Statement of Taxes Collected Report changed due to a Legislative change. (Application Button > Reports > Monthly > Statement of Taxes Collected). This is no longer an issue.

25449/HS 133220

Payout Agreement Statement incorrectly reported the Total Remaining Collection Fee as the Collection Fee Amount in the overview section. This has now been fixed.

25527/HS 129480

Additional adjustment credit amounts were calculated incorrectly on properties that had prior refunds issued on the same statement and year. The issue has been resolved.

25805/HS 135472

The Prepare Run from Payment Import list failed and received an error. (Activities > Payment Import > Imported Payment Files > Right Click on Run > Select Prepare Run). This has been resolved.

25929/HS 135627

The billing information export was producing multiple records for a single statement ID. The issue has been fixed.

25956/HS 135808

The modified bill report was missing its header. (Application > Reports > Bills > Modified Bills Reports). This has been fixed.

25958/HS 135433

The system setting for Ignore October 31st Rule when set to True was not calculating taxes correctly based upon this rule. This is no longer an issue.

26399/HS 137079

A property showed no taxes due on the website, but PACS showed taxes due in the system. This issue has been resolved.

26369/136828

Client received an error message when attempting to print delinquent notices. The issue has been resolved.

26659/HS 137835

When a client was creating a REET record with a sales date in a prior year with multiple properties associated, an error appeared. This is no longer an issue.

26696/HS 135837

Collection fees associated with LIDs and inlcuded in payout agreements were being included on regular tax statements. The issue has been resolved.

26724/HS 137960

Tax due amounts on the property access website did not match the amount in PACS. They are now consistent.

26756/HS 137492

PACS was not calculating the refund for delinquent interest and penalties when the system setting was set to True for ”Use Original Due Date”. The issue has been fixed.

26915/HS 13811

Outstanding balance reports were resulting in SQL errors. The issue has been resolved.

26924/HS 138754

When printing a tax statement with a 10/31 effective date and current year taxes due, the 2nd half coupon was missing the mailing address and the 2 perforations were directly beneath the detail grid, rather than at the top of each coupon.

2.9.0.40.2200 Release Notes Limited #

Helpstar Defect Corrections

141378

Type codes were not changing with the improvement detail. This is no longer an issue.

141613

When attempting to create a statement of account from a property record while using all default selections, an error occurred. This has been corrected.

141895

Delinquent notices were resulting in errors. This is no longer an issue.

141941

The Administrative Refund Levy configuration panel is not populating with the necessary levies in the Map Refund Levies area to allow the configuration to be completed

142382

Payment import was resulting in an SQL error. This has been corrected.

3.9.0.40.2100 Release Notes Limited #

Helpstar Defect Correction

Helpstar

Description

141405

First Half payments were not including interest. This is no longer an issue.

141413

Delinquent years on tax statements and total amounts due were not accurate. This issue has been resolved.

Help Guide Powered by Documentor
Suggest Edit
%d bloggers like this: