# Acumatica User Role and Access Matrix Worksheet > Source: https://netray.co/tools/acumatica-user-role-access-matrix-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Plan which users get which Acumatica roles and access levels, score segregation of duties risk and export an auditor friendly matrix. ## Category erp-operations ## Erp Acumatica ## Audience - ERP administrator - Controller - Internal auditor - Implementation lead ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### User **Key:** user **Type:** text #### Department **Key:** dept **Type:** select **Options:** - Finance - Purchasing - Sales - Production - Warehouse - Quality - IT #### Acumatica role **Key:** role **Type:** text #### Functional area **Key:** area **Type:** select **Options:** - AP - AR - GL - Inventory - Purchasing - Sales Orders - Manufacturing - System Admin #### Access level **Key:** access **Type:** select **Options:** - View - Insert - Update - Delete #### Can create **Key:** creates **Type:** number **Help:** 1 if the user can create transactions in this area, else 0 #### Can approve **Key:** approves **Type:** number **Help:** 1 if the user can approve or release, else 0 #### SoD risk score **Key:** sod_score **Type:** number **Expr:** creates * approves * 5 + creates * 1 + approves * 2 **Format:** integer #### Reviewed by **Key:** reviewer **Type:** text #### Last review **Key:** review_date **Type:** date **Rows:** **User:** j.moreno **Dept:** Purchasing **Role:** Purchaser **Area:** Purchasing **Access:** Delete **Creates:** 1 **Approves:** 1 **Reviewer:** Controller **Review date:** 2026-09-15 **User:** a.lindqvist **Dept:** Finance **Role:** AP Clerk **Area:** AP **Access:** Update **Creates:** 1 **Approves:** 0 **Reviewer:** Controller **Review date:** 2026-09-15 **User:** r.okafor **Dept:** Finance **Role:** Controller **Area:** GL **Access:** Delete **Creates:** 0 **Approves:** 1 **Reviewer:** CFO **Review date:** 2026-09-18 **User:** m.tanaka **Dept:** Warehouse **Role:** Warehouse Lead **Area:** Inventory **Access:** Update **Creates:** 1 **Approves:** 0 **Reviewer:** Operations **Review date:** 2026-09-20 **User:** s.petrov **Dept:** IT **Role:** Administrator **Area:** System Admin **Access:** Delete **Creates:** 1 **Approves:** 1 **Reviewer:** CIO **Review date:** 2026-09-22 **Totals:** #### Total SoD risk score **Key:** sod_score **Agg:** sum **Format:** integer #### Highest single row score **Key:** sod_score **Agg:** max **Format:** integer **Notes:** The score is a simple triage aid: rows where one person both creates and approves score 8. It does not replace a formal SoD analysis of your Acumatica roles. ## Content **Intro:** Auditors and controllers ask the same question: who can create and approve the same transaction? This worksheet lays out users, roles and rights so conflicts show up before go-live and at each periodic review. **Sections:** #### How to use it **Body:** List each user and the Acumatica role that grants access, then the functional area and the access level. Mark whether the role lets the person create transactions and whether it lets them approve or release. The worksheet scores the combination, with create plus approve in one area scoring highest. Record the reviewer and date so the matrix doubles as evidence of a periodic access review. Export to Excel for audit files. **Bullets:** - Start from job functions, then design roles - Give each person the least access that works - Review administrators and approvers first - Repeat the review at least annually and after role changes #### Roles and access levels in Acumatica **Body:** Acumatica controls access through roles assigned to users, with rights set per screen and, where relevant, per field or entity. Common access levels are View Only, Insert, Update and Delete, and rights accumulate when a user holds several roles. That accumulation is why combined roles create hidden conflicts: a purchaser who also holds an approver role can raise and release a purchase order. Approval workflows add another layer, so check both role rights and approval maps. #### Reading the score **Body:** A row scoring 8 means the same user can create and approve in that area and should have a documented compensating control, such as a second approver or an exception report. A score of 1 or 2 is normal. The total is useful for tracking improvement between review cycles, not as an absolute measure. Always examine the highest rows individually rather than relying on the sum. #### Common mistakes **Body:** Teams copy the access of a departing employee to a new hire, carrying old conflicts forward. Another mistake is to leave the implementation consultant or an integration account with administrator rights after go-live. Service accounts used for API integrations also need a row, with a named owner and the narrowest rights possible. **Cta:** If you want continuous monitoring of access conflicts across your ERP using an on-prem model with read-only access, we can discuss what that looks like. **Faq:** #### Is this a segregation of duties analysis? **Answer:** It is a planning and triage aid. A formal analysis compares the actual rights of each role against a conflict rule set. Use this sheet to organize roles and reviewers, then confirm the real rights in Acumatica before relying on it for audit purposes. #### How often should access be reviewed? **Answer:** Quarterly for administrators and financial approvers, and at least annually for everyone else. Also review after any organizational change, acquisition or role redesign. Record the date and reviewer in the sheet for evidence. #### Should integration accounts be listed? **Answer:** Yes. API users and scheduled integration accounts often carry broad rights and are rarely reviewed. List them with an owner and the purpose of the integration so they are included in every access review. #### Can I use it for other ERPs? **Answer:** The structure works for any ERP with role based access. Rename the Acumatica role column and adjust the functional areas. The scoring logic is generic. ## Search terms acumatica roles and permissions template, acumatica segregation of duties matrix, erp user access matrix excel, acumatica access rights worksheet, role based access control template erp, sox user access review template --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json