OPERA is Oracle Hospitality's property management system. It runs reservations, rates, check in, guest folios and the night audit at each hotel. 

NetSuite is a cloud ERP that runs the finance side across a group: the general ledger, payables, entities, budgets and consolidated reporting. Most hotel groups that use OPERA PMS and NetSuite together keep OPERA at the property and post a daily journal from it into NetSuite.

Just over half of Australia's hotel rooms are chain affiliated, and about three quarters of those chain rooms run under management agreements, according to Horwath HTL's Australia Hotel & Chains Report 2026. In practice, that means the business operating a hotel and the business owning it are often different, and each needs its own view of the same property's numbers.

OPERA is built to run the property. It isn't built to run the finances of a group with several hotels, trusts and operating companies, and that's where NetSuite for hotel groups comes in. This guide is part of our series on hospitality management systems, and explains what each system does, where one hands over to the other and when running both makes sense.

What OPERA PMS Handles Well

OPERA is the operational record for each hotel, and it should stay that way. Front desk teams, reservations and revenue managers work in it all day, and it's designed around how a property actually runs.

It manages reservations, rates and group blocks, runs the front desk and housekeeping, and holds every guest profile and folio. It also keeps the guest ledger and city ledger, including direct bill accounts for companies and travel agents.

Each night, OPERA's end of day close balances the day's transactions and produces the trial balance and manager's report. That's where it hands over to finance. Oracle's own documentation describes OPERA Cloud's back office exports as a way to send financial totals and statistics to a general ledger as a journal entry. In other words, OPERA feeds a ledger. It isn't designed to be one.

Where Hotel Groups Need More Than OPERA PMS

The gaps show up above the property, in entities, costs and group reporting. A single hotel can manage with OPERA and basic accounting software, but a group quickly needs a system built for finance.

Hotel groups typically need an ERP for:

• Entity books and consolidation. Each trust, property company and operating company needs its own ledger, plus eliminations when the group reports as one. Our guide to hospitality group consolidation covers this in detail.
• Payables and procurement. Supplier invoices, purchase approvals and payment runs sit outside the PMS.
• Fixed assets and capex. Refurbishments, furniture and equipment, and depreciation by property.
• Budgets and forecasts by property and department, compared against actuals.
• Owner and operator reporting. The same hotel's results, reported in different formats to different parties.
• Venues that don't run OPERA. Pubs, restaurants, gaming and properties on other PMS platforms still need to land in the same ledger.

For a closer look at the finance requirements themselves, see our guide to hotel accounting software.

How OPERA and NetSuite Divide the Work

The simplest rule is to decide which system owns each record, then avoid keeping it in both. Duplicated records are where reconciliation problems start. In most groups, OPERA owns guests, reservations, rates, folios and the night audit, while NetSuite owns the general ledger, payables, entities, fixed assets, budgets, and group and owner reporting.

The one area to settle early is the city ledger. Some groups keep direct bill accounts and collections in OPERA and post only the balances to NetSuite. Others move invoicing and collections into NetSuite so the finance team manages every receivable in one place. Either works, but choosing halfway leaves two versions of who owes what.

Most groups reach this point after years of making the PMS and spreadsheets do more than they were designed for. As Tiernan O'Connor puts it:

"Businesses evolve and change over years, and they just end up in a position where it just becomes untenable. Or a new CFO comes in and thinks, this can be done in a better way." - Tiernan O'Connor, Director of Customer Success

Connecting OPERA PMS and NetSuite

OPERA offers two main routes for getting data into NetSuite, and the right one depends on your OPERA version and how much detail you need in the ledger. The most common starting point is the back office export: at end of day, OPERA produces journal files mapped to your chart of accounts, which are then imported into NetSuite.

For a direct, automated connection, the Oracle Hospitality Integration Platform (OHIP) gives OPERA Cloud a set of REST APIs and business events. Third-party connectors built on these routes are also available. Whichever you choose, the mapping of OPERA transaction codes to NetSuite accounts, departments and properties matters more than the technology. Our guide to hotel PMS integration covers what should flow and how to avoid common problems, and a NetSuite integration partner can design the connection around your structure.

When Running Both Makes Sense (and When It Doesn't)

The case for adding NetSuite grows with the number of entities and properties, not the number of rooms. A large single hotel can be simpler to account for than three small ones held in separate trusts.

Running OPERA and NetSuite together usually makes sense once you have several properties or legal entities to consolidate, separate owner and operator reporting, or venues outside OPERA. The clearest sign is a month end that depends on spreadsheets to bring it all together.

It may not be worth it yet if you run a single hotel with one entity and straightforward books. In that case, OPERA plus basic accounting software can be enough until the group grows.

Getting OPERA and NetSuite Working Together

OPERA PMS and NetSuite do different jobs, and hotel groups get the most from both when each sticks to its own. Keep OPERA at the property for guests, rates, folios and the night audit, and run entities, payables, capex, budgets and owner reporting in NetSuite. Before you connect them, decide where the city ledger lives and how OPERA's daily journal maps to your accounts.

If your group runs OPERA and your month end still depends on spreadsheets, see how NetSuite for hotel groups brings every property and entity into one ledger, or speak with a NetSuite specialist at DWR.

Platform capabilities evolve through regular updates. Feature comparisons reflect current understanding as of 09/10/2026. Verify specific functionality with vendors before making purchasing decisions.