Valuation Change Reason Mapping

Navigate: ClosedAsmt Admin > Setup > Valuation Change Reason Mapping

Description

Define the rules for processing valuation changes based on their associated change reason codes. This setup determines whether changes will be processed as corrections or supplements, how they will be processed, and what tax change reasons they are associated with. Valuation Change Reasons control the behavior of AA changes through configuration and map a Tax Change Reason to each Valuation Change Reason. Tax Change Reason controls the behavior of the tax roll correction and posting process.

Steps

  1. On the Map Valuation Change Reasons screen, select a change reason to specify how it will be used in corrections or supplemental roll processing.

    • Change Reason Type (Implementation Defined) – Groups reason codes for reporting and/or may control some AA calculations

      • Tax Reason Code (Implementation Defined) – Associates a Valuation Change Reason to a Tax Change Reason.  Levy uses Tax Change Reasons not Valuation Change Reasons.

    • Roll Correction Type (Platform Defined) – Specifies whether the change will cause no roll Correction, a roll Correction, a Supplemental, or an Instant Assessment.

      • Auto Start (Platform Defined) – Specifies whether or not a change automatically starts in a correction queue or must be manually started.

      • Single Year Correction – Controls whether or not each year must be corrected independently.  If this is not checked, corrections affect the change year and all subsequent years.  If it is checked, the correction affects only the change year.

    • Internal Assessor Queue – Specifies automatic/manual approval in the AA queues.

      • External Assessor Queue – Specifies automatic/manual approval in the AA queues.

    • Prorate Period (Platform Defined) – Specifies Daily, Monthly, or Quarterly proration for Supplementals and Instant Assessments

      • Prorate Rounding (Platform Defined) – Specifies whether to round the proration to the start, middle or end of the prorate period.

    • Place in Queue (Implementation Defined) – Specifies the starting queue for a correction.

      • Rev Obj SubType (Platform Defined) – Maps change reason to specific Revenue Object Subtypes (parcel, personal).

    • Aumentum Event Type (Platform Defined) – Maps an Event Type to a Change Reason.

      • Event Reason Code (Platform Defined) – Maps an Event Type to a Change Reason.  This allows AA to respond to specific Aumentum Events and supply a reason code for the change.

  2. Click Copy (optional).
    • In the Copy Mapping pop-up, select the checkbox for one or more items in the list and click Apply.
  3. Click Edit.
    • Make selections from the various drop-down lists and click Apply.
  4. Click Save in the Command Item bar.
    • Click Cancel to discard changes since the last save.
    • Click Close to end the task.

California

  • Eminent Domain: The Special Processing Unit (SPU) of the TTC (Treasurer/Tax Collector) office is notified of completion of a roll correction by the Auditor's office for Eminent Domain properties via the workflow. The workflow kicks off a TaxBillCorrection workflow for review and for accept/reject. The first Accept goes to treasurer. The second Accept posts to Accounts Receivable. Valuation changes are done to determine the valuation. The Levy Annual Corrections and Escapes Category, Process of Extend Tax Roll/Create Tax Bill Date executes and posts the correction to billing. Once posted to billing, the tax bill gets sent to the workflow for review.  Any funds collected in the Eminent Domain trust can be applied to the bill by a funds transfer. To accommodate Eminent Domain, a Value Change Reason code (Asmt Admin > Setup > Valuation Change Reason Mapping ) of Eminent Domain is available, and a Tax Change reason code (Tax > Levy Management > Setup > Tax Change Reason Mapping) of Eminent Domain is available. Tax Bill correction is available for viewing and accept/reject action on the Corrections View tab of the tax bill viewer (Tax > Assessment Processing > Tax Bill Viewer > Search for Tax Bill > Review Tax Bill).

Dependencies, Prerequisites, and Setup

Valuation change reasons must be set up and mapped before processing roll corrections or supplementals.

Configuration Menu

  • Systype Maintenance – Valuation Change Reason Codes, Change Reason Types, and Tax Change Reason Codes are all user-definable systypes and must be created before they are available for mapping and processing.