Every feature, and when you would use it

A building is organized into blocks, entrances and floors; a district of houses into streets. Complexes can be archived, restored and cloned.

Use case: When you take over a new building, describe its blocks, entrances and floors once, or copy the structure of a similar complex you already run.

Apartments, houses, commercial space, offices, parking slots, storage rooms, land plots, and types of your own.

Use case: When a building mixes flats, shops and parking, every unit is registered with its own type, area and place, so fees and votes treat each kind correctly.

See a building floor by floor as a chessboard, or a district street by street, and edit units inline or in bulk.

Use case: When you need to spot at a glance which flats are vacant, rented out or in debt, open the chessboard instead of scrolling a spreadsheet.

Create hundreds of apartments, parking slots, storage rooms or houses at once and check the result before saving.

Use case: When a 200-flat building has the same layout on every floor, generate all the units in one step, with a different count on the floors that differ.

Bring an existing register over with an import wizard that shows every problem before anything is written.

Use case: When your unit and owner lists live in Excel today, import them as they are and fix the flagged rows instead of retyping everything.

A map of every parking level, slot and storage assignment or rent-out, and a registry of residents' vehicles.

Use case: When the guard finds a car in someone else’s slot, look up the plate and the slot’s owner or tenant in seconds.

Six steps take a new complex from its structure to its first invoices.

Use case: When you sign a new building, set up its structure, units, parking, fees, admins and owner invitations in one sitting, with a preview before anything is saved.

Define fees once per unit type or area; invoices are issued on the 1st of every month, with invoice, receipt and statement PDFs.

Use case: When the board sets the maintenance fee per square metre, enter it once and every owner gets a correct invoice on the 1st without anyone calculating it by hand.

A late fee of 0.1% a day after the 10th, capped at 10%, by default — each complex can adjust it.

Use case: When owners pay late month after month, the agreed penalty is added automatically and every owner sees the same rule applied.

Invoice, receipt and account statement PDFs for any period, in the owner's language.

Use case: When an owner asks what they paid last year, they download the statement themselves instead of calling the office.

Per-consumption fees for cold and hot water, gas and electricity, billed from last month's meter readings; a missing reading is estimated and corrected once the real one arrives.

Use case: When the building buys water for everyone and must pass the cost on fairly, each flat is charged for what its own meter measured.

Split one supplier bill for the common areas across the units, by area, equally or by meter readings, and charge each unit its share.

Use case: When the stairwell lighting and the elevator’s power arrive as one electricity bill, split it across the flats in a minute and record it as an expense.

Idram, Telcell, ArCa and card payments online on the Enterprise plan, plus bank transfer and cash recorded by the accountant on every plan.

Use case: When an owner wants to pay from their phone at midnight, they press Pay now; when another pays cash at the office, the accountant records it and the receipt is issued at once.

Owners upload a receipt for an offline payment and the accountant approves it — never the person who submitted it.

Use case: When an owner pays by bank transfer, they upload the receipt and their balance is updated after one click, without a trip to the office.

Import the bank's statement, match each transfer to its unit by invoice or flat number, review the doubtful lines and post the rest at once.

Use case: When a hundred transfers arrive at the end of the month, post them all from the statement instead of typing each payment.

Debt aging per unit, and payment reminders by email and SMS sent on the 5th and the 15th of each month or with one click.

Use case: When a few flats owe for three months, see them sorted by age and remind them all at once, without anyone having to make awkward calls.

A no-debt certificate from the unit's ledger, with a QR code that anyone can scan to check it is genuine and still valid.

Use case: When an owner sells the flat or takes a mortgage, they get the no-debt certificate the buyer, notary or bank asks for in minutes instead of days.

Plan the year, record expenses with their receipts and track the reserve fund against the budget.

Use case: When the board prepares the annual meeting, it shows the planned and actual spending per category and how close the reserve fund is to its target.

Project the replacement of the building's assets against the reserve fund, and see how far it is funded.

Use case: When the elevator will need replacing in five years, see whether the reserve fund will cover it and how much the contributions should be.

A “Where the money goes” page that shows owners how their fees are spent.

Use case: When owners ask why the fee went up, they see the approved budget, the spending so far and the collection rate for themselves.

Send to the whole complex, a block, an entrance, a floor or chosen owners, in several languages, now or at a set time.

Use case: When the water will be off in entrance 2 on Thursday, tell only the people of entrance 2, in their own language, and schedule it for the evening before.

See who has read an announcement and who has not, with their units.

Use case: When an important notice must reach everyone, see who has not opened it yet and follow up with those owners only.

A burst pipe or a power cut goes out at once by push, and by SMS while the messaging balance covers it, even to people who muted notifications.

Use case: When a pipe bursts at night, the concierge warns every resident at once and the alert stays pinned on top of their home page until it expires.

Every update in one place in the app, with an unread count, opened straight on the record it is about.

Use case: When an owner gets an invoice, a vote and a parcel in the same week, they find all three in the bell and open each with one tap.

Notifications by email, SMS, mobile and browser push and WhatsApp, each person choosing the channels per kind of update.

Use case: When an owner wants payment reminders by SMS but nothing about the community board, they set it once in their profile; emergency alerts always get through.

Notification, announcement and reminder emails carry an unsubscribe link that turns that kind of email off without signing in.

Use case: When someone no longer wants an email category, they leave it with one click, and the association stays on the right side of the rules for bulk email.

Conversations with the management and between neighbours, a group per entrance and one for the whole complex, with photos and files.

Use case: When a resident has a question for the office, they write in the chat instead of a phone call, and the moderator hides a rude message in the entrance group.

Simple polls and formal votes, counted one unit one vote or weighted by unit area × ownership share; formal votes check quorum.

Use case: When the board wants to replace the entrance doors, owners vote online over a week and the result is weighted and checked against quorum as the law requires.

Turnout by entrance or street as the votes come in, and a reminder to everyone who has not voted yet.

Use case: When quorum is still short two days before the deadline, see which entrances lag behind and remind only the owners who have not voted.

A formal vote ends with a PDF protocol of the result.

Use case: When the decision must be filed or shown to a contractor, download the signed-off protocol instead of writing it up by hand.

Elect the board or an audit commission online, with a nomination period, candidate statements, multi-seat ballots and proxies, and seat the winners as board members.

Use case: When the board’s term ends, owners nominate themselves, read each candidate’s statement and vote online, and the elected members get their board role on their own.

Notices, attendance, proxies and minutes for general meetings.

Use case: When a general meeting is called, owners register to attend in person, online or by proxy, and the minutes are published to everyone afterwards.

Folders, visibility per role, versions and languages for the charter, contracts and minutes.

Use case: When an owner needs the charter or last year’s minutes, they open the current version in their language instead of asking the office for a copy.

Requests with photos, assigned to staff or vendors, with a 4-hour clock for urgent ones and 48 hours for the rest.

Use case: When the elevator stops, the request goes to the right technician with a deadline, and the admin sees at once which tickets are about to run late.

Owners report a problem from their phone with photos, follow it step by step and rate the work when it is done.

Use case: When a resident sees a leak on the stairs, they report it with a photo in a minute and no longer have to call to ask whether anyone is on it.

Keep your contractors on file with their contracts, and schedule recurring work such as elevator checks, with a reminder to residents the day before.

Use case: When the elevator is inspected every month, plan it once; the residents of that entrance are reminded the day before, and the contract’s end date is flagged in time.

The building's equipment — elevators, pumps, the roof, the intercom — with its warranty and expected life, linked to its tickets and planned work, and an alert before a warranty ends or a replacement is due.

Use case: When the pump fails, see its age, warranty and repair history in one place, and get warned a month before its warranty ends.

Book the gym, the meeting hall or the BBQ area by the slot, with the rules, fees and approval each amenity has.

Use case: When two families want the BBQ area on the same Saturday, the first booking takes the slot and the second sees it as taken, with no double bookings to sort out.

Residents issue a pass with a QR code or a link for a guest, valid for a day and a time window.

Use case: When a friend is visiting on Saturday, send them a pass by message; the guard scans it at the gate without calling the flat.

The front desk sees who is expected, who is inside and which parcels are waiting, and residents are notified when a guest or a parcel arrives.

Use case: When a courier leaves a parcel at the desk, the concierge logs it and the resident gets a notification instead of a note on the door.

Owners request a permit for renovation works with plans and dates; the management approves it with conditions or rejects it, takes and returns a deposit, and the front desk sees whose contractors are expected.

Use case: When a neighbour starts knocking down a wall, the management already knows the works, their allowed hours and the contractors, and a breach becomes a violation in one click.

Owners submit readings between the 20th and the 25th of each month, with reminders when the window opens and before it closes; unusually high ones need a photo and the management confirms them.

Use case: When it is time to read the meters, owners enter the figures from their phone instead of a sheet on the door, and a mistyped reading is caught before it is billed.

Residents report noise, parking and other rule breaches with photos; the management warns, fines or dismisses, and the reporter stays anonymous to the neighbour.

Use case: When a car keeps blocking the gate, a resident reports it with a photo and the management issues a warning, then a fine charged to the unit’s account.

Posts between neighbours — lost, found, for sale, given away or a service offered — checked by the management before they appear.

Use case: When someone finds keys in the yard or sells a pram, they post it for the whole complex instead of taping a note in the lift.

Emergency numbers, the management office and utilities in one list, one tap to call.

Use case: When the gas smells at night, residents find the emergency number and the management’s phone in the app in seconds.

Ask about the next general meeting or the pool rules and get a short answer drawn from the complex's documents, announcements and rules.

Use case: When a new resident asks at 11 pm when the gym opens, the assistant answers from the amenity rules instead of the manager’s phone ringing.

Owners ask how much they owe or what happened to a request, and get their own data — never a neighbour's.

Use case: When an owner asks “what do I owe and by when?”, they get their own balance and due date in a sentence.

Every answer cites where it came from, and says so when the complex's information does not cover the question.

Use case: When the answer matters, open the cited paragraph of the charter and check it yourself.

The assistant only sees what the person asking may see, and answers in their language.

Use case: When an accountant and an owner ask the same question, each gets an answer from what their own role may see, in Armenian, Russian or English.

Admins ask how to do something in the portal and get numbered steps from the user guide, with buttons that open the right screens and the next step of the setup checklist.

Use case: When a new admin asks “how do I add the fees?”, the assistant explains the steps and opens the Fees page.

Org and complex admins, accountants, board members, maintenance staff, concierges, owners and residents — each role's permissions can be tuned per complex.

Use case: When the board member should see the finances but not change them, untick that permission for the role in this complex only.

The same person can manage one complex and own a flat in another, and switches between them in the header.

Use case: When the accountant of one building also owns a flat in another, they keep one login and switch between the two from the header.

Security-relevant actions are written to an append-only log chained with HMAC, and a check proves nothing was changed.

Use case: When an owner disputes a payment reversal, show exactly who did it and when, and prove the record was never edited.

Each management company's data is kept apart; outside your scope, a record simply does not exist for you.

Use case: When a management company runs several associations, each association’s data stays separate from every other customer’s.

Secrets are encrypted with AES-256-GCM, sign-in tokens are short-lived and every device has its own session.

Use case: When a phone with the portal open is lost, change the password and every other device is signed out at once.

An optional second step with an authenticator app, recovery codes, and a password change that signs out every other device.

Use case: When an admin who can approve payments wants their account safe even if the password leaks, they turn on two-factor authentication in a minute.

Admins can see an owner's view to help them — read-only, and every view is audited.

Use case: When an owner calls because they cannot find their invoice, see exactly what they see and guide them, without being able to change anything.

Your logo, colours and font across the web app, without the “Powered by HOA.AM” line if you prefer. Your colours are checked for contrast in the light and dark themes before they are used.

Use case: When owners should feel they are using your company’s portal, not a third party’s, they see your logo and colours from the sign-in page on.

Invoices, statements, receipts and every other PDF carry your name, logo and legal details.

Use case: When an invoice is forwarded to a bank or a tenant, it looks like your own company’s document.

Emails and notifications go out under your company's name, and email replies reach your own address once you confirm it.

Use case: When an owner replies to a payment reminder, the reply lands in your office mailbox.

Owners and staff sign in at your address, such as portal.your-company.am, on a sign-in page in your brand.

Use case: When you print the portal’s address on the entrance posters, it is your own domain.

The mobile app shows your logo and colours for everyone in your complexes.

Use case: When owners install the app, it opens in your company’s colours.

A complex can show its own name and logo, while your company's colours and font stay the same.

Use case: When one of your buildings has its own well-known name, its residents see it while your company’s look stays the same.

Dates as DD.MM.YYYY with a 24-hour clock, and amounts in Armenian dram by default.

Use case: When owners read an invoice, the dates and amounts look the way they are used to in Armenia.

A complex can use any active currency — USD, EUR, RUB and others — for all of its fees and payments.

Use case: When a commercial building charges its tenants in US dollars, set the complex’s currency once and every fee, invoice and payment follows it.

A total across complexes is shown per currency and never converted, so no exchange rate ever changes a figure.

Use case: When a management company reports on complexes in drams and in euros, each total stays exact in its own currency.

Invoice dates, late fees and meter-reading windows follow the complex's own time zone.

Use case: When a complex is abroad, its invoices go out on the 1st of its own month and its deadlines end at its own midnight.

Every owner, co-owner, tenant and family member of each unit, with ownership shares, contacts and status, and an export to Excel or PDF.

Use case: When a flat has three co-owners, record each one’s share once; votes are weighted by it and every co-owner sees the invoices.

Invite owners to the portal by email, SMS or a link with a QR code, in their own language, and resend it when it gets lost.

Use case: When you add the owners of a new building, each gets an invitation that already knows their flats, so they join in two minutes.

A printable poster for each entrance; residents scan it, type the email or phone they were registered with and get their invitation again.

Use case: When owners lose the invitation email, they scan the poster in their entrance instead of calling the office for a new one.

Owners add family members and tenants to their flat with limited access, and take it away when they move out.

Use case: When an owner rents out the flat, they invite the tenant to get the building’s announcements and report problems, without showing them the owner’s payments.

Move a unit to its new owners on the date of the sale, with the deed attached, and keep the full ownership history.

Use case: When a flat is sold, record the sale once; the old owner leaves on that date, the new one is invited, and the history shows who owned it when.

Owners upload their ownership certificate, and the management marks the owner as verified.

Use case: When the management needs to be sure who really owns a flat, it checks the uploaded certificate and marks the owner verified.

Each owner keeps their own phone, emergency contact and language, and can hide their phone from neighbours.

Use case: When an owner changes their number, they update it themselves and the office always has the right contact.

The concierge, security, cleaning and maintenance staff, their weekly shifts and the account each one signs in with.

Use case: When a resident asks who is on duty tonight, the shifts answer it, and a new concierge gets the right access when linked to their staff record.

The Org Admin, the building admin and each owner get a dashboard built from widgets they can hide and reorder.

Use case: When the building admin opens the portal in the morning, the collection rate, the debtors, today’s tickets and unread messages are all on one page.

Each complex rated healthy, watch or at risk from its collection rate and how many tickets meet their deadline, with alerts for low collection, overdue urgent tickets and ending contracts.

Use case: When a management company runs twenty buildings, it sees at once which three need attention this week.

Collection, debt, tickets and usage per complex over the last 3, 6 or 12 months, exported to Excel or CSV.

Use case: When the management company reports to its associations each quarter, compare the complexes over the period and attach the export.

Find a unit, an owner, a car plate, a ticket or a document from any page with ⌘K, within what your role may see.

Use case: When the guard reads a plate or an owner calls about flat 47, type it once and open the record.

Every list keeps your filters, sort and columns as a named view to come back to.

Use case: When the accountant checks the overdue invoices of entrance 3 every Monday, it is one saved view away.

Every list exports to Excel or PDF in your language, prepared in the background and kept in My exports.

Use case: When the auditor asks for last year’s payments, export the filtered list to Excel instead of copying it by hand.

Sign up your association yourself, confirm your email and start on the Free plan or a free trial, straight into the setup wizard.

Use case: When you want to try HOA.AM on your own building, you are setting it up within minutes, without a sales call.

Your own copy of a demo complex, opened from a link we email you, where you sign in as an admin, an accountant or an owner with one click.

Use case: When you want to see how an owner and an accountant each use the portal before you decide, try both roles on realistic data that nobody else sees.

A Getting started checklist for each complex that ticks itself off as you set things up, with a button to the screen for each step and a guide to read.

Use case: When you set up a new complex over several days, always know what is left, such as the payment methods, the late-fee rule or the first announcement.

Short answers for the page you are on, a searchable help centre and keyboard shortcuts, in English, Armenian and Russian.

Use case: When an accountant is not sure how to reverse a payment, they open the help for that page instead of calling support.

A short tour for each role at the first sign-in, and tips the first time a page is opened, replayable at any time.

Use case: When an owner signs in for the first time, a one-minute tour shows them where to pay, vote and report a problem.

Every checklist step and help article has an Ask the assistant button that answers with steps and links to the right screens.

Use case: When a step is unclear, ask in your own words and get the steps for your role.

The Billing page shows your plan, what it includes, how many units, complexes, users and storage you use, and an estimate of this month’s bill.

Use case: When the board asks what the portal will cost this month, the estimate is on the Billing page, with the usage behind it.

A warning at 80% and 100% of your plan’s units or storage, before anything stops working.

Use case: When the association is about to add a new block, you see in advance whether the plan has room for its units.

A monthly invoice for the platform, paid online or by bank transfer with the receipt uploaded for approval.

Use case: When the invoice arrives, pay it from the Billing page in a minute, or upload the bank receipt.

SMS and WhatsApp messages are paid from a prepaid balance of the organization or a complex, topped up by bank transfer, with a warning when it runs low.

Use case: When you want reminders and alerts to reach owners by SMS, keep a balance topped up and see what each message cost.

Try a paid plan free for a trial period when you sign up; without a purchase the organization moves to the Free plan.

Use case: When you are choosing between plans, try the paid one on your real building first.