Business Central Service Management & Contracts: Complete Guide [2026]

Overview: Service Management in Business Central

Business Central’s service management module is designed for organizations that provide maintenance services, support contracts, equipment repairs, or recurring service visits. It automates service contract administration, labor billing, parts tracking, and technician dispatch from a single location or distributed service team.

The service module is fundamentally different from the sales/inventory module:

• Sales: Customers buy products; transaction is complete; relationship may end
• Service: Customers sign service contracts; recurring service calls/invoices occur over months/years; relationship is ongoing and profitable

A typical service scenario: A manufacturer sells industrial equipment and offers a 3-year maintenance contract. The customer gets quarterly preventive maintenance visits, emergency repair coverage, and spare parts included. Business Central service module automates creating service orders for each visit, invoicing, tracking labor costs, managing spare parts inventory, and measuring contract profitability.

This guide covers contract types, setup, invoicing, resource allocation, and—critically—when BC service is sufficient and when you need D365 Field Service or Customer Service instead.

Licensing & Availability

Service Management License Requirements

The service management module in Business Central is available only in Premium licenses. Organizations with Essentials licenses cannot use service contracts, service orders, or service dispatching features.

Business Central Edition	Service Module Available?	Notes
Essentials	No	Basic sales & inventory only; no service contracts
Premium	Yes	Full service management, contracts, dispatching
D365 Field Service (Dynamics 365)	Yes (separate app)	Mobile-first field operations, real-time dispatch, complex routing
D365 Customer Service (Dynamics 365)	Yes (separate app)	Ticket/incident management, omnichannel support, not field operations

If your organization runs Essentials and wants service features, you must either upgrade to Premium or integrate with D365 Field Service (if you need mobile dispatch and real-time routing).

Service Contracts: Types & Structure

Service Contract Overview

A service contract is a multi-month or multi-year agreement that defines what services the customer receives, how often, and for what price. The contract is the "master" record; from it, BC automatically generates service orders at defined intervals (monthly, quarterly, annually) and invoices for each period.

Key service contract fields:

• Contract number: Unique identifier (e.g., SC-2024-001234)
• Customer: Bill-to customer
• Service items: What is covered (equipment, component, service package)
• Service period: Frequency of service visits (monthly, quarterly, annually)
• Contract price: Total contract value
• Billing method: Monthly invoice, annual invoice, or usage-based
• Contract start date: When service begins
• Contract expiration date: When contract ends (often 1-3 years)
• Automatic renewal: Auto-renew on expiration or manual renewal required
• Service items covered: Which parts/labor are included vs. extra charge
• Technician assignment: Default technician or resource team for this customer

Service Contract Types

Type 1: Fixed Monthly/Annual Price Contract

Customer pays a fixed monthly or annual fee for defined service. Examples:

• Quarterly preventive maintenance on HVAC equipment: $500/quarter
• Annual support plan for software system: $10,000/year
• Monthly inspection service: $2,000/month

BC automatically generates an invoice each period (month or quarter) for the contract price. Labor and parts may be included or billed separately.

Type 2: Hourly or Usage-Based Contract

Customer pays for actual labor hours, parts consumed, or usage metrics. Examples:

• Technician support: $150/hour for emergency calls (minimum 2 hours)
• Equipment rental with maintenance: $5,000/month + $25 per operating hour
• Parts and repair service: Hourly labor rate + parts cost at invoice time

BC tracks actual labor hours and parts consumed per service call, then invoices based on actual usage. This requires more detailed service order tracking.

Type 3: Hybrid (Fixed + Variable)

Customer pays a fixed base fee plus overages for extra service or parts. Examples:

• Support contract: $3,000/month (includes 20 hours); overage $200/hour
• Equipment lease: $2,000/month (includes maintenance) + parts at cost

Service Items vs. Regular Items

In BC, you create service items specifically for service contracts. A service item represents what is being serviced (equipment, component, installed system) and can include spare parts used during service.

Item Type	Regular Item (Inventory)	Service Item	Use Case
What it is	A product you sell to customers	Equipment/component that needs service	Sold product can have service contract
Inventory tracked?	Yes (stock on hand, reorder points)	Optional (tracking installed units)	Service items don’t have stock; they track installed base
Example	Widget model W-500 in warehouse (50 units available)	Widget model W-500 installed at customer site (serial #1234)	Customer buys W-500; later gets service contract for that unit
Parts included?	No (parts sold separately)	Yes (spare parts linked to service item)	Service contract specifies which parts are included

Best practice: Create service items as the "serviced unit" (e.g., "Widget W-500 Maintenance Plan"). Link regular parts items as components. When a service call occurs, parts are deducted from inventory and cost-tracked per service order.

Service Contract Setup & Workflow

Step 1: Create Service Items

Before creating contracts, set up the services/equipment you’ll contract:

1. Open Service Items list in BC
2. Create new service item (e.g., "HVAC-5000 Maintenance")
3. Assign item category and customer
4. Define spare parts included (link part items that can be used in repairs)
5. Set service response times (SLA: how quickly service responds if customer calls)
6. Assign default resource (technician/repair person)

Step 2: Set Up Service Price Groups (Optional)

If you charge different prices for different customer tiers:

• Create service price groups (e.g., "Premium", "Standard", "Budget")
• Assign pricing per service item per group
• Assign customer to price group (or leave blank for default pricing)

Step 3: Create Service Contract

1. Open Service Contracts list
2. Create new contract
3. Enter contract number (auto-generated or manual)
4. Assign customer and service items covered
5. Set contract price (total for period)
6. Define billing period (monthly, quarterly, annual)
7. Set start and expiration dates
8. Specify automatic renewal (yes/no)
9. Save and release contract (status changes from "Draft" to "Active")

Step 4: Automatic Service Order Generation

Once contract is active, BC automatically creates service orders at the defined frequency:

• Monthly contract: Service order created first day of each month
• Quarterly contract: Service order created first day of each quarter
• Annual contract: Service order created on anniversary date

Service orders remain in "Pending" status until technician is assigned and scheduled.

Step 5: Dispatch Service Orders & Technician Scheduling

When a service order is ready for execution:

1. Assign technician/resource from Resource List
2. Schedule service date/time (or leave flexible)
3. Technician confirms availability and accepts
4. On service date, technician travels to customer, performs work
5. Technician logs labor hours and parts used in BC
6. Service order marked as completed
7. Invoice automatically generated per contract terms

For fixed-price contracts: Invoice is automatic; amount = contract price regardless of actual hours/parts.

For hourly contracts: Invoice amount = logged hours × hourly rate + actual parts cost.

Service Invoicing & Recurring Billing

Automatic Invoice Generation

BC automates recurring invoicing per contract terms:

• Fixed-price contract ($2,000/month): BC creates sales invoice for $2,000 on first day of each month. Accountant approves and posts to GL.
• Hourly contract: BC creates sales invoice based on actual service order costs (labor + parts).
• Billing date: Configurable per contract (first of month, last day, specific day)

Service Order Completion & Invoice Details

For hourly/usage-based contracts, the service order completion creates an invoice with details:

Line Item	Source	Cost Basis
Technician labor (16 hours)	Service order labor log	16 hours × $150/hour = $2,400
Spare parts (bearing, seal, oil)	Parts list in service order	Actual parts cost from inventory
Travel/fuel (if configured)	Service resource setup	Fixed fee or mileage-based
Markup (service profit)	Service price group	Cost × markup % (e.g., +40%)

The invoice reflects actual costs + profit margin, providing transparency to the customer and profitability tracking for management.

Recurring Invoicing Best Practices

• Invoice in advance or arrears: Configure whether contract invoices on service start date (in advance) or service completion (in arrears). Most businesses invoice in advance.
• Prepaid contracts: If customer prepays annual contract, hold credit in receivables; post to revenue monthly using revenue recognition rules (avoid front-loading revenue).
• Invoice review workflow: Don’t post service invoices automatically. Review for accuracy (hours match, parts didn’t get double-charged). Establish approval before GL posting.
• Contract renewal: When contract expires, auto-renewal creates new contract with updated terms/pricing. Communicate renewal terms to customer in advance (typically 30-60 days before expiration).

Resource Allocation & Technician Management

Resource Setup in Business Central

A resource in BC service module is a person or team available to execute service. Create resources for:

• Technicians: Individual service personnel
• Teams: Groups of technicians (e.g., "East Region Service Team")
• Equipment: If service requires specialized equipment rental

For each resource, configure:

• Name & ID: Unique identifier (e.g., TECH-001, Team-East)
• Type: Person or team
• Hourly rate: Cost per hour for labor billing
• Hours available: Max hours per week/month (capacity planning)
• Location: Where the resource operates (base location)
• Skills/certifications: Custom field for qualifications
• Calendar: Working days/hours, vacation, unavailable dates

Resource Allocation to Service Orders

When a service order is created, you allocate a resource:

• Automatic: If service item has default resource assigned, automatically use that technician
• Manual: Dispatch manager selects best resource based on availability, skills, location
• Optimization: BC doesn’t do smart routing/optimization. You manually assign based on geography and capacity. (D365 Field Service does automatic routing.)

Capacity Planning & Resource Utilization

Track resource availability and capacity:

• Hours available per week: Technician works 40 hours/week. Set max capacity to 40.
• Assigned hours: Service orders consume hours (e.g., 8 hours per monthly customer visit). Track total assigned hours vs. available.
• Utilization report: Generate report showing actual worked hours vs. capacity. If technician assigned 50 hours for 40-hour week, over-allocated.
• Resource dashboard: (Requires custom development or Power BI) Track technician workload, customer satisfaction, billable hours vs. capacity.

Resource Costing & Profitability

Resource costs affect service profitability:

• Hourly cost: Set technician hourly cost (e.g., $75/hour salary + overhead cost)
• Billable rate: Separately set what you charge customer (e.g., $150/hour). Profit = $150 - $75 = $75/hour per technician.
• Service order profitability: Calculate profit as (invoice amount) - (technician cost + parts cost + travel cost)
• Contract profitability: Sum all service orders under contract; if contract loses money, renegotiate or discontinue.

Example: Quarterly maintenance contract on $2,000/quarter. Service orders cost: Technician 8 hours @ $75 = $600, Parts $200, Travel $100. Total cost $900. Gross profit $2,000 - $900 = $1,100/quarter (55% margin). Acceptable.

Spare Parts Tracking & Loaner Management

Service Item Components & Parts

When you create a service item, you can link components (spare parts that might be needed):

• Service item: "HVAC-5000 Maintenance"
• Components: Air filter (PART-001), Thermostat (PART-002), Bearing (PART-003)

During a service call, technician may use one or more components. BC tracks which parts were consumed and deducts from inventory. Cost of parts is included in service order cost.

Loaner Tracking

Loaner items are equipment you provide to the customer while their unit is being serviced. Common in manufacturing:

• Customer’s HVAC breaks; you provide loaner unit while you repair original
• You track loaner serial number, condition on loan-out, expected return date
• When customer returns loaner, you verify condition (charged for damage if customer damaged it)

In BC, you create a loaner item for each physical loaner unit. When service order is created for customer, assign loaner. BC tracks:

• Loaner serial number
• Date loaned to customer
• Expected return date (based on service contract repair timeline)
• Actual return date and condition
• Damage charges (if applicable)

Generate loaner aging report to identify long-term loaners that should be recalled or replaced.

Parts Inventory Management for Service

Maintain a separate inventory location for service parts:

• Service warehouse location: Physical stockroom where technicians get parts before traveling to customers
• Parts reorder: Set reorder points for commonly-used service parts. When inventory drops below reorder point, create purchase order automatically or manually
• Parts obsolescence: If service item is discontinued, mark as inactive but keep inventory for warranty/installed base support
• Expiration tracking: For perishable parts (oil, refrigerant), track shelf life. Discard expired parts before use.

Service Contract Profitability & Analysis

Contract Profitability Calculation

To measure whether a service contract is profitable:

Metric	How BC Calculates	Example
Contract revenue	Sum of all invoices under contract (usually fixed price × number of periods)	$2,000/month × 12 months = $24,000/year
Service order costs	Technician hours + parts + overhead per service call	8 hours @ $75 + $200 parts = $800 per month
Total contract cost	Sum of all service order costs over contract lifetime	$800 × 12 months = $9,600/year
Gross margin	Revenue - Cost	$24,000 - $9,600 = $14,400/year
Margin %	(Revenue - Cost) / Revenue × 100	$14,400 / $24,000 = 60%

Contract Profitability Report

Generate a report from BC showing contract profitability by customer, service item, or time period:

• By customer: Which customers are most profitable (highest margin)?
• By service item: Which equipment/services have lowest margin (candidates for price increase)?
• By technician: Which technicians are most productive (highest revenue per hour)?
• Trending: Is margin declining over contract lifetime? (Over time, costs may increase as equipment ages; needs to renegotiate pricing)

Unprofitable contract example: Contract margin dropped from 50% Year 1 to 30% Year 3. Equipment is aging; repairs getting more expensive. Renegotiate price increase or suggest upgrade to new equipment.

Business Central Service vs. D365 Field Service

When BC Service is Sufficient

Choose BC service module if:

• You serve local customers from a single location (or limited geographic area)
• Service calls are scheduled in advance (not emergency response)
• Service team is small (<20 technicians) and manageable in BC
• Contracts are relatively simple (fixed-price or straightforward hourly billing)
• You don’t need real-time mobile dispatch or GPS tracking
• Technicians fill out paper work orders or use BC web portal (not mobile app)
• You don’t need complex routing optimization (e.g., "schedule 5 visits in East region in fewest miles")

Typical BC service organization: Regional HVAC company with 15 technicians, 200 maintenance contracts, monthly service calls. Dispatcher schedules visits in BC, technician picks up work order, performs service, logs hours in BC web portal.

When You Need D365 Field Service Instead

Choose D365 Field Service if:

• Technicians are mobile and work across large geographic area (region/state)
• Real-time dispatch and routing optimization required (e.g., "next available technician nearest customer")
• GPS tracking of technician location needed (for liability, efficiency, SLA compliance)
• Technicians use mobile app in field (not web portal at desk)
• Significant emergency service calls (not all scheduled in advance)
• Complex contracts with multiple service levels, SLAs, priority handling
• Integration with customer service tickets (Field Service = service execution; Customer Service = ticket tracking)
• Technician team is large (100+) across multiple regions
• Travel time and mileage optimization critical to profitability

Typical Field Service organization: Nationwide IT support company. 500 technicians across US. Customer calls with problem; Field Service creates ticket, routes to nearest available technician in real-time, technician navigates to customer with GPS, closes ticket, logs time in mobile app. Real-time visibility to management dashboard.

Comparison Table: BC Service vs. Field Service

Feature	Business Central Service	D365 Field Service	Best For
Deployment model	Web browser (desktop/tablet)	Native mobile app + web	Field Service if tech always mobile
Scheduling	Manual dispatch in BC; limited automation	Intelligent scheduling with routing optimization	Field Service if >50 daily visits to schedule
Real-time dispatch	No (scheduled in advance)	Yes (emergency jobs dispatched in real-time)	Field Service if emergency response needed
GPS tracking	No	Yes (live location tracking)	Field Service for verification & liability
Geographic coverage	Single location or small region	Regional, national, international	Field Service for large geographic area
Contract management	Fixed/hourly contracts; simple	Complex SLA-driven contracts; priority levels	Field Service for complex SLAs
Parts & inventory	Limited (parts for service items)	Advanced (vehicle inventory, parts allocation)	Field Service for mobile inventory
Cost	Included in Premium license (one-time cost)	Separate Dynamics 365 license ($150-250/month per user)	BC if cost is constraint; Field Service if ROI justified
Technician team size	Up to ~30 manageable	100+ easily managed	Field Service for large teams
Setup time	2-4 weeks	4-8 weeks	BC faster to get started
Integration with Customer Service	No (separate from support tickets)	Yes (Field Service executes CS tickets)	Field Service if support tickets drive dispatch

Service Management Best Practices

• Start with fixed-price contracts: Begin with simple monthly/annual fixed-price contracts. Once mature, introduce hourly billing. Avoid mixing pricing models in early stages.
• Define SLAs upfront: Specify response time (how quickly technician responds to call), resolution time (how long to fix), and contract terms clearly. Communicate to customer.
• Resource planning: Don’t over-book technicians. If technician has 40 hours available/week and you assign 50 hours of service orders, something breaks. Maintain 80-85% utilization target; leave buffer for overtime emergencies.
• Contract renewal process: Start renewal discussions 90 days before expiration. Communicate price increases and new terms early. High renewal rate (>90%) indicates healthy service business.
• Parts inventory discipline: Maintain service parts separately from production inventory. Set min/max reorder points. Avoid parts obsolescence (discard outdated parts before they spoil).
• Profitability analysis monthly: Generate service profitability report monthly. Identify unprofitable contracts early. Options: increase price, reduce cost (more efficient technician), or discontinue.
• Technician training & certification: Track technician certifications and training in custom fields. Route complex jobs to certified technicians. Invest in training to improve technician efficiency.
• Customer portal (if possible): If you can set up portal, allow customers to view contract status, schedule service, see invoices, track technician arrival (if using Field Service). Reduces support tickets.

Common Issues & Troubleshooting

Issue: Service Orders Not Auto-Generating from Contract

Check: Is contract status "Active" (not Draft)? | Billing period configured correctly? (e.g., monthly, quarterly) | Contract start date is in past? (Service orders generate from start date forward) | Job queue running? (BC requires background job to auto-generate orders; if paused, orders won’t create)

Issue: Invoice Amount Wrong on Service Order

Check: For fixed-price contract, invoice should equal contract price. If wrong, verify contract price field. | For hourly contract, verify labor hours logged matches time worked. | Parts cost included? Check parts list in service order. | Markup applied correctly? (Profit margin should be cost × markup %).

Issue: Technician Overbooked (Too Many Service Orders)

Check: Resource capacity set correctly? (Configure max hours/week per technician) | Assign jobs to multiple technicians if one is over-allocated. | Consider hiring additional technician or reducing contract volume if demand exceeds capacity.

Issue: Loaner Equipment Not Returned from Customer

Check: Generate loaner aging report; identify loaners outstanding >30 days. | Contact customer to schedule return. | If customer won’t return, charge for loaner loss in next invoice (define policy upfront in contract).

Frequently Asked Questions