Other ERPsFree referencePDF, Excel, Word exportSage Intacct

Sage Intacct Objects and Standard Dimensions Reference

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.

Download:
API objectAreaWhat it holds
LOCATION
Dimension
Standard dimension for entities, sites or business units
DEPARTMENT
Dimension
Standard dimension for organizational departments
PROJECT
Dimension
Standard dimension for projects and jobs
CLASS
Dimension
Standard dimension for classification of transactions
EMPLOYEE
Dimension
Standard dimension for employees
CUSTOMER
Dimension and AR
Customer master record
VENDOR
Dimension and AP
Vendor master record
ITEM
Dimension and Inventory
Item master record
WAREHOUSE
Dimension and Inventory
Warehouse master record
GLACCOUNT
General Ledger
Chart of accounts entry
GLBATCH
General Ledger
Journal entry header
GLENTRY
General Ledger
Journal entry line
GLJOURNAL
General Ledger
Journal definition
APBILL
Accounts Payable
Vendor bill header
APBILLITEM
Accounts Payable
Vendor bill line
APPYMT
Accounts Payable
Payment to a vendor
ARINVOICE
Accounts Receivable
Customer invoice header
ARINVOICEITEM
Accounts Receivable
Customer invoice line
ARPYMT
Accounts Receivable
Customer payment
CHECKINGACCOUNT
Cash Management
Bank or checking account
EXPENSEREPORT
Expense management
Employee expense report
CONTRACT
Contracts
Contract header for revenue management
PODOCUMENT
Purchasing
Purchasing transaction document
SODOCUMENT
Order Entry
Order entry transaction document

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.

Dimension design second opinion

Optional: an expert review of your Intacct dimension plan.

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

How to use the reference

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

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.

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

Common mistakes

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.

Frequently Asked Questions

What are the standard dimensions?

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?

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?

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?

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

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

Talk to an ExpertExplore More Free Tools

Related Tools

Developer Tools

Sage Intacct XML readByQuery Request Generator

Build a ready-to-post XML request for the Sage Intacct web services gateway using readByQuery with your object, fields, query and page size.

Other ERPs

Sage 300 Database Table Reference

A quick lookup of well-known Sage 300 SQL table names, the module they belong to and what each stores, for reports and integrations.

Other ERPs

Sage 100 Table and Module Prefix Reference

Find the Sage 100 module prefix and the commonly used table names for items, customers, vendors, orders and bills of material.

More Other ERPs tools

See all
Back to All Tools