How to Manage Dues Exemption and Discount Rules

Why dues exemption and discount rules deserve their own process

Dues exemption and discount rules rarely live in a written procedure — in most communities they live in the property manager's head. Which unit is currently vacant, which shop pays less because it doesn't use the elevator, which ground-floor unit only owes for the shared garden — this knowledge is usually passed down verbally from one manager to the next. When a new manager takes over, or the person handling accounting changes, part of that list quietly disappears; nobody can say with confidence why a given unit is exempt. The real problem isn't just memory loss — it's that these exceptions have to be reapplied by hand on every single billing run.

Condominium law and the decisions made at the general assembly set the framework for which charges apply to which unit, but making sure that framework is applied correctly every month, on every invoicing run, is the manager's job in practice. A billing run generated before exemption and discount rules are clearly defined either produces incorrect invoices or forces the manager to correct the spreadsheet by hand every time.

Common exemption and discount scenarios

Most communities share a handful of recurring exceptions. Vacant units can be exempted from usage-based shared costs like electricity and water, but they're typically still liable for fixed costs such as the manager's salary or insurance — and that distinction needs to be written down explicitly. Commercial units are often billed under a different allocation method than residential ones; a discount on elevator, shared lighting or security costs for ground-floor and commercial units is a common general assembly decision. Some communities also carry a standing exemption for units belonging to the developer or building manager.

What all of these scenarios have in common is that they're standing rules, not one-off adjustments. Once the general assembly approves a decision, it stays in effect every month until it's formally revoked. What's actually needed, then, is to define the exception once and let the system apply it automatically on every run — not have the manager comb through the same list every month.

The real cost of managing this by hand

In a spreadsheet-based exemption list, the risk isn't in the formula itself — it's in how current the list stays. When a unit is sold, rented out, or a shop changes its use, the corresponding row needs updating; if that update is missed, either a unit that's no longer exempt keeps getting the discount, or a unit that's still entitled to one gets billed the full amount. The second case is the one that erodes trust — especially when the resident remembers getting the discount in previous periods and suddenly sees it disappear without explanation.

Manually applied exceptions also slow the billing process down. Batch invoicing is meant to complete in a single run; layering manual corrections on top of it costs time and increases the chance of error. A rounding difference that slips through unnoticed can turn into a discrepancy that's hard to untangle once it hits the ledger at month's end.

How rule-based automation handles it

The right approach is to treat exemptions and discounts as a rule defined once, not a task repeated every month. Site-Park lets you define standing rules for vacant units, commercial spaces, or ground-floor units that skip elevator costs — once a rule is saved, it applies automatically on every batch invoicing run. Managers can also see every exempted unit on a single screen, along with when the underlying decision was made and why.

The most concrete benefit of this approach is that billing becomes predictable. When the manager runs batch invoicing, the defined rules kick in automatically, and the preview screen shows exactly which unit is billed differently and why — catching a misconfigured rule before it's finalized. As we noted in our piece on improving dues collection rates, this predictability is also a precondition for resident trust — an inconsistent or unexplained charge directly discourages payment.

Transparency and the appeals process

No matter how correctly exemption and discount rules are defined, residents still need to be able to see them. If a resident can check exactly how their charge was calculated and which line item they're exempt from, right in the app, the question "why does my neighbor pay less than me" gets answered by the app itself instead of a phone call to the office. If the rule can be annotated with the general assembly decision it's based on, management has a concrete reference ready the moment someone disputes a charge.

That transparency protects the management side too. When an audit committee or a general assembly asks "why is this unit billed differently," a documented rule with a date attached gives a clear, defensible answer. An undocumented exception — even one applied in good faith — becomes hard to defend the moment it's questioned.

Common mistakes

A few recurring mistakes show up when communities manage exemption and discount rules. The first is leaving the rule as a verbal agreement or a stray email — without a documented link to the general assembly decision behind it, the rule disappears the moment the manager changes. The second is defining an exception for a temporary situation and forgetting to remove it once it expires; a "vacant unit" exemption that keeps applying after the unit is sold quietly costs the community revenue. The third is applying inconsistent allocation logic across charge categories — giving a ground-floor unit a discount on one line item while forgetting the same logic on another creates inconsistencies in the billing table. The fourth and most common mistake is never assigning clear ownership of keeping the exemption list current — when nobody owns it, it simply doesn't get updated.

What to prioritize in practice

For a management team looking to put dues exemption and discount rules on solid ground, a reasonable order of priority looks like this:

• Document every exception in writing — which unit, what reason, which general assembly decision.
• Define the rule once and automate it — a standing rule instead of a list reapplied by hand every month.
• Track status changes — update the rule the moment a unit is sold, rented, or changes use.
• Make it visible to residents — the reason for an exemption should be visible in their own charge detail.
• Never finalize without a preview — check that exceptions applied correctly on every billing run before committing it.

All of these steps serve one goal: making sure it's always possible to explain who's billed differently and why. That's not just an accounting concern — as we cover in our piece on transparency in community accounting, it's one of the foundations of trust between residents and management.

If you want your community's exemption and discount rules to be standing, automatic, and applied consistently on every billing run, get in touch and we'll map Site-Park's dues modules to your general assembly decisions together.