Other ERPsFree referencePDF, Excel, Word exportAcumatica

Acumatica Screen ID Reference

Every Acumatica screen has an ID that appears in the URL, in roles and in generic inquiries. This lookup lists the IDs people need most when they set up security or write integrations.

Download:

Screen ID	Screen name	Module
SO301000	Sales Orders	Sales Orders
SO302000	Shipments	Sales Orders
AR301000	Invoices and Memos	Accounts Receivable
AR302000	Payments and Applications	Accounts Receivable
AR303000	Customers	Accounts Receivable
AP301000	Bills and Adjustments	Accounts Payable
AP302000	Checks and Payments	Accounts Payable
AP303000	Vendors	Accounts Payable
PO301000	Purchase Orders	Purchase Orders
PO302000	Purchase Receipts	Purchase Orders
IN202500	Stock Items	Inventory
IN202000	Non-Stock Items	Inventory
IN301000	Receipts	Inventory
IN302000	Issues	Inventory
IN303000	Transfers	Inventory
IN304000	Adjustments	Inventory
GL301000	Journal Transactions	General Ledger
SM208000	Generic Inquiry	System Management
SM201010	Users	System Management
SM201020	User Roles	System Management

Screen IDs follow a pattern: two letter module code, a digit for the screen type (1 setup, 2 master data, 3 transaction, 4 inquiry or processing, 5 report in many modules), then four digits. Confirm IDs in your own instance because labels and numbering change across releases and manufacturing screens may differ with the edition.

Access design review

Optional: an expert review of your Acumatica role and access design.

Optional. The tool and every export work without this. No spam.

How to use the lookup

Search by ID or by screen name. Use the IDs when you open a screen from a link, when you grant access rights to a role, or when you build a generic inquiry or import scenario that targets a given screen. Exporting the rows to Excel gives you a checklist for a role design workshop, where each role is mapped to the screens its users need.

Reading a screen ID

The first two letters are the module, such as SO for Sales Orders. The next digit hints at the type of screen: setup, master data, entry forms, processing screens and reports. This convention is useful for guessing where a screen lives, though it is not a strict rule across every module and release.

The ID is visible in the page URL
Roles grant rights per screen ID
Import scenarios target a screen ID

Common mistakes

Administrators often give a role blanket rights across a module instead of the specific screens. Developers confuse the screen ID with the endpoint entity name used in the REST API, which is different. Remember to re-check IDs after upgrades, and keep the list for your custom screens separate.

Frequently Asked Questions

Where can I see a screen ID?

It appears in the browser address bar as the ScreenId parameter and in the page title area. It is also listed on the Access Rights screens.

Is the screen ID the same as the REST entity?

No. REST entities such as SalesOrder or StockItem are defined by the web service endpoint, while the screen ID identifies the UI screen.

Do manufacturing screens use different IDs?

Manufacturing features add their own screens with their own module codes. Look them up inside your instance, since they depend on the edition and release.

Do IDs change between versions?

The core IDs are very stable, but check after major upgrades, especially for screens that were restructured or renamed.

If you are tightening roles before an audit or go-live, we can help review your Acumatica access design.

Talk to an Expert Explore More Free Tools

Related Tools

Developer Tools

More Other ERPs tools

See all

Back to All Tools