.svg)
A finance team with a reporting connection into NetSuite can answer most questions about the account as it stands today. That is what the connection is for. The mistake is to file it under backup, because a backup has to answer a different question: what did the record look like on a given day, and can the copy be trusted after the account is no longer there to check against?
What is a reporting connection built for?
SuiteAnalytics Connect is Oracle's query service for NetSuite; what it provides and how it is licensed are set out in Oracle's NetSuite documentation. Its job is analysis and reporting against the live account: a query returns the current state of the data, through an active subscription, to a tool that expects a database on the other end. It is the right tool for a dashboard, a reconciliation in progress or an ad hoc question.
Three things follow from that design. The result is only as current as the account, so it cannot show a record as it was before a mass update or a deletion. It depends on the subscription and the credentials being live, so it is not a copy the organisation holds independently. And a query returns rows; it does not carry the folder of attachments behind a transaction, or a verified statement that the set is complete.
What does a backup have to have that a query does not?
- A point in time. A copy taken on a schedule, so a record can be seen as it stood before the change that prompted the question.
- The relationships. Customers to contacts, invoices to customers and orders, bill payments to vendors, transactions to their GL impact, records to their sublists. A relational copy keeps them; a flat export loses the answer to any question that depends on how two records connect.
- The files. The File Cabinet documents attached to transactions, with the link back to each record.
- Independence. A copy the organisation holds and can query and export whatever happens to its access to the account.
- Evidence of completeness. Counts by record type, financial totals and referential integrity compared against the source, not a row count produced by the same search that produced the export. The export verification guide explains why the second is not proof.
When is a managed extraction the right choice?
When any of those five things is the requirement. For an account that stays live, Blueacrobat's continuous backup service captures what changed each day into a relational copy on DBVault, with the records indexed so that an authorised user can find a customer, an invoice or a custom record as it stood on a given day and export it. For an account that is being retired, AcroXtract runs a one-time extraction of the agreed scope, compares it with the source, and delivers it as a database you own, hosted read-only on the same platform. Both run with your own credentials, used read-only, and neither needs a reporting connection to be in place.
The two are not rivals. Keep the reporting connection for the questions it answers well. Decide separately whether the organisation holds a verified copy of its own records, and who could produce one on the day it is needed. If that copy does not exist yet, a review of the backup position is the place to start.
.svg)
