[GH-ISSUE #5651] [Feature] Automatically merge pre-tip (uncleared) and post-tip cleared transactions using bank sync (SImpleFin) #9371

Closed
opened 2026-04-10 19:39:01 -05:00 by GiteaMirror · 4 comments
Owner

Originally created by @distantvapor on GitHub (Aug 30, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/5651

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?

When automatically pulling transaction from accounts in SimpleFin, specific transaction types that involves tips are not matched / merged correctly. Most transactions in businesses that allow tips involve running a card at the POS first and then adding a tip after the fact. This results in the uncleared transaction showing the original amount billed and the posted (cleared) transaction showing the final amount with the tip.

Actual, however, does not identify these transactions as the same which results in two distinct transactions, one left in an uncleared state (pre-tip) and the other left automatically created once posted (cleared). This results in extra work identifying the two transactions and modifying/merging or simply deleting the original and re-categorizing the cleared transaction.

I am requesting a feature be added which would enable this two to be matched and automatically categorized.

Describe your ideal solution to this problem

No response

Teaching and learning

No response

Originally created by @distantvapor on GitHub (Aug 30, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/5651 ### 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? When automatically pulling transaction from accounts in SimpleFin, specific transaction types that involves tips are not matched / merged correctly. Most transactions in businesses that allow tips involve running a card at the POS first and then adding a tip after the fact. This results in the uncleared transaction showing the original amount billed and the posted (cleared) transaction showing the final amount with the tip. Actual, however, does not identify these transactions as the same which results in two distinct transactions, one left in an uncleared state (pre-tip) and the other left automatically created once posted (cleared). This results in extra work identifying the two transactions and modifying/merging or simply deleting the original and re-categorizing the cleared transaction. I am requesting a feature be added which would enable this two to be matched and automatically categorized. ### Describe your ideal solution to this problem _No response_ ### Teaching and learning _No response_
GiteaMirror added the featureneeds votes labels 2026-04-10 19:39:01 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Aug 30, 2025):

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:3239401263 --> @github-actions[bot] commented on GitHub (Aug 30, 2025): :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 -->
Author
Owner

@youngcw commented on GitHub (Aug 30, 2025):

This problem is vendor and bank specific. The problem comes from the synced data treating the pre and post cleared transactions as different transactions. I don't think there would be a good way to do this consistently without causing other issues.

One workaround is to disable importing pending transactions for that account.

<!-- gh-comment-id:3239409454 --> @youngcw commented on GitHub (Aug 30, 2025): This problem is vendor and bank specific. The problem comes from the synced data treating the pre and post cleared transactions as different transactions. I don't think there would be a good way to do this consistently without causing other issues. One workaround is to disable importing pending transactions for that account.
Author
Owner

@deron-dev commented on GitHub (Nov 1, 2025):

How do I disable importing pending transactions for an account?

<!-- gh-comment-id:3476678582 --> @deron-dev commented on GitHub (Nov 1, 2025): How do I disable importing pending transactions for an account?
Author
Owner

@youngcw commented on GitHub (Nov 4, 2025):

How do I disable importing pending transactions for an account?

Its in the bank sync settings in the sidebar.

<!-- gh-comment-id:3483455816 --> @youngcw commented on GitHub (Nov 4, 2025): > How do I disable importing pending transactions for an account? Its in the bank sync settings in the sidebar.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#9371