IFS FSM 6 (Field Service Management) · FSM9

Pricing, Billing and Revenue

6
Processes
214
Details worked out
45
Execution steps
6
Diagrams
FSM9.01

Price Model, Entitlement and Benefit Plan Setup

Defining what things cost and what a customer gets for free. FSM 6 prices through a layered structure of price models, part and non part entitlements, benefit plans and special charges, resolved against the contract in force.

IFS FSM 6 Pricing
38 details
diagram
FSM9.02

Request Line and Usage Repricing

Putting a price on what was actually used, and putting it right when something changes. FSM 6 delivers six repricing rules covering request lines, part usage, part needs, non part usage, non part needs and quotes.

IFS FSM 6 Pricing, repricing rules
33 details
diagram
FSM9.03

Voucher Generation, Grouping and Filtering

Turning completed work into billable documents. FSM 6 collects chargeable usage into vouchers, groups them by rule, and filters out what should not be billed yet.

IFS FSM 6 Billing
38 details
diagram
FSM9.04

Invoice Generation, Distribution and Dispute

Producing the document the customer pays against, sending it, and handling what comes back. FSM 6 builds invoices from voucher detail with meter reading and price detail where relevant.

IFS FSM 6 Billing, Invoice screen
36 details
diagram
FSM9.05

Payment Capture and Settlement

Taking money and matching it to what is owed. FSM 6 records payments against invoices, including payments taken on site by a technician.

IFS FSM 6 Payments
33 details
diagram
FSM9.06

Configurable Financials and Account Determination

Extending how FSM decides charge, cost and general ledger treatment without writing code. Configurable financials is a meta rule framework, and it is both the most powerful and the most opaque part of FSM 6 configuration.

IFS FSM 6 Pricing, configurable financials
36 details
diagram
What a license opens

Everything you can see here is real and current, the names, the structure and the counts come straight out of the ModelIFS library and change as it grows. What sits behind the license is the worked-out content itself: the execution steps, the data each one needs, the configuration decisions, the KPIs, the integration points, the workshop questions and the diagrams. That is the part you would otherwise spend a program building from nothing.

Sign in to open it