github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 07:01:45 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[GH-ISSUE #7102] [Feature] Link Multiple Transactions Together with Notes for Reconciliation #44631

New Issue
Closed
opened 2026-04-26 06:21:01 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-26 06:21:01 -05:00
Owner
Copy Link

Originally created by @suyash01 on GitHub (Mar 1, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7102

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

Currently, there is no built-in way to explicitly link two or more related transactions together.

This makes it harder to:

  • Reconcile split payments (e.g., UPI/partial card payments)
  • Trace internal transfers involving fees or intermediary accounts
  • Track reimbursements
  • Match refunds with original purchases
  • Group transactions that logically belong together but occur separately

Describe your ideal solution to this problem

Introduce a feature that allows users to:

  • Link two or more transactions together
  • Add an optional shared note to the linked group
  • Visually identify linked transactions in the UI

Proposed Behavior

  • Add a new option in the transaction context menu:
  • “Link transactions”
  • User selects multiple transactions → creates a linked group.
  • Linked transactions:
    • Show a small link icon 🔗
    • Allow hovering/clicking to see all linked transactions
    • Display shared note (if added)
  • User can:
    • Add/edit a shared note
    • Remove a transaction from the group
    • Delete the entire link group (without deleting transactions)

Teaching and learning

Contextual Entry Points (Primary Discovery)

  • The feature should appear where users already think about reconciliation:
  • Right-click / context menu → “Link transactions”
  • Multi-select toolbar action → “Link”
  • Transaction details panel → “Linked transactions” section
  • This ensures users discover it naturally while reconciling or editing transactions.

Visual Indicators (Passive Discovery)

  • Linked transactions should be visibly distinct:
  • Small 🔗 icon in the transaction row
  • Subtle badge: Linked (2)
  • Tooltip on hover: “Linked to 2 other transactions”

Smart Suggestion
Could suggest linking when:

  • Amounts cancel each other out
  • Transactions occur close in time
  • Categories suggest reimbursement/refund patterns

Create a small documentation page:
Title: Linking Transactions
Include:

  • What problem it solves
  • Step-by-step instructions
  • Common use cases:
    • Reimbursements
    • Refunds
    • Split payments
    • Transfer fees
  • How to unlink transactions

Add to FAQ:

  • Does linking affect budget totals? → No
  • Does linking affect reports? → No (unless designed otherwise)
  • Can linked transactions span accounts? → Yes
  • What happens if I delete one? → Explain behavior
Originally created by @suyash01 on GitHub (Mar 1, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/7102 ### Verified feature request does not already exist? - [x] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? Currently, there is no built-in way to explicitly link two or more related transactions together. This makes it harder to: - Reconcile split payments (e.g., UPI/partial card payments) - Trace internal transfers involving fees or intermediary accounts - Track reimbursements - Match refunds with original purchases - Group transactions that logically belong together but occur separately ### Describe your ideal solution to this problem Introduce a feature that allows users to: - Link two or more transactions together - Add an optional shared note to the linked group - Visually identify linked transactions in the UI Proposed Behavior - Add a new option in the transaction context menu: - “Link transactions” - User selects multiple transactions → creates a linked group. - Linked transactions: - Show a small link icon 🔗 - Allow hovering/clicking to see all linked transactions - Display shared note (if added) - User can: - Add/edit a shared note - Remove a transaction from the group - Delete the entire link group (without deleting transactions) ### Teaching and learning Contextual Entry Points (Primary Discovery) - The feature should appear where users already think about reconciliation: - Right-click / context menu → “Link transactions” - Multi-select toolbar action → “Link” - Transaction details panel → “Linked transactions” section - This ensures users discover it naturally while reconciling or editing transactions. Visual Indicators (Passive Discovery) - Linked transactions should be visibly distinct: - Small 🔗 icon in the transaction row - Subtle badge: `Linked (2)` - Tooltip on hover: “Linked to 2 other transactions” Smart Suggestion Could suggest linking when: - Amounts cancel each other out - Transactions occur close in time - Categories suggest reimbursement/refund patterns Create a small documentation page: Title: Linking Transactions Include: - What problem it solves - Step-by-step instructions - Common use cases: - Reimbursements - Refunds - Split payments - Transfer fees - How to unlink transactions Add to FAQ: - Does linking affect budget totals? → No - Does linking affect reports? → No (unless designed otherwise) - Can linked transactions span accounts? → Yes - What happens if I delete one? → Explain behavior
GiteaMirror added the needs votesfeature labels 2026-04-26 06:21:02 -05:00
GiteaMirror commented 2026-04-26 06:21:08 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 1, 2026):

✨ Thanks for sharing your idea! ✨

This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don't forget to upvote the top comment with 👍!

<!-- gh-comment-id:3979804383 --> @github-actions[bot] commented on GitHub (Mar 1, 2026): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don't forget to upvote the top comment with 👍! <!-- feature-auto-close-comment -->
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label feature needs votes
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#44631
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?