Hierarchy of posting in Acumatica.

Hi Team,

The hierarchy of posting.  

• Item-Level Accounts Take Precedence → If the GL Account is specified in the Stock Item, it will be used before checking the Posting Class.
• Transaction Overrides Are Always First→ If an account is manually set on a transaction (Receipt, Bill, Invoice, Adjustment), it overrides all other settings.
• Posting Class Acts as a Default → The Posting Class is the fallback if an Item does not have a specific account.
• Warehouse Accounting Can Affect Posting→ If enabled, Warehouse-Specific GL Accounts may override the Posting Class.
• Company Defaults Are Last Resort → If no account is found at the Item, Posting Class, or Warehouse level, Acumatica uses the default GL accounts from Inventory Preferences.

I’m consolidating the “gl account lookup” logic in Acumatica and want to confirm the correct hierarchy of determination. Here’s my proposed ladder of precedence:

1. Transaction-level override (manually set in the document)

2. Item-level GL account (if defined on the stock/non-stock item)

3. Warehouse or location-specific GL (if Warehouse Accounting is enabled)

4. Posting Class defaults (as assigned to the item)

5. Company / system-wide default GL accounts (Inventory Preferences)

A few questions for the community:

• Is this order accurate across all transaction types (PO, SO, adjustments)?

• Are there any “hidden” rules (e.g. order type settings) that override this?

• In your experience, have you run into surprises or exceptions in implementations?

Thanks in advance for your insights!