Dimensions & Analytics Axes

Dimensions add analysis power beyond what your chart of accounts provides alone. While your GL accounts categorize transactions by nature (salary, rent, travel), dimensions categorize them by context -- which department incurred the cost, which project it supports, which location it belongs to, or which business segment it serves. This multi-dimensional tagging enables the kind of cross-cutting analysis that drives real business decisions.

Two-Level Structure#

Dimensions use a clean two-level structure. Dimension types define the analysis categories your organization needs: department, project, location, cost center, business segment, or any custom axis. Dimension values define the specific options within each type: Engineering, Sales, and Marketing for department; North America, Europe, and Asia for region; or any hierarchy you need.

Each dimension value can have a parent, creating hierarchical structures that support roll-up reporting. A location dimension might have USA at the top, with West and East regions below, and individual states (California, Oregon, New York) at the leaf level. Reports can show totals at any level in the hierarchy.

Transaction Tagging#

When you post any transaction -- an AP invoice, journal entry, expense report, or payroll entry -- you can tag it with dimension values. A marketing expense might carry department=Marketing, location=NYC, and project=Q2-Campaign. These tags travel with the transaction through your ledger and appear in every report that includes dimension analysis.

Dimension validation ensures that only configured values can be used on transactions. If a dimension type is marked as required, every transaction must carry a value for that type. This prevents the "uncategorized" bucket that plagues organizations trying to do departmental reporting after the fact.

Multi-Entity Support#

Dimensions use the same master-entity architecture as other master data. Types and values are defined at the organization level, with entity-specific overrides available when needed. A department dimension value that means "Engineering" for your US entity might be overridden to "Tehnika" for your Estonian entity -- same code, different display name, same reporting rollup.

Reporting Power#

With dimensions in place, your financial reports gain a new axis of analysis. Instead of just seeing total salary expense, you can see salary expense by department. Instead of revenue by account, you can see revenue by business segment and region. Budget variance reports can compare planned versus actual at the dimension level, showing which department is over budget or which project is consuming more resources than expected.

This analysis happens naturally through the reporting system -- no pivot tables, no manual data manipulation. Ask for revenue by segment, and you get it.