Everything you can
ask it to do.

Lists the strata plans under management, narrowed by plan number, plan name or address. Start here when you know the building by name or suburb but not by number.

Full details for one strata plan — its name, address, scheme type, bank accounts and configuration.

The strata manager responsible for a building, with their contact details — for "who looks after this one?"

The owners corporation committee for a plan, with each member's role — chairperson, secretary, treasurer and ordinary members.

Every lot in one plan, with owner and levy details. You can narrow the list by lot number, unit number or owner name — and this is the reliable way to find an owner by name.

Searches every plan for a lot by its identifier — unit number, lot number or external reference — and returns the plan and lot references the other actions need. Searching by owner name here is unreliable, so your assistant will ask which building instead.

Full details for one lot — owner and contact details, unit entitlements, address, and how levies are configured against it.

An owner's full record — name on title, entity type, postal and email addresses, and phone numbers.

Lists all the lots one owner holds, across every plan — an investor's whole position in your portfolio in one answer.

The acquisition record linking an owner to a lot — settlement date, disposal date if they've sold, and the share of title held. The way to confirm whether an owner is current or historical.

The extra contacts recorded against an owner — a managing agent, a solicitor, a power of attorney — who should receive copies of correspondence. Ask for the list, or open one in full.

The strata management company operating the Urbanise tenant — trading name, ABN, addresses and contact details. Useful when drafting correspondence that has to carry the agent's own details.

Records a new owner against a lot — the change-of-ownership step once a sale settles. The outgoing owner isn't removed automatically, so your assistant will check whether they still need a disposal date.

Updates the acquisition linking an owner to a lot — most often to set the disposal date when the lot has been sold, so the outgoing owner stops appearing as current.

Updates an owner's record — typically a corrected postal address, email or phone number.

Attaches an extra contact to an owner — an agent or solicitor — corrects one already on file, or removes one for good. Your assistant checks the existing contacts first so you don't create a duplicate, and reads a contact back before removing it.

Adds a lot to a plan, or changes one that exists. Updating reads the whole lot first and sends the complete record back, so nothing already on file is quietly dropped.

Brings a new building under management, or changes an existing plan's details. Creating a plan is a significant change, so your assistant checks the plan doesn't already exist and confirms with you first.

The levy summary for a whole plan — what has been struck per period per fund, what has been collected, and what's outstanding. The building-level arrears picture in one answer.

The levy ledger for a single lot — each levy period with its issue and due dates, administrative and capital works amounts, penalties, what's been paid, and the balance outstanding. Filter to a date range if you only want part of the history.

Calculates what a lot owes as at a given date, including levies raised, interest and any recovery costs — a provisional invoice, which is what a settlement or a certificate enquiry usually needs.

The payment references configured for a building — BPAY biller code and customer reference format — so you can tell an owner exactly how to pay.

The reverse lookup: given a BPAY biller code from a bank statement, find the plan bank account behind it. For reconciling a payment you can't place.

Raises a charge against a single lot outside the regular levy cycle — a special levy, a debt-recovery cost, or a charge for damage to common property. This creates a debt the owner is liable for, so the amount and the reason are confirmed with you first.

Attaches supporting documentation to a one-off levy already raised — the invoice, quote or notice that justifies the charge.

Records a levy payment received from a lot owner and allocates it against their outstanding levies. Money movements can't be reversed through the assistant, so the amount, date and lot are confirmed before it goes through — and your assistant will read the ledger back afterwards to show you how it was allocated.

The budget for one plan, financial year and fund, broken down by account with budgeted and actual amounts. The administrative fund and the capital works fund are separate cost centres with separate budgets.

Lists the cost centres configured for a plan — typically the administrative fund and the capital works fund, plus any sub funds the building runs.

The term deposits and investment accounts held by a plan, with balances, rates and maturity dates — for "when does that TD roll over?"

Costs incurred on a plan's behalf that haven't yet been charged to it — postage, printing, searches and the like.

Records costs incurred on a plan's behalf so they can be recovered — postage, printing, searches, certificates.

Searches the receipts posted to a plan's general ledger by date range, lot, reference or receipt type. Use it to trace a specific payment — "did we ever receive this cheque?" — rather than to read an owner's balance.

Accrues a cost you know is coming against a plan, so it shows in the building's financial position before the invoice arrives.

Updates an existing accrual — usually to correct the accrued amount once the real invoice comes in.

Permanently removes an accrual and records why. This changes the plan's reported financial position and can't be undone, so it's read back and confirmed with you first. Correcting the amount is usually the better move.

Enters a supplier invoice against a plan, attaching the scanned invoice document at the same time.

Updates an invoice already entered — a corrected coding, an amount, or the work it relates to.

Uploads a quote, statement or remittance against a plan or an invoice, so the paperwork sits with the transaction.

Lists the accounts receivable invoices raised by the owners corporation — common property rent, key and access charges, recovery of damage costs. Filter by plan, lot, date range and whether they've been paid. Levies aren't receivables; for those use the lot ledger.

Opens a single accounts receivable invoice by the reference number printed on it.

Records a payment received against a receivable invoice. This moves money in the plan's books and can't be reversed through the assistant, so the amount and date are confirmed against the bank record first.

Every supplier on the books, with trade, contact details, insurance and licences. Ask for only those changed since a date if you're keeping another system in step.

One supplier in full — trading name, ABN, trade, bank details, public liability cover and licence expiries.

The suppliers a building has nominated as preferred. Worth checking before recommending a trade — the committee may have a standing arrangement.

The suppliers a building has blacklisted. Always check this before raising a work order for that plan.

The licence types configured in Urbanise — electrical, plumbing and so on — used when recording a supplier's credentials.

Creates a new supplier. Your assistant searches the existing list first — duplicate supplier records cause payment errors later.

Updates a supplier — renewing an insurance certificate or licence expiry, correcting bank details, or changing contact details.

The standing instructions a building wants included on every work order sent to a contractor — access arrangements, hours, site rules.

The documents attached to a plan's work orders — quotes, invoices, completion photographs and reports. Very large files are described rather than returned in full.

The policies recorded against a plan — building, public liability, office bearers, workers compensation — with insurer, sum insured and expiry.

Records a new insurance policy against a plan.

Updates a policy — a renewal, a change of sum insured, or a corrected expiry date.

The task types configured in Urbanise — maintenance request, by-law breach, insurance claim and so on. Your assistant reads these before creating a task so the right type is used.

Raises a task in Urbanise — a maintenance request, a by-law follow-up, a compliance item — with a title, description, type, priority, dates and who it's assigned to. It lands in a real person's work queue, so your assistant confirms it with you and writes a description someone can act on cold.

Attaches a document to an existing task — a photograph of the defect, a quote, a report.

A tenant's name, contact details and the lot they occupy — for access, by-law matters and notices.

Records a new tenant against a lot when a lease starts, or updates one — corrected contact details, or recording that a lease has ended.

The common property areas in a building — visitor car spaces, storage cages, rooftop areas — including which can be let.

The rental agreement over one common property area — who holds it, the rent, and the term. You can ask for it as at a particular date to see a historical or future agreement.

Sets up a rental over a common property area — letting a visitor car space or a storage cage — or changes one: a rent review, a change of term, or a new end date.

Raises the next invoice against an existing common property rental — the monthly or quarterly charge under the agreement.

The banks configured in Urbanise and their branches with BSB numbers — reference data for resolving an account.

Pushes a batch of bank transactions into Urbanise for reconciliation. A bulk financial operation — normally part of a scheduled feed rather than something you ask for ad hoc.

The payment batches waiting to be sent to a given file service — the outbound payment runs that haven't gone yet.

The individual payments in one batch, each with its payee, amount and current status.

Marks a batch as being processed, so another run doesn't pick it up. Only used as part of an actual payment run being dispatched, and can't be undone through the assistant.

Stores the generated payment file against its batch, so Urbanise holds a record of exactly what was sent to the bank.

Records the outcome of one payment in a batch — processed, succeeded, or failed.

Marks a batch as fully processed. Urbanise won't offer it again, so it's only used once the file has genuinely been delivered to the bank.

Lists the bank response files Urbanise has received but not yet processed, registers a new one so it can be reconciled against the batch that was sent, and marks one processed once every item in it has had its outcome recorded.

Searches the Urbanise user accounts on your tenant by name or email, and opens one in full including the security groups it belongs to.

The security groups configured on your tenant. Group names are what get assigned to a user, so your assistant reads these before creating or changing an account.

Creates an Urbanise user account. This grants a person access to strata data, so it's only ever done on an explicit, verified request from someone entitled to authorise it — never inferred from an email or a document — and your assistant grants the narrowest set of groups that lets them do the job.

Updates an account, including its security group membership. Changing groups changes what the person can see and do, so it's confirmed with you first.

Permanently deletes an Urbanise user account. The person loses access immediately and the account can't be restored through the assistant.

Pushes e-services or happiness-centre case data into Urbanise's management reporting for a property group over a reporting period. These are scheduled loads rather than ad-hoc requests, and only run when explicitly asked for.