Dynamics 365 for professional services

Professional services — consulting firms, agencies, IT services, engineering services, architects, accountants — have a specific software shape: they sell people's time, deliver against project plans, capture time and expense, bill complex contracts, and report on utilisation and margin. Dynamics 365 covers it through the combination of Sales, Project Operations, and either Business Central or Finance for the back office.

The shape.

• Sales runs the opportunity pipeline — prospects, qualified opportunities, won deals, lost analysis.
• Project Operations handles the project lifecycle from contract to delivery — WBS, resourcing, time and expense, milestone billing.
• Business Central (for SMB firms) or Finance (for larger firms) takes the resulting invoices into general ledger and AR.

The integration between these is configured, not custom — Microsoft ships standard integrations for the common patterns.

Sales side

Pursuit of services deals through opportunities, with quoting that includes project phases, named or generic resources, expected hours per role, and pricing. Quotes can include retainers, milestone schedules, capped time-and-materials, and fixed-price components in the same contract.

Resourcing

A resource hub in Project Operations shows availability by skill, location, cost rate, and time. Resource managers assign named resources to confirmed projects; sales pre-assigns generic roles to pipeline opportunities for capacity planning. Firms staffing projects across multiple countries add offshore delivery models on top — resource company versus contracting company being the core design decision there.

Time and expense

Consultants enter time on a weekly time sheet against project tasks, with billable/non-billable classification. Expenses come in with receipt photos, policy compliance (per-diem limits, mileage rates), approval workflow, and reimbursement integration.

Billing

The hard part of professional services software. Project Operations supports complex billing scenarios: time-and-materials with capped budgets, milestone-based invoicing, retainer drawdown, fixed-price with progress recognition, and combinations on a single contract. Invoices stage through review and then post to BC or Finance for collection.

Revenue recognition

ASC 606 / IFRS 15 compliance. Project Operations defers and recognises revenue per the contract's performance obligations — straight-line for retainers, percentage-of-completion for fixed-price, on-billing for T&M. The financial postings land in the GL through the back-office system.

Utilisation and margin reporting

Pre-built Power BI dashboards cover the metrics professional services firms live by: billable utilisation per consultant, project margin, backlog, revenue per FTE, time-to-bill.

Variants.

• Small/medium firms (under 50 consultants) often start with BC + Project Operations Lite — simpler, faster to deploy, BC as the accounting backbone.
• Larger firms move to Finance + Project Operations with the F&O accounting stack.
• Pure consulting/agency teams without complex back-office needs sometimes run Sales + Project Operations alone, with a simple accounting integration to QuickBooks or Xero.

Where the value compounds

Tying the Sales pipeline to Project Operations resourcing means revenue forecasts are real — based on actual people-availability, not optimistic spreadsheets.

Where to go next

The core product is Project Operations, with time and expense as the daily surface. The two finance questions services firms fight over are covered in revenue recognition and utilisation reporting. Smaller firms often start on Business Central projects. A neighbouring project-driven vertical with its own accounting quirks is Dynamics 365 for construction, where job costing plays the same role time and expense plays here.