Straight into the service manual page
WrenchQuarry
More

2 discount entitlements: 10% off or 100% free work orders

WrenchQuarry Editorial Team · Published · 11 min read · How these guides are written

Two promises that look alike

A percentage discount keeps a lower price on covered work, while a 100% discount makes covered work free for the agreement's length. Owners and dispatchers often hear "discount" and "free" as the same kind of thing, but they are not the same promise. Each one changes the invoice in a different way, so each one should be set up as its own discount entitlement.

Microsoft's guidance for Dynamics 365 Field Service lays out the two cases as separate scenarios. In the first, an organization wants to offer a customer a 10% discount for two years on all work order products and services based on a preset price list. In the second, an organization wants to offer a customer free work order products and services for two years for work orders that relate to customer assets of a specified category.

Those two scenarios frame the rest of this post. The advice below is general, but it follows the structure Microsoft describes.

Start with the percentage discount

The percentage version is the easier one to explain to a customer. The entitlement takes a rate and applies it to the work order, and the customer still sees a price. For the shop, that keeps the normal billing path in place with a lower number at the bottom.

Microsoft describes entitlements for work orders as a way to dynamically apply price lists and discounts to work order products and services based on work order attributes and date range factors. Read that sentence twice before you build anything. The discount is driven by two things: the attributes on the work order and the date range on the entitlement. If either one is set loosely, the discount will show up on work you did not mean to cover, or it will be missing from work you did.

Write the date range down in the agreement too. Owners and dispatchers should be able to say, in plain words, which work orders get the discount and during which dates. If nobody can state those two things without opening the system, the setup is not ready for a customer.

The term is part of the promise too. Microsoft's first scenario describes the discount running for two years, and its second describes free work running for two years. Those are examples, not a required length. Pick the term that matches the signed agreement, then confirm that the entitlement's dates start and end on exactly those days. An end date that is off by a few days causes confusion at renewal, and it is easy to avoid by checking the dates against the signed copy.

Price lists come first

The discount scenario depends on a price list. Microsoft is direct about this: for this scenario, you must have a price list with associated products. A percentage off nothing is still nothing, so the price list needs to exist and it needs to contain what the shop actually sells under the agreement.

The same page says to add the products and services as price list items with the related prices. Services count as well as parts. A maintenance agreement that covers an inspection, a filter change, and a fluid service should have each of those on the price list, not only the parts that go with them. A service left off the list has no related price on the list.

This is also the step most likely to be skipped. Someone sets the entitlement, runs a test work order, sees no discount, and assumes the entitlement is broken. Often the price list is the missing piece. Check it first, because it takes less time than rebuilding a working entitlement.

Prices also move. A price list that was correct when the agreement was signed can be out of date months later, and the discount is only as good as the prices it works from. Review the price list on a schedule the shop can keep, and note in the agreement that the list is the reference for covered work. That keeps an owner from asking why an old price is still on the invoice, or why the discount seems to have shifted. For the billing side of recurring agreements, see maintenance plan billing settings.

Split rates need two entitlements

Some agreements give one rate for parts and a different rate for labor. Microsoft covers this case directly: for a different scenario where you want to apply a 10% discount on products and a 20% discount on services, create two entitlements.

Keep that rule in mind when someone asks for a split. A single entitlement applies one rate across the scope it covers. If the customer is promised 10% on parts and 20% on services, that is two entitlements, each with its own rate. Trying to fit both rates into one entitlement is a fast way to end up with a wrong invoice, and a wrong invoice is harder to explain than a slightly longer setup.

The split also makes the agreement easier to read. Owners can see at a glance which rate goes with parts and which goes with service.

Think about the split from the customer's side too. A customer who reads a 10% line next to a 20% line will ask why the rates differ, so have the reason ready. The reason is a business choice, not a system setting. Write it into the agreement in a sentence so the answer does not depend on who happens to be on the phone that day.

Free work means a 100% discount

For the free-work case, the setting is a 100% discount. Microsoft's guidance is to create an entitlement with the % Discount set to 100% to make the work order products and services free when the entitlement is applied. The same page shows the result in its example: the 100% discount is applied, rendering the work order products as free.

Treat that setting as a promise, not a convenience. A 10% discount applied by mistake costs the shop a little margin on one job. A 100% discount applied to the wrong work order gives away the whole job. That difference is the reason to build the free-work entitlement more carefully than the percentage one, with a second pair of eyes on the scope before it goes live.

Before the shop agrees to free work, ask what the covered equipment costs to service over the term. That is a business question, and the answer belongs with the owner, not only the dispatcher. Free work that looks small on one job can add up across a whole fleet, so look at the full list of covered units before anyone signs.

Naming matters here as well. An entitlement called "Discount 2" tells nobody what it does, while a name that says what is covered and what is free can be read by an owner, a dispatcher, and a bookkeeper without opening the record. This is general good practice, and it saves time every time someone asks what an entitlement is for.

Scope free work to an asset category

Microsoft's second scenario ties free work to work orders that relate to customer assets of a specified category. That scope is the most important part of the setup.

Pick the asset category before you pick anything else in the free-work entitlement. Ask the owner which equipment is in the agreement, and get that list in writing. Then set the category on the entitlement to match the list. If the category is too broad, free work spreads to equipment nobody priced in. If it is too narrow, the customer calls to ask why a covered unit is being billed, and the shop has to explain a gap in its own setup.

Dispatchers should look at the asset on each work order before the job is dispatched, not only after invoicing. The asset is what decides whether the free-work entitlement belongs on the job. Catching a mismatch at dispatch is far cheaper than issuing a credit after the customer has already paid. For the handoff steps, see the field service work order checklist.

Asset records need to be clean for the scope to work. If the same unit is entered twice, or its category is missing, the free entitlement may not match the work order it should. Before the agreement starts, walk through the asset list with whoever keeps those records and fix the gaps. That is a small job at the start and a painful one in the middle of a dispute.

Keep the two entitlements from overlapping

A customer can end up with both kinds of agreement, or with a percentage entitlement and a free entitlement that both seem to match the same work order. Check how the system chooses between two matching entitlements before assuming an answer. Test it.

Set up one work order that should match only the percentage entitlement. Then set up one that should match only the free entitlement. Then create a work order that falls into both and see what the result is. If the answer is not what the agreement says, fix the scope before the customer sees an invoice. A scope change is quick to make on a test record and slow to unwind on a real one.

Write the overlap rule into the agreement too, so a dispatcher is not guessing at the desk. Sample wording might read: covered units on the listed equipment are free for covered work, and all other eligible work receives the stated discount. That is an example to adapt, not standard language, and it should be checked with whoever handles contracts for the shop.

Test with a real work order first

Testing is cheap and quick. Create a test work order with the right customer, the right asset, and a date inside the entitlement's range. Confirm three things: the entitlement applies, the discount rate is the one you intended, and the price list lines show the amounts you expect.

For a free entitlement, the expected result is zero on each covered line, as in Microsoft's example. If a product line still shows a charge, do not start by rebuilding the entitlement. Work through the scope, then the price list, then the entitlement settings, in that order. Rebuilding first often hides the real cause.

Run one test for each kind of covered line on the agreement. A parts line, a service line, and a line for equipment outside the agreement will tell you more than three parts lines would. The outside-the-agreement line matters most, because it shows whether the scope is holding.

Keep a short record of each test: the work order number, the entitlement tested, and the result you saw. When something changes later, that record shows what the setup did when it was last checked. It also gives the owner something concrete to review, rather than a general sense that the setup is right.

Write the agreement to match the system

The agreement and the system need to say the same thing. An owner who signs for "10% off covered work" and a system set to 10% on products only has a dispute waiting to happen. Read the entitlement back against the agreement before it goes live, line by line, with the owner or the person who signed for the customer if possible. Make sure that person understands what the system will do, not only what the contract says. A short walkthrough with one sample invoice is a practical way to do that.

For percentage agreements, state the rate, what it applies to (parts, services, or both), and the date range. For free-work agreements, state the asset category and the term. Your agreement can use any term you and the customer agree on, as long as the entitlement's dates match it exactly. For limits to set on a recurring discount, see limits on a recurring maintenance plan discount.

Keep the agreement and the entitlement in the same folder, with the same version date on both. When an owner asks six months later what they signed, the answer should take a minute, not an afternoon of searching records.

Handle changes in the middle of a term

Agreements change. A customer adds a unit, drops a service, or moves from a percentage to a free arrangement on one piece of equipment. Each change touches an entitlement, and each one raises the same question: does it apply to work already done?

Decide before editing anything whether a change should apply to open work orders only or to completed work, and test how the system handles that change before relying on it. Mixing the two without a note is how invoices get disputed. Write down the cutoff date for each change and tell the owner what it is.

Dispatchers should be told about changes the same day they are made. A dispatcher who books a job with the old setup in mind will be surprised by the new invoice, and that surprise lands on the customer relationship, not on the system.

Two promises, kept separate

The percentage discount and the free-work entitlement solve different problems. One gives the customer a lower price on a wider scope. The other gives the customer no charge on a narrow, named scope. Setting them up as two entitlements keeps each promise clear, and it keeps the invoice easy to read.

Build the price list first, since the percentage version depends on it. Scope the free version to a named asset category, since that scope is where most of the risk sits. Test each entitlement on a real work order, including one that should fall outside the agreement. Then match the agreement wording to what the system does, and write down how changes are handled.

Done that way, a 10% discount and a 100% discount can live on the same customer without confusing anyone who has to read the bill.

Sources

More field guides