No handoff gaps
Each step updates the shared record.
Solutions · By Workflow
Follow the work from start to ledger
Property work crosses departments. A lease touches leasing and finance. A repair touches residents, maintenance, vendors and AP. These five workflows show how RIOO carries work end to end on one system of record, without a hand-off by spreadsheet. Confirmworkflow names as approved framing
Workflows on one record
- Lease to ledgerBilling & revenue
- Request to expenseMaintenance cost
- Procure to payVendors
- Month-endConsolidation
Why think in workflows
Every department can be efficient while the business is still slow, because the delays live between departments. A workflow view shows where work waits, where data is retyped and where numbers drift. It's also the best way to test any vendor's claims. Ask them to trace one workflow live, from the first click to the journal entry.
What is a property management workflow?
A property management workflow is a sequence of steps, owned by different people, that turns a business event into a finished outcome, such as a lease becoming billed revenue or a repair request becoming a paid vendor bill. In RIOO each workflow runs on NetSuite records, so every step updates the same data and the general ledger reflects the outcome automatically.
Thinking in workflows rather than modules shows where handoffs fail and where time is lost.
The five workflows
Lease to ledger. A signed lease creates charges, invoices and GL entries, without re-keying.
Request to expense. A resident's repair request becomes a work order, a vendor bill and a correctly coded property expense.
Procure to pay. Purchase order, receipt, invoice, approval and payment in one auditable trail.
Month-end & consolidation. Property P&Ls and multi-entity roll-ups from records that were current all month.
Move-in to move-out. Readiness, inspections, deposits, deductions and final statements across the whole tenancy.
Lease to ledger →Request to expense →Procure to pay →Month-end & consolidation →Move-in to move-out →
Who owns each step
Each workflow passes between roles: leasing agents, community managers, technicians, AP clerks, controllers and asset managers. RIOO gives each role its own view while keeping the record shared.
How to use these pages
Each workflow page walks through the steps, the roles involved, the records created and the controls applied. Use them as an evaluation script. Ask any vendor to run the same steps in a demo, and watch where the data leaves the system.
Compare
Which workflows does RIOO cover?
RIOO documents five core workflows that together cover most of the money and work in a property business. Each one has its own page with the steps, owners and controls, and each runs end to end in NetSuite. Start with the workflow that causes your team the most manual work today.
| Workflow | Starts with | Ends with |
|---|---|---|
| Lease to ledger | A signed lease | Billed and recognised revenue |
| Move-in to move-out | An approved applicant | A settled deposit |
| Procure to pay | A purchase request | A paid vendor bill |
| Request to expense | A maintenance request | A coded property expense |
| Month-end close | Period transactions | Consolidated results |
How it works
How do you choose which workflow to fix first?
Choose the first workflow to fix by finding where manual work, errors and delays cost the most today. A short review with finance, operations and leasing usually points to one or two workflows, and fixing those first delivers visible results that build support for the rest of the rollout.
- 01
List handoffs
Where does work move between teams or systems?
- 02
Count manual steps
Rekeying, exports and spreadsheets in each workflow.
- 03
Measure delays
Days lost waiting at each handoff.
- 04
Check errors
Corrections, disputes and audit findings.
- 05
Pick the biggest gap
Start there and measure the change.
Compare
Who owns each workflow?
Each workflow has a business owner who is accountable for its results, even though several teams carry out the steps. Naming an owner makes it clear who agrees changes to approvals, notifications and controls, and who reviews the workflow measures after go-live.
| Workflow | Typical owner |
|---|---|
| Lease to ledger | Controller |
| Move-in to move-out | Head of operations |
| Procure to pay | Finance or procurement lead |
| Request to expense | Head of maintenance |
| Month-end close | CFO or controller |
How it works
What all five have in common
- 01
They start where the work starts
in leasing, a portal or the field.
- 02
They create the financial transaction at the source
inside NetSuite.
- 03
They route approvals
by role, with backups.
- 04
- 05
They end in the ledger
not in an export.
Explore by topic
How do teams put solutions by workflow into practice?
Teams put solutions by workflow into practice by configuring RIOO to their own policies, training each role on real scenarios and starting with one property or workflow before rolling out further. The examples below show how that typically looks, from set-up to day-to-day use, and which team owns each part of the work.
How to use these workflow pages
Each workflow page follows the same pattern: the trigger, the steps, who's involved, the records created in NetSuite and what you can report afterwards. They're written for evaluation teams. Use them to script your demo and ask us to show each step live with your own scenario.
Workflows you can configure
These five are the most common end-to-end processes, but they aren't the only ones. RIOO's workflow tools let you add approvals, notifications and tasks for your own processes, such as owner approvals over a spending limit, inspections before deposit refunds or legal review for non-standard lease terms.
Measuring workflow health
Measure each workflow by cycle time, exceptions and manual touches. If move-out deposit refunds take three weeks, the workflow shows where they wait.
In detail
Why do workflows work better on NetSuite?
Workflows work better on NetSuite because every step writes to the same database as the general ledger. In RIOO, when a step completes, the next owner sees it immediately and finance sees the accounting effect, without a sync or batch job. Approvals, permissions and audit trails also come from NetSuite, so controls are consistent across workflows.
Built-in controls
Approvals and limits apply in every workflow.
Audit trail
Every change is logged with user and time.
One set of reports
Operational and financial results match.
Who are the workflow pages NOT for?
The workflow pages are not detailed configuration manuals for NetSuite administrators, and they are not legal or accounting advice. They describe how RIOO runs each process for evaluation and planning. Administrators should use the NetSuite administrators page and implementation documentation for set-up detail.
Configured to your policies
These workflows describe how RIOO's documented capabilities connect. Approval thresholds, notice periods, allocation rules and checklists are configured to your policies during implementation, and we test them with your real scenarios before go-live.
Checklist
How do you measure workflow improvement?
Measure workflow improvement by comparing time, effort and errors before and after moving each workflow to RIOO. Agree the measures before go-live, record a baseline and review them after the first few months, so the gains are clear to owners and the board.
- Days to close the month
- Manual journals per month
- Time from lease signing to first invoice
- Time from request to closed work order
- Duplicate or misapplied payments per month
- Audit adjustments related to property data
Talk to a specialist
See solutions by workflow on your own portfolio.
These five workflows show how RIOO carries work end to end on one system of record, without a hand-off by spreadsheet.
Every page
All of Solutions by workflow, one page each.
Are these workflows prebuilt?
The workflows combine standard RIOO capabilities, such as leasing, billing, maintenance and payables, configured to your policies during implementation. You do not build them from scratch, but approval steps, limits, notifications and owners are set to match how your organisation works, so each workflow reflects your controls.
Can we change approval steps?
Yes. Workflows are configurable by property and transaction type, so approval steps, limits and routing can differ between, for example, routine repairs and capital projects, or between regions. Changes are made in configuration rather than code, and they apply to new transactions from the date they take effect.
Can we see a workflow in the demo?
Yes. We recommend tracing lease to ledger live in the demo: sign a lease, bill the first rent, take a payment and show the journal entry in NetSuite. Seeing a full workflow end to end shows how RIOO connects operations and accounting better than a tour of individual screens.
Do workflows work for commercial and residential?
Yes. The workflows work for both commercial and residential portfolios, with separate configurations where needed, such as recoveries and critical dates for commercial leases or deposits and inspections for residential tenancies. Mixed portfolios can run both configurations in the same NetSuite account.
Can workflows include our own approval rules?
Yes. Approval rules, limits and routing can be set for each workflow by property, amount, transaction type or role, using NetSuite workflow and approval features. Your policies define the steps, and RIOO applies them consistently across every property, so new sites follow the same controls from the day they go live.
Do the five workflows cover commercial properties?
Yes. The same five workflows apply to commercial properties, with steps that reflect commercial terms such as rent reviews, recoveries and critical dates. Lease to ledger, for example, includes straight-line revenue and CAM estimates for commercial leases, while residential leases follow a simpler billing path.
Can we run one workflow on RIOO before the others?
Yes. Many portfolios move one or two workflows first, such as lease to ledger and month-end close, then add maintenance and procurement in a later phase. The phasing is agreed during implementation planning, so each step delivers value on its own while the full set is rolled out over time.
Related
Related to solutions by workflow
