[Bug]: Linking or merging manual and scheduled transactions results in duplicates and incorrect “Due” status #2937

New Issue

GiteaMirror · 2026-02-28T20:32:53-06:00

GiteaMirror commented

2026-02-28 20:32:53 -06:00

Originally created by @jeremyj on GitHub (Feb 16, 2026).

What happened?

I was trying to reconcile a manually added transaction with an automatically created scheduled transaction for the same payment.

Expected behavior:
Linking or merging the two should result in a single transaction associated with the schedule.

Actual behavior:
Two transactions remain:

If I link the manual transaction to the scheduled one → I end up with two transactions instead of one.

If I merge them → the automatically created scheduled transaction is marked as “Due”, and there are still two transactions present.

This makes it unclear which transaction is the correct one and breaks the expected reconciliation workflow.

How can we reproduce the issue?

Create a scheduled transaction that is automatically added to the ledger.

Manually add a transaction representing the same payment.

Attempt to reconcile them:

Option A: Link the manual transaction to the scheduled transaction.

Option B: Merge the two transactions.

Observe the results.

Expected:
A single transaction remains, correctly associated with the schedule and marked as Paid

.

Actual:
Two transactions remain. In the merge case, the scheduled one is also marked as Due.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome

Operating System

Linux

Originally created by @jeremyj on GitHub (Feb 16, 2026). ### What happened? What happened? I was trying to reconcile a manually added transaction with an automatically created scheduled transaction for the same payment. Expected behavior: Linking or merging the two should result in a single transaction associated with the schedule. Actual behavior: Two transactions remain: If I link the manual transaction to the scheduled one → I end up with two transactions instead of one. If I merge them → the automatically created scheduled transaction is marked as “Due”, and there are still two transactions present. This makes it unclear which transaction is the correct one and breaks the expected reconciliation workflow. ### How can we reproduce the issue? How can we reproduce the issue? Create a scheduled transaction that is automatically added to the ledger. Manually add a transaction representing the same payment. Attempt to reconcile them: Option A: Link the manual transaction to the scheduled transaction. Option B: Merge the two transactions. Observe the results. Expected: A single transaction remains, correctly associated with the schedule and marked as Paid <img width="1618" height="138" alt="Image" src="https://github.com/user-attachments/assets/c9b3fecd-4270-4d76-8167-a783402e6280" /> <img width="1624" height="143" alt="Image" src="https://github.com/user-attachments/assets/2447c755-0847-4e8c-9501-e2ecad5e86bb" /> <img width="827" height="241" alt="Image" src="https://github.com/user-attachments/assets/16402ca7-b639-4052-9bd9-5c9ba39b646e" /> <img width="1616" height="153" alt="Image" src="https://github.com/user-attachments/assets/8d99252c-e7aa-4319-8f68-f0480d7687aa" /> <img width="1612" height="262" alt="Image" src="https://github.com/user-attachments/assets/59c70cb1-fe0f-4789-9510-b64475841d85" /> <img width="1612" height="143" alt="Image" src="https://github.com/user-attachments/assets/45c2fe0f-9f1e-43a9-8363-273ed5f7095f" /> . Actual: Two transactions remain. In the merge case, the scheduled one is also marked as Due. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Chrome ### Operating System Linux

GiteaMirror added the transactions good first issue bug help wanted labels 2026-02-28 20:32:54 -06:00