NetSuite

What Plutus imports

• Vendor bills, by vendor and GL account
• Filtered to the expense accounts you name — nothing else

Connecting

Method: OAuth 2.0 Client Credentials (M2M)

1. In NetSuite, go to Setup > Integration Management > Manage Integrations and create a new Integration record with Client Credentials (Machine to Machine) enabled. Note its Client ID.
2. Generate an RSA key pair. Upload the public certificate to the Integration record and note the Certificate ID NetSuite assigns it — keep the private key.
3. In Plutus, paste your NetSuite Account ID, the Client ID, the Certificate ID, and the private key (PEM format).
4. Name the expense accounts holding your software and infrastructure spend, exactly as they appear in your chart of accounts (for example, Software Subscriptions, Computer & Internet Expenses). This is required — without it, Plutus would import your entire general ledger, including rent, payroll, and travel, and every chart would describe it as technology spend. Only lines posted to the accounts you name are read: a bill that mixes a subscription with an office expense contributes the subscription line only.
5. Save the connection. As with any payment-side source, newly discovered vendors are held until you decide what each one is.

Notes

NetSuite is an ERP rather than a cloud bill, so this follows the same model as Ramp and QuickBooks: read vendor bills off the general ledger, and route discovered vendors through the same review step those two use.

This uses NetSuite’s Client Credentials (M2M) flow rather than an interactive OAuth login, so there’s no refresh token to expire and no recurring reconnect. The certificate itself can be issued valid for up to 2 years — renew it in NetSuite before it expires, or the next sync will fail with an auth error naming it.