When a dispute is past chargeback deadline date it should be routed to process liability.  This should also apply for disputes autopaid that are pursuing recovery.

1. Create a claim on a dispute which has indeterminate recovery rights outcome but past the chargeback deadline.  The dispute is routed to process liability.

Resolved a issue where past chargeback deadline items were routing to review.

After a repre response is accepted, denying for merchant credit errors out on transaction selection with the message "This credit has been applied to this dispute"

1. ValPartialMerchCreditNotAccepted validates that a merchant credit was selected. **

Resolved an issue where when a Mastercard claim received a representment response and it was accepted by the user and they chose to deny the claim for a deny reason Merchant Credit an error message was displayed "This credit has been applied to this dispute". This fix ensures that when a representment response was received and the user is selecting to fully accept the response and deny for merchant credit, the credits must be equal to or greater than the remaining recovery amount. If a user selects a credit less than the remaining recovery amount a message will display to the user to go back and partially accept the representment response with a merchant credit. Additionally, validation exists to ensure that if a credit is selected that is greater that or equal to the remixing recovery amount and the user attempts to select another credit a message will display "The dispute already ahs fully applied merchant credits.'

After a repre response is accepted, denying for merchant credit errors out on transaction selection with the message "This credit has been applied to this dispute"

1. After a repre response is accepted, denying for merchant credit does not error out with the message "This credit has been applied to this dispute"
2. The validation will not allow you to move forward until you have selected credits equal to or greater than the remaining recovery amount plus ChargebackFXLossAmount Amount and less ChargebackFXGainAmount Amount
3. If you selected Merch creditsequal to or greater than the remaining recovery amount plus ChargebackFXLossAmount Amount and less ChargebackFXGainAmount Amount, and you select another merchant credit, you will see the message "This dispute already has fully applied merchant credit(s)."
4. The validation is present at both review representment assignments in the  MCReviewRepresentment flow (before and after PreArbitrationAttemptDeadlineDateTime expires)
5. Multiple merchant credits applied across the same dispute work
6. multiple merchant credits applied across multiple disputes on the same claim work
7. bulk processing of representment recieved works
8. Agent processing of Merchant credit works
9. Deny works for a user for merchant issued credit
10. Deny works for a user on non merchant issued credit
11. Deny works when the system kicks off deny debit date automation
12. Any other MIC regression scenarios

Resolved an issue where when a Mastercard claim received a representment response and it was accepted by the user and they chose to deny the claim for a deny reason Merchant Credit an error message was displayed "This credit has been applied to this dispute". This fix ensures that when a representment response was received and the user is selecting to fully accept the response and deny for merchant credit, the credits must be equal to or greater than the remaining recovery amount. If a user selects a credit less than the remaining recovery amount a message will display to the user to go back and partially accept the representment response with a merchant credit. Additionally, validation exists to ensure that if a credit is selected that is greater that or equal to the remixing recovery amount and the user attempts to select another credit a message will display "The dispute already ahs fully applied merchant credits.'

As a users, I should be able to update the extend the deny debit date to past the current date on an autopaid claim when a withdrawal or merchant credit has been found.

1. When a regulatory claim has been autopaid and merchant credit is identified users have the ability to update the deny debit date to same day+.
2. (regression) When a regulatory claim has been autopaid and a withdrawal request was received users have the ability to update the deny debit date to same day+.
3. When a group of disputes receives a Final Credit on the Provisional Credit Assignment, when the user decides to Do Not Pursue Recovery from Disposition, the Deny Debit date should be available.

Resolved an issue where when a regulatory claim was auto-paid and a merchant credit or withdrawal request was received users were unable to update the deny debit date. This fix ensures that when a claim was auto-paid and a merchant credit or withdrawal request was processed users have the ability to update the deny debit date to todays date or extend beyond todays date. 

Issue: After auto-accounting is successfully performed, the ExecutedOn value is not being persisted to the object. 

1. When automatic accounting is successfully performed the Execute on date is persisted to the object.  
   1. This should be true when processing an individual accounting manually
   2. This should be true when processing multiple accounting entries on the same work object manually
   3. This should be true when the system processes the accounting

Resolved an issue where after auto-accounting was successfully performed, the ExecutedOn value was not being persisted to the object. This fix ensures that the Execute on date is persisted to the object when accounting is performed systematically or manually.

As a system, the data page for Recent Attachments is currently read-only and does not allow for users to delete attachments. 

1. Data page for Recent Attachments is not read-only.
2. User is able to attach documents.
3. Users can refresh the page.
4. Users can delete attachments. 
5. Only Fulfilment users have the ability to attach/refresh/delete attachments
6. (Regression) Intake Users/External Client Users data page is read only.

Updated data page to ensure fulfillment users can delete attachments. Intake and External Client Users will continue to have the ability to upload documents to the claim.