FFA

Description

Userstory: https://gitlab.maccs.mu/rnd/ffa/ffa-fe/-/issues/233

As a user, I want to cancel a payment that I made, so that I can stop the transaction if I no longer wish to proceed with the payment.

Acceptance Criteria:

1. Add a cancel payment button , the user should have an option to cancel a payment before it is fully processed.
2. The user should receive a confirmation prompt before proceeding with the the payment cancellation.
3. The payment status should be updated to “Canceled” on the Retrieve invoice payment page.

Points To be discussed

• The user should be informed of any potential consequences or fees associated with canceling the payment.
• If the payment is successfully canceled, the customer should receive a notification informing payment cancelled successfully.

Title: Enable users to cancel payments and handle associated actions like issuing credit notes and refunds within the system.

As a user
I want to be able to cancel payments that have been erroneously made or need to be voided or are linked to bounced cheques or have been overbilled
So that I can correct any mistakes and ensure accurate financial records, issue credit notes, and process refunds if necessary.

Acceptance Criteria:

1. Cancel Payment Action:
   • The system must provide an option to cancel a payment from the payment details page screen.
   • Only authorized users (such as managers) should be able to perform the cancellation action.
2. Confirmation Prompt:
   • When selecting "Cancel Payment," a confirmation prompt must appear to ensure the user understands that:
     • This action is irreversible.
     • A new receipt will need to be issued after cancellation.
   • The prompt should include a field for entering a reason for the cancellation, which must be mandatory.
3. Cancellation Status Update:
   • Once confirmed, the payment status will be updated to “Cancelled” in the system.
   • The payment should no longer be considered active and should not be included in any financial reports or balance calculations.
4. Audit Trail:
   • The system should keep a detailed log of the cancellation event, including:
     • User who cancelled the payment.
     • Time and date of cancellation.
     • Reason for cancellation.
   • This information should be available for review in the system audit logs.
5. Impact on Related Transactions:
   • If the cancelled payment is linked to an invoice, the system should automatically update the status of that invoice to reflect the payment cancellation.
   • The system should prompt users to take further action, such as initiating a refund, if necessary. E.g. If a credit note is issued, a refund request should be automatically generated and sent to the accounting department for further processing.
6. Notifications:
   • After cancellation, notifications should be sent to relevant stakeholders (e.g., the finance team, client, or vendor) to inform them of the payment cancellation and if any refund request is needed.
   • The notification should include the payment details, cancellation reason, and next steps, if applicable.
7. Reversal of Financial Impact:
   • The system should automatically reverse any financial impact the payment had (e.g., (e.g., recalculating available balance, reversing the transaction).

Dependencies:

• Role-based access control to ensure only authorized users can cancel payments, issue credit notes, and process refunds.