Axio

Site and residence management, on a single platform.

Axio brings dues and collections, requests and work orders, the front desk, the owners’ board and resident communication onto one shared record. The management team works in the web console, residents in the mobile app, and every action leaves a trail.

Request a demo Explore the modules

Rule templates based on the Turkish Condominium Law (KMK)
Four-eyes approval for anything that moves money
Turkish and English interface

Axio management console overview (Turkish UI): collections this month, collection rate, outstanding receivables and open requests; cash-flow chart and today’s plan.

Modules

From the management office to the front desk, one system.

The modules are connected: a cash payment taken at the front desk settles the receivable, a request a resident opens on the phone lands in the technical team’s queue, and a board decision updates the operating budget.

Finance & collections

Dues, collections and cash desk on one ledger.

From the operating budget to monthly charges, from bank transfers to receipts, every lira is tracked in a double-entry ledger. Balances are never edited by hand; each correction is a justified, approved entry.

Monthly dues charged from the operating budget; each cost line split equally or by land share.
Bank transfer, card and cash payments settle the same receivable; late fees follow the configured rule.
Front-desk cash desk: a numbered receipt for every cash payment, cash handover subject to approval.
Four-eyes approval: preparers cannot approve their own work; one or two approvers by amount.
Bank statement import (including MT940), automatic matching and a review queue for differences.
Instalment plans, refunds, period close and export to the accounting system.

Finance and collections screen (Turkish UI): total charges, collected, outstanding, overdue and reconciliation difference; a per-unit list of charges.

Requests & work orders

Every request has an owner and a deadline.

Faults, maintenance and resident requests share one operations queue. SLA deadlines follow the business calendar; at-risk and breached work stands out on the board.

A request flow tracked through new, assigned, in progress, waiting, resolved and closed.
SLA deadlines computed from the policy version and business calendar; a reason is required to pause.
Kanban and list views, work orders, assignment and checklists.
Shift handover: open work is handed over and the next team acknowledges it.
Technicians only see work for the blocks they are assigned to.

Requests and work screen (Turkish UI): open work, SLA risk and awaiting assignment; a kanban board with New, In progress, Planned and Done columns.

Front desk

A front-desk board instead of a paper logbook.

Who is away, who is expected, which parcel is where, who holds which key: the front desk and security team run the day from one screen.

Units away today, authorised entries, delivery instructions and follow-ups.
Visitor and entry permissions: which unit, who, between which dates.
Valet: requested, assigned, retrieving, ready and handed over, every step recorded.
Amenity bookings: pool, spa, meeting room, guest suite, with conflict-free capacity.
Unit notes carry a sensitivity class and audience; restricted notes are masked for others.
Key handovers with a signed chain of custody.

Front-desk board (Turkish UI): units away today, authorised entries today, instructions and follow-ups.

Board & governance

From the meeting to the resolution book.

Owners’ board meetings, the resolution book, the operating budget and office holders in one place, with the quorum rules of the Condominium Law.

Meeting notice, agenda, proof of notice and attendance; first and second session.
Resolution book: resolution number, book page and challenge-period tracking.
Approved and provisional operating budgets; revisions require approval.
Manager and auditor terms, with a warning before they end.

Board management screen (Turkish UI): next meeting, open meetings and manager term; the resolution book table.

Announcements & messaging

The right people, through the right channel.

See who an announcement will reach before you publish it. Resident messages can be linked to a request, and message bodies are stored encrypted.

Announcements with an audience preview, scheduled publishing and read receipts.
In-app notifications, mobile push and Turkish e-mail templates.
Resident conversations; turn a message into a request directly.
Per-user notification preferences.

Reports

The morning on one screen: money, work, today.

The overview shows collections, collection rate, outstanding receivables and open requests together, with the detail one click away.

Portfolio, operations, maintenance, resident and security reports.
Exports of collection and receivable lists; scheduled reports.
Auditor role: read-only access to finance, reports and the audit log.

Resident app

Residents pay their dues and follow their requests.

Owners, tenants and household members see what belongs to their own unit. They pay, open requests and book amenities without calling the management office.

Payments: Current balance, line-by-line breakdown and receipts. Pay by card or by bank transfer with a unit-specific reference code; re-authentication before paying.
Requests with photos: Open a request with photos, follow its status, see the planned visit and rate the result.
Push notifications: Request status, updates and visit notifications; each category can be switched on or off.
Bookings and announcements: Amenity bookings, site announcements and unit notes such as letting the front desk know you are away.

Security & privacy

Security was not bolted on later.

Tenant isolation, permissions and the audit log are part of the core. Everything below is a control that runs today.

Tenant isolation

Each management company’s data is separated at the database level with row-level security (PostgreSQL RLS). Without a tenant context, access is denied by default; isolation is exercised by automated tests.

Audit log

Every change is recorded in the same transaction: who, when, which record, the reason and the approval. The application cannot alter or delete the audit log. Passwords, card numbers, full IBANs and message bodies never enter it.

Roles and permissions

Permissions take the form “domain.resource.action”; roles are editable and can be scoped to a block or unit. Time-limited delegation is supported; there is no unrestricted “super admin”.

Four-eyes principle

Manual payments, receivable adjustments, budget revisions and rule changes require approval; the preparer cannot approve their own work.

KVKK-minded data handling

Data is classified (internal, confidential, restricted). Data subject requests, data exports, retention periods, legal holds and erasure or pseudonymisation jobs run inside the system. Card data stays in the payment provider’s flow.

File safety

Uploaded documents and photos are scanned in quarantine and only become available once clean.

Approvals screen (Turkish UI): pending approval requests with preparer, required approvals and status.

Axio provides tools that support KVKK (Turkish data protection law) processes; each site’s compliance assessment remains with its management, as data controller, and its legal counsel.

How it works

Up and running in three steps.

Describe your site
Blocks, units and land shares; owners, tenants and opening balances are imported from files.
Set up rules and the team
Condominium Law templates, the operating budget, approval limits, roles and scopes. Site-specific exceptions are added as approved rule versions.
Run day to day
Management and the front desk work in the web console, residents in the mobile app. Reports are live and every action is in the audit log.

Request a demo

See Axio with your own site’s data.

Tell us how large your site is and which tools you use today, and we will plan a demo that fits.

Request a demo by e-mail

E-mail address: iletisim@axiotürkiye.com