Change Control — Municipal Property Tax
Property-tax data is inherently time-sensitive
Municipal property-tax files change because tax years roll over, ownership changes, building or land characteristics are corrected, official values are updated, legislation/communiqués change calculation inputs, and payments or assessments are posted. A transaction file that simply stores one certificate can become stale quickly. Change control records the baseline used for a decision and every material change afterwards so the team knows which tax evidence remains historical and which evidence is current.
Establish a year-specific baseline
Record municipality, property identifiers, taxpayer, tax year, property category, official tax value, account status and source date. If the transaction relies on a municipal document, save its reference. Do not merge different years into one “current tax” field. The same property can legitimately show different values or cost inputs across years. The baseline must be precise enough that a later reviewer can tell whether a new number is a correction, a new-year assessment or simply a figure from another property.
Capture owner and property changes immediately
A sale changes ownership, while subdivisions, independent-unit corrections, building completion or classification changes can alter how records are displayed. When any identifier or taxpayer changes, update the municipal/tax file and link old to new. Do not overwrite the previous owner as if they never existed. Preserve acquisition/disposal dates and the period each record covers. If the municipality account still shows an old owner after transfer, open an exception instead of silently editing the internal spreadsheet.
Treat annual official rules as versioned sources
GİB’s property-tax communiqués are date/year specific. Series 89 and 90 illustrate why source versioning matters: they concern different years and inputs. Store the exact communiqué used, its date and the year it applies to. When a new communiqué is published, it does not retroactively replace the historical rule used for a prior year unless the law explicitly gives such effect. Current transaction decisions should use the rule applicable to the current tax period.
Record value and classification changes separately
A tax value can change because of a new year, an official correction, altered building characteristics, land classification, a statutory cap or another recognised reason. State which field changed and the official basis. If a building-class or area error is corrected, record the before/after data rather than merely updating the total. This helps distinguish a genuine correction from a market-value change, which is a different concept.
Payments and new assessments reopen the balance
When a payment posts, keep the receipt and updated account. When a penalty, additional assessment or correction appears, reopen any “clear” status that depended on the earlier balance. A previous zero balance is evidence for its timestamp, not a perpetual guarantee. If funds are being held under a contract, a change before release should trigger revalidation of the payment gate.
Propagate material changes to the property sale file
A changed emlak vergisi value may affect transaction-value checks under the land-registry process; a changed owner/property identifier affects document matching; a changed balance may affect a contractual tax-clearance condition. List these dependent checks in the change record. Conversely, a future-year construction-cost communiqué with no relevance to the current transfer should not trigger unnecessary changes. Impact analysis prevents both underreaction and overreaction.
Freeze the evidence used at closing
At the decision point, save the official municipal/tax evidence, tax value, account/payment status, applicable rule source and review timestamp. If the municipality updates the account later, preserve the old snapshot as the evidence actually used and add the new state as a later version. This makes the transaction auditable without pretending historical data should be rewritten to match today.
Quality standard
A controlled tax file tells a clear story: what the official position was, when it was checked, what changed, why, which year it belongs to, what evidence supports the change, and which transaction decisions were reopened. It avoids “latest value” fields with no history and prevents future-year rules, market values and payment receipts from being mixed into one unreliable tax record.