Enumerate for Property Management Companies

Enumerate is the platform TOPS Software became, and most of what is written about it assumes a single association. That is not the problem a management company has. When one Enumerate Central instance carries forty, eighty or two hundred communities, the accounting difficulty stops being how do I post this and becomes how do I make two hundred sets of books close the same way, every month, with staff turnover in the middle of it.

One clarification before anything else, because it saves wasted evaluation time. Enumerate is built for companies that manage community associations. Its own FAQ puts it plainly: the platform is designed for companies managing community associations “rather than general rental properties.” If you manage rental doors, you are in AppFolio, Buildium, Yardi or Propertyware territory, and this article is not about your stack.

What actually changes when it is forty associations instead of one

A single association forgives inconsistency. If the treasurer codes landscaping to one account in March and a slightly different one in July, someone notices at year end and fixes it. Nothing structural depends on the choice.

A portfolio does not forgive it. Once you are producing board packages for dozens of communities, three things that were previously invisible start to govern your month:

Variance between communities becomes unreadable. If each association’s chart of accounts drifted to suit whoever set it up, you cannot compare utilities across the portfolio, you cannot build a budget template, and a manager moving from one community to another has to relearn the books.
The close becomes a queue. One association closes when the work is done. Forty close in an order, and any community that stalls pushes the ones behind it.
Errors stop being individual. A misunderstanding about how reserve expenditures are posted is not one mistake — it is the same mistake replicated across every community that person touches, discovered months later.

Almost everything that goes wrong in a portfolio-scale Enumerate instance traces back to one of those three.

Standardising the chart of accounts across boards that disagree

This is the foundational decision and the one most often deferred, because it is political rather than technical. Each board believes its financials belong to it, and some will have strong views about how their statements look.

The workable compromise is a standard core with permitted extensions. The operating and reserve fund structure, the major expense groupings and the equity accounts are identical in every community. Below that, individual associations can carry accounts the others do not — a community with a marina or a gatehouse needs lines nobody else needs.

What that buys you: portfolio reporting that aggregates without manual mapping, a budget template that can actually be reused, and a manager transfer that costs an afternoon rather than a month. What it costs: a conversation with every board, once.

If you are inheriting an instance where this never happened, treat it as a remapping project with a defined cutover date rather than something to fix community by community as you go. Partial standardisation gives you the cost of the exercise without the benefit.

The close calendar is the product

Boards do not experience your accounting. They experience a package arriving on a predictable date, or not arriving. For a management company, the close calendar is the deliverable, and it should be designed deliberately rather than inherited.

A workable portfolio close staggers communities across the month rather than attempting all of them at once. Bank statement availability usually drives the grouping — associations whose statements cut at month end cannot close as early as those cutting mid-month, and pretending otherwise just produces packages built on incomplete data.

Three things worth fixing in the calendar rather than leaving to judgement:

A hard cut-off for AP. Invoices arriving after the cut-off go to the following period. Without this, the close date moves whenever a vendor is late.
A named reviewer per community, not per task. Review that rotates by workload is review that nobody owns.
A defined exception path. When an association cannot close — a disputed balance, a missing statement — it should move to a known state with a reason, not sit silently in the queue.

Where the Central and Engage seam shows at volume

Enumerate Central handles accounting, payments and operations; Enumerate Engage is the homeowner and board-facing side. The two products came from different companies — TOPS and Nabr Network — and while that lineage matters less each year, any boundary between systems is worth a monthly completeness check when volume is high.

The check is simple and worth building into the close: for each community, confirm that payments visible to owners reconcile to what posted to the ledger, and that the owner-facing balance agrees to the receivable. At one association you would notice a discrepancy. Across a portfolio, a small posting gap in one community is easy to miss until an owner disputes a late fee and the board asks why the portal and the statement disagree.

Supervising the AI bank reconciliation rather than trusting it

Enumerate’s Numa AI includes automated bank reconciliation transaction matching, and at portfolio scale that kind of automation is genuinely valuable — matching is the most mechanical part of the work and the least deserving of human hours.

The discipline that matters is what you do with the exceptions. Automated matching is good at the obvious and leaves the ambiguous, which means the residue it hands back is, by definition, the harder population. Two habits keep this honest: never clear an unmatched item by forcing it, and treat a sudden drop in exception volume as something to investigate rather than celebrate. A reconciliation that got easier without the underlying processes changing usually means something is being matched that should not be.

This is not a criticism of the tooling. It is the same supervision any bank rule set deserves — see our working reference on bank reconciliation for what a reconciliation actually has to prove.

Onboarding an association mid-year

Portfolios grow by taking on communities from other management companies, and the books arrive in whatever condition the previous arrangement left them. The costly mistake is loading opening balances that have not been proven and discovering in month four that the fund balances never tied.

A defensible onboarding establishes, before the first close:

Bank balances agreed to statements at the takeover date, for every account including reserve accounts held separately.
The owner ledger total agreed to assessments receivable. A difference here is the single most common inherited defect, and it compounds the moment you start billing.
Fund balances that are real fund balances. A separate bank account is not fund accounting — a fund is a self-balancing set of accounts with its own fund balance, and plenty of inherited files have the cash separated while the accounting never was.
Whatever the prior preparer’s reserve treatment was, documented, so corrections are traceable.

Where years of drift are involved, that is catch-up work before it is monthly work, and pricing it as monthly work is how management companies end up absorbing someone else’s mess.

Staffing: what one person can actually carry

We are asked for a ratio — how many associations per accounting person — and the honest answer is that the number is meaningless without the inputs behind it. A hundred-unit association with a gatehouse, a pool, three reserve components and a litigious board is not comparable to a forty-unit community with two vendors.

The variables that actually drive the workload are transaction volume, number of bank accounts, how many reserve components are tracked separately, delinquency levels, and how much board communication the manager absorbs versus pushes to accounting. A portfolio where accounting also fields owner calls carries a fundamentally different load from one where Engage absorbs that traffic.

What we can say from running association books since 2005: the capacity question is usually answered wrongly because the close calendar is undefined. Teams that cannot say which communities close on which day are not short of people — they are short of sequence.

Where an outside bookkeeping team fits

Management companies use us in two shapes. Some hand over the whole accounting function and keep managers client-facing. Others keep their accounting team and use us for the work that spikes — onboarding a batch of new communities, a migration cleanup, covering a departure — so the portfolio close does not slip while they hire.

We work inside your Enumerate instance rather than exporting to our own system, and our team can be white-labelled so the board sees your brand. Enumerate also sells its own financial services arm; the difference with an outside bookkeeper is independence and portability — your books and procedures answer to your company and survive any future platform decision.

Management companies and CPA firms use our wholesale tier at $300 a month for 30 hours, an effective $10 an hour. Smaller engagements start at $75 a month for 5 hours, with additional hours at $15 an hour. Your first retainer carries a 100% money-back guarantee, refundable on the unused balance, so a portfolio can be tested on one or two communities before anything larger is committed.

Ready to simplify your bookkeeping?

Partner with Maxim Liberty for reliable, affordable bookkeeping services backed by a dedicated support team.

Get Started

Frequently asked questions

Is Enumerate suitable for rental property management?

No. Enumerate states that its platform is designed for companies managing community associations rather than general rental properties. For rental portfolios the common platforms are AppFolio, Buildium, Yardi, Rentvine and Propertyware, and we keep books in all of them.

Can you standardise our chart of accounts across existing communities?

Yes, and it is usually the first thing worth doing. We map each community’s current accounts to a standard core, agree the extensions each association genuinely needs, and run the remap to a defined cutover date so prior-period comparatives remain meaningful.

Do you work inside our Enumerate instance or export the data?

Inside your instance. Your system stays the book of record, your managers keep the access they already have, and nothing has to be reconciled back from an external ledger.

Can you be white-labelled to our boards?

Yes. Management companies on our wholesale tier present our team as their own, and board communication continues to come from your brand.

We are taking on twelve communities in January. Can you handle the onboarding?

That is a common engagement. Onboarding is scoped separately from the monthly cycle because proving opening balances, agreeing owner ledgers to receivables and rebuilding fund balances is catch-up work, not recurring work.