Sage Intacct Dimensions, Explained (and How Card Spend Should Use Them)

If you came to Sage Intacct from QuickBooks or a legacy GL, "dimensions" is the concept that changes everything — and the one that most expense workflows never fully use. This guide explains what dimensions are, which ones you have, and what it takes for corporate card spend to actually arrive dimension-complete.

What a dimension is

In an old-style segmented chart of accounts, every reporting slice gets baked into the account number: 6010-100-NYC means travel expense, department 100, New York. Want a new location? Multiply your account list again. Intacct's answer is to keep the account list small and attach dimensions — independent tags like department, location, and project — to each transaction line. Per Sage's dimensions overview, a dimension is a classification used to organize, sort, and report on company information, available on both reports and transaction entry pages.

The payoff is reporting: profit and loss by location, by project, by customer, by any combination — without a combinatorial chart of accounts.

The dimensions you have

Intacct ships with a core set of standard dimensions, with a few arriving alongside specific modules (Doeren Mayhew has a good rundown; see also Sage's types of dimensions):

Dimension	Typical use for card spend
Department	Which team owns the expense — usually derivable from the cardholder
Location	Entity or office — often fixed per card or per employee
Project	Client work, jobs, grants — the one that usually needs a human or a rule
Customer	Billable/reimbursable spend attribution
Vendor	The merchant, normalized to your vendor list
Employee	The cardholder
Item	Goods/services detail (arrives with Order Entry, Purchasing, or Inventory)
Class	A free-form slice many teams use for product lines or funds
Warehouse	With Inventory Control
Contract	With the Contracts module

Beyond these, user-defined dimensions built on Platform Services behave like standard ones anywhere dimensions appear — so if your company tracks funds, programs, or events as UDDs, card spend can and should carry them too.

Why card spend is where dimensions break down

Dimension discipline is easy in AP: a bill gets keyed once, deliberately. Card spend is the opposite — high volume, small amounts, entered after the fact by whoever draws the short straw. In practice three failure modes show up:

• GL-account-only coding. Transactions land with an account and nothing else, and every report that slices by department or project silently omits card spend.
• Batch guessing at month end. Someone codes 300 transactions in one sitting, three weeks after the purchases, with predictable accuracy.
• The spreadsheet middle layer. Dimensions get tracked in Excel and re-keyed into Intacct — double entry with double the error surface.

What dimension-complete card spend looks like

The fix is structural: dimensions get set on the transaction, upstream of Intacct, while context still exists.

1. Derive the derivable. Employee is the cardholder. Department and location usually follow from the employee or the card. These should never be typed by hand.
2. Rule the recurring. The same merchants recur month after month; a merchant-based rule can carry a full dimension set — account, department, location, class — not just a category.
3. Suggest the rest. For the long tail, AI suggestions drawing on your actual dimension values (not a generic category list) get you a review pass instead of data entry.
4. Block the incomplete. If project is required for job costing, an export gate that holds back dimension-incomplete transactions beats discovering the gaps in a report.

Run that pipeline and what posts to Intacct is indistinguishable from carefully keyed AP — at card-feed volume.

Where Summit Spend fits

Summit Spend was built around exactly this workflow: it connects the corporate cards you already have (any bank, via Plaid), then codes each transaction against all ten Intacct dimensions — with rules, AI suggestions trained on your chart of accounts and dimension values, custom dimension labels, and approvals — before anything exports. If dimension-complete card spend is the goal, you can test it against your own Intacct instance on a 14-day trial.