How Fuel Levies Are Applied

1. Manual Job Bracket (Highest Priority)

If a fuel levy bracket has been manually selected for a job:

• This may have been set during initial booking or at any later stage when the job was edited
• Once a user manually selects a fuel bracket, that selection becomes fixed
• The system will always use this manually selected bracket going forward
• No further automatic rate evaluation or recalculation will occur, regardless of any later changes to fuel rates or system rules

✅ Outcome:
A manually selected fuel bracket overrides all other logic and persists, even if it was applied previously and not as part of the current update.

2. System Selection Order (If No Manual Bracket)

If no bracket is manually applied, the system evaluates fuel levies in the following priority order and stops at the first valid match.

Priority 1: Customer + Exact Service Type

• Matches the job’s customer (entity)
• Matches the exact service type

Priority 2: Customer + Any Service Type

• Matches the job’s customer
• Applies to all service types (no restriction)

Priority 3: Division Rate + Exact Service Type

• Applies at the division level
• Matches the exact service type

Priority 4: Division Rate + Any Service Type

• Applies at the division level
• Applies to all service types

Priority 5: No Service Type Match (Fallback)

• Used only if no other rule matches
• Service type is not matched or not defined

✅ Outcome:
The system always selects the first valid match in this order

3. Rate Selection Within Each Level

For each priority level above, the system applies the following logic:

1. Ranged Rates (Preferred)
   • The system checks if the job falls within a defined bracket range
   • If valid, this rate is selected
2. Constant Rates (Fallback)
   • If no ranged rate applies
   • The system selects the first available constant rate

✅ Outcome:
Ranged rates take precedence over constant rates at every level

4. No Matching Rate Found

If no rate meets any criteria:

• No fuel levy is applied to the job

✅ Outcome:
The system returns no levy when no suitable match exists

Key Takeaways

• Manual selections always override system logic
• The system evaluates rates from most specific → least specific
• Customer-specific rates take priority over division-level rates
• Ranged rates are preferred over constant rates
• If nothing matches, no fuel levy is applied