Issuing a fine

When a complaint is confirmed and the resident hasn’t fixed the issue, the next step is usually a fine. This is enforcement. It needs to be done right — wrong process leads to disputes, board liability, and refunds. This article covers the legitimate path.

Before you fine — the prerequisites

A fine should not be the first thing a resident sees about a violation. Most communities follow this sequence:

1. First notice / warning — informational, no fine. Resident is told about the violation and given time to fix it.
2. Second notice — if the violation persists, a stronger notice is sent. Some communities still don’t fine here.
3. Fine assessed — if the issue still isn’t resolved after the grace period, the fine is added to the property’s balance.

What “grace period” means varies by community and by violation type. Common defaults:

• 14 days for cosmetic issues (paint, trash cans)
• 30 days for harder fixes (landscaping, structural)
• 0 days (immediate fine) for severe issues like unauthorized construction or repeated short-term rentals

Your bylaws should specify. If they don’t, your board needs a written enforcement policy. The system follows whatever you configure.

Where fines attach

This is the key part: fines are charged to the property, not the resident.

Same as dues, same as assessments. The fine creates a Fine entry on the property’s ledger. The amount is added to the property’s balance. The resident sees it in their portal.

Why property and not resident:

• Same legal logic as dues (HOAs collect against properties)
• If the resident moves out before paying, the fine doesn’t disappear — the new owner inherits the balance, or it’s settled at closing
• Multi-resident households (married couples, families) don’t have to figure out which resident is “responsible” for the fine — the property is

The resident does get notified, of course, but the financial record is at the property level.

Issuing the fine

The flow:

1. Open the violation (the request that triggered this)
2. Confirm the violation has been verified and the grace period has elapsed
3. Click Issue Fine (or Assess Penalty)
4. Fill in:
   • Amount — the dollar amount per your fine schedule
   • Reason — pulls from the violation, but you can refine
   • Effective date — usually today, can be future-dated
   • Notice text (optional) — explanatory letter sent to the resident
5. Confirm

What happens:

• A fine entry is added to the property’s ledger
• The property’s balance increases by the fine amount
• The resident gets an email with the fine notice
• The violation’s status updates to Closed (with the fine recorded)
• The fine record links back to the original violation for audit traceability

The fine schedule

Most communities have a tiered fine schedule:

Tier	Trigger	Typical amount
First fine	After grace period elapses on initial notice	$25-$100
Second fine	Continued violation after first fine	$50-$200
Third fine	Continued violation after second fine	$100-$500
Daily fines	After multiple notices, escalating	$25-$50/day

Your bylaws should set the maximums. Check state law too — some states cap HOA fines.

Internal notes vs. resident-facing text

When issuing a fine, you write two things:

1. Notice text — what the resident sees in the email and in their portal. Be clear, professional, and reference the bylaw. Example:

   “A fine of $100 has been assessed against your property at 123 Maple St for an unresolved violation: garbage cans left at the curb past Tuesday at 8pm, in violation of CC&R Section 4.3. The fine has been added to your account balance. To resolve, please remove cans by the next collection day. Continued violation may result in additional fines.”

2. Internal notes — board-only commentary on the fine. Justification, observations, who reviewed. Not visible to the resident.

Both go into the audit trail. The resident-facing text is what shows in the email and portal; internal notes are admin-only.

Auto-fining via Herald Shield

If you have Herald Shield automation enabled, the AI can auto-issue fines based on rules you configure (e.g., “after 30 days unresolved, assess a $50 fine”). See Escalations and repeat offenders for the full Herald Shield workflow.

A safe pattern: start with review mode — Herald Shield drafts the fine action and an admin approves before it executes. Once you trust the rules, switch to autopilot for routine violations.

When residents push back

Common challenges:

“I didn’t know about the violation”

Check the audit trail — what notices were sent and when. If documentation shows the resident was notified at every step, the fine stands. If the chain is broken, the board may want to waive in good faith.

”The fine amount is too high”

If the amount is per your published fine schedule, it’s defensible. If you went above the schedule for this resident specifically, that’s harder to defend — bylaws usually require consistent enforcement.

”I’m being unfairly singled out”

Most state laws require that HOAs enforce rules consistently. If a resident can point to others with the same violation who weren’t fined, that’s a real legal issue. The system gives you visibility — you can search for similar violations across the community to confirm consistency.

”I’m going to dispute this”

Disputes go through whatever process your bylaws define — typically a written response to the board, sometimes followed by a hearing. The system doesn’t automate the hearing process, but you can track the dispute as comments on the original request.

If the board reverses the fine, don’t delete the FINE record. Add a CREDIT for the same amount with a memo: Fine waived per [meeting/decision date], [reason]. The audit trail shows the fine was issued and reversed; everyone can see what happened.

Voiding vs. crediting a fine

Two ways to “remove” a fine:

Action	When	What happens
Void	Fine was issued in error (wrong property, duplicate, etc.)	The FINE record is marked voided; doesn’t affect balance
Credit	Fine was valid but the board decided to waive	A new CREDIT record offsets the FINE; both visible in audit trail

For waivers, always use credit — the fine itself was correctly issued at the time; the waiver is a separate decision. Voiding pretends the fine never happened, which isn’t accurate.

Common situations

”A resident is racking up fines and not paying”

Continued non-payment after multiple fines usually progresses to:

1. Suspension of amenity privileges — disable their bookings under the property record
2. Reporting to collections — outside the system, but you can export the ledger as evidence
3. Lien filing — formal legal action against the property; coordinate with HOA legal counsel
4. Foreclosure — last resort; rare but legal in many states

The system provides the data; the legal actions happen outside.

”The violation was caused by a guest, not the homeowner”

The fine still attaches to the property. The homeowner is responsible regardless of who triggered it. That’s how HOA enforcement works — the property owner is on the hook for activities at the property.

”Multiple residents are co-responsible (e.g., joint owners)”

There’s still one fine on the property. Both owners see it; either can pay. The system doesn’t split it.

”I want to fine the homeowner directly, not the property”

You can’t, by design. Money flows through the property’s ledger. If the homeowner moves and a new owner takes over, the fine is still on the property.

Where to go next

• The four request types — where fines come from
• The request lifecycle — how a request becomes a fine
• Escalations and repeat offenders — automated escalation
• How the ledger works — fine records in the ledger
• Issuing refunds — for waiving paid fines