Batch Invoicing: Automating Dues Accrual in Communities

Why does dues accrual eat the same hours every month?

In many communities the first days of the month look the same. The manager opens a spreadsheet, works out each unit's amount, makes a separate note for vacant flats and shops, then retypes the figures into the ledger and into the list that goes out to residents. Batch invoicing for dues accrual is the practice of collapsing that routine into a single run: the period's dues and expenses are posted to every unit together, according to rules you have defined once.

The trouble with the manual process is not that the maths is hard. It is that it repeats. The same sheet gets copied every month, a formula breaks in one cell, one unit's exemption is forgotten. The mistake only surfaces when a resident asks why their balance looks different, and by then fixing it costs both time and trust.

Accrual, invoicing and collection are different things

These terms get mixed up, so it helps to separate them:

• Accrual: recognising the amount owed for the period. It has not been paid yet, but it is now a settled obligation.
• Invoicing (posting a charge): actually applying that amount to each unit's balance. The debt a resident sees in the app is the result of this step.
• Collection: the payment arriving and the debt closing.

All three belong to one chain. When the chain lives in a single system, the accrued amount, the unit balance and the ledger have to agree. When it lives across several files, "why don't these match?" comes back every month.

What happens in a single run?

In Site-Park, batch invoicing posts the period's dues and expenses to every unit in one run. You can think of it in this order:

1. Pick the period and the lines. Decide which month's dues, and which additional expenses (lift maintenance, shared energy and so on), are part of this run.
2. Apply the allocation method. Each expense line can be split equally, by floor area, by land share, by occupant count, by unit type or by metered consumption. We covered how to choose among them in our annual operating budget guide; invoicing is the step that executes the decisions made in that document.
3. Let standing rules apply. Exemptions and discounts defined for vacant units, shops or ground-floor flats that do not use the lift apply automatically on every run. See our article on dues exemption and discount rules for how to set them up.
4. Review the preview. Before anything is final, you see the amount each unit will receive.
5. Commit. The moment you confirm, the charges are posted; they appear in the resident app and the ledger and balances update together.

Why the preview is the step that matters most

The biggest risk of any bulk operation is that a mistake spreads across the whole community at once rather than touching one unit. Picking the wrong allocation method, adding a line twice or missing an exemption can affect hundreds of units. The preview is therefore a safety net, not a luxury.

A few things worth checking in it:

• Does the total match expectations? Do the unit amounts add up to something close to the period budget in your operating plan?
• Edge values. Check the highest and lowest few units by hand; rule errors tend to show up at the extremes.
• Exempt units. Confirm that vacant or special-case units received the amount you expected.
• Recent move-ins. Make sure units that changed owner or tenant mid-period are charged to the right person. Our piece on the move-in and move-out wizard helps here.

The odd-cents problem

Anyone who has split a cost by hand knows this one. A 10,000 TL expense is shared across 37 units. Round each share, add them up, and the total will not land exactly on 10,000: you are a few cents over or under. That tiny gap between the amount allocated and the ledger turns into a long evening at trial-balance time.

In batch invoicing the split is completed to the last cent, so the total always equals the amount being distributed. The "few cents" mismatches that haunt the chart of accounts and trial balance are prevented at the source. The accounting side of that consistency is covered in our article on the chart of accounts and trial balance.

After posting: how payments match

Once the charges are posted, a resident's payment closes the oldest open charge first, and any surplus waits as credit. The argument about which month a payment covered is settled by a rule rather than by memory. This is especially useful for units carrying several periods of debt, because manager and resident look at the same ledger.

Late-payment interest accrues automatically each month on overdue balances, and the process is tracked from tiered reminders through to a draft of a formal notice. For the collection side, see how to improve dues collection rates.

What if a charge was posted wrongly?

Quietly deleting a committed record is bad for accounting discipline and for resident trust. In Site-Park an incorrect charge or payment is not deleted; it is marked as cancelled and the original entry stays in the trail. The correction appears as its own record, and the audit log shows who cancelled what and when.

The practical benefit is that when a resident or a board member asks "what was posted to this unit last month?", the answer is there with the original and its correction side by side. We wrote about why audit logs matter separately.

A checklist before your first run

• Are unit lists, floor areas and land shares up to date?
• Is an allocation method set for every expense line?
• Are exemption and discount rules defined as standing rules?
• Have you tried the first run as a preview, rather than going straight into a live period?
• Did you compare the run total to the period amount in the operating plan?
• Have residents been notified, and are payment channels open?

For the first two periods, walking through this list every time is enough. After that the process becomes routine and most of the work at the start of the month disappears.

In short

Automating dues accrual frees the manager from repetition, not from judgement: rules are defined once, the preview catches errors before they are final, no odd cents are left over, and the history stays in the trail unchanged. Management time goes to interpreting the numbers and talking to residents instead of typing them.

If you would like to see how batch invoicing would work on your own unit structure, you can browse the modules on the Site-Park page, or contact us and we can map out a setup plan around your current dues rules.