Project

General

Profile

Actions

Task #16368

closed

Task #16360: Sprint Planning for 20/01/2025 - 31/01/2025

BE:Invoice Minimum Viable Product: Cancelling a clearance invoice

Added by Redmine Admin 7 months ago. Updated about 1 hour ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Start date:
01/14/2025
Due date:
01/31/2025
% Done:

100%

Estimated time:
8:00 h
Spent time:
GitLab ID:
1741
GitLab Milestone:
GitLab Ticket Number:
230
GitLab Time Logged:
14400
Lock Timeline Date:
No
gitlab project trace:
Sprint Planning for 20/01/2025 - 31/01/2025

Description

Description

As a user
I want to be able to cancel a clearing invoice that need to be voided or have been overbilled
 

Acceptance Criteria:

  1. Cancel Invoice :
    • The system must provide an option to cancel a clearing invoice from the invoice page screen.
    • Only authorized users (such as managers) should be able to perform the cancellation action.
  2. Confirmation Prompt:
    • When selecting "Cancel invoice," for clearing a confirmation prompt must appear to ensure the user understands that:
      • This action is irreversible.
      • A new invoice 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 invoice status will be updated to “Cancelled” in the system.
  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 invoice is linked to payment, the system should automatically update the status of that payment reference 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) to inform them of the invoice cancellation and if any refund request is needed.

GitLab Sync Log

[{"id": "14066", "author": "Ra-ees Peeroo", "hours": 4.0, "created": "2025-01-23T07:08:07.813Z", "log_date": "2025-01-22", "comment": "Imported from GitLab by @Ra-ees Peeroo on 2025-01-23T07:08:07.813Z: 4h-(4.0)h spend at: 2025-01-22", "status": "active", "deleted_by": "", "redmine_entry_id": 7856}]

Actions #1

Updated by Redmine Admin 7 months ago

  • GitLab Sync Log updated (diff)
Actions #2

Updated by Redmine Admin 5 months ago

  • Status changed from QA to Closed
  • % Done changed from 50 to 100
Actions

Also available in: Atom PDF