mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-15 14:43:36 -05:00
[GH-ISSUE #1511] Mobile - record GPS location of transaction entry to auto-suggest future entries #97977
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#97977
Reference in New Issue
Block 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 @Lunchtime0614 on GitHub (Aug 11, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1511
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
Speed up the transaction entry on mobile when traveling by auto suggesting payees at the time of transaction entry based on the mobile devices current location.
Describe your ideal solution to this problem
Using the mobile phone's GPS location during every transaction entry on the mobile device tie the location/GPS coordinates to that transaction entry. On subsequent transaction entries within a to be determined radius of that GPS location (relatively small distance), have the Actual app auto-suggest the payee based on known previous entries with GPS locations within the radius of the current location.
There should be an option within the settings to enable or disable this feature as some users may not want the app to record their location history. It should be disabled by default.
Teaching and learning
This could be documented as a usability feature that (presumably) other apps do not have. It would aid in speeding up transaction entries on the go, potentially one handed (not having to type the payee). Simple documentation in the guides to explain the toggle on/off in the settings.
@github-actions[bot] commented on GitHub (Aug 11, 2023):
✨ 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 👍!
@ElDubsNZ commented on GitHub (Jul 9, 2024):
Support this. YNAB has it and it's such a time saver. Combined with remembering the last category used for a transaction to that payee, and what your default spending account is, pretty much all you have to do at checkout is enter the amount and hit save.
@jj33 commented on GitHub (Mar 24, 2025):
Giving a vote for this one, as stated above YNAB does this and makes it super easy when out and about to easily add a transaction.
@SunFlowerOwl commented on GitHub (Sep 15, 2025):
I'd also like to voice my support for this issue.
@mannkind commented on GitHub (Sep 26, 2025):
Yes, please. This would help make mobile entry far less painful.
@xela-zone commented on GitHub (Apr 30, 2026):
Up and coming #6706