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

New Issue

GiteaMirror · 2026-05-29T19:08:21-05:00

GiteaMirror commented

2026-05-29 19:08:21 -05:00

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.

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

Begin entering a new transaction.
Enter or select a payee.

Your browser will prompt for location permissions. Grant access to continue.

Tap the small Save geolocation button that appears in the payee field.
Continue entering transaction details as desired.
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.

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.

Begin entering a new transaction.
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.
Select a nearby (or any!) payee from the autocomplete OR tap the Nearby button — the closest matching payee will be set automatically.
Continue entering transaction details as desired.
Save the transaction.

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:

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

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

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 experimental feature feedback labels 2026-05-29 19:08:23 -05:00

GiteaMirror commented

2026-05-29 19:08:28 -05:00

@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 👍!

@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 👍!

GiteaMirror commented

2026-05-29 19:08:30 -05:00

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

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

@Juulz commented on GitHub (Apr 8, 2026): There is no documentation other than PR #6157 for this.

GiteaMirror commented

2026-05-29 19:08:35 -05:00

@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!

@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-05-29 19:08:37 -05:00

@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

@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-05-29 19:08:40 -05:00

@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!

@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-05-29 19:08:43 -05:00

@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

@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

GiteaMirror commented

2026-05-29 19:08:44 -05:00

@MatissJanis commented on GitHub (May 15, 2026):

A small annoyance: each time I enter the transaction creation page I get re-prompted for location permissions. Even if I allowed it in a previous session.

I know this can be fixed by toggling a setting in safari, but we can't expect every user to know this trick.

What if we fixed this by adding a "nearby" chip in the payee selector that the user has to explicitly click? After clicking it - it would request location permissions only at that stage (not the default behaviour) and thus be a smaller annoyance.

Open to other suggestions too obviously.

@MatissJanis commented on GitHub (May 15, 2026): A small annoyance: each time I enter the transaction creation page I get re-prompted for location permissions. Even if I allowed it in a previous session. I know this can be fixed by toggling a setting in safari, but we can't expect every user to know this trick. What if we fixed this by adding a "nearby" chip in the payee selector that the user has to explicitly click? After clicking it - it would request location permissions only at that stage (not the default behaviour) and thus be a smaller annoyance. Open to other suggestions too obviously.

GiteaMirror commented

2026-05-29 19:08:47 -05:00

@Juulz commented on GitHub (May 15, 2026):

I know this can be fixed by toggling a setting in safari, but we can't expect every user to know this trick.

If it's that easy to fix, perhaps it should just be in the docs?

@Juulz commented on GitHub (May 15, 2026): > I know this can be fixed by toggling a setting in safari, but we can't expect every user to know this trick. If it's that easy to fix, perhaps it should just be in the docs?

GiteaMirror commented

2026-05-29 19:08:48 -05:00

@mannkind commented on GitHub (May 15, 2026):

Happy to add to the docs; I should be able to do so later this evening.

Otherwise, if a UI change is in order, I'd love to be able to retain the current behavior if the permissions have already been granted without requiring another explicit user interaction. Perhaps we can only show the new chip if the permissions are currently 'prompt' (which Safari stupidly returns even when the special setting is Deny)

This was a barely tested, very fast change via Claude to try to visualize what I was thinking about. It's not perfect.

https://github.com/user-attachments/assets/038d3c2f-780b-4e24-9a4d-39cfc3bba5ea

@mannkind commented on GitHub (May 15, 2026): Happy to add to the docs; I should be able to do so later this evening. Otherwise, if a UI change is in order, I'd love to be able to retain the current behavior if the permissions have already been `granted` without requiring _another_ explicit user interaction. Perhaps we can only show the new chip if the permissions are currently 'prompt' (which Safari stupidly returns even when the special setting is Deny) This was a barely tested, very fast change via Claude to try to visualize what I was thinking about. It's not perfect. https://github.com/user-attachments/assets/038d3c2f-780b-4e24-9a4d-39cfc3bba5ea

GiteaMirror commented

2026-05-29 19:08:50 -05:00

@MatissJanis commented on GitHub (May 16, 2026):

If it's that easy to fix, perhaps it should just be in the docs?

We'll get a flood of angry people complaining that their permission selection is not persisting. Sure, we can point all of them to the docs, but I'd prefer to nip it in the bud: by default not have the permission window pop up each time you try to enter a transaction (i.e. the current behaviour we already have when the location feature is disabled).

@mannkind that looks good! As long as we can stop the permission window from popping up all the time (without pointing people to docs) - that's golden!

@MatissJanis commented on GitHub (May 16, 2026): > If it's that easy to fix, perhaps it should just be in the docs? We'll get a flood of angry people complaining that their permission selection is not persisting. Sure, we can point all of them to the docs, but I'd prefer to nip it in the bud: by default not have the permission window pop up each time you try to enter a transaction (i.e. the current behaviour we already have when the location feature is disabled). @mannkind that looks good! As long as we can stop the permission window from popping up all the time (without pointing people to docs) - that's golden!

Sign in to join this conversation.

Branches Tags

master

dependabot/npm_and_yarn/npm_and_yarn-cd62b4b37a

enforce-append-only-migrations-ci

claude/error-codes-worker-boundary-26i5uu

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

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/actual#100249