Skip to main content
The Oracle NetSuite integration turns NetSuite sales orders into Pike projects, syncs customers, items, posted invoices, credit memos, payments, and vendor bills, and sends invoices created in Pike to NetSuite. NetSuite stays your ledger; Pike runs delivery.

​
Connect NetSuite

  1. Go to Workspace settings → Integrations → NetSuite.
  2. Click Add integration.
  3. Authorize Pike with OAuth 2.0 for your NetSuite account in the popup.
  4. Choose a subsidiary. OneWorld accounts can connect several subsidiaries, each mapped to Pike.
Only workspace admins can connect or disconnect NetSuite.

​
Import data

On the integration page, click Import data. The stepper runs entities in dependency order, so customers import before the projects and invoices that reference them. It skips entities whose Read toggle is off, names them, and links to sync settings.

​
What syncs

​
Subsidiaries and dimensions

Invoices created in Pike become NetSuite invoices on the mapped customer and subsidiary. Map NetSuite departments or classes to Pike teams, so revenue and cost report by team in both systems.

​
Source of truth

Once a record is linked, NetSuite owns the linked fields and Pike reads them back. Pike-only fields, such as project links, internal notes, allocations, and cost profiles, stay in Pike and are never overwritten. NetSuite owns customer master data, items, and posted documents.

​
Schedule

Pike syncs with NetSuite every 24 hours by default. Change the schedule in the integration settings. Payments update in real time. Import data and Refresh always run on demand.

​
Sync settings

While NetSuite is connected, the What syncs with NetSuite card sits under the top button row on the integration page. Each entity has a Read toggle (NetSuite to Pike) and, where supported, a Send toggle (Pike to NetSuite) and a Send when option. Toggles save immediately. Admins and finance users can change these settings. New connections start with Read on for everything and Send on for invoices only.

​
Send when

Send when applies to customers only and needs Send on.
  • When you send it: you send each customer yourself.
  • With its first invoice: sending an invoice for an unlinked customer creates the customer in NetSuite first.

​
Invoices and payments

Invoices reach NetSuite only when someone sends them. Emailing an invoice from Pike does not send it to NetSuite. After an invoice is sent, make changes in NetSuite. Payments update Pike in real time.

​
Synced records

Every synced record shows the NetSuite marker, “Last synced ” or “Not synced yet”, and a Refresh action. Refresh shows only while Read is on for that entity.

​
Sync issues

Records that fail to sync appear in the Sync issues list on the integration page, with the record, the reason, and a Retry action. The integration never deletes Pike data on its own. A record removed in NetSuite is marked “Removed in NetSuite” in Pike, never deleted.

​
Disconnect

Disconnecting NetSuite stops syncing and keeps all imported data. Linked records keep their history.

​
Permissions

Synced data respects Pike roles and private projects. A private project’s tasks never sync out to anyone who cannot see the project in Pike.

​
Limits

  • Pike does not post to the general ledger. NetSuite stays the system for posting.
  • Update customer master data and items in NetSuite, not Pike.
  • After an invoice is sent to NetSuite, make changes in NetSuite.