Skip to content

Security

Read-only by design.

Our products are built for finance data, so security comes first.

How data moves

NetSuite stays the system of record.

We read your ledger as it is. Nothing we do changes a transaction. When something needs to go back, it leaves as a file your own team imports.

NetSuiteYour system of record
Read-only
ClarativeReviews and approvals
File · approved
NetSuiteYour team imports

The controls

Seven things we hold ourselves to.

The controls your auditors already expect, applied to the data we read.

01

Read-only access to NetSuite

We read your data and never change a transaction. Anything that needs to go back goes as a file your own team imports.

02

Your data, separated

Each customer's data is held separately, in the UK.

Confirm before launch: Confirm hosting region wording.
03

Sign-in your way

Microsoft or Okta single sign-on, or passwords with two-factor authentication.

Confirm before launch: Two-factor is in development; confirm the wording at launch.
04

Least privilege

Each person sees only the companies and modules they're given.

05

Separation of duties

Preparers can't approve their own work; approvals and changes are recorded.

06

A full audit trail

Of sign-ins, changes and approvals.

07

Independent review

Regular security reviews of the code and the servers.

Confirm before launch: Confirm before publishing.

See how the controls work on example data.