A services business runs the same process areas whether it bills five people or five hundred. What separates them is not which processes exist but how many of the decisions inside them were made deliberately. This is the leading practice reference for services: every process area, the flow it follows, the rules that govern it, and a copy-ready skill file for each one.
How to Use This
Each process area below carries three things. A flow, which is the sequence the process actually runs in. A short set of rules specific to services rather than generic ERP advice. And a skill file you can copy straight out of the page, written as markdown so it can be handed to an AI assistant, dropped into a project repository, or used as the basis for a design document.
The skill files are deliberately short. They are checklists for people who already know the domain, not tutorials. Each one names the roles that own the process, the flow, the rules, what to verify before go-live, and the failure modes that recur.
Methodology note. This reflects the Services Standard edition as applied by Azdan across its NetSuite delivery in the UAE, Saudi Arabia, and Egypt. Module availability differs by edition and license, so confirm against your own before treating any rule as available. Where a point is a recommendation from delivery experience rather than a documented rule, it is labeled as one.
The 11 Process Areas
Master Data Management → Design to Build → Lead to Quote → Project Management → Resource Management → Order to Cash → Revenue Management → Return to Credit → Procure to Pay → Return to Debit → Financial Management
Process area
Primary owner
What it covers
Master Data Management
Controller
Accounts, customers, vendors, employees and items.
Design to Build
Sales Rep
Service items, and the pricing strategy that charge based billing runs on.
Lead to Quote
Sales Rep
Recording and managing selling activities for new customers.
Project Management
Operations
The core delivery process area, and the one carrying the most configuration decisions that are hard to reverse.
Resource Management
Project Manager
Labor cost, allocation and utilization.
Order to Cash
Sales Rep
Transacting with the customer, delivering, billing and collecting.
Revenue Management
Controller
Recognition across both sales orders and projects, which in services frequently run together on the same engagement and recognize on different triggers.
Return to Credit
Accounts Receivable
Customer returns, credits and refunds.
Procure to Pay
Accounts Payable
Purchasing and vendor management.
Return to Debit
Accounts Payable
Returns of vendor goods and services, and the vendor credits and refunds that affect accounts payable.
Financial Management
Controller
Everything that ensures accurate financial reporting, and the area the edition notes directly impacts the success of every other process performed in the system.
1. Master Data Management
Accounts, customers, vendors, employees and items. In a services business the employee record is not administration, it is a costing record, and nothing downstream can recover a labor rate that was never entered.
Define accounts and segments → Create service items → Load customers and vendors → Set employee labor rates and targets → Validate
Leading practice rules
Master data must be maintained before process area transactions can be carried out.
Define a standard blended labor cost per job function and set it as the default on the employee record, rather than entering rates project by project.
Set the target utilization on the employee record, because the Available Hours column on utilization reports uses it.
Skill file: Master Data Management
---
name: services-master-data-management
description: NetSuite leading practice for Master Data Management in services
---
# Master Data Management - Services Companies
## Roles
Controller, Accounts Receivable, Accounts Payable, Operations
## Process flow
Define accounts and segments → Create service items → Load customers and vendors → Set employee labor rates and targets → Validate
## Leading practice rules
- Master data must be maintained before process area transactions can be carried out.
- Define a standard blended labor cost per job function and set it as the default on the employee record, rather than entering rates project by project.
- Set the target utilization on the employee record, because the Available Hours column on utilization reports uses it.
## Check before go-live
- [ ] A labor cost rate on every employee who will enter time, before time entry opens
- [ ] Target utilization set per employee, not assumed
## Known failure modes
- Time entered against an employee with no cost rate, which produces no cost at all, with no error and no warning
## Scope note
This reflects the Services Standard edition. Confirm against your own licensed
modules and edition before treating any rule as available.
2. Design to Build
Service items, and the pricing strategy that charge based billing runs on. The edition is direct that a clear strategy for creating service items is a prerequisite rather than a refinement.
Roles: Sales Rep, Controller, Operations
Process flow
Define the service catalog → Create service items → Set pricing → Map to billing rules → Release
Leading practice rules
Service item pricing is the basis for pricing services under charge based billing, so a strategy for creating service items must be clearly defined.
Item records reduce entry errors and make transaction processing more efficient, which matters most where the same service is sold repeatedly at different rates.
Skill file: Design to Build
---
name: services-design-to-build
description: NetSuite leading practice for Design to Build in services
---
# Design to Build - Services Companies
## Roles
Sales Rep, Controller, Operations
## Process flow
Define the service catalog → Create service items → Set pricing → Map to billing rules → Release
## Leading practice rules
- Service item pricing is the basis for pricing services under charge based billing, so a strategy for creating service items must be clearly defined.
- Item records reduce entry errors and make transaction processing more efficient, which matters most where the same service is sold repeatedly at different rates.
## Check before go-live
- [ ] Service item list agreed between sales, operations and finance before the first quote
## Known failure modes
- Service items created ad hoc per deal, so pricing cannot be compared across clients
## Scope note
This reflects the Services Standard edition. Confirm against your own licensed
modules and edition before treating any rule as available.
3. Lead to Quote
Recording and managing selling activities for new customers. In services the estimate is not a document, it is a simulation of the delivery, built as a project before the project exists.
Roles: Sales Rep, Operations, Project Manager
Process flow
Lead → Opportunity → Build scoping project → Refresh items from project → Quote
Leading practice rules
Where an opportunity needs scoping before a quote, create a project and build it out: populate the work breakdown structure, make resource task assignments using generic resources, and set project billing rules.
That structure yields the numbers the quote needs: hours required, expected timeline, and ultimately the cost to the customer.
Once the project is built out, use the Refresh Items from Project button to update the opportunity or estimate with the forecast charges generated from task assignments and billing rules.
Use generic resources rather than named people at this stage, so the estimate does not silently assume the availability of a specific person.
Skill file: Lead to Quote
---
name: services-lead-to-quote
description: NetSuite leading practice for Lead to Quote in services
---
# Lead to Quote - Services Companies
## Roles
Sales Rep, Operations, Project Manager
## Process flow
Lead → Opportunity → Build scoping project → Refresh items from project → Quote
## Leading practice rules
- Where an opportunity needs scoping before a quote, create a project and build it out: populate the work breakdown structure, make resource task assignments using generic resources, and set project billing rules.
- That structure yields the numbers the quote needs: hours required, expected timeline, and ultimately the cost to the customer.
- Once the project is built out, use the Refresh Items from Project button to update the opportunity or estimate with the forecast charges generated from task assignments and billing rules.
- Use generic resources rather than named people at this stage, so the estimate does not silently assume the availability of a specific person.
## Check before go-live
- [ ] A scoping project required for any opportunity above an agreed value threshold
- [ ] The scoping project retained as a baseline after the win rather than overwritten by the working plan
## Known failure modes
- Quoting from a spreadsheet, so there is no baseline to compare actual hours against once delivery starts
## Scope note
This reflects the Services Standard edition. Confirm against your own licensed
modules and edition before treating any rule as available.
4. Project Management
The core delivery process area, and the one carrying the most configuration decisions that are hard to reverse. Several of them look like preferences and behave like accounting policy.
Roles: Operations, Project Manager, Controller
Process flow
Create from template → Set up tasks and milestones → Configure time and expense controls → Allocate resources → Track progress → Close
Leading practice rules
Create new projects from a project template, which creates the tasks and milestones with estimated hours.
Limit project tasks to those required for reporting and billing. Think of them as phases such as design, configure and testing, because they are used for accounting controls and reporting rather than for detailed scheduling.
Check Limit Time and Expense to Resources to control who can enter time and expense to the project, and check Allow Time Entry and Allow Expenses to make the project available.
Percent complete is calculated using the Percent Complete Denominator, which can be planned time only, or planned and actual hours where actuals have overrun the plan. The two produce different answers on a late project.
Classify Time as Productive without Utilized for time that should count toward productivity but not utilization, such as pre-sales and training.
Leave both Classify Time as Utilized and Classify Time as Productive unchecked for administrative work and bench time.
Set minimum and maximum hours per week, per day and per entry, aligned to work calendars or separately, with different thresholds available for contractors.
When a project task is fully complete, update its status to completed manually to close it for time tracking.
Budget by Project and Activity Code only. Project Tasks are not available on invoices, revenue arrangements or journal entries, so budgeting at task level prevents actuals from matching.
Use one line per Activity Code in the budget. Repeating an Activity Code across rows leaves actuals unmatched, because the system cannot tell which row to match against.
Skill file: Project Management
---
name: services-project-management
description: NetSuite leading practice for Project Management in services
---
# Project Management - Services Companies
## Roles
Operations, Project Manager, Controller
## Process flow
Create from template → Set up tasks and milestones → Configure time and expense controls → Allocate resources → Track progress → Close
## Leading practice rules
- Create new projects from a project template, which creates the tasks and milestones with estimated hours.
- Limit project tasks to those required for reporting and billing. Think of them as phases such as design, configure and testing, because they are used for accounting controls and reporting rather than for detailed scheduling.
- Check Limit Time and Expense to Resources to control who can enter time and expense to the project, and check Allow Time Entry and Allow Expenses to make the project available.
- Percent complete is calculated using the Percent Complete Denominator, which can be planned time only, or planned and actual hours where actuals have overrun the plan. The two produce different answers on a late project.
- Classify Time as Productive without Utilized for time that should count toward productivity but not utilization, such as pre-sales and training.
- Leave both Classify Time as Utilized and Classify Time as Productive unchecked for administrative work and bench time.
- Set minimum and maximum hours per week, per day and per entry, aligned to work calendars or separately, with different thresholds available for contractors.
- When a project task is fully complete, update its status to completed manually to close it for time tracking.
- Budget by Project and Activity Code only. Project Tasks are not available on invoices, revenue arrangements or journal entries, so budgeting at task level prevents actuals from matching.
- Use one line per Activity Code in the budget. Repeating an Activity Code across rows leaves actuals unmatched, because the system cannot tell which row to match against.
## Check before go-live
- [ ] Percent Complete Denominator chosen deliberately and documented, not left at its default
- [ ] Time classification agreed for every project type, including internal and pre-sales projects
- [ ] Budget built at Project and Activity Code level with no repeated codes
## Known failure modes
- Too many project tasks, created for scheduling detail, which makes time entry slow and reporting noisy
- Bench time classified as utilized, which flatters utilization and hides the real capacity position
## Scope note
This reflects the Services Standard edition. Confirm against your own licensed
modules and edition before treating any rule as available.
5. Resource Management
Labor cost, allocation and utilization. This area decides whether project profitability is real or decorative, and it depends on one field being populated before anyone enters a timesheet.
Roles: Project Manager, Operations, Controller
Process flow
Set labor rates and targets → Allocate resources → Enter and approve time → Cost the time → Report utilization
Leading practice rules
Labor cost is the hourly cost from the employee record multiplied by hours worked. The rate can be overridden on the project task assignment record.
Job costing takes the cost from the employee record unless overridden on the project resource list or the project task assignment.
Ensure labor costs are entered on the employee before time entry, otherwise there will be no cost for labor.
Most services organizations do not post time to the general ledger, because payroll is journaled monthly and independently. Where that is the case, set the project profitability report preference to include approved time entries as actual costs, select a project expense type, and check apply to all time entries on the project record so approved time appears on the project P&L sublist.
Where time is posted to the general ledger, an adjustment journal is required so labor costs are not double counted against journaled salary.
Check Display all resources for project task assignment only where allocations are made by CSV import.
Use the utilization reports for project resources. The Available Hours column considers the target entered on the employee record.
Skill file: Resource Management
---
name: services-resource-management
description: NetSuite leading practice for Resource Management in services
---
# Resource Management - Services Companies
## Roles
Project Manager, Operations, Controller
## Process flow
Set labor rates and targets → Allocate resources → Enter and approve time → Cost the time → Report utilization
## Leading practice rules
- Labor cost is the hourly cost from the employee record multiplied by hours worked. The rate can be overridden on the project task assignment record.
- Job costing takes the cost from the employee record unless overridden on the project resource list or the project task assignment.
- Ensure labor costs are entered on the employee before time entry, otherwise there will be no cost for labor.
- Most services organizations do not post time to the general ledger, because payroll is journaled monthly and independently. Where that is the case, set the project profitability report preference to include approved time entries as actual costs, select a project expense type, and check apply to all time entries on the project record so approved time appears on the project P&L sublist.
- Where time is posted to the general ledger, an adjustment journal is required so labor costs are not double counted against journaled salary.
- Check Display all resources for project task assignment only where allocations are made by CSV import.
- Use the utilization reports for project resources. The Available Hours column considers the target entered on the employee record.
## Check before go-live
- [ ] A decision recorded on whether time posts to the general ledger, with the matching configuration applied
- [ ] Labor rates present on every employee before go-live, verified rather than assumed
## Known failure modes
- Posting time to the ledger alongside journaled payroll, with no adjustment journal, which double counts labor
- Project profitability reviewed while some resources carry no cost rate, so margin is overstated on their projects
## Scope note
This reflects the Services Standard edition. Confirm against your own licensed
modules and edition before treating any rule as available.
6. Order to Cash
Transacting with the customer, delivering, billing and collecting. The distinctive risk here is a missing link between two records that people reasonably assume are connected.
Charge based billing is encouraged for all project billing scenarios. It supports labor, expenses and fixed fees in one flexible engine.
Add one or more charge rules so the billing setup on the project matches the contract terms.
If you change the amount on the sales order you must also change it on the billing rule. There is no direct link between the two.
Once the customer signs the contract the sales order should not be altered, because it represents the agreed scope.
Skill file: Order to Cash
---
name: services-order-to-cash
description: NetSuite leading practice for Order to Cash in services
---
# Order to Cash - Services Companies
## Roles
Sales Rep, Accounts Receivable, Controller, Operations, Project Manager
## Process flow
Quote → Sales order → Deliver → Charge rules generate charges → Invoice → Collect
## Leading practice rules
- Charge based billing is encouraged for all project billing scenarios. It supports labor, expenses and fixed fees in one flexible engine.
- Add one or more charge rules so the billing setup on the project matches the contract terms.
- If you change the amount on the sales order you must also change it on the billing rule. There is no direct link between the two.
- Once the customer signs the contract the sales order should not be altered, because it represents the agreed scope.
## Check before go-live
- [ ] Charge rules reconciled against the signed contract for every project before the first invoice
- [ ] A control in place so sales order amendments trigger a billing rule review
## Known failure modes
- Amending a sales order and assuming the billing rule follows, which it does not, so the client is billed the old amount
## Scope note
This reflects the Services Standard edition. Confirm against your own licensed
modules and edition before treating any rule as available.
7. Revenue Management
Recognition across both sales orders and projects, which in services frequently run together on the same engagement and recognize on different triggers.
Revenue arrangement → Revenue plan → Recognize by period → Reconcile deferred revenue → Report
Leading practice rules
Revenue recognition applies to both sales orders and projects, and the two are configured separately.
Operations carries responsibility for billing rule maintenance, revenue arrangements and deferred revenue reconciliation, so this is not a finance-only area.
Reconcile deferred revenue on a cycle rather than at audit, because in services it accumulates from several sources at once.
Skill file: Revenue Management
---
name: services-revenue-management
description: NetSuite leading practice for Revenue Management in services
---
# Revenue Management - Services Companies
## Roles
Controller, Operations, Accounts Receivable
## Process flow
Revenue arrangement → Revenue plan → Recognize by period → Reconcile deferred revenue → Report
## Leading practice rules
- Revenue recognition applies to both sales orders and projects, and the two are configured separately.
- Operations carries responsibility for billing rule maintenance, revenue arrangements and deferred revenue reconciliation, so this is not a finance-only area.
- Reconcile deferred revenue on a cycle rather than at audit, because in services it accumulates from several sources at once.
## Check before go-live
- [ ] Recognition treatment agreed per engagement type, including where a fixed fee and time and materials sit on one contract
- [ ] Deferred revenue reconciliation owned by a named person with a cadence
## Known failure modes
- Recognition designed for the sales order and left undesigned for the project, or the reverse
## Scope note
This reflects the Services Standard edition. Confirm against your own licensed
modules and edition before treating any rule as available.
8. Return to Credit
Customer returns, credits and refunds. In services the credit usually corrects a billing disagreement rather than a returned good, which means it touches the charge that produced it.
Create the credit from the originating transaction so it reconciles back to the charge and the project it came from.
Where a credit corrects a billed charge, check whether the underlying charge rule also needs changing, or the same error recurs next cycle.
Skill file: Return to Credit
---
name: services-return-to-credit
description: NetSuite leading practice for Return to Credit in services
---
# Return to Credit - Services Companies
## Roles
Accounts Receivable, Controller, Project Manager
## Process flow
Credit request → Authorization → Approve → Credit memo → Apply or refund
## Leading practice rules
- Create the credit from the originating transaction so it reconciles back to the charge and the project it came from.
- Where a credit corrects a billed charge, check whether the underlying charge rule also needs changing, or the same error recurs next cycle.
## Check before go-live
- [ ] Credit approval thresholds agreed and configured
## Known failure modes
- Crediting the invoice and leaving the charge rule unchanged, so the error repeats on the next billing run
## Scope note
This reflects the Services Standard edition. Confirm against your own licensed
modules and edition before treating any rule as available.
9. Procure to Pay
Purchasing and vendor management. In services this is weighted toward subcontractors, software and travel rather than stock.
Roles: Accounts Payable, Controller
Process flow
Requisition → Purchase order → Receive or approve → Vendor bill → Pay
Leading practice rules
Where a subcontractor works on a client project, ensure the cost lands on the project rather than in general overhead.
Use amortization schedules for costs paid in advance so they are recognized in the period they belong to.
Electronic bank payments generate payment files for import to the bank. Mark the vendor with EFT Bill Payment and set up their bank details, and bill payments for that vendor are flagged for the file generation queue automatically.
Skill file: Procure to Pay
---
name: services-procure-to-pay
description: NetSuite leading practice for Procure to Pay in services
---
# Procure to Pay - Services Companies
## Roles
Accounts Payable, Controller
## Process flow
Requisition → Purchase order → Receive or approve → Vendor bill → Pay
## Leading practice rules
- Where a subcontractor works on a client project, ensure the cost lands on the project rather than in general overhead.
- Use amortization schedules for costs paid in advance so they are recognized in the period they belong to.
- Electronic bank payments generate payment files for import to the bank. Mark the vendor with EFT Bill Payment and set up their bank details, and bill payments for that vendor are flagged for the file generation queue automatically.
## Check before go-live
- [ ] Subcontractor costs routed to projects, verified on a live engagement before go-live
## Known failure modes
- Subcontractor cost sitting in overhead, so the project shows a margin it did not earn
## Scope note
This reflects the Services Standard edition. Confirm against your own licensed
modules and edition before treating any rule as available.
10. Return to Debit
Returns of vendor goods and services, and the vendor credits and refunds that affect accounts payable. Low volume in services and correspondingly easy to leave uncontrolled.
Roles: Accounts Payable, Controller
Process flow
Identify overcharge or cancellation → Vendor credit request → Approval → Vendor credit → Apply to payable
Leading practice rules
Raise vendor credits from the originating purchase transaction so the payable reconciles.
Where the original cost was charged to a project, ensure the credit reverses against the same project rather than against overhead.
Skill file: Return to Debit
---
name: services-return-to-debit
description: NetSuite leading practice for Return to Debit in services
---
# Return to Debit - Services Companies
## Roles
Accounts Payable, Controller
## Process flow
Identify overcharge or cancellation → Vendor credit request → Approval → Vendor credit → Apply to payable
## Leading practice rules
- Raise vendor credits from the originating purchase transaction so the payable reconciles.
- Where the original cost was charged to a project, ensure the credit reverses against the same project rather than against overhead.
## Check before go-live
- [ ] Open vendor credits reviewed within the close
## Known failure modes
- A vendor credit applied to overhead when the original cost was charged to a project, which quietly improves that project's margin
## Scope note
This reflects the Services Standard edition. Confirm against your own licensed
modules and edition before treating any rule as available.
11. Financial Management
Everything that ensures accurate financial reporting, and the area the edition notes directly impacts the success of every other process performed in the system.
Maintain accounts and segments → Post journals and allocations → Amortize → Reconcile → Close period → Report
Leading practice rules
Use allocation schedules to distribute expenses across subsidiaries, departments, locations and classes rather than entering complex journals by hand.
Use amortization schedules where cost is paid in advance, posting to a deferred expense account and recognizing in the correct period.
The A/R and A/P analyst roles support the controller on tax reports, chart of accounts maintenance, allocation and amortization schedules, journals, banking operations and period close.
Skill file: Financial Management
---
name: services-financial-management
description: NetSuite leading practice for Financial Management in services
---
# Financial Management - Services Companies
## Roles
Controller, Accounts Receivable, Accounts Payable
## Process flow
Maintain accounts and segments → Post journals and allocations → Amortize → Reconcile → Close period → Report
## Leading practice rules
- Use allocation schedules to distribute expenses across subsidiaries, departments, locations and classes rather than entering complex journals by hand.
- Use amortization schedules where cost is paid in advance, posting to a deferred expense account and recognizing in the correct period.
- The A/R and A/P analyst roles support the controller on tax reports, chart of accounts maintenance, allocation and amortization schedules, journals, banking operations and period close.
## Check before go-live
- [ ] Allocation and amortization schedules created with dashboard reminders enabled
## Known failure modes
- Recurring journals entered manually each period, which is slow and the most common source of close errors
## Scope note
This reflects the Services Standard edition. Confirm against your own licensed
modules and edition before treating any rule as available.
Where to Start
Master data first, then design to build, because the service item strategy underpins charge based billing and everything priced against it. Project management and resource management next, and design them together, because a project cannot cost anything until labor rates exist on the employee record. Revenue management follows. The two return processes, procure to pay and financial management run alongside rather than in sequence.
The single highest-value check across all of them: confirm labor cost rates exist on every employee record before time entry opens. Time entered against an employee with no cost rate produces no cost, silently, with no error, and every project shows an excellent margin until someone checks.
Published by Azdan, an Oracle NetSuite Solution Provider operating across the UAE, Saudi Arabia, and Egypt. Guidance in this article reflects Azdan's process design work with services businesses. Content checked August 2026.
Blog
News & Insights
Fresh thinking and real-world advice to help you scale smarter, faster, and with more clarity
.svg)
