Condominium fees without spreadsheets

A condominium management app that calculates each apartment's monthly fees from versioned rules, so a change voted by the general assembly never rewrites past months.

The problem

In most Bulgarian apartment buildings the fees live in a spreadsheet kept by one volunteer. The rules sound simple, €7 per resident over six, €2 per pet, repairs by ideal shares, until someone moves out mid-month, a flat stays empty or the general assembly raises the fee from January. Then the spreadsheet gets a new column, the old months quietly change and nobody can explain why apartment 14 owes €64.98.

How the app solves it

Contribution rules per fund, each with its own effective date

The monthly calculation: totals per fund and per apartment, before anything is saved

Payments are never deleted. A wrong entry is cancelled with a reason, so the history of every apartment can be checked line by line.

Under the hood

The app is a Spring Boot modular monolith on PostgreSQL with Flyway migrations and an Angular front end.

flowchart LR
  P[Contribution rules<br/>effective from a month] --> C[Monthly calculation]
  O[Occupancy and pets<br/>by month] --> C
  S[Ideal shares] --> C
  C --> V[Preview]
  V -->|Calculate month| D[Charges per apartment]
  D --> PAY[Payments and receipts]

Effective-dated rules are the core of the design: a calculation always asks "which rule was valid for this month", never "what is the rule now".

The result

A building manager can bill a 16-apartment building in minutes, explain any amount to any owner and change the fees without breaking a single past month.

The app runs at domsavet.eu; its login page has a public demo with two fictional buildings that reset every night.

Technologies

Java, Spring Boot, PostgreSQL, Angular, Property management