Expense Approval Workflows for Communities: A Guide

Why an expense approval workflow protects a community instead of slowing it down

A residential community spends money constantly: a lift breakdown, a roof repair, landscaping, a fresh coat of paint in the lobby. In many communities, the "who approved this" part of each expense is never written down. The manager says "go ahead" on the phone, the contractor finishes, the invoice arrives, the payment goes out. Months later an owner stands up at the general assembly and asks who decided on that spend, and the answer lives in a chat message or in nobody's memory.

An expense approval workflow removes that ambiguity with a simple rule: spending above a defined amount is approved by named people before it happens, and the approval is recorded. The goal is not to slow the manager down. It is to protect both the manager and the owners from the tension that comes from not knowing who said yes, to what, and when.

What goes wrong without a workflow

The same few problems appear again and again:

• Verbal approval, unclear responsibility. After the work is done, who authorised it becomes a matter of dispute.
• Split invoices. A large job gets broken into smaller pieces so each one stays under the approval line. This is rarely deliberate; it is usually habit, but the outcome is identical.
• Late discovery. The board learns about a spend after the invoice is issued, so any objection is purely theoretical.
• Dependence on one person. When the manager is on leave or changes, urgent spending either stalls or happens with no oversight.

None of these requires bad intent. A messy process can erode trust even among well-meaning people, which is why the workflow is best presented as a shared set of ground rules rather than a control measure aimed at one person.

Designing the workflow, step by step

1. Sort spending into types first

Not all spending carries the same risk. A common split looks like this:

• Recurring costs: cleaning, security and lift maintenance contracts that were approved once and are paid on schedule.
• Routine small purchases: light bulbs, locks, minor repairs that keep the day-to-day running.
• Unplanned emergencies: a burst pipe or a failed booster pump that cannot wait.
• Major investments: roof renewal, facade work or a camera system that materially affects the budget.

Writing a different rule for each type is far more realistic than applying one rule to everything.

2. Set thresholds that fit your community

Thresholds depend on the size of the community and its monthly budget; there is no magic number. The table below is a fictional example meant only to show the logic:

| Spending tier | Who approves | Note | | --- | --- | --- | | Small amounts | Manager | Reported afterwards | | Mid-range amounts | Manager + a board member | Approved in advance | | Large amounts | Board, and the general assembly where required | With quote comparison |

Base the thresholds on your governing documents and on past assembly resolutions. Some major works may legally require a decision by the owners' body; in that case a digital approval flow does not replace the assembly resolution, it only records the execution step. When in doubt, ask the community's legal adviser.

3. Separate the roles: requester, approver and payer should differ

The most important principle of a good workflow is segregation of duties. The person who requests an expense, the person who approves it and the person who pays it should ideally be different people. Even in a small community the three roles can be shared between two people: the manager requests, a board member approves. What matters is that nobody holds both the decision and the payment authority alone. This directly reduces the error and misuse risk we discussed in the supplier payment tracking checklist.

4. Attach quotes and reasoning to the request

A request that only says "this much money" is not enough. A good one includes a short description of the work, why it is needed, the quotes received (at least two for larger amounts) and any photos or fault records. When the approver decides with this information, the later question "why did we choose this contractor?" can be answered with documents. If your maintenance request process is already recorded, the spending request can link straight to the originating fault.

5. Give emergencies their own path

The most common mistake is applying the full process to emergencies. Waiting for three approvals at midnight while a pipe floods the basement makes no sense. Define an emergency exception instead: the manager may act alone up to a set ceiling, but must submit the spend with its justification on the next working day. Speed is preserved and accountability is not lost.

6. Decide in advance what happens when the approver is away

If a board member is on holiday or unreachable, the request should not sit for weeks. Name a backup approver and agree on where the request goes if no one responds within a set time. We described a similar idea for HR in delegation and escalation in approvals; the same approach adapts well to community spending.

Why the record matters as much as the approval

Approval is not the finish line. The lasting value lies in recording it permanently. The record should contain at least the requester, the request date and amount, the approver or rejecter, the decision date and any note. When you run a budget versus actual comparison at year end, being able to trace a variance back to a specific approved decision strengthens the manager's position at the assembly.

The same record helps the audit committee. When an auditor opens an expense file they see not only the invoice but the chain of decisions behind it. That is the core argument in why audit logs matter: the record exists not to blame anyone but to close the gaps in what people remember.

Common mistakes

• Building a long chain. Four approvers per expense pushes people to work around the rule.
• Never updating thresholds. Review them once a year as prices move.
• Turning the exception into the rule. If every job is "urgent", the workflow means nothing.
• Approving after the invoice. Approval must come before the work.

Running the workflow digitally

A spreadsheet and email can carry an approval routine, but when the request, quote, approval and payment live in different places the record loses integrity. The approval workflows module in Site-Park routes spending, purchasing and discounts above a set amount for approval, and who approved what and when stays on the record permanently. To see which capabilities sit in which tier, have a look at our guide to module packages.

A small plan to start with

You do not need a big overhaul. This week you can do three things: sort the last six months of spending by type, mark which items have no approval trail, and agree a one-page threshold table with the board. Moving that table into a system afterwards makes the rule independent of any single person.

If you want to clarify and record the expense approval process in your community, you can reach us through the contact page to see how Site-Park approval flows could be set up for your structure.