# Sage Intacct Objects and Standard Dimensions Reference

> Source: https://netray.co/tools/sage-intacct-dimension-and-module-reference
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A searchable lookup of common Sage Intacct API object names and the standard dimensions used to tag transactions.

## Category

other-erp

## Erp

Sage Intacct

## Audience

- Sage Intacct developer
- Controller
- Finance systems analyst

## Tool

**Kind:** worksheet

**Mode:** reference

**Columns:**

#### API object

**Key:** object

**Type:** text

#### Area

**Key:** area

**Type:** text

#### What it holds

**Key:** meaning

**Type:** text

**Rows:**

**Object:** LOCATION

**Area:** Dimension

**Meaning:** Standard dimension for entities, sites or business units

**Object:** DEPARTMENT

**Area:** Dimension

**Meaning:** Standard dimension for organizational departments

**Object:** PROJECT

**Area:** Dimension

**Meaning:** Standard dimension for projects and jobs

**Object:** CLASS

**Area:** Dimension

**Meaning:** Standard dimension for classification of transactions

**Object:** EMPLOYEE

**Area:** Dimension

**Meaning:** Standard dimension for employees

**Object:** CUSTOMER

**Area:** Dimension and AR

**Meaning:** Customer master record

**Object:** VENDOR

**Area:** Dimension and AP

**Meaning:** Vendor master record

**Object:** ITEM

**Area:** Dimension and Inventory

**Meaning:** Item master record

**Object:** WAREHOUSE

**Area:** Dimension and Inventory

**Meaning:** Warehouse master record

**Object:** GLACCOUNT

**Area:** General Ledger

**Meaning:** Chart of accounts entry

**Object:** GLBATCH

**Area:** General Ledger

**Meaning:** Journal entry header

**Object:** GLENTRY

**Area:** General Ledger

**Meaning:** Journal entry line

**Object:** GLJOURNAL

**Area:** General Ledger

**Meaning:** Journal definition

**Object:** APBILL

**Area:** Accounts Payable

**Meaning:** Vendor bill header

**Object:** APBILLITEM

**Area:** Accounts Payable

**Meaning:** Vendor bill line

**Object:** APPYMT

**Area:** Accounts Payable

**Meaning:** Payment to a vendor

**Object:** ARINVOICE

**Area:** Accounts Receivable

**Meaning:** Customer invoice header

**Object:** ARINVOICEITEM

**Area:** Accounts Receivable

**Meaning:** Customer invoice line

**Object:** ARPYMT

**Area:** Accounts Receivable

**Meaning:** Customer payment

**Object:** CHECKINGACCOUNT

**Area:** Cash Management

**Meaning:** Bank or checking account

**Object:** EXPENSEREPORT

**Area:** Expense management

**Meaning:** Employee expense report

**Object:** CONTRACT

**Area:** Contracts

**Meaning:** Contract header for revenue management

**Object:** PODOCUMENT

**Area:** Purchasing

**Meaning:** Purchasing transaction document

**Object:** SODOCUMENT

**Area:** Order Entry

**Meaning:** Order entry transaction document

**Notes:** Object names are those used by the Sage Intacct web services; lines and subtypes can differ by release and subscription. Confirm in the object reference of your own company before building an integration. Custom dimensions are added per company and are not listed here.

## Content

**Intro:** Sage Intacct tags every transaction with dimensions instead of building an ever longer account string. This reference lists the standard dimensions and the API object names developers look up most often.

**Sections:**

#### How to use the reference

**Body:** Type part of an object name or an area into the search box to filter the table. Use the object column when you write queries against the web services and the area column to see which module owns the data. Export the filtered rows to Excel to share with your implementation team or to document a mapping from your legacy system.

#### Why dimensions matter

**Body:** Location, department, project, class, employee, customer, vendor, item and warehouse are standard dimensions. Any journal line or transaction line can carry several of them at once, which lets finance report by combinations without a huge chart of accounts. Plan dimensions before migrating history, because changing the design after go-live means restating data.

**Bullets:**

- Keep the chart of accounts lean
- Use dimensions for analysis, not accounts
- Decide required dimensions per account early

#### Common mistakes

**Body:** Teams often create accounts for what should be a dimension value, copy a legacy segment structure one for one, or forget that user-defined dimensions need a defined relationship to transaction types. When integrating, also check whether your subscription enables the module behind the object you query.

**Cta:** Designing dimensions for a manufacturer is easier with a second opinion. We can help review your mapping.

**Faq:**

#### What are the standard dimensions?

**Answer:** Location, department, project, class, employee, customer, vendor, item and warehouse are the standard dimensions. Companies can add user-defined dimensions on top of these.

#### Where do I find the full object list?

**Answer:** The Sage Intacct developer documentation lists every object and its fields for each release. This reference only covers the commonly used names.

#### Can transactions use more than one dimension?

**Answer:** Yes. A single line can carry location, department, project and others together, which is the main advantage over a segmented account string.

#### Are custom dimensions available through the API?

**Answer:** Yes, user-defined dimensions are exposed as objects or fields in the company, with names that depend on how they were created.

## Search terms

sage intacct standard dimensions, sage intacct api object names, intacct location department project class, sage intacct glaccount apbill object, sage intacct object list, sage intacct dimensions explained

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json