github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-15 22:54:03 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #6706] [Feedback] Payee Locations #44494

New Issue
Open
opened 2026-04-26 05:50:02 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-04-26 05:50:02 -05:00
Owner
Copy Link

Originally created by @mannkind on GitHub (Jan 18, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/6706

Payee Locations

Note: This is an experimental feature. Enable it via Settings → Advanced → Experimental Features → Payee Locations.

Prerequisites

  • Enable the Payee Locations experimental feature in Settings.
Image
  • The payee locations feature is only enabled on the mobile transaction screen and not the table-based screen found on large screens/desktops

Troubleshooting location permissions

⚠️ Browsers restrict access to sensitive APIs like geolocation to secure contexts only. When you access your server via IP address (e.g., http://192.168.x.x), it’s HTTP, not HTTPS, so the browser silently refuses to even prompt for location permission.

ℹ️ Workaround 1 - Chrome Flags

This method tells Chrome to treat a specific insecure origin (HTTP) as secure for testing purposes.

  • Open Chrome on your Android device.
  • In the address bar, type: chrome://flags and press Enter.
  • Search for: unsafely-treat-insecure-origin-as-secure.
  • Tap the dropdown menu under the flag and select Enabled.
  • In the text box that appears, enter your HTTP site address (e.g., http://example.com/ or http://192.168.1.50:8080/).
  • Note: If you are using a non-standard port, you must include it, e.g., http://192.168.1.50:8080/.
  • Tap the Relaunch button at the bottom of the screen.
  • Navigate to your HTTP site, and it should now prompt for location permission.

🙏 to zenmeow on Discord for this info

⚠️ If the geolocation permission prompt is declined, Actual will not ask again. Location permissions for this site will need to be manually updated in the browser settings — the exact location of this setting varies depending on the browser.

Saving a Payee Location

  1. Begin entering a new transaction.
  2. Enter or select a payee.
  • Your browser will prompt for location permissions. Grant access to continue.
  1. Tap the small Save geolocation button that appears in the payee field.
  2. Continue entering transaction details as desired.
  3. Save the transaction.

⚠️ The Save button will only appear if no existing location for this payee is within 500m. If you don’t see it, a nearby location may already be saved.

Image

Using the Nearest Payee

Once you have saved one or more payee locations, Actual can automatically suggest the nearest one when entering a transaction OR use the nearest payee with a quick tap.

  1. Begin entering a new transaction.
  2. If any saved payees are within 500 metres of your current location, a Nearby Payees section will appear in the payee autocomplete and a Nearby geolocation button will appear in the payee field.
  3. Select a nearby (or any!) payee from the autocomplete OR tap the Nearby button — the closest matching payee will be set automatically.
  4. Continue entering transaction details as desired.
  5. Save the transaction.
Image Image

Forgetting a Payee Location

There is currently no dedicated screen for managing all saved payee locations. However, you can remove a location while you are at or near it:

  1. Begin entering a new transaction at or near the payee location you want to remove.
  2. Tap the payee field to open the autocomplete dropdown.
  3. Tap the Forget option next to the payee entry.

ℹ️ The Forget button only appears when you are physically near the saved location.

Image
Originally created by @mannkind on GitHub (Jan 18, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/6706 # Payee Locations > **Note:** This is an experimental feature. Enable it via Settings → Advanced → Experimental Features → Payee Locations. ## Prerequisites - Enable the **Payee Locations** experimental feature in Settings. <img width="472" height="269" alt="Image" src="https://github.com/user-attachments/assets/6c471e87-bb41-4944-b965-d81412c8353a" /> - The payee locations feature is only enabled on the mobile transaction screen and not the table-based screen found on large screens/desktops ### Troubleshooting location permissions ⚠️ Browsers restrict access to sensitive APIs like geolocation to [secure contexts](https://developer.mozilla.org/en-US/docs/Web/Security/Secure_Contexts) only. When you access your server via IP address (e.g., http://192.168.x.x), it’s HTTP, not HTTPS, so the browser silently refuses to even prompt for location permission. <details> <summary>ℹ️ Workaround 1 - Chrome Flags</summary> This method tells Chrome to treat a specific insecure origin (HTTP) as secure for testing purposes. * Open Chrome on your Android device. * In the address bar, type: chrome://flags and press Enter. * Search for: unsafely-treat-insecure-origin-as-secure. * Tap the dropdown menu under the flag and select Enabled. * In the text box that appears, enter your HTTP site address (e.g., http://example.com/ or http://192.168.1.50:8080/). * Note: If you are using a non-standard port, you must include it, e.g., http://192.168.1.50:8080/. * Tap the Relaunch button at the bottom of the screen. * Navigate to your HTTP site, and it should now prompt for location permission. **🙏 to zenmeow on Discord for this info** </details> ⚠️ If the geolocation permission prompt is declined, Actual will not ask again. Location permissions for this site will need to be manually updated in the browser settings — the exact location of this setting varies depending on the browser. ## Saving a Payee Location 1. Begin entering a new transaction. 2. Enter or select a payee. - Your browser will prompt for location permissions. Grant access to continue. 3. Tap the small **Save** geolocation button that appears in the payee field. 4. Continue entering transaction details as desired. 5. Save the transaction. > ⚠️ The Save button will only appear if no existing location for this payee is within 500m. If you don’t see it, a nearby location may already be saved. <img width="499" height="315" alt="Image" src="https://github.com/user-attachments/assets/f0d5bd3a-f7bd-4e9d-8ad8-a9a936ea90af" /> ## Using the Nearest Payee Once you have saved one or more payee locations, Actual can automatically suggest the nearest one when entering a transaction OR use the nearest payee with a quick tap. 1. Begin entering a new transaction. 2. If any saved payees are within **500 metres** of your current location, a **Nearby Payees** section will appear in the payee autocomplete **and** a **Nearby** geolocation button will appear in the payee field. 3. Select a nearby (or any!) payee from the autocomplete **OR** tap the **Nearby** button — the closest matching payee will be set automatically. 4. Continue entering transaction details as desired. 5. Save the transaction. <img width="499" height="348" alt="Image" src="https://github.com/user-attachments/assets/a96ab93e-fcc0-4924-bc13-5e4080d3d3e1" /> <img width="501" height="481" alt="Image" src="https://github.com/user-attachments/assets/adecfe99-6258-4bed-9101-6237974d9612" /> ## Forgetting a Payee Location There is currently no dedicated screen for managing all saved payee locations. However, you can remove a location while you are at or near it: 1. Begin entering a new transaction at or near the payee location you want to remove. 2. Tap the payee field to open the autocomplete dropdown. 3. Tap the **Forget** option next to the payee entry. > ℹ️ The Forget button only appears when you are physically near the saved location. <img width="501" height="481" alt="Image" src="https://github.com/user-attachments/assets/4b5e9e02-ed4e-4697-9326-978a2bb5a414" />
GiteaMirror added the feedbackexperimental feature labels 2026-04-26 05:50:04 -05:00
GiteaMirror commented 2026-04-26 05:50:06 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 18, 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:3765757043 --> @github-actions[bot] commented on GitHub (Jan 18, 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 -->
GiteaMirror commented 2026-04-26 05:50:06 -05:00
Author
Owner
Copy Link

@Juulz commented on GitHub (Apr 8, 2026):

There is no documentation other than PR #6157 for this.

<!-- gh-comment-id:4205720555 --> @Juulz commented on GitHub (Apr 8, 2026): There is no documentation other than PR #6157 for this.
GiteaMirror commented 2026-04-26 05:50:09 -05:00
Author
Owner
Copy Link

@zenmeow88 commented on GitHub (Apr 9, 2026):

Thanks for adding this feature!

Currently the geolocation feature is unable to save multiple locations using the same payee name, e.g. saving Starbucks at different franchise locations.

Would be great if this feature can be added too. Thank you for considering!

<!-- gh-comment-id:4214852741 --> @zenmeow88 commented on GitHub (Apr 9, 2026): Thanks for adding this feature! Currently the geolocation feature is unable to save multiple locations using the same payee name, e.g. saving Starbucks at different franchise locations. Would be great if this feature can be added too. Thank you for considering!
GiteaMirror commented 2026-04-26 05:50:10 -05:00
Author
Owner
Copy Link

@mannkind commented on GitHub (Apr 10, 2026):

Currently the geolocation feature is unable to save multiple locations using the same payee name, e.g. saving Starbucks at different franchise locations.

@zenmeow88 Multiple locations for any single payee should be working. Though there is the caveat that it won't show the save button again if there's already a nearby location for the payee (within the default search distance of 500m; I’ve updated the docs above with this info).

(Edited with a better example)
Using Chrome I set my location near a Target. You can see it shows up in a nearby location, and it doesn't show the save button (because there's one nearby) after I select it. I then virtually moved my location a few miles away. After refreshing to get the new location, I can select Target from the dropdown and save a new location for Target. I have ~13 years of Targets around the country in my budget from YNAB/YNAB5.

https://github.com/user-attachments/assets/8f68a6be-2f3f-4320-ba0d-470806034477

<!-- gh-comment-id:4220307837 --> @mannkind commented on GitHub (Apr 10, 2026): > Currently the geolocation feature is unable to save multiple locations using the same payee name, e.g. saving Starbucks at different franchise locations. @zenmeow88 Multiple locations for any single payee should be working. Though there is the caveat that it won't show the save button again if there's already a nearby location for the payee (within the default search distance of 500m; I’ve updated the docs above with this info). (Edited with a better example) Using Chrome I set my location near a Target. You can see it shows up in a nearby location, and it doesn't show the save button (because there's one nearby) after I select it. I then virtually moved my location a few miles away. After refreshing to get the new location, I can select Target from the dropdown and save a new location for Target. I have ~13 years of Targets around the country in my budget from YNAB/YNAB5. https://github.com/user-attachments/assets/8f68a6be-2f3f-4320-ba0d-470806034477
GiteaMirror commented 2026-04-26 05:50:11 -05:00
Author
Owner
Copy Link

@zenmeow88 commented on GitHub (Apr 10, 2026):

Thanks for the clarification! It really works as you mentioned when the distance is more than 500m, which is really awesome!

<!-- gh-comment-id:4222321642 --> @zenmeow88 commented on GitHub (Apr 10, 2026): Thanks for the clarification! It really works as you mentioned when the distance is more than 500m, which is really awesome!
GiteaMirror commented 2026-04-26 05:50:12 -05:00
Author
Owner
Copy Link

@xela-zone commented on GitHub (Apr 22, 2026):

Have a ux tweak:

Before, the flow for typing a payee in would 'save' the amount at the top, but now hitting the 'nearby' button can cause the value to get lost

Firefox installed pwa, android 17 beta 4? Build id CP21.260330.008
Pixel 9 pro xl

Vid: https://github.com/user-attachments/assets/31bc0ced-4c45-44f4-af85-cb65f196729c

<!-- gh-comment-id:4297480933 --> @xela-zone commented on GitHub (Apr 22, 2026): Have a ux tweak: Before, the flow for typing a payee in would 'save' the amount at the top, but now hitting the 'nearby' button can cause the value to get lost Firefox installed pwa, android 17 beta 4? Build id CP21.260330.008 Pixel 9 pro xl Vid: https://github.com/user-attachments/assets/31bc0ced-4c45-44f4-af85-cb65f196729c
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
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label experimental feature feedback
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#44494
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?