> ## Documentation Index > Fetch the complete documentation index at: https://docs.nyumbazetu.com/llms.txt > Use this file to discover all available pages before exploring further. # Introduction > What Nyumba Zetu is, who uses it, and how this documentation is organised. **Nyumba Zetu** is a property management platform built for the East African market. It runs the full lifecycle of a managed property portfolio — units and leases, residents, billing and rent collection, arrears recovery, payables, double-entry accounting, KRA tax compliance, utilities and smart meters, owner payouts, and tenant-purchase (ownership) schemes — in one system. The platform is **multi-tenant and white-label**: each organisation gets its own branding, its own branches, its own configuration, and strict data isolation. ## Who uses it Run day-to-day operations across many properties, blocks, units and leases — billing, arrears, maintenance, utilities, and communications. Issue and settle invoices, allocate payments, post to the general ledger, close periods, file to eTIMS, and produce statutory statements. See their own units, statements, management fees, and disbursements. Use the tenant portal to view bills and statements, pay, submit service requests, and book amenities. ## The shape of the product Nyumba Zetu is organised around a small number of core records that everything else hangs off: | Record | What it is | | ------------------------- | ------------------------------------------------------------------------------------------------------------- | | **Organisation / branch** | Your company and its operating branches. Almost every screen is scoped to the branch you are currently in. | | **Block & unit** | The physical property. A block holds units; a unit is the billable place. | | **Lease** | The contract between an organisation and a resident for a unit. Rent, charges, dates, and deposits live here. | | **Resident** | The person — tenant, owner, next of kin, or other contact — attached to a lease. | | **Invoice & payment** | What was billed and what was received. Allocation links the two. | | **Journal** | The double-entry projection of every money event, driving the financial statements. | **Money lives in one place.** Invoices, payments, allocations, credit notes and balances are authoritative in the platform's core ledger. Modules such as Collections, Penalties and IoT billing *orchestrate* around that ledger — they never keep a second set of balances. This is why figures on a case page, an aging report, and a tenant statement always agree. ## What you can do Create leases, assign residents, manage charges, renewals, and offboarding. Issue invoices, run recurring invoices, apply escalations, and reconcile. Record M-Pesa, bank and cash receipts, then allocate them against debt. Score arrears, work a ranked case queue, send demand letters, and escalate. Chart of accounts, periods, journals, trial balance, P\&L and balance sheet. Submit invoices to KRA through DigiTax and track certified receipts. Smart-meter readings, consumption, tariffs, billing runs and valve control. Owner contracts, management fees, statements, and disbursements. Financial, operational and portfolio reporting with export. ## How this documentation is organised * **Start here** — orientation: sign in, the layout of the app, roles, and vocabulary. * **Property & tenancy** through **Tenant experience** — one section per product area, ordered the way work actually flows: property → tenancy → billing → collection → accounting → operations. * Each guide states **where the screen lives**, **what it does**, **the step-by-step workflow**, and **what to check when something looks wrong**. Screens marked **Beta** in the app sidebar are live and supported but still changing. Where a guide covers a Beta surface it says so at the top, and notes anything gated behind a feature flag your administrator has to switch on. ## Next steps Sign in and complete your first end-to-end task. Branches, the sidebar, grids, filters, and views.