- Business Central offers two ways to track projects: the full Projects/Jobs module for task, budget, and timesheet-level accounting, or a project financial dimension that tags transactions for per-project reporting from the GL.
- Use the module when the system must manage the work itself, and use the dimension when execution and scheduling already live in another system and you only need profitability by project.
- The choice affects licensing: a dimension-based approach can keep users on cheaper Essentials, while the full project module may push them to Premium across every seat.
- Keep dimensions lean at roughly two to four (like department, project, and cost center), because every extra one is a field to fill in correctly on every transaction and a drag on reporting.
When the finance lead at an engineering-heavy clean-energy company told us he wanted to "track everything by project," our first question surprised him: do you actually need the project module, or just a project tag? It's one of the most useful, least understood choices in a Business Central setup, and getting it right can lower your licensing bill.
Two very different ways to "track projects"
Business Central, Microsoft's cloud ERP (enterprise resource planning) system, gives you two paths:
- The Projects module (older versions call it Jobs). This is full project accounting: project tasks, budgets, time entries, and timesheets, with planned-versus-actual cost and revenue at a detailed level.
- A project financial dimension. A "dimension" in Business Central is just a tag you attach to transactions, like department or cost center. Add a project dimension and every invoice, bill, and journal entry can carry the project it belongs to, so you can report cost and revenue per project straight from the general ledger.
The module is the right answer when the system needs to manage the work: assign tasks, capture labor against them, and bill from them.
The dimension is the right answer when you only need to see profitability by project, and the actual execution and scheduling already live somewhere else, like a dedicated scheduling tool.
A good rule of thumb: if you're already managing the schedule and the work breakdown in another system, you probably want the project dimension in Business Central, not the full module. Don't pay to model the same project twice.
The part that touches your wallet
Here's the wrinkle most buyers never hear: the choice can change your license tier. The lighter, dimension-based approach can keep certain users on the less expensive Essentials license, where leaning on the full project module may push you to Premium. Multiply that across a handful of seats and it's real money every month, for a capability you may not need.
While you're at it: keep your dimensions lean
One more piece of hard-won advice. Dimensions are powerful, so it's tempting to add a lot of them. Resist. Most healthy implementations use a handful, often two to four, such as department, project, and cost center. We've seen companies arrive from older systems with fifteen or twenty segments, and every one becomes a field someone has to fill in correctly on every transaction, plus a drag on reporting. Add the dimensions you'll actually report on, and no more.
The broader lesson is worth keeping: in Business Central, "we need to track projects" is a question with two answers at two price points. Decide what you need the system to do, the work or just the reporting, before you turn anything on.
If you're scoping a Business Central setup and want a second opinion on where the module is overkill and a dimension will do, that's an easy conversation. Let's talk it through.