PRODUCT ENGINEERING / CONNECTED BUSINESS SYSTEMS
OMNISTUGLOBALStart a project

Industry / Real Estate and PropTech

Connect the listing, the lease and the ledger.

Property software needs to know what is available, who has agreed to occupy it and what each payment represents. Design those records together, from enquiry to reconciled owner statements.

Discuss your project โ†—
Contents ยท Real Estate and PropTech

Start with the portfolio and the money position.

A listing portal, a portfolio manager and a property transaction service can share an address without sharing a money model. Decide which business you are building, who holds funds and which jurisdictions and tenancy types apply. Search freshness, leasing operations and financial controls then have clear boundaries instead of drifting into an unreviewed custody or lending service.

From inventory to the first accounting cycle.

Inventory: properties, units and leases

Separate the physical asset, marketable unit and contractual relationship. Track building/unit structure, lease term and rent, signatories versus occupants, renewals, mid-term changes and off-market works without losing history. For commercial space, include subdivisions, area/service-charge allocation and review/break schedules where needed. An existing residential system may be extensible; inspect its model rather than assume a rebuild or that every residential schema fails.

Listing ingestion, syndication and freshness

Ingest authorised agent feeds and manual entries with provenance, update times, rights and media processing. Match duplicate units across descriptions, photographs and price variations while keeping uncertain matches reviewable. Agree confirmation windows, expiry/demotion/withdrawal and supplier corrections with a published policy. Test freshness and enquiry outcomes instead of asserting stale inventory always costs more than missing features or damages every other listing permanently.

Leads, viewings and applications

Route enquiries, measure pending response times and record follow-ups without treating any fixed response delay as a lost transaction. Coordinate viewing slots with actual keys/access, authorised host and access instructions. Stage identity and financial data collection according to a justified purpose, lawful basis and actual application stage, with access and retention limits. Do not collect every sensitive record at first enquiry or assume staged collection alone makes it lawful.

Screening, leases and decision controls

Scope published criteria, credit/reference provider checks, scoring, ranking, automatic accept/decline and human referral only after assessing the actual lawful purpose, housing/consumer-report rules and automated-decision requirements. Human review is not optional where rules or the actual risk require it. Version approved criteria, test accuracy/discriminatory effects, allow correction/challenge and record actual reasons, not a score alone. Model lease parties, terms, execution and amendments as structured versioned records alongside signed documents.

Trust accounting, rent and owner payouts

First determine the actual holder, legal structure, permitted accounts and relevant client-money/deposit protection arrangements. Keep owner positions, per-tenancy deposit liabilities, fees and authorised works distinct from operating revenue; a ledger label is not legal segregation. Reconcile bank/control records and beneficiary/transaction positions, linked to property/lease records, at the required cadence. Move fees and owner payouts only under actual entitlement, approval and provider/bank rules. Requirements differ by jurisdiction and money flow.

Maintenance, works and evidence

Track reporter, severity, responsible contractor, approval limit, authorised spend, any lawful cost allocation and completion evidence. Capture move-in/out condition, relevant photographs, work stages and approvals with appropriate privacy, integrity and retention. Track applicable inspection/certificate expiry and legal repair windows for the actual property/category. Evidence helps assess disputes but does not guarantee resolution, justify every deduction or make later reconstruction from other records impossible.

Migration, launch and the first accounting cycle

Inventory live leases, deposits, balances, ownership and source quality; reconcile opening positions and investigate differences before authorised cutover. Choose representative parallel runs, including a rent/accounting cycle where relevant, with acceptance, rollback and operator sign-off rather than claim one cycle is the only valid test. Rehearse collection, fees, works, payouts and statements through month-end. Agree support, fixes and updates in writing; no fixed included duration is evidenced here.

Eight property businesses with different boundaries.

Listing portals

Search, media, leads, feed provenance and current availability. A portal that genuinely handles no client funds has a different custody scope, but fees, reservation payments or added payment features can change that. No simplest/hardest ranking is established.

Property management software

Portfolio operations, structured leases, owner statements, maintenance and relevant client-money controls. Who holds money may be the manager rather than the software supplier; establish actual responsibilities instead of infer them from a product label.

Institutional rental operators

Portfolio-scale leasing, maintenance, occupancy and financial reporting with appropriate entity/property permissions and investor reporting definitions. Validate throughput and data quality against the real unit mix rather than promise a particular velocity.

Co-living and student housing

Rooms/bedspaces, shared facilities, tenancy parties, liability terms, academic/turnover cycles and condition records. Joint-and-several liability is a possible contractual arrangement to assess, not a universal feature of every room tenancy.

Commercial real estate

Multi-level/subdivided space, area basis, service-charge apportionment, rent reviews, indexation where needed, breaks and amendments. Choose extensions, specialist products or custom modelling after an actual fit review.

Brokerage and agent tools

Agent pipelines, instructions, commissions and splits, referrals and required transaction/compliance records. Verify authority and applicable rules for money, documents and disclosures rather than automatically reuse a tenant workflow.

Mortgage and lending technology

Application, underwriting, servicing, notices, payments and audit records with financial-services eligibility and permissions assessed separately. A property-software scope does not authorise credit decisions, lending or servicing.

Short and mid-term management

Owned/managed inventory, nightly or monthly availability, booking/lease distinctions, turnover, owner accounting and hospitality integrations. Check the actual stay classification, permits and consumer/tenancy rules rather than assume a duration label decides them.

A delivery process grounded in the live portfolio.

Scope the portfolio and money position

Document asset/unit/room mix, ownership, tenancy type, operating jurisdictions, actual custody of rent/deposits and source systems. Output the inventory model, funds flow, responsibilities and migration boundaries, not an assumed trust-account obligation for every portal.

Design the ledger and reconciliation

Define beneficiary/owner positions, tenant-deposit liabilities, fee entitlement, account mappings, approval roles and traceable entries before integration. Plan reconciliation exceptions as outputs operators can investigate; software records alone cannot create legally compliant accounts.

Build against portfolio-shaped data

Test renewals at changed rent, occupant changes, subdivisions, partial disputed deposit deductions, off-market works and ownership transfer mid-tenancy. Add duplicate payments, unknown outcomes, concurrent edits and permissions tests; validate actual financial state before retry.

Validate compliance, fairness and security

Review actual screening/data-use rules, approved criteria, challenge routes and client-money controls with relevant specialists. Scope tokenized card handling and assess actual PCI responsibilities instead of promise tokenization removes them. Agree security/VAPT evidence and acceptance tests; no pre-existing certificate or clearance is supplied.

Migrate and run comparative checks

Map identifiers, documents, leases and opening balances; reconcile deposits and beneficiary positions to reliable source/bank evidence. Resolve or explicitly escalate unexplained differences. Choose a representative parallel-run plan, including cycles and exceptions appropriate to the portfolio, with operator sign-off and rollback.

Cut over and support the first cycle

Verify collections, fees, works, owner payouts and statements against actual bank/provider and ledger outcomes. Define authorised operations, escalations and post-cutover monitoring. Support hours, maintenance and update commitments are agreed in the written scope, not fixed by this page.

Keep the records and controls connected.

Asset, unit and lease separated

Keep independent identifiers and history for physical assets, marketed spaces and contracts, including changes to occupants, ownership, availability and terms.

Client money and deposit liabilities identified

Where applicable, map actual designated accounts/custodians, per-beneficiary balances and conditional deposit liabilities separately from revenue, with approved movement rules and the required protection arrangements.

Three-way reconciliation with traceable exceptions

Compare bank statements, cash/control records and separate beneficiary/transaction records, linked to property and lease evidence. A matching total alone does not prove each position or explain an unexplained shortage/overage.

Screening with lawful decision controls

Scope scores, provider checks, automated decisions and referrals only within the assessed legal/privacy/fairness conditions. Use versioned criteria, meaningful review where required, correction/challenge routes, required notices and attributable outcomes.

Listing freshness under an explicit policy

Track source and confirmation times, detect duplicates and apply agreed expiry, demotion or withdrawal with supplier correction paths. Evaluate the policy rather than guarantee it wins trust or never loses valid inventory.

Evidence through condition changes

Link relevant move-in, maintenance and move-out records, photographs and approvals to the right lease/unit. Limit access/retention and make lawful deductions or dispute decisions reviewable rather than claim images decide every case.

Engineering work around your actual systems.

Commercial lease modelling

Represent subdivisions, area/service-charge apportionment, rent-review schedules, breaks and amendments with actual contract versions and approval rules. Compare existing specialist tools before assuming nothing off the shelf fits.

Trust accounting engines

Build beneficiary/owner positions, deposit liabilities, permitted fee movements and reconciliation around the actual jurisdiction, holder and bank/custodian arrangement. Keep unresolved exceptions visible; no engineering deliverable itself confers regulated authority.

Portfolio migration tooling

Map and validate live leases, ownership, balances, deposits and documents; preserve identifiers/audit evidence, compare outputs and provide repeatable dry-run, cutover and rollback tools. Migration complexity is investigated, not universally ranked hardest.

Valuation and market analytics

Evaluate price, rent and yield models against authorised relevant data, holdout evidence, assumptions and uncertainty. Explain drivers and limits for the intended decision; historical training or an explanation does not guarantee investment value or qualified valuation advice.

Mortgage and servicing workflows

Design application, underwriting support, servicing, notices, payments and audit trails only after actual lender/servicer role and regulatory permissions are resolved. Review automated credit decisions separately from tenant selection and operational workflows.

Building systems integration

Join authorised access-control, metering and smart-building records to the correct asset/unit/lease with permissions, privacy and event reconciliation. Separate read integration from any physical-access or control change, which needs specific authority and appropriate safety/security review.

Three possible property software scopes.

Management: a portfolio ledger and statements

Illustrative scope: explicit owner/beneficiary positions, per-tenancy deposit liabilities, bank/control/beneficiary reconciliation and traceable statements. Actual custody, account protections and qualified review must be agreed; this is not verified client or live platform evidence.

Portal: freshness and feed provenance

Illustrative scope: authorised feeds, media processing, duplicate detection, confirmation windows and agreed demotion/withdrawal rules with corrections. Test stale and contradictory updates rather than claim a particular portal outcome or client deployment.

Co-living: room-level leasing

Illustrative scope: room identifiers, parties, applicable joint/separate liability terms, shared-space records, turnover and academic-cycle scheduling. Use actual tenancy terms and legal review rather than universally impose joint liability. No named client result is asserted.

Decisions to settle before implementation.

A bank total is not a full beneficiary reconciliation

Check both the control/bank position and the separate liabilities/beneficiary records. A balance per property may be insufficient for the intended accounting questions, but no particular product is declared to fail an audit without evidence.

Freshness with supplier corrections

Set confirmation and expiry policy, ownership and escalation. Balance stale-data risk with inaccurate withdrawal and test the result rather than assume one policy is always worth more than any feature.

Screening needs more than consistent thresholds

Identically applied criteria and stored reasons do not by themselves establish fairness or legality. Assess relevance, accuracy, discriminatory effects, required accommodations/review, data-use authority and the actual notice/challenge routes.

Move the portfolio with evidence of its opening position

Inventory source discrepancies, rehearse representative cycles and exceptions, and sign off balances before cutover. These are planning subjects, not verified articles, client testimonials or a promised briefing pack.

Bring the details that shape the first proposal.

What you manage

Describe units, rooms and commercial spaces, tenancy/stay models, operating regions, owners and actual authorised users.

Money position

Identify who receives rent/deposits, the legal holder, accounts/custodians, protection schemes, fee rights and governing rules. A platform label does not settle them.

What you run today

Bring source systems, active leases, opening balances and deposit/beneficiary reconciliations, including unresolved differences and migration constraints.

Existing systems

List accounting, banking/payment, screening, feed/syndication and building/access interfaces, actual rights and receiving teams. Fit, readiness, quote and delivery plan follow evidence, not a guaranteed first-call price or universal willingness to build.

Identify whose money each movement represents.

Tenant

Identify the payer, tenancy and payment nature: rent, deposit, holding amount or another charge. One incoming transaction may need distinct allocations and rules.

Client account or actual custodian

Map the legally permitted holder and designated account/scheme for the actual funds. An internal segregated ledger is not a substitute for the required bank or protection arrangement.

Owner

Track the owner entitlement and any approved, lawful fee/works allocation, then reconcile actual payouts and statements. Do not net unapproved costs or assume every portal handles owner funds.

Deposits and fees have different conditions.

Tenant deposit liability

Track each tenancy liability and applicable release/deduction/protection process separately. Custodial schemes can hold the deposit rather than the manager; deposit return/dispute timing depends on the actual rules, not an automatic tenancy-end release.

Management fee to operating revenue

Record when the fee is actually earned and authorised to leave the applicable client position, with an attributable transaction. Scope refunds, reversals and reconciliation instead of informal netting.

Reconcile the detail as well as the total.

Bank statement

Match actual receipts, payments and outstanding items to the cash/control record and investigate unexplained entries.

Ledger/control and beneficiary positions

Reconcile the cash/control balance with separate beneficiary or transaction liabilities, not merely an aggregate property total.

Property and lease records

Link each balance, liability, fee and work allocation to valid tenancy/ownership records and supporting evidence. Resolve discrepancies before presenting a statement as reconciled.

Make exceptions and update ownership visible.

Money roles are model-specific

Property software may expose a funds flow without being the regulated holder. Determine actual client-money, deposit-protection and bank/provider obligations with qualified owners rather than assert every portal follows the same account model.

Check individual positions as well as totals

An aggregate bank match can conceal allocation or liability errors. Inspect beneficiary/deposit positions and unresolved exceptions; no claim about the most common defect in existing client systems is evidenced.

Stale data can undermine a viewing

An unavailable listing can waste time, but users may attribute responsibility differently. Record provenance, availability and update ownership rather than generalise every user reaction or rank damage against all other features.

Enforce an agreed freshness policy

Apply published confirmation/expiry rules with supplier notice, correction and accountable overrides. Do not assume the same window or automatic demotion is lawful, contractually permitted or suitable for all feeds.

Review the actual accounting and listing risks

Use the portfolio, money flow, reconciliation evidence and supplier feeds to identify gaps before rollout. A planning review is not an audit finding, compliance certificate or guaranteed audit prevention.

Screening needs accountable decisions, not only scores.

Apply

Collect justified information at the relevant stage with transparency, lawful purpose and access/retention controls. Staging alone does not establish consent, necessity or a right to obtain a report.

Check

Validate authorised provider data, identity matching, accuracy and relevant approved criteria. Investigate missing/incorrect records and discriminatory effects; consistent application alone does not make a criterion fair.

Decide

Scores, ranking, flags, automatic accept/decline and referral require an actual legal/risk assessment. Set meaningful human involvement and challenge safeguards where required, not merely where an operator prefers; control changes to criteria and automation.

Record

Keep the actual input/criteria/model version, decision maker, reasons, notices and review/correction outcome with justified retention. A reason is useful but is not proof of fairness, and an audit log cannot answer every future regulatory question.

Decide why each control is needed.

Staged capture

Limit sensitive collection to what is justified for the current step and legal basis; some early information can have a valid purpose, so do not state all early capture has no benefit.

Published criteria

Use approved relevant criteria transparently with necessary lawful accommodations and fair review. Identical treatment is not a substitute for analysing discriminatory effects or individual errors.

Automated outcomes and referral

Separate decision support from solely automated significant decisions, assess law and special-category data restrictions, and provide the safeguards actually required. Do not promise unrestricted straight-through approval/decline configurable by a lettings team.

Reasons, notice and correction

Give the applicable notices and correction/challenge routes. US consumer-report adverse action can include denial, a larger deposit or higher rent; follow the actual FCRA process rather than apply employment notice rules by default.

Assess the actual decision and safeguards.

Define the purpose before the automation

Screening can reduce some repetitive work but throughput gains are not established here. Assess actual source data, role, law, accuracy and effects before using scores to rank, approve or decline applicants.

Safeguards are not just a preferred referral setting

Use meaningful human involvement where required, challenge/correction paths, relevant notices and accountable criteria changes. Current law and special-category-data rules must be reviewed for the actual deployment; this page is neither a blanket ban nor a legal clearance for fully automated housing decisions.

Keep records that can support an actual explanation

Record relevant input/criteria/model versions, decisions and reasons, but do not promise logging costs nothing or answers every applicant, landlord or regulator question. Assess retention/access and investigate disputes rather than equate an explanation with fairness.

Compare the actual listing and management requirements.

The original separates listing/search/lead systems from management/lease/accounting systems. That distinction is useful to scope, but neither label proves who holds funds. Five shipped-platform and six reusable/two custom claims are not verified availability. Inspect existing tools, code, rights and responsibilities before choosing reuse, adaptation or custom work. No source ownership, client/reference access, VAPT, launch/support duration or deployment is established here.

Zillow

Historical catalogue reference only, not an inspected Omnistu product, client project, affiliation, available platform or owned live demo. Use the name to locate listing or management requirements in the original scope; verify actual code/assets/licences and fit before proposing reuse.

Trulia

Historical catalogue reference only, not an inspected Omnistu product, client project, affiliation, available platform or owned live demo. Use the name to locate listing or management requirements in the original scope; verify actual code/assets/licences and fit before proposing reuse.

Appfolio

Historical catalogue reference only, not an inspected Omnistu product, client project, affiliation, available platform or owned live demo. Use the name to locate listing or management requirements in the original scope; verify actual code/assets/licences and fit before proposing reuse.

Buildium

Historical catalogue reference only, not an inspected Omnistu product, client project, affiliation, available platform or owned live demo. Use the name to locate listing or management requirements in the original scope; verify actual code/assets/licences and fit before proposing reuse.

Greystar

Historical catalogue reference only, not an inspected Omnistu product, client project, affiliation, available platform or owned live demo. Use the name to locate listing or management requirements in the original scope; verify actual code/assets/licences and fit before proposing reuse.

Trace the balance back to the tenancy.

Check the deposit position behind the bank total

An illustrative planning risk is a bank-balanced system with unexplained tenancy allocations. Investigate the actual control and beneficiary/deposit records before relying on the total. This is not a verified client quotation, existing-system audit finding or testimonial collection.

Questions about Real Estate and PropTech.

Can we really launch in six working days?

Agree a delivery plan after inspecting code/components, integrations, data migration and acceptance requirements. A representative parallel run may include a rent cycle, but no fixed ready-made launch duration or universal test length is established.

Do we own the source code?

Put source/asset rights, licences, deployment access, runtime dependencies and per-unit/tenancy or other fees in writing. This page does not establish full ownership, no licence fees or a verified ready-made product.

Do we need trust accounting?

First determine the actual holder, funds flow, tenancy type and jurisdictions. A manager handling rent/deposits may have client-money, deposit-protection and accounting duties different from a no-funds portal. Obtain appropriate local advice; software does not create authority.

Our current system balances. Is that enough?

Not by itself. Reconcile bank/control records and separate beneficiary/transaction positions, with lease/property evidence and unresolved items. A bank total alone need not show whether an individual deposit liability is correctly allocated.

Will you build automated tenant screening?

The engineering scope can cover checks, scores, ranking, flags, automatic accept/decline and referral only within the actual legal, privacy and fairness assessment. Define human involvement where required, notices, corrections/challenges and approved criteria changes. Logging a threshold is not proof a decision is lawful.

Can we manage residential and commercial together?

Yes as a scoped model if it supports both. Inspect subdivisions, service charges, rent reviews, breaks and contract versions rather than assume every residential system is incapable or that extension never works.

How is migration handled?

Map source records and opening positions, investigate differences, rehearse representative cycles and exceptions, and obtain operator sign-off for cutover/rollback. Do not carry unexplained balances into a claim that the new system is reconciled.

How do you keep listings current?

Use authorised feed updates, provenance, confirmation windows and an agreed expiry/demotion/withdrawal policy with corrections and overrides. Test stale and contradictory listings; no automatic policy guarantees trust or conversion.

Can owners see their own statements?

Owner access can be scoped with permissions and statements traceable to rents, fees, works, liabilities and actual payouts. Reconcile outcomes and keep unresolved items visible instead of presenting an unexplained net total.

What about maintenance approvals?

Set approval limits by role, amount and actual owner instructions, with lawful cost allocations, relevant evidence and escalation. A photo or approval record does not itself justify a tenant charge or deposit deduction.

What does support look like after launch?

Agree response hours, operator training, month-end/payout escalation, maintenance, fixes and updates in the written scope. No fixed included support window is evidenced here.

What if we are not ready to build yet?

Clarify the money position, source quality and unresolved balances first. A review may recommend reconciliation, narrower scope or existing tools before custom development; software migration does not automatically repair an accounting discrepancy.

Implementation and platform references.

Use documentation for the selected versions, devices, configuration and operating region. Project acceptance depends on the implementation, not a tool label.

Bring your workflows and operating requirements.

Share the users, business rules, current code and data, integrations, device/browser targets and receiving team. Agree the build boundaries, rights, acceptance evidence and operating responsibilities before implementation.

Discuss your project โ†—