github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-07 12:28:57 -05:00
Code Issues 1.6k Packages Projects Releases 55 Wiki Activity

[GH-ISSUE #5089] [Feature] Add functionality for reimbursement to actual #9107

New Issue
Closed
opened 2026-04-10 19:22:53 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-10 19:22:53 -05:00
Owner
Copy Link

Originally created by @KaranJayakumar on GitHub (Jun 4, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/5089

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, when a user covers a shared cost (e.g., full rent payment) and is later reimbursed (e.g., by a roommate), the budget remains inaccurately inflated or overspent. There’s no clean way to indicate that the reimbursement transaction offsets a previous expense. This happens insanely often so I have to budget way more than i need to for rent etc which makes the values for each category completely inaccurate.

People currently use hacks like:

  • Manually splitting transactions.
  • Categorizing reimbursements as “income” (which messes with income reports).

So a native feature would be great imo.

Describe your ideal solution to this problem

Allow users to select a transaction (e.g., "Roommate Reimbursement") and link it to a prior expense (e.g., "Rent").

Visually show the reimbursed amount against the original transaction.

The budget should reflect the net expense, showing the user's true out-of-pocket cost.

Teaching and learning

We can add the reimbursement option to the “Add Transaction” flow, since it’s already highly visible and used often. That makes it easy to discover in-context. Also, just include a short section in the docs/help center with a clear example like fronting rent and getting paid back. That’s enough to cover most use cases without adding clutter.

Originally created by @KaranJayakumar on GitHub (Jun 4, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/5089 ### Verified feature request does not already exist? - [x] I have searched and found no existing issue ### 💻 - [x] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? Currently, when a user covers a shared cost (e.g., full rent payment) and is later reimbursed (e.g., by a roommate), the budget remains inaccurately inflated or overspent. There’s no clean way to indicate that the reimbursement transaction offsets a previous expense. This happens insanely often so I have to budget way more than i need to for rent etc which makes the values for each category completely inaccurate. People currently use hacks like: - Manually splitting transactions. - Categorizing reimbursements as “income” (which messes with income reports). So a native feature would be great imo. ### Describe your ideal solution to this problem Allow users to select a transaction (e.g., "Roommate Reimbursement") and link it to a prior expense (e.g., "Rent"). Visually show the reimbursed amount against the original transaction. The budget should reflect the net expense, showing the user's true out-of-pocket cost. ### Teaching and learning We can add the reimbursement option to the “Add Transaction” flow, since it’s already highly visible and used often. That makes it easy to discover in-context. Also, just include a short section in the docs/help center with a clear example like fronting rent and getting paid back. That’s enough to cover most use cases without adding clutter.
GiteaMirror added the needs votesfeature labels 2026-04-10 19:22:53 -05:00
GiteaMirror commented 2026-04-10 19:22:55 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 4, 2025):

✨ Thanks for sharing your idea! ✨

This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make 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:2939140456 --> @github-actions[bot] commented on GitHub (Jun 4, 2025): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make 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#9107
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?