For Brendan and IT

Open the NetSuite connection

SuiteTalk REST only — not a third-party connector. Sandbox first. We do not need a NetSuite login or a VPN. Send credentials out of band, never on this page.

Back to the package

What we are connecting

Sweepa will push issued sales invoices, the payments that settle them, and credit notes for card refunds. Stripe card payments also carry Camperdown’s Sweepa platform fee of 1.5 percent and Stripe’s processing fee as expense lines so a one-hundred-dollar invoice ties to the bank deposit. Bookings, gate codes and member records are not transactions.

This page is the handshake: switch SuiteTalk on, send us the IDs, we prove the pipe with one test invoice. Production stays off until that looks right.

What you do in NetSuite

1. Enable the features

Administrator: REST Web Services and OAuth 2.0. Use a sandbox company first — the account id will look like a production id with _SB1 on the end.

2. Create the Sweepa integration

Setup, Integration, Manage Integrations, New. Name it Sweepa. Tick Client Credentials, Machine to Machine. Save once and copy Client ID and Client Secret immediately — NetSuite will not show them again.

3. Dedicated user and role

Not a person’s login. Role may create Invoice, Customer, Customer Payment and Credit Memo. No bank, payroll or employee access.

4. Map the certificate

Setup, Integration, Manage Authentication, OAuth 2.0 Client Credentials. Map that user and role to Sweepa. Upload the public certificate we send. Note the Certificate ID NetSuite returns.

5. Confirm the account id

The realm in your SuiteTalk host: ACCOUNTID.suitetalk.api.netsuite.com (sandbox ids often end in _SB1). Sandbox first. Tell us the subsidiary if the company has more than one.

6. Draft the chart map

Income accounts, GST tax codes, receivables or undeposited funds, and expense accounts for the Sweepa fee and the Stripe fee. A spreadsheet is enough.

What to send Sweepa — securely, not on this page

Account IDThe SuiteTalk realm, including _SB1 if sandbox.: Sandbox first
Client ID and Client SecretFrom the Sweepa integration record. Shown once on save.: Once only
Certificate IDFrom the M2M mapping. We hold the private key; you upload the public file.: After upload
SubsidiaryWhich company the invoices post to.: If multi-sub
Chart and tax mapIncome, GST, AR or undeposited funds, Sweepa fee, Stripe fee.: Spreadsheet OK
Test customer OKPermission to post and void invoice SWEEPA-TEST-001.: Yes or create

How we prove the connection

Token

We request a token at the SuiteTalk OAuth URL — ACCOUNTID.suitetalk.api.netsuite.com, then /services/rest/auth/oauth2/v1/token. A valid token is the connection test.

Test invoice

We post SWEEPA-TEST-001 on a dummy customer. You confirm it in NetSuite. We credit or void it.

Then two more

One card-style payment with both fee lines. One open invoice marked paid offline — no card fees. Production IDs wait until those three look right.

Questions we get first

Do you need our NetSuite password?

No. No VPN, no bank details, no employee or payroll access. Machine-to-machine only, on a role we agree with you.

Is this live on 1 October?

That is the target once the handshake and the three test documents look right. Until then, issued invoices can still leave Sweepa as a file if you need a stopgap.

What posts into NetSuite?

Issued invoices, Stripe or offline payments, credit notes for card refunds, and the two fee lines on card sales so the bank deposit ties out. Not the booking diary.

What we are connecting

This page is the handshake: switch SuiteTalk on, send us the IDs, we prove the pipe with one test invoice. Production stays off until that looks right.

What you do in NetSuite

1. Enable the features

Administrator: REST Web Services and OAuth 2.0. Use a sandbox company first — the account id will look like a production id with _SB1 on the end.

2. Create the Sweepa integration

3. Dedicated user and role

Not a person’s login. Role may create Invoice, Customer, Customer Payment and Credit Memo. No bank, payroll or employee access.

4. Map the certificate

Setup, Integration, Manage Authentication, OAuth 2.0 Client Credentials. Map that user and role to Sweepa. Upload the public certificate we send. Note the Certificate ID NetSuite returns.

5. Confirm the account id

The realm in your SuiteTalk host: ACCOUNTID.suitetalk.api.netsuite.com (sandbox ids often end in _SB1). Sandbox first. Tell us the subsidiary if the company has more than one.

6. Draft the chart map

Income accounts, GST tax codes, receivables or undeposited funds, and expense accounts for the Sweepa fee and the Stripe fee. A spreadsheet is enough.

What to send Sweepa — securely, not on this page

Account IDThe SuiteTalk realm, including _SB1 if sandbox.

Sandbox first

Client ID and Client SecretFrom the Sweepa integration record. Shown once on save.

Once only

Certificate IDFrom the M2M mapping. We hold the private key; you upload the public file.

After upload

SubsidiaryWhich company the invoices post to.

If multi-sub

Chart and tax mapIncome, GST, AR or undeposited funds, Sweepa fee, Stripe fee.

Spreadsheet OK

Test customer OKPermission to post and void invoice SWEEPA-TEST-001.

Yes or create

How we prove the connection

Token

We request a token at the SuiteTalk OAuth URL — ACCOUNTID.suitetalk.api.netsuite.com, then /services/rest/auth/oauth2/v1/token. A valid token is the connection test.

Test invoice

We post SWEEPA-TEST-001 on a dummy customer. You confirm it in NetSuite. We credit or void it.

Then two more

One card-style payment with both fee lines. One open invoice marked paid offline — no card fees. Production IDs wait until those three look right.

Questions we get first

Do you need our NetSuite password?

No. No VPN, no bank details, no employee or payroll access. Machine-to-machine only, on a role we agree with you.

Is this live on 1 October?

That is the target once the handshake and the three test documents look right. Until then, issued invoices can still leave Sweepa as a file if you need a stopgap.

What posts into NetSuite?

Issued invoices, Stripe or offline payments, credit notes for card refunds, and the two fee lines on card sales so the bank deposit ties out. Not the booking diary.

Open the NetSuite connection

What we are connecting

What you do in NetSuite

1. Enable the features

2. Create the Sweepa integration

3. Dedicated user and role

4. Map the certificate

5. Confirm the account id

6. Draft the chart map

What to send Sweepa — securely, not on this page

How we prove the connection

Token

Test invoice

Then two more

Questions we get first

When the IDs are ready

Open the NetSuite connection

What we are connecting

What you do in NetSuite

1. Enable the features

2. Create the Sweepa integration

3. Dedicated user and role

4. Map the certificate

5. Confirm the account id

6. Draft the chart map

What to send Sweepa — securely, not on this page

How we prove the connection

Token

Test invoice

Then two more

Questions we get first

When the IDs are ready