Skip to content

Create a service

Creating a service records its identity and unlocks the cost-component sections where you build up its true delivery cost. Once a service exists, sales can quote it just like a product.

  1. Open Service and click New service.
  2. Fill in the details:
    • Name (required)
    • Description, service unit and service cost
    • Default unit of measure (chosen from your UOM master)
    • Service type and HSN/SAC code (validated against the GST master)
    • Category, delivery mode (field, in-house or remote), billing unit, default duration and default rate
  3. Click Save.

The service is created and you are taken to its record, where the cost-component sections become editable. Creating a service needs service-create permission, a user without it is not allowed to create one. Every creation is recorded in the audit log with its key fields.

  • Saving without a Name shows “Name is required” and nothing is saved.
  • Service cost and other numeric fields reject non-numeric or negative values.
  • The service code must be unique within your organisation.
  • The HSN/SAC code must exist in the GST master, or it is rejected.

The delivery mode you choose decides which cost sections are switched on by default:

  • Field delivery turns on travel and accommodation.
  • In-house delivery turns on timesheet and resource costs.

You can always turn other sections on or off afterwards.

Some service work is outsourced or sub-contracted. The vendor price list lets you record vendor-specific rates; the sub-service flag lets a service be referenced under a parent.

  1. On the service record, switch on Vendor price list.
  2. Add a rate line: choose a vendor (only your organisation’s active vendors appear), then enter description, quantity and unit cost. The line total is calculated for you.
  3. Save. When you reopen the service, the vendor rate is still there.

Vendor pricing rolls into the service’s cost summary, and every rate-line change is recorded in the audit log.

  1. Switch on Sub service on the service record.
  2. Save. The service is now flagged so it can be referenced under a parent service.

In this version, sub-service references are one level deep; nested roll-ups come later.