Municipal target-setting usually lives in a strange limbo: the numbers are politically real (they appear in budget speeches and performance contracts) but methodologically fictional (nobody can say how they were computed, which base year, or what collection rate they assume). The result is the annual theater of chasing a number that no ledger recognizes. A structured target model fixes the epistemology: collection targets are set per revenue item and per municipality, scoped to financial years that bound every report, and — crucially — imported from the same authority sheets that carry the rest of the master data, so targets arrive as data with provenance rather than as decrees with attachments. When the target is queryable, the achievement conversation stops being a negotiation about interpretation and becomes arithmetic about collection.
The three scopes that make a target honest #
- By financial year: targets live inside accounting years that scope reporting — no orphan targets belonging to closed fiscal periods.
- By revenue item: each chargeable revenue code carries its own target, because a fine and a lease compound differently.
- By municipality: geography carries its own economics — a single national target hides the three regions doing all the work.
The monthly decomposition is where targets meet operations: an annual number per revenue per municipality becomes twelve monthly expectations, and the targets dashboard tracks actual against expected with paid and not-paid variants — so March's shortfall is visible in March, not reconstructed in December. The discipline that separates functional target systems from decorative ones is variance honesty: when actual collection runs 40% above target for a revenue code, either the target was wrong (fix the methodology) or enforcement changed (document why) — unexplained over-performance is a forecast error wearing a celebration costume. Revenue directors who read targets this way build an institutional memory of what the municipality can actually collect, which is the only honest basis next year's budget will ever have.
Because targets import from authority sheets alongside contracts, payments, and financial years, the target model stays synchronized with the master data it measures — a new revenue code activated mid-year arrives with its target row in the same import, not as a footnote in a quarterly memo. That synchronization is what lets the Ministry-of-Finance achievement KPI be computed without a reconciliation meeting: the target, the invoices, and the payments all live in one ledger with one taxonomy, and the dashboard's job is subtraction, not archaeology.