mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-16 07:04:23 -05:00
[GH-ISSUE #338] Can't manually match an imported transaction with a previously entered (or scheduled) transaction #97429
Closed
opened 2026-05-29 07:34:45 -05:00 by GiteaMirror
·
5 comments
No Branch/Tag Specified
master
dependabot/npm_and_yarn/npm_and_yarn-cd62b4b37a
api-browser-custom-data-dir
tabedzki/feat/replacing-month-picker-with-day-picker
delay-initial-sync-until-loaded
jfdoming/mobile-app-build
cross-version-sync-compat
jfdoming/api-tokens-part-1
jfdoming/api-tokens-part-2
jfdoming/api-tokens-part-3
jfdoming/mobile-app-updates
claude/budget-version-migration-compat-151jlr
claude/worker-error-serialization-9iqtl7
claude/react-table-library-research-afx83z
claude/issue-8401-regression-test-9nw9l3
jfdoming/mobile-app-foundation-part-1
jfdoming/mobile-app-scaffold
release
ai-fix-cleanup-def-8290
claude/relaxed-shannon-jusywa
claude/fervent-keller-s6f2fq
claude/determined-feynman-st1y9z
claude/wizardly-einstein-vi2wce
claude/sweet-albattani-7nseio
feat/bank-sync-per-budget-file
claude/affectionate-cannon-y0kc82
claude/dependabot-findings-m9pgmb
claude/mac-app-ios-publish-zjs1lz
claude/vigilant-tesla-aiiyos
depot-migrate-secrets-1781296330308
claude/quirky-cerf-v5qck7
claude/animation-removal-alternative-2etfh1
claude/netlify-preview-comments-consolidate-9XPYa
osc/7391-error-boundaries-reports
claude/pensive-dijkstra-7DYui
claude/server-app-version-mismatch-HTCGv
claude/pr-8027-review-feedback-mELuO
claude/zealous-wozniak-e5pO0
claude/intelligent-heisenberg-BSHJq
claude/translation-download-refactor-jFRsO
claude/mobile-performance-ideas-G9PAO
claude/github-issue-7988-5A5ly
blacksmith-migration-ff70d2d
claude/great-mayer-KRvOk
claude/react-native-ios-compilation-fcJh5
claude/serene-goldberg-58xv0
claude/kind-euler-LVG3K
release-automation/edge-nightly
7710-bundle-migrations
claude/fix-docker-build-error-WMfed
claude/llm-compatible-release-notes-t20Nr
7710-tests-tdd
cursor/transaction-table-rewrite-f077
claude/plan-ci-secure-context-OtEe1
claude/fix-issue-7667-DPXi3
cursor/resolve-pr-7449-ee11
claude/fix-typescript-build-error-JPtZ5
copilot/add-repository-configs-to-packages
worktree-compressed-drifting-ritchie
claude/api-consumer-verification-kfz1K
pr-7454
claude/fix-issue-7410-LLLQ4
revert-7281-generate-icons
react-query-useSchedules
copilot/sub-pr-6140
package-upgrades
v26.7.0
v26.6.0
v26.5.2
v26.5.1
v26.5.0
v26.4.0
v26.3.0
v26.2.1
v26.2.0
v26.1.0
v25.12.0
v25.11.0
v25.10.0
v25.9.0
v25.8.0
v25.7.1
v25.7.0
v25.6.1
v25.6.0
v25.5.0
v25.4.0
v25.3.1
v25.3.0
v25.2.1
v25.2.0
v25.1.0
v24.12.0
v24.11.0
v24.10.1
v24.10.0
v24.9.0
v24.8.0
v24.7.0
v24.6.0
v24.5.0
v24.4.0
v24.3.0
v24.2.0
v24.1.0
v23.12.0
v23.11.0
v23.10.0
v23.9.0
v23.8.1
v23.8.0
v23.7.2
v23.7.1
v23.7.0
v23.6.0
v23.5.0
v23.4.2
v23.4.1
v23.4.0
v23.3.2
v23.3.0
v23.2.9
v23.2.5
v23.1.12
v22.12.9
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
regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
Mirrored from GitHub Pull Request
No Label
feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#97429
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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?
Originally created by @bpaulien on GitHub (Nov 19, 2021).
Original GitHub issue: https://github.com/actualbudget/actual/issues/338
I have a scheduled transaction that was in the register, and then manually imported a transaction from the bank. I don't see a way to tell the software that these 2 are a "match" and really the same transaction. I guess I can delete the one that I imported, but it would be nice if they could be matched so I don't have to delete.
@bpaulien commented on GitHub (Nov 19, 2021):
I guess the main reason I want to be able to match them instead of deleting the imported one is because the imported one is now marked as "cleared" because it came from the bank. But the "real" one (that has the correct payee and notes) is not marked as cleared. So now I have to delete the one with the funny payee and "External Deposit" in Notes, and then go and mark the scheduled one as cleared.
So I guess we need to come up with some rules for what happens when 2 transactions are matched. I guess you would want the Payee and the Notes to be taken from the scheduled, or manually entered one, because those have the correct information (presumably, since you did it by hand) But the "cleared" status of the imported one. I guess the amounts should typically be the same? But if not, take the value of the imported one because that came from the bank, so is official. In case you "fat fingered" the amount when manually entering it (or forgot to add tip to restaurant meal) the amount from bank would be right.
What do you think about date? Take date from manual entry, or from import?
@github-actions[bot] commented on GitHub (Jan 15, 2023):
🚧🚨 This issue is being marked as stale due to 90 days of inactivity. 🚧🚨
@github-actions[bot] commented on GitHub (May 2, 2023):
✨ Thanks for sharing your idea! ✨
This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. 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 👍!
@youngcw commented on GitHub (Feb 8, 2024):
You can link a transaction to a schedule manually by selecting the transaction and using the "Link Schedule" option in the menu.
@mosteo commented on GitHub (Aug 5, 2025):
The shortcoming of manually linking is that if the schedule applies rules on automatic matching, those are not applied.
You have to enter the "edit as rule" secondary dialog /before linking the transaction/ and then adjust the fields to make it match. Then you can "apply" the rule.
As a further nuisance of my bank, it posts several transactions from unrelated payees under the same fake payee (just a code, don't know why). Something similar happens with transactions that arrive through Paypal. They're difficult to match to a schedule because the payee will always be wrong, and you can't rename the payee, as it's shared by several real payees. If you don't enter a payee in the schedule to allow it to match on e.g. the notes, the upcoming transaction will show blank fields.
Unless I'm missing the proper workflow here, this translates into lots of manual cumbersome editing to apply the rules of a schedule to the manually linked transaction. It would be ideal to be able to select the scheduled transaction and the real one, and have something like "link & apply rules" in the context menu. Or at least that "link schedule" had a straightforward way of force-applying rules bypassing the matching.