Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
For property managers & landlords
Rent and service charge invoiced and reconciled, arrears aged and chased, repairs approved before the spend and logged with photos. Units, deposits, owner statements and costed work orders are the property layer, and it is a build rather than a feature — the honest split is below.
If any of these ring true, you are exactly who this was built for.
Rent lands across M-Pesa, three banks, and cash with vague references — and the first week of every month goes to working out who actually paid.
Repairs handled by phone calls and receipts: nothing tracked, nobody sure what was approved, and owners billed for work no one verified.
Deposits, landlord funds, and the agency's own income sit in one account — until a refund or remittance is due and the pool will not stretch.
Every landlord wants to know what their property earned and cost — and each statement is rebuilt manually, late, and inconsistently.
Each capability links to a deeper feature tour.
One invoice per unit with a unique reference; M-Pesa and bank payments matched automatically, so collection reconciles itself.
Overdue balances flagged and aged by 30/60/90 days per unit and building, so follow-up is prioritised, not guessed.
Every repair a task with photos, a checklist, an assignee and recurrence, and its spend approved before it happens. Not a work order: the task carries no unit, no owner and no cost of its own.
Expenses coded to department, category and project, purchase orders for parts and works, and payment out by bank or M-Pesa on a single register. Deposit segregation is not built — keep held money in its own bank account.
Parts and contractor spend flow through approved purchase orders, so maintenance money is controlled, not a cash run.
Invoices, payments and balances per customer, aged arrears, approved spend and contractor payouts — all real and exportable. The landlord statement itself is not generated; it needs the unit and owner records that are still roadmap.
Running in the product now
The property layer — on the roadmap, and commissionable now
Every item above is an absence rather than a position — there is nothing in this list we would decline, which is why this page has no third column. Each is commissionable now on the same terms as everything else here: a written specification, a timeline and a price, before any money moves. Property, unit and lease records are the right place to start, because the billing, the deposits and the owner statements all hang off them. The evidence that this is a real offer rather than a sales line is Kenya, where the eTIMS transmission and the maintained statutory payroll engine were both built exactly this way. We will not name a date on this page, and we will name one in a quote.
Be clear-eyed about the shape of this: the money layer is live and genuinely good, and the property layer is a build rather than a configuration. Agencies run on us today by using customers and projects where units would go — workable at one or two buildings, thin across a portfolio. If you want the property layer itself, that is a conversation we welcome and will scope in writing. If you need it live this quarter, buy a dedicated property package and keep us for the accounting.
Load units and issue referenced invoices — M-Pesa and bank payments start matching themselves, and the matching week disappears.
Every repair a task with photos and an assignee, and its parts and contractor spend on an approved purchase order. This is the step that stops the leak; the costing-to-unit half needs the property layer.
Collections, arrears and approved spend exported per customer and period, assembled into your own statement template. One click is what the property layer would buy you, and it is not built yet.
A managing agent is trusted with other people's buildings and other people's money. The four disciplines — collection, maintenance, trust funds, and owner reporting — that keep both in good order.
Collection is the heartbeat of an agency and where most bleed time. The cycle that ends the monthly matching game, ages arrears into a managed list, and reconciles every channel.
Maintenance is where agencies lose money and trust at once — through repairs nobody tracked, approved, or verified. A work-order discipline from report to verified-closed.
Questions we are asked here
Yes, at invoice level — the unit layer above it is roadmap work. An M-Pesa payment quoting the invoice number attaches to that invoice automatically and updates the balance, and unreferenced or partial receipts are still captured for you to attach by hand. Bank statement matching is not built and sits on the roadmap alongside it. The reference is per invoice rather than per unit, because property, unit and lease records are themselves roadmap items: agencies run today with the renter or the landlord as the customer, which works at a building or two and gets thin across a portfolio.
It does not yet, and this is the honest gap on the page. There is no deposit record, no per-unit deposit balance, no itemised deduction and no refund workflow in the product today, so held money is not segregated by the system and you should not rely on it for that. What is on the roadmap, and what we will scope in writing, is deposits held and proven per unit with itemised deductions and a refund flow. Until it ships, keep deposits in a separate bank account and reconcile them outside the system — and if segregated client money is the reason you are buying, say so now rather than in month three.
Not as a generated statement today; that is roadmap work. The underlying numbers are real — invoices, payments and balances per customer, aged arrears with reminders, approved spend and contractor payouts on one register, and documents attached to the transaction — so the components exist and can be exported. What is not built is the statement itself: collected, less fee, less costs, per landlord, per period, produced on demand. It needs the property and unit records it would hang off, which are the first thing we would build here.
Today it suits a landlord or agency whose main pain is collection and spend control rather than portfolio administration. Referenced invoicing, automatic M-Pesa matching, aged arrears with reminders, approved repair spend, contractor payouts and maintenance tasks with photos and checklists all work now. Recurring rent and service-charge runs, deposits, owner statements and work orders costed to a unit are roadmap items rather than live features. That trade is usually fine at a handful of units and gets steadily worse across a portfolio — so if you need the property layer this quarter, buy a dedicated property package and keep us for the accounting.
See referenced rent reconcile itself against real M-Pesa receipts, arrears aged and chased, and repair spend approved before it happens. Then ask us to show you a unit record, and watch us say it does not exist yet — that is the part worth testing.