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

Two tools, one question

Business Central gives finance teams two ways to track project-related costs: Dimensions and Jobs. They look similar on the surface — both let you attach more detail to a transaction — but they serve different purposes. Using the wrong one creates lasting problems: report clutter, missing budget control, and billing gaps.

This article explains what each tool does, when to use each, and the most common mistake finance teams make when configuring Business Central.

What are Dimensions in Business Central?

Dimensions are reporting tags. They attach to transactions — G/L entries, sales orders, purchase invoices, journals — so you can slice financial data without multiplying your chart of accounts.

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; the North warehouse does not cease to exist at year end. A Dimension value carries no budget, no start date, and no completion state.

What are Jobs in Business Central?

Jobs — renamed Projects in Business Central 2024 — are a dedicated module for tracking a defined piece of work from start to finish. A Job holds:

• A budget — planned hours and costs broken down by task
• Actuals — time sheets, purchase orders and expenses posted against it
• WIP — work-in-progress calculations for revenue recognition
• Invoicing — billing schedules linked directly to what was spent

Jobs have a lifecycle. They open, accumulate costs, get invoiced, and close. Business Central tracks the gap between budget and actual at every stage.

The core difference

The simplest way to state it:

• Dimension: "Tag this transaction so I can report by category."
• Job: "Track all revenue, cost and time against this named piece of work."

Dimensions slice existing data for reporting. Jobs aggregate costs and revenue into a structured project with its own budget, WIP and billing lifecycle. A Dimension value has no financial structure of its own. A Job does.

When to use Dimensions

• Categorising transactions for a permanent entity — a department, a cost centre, a region
• High-volume, always-on splits — tagging every sales invoice by region, for example
• Fund accounting — labelling grants or restricted funds across many nominal codes
• Where the same category will be reported on for years regardless of what is posted to it

When to use Jobs

• Client work that is quoted, delivered, and invoiced
• Any project with a defined budget and a completion date
• When you need a budget vs actual view for a specific project
• Billing that depends on what was spent — time and materials or milestone billing
• Construction, professional services, sub-contracted work, grant-funded capital projects
• Anywhere you need WIP accounting for revenue recognition under FRS 102 or IFRS 15

The most common mistake

The classic error is creating a new Dimension value for every client project. It feels natural at first — add "ProjectABC" as a value and tag costs to it. Within a year the dimension has hundreds of values, no budgets, no billing links, and no way to tell which entries are still active.

Signs this has happened in your system:

• A dimension called "Project" with hundreds of values, many of them stale
• A spreadsheet sitting alongside Business Central tracking project hours and costs separately
• Sales invoices raised manually with no link to what was spent on the work
• No WIP balance — revenue recognised when invoiced rather than when earned

The remediation is to migrate active project tracking into Jobs and restrict the Dimension to the permanent categories it is designed for.

Using both together

Jobs fully support Dimensions. Every cost posted to a Job can also carry a Department, Region or Cost Centre dimension. This lets you answer compound questions — "What is our WIP on all London-office projects this quarter?" — by combining the Job module for WIP with a Region dimension for the office split.

Think of it as a two-layer structure: Jobs provide the project container; Dimensions add the cross-cutting reporting view on top.

A quick decision guide

• Does it have a completion date and a budget? → Job
• Does it persist for years with no natural end? → Dimension
• Do you bill clients based on what you spent? → Job
• Do you report on it monthly as part of management accounts? → Dimension
• Do you need WIP calculations for revenue recognition? → Job

Frequently asked

We already 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 adequate. If you have a budget and invoicing requirements, you need a Job.

We are in professional services. Which do we need?
Jobs. Professional services firms need WIP accounting, client billing, and budget-vs-actual in one place. A Dimension alone cannot provide any of those.

Our Dimension list has grown to hundreds of project values. What now?
Block the stale values from new postings, migrate active projects into Jobs, and reset the Dimension to permanent categories only. This is a standard finding and remediation step in Business Central health checks.

What changed when Microsoft renamed Jobs to Projects?
The name changed in Business Central 2024 Wave 1. The module structure and functionality are the same. Existing records created before the rename still appear under the Jobs menu in earlier versions.

Can a Job appear in management accounts alongside Dimension-tagged costs?
Yes. Job Ledger Entries post to G/L accounts and appear in all G/L-based reports. Attach Dimensions to the Job or its planning lines and you get the project view and the departmental breakdown in the same report.

Take the free ERP Health Check →