No two community associations govern charges in exactly the same way. One condominium may require two board members to approve every special assessment. A smaller HOA may permit a property manager to approve routine utility adjustments but require an additional board review above a set dollar amount. Another community may want one approval for its recurring dues schedule and two for any unusually large charge.
That flexibility should not create a control gap.
Resinara's association charge approval policy is built around a simple protection: the person who proposes a governed charge cannot approve or reject that same request. The association can customize who is eligible to review it and how many independent approvals are required, but it cannot configure away that separation of duties.
The result is not a generic setting applied to every property. It is a versioned, property-specific control that translates the association's approved financial policy into enforceable software rules and preserves the evidence behind each decision.
The short version: Resinara lets an association tailor approval rules by action, charge type, amount, role, and approval count. A proposal stays pending until the required independent reviewers approve the exact details. The requester can never approve their own request.
A Charge Approval Policy Is Not the Same as a Collection Policy
These two policies work together, but they solve different problems.
An association's assessment or collection policy establishes the substantive rules: what owners owe, when amounts are due, when late charges may apply, which notices are required, and how delinquent balances are handled. The Community Associations Institute recommends that every association maintain a collection policy adopted by the board, reviewed by association counsel, and distributed to owners. Read CAI's assessment-collection policy.
A charge approval policy is an internal control. It determines what must happen inside the software before a proposed amount becomes a charge on a unit's account. It answers questions such as:
- Who may propose the charge?
- Which roles may review it?
- How many independent approvals are required?
- Does a higher amount require more reviewers?
- Should special assessments follow a stricter path than utilities or parking charges?
- Which rule applied when the decision was made?
Resinara does not decide whether an assessment is legally authorized. The board, governing documents, adopted budget, applicable law, and professional guidance determine that. Resinara's role is to make the association's approved decision path difficult to bypass and easy to reconstruct later.
Why One Universal Workflow Does Not Fit Every Property
Community size, staffing, documents, risk tolerance, and board practices vary. A useful approval policy needs enough structure to be consistent and enough flexibility to match the property.
Consider four common situations:
| Situation | Possible property-specific control |
|---|---|
| A recurring monthly dues schedule | One independent approval from an authorized board member or administrator before the schedule becomes active |
| A small utility adjustment | One independent approval from a property manager, tenant administrator, or board member |
| A special assessment | Two independent approvals from board-authorized roles |
| Any charge above $5,000 | Two independent approvals, regardless of charge category |
Those examples are not recommendations for every association. They show why a policy engine should support rules instead of forcing every community into one hard-coded threshold.
CAI's financial safeguards checklist asks whether financial duties are appropriately segregated and whether dual control is used to create and authorize a transaction. Review CAI's Checklist for Safeguarding Association Assets. Resinara carries that principle into the charge-posting workflow.
How Resinara Makes the Policy Flexible
Every association begins with a default approval requirement. More specific rules can then override that default when a proposal matches defined conditions.
Action
A policy can distinguish a one-time manual charge from a recurring fee-rule proposal. That matters because approving a monthly dues schedule is different from reviewing an individual special assessment or account adjustment.
For a recurring schedule, the controlled decision is the schedule itself: its amount, timing, effective dates, and other configured terms. Once that schedule has been approved, the system can create its routine monthly charges without asking the board to repeat the same approval every billing period.
Charge Type
Rules can be tailored to association dues, late charges, special assessments, utilities, parking, amenities, violations, processing fees, or another approved charge type. A property can apply a stricter requirement to a special assessment than to an ordinary parking charge.
Amount Range
Minimum and maximum amounts let the association create approval tiers. For example, one reviewer may be sufficient through $5,000, while two are required for anything above that amount.
Eligible Roles
The association can limit reviewers to supported administrative roles: tenant administrators, property managers, and board members. A rule may include more than one eligible role without giving residents or unrelated users approval authority.
Number of Independent Approvals
Each rule requires between one and ten approvals. Because the requester does not count, even the lightest valid policy involves at least two distinct people: one person proposes and another independently approves.
Rule Priority
Several rules could match the same proposal. A $7,500 special assessment, for example, may satisfy both a special-assessment rule and a high-value rule. Resinara gives rules unique priorities and evaluates them deterministically, so the result does not depend on list order, timing, or a person's interpretation.
A default rule ensures every governed proposal has an approval path. Specific rules add precision for higher-risk actions without leaving unmatched charges outside the policy.
What Happens When Someone Proposes a Charge
The approval workflow separates proposing a charge from posting one to the resident ledger.
1. Resinara Validates the Proposal
The system checks the association, unit, charge type, amount, due date, and related information in the authenticated association context. The amount must be positive and use valid currency precision. A late charge must point to an eligible overdue source charge for the same unit.
2. The Matching Policy Rule Is Resolved
Resinara compares the action, charge type, and amount with the association's active rules. The highest-priority match determines the required approval count and eligible reviewer roles. If no specific rule matches, the default requirement applies.
3. An Exact Snapshot Becomes Pending
The proposal is stored as a pending request with the exact unit, type, description, amount, due date, requester, policy version, and resolved requirement. At this point, the proposal is not yet an open receivable. It is not available for a resident to pay, and rejecting or canceling it does not create a charge.
4. Other Eligible People Review It
An eligible reviewer can approve or reject the request. The requester is blocked from making either decision on their own proposal, even if that person also holds an approver role. Each reviewer can record only one decision on a request, and a rejection requires a reason.
5. Final Approval Creates the Charge
When the last required independent approval is recorded, Resinara creates the exact approved charge in the same controlled transaction. The posted charge is linked back to the approval request that authorized it.
6. Rejection or Cancellation Ends the Request
A rejection or valid cancellation closes the pending request without creating a resident charge. The outcome remains part of the workflow history.
Why the Control Is Enforced in Code
A written procedure is valuable, but a procedure that relies entirely on memory can be skipped during a busy month. Resinara turns the most important requirements into system invariants.
- Self-approval is always disabled. It is not an optional switch that an administrator can turn back on.
- The authenticated account supplies the actor and association. The browser does not choose who acted or which property owns the request.
- Roles are checked when a decision is made. Having access to the platform does not automatically make someone an eligible reviewer.
- Distinct reviewers are counted. Repeating the same approval does not satisfy a multi-approval requirement.
- Pending state is locked during decisions. Competing actions cannot legitimately approve, reject, or execute the same request twice.
- Idempotency protects submissions. Retrying the same request does not create duplicate proposals, while reusing its key for different details is rejected.
- The final charge is linked to one approval request. The decision record and resulting receivable have a durable causal connection.
Special assessments receive an additional database-level safeguard: a special assessment cannot be inserted without an approved request whose association, unit, type, description, amount, due date, and related source match the preserved approval snapshot. Changing the amount after approval is rejected rather than silently posting a different charge.
That defense-in-depth approach matters. Access control determines who may attempt an action, application rules control the workflow, and database constraints protect the most sensitive invariants at the persistence layer.
What Makes the Evidence Audit-Ready
"Audit-proof" can imply that no question, error, or compliance issue could ever arise. No responsible software should make that promise. Resinara instead creates audit-ready, tamper-resistant evidence that helps an association answer what happened without piecing the story together from email threads.
For each governed request, Resinara preserves:
- The association and unit
- The person who submitted the proposal
- The exact proposed charge details
- The policy version and rule that applied
- The required approval count and eligible roles at submission time
- A cryptographic fingerprint of the policy, proposal, and approval requirement
- Each reviewer's identity, role snapshot, decision, comment, and time
- Requested, approved, rejected, canceled, and executed workflow events
- The final posted charge reference, when approved
Decisions and workflow events are append-only. Policy changes create a new version instead of overwriting the old one. A request keeps the policy and approval requirement that governed it when it was submitted, so changing today's configuration does not rewrite yesterday's evidence.
This is the practical difference between a status field that merely says "approved" and an approval record that can explain who approved what, under which rule, and when.
How a Customized Charge Policy Is Set Up
Customization should begin with governance, not with a blank software form. During implementation, Resinara can translate the association's already-approved controls into a structured decision map.
1. Gather the Source Documents
Review the adopted budget, assessment resolutions, collection policy, governing documents, management agreement, relevant delegations, and counsel's guidance. The purpose is to identify what the association has actually authorized—not to invent policy during software setup.
2. Build the Decision Map
For each governed action, document:
- Charge type and business purpose
- One-time charge or recurring schedule
- Amount range, if thresholds apply
- Number of independent approvals
- Roles eligible to approve
- Effective date and any known exception process
3. Configure a Safe Default
The default requirement should cover anything that does not match a specific rule. This prevents an unusual or newly introduced charge category from falling through the cracks.
4. Add and Prioritize Specific Rules
Translate the decision map into typed rules, then resolve overlaps deliberately. High-value or exceptional transactions normally receive a higher priority than routine cases so the intended safeguard wins consistently.
5. Test Real Scenarios
Before launch, walk through representative examples: ordinary dues, a special assessment, a utility adjustment, a high-value charge, an ineligible reviewer, an attempted self-approval, a rejection, a duplicate submission, and a policy change while another request is pending.
6. Confirm and Version the Configuration
The association should review the configured result against its adopted policy. When requirements change later, Resinara creates a new policy version and retains the prior one for historical requests.
CAI describes the community manager's role as implementing policies established by the board rather than setting those policies independently. See CAI's overview of community manager responsibilities. The same boundary should guide software configuration: the system operationalizes authorized policy; it does not replace board governance.
Questions Every Association Should Answer
Before configuring charge approvals, ask:
- Which charges or schedules require advance review?
- Which roles may propose each action?
- Which roles may approve it?
- How many independent approvals are required?
- Do special assessments need a board-only path?
- At what amount should the approval requirement increase?
- Which rule should win when several conditions match?
- Who may cancel a pending proposal?
- What explanation or supporting documentation should reviewers expect?
- Who is authorized to approve a future policy change?
The answers will differ from one community to another. The non-negotiable point in Resinara remains the same: the requester cannot become the independent reviewer of their own action.
Frequently Asked Questions
Can the Person Who Proposes a Charge Approve It?
No. Resinara fixes requester approval to false. The rule remains in effect even if the requester is also a tenant administrator, property manager, or board member.
Can One Person Post a Governed Manual Charge by Themselves?
No. A proposal requires at least one independent approval. The charge does not become an open receivable until the configured approval requirement is satisfied.
Does Every Association Use the Same Approval Count?
No. An association can require from one to ten independent approvals and can use different requirements for different actions, types, and amount ranges.
Who Can Change the Charge Approval Policy?
Policy-management access is limited to a tenant administrator. A valid update creates a new immutable version and still cannot permit self-approval or unsupported approver roles. The association should separately define who is authorized to direct that administrator to make a policy change.
What Happens to a Pending Request When the Policy Changes?
It keeps its original policy version and frozen approval requirement. That makes the decision reproducible and prevents a later configuration change from silently changing the standard for an existing proposal.
Does Approval in Resinara Make a Charge Legally Valid?
No. Software approval confirms that the configured internal workflow was completed. The association remains responsible for authority under its governing documents, adopted resolutions, contracts, applicable law, notice obligations, and professional advice.
Can a Small Association Use This Model?
Yes, as long as at least two eligible people can participate. A community that cannot identify an independent reviewer should resolve that governance and staffing limitation before enabling governed charge posting.
The Bottom Line
Financial flexibility should mean that each property can express its own approved rules—not that one person can bypass review.
Resinara combines a configurable policy with a fixed separation-of-duties safeguard. Associations can choose the right approval path for routine dues, adjustments, special assessments, and higher-value actions while keeping self-approval off, preserving the exact decision evidence, and linking every approved charge back to the people and policy that authorized it.
That is how highly customized association charge governance becomes both practical for daily operations and accountable when questions arise later.
Want to map your association's charge policy into a controlled Resinara workflow? Schedule a personalized demo.
This article provides general operational information and is not legal, accounting, audit, or tax advice. Assessment authority, approval requirements, notices, collections, and record-retention obligations vary by governing documents and jurisdiction. Consult qualified professionals for guidance specific to your association.
