Context
Follow-up from #189.
LITEFile already calculates filing fees on the Payment step and persists the quoted total/breakdown for Review. However, edits made after a quote is stored can change the applicable fees without automatically invalidating that saved quote.
For example, changing court/case classification, filing/document types, or optional services can affect the fee. The current optional-services E2E flow explicitly revisits Payment to obtain a new quote after removing an optional service.
Goal
Ensure a filer never sees or submits against a stale fee quote after changing filing data that can affect the fee.
Acceptance criteria
- Invalidate any stored fee quote when fee-affecting filing data changes.
- Fee-affecting changes include, at minimum:
- court;
- case category/type;
- filing/document types;
- fee-bearing optional services;
- any other payload fields known to affect EFSP fee calculation.
- Before final submission, obtain a fresh fee quote if the existing quote is missing or stale.
- Review must not display a stale total/breakdown as if it were current.
- If recalculation fails or the fee cannot be determined, explain that clearly and prevent submission where appropriate.
- Add regression coverage showing that changing a fee-bearing optional service invalidates/recalculates the quote without relying on the filer to manually revisit Payment.
Related
Context
Follow-up from #189.
LITEFile already calculates filing fees on the Payment step and persists the quoted total/breakdown for Review. However, edits made after a quote is stored can change the applicable fees without automatically invalidating that saved quote.
For example, changing court/case classification, filing/document types, or optional services can affect the fee. The current optional-services E2E flow explicitly revisits Payment to obtain a new quote after removing an optional service.
Goal
Ensure a filer never sees or submits against a stale fee quote after changing filing data that can affect the fee.
Acceptance criteria
Related