Apartments and complexes
LiveApartment & Complex Management
Dues, collections, expenses and resident communication in one place — right up to preparing the general meeting.
Apartment & Complex Management keeps blocks, units, owners and tenants, dues, collections and expenses together. Residents open their own page on their phone, with nothing to install: they see what they owe, report faults, and read announcements and reports. Dues are paid into the complex’s own bank account; you upload the bank statement and match the payments. We switch Apartment & Complex Management on in your account together with you.
- 3
- allocation methods, per budget line: equal, land share, m²
- 15 / 7
- days: general meeting notice periods checked
- TR · EN · AZ
- interface languages
We switch Apartment & Complex Management on in your account together — write to us.
How it works
- 01
Set up your complex
Create blocks and units with the bulk builder or import them from Excel; add owners and tenants with their dates.
- 02
Approve the annual budget
List the expense lines and choose the allocation for each: equal, land share or m². The budget moves from draft to provisional to approved.
- 03
Bill each month
See each unit’s amount in the preview and approve it. The same month cannot be billed twice, and rounding differences are shown openly.
- 04
Collect, match, report
Enter collections or upload the bank statement; matches are suggested using each unit’s payment reference. Publish the income and expense report to residents.
Who it’s for
- Owners who run their building as volunteers
- Management companies running several complexes
- Managers who want dues and expenses out of notebooks and Excel
Example
The path of a month’s dues
An illustrative flow; it does not describe a real business.
- Start of the month
The manager checks the preview and bills the month’s dues; for a rented flat, the charge goes to the tenant or the owner, as chosen.
- A few days later
A resident opens their page on the phone, sees what they owe, their payment reference and the complex’s IBAN, and pays by transfer from their own bank.
- Mid-month
A resident reports a lift fault with a photo. Common-area requests are visible to the whole complex without the reporter’s name; neighbours add “I have the same problem”.
- Month end
The manager uploads the bank statement and approves the matches suggested from the payment references; the receipts are ready.
- Year end
The income and expense report is compared with the budget and published to residents; the meeting notice and attendance list for the general meeting are prepared.
Live today
Complexes, blocks and units
- Several complexes in one account
- Units: land share, m², included in allocation or not
- Bulk unit builder
- Import units and people from Excel
- Owner and tenant history, with dates
- Officers: manager, auditor; assigning complexes to users
Dues and billing
- Annual budget: draft → provisional → approved
- Allocation per line: equal, land share or m²
- Monthly billing with a preview; the same month is never billed twice
- Rounding differences are shown, not hidden
- Tenant or owner responsible for the charge
- Late-payment charges and opening balances
Collections and bank statements
- Collections and advance payments
- Receipts (not an official document)
- A fixed payment reference for each unit
- Upload the bank statement as a file, approve the suggested matches
Resident page
- Opens on the phone, nothing to install
- Own balance and transactions; payment reference and the complex’s IBAN
- Announcements, documents and published reports
- Residents set their own password through a one-time link the manager passes on
Faults, requests and polls
- Fault and request reports with photos
- Common-area requests are visible to the whole complex; the reporter stays anonymous
- “I have the same problem”
- Advisory polls: one vote per unit
Income and expenses
- Expense entries with a photo of the receipt
- Cash and bank accounts, transfers between them
- Negative balance warning
- Income and expense report compared with the budget
- Publishing to residents: no personal data or flat balances included
- Year-end budget versus actual
General meeting preparation
- 15 / 7-day notice period check
- Agenda template and a printable meeting notice
- Attendance list: quorum counted on all units and land shares
- Proxy warnings and draft resolutions
- A read-only review screen for the auditor
Good to know
- Receipts and documents are not official documents or invoices.
- General meeting outputs are for preparation; they do not replace the notarised minutes book.
- Online polls are advisory; they do not replace a meeting resolution.
- Dues are paid into the complex’s own bank account; we never hold the money.
- We do not connect to the bank: the manager uploads the statement and approves the matches.
- No list of debtors is put on display; only the manager sees flat balances, and each resident sees only their own (data protection).
- The system sends no email or SMS: you print the meeting notice and pass on the invite link yourself.
The shared core underneath
The same in every block: users, permissions, security and records.
- Your own company space
- Each company’s data is isolated from others and lives at its own address.
- Roles and permissions per app
- A separate role per user per app; managers see only their team.
- Two-factor authentication
- A code sent by email; turned on per company.
- Audit log
- Who changed what, and when — recorded.
- You choose where your data lives
- AWS Frankfurt (EU) by default; on request AWS Istanbul (Türkiye) or your own servers (on-prem).
- Interface in three languages
- Turkish · English · Azerbaijani.
Next up
Planned, not live yet.- Online payment of dues
- Connecting to the bank to pull transactions automatically
- Sending announcements and invites by email or SMS
- Allocation by meters and heat cost allocators
- A mobile app from the app stores