/ /

How to Reconnect Your NetSuite Integration

Updated 21 days ago

A guide to why your NetSuite integration may show an "Invalid configuration" status, and the steps to reconnect it safely.

Why Did My NetSuite Integration Disconnect?

If your NetSuite integration shows an "Invalid configuration" status, this is almost always a role or credential issue on the NetSuite side, not a block from Kintsugi. This error appears when NetSuite's Token-Based Authentication (TBA) credentials fail to validate.

The most common causes are:

  • Missing role permissions. The connected NetSuite role doesn't have everything it needs enabled, most often Accessible Subsidiaries, SOAP/REST Web Services, or Log in using Access Tokens.

  • Credentials pulled from different Integration records. Your Consumer Key/Secret and Access Token ID/Secret all need to come from the same NetSuite Integration record. Mixing credentials from two different Integration records will cause validation to fail even if each piece looks correct on its own.

  • Incorrect sandbox Account ID formatting. Sandbox accounts need an underscore (e.g., 884606_SB1), not a hyphen (884606-SB1).

  • A temporary issue on NetSuite's side. If you notice several NetSuite connections (yours or others') going invalid around the same time, this is often a short-lived, transient issue that reconnection usually resolves without any deeper changes needed.

How to Reconnect

Here's a step-by-step guide to reconnect your NetSuite to Kintsugi and continue syncing

  1. Check your NetSuite role settings first.

    • Make sure Accessible Subsidiaries is set to All and not limited to a single subsidiary.

    • Confirm the role has both SOAP/REST Web Services and Log in using Access Tokens permissions enabled.

    • If your account uses SuiteTax, verify that STE Tax Exemption Certificate is set to View.

    • If you're connecting a sandbox account, double-check the Account ID uses an underscore (884606_SB1) rather than a hyphen.

    • Confirm your Consumer Key/Secret and Access Token ID/Secret were all generated from the same Integration record in NetSuite.

  2. Re-authorize the connection. Once your role settings are confirmed, go to Settings → NetSuite and click Re-authorize, then complete the token setup flow. This is safe to do and will not affect your existing data or filings.

  3. If you're not sure what's misconfigured, you can check NetSuite's own audit trail for more detail: go to Setup → Users/Roles → User Management → View Login Audit Trail in your NetSuite account to see what's failing on login.

If the issue persists after re-authorizing and verifying your role settings, contact Kintsugi support.

FAQs

Q: Is it safe to re-authorize my NetSuite connection?

A: Yes. Re-authorizing only refreshes your credentials with NetSuite; it doesn't touch data that's already synced or filings that have already been submitted.

Q: Will I need to redo any of my NetSuite integration settings after reconnecting?

A: No. Your existing configuration stays as-is. Reconnecting only re-establishes the authorization between Kintsugi and NetSuite.

A: Several of my organizations lost their NetSuite connection around the same time. Is that normal?

A: Yes, this happens occasionally and is usually a short, transient issue on NetSuite's side rather than something wrong with your specific setup. Re-authorizing typically resolves it.

Q: I've double-checked my role permissions and the connection still shows "Invalid configuration." What else could it be?

A: Two things worth checking: make sure your TBA credentials (Consumer Key/Secret and Access Token ID/Secret) all come from the same NetSuite Integration record, and confirm your sandbox Account ID uses an underscore, not a hyphen. If both check out, contact Kintsugi support.

Q: Where can I see exactly what's failing on the NetSuite side?
A: In NetSuite, go to Setup → Users/Roles → User Management → View Login Audit Trail. This shows the specific login/permission failures tied to your integration's role.

Q: Does the "STE Tax Exemption Certificate" setting apply to everyone?
A: No. This only applies to accounts using SuiteTax. If your account doesn't use SuiteTax, you can skip this check.

Q: What if reconnecting doesn't resolve the issue?
A: Contact Kintsugi support. Some cases need a fix on our end or coordination with NetSuite directly.

Need Help?

Still need help? Reach out to our support team anytime using the chat in the bottom-right corner of your screen; we are always happy to help.

Was this article helpful?