Association dues as repeating invoices

Dues are rent with a different name and a harder collection problem. The same repeating-invoice engine handles them, and the treasurer gets the two reports an assembly always asks for: who has paid, and who has not.

By the end of this page

You will know how dues are scheduled, sent and collected, what homeowners see, and how to read the arrears report.

A subdivision gate with its guard house and barrier
A month of duesDrag the slider
Schedule1st5thChaseAssembly
setupreporting

What homeowners see

On the portal: this month's statement, the history of statements and receipts, the balance, QR codes to pay. A homeowner who pays on time sees a clean record; one who does not sees exactly what they owe and since when. Receipts are acknowledgement receipts from the platform; the association's official receipt, if it issues one, is still the booklet or its BIR-registered system.

Annual dues, paid monthly

Some associations set an annual amount and accept monthly instalments. Schedule it monthly; the portal shows the annual total and what remains. A homeowner who pays the year up front gets credit that the remaining months consume.

Recording payments

Same as rent: from the statement, amount, date, method, reference. A treasurer recording thirty GCash payments on the 6th uses the Batch view — one row per lot, paste the references. Payments on account and overpayments become credit on the homeowner.

What the platform will not decide. Penalty rates, grace periods, denial of gate privileges, collection action — these are by-laws and board resolutions. The platform records what you decided and shows the arrears; it does not enforce anything on its own.

Was this useful?

Thank you — that is what it was written for.

Describes the platform as it is today. Something out of date? Tell us. · help 0.71.0