Business Central Jobs & Projects Module

What Business Central Jobs (Projects) actually are

Business Central Jobs, now branded Projects, is the built-in module for managing project accounting: any body of work with a customer, a budget, consumed resources or items, and an invoice. Microsoft's own overview describes it as supporting project management tasks (creating projects, scheduling resources), providing budget information and monitoring progress, and tracking machine and employee hours on projects using time sheets.

It is integrated, not standalone. The same module posts to the general ledger, pulls from inventory, links to purchasing, and feeds the sales-side invoicing engine. That integration is the main reason a project-based SME chooses Business Central Jobs over a dedicated PSA tool bolted onto a separate ledger: one source of truth for cost, revenue, and WIP.

This guide covers the module as it ships in Business Central Essentials and Premium. Project management is included in the Essentials tier at $80/user/month; Premium ($110/user/month) adds Manufacturing and Service Management but does not change the Projects module itself.

Business Central project structure: card, tasks, planning lines

A Business Central project has two layers. The header is the Project Card, which carries the bill-to customer, the project posting group, the WIP method, dates, and the responsible manager. Beneath it sits a hierarchical list of Project Tasks, each typed as Begin-Total, Posting, or End-Total. Every posting, whether usage or sale, references a task, so the task list is the spine of the project.

Inside each Posting task sit Project Planning Lines, the line-level budget. Each planning line is one of three types: Budget (added to the schedule, not invoiced), Billable (invoiced, not added to the schedule), or Both Budget and Billable (invoiced and added to the schedule). Choosing Both is the common pattern for time-and-materials work, where expected usage and expected revenue match; separating Budget from Billable is the pattern for fixed-price billing.

A concrete tell that a project is misconfigured: the team cannot create a sales invoice for it. The cause is almost always that only Budget planning lines were entered. You need Billable planning lines to invoice a customer.

• →Layer 1: Project Card (header) — customer, posting group, WIP method, dates, manager.
• →Layer 2: Project Tasks (Begin-Total / Posting / End-Total) — all posting references a task.
• →Layer 3: Project Planning Lines on Posting tasks — Budget, Billable, or Both Budget and Billable.
• →Budget lines track expected cost; Billable lines track expected sales; Both is typical for time-and-materials billing.
• →Cannot invoice a project? You almost certainly only created Budget lines. Add Billable lines.

Resources: capacity, work types, and project-specific pricing

Resources are the people, machines, or subcontractor pools whose time and cost flow through a project. Each resource carries a unit cost and unit price, plus work types (overtime, weekend, specialized task) that adjust cost and price. A single resource can be both internal (employee) and external (contractor), which matters when the same project mixes employed consultants and subcontracted specialists.

Resources are attached to planning lines, not directly to tasks. Capacity is visible through the resource register, and over-allocation surfaces in capacity reports. Pricing can be overridden at the project level: project-specific resource prices take precedence over the standard resource price, so a senior consultant can bill at one rate on Project A and another on Project B without duplicating the resource record.

For shift-based teams, the constraint to plan around is that licenses are per named user, not per concurrent session. Seasonal or shift coverage is better served by a Device license (a workstation-licensed seat) than by bouncing a single license between users, which the Online Services Terms do not permit.

Recording usage: journals, time sheets, purchase orders, picks

Usage is how budgeted work becomes actual cost. Business Central records project usage through four integrated channels, all of which post to the project ledger and (where relevant) the general ledger.

Project journals accept manual lines for labor, materials, machine time, and expenses, and a Calc. Remaining Usage action pulls planned quantities into the journal for fast entry. Integrated time sheets let resources submit hours against a project task and planning line, route the sheet through an approval workflow, and post approved lines straight to the project journal. Purchase orders and purchase invoices can be linked to a project task so third-party costs land on the right project automatically. And where warehouse is in scope, inventory picks move items from bins to a project task, consuming stock against the project.

The audit trail this produces is the second reason project-based SMEs choose Business Central Jobs: usage entries (actual consumption) and sale entries (actual invoicing) both live in the project ledger, side by side, so budget-versus-actual and billable-versus-invoiced comparisons are native, not exported.

Business Central WIP methods: five ways to recognize a project

Work in Process (WIP) is how Business Central estimates the financial value of an ongoing project in the general ledger before the customer is invoiced. It exists because for most projects, costs accrue and revenue is recognized on different cadences; without WIP, the income statement would overstate cost in early periods and overstate revenue when the invoice finally lands.

Business Central ships five WIP methods. Cost Value and Cost of Sales recognize based on incurred cost. Sales Value recognizes based on invoiced sales. Percentage of Completion recognizes cost as incurred and sales in proportion to cost-versus-budget. Completed Contract defers all recognition until the project is finished. Once a method has been used on a project, it cannot be modified, so the choice should be deliberate.

WIP is calculated and posted as two separate periodic steps: first Calculate WIP, which writes Project WIP Entries, then Post WIP to G/L, which moves those values to the general ledger. Many teams calculate weekly but post monthly. The WIP Cockpit is the central page for reviewing calculated-but-unposted WIP before it hits the ledger.

Invoicing a Business Central project

Invoicing converts Billable planning lines into posted sales invoices and credit memos. The standard flow uses Qty. to Transfer to Invoice on each planning line to mark how much to bill this cycle, then a sales invoice pulls those lines in. Batch invoicing lets one invoice cover multiple projects for one customer; lines can be combined or kept separate per the customer's preference.

Fixed-price billing is supported through fixed-price planning lines, and installment or payment-schedule billing is supported through dedicated Billable task lines that act as milestone invoices. Partial billing is native: transfer some quantity now, the rest later. Credit memos reverse invoiced amounts cleanly against the originating project task.

One limitation worth flagging before go-live: the Get Project Planning Lines action works on sales invoices but not on sales orders or sales quotes, and its filter options are limited (Ship-to and Contact are not always available). If your sales process requires quoting or ordering before invoicing, design the project-to-invoice flow around sales invoices, not orders.

Project analytics: statistics, reports, and the Power BI app

Business Central exposes project analytics at four levels of depth. The Project Statistics page gives a real-time snapshot of a single project: budget, usage, billable, invoiced, WIP, and recognized amounts. Project and resource ledger entries are the granular record behind those totals, drillable from the statistics page.

Standard reports cover the routine needs. Report 1006 (Project Planning Lines) summarizes planned work; Report 1008 (Project Analysis) gives a financial overview based on user input; Report 1010 (Project WIP to G/L) calculates WIP for one or all projects and posts results to the general ledger; Report 1012 (Projects per Customer) shows scheduled price, percent complete, and invoiced amounts by customer. Every report supports Open in Excel for offline analysis.

For richer visualization, the Power BI Projects app ships reports for Project Profitability (actual cost vs. price, margin KPIs), Project Tasks, Project Realization, Performance to Budget, Invoiced Sales, and a Timeline/Gantt view. These reports are generally available as of Business Central 2024 release wave 2 and pull from the Job, Job Task, and Job Ledger Entry tables.

• →Project Statistics: real-time per-project snapshot (budget, usage, billable, invoiced, WIP).
• →Report 1006 (Project Planning Lines), 1008 (Project Analysis), 1010 (Project WIP to G/L), 1012 (Projects per Customer).
• →WIP Cockpit: central page for reviewing calculated-but-unposted WIP.
• →Open in Excel on every standard report for offline analysis.
• →Power BI Projects app: Profitability, Tasks, Realization, Performance to Budget, Invoiced Sales, Timeline (GA in 2024 wave 2).

Setting up Business Central projects before go-live

Microsoft's setup guidance is explicit that before you can use Business Central to manage projects, you must set up resources, time sheets, and projects. The setup sequence below is the order that minimizes rework, because later steps depend on earlier ones.

1. 01
   Set up Resources

   Create resource records for every person, machine, or subcontractor pool that will charge time to a project. Enter unit cost and unit price, define work types (overtime, weekend, specialized), and decide whether each resource is internal or external. Resources drive every planning line, so this is the foundation.

2. 02
   Set up Time Sheets

   Configure time sheets on the Resources Setup and User Setup pages, including approval rules (who approves whom) and the project journal posting link. Time sheets are the lowest-friction way to capture labor usage, so approval flow should match your real organizational structure.

3. 03
   Configure Projects Setup

   On the Projects Setup page, set the default WIP method (the one most of your projects will use), set Apply Usage Link default to Yes if you want usage to stay tied to its planning line, and confirm the default posting groups. These defaults reduce data entry error at project creation.

4. 04
   Map Project Posting Groups to G/L accounts

   For each Project Posting Group, map the G/L accounts for WIP accrued cost, WIP applied cost, WIP recognized cost, WIP cost adjustment, and the matching sales accounts. These mappings must align with your chart of accounts, because every project posting routes through them. Get this reviewed by whoever owns your GL.

5. 05
   Review WIP Methods

   On the WIP Methods page, review the five built-in methods and confirm which ones your finance team will actually use. You can create custom WIP method codes if standard methods do not fit your recognition policy, but most SMEs use Percentage of Completion or Completed Contract. Lock the choice per project at creation time, because it cannot be changed after WIP entries exist.

What Business Central projects cost to run

Project management is included in both Business Central licensing tiers; you do not pay extra for the module. Essentials is $80/user/month and Premium is $110/user/month, USD, billed annually, following Microsoft's November 2025 list-price adjustment (Essentials rose from $70, Premium from $100). Team Members is $8/user/month for light read-and-approve users such as approvers or time-entry staff.

For a typical 10-person project-based SME on Essentials, list annual license cost is $9,600/year. The storage entitlement that came with the November 2025 change is also relevant: Essentials now includes 3 GB per user (up from 2 GB) and Premium includes 5 GB per user (up from 3 GB), with an 80 GB tenant base. Most project-based SMEs stay well under those allowances.

Licenses are purchased through a Cloud Solution Provider (CSP) partner, and entitlements are enforced through Microsoft Entra ID service plans. At least one full Essentials or Premium license is required per tenant. The licensing guide is the authoritative source for which service plans unlock which pages.

Limitations to plan around before you configure projects

Three limitations come up repeatedly in real Business Central projects, and each is documented by Microsoft. Planning for them before go-live is much cheaper than retrofitting after.

First, with Directed Put-Away and Pick locations (advanced warehousing), Project No. and Task No. cannot be combined on a purchase order the way they can in basic warehousing. Receipts and consumption are more separated, and you must enter a To-Project Bin Code on the Location Card. If your warehouse runs advanced bin management, design the project consumption flow around that separation.

Second, advanced WIP methods (Cost Value, Percentage of Completion, Sales Value) require correctly entered Billable (Total Price) and Budget (Total Cost) values. Incomplete data produces warnings or incorrect recognition. And once WIP entries exist, you may need to delete them via the WIP Cockpit before changing certain task or WIP settings. Treat WIP setup as a finance-controlled configuration, not a project-manager one.

Third, the Get Project Planning Lines invoicing action works on sales invoices but not on sales orders or quotes, with limited filtering. If your commercial process requires a quote-to-order-to-invoice chain, either accept that project billing bypasses the order stage or use a custom flow.

Who Business Central projects is for (and who should look elsewhere)

Business Central Jobs is well suited to SMEs whose work is project-shaped: professional services, field service, light construction and trades, marketing and design agencies, IT implementers, and any business that bills by milestone, time-and-materials, or fixed price against a budget. If your finance team needs WIP on the balance sheet and your operations team needs resource scheduling against customer commitments, the module fits.

It is a weaker fit for heavy construction job-cost accounting with prevailing-wage or union rules, where a vertical like Dexter + Chaney or a construction-specific ERP handles certified payroll and retention more natively. It is also a weaker fit for pure PSA-only shops that do not need a connected general ledger, where a dedicated PSA tool may be simpler. And for SMEs that want an open-source, self-hostable alternative with its own project accounting, Odoo's project and timesheet modules are the route we implement when Business Central is the wrong call.

The practical test: do you need project accounting that posts to the same ledger as the rest of your business? If yes, Business Central Projects is in scope. If you need standalone job costing disconnected from ERP, it is not.