Form 3X entity aggregate totals are incorrect for unaggregated transactions

[exalate-issue-sync]

Where was the issue found:

• Committee ID: C00104174
• Environment: STAGE
• Browser: Chrome

Please describe the issue clearly and concisely (e.g., expected vs. actual result):

Form 3X reports with unaggregated or “re-aggregated” Schedule A transactions have incorrect entity aggregate value displays on the Manage transactions and the transaction detail page.

Scenarios identified:

1. When a report has three transactions for an entity and the first transaction (based on receipt date) is Unaggregated,
   • Manage transactions page Aggregate display is incorrect for first transaction but correct for subsequent transactions
   • Transaction detail page Aggregate display is correct for first and third transactions but incorrect for second transaction
2. When the Unaggregated transaction from the previous scenario is Reaggregated,
   • Manage transactions page Aggregate display is correct for first transaction but incorrect for second and third
   • Transaction detail page Aggregate display is correct for first and second transaction but incorrect for third

Approximate time the issue was found: 8/19/26, 11am

Steps to Reproduce (UNAGGREGATE):

1. Create a F3X report with 3 individual receipt transactions
2. For the 1st transaction, click Actions > Unaggregate
3. On the Manage transactions page, the Aggregate value for the 1st transaction is not $0.00 but should be (This is a bug)
4. Select the 2nd transaction to display the transaction detail page where the Aggregate value is incorrect (This is a bug)

Steps to Reproduce (REAGGREGATE):

1. Select the 1st transaction (Unaggregated) and click Actions > Aggregate
2. On the Manage transactions page, the Aggregate value for the 2nd and 3rd transactions are incorrect (This is a bug)
3. Select the 3rd transaction to display the transaction detail page where the Aggregate value is incorrect (This is a bug)

Original requirements ticket (if applicable):

Add/see relevant screenshots in "design" section below.

Unit tests in api around the unagregate action removing the aggregate value in the transaction record

QA Notes

null

DEV Notes

If the calculation is wrong (rather than the display), migration for batch re-calculating aggregates (production data).

Design

Unaggregate individual receipt:

Manage transactions - Aggregate for 1st is {color:#bf2600}incorrect{color}; correct for 2nd, 3rd

!image-20260824-164814.png|width=595,alt="image-20260824-164814.png"!

1st transaction detail - correct aggregate

!image-20260824-164908.png|width=595,alt="image-20260824-164908.png"!

2nd transaction detail - {color:#bf2600}incorrect{color} aggregate

!image-20260824-170246.png|width=595,alt="image-20260824-170246.png"!

3rd transaction detail - correct aggregate

!image-20260824-170520.png|width=595,alt="image-20260824-170520.png"!

Reaggregate individual receipt:

Manage transactions - Aggregate for 1st is correct; 2nd, 3rd are {color:#bf2600}incorrect{color}

!image-20260827-132755.png|width=671,alt="image-20260827-132755.png"!

Individual detail - first and second are correct, third is incorrect

1st transaction detail - correct aggregate

!image-20260827-133109.png|width=720,alt="image-20260827-133109.png"!

2nd transaction detail - correct aggregate

!image-20260827-133219.png|width=721,alt="image-20260827-133219.png"!

3rd transaction detail - {color:#bf2600}incorrect{color} aggregate

!image-20260827-133254.png|width=707,alt="image-20260827-133254.png"!

See full ticket and images here: FECFILE-3384

Pull Request: #2307

[exalate-issue-sync]

akhorsand commented: [~accountid:712020:2a1493e5-adee-45bd-b27e-868a5c8d3f62] no longer on hold, Ava updated. Should be ready for devs.