When quoting a PHEV, the Date First Held field stays greyed out and can't be edited. This holds even after the quote is set up to meet the conditions that should make the field relevant — Used/Demonstrator, EV Exempt Reportable ticked, LCT set to 0.00.
The practical impact is on existing client vehicles. Budget adjustments on a vehicle already held need the actual date first held, and there's currently no way to enter it at the quoting stage. Users are stuck.
Why the field matters here
For PHEVs, date first held isn't cosmetic. The PHEV FBT exemption ended for new arrangements from 1 April 2025, with transitional treatment depending on when the vehicle was first held and whether a binding commitment existed before that date. So the date drives whether the exemption applies at all. Anything we do here needs to keep that logic correct, not just make the field typeable.
Objective
Allow Date First Held to be entered at the quoting stage for PHEVs where the vehicle is already held, without weakening the FBT logic that depends on it.”
In scope
Unlocking Date First Held in quoting for PHEV vehicles that meet the relevant conditions
Feeding the entered date into FBT exemption determination and budget calculations
Whatever validation is needed to stop the field being misused
Out of scope
Changing FBT exemption rules themselves
Behaviour for BEVs or ICE vehicles, unless the fix turns out to be shared logic
Post-quote stages where the field is already editable
Functional requirements
Find out why it's locked. First step is establishing what currently drives the lock: fuel type, new vs used, quote stage, EV exemption flag, or a combination. The user has already tried the obvious levers without success, which suggests the condition is either stricter than expected or the field is simply disabled at quote stage regardless. That answer shapes the fix.
Unlock condition. Once known, define the specific condition under which the field becomes editable. The likely shape: PHEV, Used/Demonstrator, and an existing vehicle rather than a new acquisition. Needs to be tight enough that it can't be used to backdate a new PHEV into an exemption it isn't entitled to.
Validation. Date entered can't be in the future. It should sit sensibly against the vehicle's build or compliance date and the contract start. Where the date implies FBT-exempt treatment, the system should apply the relevant checks rather than taking the date on trust.
Downstream effect. The entered date flows through to FBT exemption determination, the budget calculation, and anything on the quote that displays exemption status. Changing the date recalculates the quote.
Permissions. If this field can shift a vehicle into or out of FBT exemption, restricting who can set it is worth considering.
Validation and audit
Standard Catch-e confirmation prompts on save
Date First Held changes at quote stage are audited: who, when, old value, new value
Where the date drives an exemption outcome, that outcome is recorded against the quote so it can be evidenced later
Acceptance criteria
A user quoting a PHEV on an existing client vehicle can enter Date First Held
Entering the date updates the FBT treatment and budget figures on the quote
The field stays locked in scenarios where it shouldn't be editable
Invalid dates are rejected with a clear message
The change is audited
No change to BEV or ICE quoting behaviour