Residential Dues Management

The flows below were tried on the live demo and on a local sample installation. Automated tests also verified that the same statement row cannot create a second payment. The “Boş siteyle yeniden başla” (start with an empty site) button on the demo’s setup page was not tried for this page; the demo never sends notifications, so they do not appear in the screens (their limits are under “Limits”).

• Blocks, flats, owners and tenants; flat numbers are filled in a table of ready rows by typing only a name (and a phone if wanted), by pasting a list from WhatsApp or Excel, or by an Excel/CSV file; a preview is shown before saving (columns are recognised by their header, an unwanted row is left out, the last import can be taken back); carried-forward balances
• Monthly dues: the same amount for every flat or a simple calculator from the expenses (equal, by square metres or by land share); where there is central heating, the heating charge is written as a separate line. For a charge you only pick the month, the preview shows the total and nothing is written before you approve; an optional “monthly automatic charge” setting exists (off by default)
• Cash or bank-transfer payments entered by hand (the amount comes ready as the debt, the method starts as the last one used), bulk collection (overdue flats in a table, tick who paid, a separate receipt for each flat), approval of the resident’s payment notice, receipts, partial payments, expenses and transfers between accounts; on the debtors page a tap on a row opens “Tahsilat gir” (record a payment), “WhatsApp’tan hatırlat” (remind on WhatsApp) and “Hesabı aç” (open the account)
• Statement file (CSV/Excel) upload with an explained matching suggestion by flat payment code, sender and amount, posted after the manager’s approval
• A step-by-step setup wizard with a progress bar (“Kurulum %50 · Sıradaki: …”, setup 50% · next): when one step is done the next opens; a closed “Bu ekran ne işe yarar?” (what is this screen for?) box on each panel screen; faulty rows and empty screens say the next job in a sentence
• Telling residents: a ready WhatsApp message, copy the link and an A4 poster with a scannable code for the door; the resident portal has a balance card, annual summary, monthly chart, statement and payment details; payment notices and requests are worded from the resident’s side (“Yönetim kontrol ediyor”, “Ödemeniz alındı”, “Aldık”, “Tamamlandı”)
• Plain screen (on in a new installation): big buttons on the home screen: “Ödeme aldım” (I took a payment), “Kimler borçlu?” (who owes?), “Bu ayın aidatını yaz” (write this month’s dues), “Kim ödedi?” (who paid?), “Duyuru yaz” (write an announcement), “Gider yaz” (write an expense); rarer pages under “Diğer işlemler” (other tasks); larger type. You can switch to the detailed screen
• Free instant notification (Web Push): to the manager and staff for a new payment notice and a new request, to the resident for “ödemeniz alındı” (your payment was received), an announcement and a request update; it carries no name, phone number or balance. There is an add-to-phone button and a setup page without sign-in; the management icon opens the management sign-in and the resident icon the resident page. It is not an SMS or a WhatsApp message, so there is no message fee
• Şeffaf Kasa (open ledger, off by default): when management switches it on, a monthly summary that anyone with the secret-key address opens without signing in; what was collected, spending by expense type, the cash left and a “X / Y flats paid” bar. No names, phones, debtor list or expense supplier are shown; each expense can be hidden from the list, the address can be renewed and the page is closed to search engines
• Building directory (firms such as lift, cleaning and security, plus the caretaker and building staff; a resident taps a number to call) and building rules (management writes plain text, residents read it)
• “Kime ulaştı?” (who was reached) under an announcement: how many flats it was opened to, how many of them have a resident portal account, how many opened it in the portal and a flat-by-flat list; it says plainly that flats without a portal account are not reached through the portal. A PDF (up to 5 MB) can be attached to a request next to a photo
• Staff and residents see only the pages, buttons and links they are allowed to use; no path to a page they cannot open is shown (the server still refuses an address typed by hand)
• Maintenance requests, announcements with ready texts, a debtor list (“everybody with a balance owed” or only the overdue), income and expense reports, backups and restore
• On the live demo there are password-free “… olarak gir” (sign in as …) buttons for manager, staff and resident

What you do

• With your own installation (A): you prepare the hosting, domain, secure connection (SSL) and database; upload the package, run the setup wizard, and set up backups and scheduled tasks.
• With our installation (B): you open the hosting and domain account in your own name, give access through a secure channel, provide the details on the data-transfer form and approve the acceptance list.
• In both cases: you enter the block, section and people details or import them from Excel.

Installation requirements

• PHP 8.2 or newer; pdo with pdo_sqlite or pdo_mysql, plus the mbstring, json, openssl, fileinfo and zip extensions.
• SQLite or MariaDB; tested with MariaDB 10.11 and 11.4. On other versions, extra checks are needed after installation.
• A secure connection (HTTPS) is required; at least 200 MB of free space.
• A settings file for Apache/LiteSpeed is ready; Nginx rules are in the documents.

Support and updates

• Support and update terms have not been set yet; support hours and response time have not been decided either.

Release notes

• Summarised from the package’s release notes (CHANGELOG). The live demo runs version 1.1.32; 1.1.32 is still marked as a “candidate” and has not been tried on a customer’s hosting.
• 1.1.32 (26 October 2026): in the demo Şeffaf Kasa, the building directory and the building rules come with sample data; staff and residents see no link, button or row that leads to a page they are not allowed to open (the server still refuses it); the activity log is in Turkish; the resident menu has the building directory and rules; on the resident’s payment details the late fee is explained as two separate figures.
• 1.1.31 (25 October 2026): Şeffaf Kasa (the open ledger: a public monthly summary, off by default, showing no names or debts); the building directory (firms, caretaker, staff); “Kime ulaştı?” (who was reached) under an announcement; a PDF attachment on a request next to a photo; building rules. The database schema goes from 5 to 6 and old data is kept.
• 1.1.30 (21 October 2026): “Bölüm ve kişi ekle” (add units and people) takes a list from your old program or Excel as it is: columns are recognised by their header (Daire No, Ad Soyad, Telefon, Borç…), a column that is not recognised is chosen by hand in the preview, an unwanted row is left out with “Alma” (do not take), and the last import can be taken back with one tap; nobody is messaged in the preview or during the import.
• 1.1.29 (20 October 2026): in the setup wizard each step’s card opens that step’s page; the debtors page opens with “everybody with a balance owed”; the dues table opens on the current month; the announcement form was simplified.
• 1.1.28 (19 October 2026): an optional monthly automatic charge (off by default), bulk collection, status wording from the resident’s side on the resident page.
• 1.1.20–1.1.27 (19 October 2026): a simple setup that keeps people from getting stuck: a wizard that moves on when a step is done, a flat list with ready rows and pasting, telling residents (a ready WhatsApp message, a poster with a scannable code), a hint when stuck, an optional automatic reminder (off by default), a tap on a row opens its card, a two-step confirmation for deleting a person’s details.
• 1.1.19 (18 October 2026): a plain screen (a home screen with big buttons), an add-to-phone button and a setup page without sign-in, a free instant notification (Web Push) for manager and resident.
• 1.1.9–1.1.18 (18 October 2026): a guidance package (a setup wizard and progress bar, a “Bu ekran ne işe yarar?” box on each screen), “Boş siteyle yeniden başla” / “Örnek veriyi geri yükle” in the demo, a three-way page for adding flats and people, a simpler Settings page, a monthly dues page and central heating, a simpler charge page.
• 1.1.3 (7 October 2026): the web app manifest and the colour sheet no longer leave an unnecessary session cookie.
• 1.1.2 (6 October 2026): “Add to home screen” support for the resident portal (web app manifest, home-screen icons, help steps); there is no offline mode.
• 1.1.1 (4 October 2026): text and label corrections only; screen texts now match the scope of “no automatic bank movement retrieval or matching”, and the code behaviour did not change.
• 1.1.0 (4 October 2026): an optional meeting link (https address) on a meeting decision; announcement and dues e-mails sent by the manager’s button (the same message never goes to the same person twice); database schema 3 to 4.
• 1.0.18 (4 October 2026): printing the dues table is limited to 12 months.
• 1.0.13 (3 October 2026): the dues table, Excel (.xlsx) export, and a demo with three buildings and 96 flats.

Decisions not made yet

• Rights to use, modify, transfer and receive the source code: to be set in a written agreement; not decided yet.
• Support hours and response time have not been decided yet.
• The tax and invoicing arrangement has not been decided yet.