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.

Rioo Management · Workflows & Customization

Property Management Workflow Automation

Workflows that match how your teams really work

Design approval chains and routing rules property by property. Route work to the right role, re-route it when someone's away, and keep a record of who did what and when.

Process is where portfolios lose control

The lease that waited a week for a signature. The invoice that sat with someone on vacation. The renewal nobody started because the person who usually starts it left. These aren't software failures. They're process failures that software made invisible. RIOO makes process explicit: every step has an owner, a rule and a record.

Role permissionsViewEditApproveAuditorManagerControllerOwnerSSO · 2FA · audit log

What is workflow customization in property management software?

Workflow customization in property management software means configuring how tasks and approvals move between people, based on your own rules: which role approves a lease, what cost limit sends a work order to a manager, who covers when an approver is away. In RIOO those rules act on NetSuite records, so every step is logged with the record it changed.

The aim is not to automate everything. It is to make the important decisions consistent, visible and fast. A portfolio with forty buildings and a dozen managers will otherwise develop forty slightly different ways of approving a concession or releasing a vendor payment, and nobody will notice until an auditor or an owner asks why.

RRent rollCCAMEEstoppelSStraight-line rent

How it works

How does workflows & customization work in RIOO?

Workflows & customization in RIOO runs inside Oracle NetSuite. The properties, units, leases, tenants and vendors it uses are native NetSuite records, so each step updates the same data finance reports on. There is no separate system to sync, and every action keeps an audit trail. The steps below show how the work flows.

1Capture2Validate3Approve4Post5Report
  1. 01

    Map the process

    During implementation, we document how leases, invoices, work orders and renewals move through your organization today.

  2. 02

    Configure the rules

    Steps, conditions, thresholds and approvers are set per property, community or transaction type.

  3. 03

    Assign roles and backups

    so nothing depends on one person being at their desk.

  4. 04

    Run and refine

    Watch where work queues up, then adjust thresholds or routing without starting over.

Compare

Workflow patterns by trigger, condition and action

Most property workflows can be described in three parts: a trigger such as a new record or status change, a condition such as an amount or property type, and an action such as routing for approval or sending a notice. Writing workflows this way makes them easier to configure, test and explain to auditors.

Lease eventNeeds sign-off?YesNoRoute to ownerDueAuto-processInstantUpdate records
TriggerConditionAction
Lease draftedRent below asking by more than a set percentageRoute to regional manager for approval
Work order createdEstimated cost above the site limitHold vendor dispatch until manager approves
Vendor bill enteredNo matching purchase orderSend to AP exceptions queue
Notice to vacate recordedAny residential unitCreate move-out inspection and turn tasks
Lease end approaching120 days before expiry on commercial leaseNotify asset manager and start renewal review
Payment returnedSecond return within six monthsSuspend autopay and notify property manager

How it works

How should a new workflow be introduced?

A new workflow should be introduced through a short, documented change process: describe the business rule, configure it in a sandbox, test it with real scenarios, get sign-off from the process owner, then release it with a note to affected users. That routine keeps workflow changes intentional and gives auditors a clear history of when rules changed.

NetSuite environmentsDevelopmentBuild and configureSandboxTest with real dataProductionLive operationsChanges promoted with sign-off
  1. 01

    Write the rule in plain language

    For example, concessions above one month's rent need regional approval.

  2. 02

    Name an owner

    One person is accountable for the rule and its thresholds.

  3. 03

    Configure in sandbox

    Build the steps, conditions and backups in a test account.

  4. 04

    Test with real cases

    Run typical, edge and exception scenarios, including an absent approver.

  5. 05

    Sign off

    The owner and finance confirm the result matches policy.

  6. 06

    Release and communicate

    Deploy to production and tell affected users what changes.

In detail

Who owns what in a governed workflow

Clear ownership keeps workflows from drifting as staff and portfolios change. These are the roles most organisations assign.

Who does whatYour teamRIOOPartnerProject kickoffACRData extractRCIConfigurationCRIUser testingRCIGo-live sign-offARCRResponsibleAAccountableCConsultedIInformed

Process owner

Decides the business rule and thresholds, for example the head of leasing for concession approvals.

NetSuite administrator

Configures, tests and deploys the workflow, and maintains its documentation.

Finance controller

Confirms financial controls such as segregation of duties are preserved.

Approvers and backups

Act on routed tasks, and keep their backup assignments current before leave.

Internal audit

Periodically reviews workflow history and changes as evidence of control.

In detail

What can RIOO do for workflows & customization?

RIOO handles workflows & customization with capabilities built on NetSuite records rather than a separate database. Each capability below works with the same properties, leases, tenants and ledger, so operations and finance see one version of the data. Capabilities are configured to your policies during implementation, without custom code for routine changes.

Configurable processes

at property or community level, so commercial and residential properties can run separate structures at the same time.

Role-based routing

sends each task to the role responsible, not to a named person who might leave.

Multi-step approval chains

follow your actual hierarchy, from site manager to regional lead to finance.

Automatic backups

Pending approvals move to a designated backup when the primary approver is unavailable.

Activity audit trail

Every workflow action records who acted, when and what changed.

Lease lifecycle workflows

for applications, approvals, renewals and terminations.

Update-safe configuration

Custom workflows are designed to carry through platform updates without rebuilds.

Keep it governed

Document each workflow, its owner and its purpose so changes stay intentional.

Keep it governed{tenant_name}{unit}Merge fieldsOn recordBranded PDF

Native to NetSuite

Because RIOO runs inside NetSuite, workflows act on the same records finance reports from. Your NetSuite administrators work with familiar concepts (roles, permissions and records) rather than a second system with its own logic.

Administrators & NetSuite teams

Bolt-onNative (RIOO)Property appown databaseERP / GLown databasesync jobs · CSVOracle NetSuiteProperty…Portals & mobileLeasingManagementOne database · one GL

Explore by topic

Approval designs by portfolio type

MultifamilyCommercialStudentHOAIndustrialMixed-use

Residential portfolios

Residential approvals are high-volume and low-value, so the goal is speed within policy. Renewals within guidelines can pass automatically, with exceptions such as larger concessions or waived fees routed to a manager. Mobile approval keeps site teams moving.

Commercial portfolios

Commercial approvals are fewer but carry more value and complexity. A lease deal sheet may need leasing, asset management, legal and finance sign-off, with thresholds based on rent, term, incentives and tenant credit. Each approver sees the deal terms and supporting documents in one place.

Facilities and maintenance

Maintenance approvals balance cost control with speed of response. Emergency work proceeds immediately with retrospective review, while planned work above set limits waits for approval before a vendor is dispatched. Approval limits typically differ by role and property.

Who is RIOO workflow customization NOT for?

RIOO workflow customization is not a general business process management platform for designing unrelated applications. It configures how property records, such as leases, work orders, bills and renewals, move through approval and routing inside NetSuite, rather than building new apps for HR, marketing or other departments.

It may also be more than a very small team needs. A landlord with one manager who approves everything personally gains little from multi-step routing. The value grows with the number of sites, roles and thresholds, and with the need to show auditors and owners that policy is applied consistently.

Strong fitNot a fitRuns NetSuiteVacation rentalsFinance-led teamsSingle small…Mixed portfoliosNo ERP plannedHonest fit check

What changes

What changes when workflows & customization runs on NetSuite?

When workflows & customization runs on NetSuite through RIOO, operational work and accounting stop being two separate jobs. Transactions post to the general ledger as they happen, reports use the same records as daily work, and controls come from NetSuite roles and approvals. The changes below are the ones teams usually notice first.

BeforeWith RIOOSystems to updateOne recordManual hand-offsRules and alertsReports built by handLive reports
  • Consistencyacross sites, managers and shifts.
  • Fewer stalled approvalsbecause backups pick up automatically.
  • Audit readinesswith a trail of every action.
  • Scale without headcount creepbecause routine routing happens without manual chasing.

Checklist

Workflow design checklist

Workflow design checklistConfirm data ownersClean tenant recordsMap chart of accountsAgree approval limitsSchedule training3/5complete
  • Every approval step has a named role, not a named individual.
  • Every approver role has a backup assigned for leave and absence.
  • Thresholds are written down and reviewed at least once a year.
  • Emergency paths exist for urgent maintenance and are reviewed afterwards.
  • No workflow lets one person both request and approve the same transaction.
  • Changes are tested in sandbox before each NetSuite release.

Talk to a specialist

See workflows & customization on your own portfolio.

Route work to the right role, re-route it when someone's away, and keep a record of who did what and when.

FAQ

Workflows & customization FAQs

Still curious? Ask the team.

Is there a limit to approval steps?

Workflows support multi-step approval chains designed around your hierarchy, such as site manager, regional lead and finance. In practice, most teams keep chains short, because every extra step adds delay. A useful rule is that each step should add a decision someone is accountable for, not just a signature.

What happens when an approver is on leave?

Role-based routing reassigns pending tasks to the designated backup, so a vendor bill or lease approval does not sit waiting while someone is away. Backups are set per role and property, and the workflow history records who actually approved each item, keeping the audit trail accurate even when the primary approver was absent.

Can commercial and residential properties use different approval chains?

Yes. Workflows are configurable at property or community level and can run side by side. A residential renewal within policy can pass straight through, while a commercial lease above a set value requires asset manager, legal and finance approval. Mixed portfolios use both, with each property following the rules that suit it.

Is every action logged?

Yes. Each workflow action records who acted, when and what changed, on the NetSuite record itself. That history covers approvals, rejections, reassignments and edits, and it can be reviewed by finance, internal audit or external auditors without exports. It also helps managers spot where work regularly queues up and adjust routing.

Will updates break our custom workflows?

Existing configurations are designed to be preserved through RIOO and NetSuite platform updates, so workflows should not need rebuilding after each release. NetSuite still ships two major releases a year, so we recommend testing critical property workflows, such as lease approval and vendor bill routing, in the release preview or sandbox each time.

Can site managers change workflows themselves?

Usually not. Workflow configuration is normally restricted to NetSuite administrators so that rules stay consistent and changes are tested and logged. Site managers can request changes through the process owner, and thresholds can often be adjusted by authorised roles without rebuilding the workflow, depending on how it was designed.

Do workflows slow down urgent maintenance?

They should not. Well-designed maintenance workflows include an emergency path, so urgent issues such as leaks, lockouts or no heating are dispatched immediately, with approval reviewed after the fact. Cost limits and approvals apply to planned and non-urgent work, where a short pause saves money without putting residents or buildings at risk.

Turn tribal knowledge into a process anyone can follow.