> For the complete documentation index, see [llms.txt](https://help.filed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.filed.com/reference/plugins/integrations/accounting-and-erp/netsuite.md). # NetSuite With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from NetSuite and, when **Write** access is enabled, perform approved actions in NetSuite. This integration to Filed is connected via our integration provider [Composio](https://composio.dev/) ## What you need * A NetSuite OAuth client ID, client secret, and account ID from your NetSuite administrator. * A NetSuite role that can access the records Filed should use. ## Connect NetSuite 1. Create the connection and enter the requested client ID, client secret, and account ID. An account ID may look like `1234567_SB1`. 2. Continue to NetSuite, sign in with the authorized user, and approve access. 3. Return to Filed and wait for the connection to verify. 4. Keep write access off until a test workflow succeeds. If authorization fails, verify the OAuth integration record, redirect URL, role permissions, and account ID with your NetSuite administrator. Never reuse another customer's OAuth credentials. ## Verify the connection After the connection becomes **Active**, open a known item that the authorized account should be able to access. Confirm OAuth application, account ID, and role permissions. For a new connection, test against a non-production or non-client-sensitive item before relying on it in a deadline-driven workflow. ## Manage permissions Read access is always enabled. Turn off **Write** in the connection settings to prevent Filed from creating or modifying NetSuite data while keeping the connection available for read-only workflows. Re-enable it only after the firm approves the change. ## Troubleshooting **The authorization screen will not complete.** Sign out of the wrong provider account, restart the connection, and use the firm-managed account that has OAuth application, account ID, and role permissions. **The connection is active but data is missing.** The provider only exposes content available to the authorized user. Review OAuth application, account ID, and role permissions, then reconnect if the account or environment was wrong. **The connection is pending or failed.** Open the connection in Filed, correct the provider-side issue, and select **Reconnect**. Do not create duplicate connections to work around a permissions problem. ## Using this integration with Filed Chat and Routines Use **Chat** for one-off questions and guided work on a client, such as finding NetSuite information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with NetSuite data on a schedule or in response to a trigger. Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them. ## Example prompts Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled. * “Summarize the NetSuite information for \[client name] for \[date range].” * “Find records in NetSuite that need review before \[deadline].” * “With write access enabled, prepare the approved NetSuite update and show the proposed changes first.” ## Capabilities ### Review financial records Use Filed to retrieve the accounting or ERP information available to the connected account. This is useful for reconciliation, tax preparation context, and review workflows. ### Prepare approved accounting changes When **Write** access is enabled, Filed can prepare or run approved updates supported by the provider. Use this only after validating the company, environment, and accounting policy involved. ### Keep production changes controlled Use a separate connection for production and sandbox environments where applicable. Turn off Write when the connection is used only for reporting or review. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.filed.com/reference/plugins/integrations/accounting-and-erp/netsuite.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.