Skip to content
Connection Guide

Connect Oracle NetSuite ERP Without Breaking the Audit Trail

Use this guide to connect Oracle NetSuite ERP or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeDirect connection
CategoryFinance
Checklist4 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect Oracle NetSuite ERP and make sure the first collection lands cleanly.

  1. 1
    Enable REST Web Services and SuiteAnalytics Workbook, then create a dedicated custom role for runtime collection.
  2. 2
    Store account_id, client_id, certificate_id, and private_key_pem securely; optionally set base_url if the account-specific SuiteTalk domain is already known.
  3. 3
    Provide shared System Notes dataset IDs only when audit-event collection is needed in the target tenant.
  4. 4
    Validate employee REST, SuiteQL role queries, and any dataset execution before enabling scheduled sync.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

client_idprivate_key_pem

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.