What to check before you install a SuiteApp

At some point most accounting teams need something NetSuite doesn't do on its own, whether that's depreciation for a few thousand fixed assets, a growing lease portfolio, or bank reconciliations that eat away time every month. The SuiteApp Marketplace is where you go looking. SuiteApps go through a rigourous vetting process with NetSuite’s team to make sure you are getting a working, helpful app for use cases beyond what native NetSuite offers. The end result is that the app is Built for NetSuite, aka has the BFN Badge. But not all BFN apps are created equally.  

SuiteApps aren't all built the same way. Some run entirely inside your NetSuite account, using the records you already have. Others run on the vendor's servers and sync data into NetSuite on a schedule. Either kind can be the right pick, and the two create very different amounts of work at close.

Here you'll learn what a SuiteApp is, what the Built for NetSuite badge covers, and five questions to ask a vendor before you install, so you end up with an app that makes your financial processes easier instead of more complex.

What is a SuiteApp?

Oracle defines SuiteApps as "applications or bundles that extend NetSuite for specific industry and business needs." Some are built by Oracle NetSuite. Others come from members of the SuiteCloud Developer Network, Oracle’s third-party developer program.

You install them from the SuiteApp Marketplace inside NetSuite, or through Customization > SuiteBundler > Search & Install Bundles. Either way, the install looks about the same from your side. What changes is how much of the product ends up in your account.

What does the Built for NetSuite badge mean?

Oracle reviews the SuiteApp against its own standards for security, data privacy, and overall quality. The partner submits a completed questionnaire, provides positive customer references, and demonstrates the product to the NetSuite SDN team.

Oracle also spells out how far that review goes. The Built for NetSuite program sorts applications into three types:

• Native. The entire solution resides on the SuiteCloud platform, and every component gets reviewed.

• Integrated. The majority of the solution resides outside NetSuite. Oracle reviews only the integration components.

• Hybrid. A mix of both, where Oracle reviews the native components and the integration components.

Oracle says plainly what the badge doesn’t do: "While Built for NetSuite may increase confidence in the quality and security of thirdparty applications, the program does not provide any guarantee from NetSuite, and it is important that customers understand the implications of using third-party applications."

The badge covers Oracle's review of the product. It doesn't tell you where the product runs.

What's the difference between native, integrated, and hybrid SuiteApps?

The three labels describe where the software runs.

A native SuiteApp runs inside your NetSuite account. Developers build it on Oracle’s SuiteCloud platform using tools like the SuiteCloud Development Framework, and it deploys custom records, custom forms, and workflows straight into your account. It reads and writes the records you already have, using your subsidiaries, your chart of accounts, and your saved searches.

An integrated SuiteApp runs on the vendor's own infrastructure and connects to NetSuite through an API or a scheduled sync. Your data sits in two systems, so you'll need that sync to keep the two matching, plus someone to watch it.

A hybrid SuiteApp does some of each.

Any of the three can be the right pick for your team. You just need to know which one you're looking at, and the marketplace listing often won't say.

Five things to check before you install a SuiteApp

1. Where your data will sit

If the SuiteApp holds the detail and NetSuite gets a summary journal entry, your team ties the two together every month. A lease app tracking 400 leases and posting one monthly entry means 400 schedules reconciling back to one number. Ask the vendor to walk through that reconciliation with real numbers instead of demo data.

2. What your audit trail will show

NetSuite's system notes record what changed, when it changed, and which user made the change. A Context field shows how the change was made, and Oracle notes that external systems make updates through channels like web services.

A change pushed in by an integrated SuiteApp gets recorded under that integration's service account. NetSuite will tell your auditor the integration made the change. To find out which person approved it, your auditor goes to the vendor's system for their log. That's a frustrating week of fieldwork for everyone involved.

3. How user access gets managed

If the records sit in NetSuite, your administrator controls access the same way they control everything else. Every custom record type has a Permissions subtab where you set access by role and access level. Ask how the vendor's records ship, since a custom record type can also be opened to public access.

An integrated SuiteApp keeps its own user list and roles. When a controller leaves, your admin removes their NetSuite role, and someone still has to remove them from the vendor's app.

4. Who supports the connection

For an integrated SuiteApp, ask who owns the connection when it fails, how fast they respond, and whether that response time is in writing. Ask who answers your support tickets, too. All of it is easier to pin down before you install than during a bad close.

5. How the app handles NetSuite releases

NetSuite ships two major releases every year. Oracle’s Release Preview gives you a test account ahead of each one and recommends verifying that your existing customizations and workflows still work, noting that "changes in design or functionality may affect existing solutions, particularly customizations."

Say a release changes how a saved search behaves, and your depreciation schedule depends on that search. You want to find out during the preview window, not on the first close after the upgrade. Ask the vendor whether they test against Release Preview, and what they had to fix last time.

Why every extra system adds work to the period-end close

Add a system and you add work. Your team runs it every month, and your auditors test it every year.

Companies have been adding systems fast. In KPMG's SOX survey, the average number of in-scope systems reached 40 in FY24, up from 17 two years earlier, while automated controls dropped from 21% of the total to 17%. Material weakness filings point the same way: among companies that disclosed one in FY25, 58% reported issues involving IT, software, security, and access, up from 31% in 2021.

Ten minutes on a vendor call to understand what you're taking on is time well spent.

Myths and realities of choosing a SuiteApp

Myth #1: The Built for NetSuite badge means the app was built inside NetSuite

Reality: Oracle grants the badge to native, integrated, and hybrid applications. The badge confirms a review happened. Where the software runs is a separate question, and you have to ask it.

Myth #2: A frequent sync is the same as living in one system

Reality: Once you install a sync, it's one of your controls. It needs an owner, it can fail, it runs on a delay, and it goes in your SOX documentation. That can be a good trade. Just make sure you know you're making it.

Myth #3: Anything on the SuiteApp Marketplace is supported by Oracle

Reality: Oracle distributes and supports the SuiteApps it builds itself. A SuiteApp from an SDN partner is supported by that partner. Find out which one you're buying, and who picks up the phone.

When is an integrated SuiteApp the right choice?

If another system genuinely owns the data, pulling it into NetSuite creates a bigger problem than it solves. Payroll, procurement, CRM, tax engines, and industry-specific systems your finance team uses but doesn’t own all belong where they are. For that data, a well-built integration is the right call.

Some products outside the platform are also just better at what they do. If that gap matters to your team, take the product, and go in knowing you own the connection.

It's a tighter call with your subledgers and anything that posts to the GL: leases, fixed assets, reconciliations, and allocations. When that detail sits outside NetSuite, your team ties it back to the statement every month, and your auditor tests the tie at year end.

How Netgain builds SuiteApps

The six Netgain products that touch the close most directly are built on the SuiteCloud platform, so they run inside your NetSuite account and work with the records already there. Here’s how that plays out for each one.

NetLease automates lease accounting under ASC 842, IFRS 16, and GASB 87 and 96. It handles modifications, early terminations, multi-book, and foreign currency, and it generates your lease schedules, disclosures, and audit reports inside NetSuite, so there’s no separate lease system to tie back.

NetAsset manages fixed assets from creation through disposal. Assets get built up from the bills and journal entries already in your account, which pulls the details onto the asset record for you. It keeps separate depreciation schedules for financial and tax reporting, and it handles intercompany transfers with built-in elimination.

NetCash automates bank and credit card reconciliation. Depending on the rule you set, it creates journal entries, transfer journals, or deposit and check records, and all of them post natively to your GL. Match History keeps a record of what matched, how, and when, which answers the audit question from earlier inside NetSuite.

NetClose centralizes close tasks, reconciliations, prepaid amortizations, accruals, and flux analysis. Changes to NetClose records are stored in each record’s NetSuite System Notes, so the history sits exactly where your auditor already looks.

Shared Transactions allocates transaction lines across subsidiaries, segments, accounts, and entities. The allocation journal and the source transaction link to each other automatically, in both directions, which keeps allocations traceable without a spreadsheet on the side.

Cross-Validation Rules moves your accounting policies into NetSuite and enforces them when a transaction is saved. You can hard-block a violation or flag it for review. Because the rules run inside NetSuite, they apply to transactions arriving through CSV import and integrations, along with the ones your team keys in.

Choose your next SuiteApp with confidence

Before you install anything, send the vendor these five questions:

1. Does this SuiteApp store its records in my NetSuite account, or on your servers?

2. What will my team reconcile between the two systems each month?

3. When my auditor asks who changed a number, where do they look?

4. Who owns the connection when it fails, and what's the response commitment?

5. Do you test against Release Preview, and what did you fix last time?

A vendor who answers all five quickly and specifically is a good sign for the rest of the relationship.

If you’d like to see where the records actually sit, our interactive product tours walk through these products at your own pace. And when you’re ready to talk through your own lease portfolio, asset register, or close calendar, Netgain was founded by former Big Four accountants and is backed by a deep bench of CPAs who understand these processes and work directly with end users. Request a personalized demo and we’ll show you what it looks like in a NetSuite account.