github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 07:01:45 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[Feature] track statement balance separately for credit cards #1159

New Issue
Closed
opened 2026-02-28 19:34:17 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-02-28 19:34:17 -06:00
Owner
Copy Link

Originally created by @citrus-it on GitHub (Jun 21, 2024).

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?

As I am using Actual to keep track of my finances, I find I am having to manually keep my credit card balances in mind (or on scraps of paper) so that I know how much will be taken on the payment date. It is quite common for a credit card balance to be double the payment amount because they are offset by two weeks. As an illustration:

  • 15th of the month, balance £500 (statement date)
  • 30th of the month, balance £1100 (payment date)
  • 1st of the month, balance £600 (payment has been taken)

As I approach the 30th, Actual shows that I have £1100 pending on my credit card, and I see the upcoming schedule for the payment, yet I only need to ensure that I have £500 in my current account to cover it. This is when I need to check back and confirm how much will be taken. It would be great if Actual could aid here.

I've tried various things to manage this and I currently have each credit card represented as two separate accounts. I transfer the statement amount from one to the other on the statement date, then record the payment against the second when it occurs. This is not too bad but more manual than I'd like and I have to deal with the payment appearing on what is now the wrong account via sync.

Describe your ideal solution to this problem

Fundamentally I want to be able to look at the list of accounts and upcoming payments and verify I'm not going to go overdrawn.

Internally that could look like a new flag on each transaction which indicates whether it has been statemented, then an option to show the statemented balance alongside the normal balance against the account, as well as setting a date when all transactions in the account should be automatically marked as statemented. For non credit-card accounts, or where you don't care, one would just not set such a statement date.

Teaching and learning

No response

Originally created by @citrus-it on GitHub (Jun 21, 2024). ### Verified feature request does not already exist? - [X] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? As I am using Actual to keep track of my finances, I find I am having to manually keep my credit card balances in mind (or on scraps of paper) so that I know how much will be taken on the payment date. It is quite common for a credit card balance to be double the payment amount because they are offset by two weeks. As an illustration: - 15th of the month, balance £500 (statement date) - 30th of the month, balance £1100 (payment date) - 1st of the month, balance £600 (payment has been taken) As I approach the 30th, Actual shows that I have £1100 pending on my credit card, and I see the upcoming schedule for the payment, yet I only need to ensure that I have £500 in my current account to cover it. This is when I need to check back and confirm how much will be taken. It would be great if Actual could aid here. I've tried various things to manage this and I currently have each credit card represented as two separate accounts. I transfer the statement amount from one to the other on the statement date, then record the payment against the second when it occurs. This is not too bad but more manual than I'd like and I have to deal with the payment appearing on what is now the wrong account via sync. ### Describe your ideal solution to this problem Fundamentally I want to be able to look at the list of accounts and upcoming payments and verify I'm not going to go overdrawn. Internally that could look like a new flag on each transaction which indicates whether it has been statemented, then an option to show the statemented balance alongside the normal balance against the account, as well as setting a date when all transactions in the account should be automatically marked as statemented. For non credit-card accounts, or where you don't care, one would just not set such a statement date. ### Teaching and learning _No response_
GiteaMirror added the needs votesfeature labels 2026-02-28 19:34:17 -06:00
GiteaMirror commented 2026-02-28 19:34:18 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 21, 2024):

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

@github-actions[bot] commented on GitHub (Jun 21, 2024): :sparkles: Thanks for sharing your idea! :sparkles: 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 👍! <!-- feature-auto-close-comment -->
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
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label feature needs votes
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#1159
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?