Reporting Dimensions

Create and manage reporting dimensions to further analyze your financial reporting beyond just the chart of accounts. This is useful for concepts like cost centers, departments, projects, and more.

Overview

Reporting dimensions are a feature in Mezan that allows you to create and manage dimensions to further analyze your financial reporting beyond just the chart of accounts. This is useful for concepts like cost centers, departments, projects, and more.

Using Reporting Dimensions

Every transaction in Mezan can be associated with a reporting dimension. This is useful for concepts like cost centers, departments, projects, and more. Reporting dimensions are used in all of the Mezan modules:

  1. Sales
  2. Purchasing
  3. Inventory
  4. Fixed Assets
  5. Accounting

When a transaction is created, you can select the reporting dimension in the transaction form.

Reporting Dimensions can be used in the following reports:

  1. Trial Balance
  2. Balance Sheet
  3. Income Statement
  4. Account Statements
  5. Customer Statements
  6. Vendor Statements

With more to come soon. If you need reporting dimensions on a report we don't support yet, you can request it by contacting support.

Use Cases of Reporting Dimensions

Reporting dimensions are useful for concepts like cost centers, departments, projects, and more.

A few key use cases of reporting dimensions are:

  1. As cost centers for business units, to group expenses and revenues by business unit, and then use that filter in the income statement to figure out profit by business unit.
  2. As projects for business assets, cashflow, expenses, or revenues, to figure out the available cash on hand for a project, a project's profitability, or track staff billing by project.
  3. As departments, to track payroll or other expenses by department.

Grouping Reporting Dimensions

Currently reporting dimensions aren't structured in multiple levels, but there are ways to use them to create a hierarchy, as Mezan supports multiple dimensions to be attached to a transaction.

The following pattern of use is supported:

  1. Create a reporting dimension for the parent category, for example "Projects".
  2. Create a reporting dimension for the child categories, for example "Project 1" and "Project 2".
  3. When creating a transaction, select the parent category, for example "Projects", along with the needed child categories, for example "Project 1" and "Project 2".
  4. When viewing a report, filter by the parent category, for example "Projects", and then drill down into the child categories, for example "Project 1" and "Project 2", to filter by multiple dimensions at once.

This also allows you to find the intersection of dimensions, for example the profit of "Project 1" by "Business Unit B" in "Sales Department".

Transaction forms don't enforce the use of reporting dimensions, we leave it optional as it's not always required for typical business operations.