Anrok

The Corma and Anrok integration keeps access to your sales tax data in line with the finance team that owns it. Anrok describes itself as the global sales tax solution built for SaaS, and it syncs with billing systems such as Stripe, Chargebee, QuickBooks Online, NetSuite and Xero. Even its most limited role sees every customer, transaction and return, so the list of Anrok users is a list of people who can read your sales data.

Key takeaways

• Anrok has three roles, Viewer, Editor and Admin, and even Viewers can see all of the company's customers, transactions and returns in Anrok.
• Only Anrok Admins can add users, change permission levels or remove users, and Admins cannot remove themselves from the account.
• Each Anrok seller account has its own API keys, and a key's secret can no longer be viewed in Anrok after it is generated.
• Anrok-built integrations sync data both ways with billing systems such as Stripe, Chargebee, QuickBooks Online, NetSuite and Xero.

Who can see your tax data in Anrok?

Anrok's roles are simple, and broad. The Viewer role has access to all of the company's data in Anrok, without Settings or Billing and without editing rights, and Editors and Admins go further. Only Admins manage users, invitations stay open for 30 days, and an Admin cannot change their own role or remove themselves, so a departing Admin has to be removed by another Admin.

Connections carry access too. A Stripe connection is authorized by signing in with Stripe credentials from Anrok, and the Chargebee integration exchanges keys both ways: a Chargebee read-only key goes into Anrok and an Anrok key goes into Chargebee. Anrok API keys are created under Settings with a notes field and can be disabled and re-enabled, and Anrok does not document scopes or expiry for them.

How Corma governs Anrok

• Users mapped to the finance team: Corma maps each Anrok user to an employee, so people outside tax and finance, or people who left, stand out. See how Corma works for finance teams.
• Leavers removed by another Admin: a leaver workflow in the IT Workflow Builder asks a remaining Anrok Admin to remove the person, with an approval step and a clear audit trail.
• Keys and connections with an owner: Anrok API keys and the keys exchanged with Chargebee are non-human identities that need a named owner.
• Roles reviewed before audits: Admin and Editor roles go into automated access reviews, so edit rights on tax data are confirmed on a schedule.

Frequently asked questions

Does Anrok support SSO or SCIM?

Anrok's pricing page lists single sign-on as a plan feature, but its help center does not document the protocol, an identity provider setup or SCIM. Login is documented as a password plus a code from a two-factor authentication app. Learn what single sign-on covers.

How does Corma connect to Anrok?

Anrok's API reference covers customers, transactions, products and filings and lists no user endpoints, so Corma's browser-based agents handle user steps in Anrok's settings, in an isolated browser session.

Where is Corma data hosted?

Corma runs on AWS, with web servers and databases in data centers inside the European Union. Data is encrypted in transit and at rest, and Corma is ISO/IEC 27001:2022 certified.

Want to know who can read your sales tax data today? Book a Corma demo.