When multiple funding sources are defined in the project contract along with their respective allocation percentages, the customer tax information in the invoice proposal does not update correctly based on the funding source.

Example Scenario:

• Customer A (Funding Source 1) – Allocation: 60%
• Customer B (Funding Source 2) – Allocation: 40%
• Milestone amount: Rs.10,000

The system correctly splits the milestone Rs.10,000 and generates two invoice proposals:

• Rs. 6,000 for Customer A
• Rs. 4,000 for Customer B

Issue:

During the invoice proposal process, D365 automatically populates the tax information based on the address of the primary funding source (Customer A). For the invoice proposal linked to Funding Source 1: Customer A, the tax information are populated correctly.

However, for the second invoice proposal associated with Funding Source 2: Customer B, the system incorrectly defaults the tax information as the system picks primary funding source (Customer A) address & GSTIN instead of showing Customer B address & GSTIN. As a result, incorrect tax data being reflected in the invoice proposal for Funding Source 2. We need to ensure that the customer tax details in the invoice proposals accurately reflect the assigned funding source.

Impact:

This issue causes significant problems in handling scenarios with multiple funding sources, as tax compliance and reporting become inaccurate.

Requirement:

The system should ensure that each invoice proposal correctly inherits the tax details (address and GSTIN) of its respective funding source, rather than defaulting to the primary funding source.

This needs to be addressed urgently to avoid compliance and billing discrepancies for the client.