Property management, built natively on Oracle NetSuite

Request a demo

Platform

Six connected areas on one NetSuite system of record.

Solutions

Start from the places you manage, the business you run, your role or the workflow you want to fix.

NetSuite

Property management built natively on NetSuite, not synced to it.

Integrations

External tools exchange data with RIOO. Core property and financial records stay in NetSuite.

Markets

Localised pages for the five markets RIOO serves, with the rules that change how property is run.

Resources

Answers for choosing, implementing and running property management on NetSuite.

Company

The team behind the NetSuite-native property platform.

Property Management

NetSuite Customization for Real Estate: What to Build

How to customize NetSuite for real estate: a five rung ladder from settings to scripts, a CPI escalation example and a register that keeps upgrades safe.

LinkedIn X
Illustration of a smiling man in a coral shirt holding a clipboard beside a coral house standing on a map, with keys, coins, a document and a location pin around it

NetSuite customization for real estate means shaping the account to how property works. That covers custom records for properties, units and leases, fields for lease terms, and workflows for approvals and reminders. Scripts come in only where the logic needs code. The rule that keeps it safe is to use the lightest tool that does the job. Configure first, then add a field, then a workflow, and write a script last.

The usual failure looks like this. Every request becomes a script. Two years later nobody can say what half of them do, and each release week feels like a gamble. The ladder below keeps an account away from that.

The customization ladder

Each rung adds power and adds upkeep. Climb only as far as the requirement needs.

RungWhat it isReal estate exampleUpkeep
1. ConfigurationSettings, classes, locations, departments, subsidiariesA location for each buildingLow
2. Custom fieldsExtra data on standard recordsLease end date on a customer recordLow
3. Custom recordsNew record types with their own fieldsProperty, unit and lease records linked togetherMedium
4. Workflows (SuiteFlow)Point and click logic for approvals and alertsApproval of a lease discount over 5%Medium
5. Scripts (SuiteScript)Code for logic a workflow cannot expressA CPI escalation with a floor and a capHigh

What real estate teams usually customize

Records for the property hierarchy

Standard NetSuite has customers, vendors and items, but no building or unit. Real estate accounts add custom records for property, building, floor, unit and lease, linked to each other. That hierarchy is what lets a rent roll, a vacancy report and a work order all point at the same unit.

Fields for lease terms

Lease start and end, notice dates, renewal options, escalation type and deposit held. Keep the list short and named clearly. A field called "Date 2" will confuse the next administrator.

Saved searches and dashboards

Saved searches turn records into lists: leases ending in 90 days, units vacant over 30 days, tenants with balances over 60 days. Put the important ones on role dashboards so each person sees their own queue. Our guide to NetSuite real estate dashboards covers the KPIs worth showing.

Forms

Custom forms hide fields a role does not need. A leasing agent sees lease terms. An accountant sees the posting accounts. Fewer fields means fewer mistakes.

One escalation rule, built three ways

A made up office portfolio has 60 leases. Twenty use CPI escalations with a 2% floor and a 5% cap, applied on each lease anniversary.

  • Manual. An accountant checks a spreadsheet each month and edits the billing. About 2 hours a month, and one missed anniversary costs a year of underbilling.
  • Workflow. A workflow sends a reminder 30 days before each anniversary, and a person enters the new rent. The reminder is reliable. The maths is still manual.
  • Script. A scheduled script reads the CPI value, applies the floor and cap, and updates the billing schedule for review. This is a fair use of code, because the logic has rules a workflow cannot hold.

Take a lease at $10,000 a month. If CPI comes in at 6.1%, the cap applies and the new rent is $10,500. If CPI is 1.2%, the floor applies and rent goes to $10,200. Test both edge cases in a sandbox before the script goes live. Our post on rent escalation clauses covers the clause side.

Keep a customization register

This is the habit that keeps an account upgradeable. Every custom record, field, workflow and script gets one line in a register.

  • Name and internal ID.
  • Owner: the person who asked for it and can say if it is still needed.
  • Purpose in one sentence.
  • What it touches: records, roles and any integration.
  • Last tested, and on which release.

NetSuite ships major releases twice a year. Before each one, test every script and workflow on the register in a release preview account. Retire anything whose owner says it is no longer used. A register of 40 lines can be tested in two days. An account with 40 unknown scripts cannot.

When not to customize

Do not customize to copy a spreadsheet layout someone is used to. Do not build a feature a standard setting already covers. And do not build a full property management layer from scratch if a native one already exists for your account. Starting from a built product saves the design work and the upkeep.

Where RIOO fits

RIOO is built natively on NetSuite, so the property, unit and lease records already exist inside your account. Teams then adjust fields, forms and approvals with standard NetSuite tools, and keep their own customizations on the same register. The workflow customization page shows what can be changed without code.

Questions administrators ask

Will customization break when NetSuite updates?

Scripts are the part to watch, especially ones written against older APIs. Configuration and fields are less likely to be affected. Test them in the release preview before each major release.

Should we use SuiteFlow or SuiteScript?

Use SuiteFlow when the logic is a set of conditions and actions. Use SuiteScript when you need calculations, loops over many records, or integrations.

How many custom fields is too many?

There is no fixed number. The warning sign is fields nobody fills in. Review usage once a year and hide or retire the empty ones.

Who should own customizations?

One NetSuite administrator owns the register. Each item also has a business owner who can confirm it is still needed.