At a glance
Before you start
You need:- An owner or admin role in Hebno.
- Your NetSuite account ID, for example
1234567or1234567_SB1for a sandbox. - An integration record in NetSuite with OAuth 2.0 enabled, created by a NetSuite administrator under Setup → Integration → Manage Integrations → New. Note the client ID and secret or certificate it issues.
- A role for the integration with the permissions Log in using OAuth 2.0 Access Tokens and REST Web Services, plus view access to the records Hebno should read (customers, projects, transactions, saved searches).
Permissions
The token includes the role of the signing-in user, so NetSuite enforces that role’s permissions on every call.
Connect NetSuite
1
Allow the integration
Open Admin → Connectors → Catalogue, find Oracle NetSuite under ERP, and set it to Allow.
2
Connect the organisation
Select Connect, enter your account ID and the integration record’s client credentials, then select Test connection. Hebno checks that it can connect to NetSuite and lists the record types the role can read and write.
3
Choose teams and data areas
Under Who can use it, choose All teams or pick teams. Under Data areas, choose what members can see. See Data areas.
4
Set access
Access is Read only by default. Choose Read and write to let members propose time entries and draft invoices.
Link your own account
Members can link their own NetSuite sign-in so writes are made in their name under their own NetSuite role.- In Hebno, open Settings → Connections, find Oracle NetSuite and select Link your account.
- Sign in to NetSuite when prompted and approve the request.
Data areas
Data areas control what members of the allowed teams can see through the organisation connection. They apply on top of what the integration role can read in NetSuite.
An organisation connection with team access and data areas. Financial figures default to owners and admins.
When a member has linked their own account, Hebno uses that member’s NetSuite role instead of the organisation connection. Data areas still apply, so a member never sees more through Hebno than both NetSuite and your Hebno settings allow.
What Hebno reads
Hebno runs SuiteQL against the transaction tables for questions that span records, such as revenue by customer or cost by project. Results are returned in pages, and Hebno states when a reply includes only part of a large result. Reads are live. Hebno queries NetSuite when a request needs it. Only what a reply used is stored with the conversation as its sources.
What Hebno writes
Every write appears first as a confirmation card. You can change any field before you select Confirm.
An Oracle NetSuite change pending confirmation. Nothing is written until you confirm.
Link a project to NetSuite records
Linking marks which NetSuite records belong to a project, so you can ask “what is unbilled?” without naming the customer or job.- Open the project and select Brain.
- Under Linked records, select Link record, then Oracle NetSuite.
- Search by customer name or project name, and select the record. Link the customer and each NetSuite project in the engagement.
Use NetSuite in chat
-
Attach: open the + menu, choose Sources → Oracle NetSuite, and pick a customer, a project, an invoice or a saved search. Or type
/and choose Oracle NetSuite. -
Ask: name the customer, project or period in your request. For example:
Which Contoso invoices are more than 30 days overdue, and what is the total?
Summarise billed versus budgeted fees on the Contoso data audit project.
Draft an invoice for Contoso covering the unbilled time on the data audit from October.
- Research runs show a Checking Oracle NetSuite step, with a chip for each record or query result it read.
- Agents can read NetSuite on a schedule, for example a Monday list of overdue invoices by account manager. Writes an agent proposes appear in agent approvals for review.