Jobs vs Dimensions in Business Central: Which to Use and When

Business Central gives finance teams two ways to track project-related costs: Dimensions and Jobs. They look similar on the surface, because both attach more detail to a transaction, but they serve different purposes, and using the wrong one creates lasting problems.

This guide explains what each tool does, when to use each, and the most common mistake finance teams make when they set Business Central up.

What are Dimensions in Business Central?

Dimensions are reporting tags. Microsoft's guide to working with dimensions explains that they can, for example, indicate the project or department an entry came from, so you do not need separate G/L accounts for each one.

A business might define four dimensions:

• Department: Finance, Operations, Sales
• Cost centre: Head office, North warehouse, Remote
• Region: North, South, Export
• Project: a catch-all tag for informal cost tracking

Dimensions are permanent categories. Finance always has a Finance department, and the North warehouse does not disappear at year end. A dimension value carries no budget, no start date and no completion state.

What are Jobs in Business Central?

Jobs, now called Projects in Business Central, are a dedicated module for tracking a defined piece of work from start to finish. Microsoft's project management overview covers what a project holds:

• A budget: you can set up a budget for each project, divided into tasks if you need that detail
• Actuals: time sheets, purchases and expenses posted against it
• Work in process (WIP): an estimate of the project's financial value while it is ongoing
• Invoicing: billing when the work finishes or on a schedule

A project has a lifecycle. It opens, gathers costs, gets invoiced and closes, and you can compare budget against actual along the way.

Key PointA dimension tags a transaction so you can report by category. A project tracks all revenue, cost and time against a named piece of work.

The core difference

Dimensions slice existing data for reporting. Projects gather costs and revenue into a structure with its own budget, WIP and billing.

A dimension value has no financial structure of its own. A project does.

When to use Dimensions

• Categorising transactions for a permanent entity, such as a department, cost centre or region
• High-volume, always-on splits, such as tagging every sales invoice by region
• Fund accounting, such as labelling grants or restricted funds across many nominal codes
• Any category you will report on for years, regardless of what is posted to it

When to use Jobs (Projects)

• Client work that is quoted, delivered and invoiced
• Any piece of work with a defined budget and a completion date
• When you need budget against actual for a specific project
• Billing based on what was spent, such as time and materials or milestones
• When you need WIP, because you post costs before you invoice

Microsoft's guide to WIP methods explains that WIP lets you estimate the financial value of projects in the general ledger while they are ongoing.

The most common mistake

The classic error is creating a new dimension value for every client project. It feels natural at first. Within a year the dimension has hundreds of values, no budgets, no billing links and no way to tell which are still active.

Signs this has happened in your system:

• A dimension called "Project" with hundreds of values, many of them stale
• A spreadsheet alongside Business Central tracking project hours and costs
• Sales invoices raised by hand with no link to what was spent
• No WIP balance, so revenue is recognised when invoiced rather than as the work is done

Watch OutThe fix is to move active project tracking into Projects and keep the dimension for the permanent categories it was designed for.

Using both together

You do not have to choose one for the whole business. Use projects for the work that has a budget, a lifecycle and billing, and keep dimensions for the permanent categories you report on every month.

Each then does the job it was designed for, and neither ends up cluttered with values that belong to the other.

Pro TipWrite down which categories are dimensions and which pieces of work are projects. A one-page rule stops the two drifting into each other.

A quick decision guide

• Does it have a completion date and a budget? Use a project.
• Does it last for years with no natural end? Use a dimension.
• Do you bill clients based on what you spent? Use a project.
• Do you report on it monthly in the management accounts? Use a dimension.
• Do you need WIP? Use a project.

Frequently asked

We track projects through a dimension value. Is that wrong?

Not necessarily. If the project is an informal internal cost pool with no budget or client billing, a dimension value may be enough. If you have a budget and invoicing, you need a project.

We are in professional services. Which do we need?

Projects. Professional services firms usually need WIP, client billing and budget against actual in one place, and a dimension alone provides none of those.

Our dimension list has grown to hundreds of project values. What now?

Stop the stale values being used for new postings, move active projects into Projects, and keep the dimension for permanent categories. Our Business Central health check guide covers how to review dimensions as part of a wider setup review.

Is your setup working for you?

If your project reporting lives in spreadsheets, our article on why month-end should not take a week shows where the time goes.

Our free ERP Health Check asks where your system is letting you down and sends back a short report on where to focus first, with no obligation. You can also talk to our team. For independent guidance, see the ICAEW technology resources, and for VAT, GOV.UK says all VAT-registered businesses should now be signed up for Making Tax Digital for VAT.