Accountant vs Site-Park: Who Does What in Community Books

One of the questions community managers and management firms ask most often before adopting new software is whether it will replace their accountant's software. The short answer is no, but the reasoning behind that "no" matters. The two systems do not do the same job, and a setup built on the wrong expectation ends up either duplicating effort or leaving gaps nobody owns. This article draws the line between your accountant and your community management software with concrete examples.

Two separate sets of books

The confusion usually comes from the word "accounting" covering two different jobs.

The first is the community's own accounting. It records the dues collected from owners, shared expenses, supplier payments and cash and bank movements. These records exist so you can answer to the audit board and the general assembly. They generate hundreds of small movements every month: per-unit collections, the elevator maintenance invoice, the cleaning payment, meter-based bills.

The second is the management firm's corporate accounting. The firm's own income and expenses, payroll, tax obligations and filings. An accountant usually runs this in their own software.

Site-Park owns the first area. It keeps the community's operating ledger and community accounts in full, and the reports for the audit board and general assembly come straight out of it. The second area stays in the accountant's software. The platform does not try to take it over; it hands that side ready-made period reports and listings.

A practical split of work

The table below summarises a division that works for many management firms. Every firm's setup differs, so treat it as a starting frame.

| Task | Community software | Accountant | | --- | --- | --- | | Dues billing and collection records | Yes | No | | Matching bank movements | Yes | Spot-check if needed | | Community ledger and trial balance | Yes | Reviews | | Supplier accounts | Yes | Takes data for filings | | Management firm's corporate records | No | Yes | | Tax filings and regulatory interpretation | No | Yes |

The pattern is simple: daily, high-volume, unit-level work lives in the system, while interpretation, filing and regulatory compliance sit with the professional. Each side does what it is good at.

What changes for the accountant

You should not expect the move to software to remove your accountant's role. What changes is the quality of the data that reaches them.

In a manual setup the accountant receives a spreadsheet, a few bank statements and a folder of invoices at month end. Their first job is to make these agree with each other, and much of the advisory time goes into gathering and cleaning data. When the record system runs cleanly, the accountant receives per-account movement listings, the period trial balance and the ledger ready to use. The same hours go into the work that actually needs expertise: interpretation and filing.

We covered this data structure in detail in our piece on chart of accounts and trial balance. The point to take away is that a trial balance that balances is a signal of trust for the accountant, because moving on to review becomes much easier.

Three common misunderstandings

"We bought software, so we no longer need an accountant"

Community management software does not give tax advice or interpret regulation. For something like a management fee invoice, which document to issue depends on the status of the party providing the service, and that decision is settled with your accountant. Our e-archive invoicing article draws this line deliberately: software organises the operational side, while the legal and tax side is decided by the professional.

"The accountant already has software, so a second record is pointless"

An accountant's software is not designed to track the unit-level relationship inside a community: which unit owes how much, which resident paid what and when. When a resident asks "what is my balance?", the record that answers is the community system, not the accountant's corporate book. The two answer different questions; one is not a copy of the other.

"We will have to reconcile the two systems by hand every month"

This is the real risk: data typed by hand into two places will not agree. The fix is for each piece of data to originate in exactly one place. Community movements originate in the system and travel to the accountant as reports; the accountant's corporate records originate in their own software. The handover between them is an exported report, not a retyped entry. Every retyped line is another chance for an error.

How the period-end flow works

Year-end close is where the split is most visible. On the system side the period is closed, balances carry into the new year, and retroactive entries into the closed period are blocked. That last rule matters to the accountant too: the figures they were given will not change silently afterwards. Our year-end close guide walks through the steps.

A similar rhythm works ahead of a general assembly:

1. The manager clears open items in bank reconciliation before closing the period.
2. The period trial balance and per-account listings are produced.
3. The accountant reviews them and sends back any questions or correction requests.
4. Corrections are entered while the period is still open, then the period is closed.
5. Reports for the audit board and general assembly come from the same record.

The value of this order is that everyone looks at the same numbers. The trial balance the accountant sees cannot differ from the one the audit board sees.

An extra benefit for multi-community firms

For a firm managing dozens of communities, an accountant who receives a separate file flow for each one faces workload that grows quickly. When every community is kept on the same chart-of-accounts structure, listings arrive in a consistent shape and the accountant does not have to learn a new layout every time. The same structure also makes portfolio-wide comparison easier on the management firm's side.

The first conversation with your accountant

A short conversation with your accountant before switching settles most friction up front. We suggest raising these questions:

• Which period reports do they need, and how often?
• Do their existing account codes need mapping to the community chart of accounts?
• Will past years stay in the old setup, or will you start from opening balances? For most communities the cleanest route is to start from opening balances rather than migrating old books.
• Which document type is needed for management fees and similar invoices?
• Through which channel and within what time will questions and correction requests be handled?

The outcome should be a written division of work. Even a one-page note keeps the process running when the manager or the accountant changes.

Conclusion

Community management software and an accountant are not rivals; they are two kinds of expertise at opposite ends of the same data. The system keeps daily, unit-level, high-volume work orderly, and the accountant handles interpretation, filing and regulatory compliance. Management teams that draw the line at the start avoid both duplicated effort and work that nobody owns.

If you would like to look at how your current accounting setup would fit alongside Site-Park, including the reports your accountant needs, get in touch with us, and you can explore the ledger and reporting modules on the Site-Park product page.