Detection
Failed calls are logged against the record involved, such as a payment attempt or a notice, so they can be found and reported.
Integrations
NetSuite Property Management Integrations
Connect the tools around your work
External services exchange data with RIOO: payment gateways, utility billing, CRM, messaging, e-signature, listings and cloud infrastructure. Core property and financial records stay in NetSuite.
IntegrationsRecords stay in NetSuite
- CaCardknoxPaymentsConnected
- TwTwilioSMSConnected
- DoDocuSignE-signatureConnected
- ZiZillowListingsSyncing
Connected natively
Native at the core, connected at the edges
RIOO's core property and financial records live in NetSuite. That doesn't mean nothing connects from outside. Payment processors, signature tools, messaging services and listing sites are specialists, and RIOO works with them. The difference is what they connect to: one system of record, not a property system that then syncs to an ERP.
In detail
What happens when an integration fails?
Every integration will fail occasionally. Good design decides in advance how failures are noticed and handled.
Retry
Transient errors, such as a provider timeout, can be retried without creating duplicates.
02
Alerting
Repeated failures notify an administrator rather than waiting for a tenant to complain.
03
Fallback
Teams know the manual route, for example a phone call instead of an SMS, until the service recovers.
04
Core unaffected
Leases, charges and balances remain correct in NetSuite throughout.
05
Who should NOT expect an integration to solve the problem?
An integration will not fix a process that is unclear or data that is poor. If two teams disagree about who owns a lead, or unit records are incomplete, connecting a CRM or listing site will spread the confusion faster. Agree ownership and clean the data first, then integrate.
Operators hoping to keep a standalone property management system and use RIOO only as a connector to NetSuite are also misreading the design. RIOO replaces the separate property system rather than syncing to it, so the integration strategy focuses on specialist services around NetSuite, not on bridging two ledgers.
What does "native at the core, connected at the edges" mean?
"Native at the core, connected at the edges" means RIOO keeps leases, tenants, charges, payments and the general ledger inside NetSuite, while specialist services such as payment gateways, messaging, e-signature and listing sites connect around that core. Integrations exchange results with RIOO records; they never become a second system of record for property finances.
The distinction matters when something goes wrong. If a messaging provider has an outage, notices queue or fail, but rent charges and balances are unaffected because they live in NetSuite. If a gateway changes its API, the payment connector needs attention, but the tenant ledger history is intact. Separating the core from the edges keeps the blast radius of any integration problem small.
How it works
How integrations work with RIOO
- 01
An external service performs its specialty
taking a card payment, sending an SMS, collecting a signature.
- 02
The result returns to RIOO
and attaches to the right record (tenant, lease, unit or work order).
- 03
Financial effects post in NetSuite
in the same ledger as everything else.
- 04
Your team works in one place
without logging into each tool for routine tasks.
How many integrations?
RIOO connects 30+ integrations overall, and the current integrations directory names specific providers across payments, utility billing, CRM and service, messaging, documents, listings and cloud infrastructure, as listed above. Logos indicate available connections, not commercial partnerships or certifications, so ask which connectors are live and supported in your region before relying on them.
Planning integrations during rollout
We map your existing tools during implementation: which stay, which are replaced by RIOO capability, and how each connection is configured and tested.
Compare
Which integrations does RIOO connect, and what flows each way?
RIOO connects 30+ integrations across payments, utility billing, CRM, messaging, documents, listings and cloud services, with the providers below named in the current directory. Each integration has a defined purpose and data direction, so administrators know what leaves NetSuite, what returns and which RIOO record it attaches to.
| Category | Named providers | Typical data flow |
|---|---|---|
| Payments | Cardknox, AsiaPay, Cybersource | Charges out, payment results back to tenant ledger |
| Utility billing | National Utility Billing System | Readings or bills in, charges to residents |
| CRM and service | Salesforce, HubSpot, Intercom, Slack | Leads in, status and alerts out |
| Messaging | Twilio, MessageBird, SendGrid | Notices out, delivery status back |
| Documents and e-signature | DocuSign, HelloSign, PandaDoc, Dropbox | Lease out for signing, executed copy back |
| Listings | Zillow, Trulia | Available units out, inquiries back |
| Cloud | AWS | Supporting services around the core |
How it works
How should integrations be phased during implementation?
Integrations should be phased by business risk: connect what is essential for go-live first, typically payments and e-signature, then add services that improve efficiency, such as messaging and listings, once core workflows are stable. Phasing keeps testing focused and avoids diagnosing several new connections at once during cut-over.
- 01
Inventory
List every tool in use today, who owns it and what it does.
- 02
Decide
Mark each tool as keep and connect, replace with RIOO capability, or retire.
- 03
Prioritise
Put go-live essentials such as payments and signatures in phase one.
- 04
Configure and test
Set credentials, map fields and test in sandbox with realistic data.
- 05
Go live
Switch on phase-one integrations with monitoring in place.
- 06
Extend
Add phase-two services after the first month-end close on RIOO.
Explore
Integration categories
Need something not listed?
Tell us what you use. We'll explain whether it's supported, planned or possible as a custom integration.
How it works
How do teams put integrations into practice?
Teams put integrations 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.
Whoever you evaluate, integration claims deserve the same scrutiny as architecture claims:
In each pattern, the external service does one job well, and the record of that job lives with your property and financial data in NetSuite.
- 01
Is it live and supported today
or planned?
- 02
What data flows
in which direction and how often?
- 03
Who maintains it
when the provider changes their API?
- 04
What happens when it fails
and how would we know?
- 05
Do we need our own account
with the provider, and who pays its fees?
- 06
Is it available in our region?
Explore by topic
Integration considerations by region
North America
US and Canadian operators typically need ACH and card payments, SMS for resident notices with TCPA-compliant consent, and listing syndication to major rental sites. Many of RIOO's named integrations were built with this market in mind.
United Kingdom and Europe
UK operators commonly collect rent by Direct Debit or bank transfer, need GDPR-compliant messaging and rely on regional portals for listings. Check gateway and portal coverage early.
Asia-Pacific and the Middle East
AsiaPay supports payment processing in Asia-Pacific markets. Operators in Australia, Singapore and the UAE should confirm local methods such as BPAY, PayNow, GIRO or cheque handling, and local messaging rules, during scoping.
Checklist
Integration readiness checklist
- Every integration has a business owner and a technical owner.
- Provider accounts, contracts and fees are in your organisation's name.
- Credentials are stored securely and rotated when staff change.
- Field mappings and data direction are documented.
- Test cases include failures, reversals and duplicates, not only success.
- Monitoring and alerting are agreed before go-live.
Talk to a specialist
See integrations on your own portfolio.
Core property and financial records stay in NetSuite.
Every page
All of Integrations, one page each.
CRM & serviceConnect Salesforce, HubSpot, Intercom and Slack with RIOO so marketing, sales and service teams share context with property and financial records.
MessagingSend rent reminders, maintenance updates, notices and community alerts by SMS and email through Twilio, MessageBird and SendGrid, logged to each profile.
Documents & e-signatureUse DocuSign, HelloSign, PandaDoc and Dropbox with RIOO for leases, renewals and closing documents, signed remotely and stored on the right record.
ListingsPublish available units to Zillow and Trulia from RIOO and bring inquiries back into one leasing pipeline, with availability and pricing kept in sync.
Cloud infrastructureHow RIOO uses AWS alongside Oracle NetSuite, and what that means for storage, scale and security. Core property and financial records stay in NetSuite.Does integrating a tool mean RIOO isn't native?
No. Native describes where core property and financial records live, which for RIOO is inside NetSuite. Integrations connect specialist services, such as payment gateways or e-signature, around that core and return their results to RIOO records. The ledger, leases and balances are never held in a separate property database that syncs to NetSuite.
Is NetSuite an integration?
No. NetSuite is RIOO's foundation, not a connected tool. RIOO's records, workflows and transactions run inside your NetSuite account, so there is no connector between a property system and the ERP to maintain. Integrations in RIOO's directory are the external services, such as payments, messaging and listings, that connect around that core.
Which payment gateways work by region?
The current directory lists Cardknox, AsiaPay and Cybersource. AsiaPay focuses on Asia-Pacific markets, while Cybersource offers global processing, and available payment methods vary by gateway and country. Operators in the US, UK, Australia, Singapore and the UAE should confirm local method coverage during scoping.
How are integrations scoped?
Third-party providers such as payment gateways, messaging services and e-signature tools have their own agreements with you. The integrations you need are scoped during discovery and described in your proposal, so you know which connections are configured at go-live and which can follow in a later phase.
Who maintains the integrations?
Responsibility is shared. RIOO maintains its connectors against provider and NetSuite changes, each provider runs its own service, and your administrator manages credentials, monitoring and user access. Agreeing this split in writing during implementation means everyone knows who acts when a connection fails.
Can RIOO connect to a tool that is not in the directory?
Possibly. Tell RIOO which tool you use and what it needs to exchange, and the team will explain whether it is supported, planned or feasible as a custom integration. Because RIOO runs on NetSuite, standard NetSuite integration methods may also apply, subject to your administrator's governance.
Do we need our own accounts with each provider?
In most cases, yes. Services such as payment gateways, messaging and e-signature are contracted by your organisation, so you control the relationship, fees and data with each provider. RIOO connects to those accounts using credentials your administrator manages. Confirm during scoping which providers require a direct contract in each market.
Related
Related to integrations
