Project

General

Profile

Actions

Task #16763

closed

Task #16337: Ocean Sprint Planning for 21/04/2025 - 30/04/2025

Payment: Optimizing receipt for Multiple Invoice Payments

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

Status:
Closed
Priority:
High
Assignee:
-
Start date:
01/23/2025
Due date:
01/23/2025
% Done:

100%

Estimated time:
0:00 h
GitLab ID:
1822
GitLab Milestone:
GitLab Ticket Number:
600
GitLab Time Logged:
0
Lock Timeline Date:
No
gitlab project trace:
Ocean Sprint Planning for 21/04/2025 - 30/04/2025

Description

Points discussed with CPworld , Silverline on 21/01/25

Description

  • All FFWD representatives agreed that when a client pays for multiple invoices simultaneously, only one consolidated receipt will be issued. FFS will also give the user option to choose whether to issue a single receipt or separate receipts.

Screen: Accounting > Payment

Acceptance Criteria:

  • When a client selects multiple invoices for payment, the payment screen should display two options:
    • "Issue a single consolidated receipt" (If the client chooses the consolidated receipt option, the system should generate one receipt that lists all paid invoices with their respective amounts.)
    • "Issue separate receipts for each invoice" (If the client choose for separate receipts, the system should generate individual receipts for each invoice paid.)
  • The system should default to the "single consolidated receipt" option

Scenario:

  • 2 invoices with 2 different modes of payment each. If user chooses to issue diff receipts then system will generate 4 receipts.

1st receipt : Inv A with payment mode 1

2nd receipt; Inv A with payment mode 2

3rd receipt : Inv B with payment mode 1

4threceipt; Inv B with payment mode 2


GitLab Sync Log

[]

Actions #1

Updated by Redmine Admin 7 months ago

  • GitLab Sync Log updated (diff)
Actions

Also available in: Atom PDF