Acumatica

The Corma and Acumatica integration connects your Acumatica cloud ERP to Corma's identity governance platform, so IT and finance teams can see who holds which Acumatica roles, grant the right access when someone joins, and remove it the day they leave. Acumatica runs financials, distribution, manufacturing and project accounting for mid-sized companies, so every user account leads straight to your financial data.

Key takeaways

• Acumatica does not charge per user, so governing Acumatica access is about risk and audit evidence, not license savings.
• Acumatica permissions are built from roles and restriction groups, which decide which forms and which branches a user can reach.
• Corma ties Acumatica access to joiner, mover and leaver events and to recurring access reviews that finance auditors can rely on.

Why govern Acumatica access if users are unlimited?

Acumatica states that it does not charge by user and offers unlimited users at no additional cost. Good news for your budget, and a quiet risk for your internal controls: with no seat to pay for, nobody has a financial reason to close an account. Former employees, temporary accountants and external consultants often keep their logins long after their mission ends.

Inside the ERP, roles are sets of access rights to forms and actions, and restriction groups limit what a user sees by branch or company. After a few reorganizations, users collect roles they no longer need. The classic case is one person who can both create a vendor and approve its payment, a conflict auditors look for under separation of duties.

How Corma governs Acumatica access

• One view of Acumatica accounts and roles, next to every other application in your stack, so dormant and external accounts stand out.
• Joiner, mover and leaver automation: automated provisioning gives a new accountant the Acumatica access they need, adjusts it when they change team and revokes it at offboarding.
• Access reviews for finance controls: managers confirm or remove each Acumatica account in automated access review campaigns, and every decision is logged as evidence for ISO 27001 or a statutory audit.

If you already use single sign-on, keep it. Acumatica supports OpenID Connect providers such as Microsoft Entra ID, Google and Okta, but SSO decides how people log in, not which roles they keep. Corma's identity governance answers that second question.

Who uses the Corma Acumatica integration?

CFOs and controllers who answer to auditors, IT managers who run onboarding and offboarding, and finance teams who want to see their software, and who uses it, in one place.

Frequently asked questions

How do I connect Corma to Acumatica?

An Acumatica administrator authorizes Corma through a secure OAuth flow, in about a minute and with no code. Corma then starts syncing accounts, and most teams run fully automated workflows within a few days.

Can Corma reduce Acumatica license costs?

Not directly, because Acumatica pricing is not based on user seats. The value of the integration is control: fewer dormant accounts, cleaner roles and faster audits.

How is our financial data protected?

Corma requests only the permissions needed to manage access, encrypts data in transit and at rest, hosts it in France on AWS and is ISO/IEC 27001:2022 certified. You can revoke the connection at any time.

Want to see Acumatica access next to the rest of your stack? Book a Corma demo.