COAM\ Penalty - Obligation must be paid before penalties can be paid

[NicoleGovvy]

Description:

Operators must pay their obligation in full before they can submit a payment notification for a missed compliance deadline or an additional compliance obligation penalty.

Acceptance Criteria:

As an operator, given that I have penalties accruing, when I pay my outstanding obligation amount, then I will see the total amount of my penalties and I am able to pay them.

• [ ] Outstanding obligations must be paid for late payment and additional compliance obligation penalties before the total penalty can be calculated and displayed
• [ ] Outstanding obligations must be paid before a payment notification for the penalties can be submitted.
• [ ] This does not apply to imposed penalties

Given When Then

Development Checklist:

• [ ] Checklist item
• [ ] Checklist item
• [ ] Checklist item
• [ ] Meets the DOD

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

• [ ] User story is included
• [ ] User role and type are identified
• [ ] Acceptance criteria are included
• [ ] Wireframes are included (if required)
• [ ] Design / Solution is accepted by Product Owner
• [ ] Dependencies are identified (technical, business, regulatory/policy)
• [ ] Story has been estimated (under 13 pts)

Definition of Done (Note: If any of these points are not applicable, mark N/A)

• [ ] Acceptance criteria are tested by the CI pipeline
• [ ] UI meets accessibility requirements
• [ ] Configuration changes are documented, documentation and designs are updated
• [ ] Passes code peer-review
• [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
• [ ] Ticket is ready to be merged to main branch
• [ ] Can be demoed in Sprint Review
• [ ] Bugs or future work cards are identified and created
• [ ] Reviewed and approved by Product Owner

Blocked By/Blocking

Notes: