mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-16 07:04:23 -05:00
[GH-ISSUE #7061] [Feature] Check Printing #72703
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#72703
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 @ccaffee1 on GitHub (Feb 23, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7061
Verified feature request does not already exist?
💻
Pitch: what problem are you trying to solve?
I would like to enter and print, using stock forms, each check I issue whether in payment of an invoice or ad hoc.
Describe your ideal solution to this problem
Add a register entry screen where individual checks can be recorded for either immediate print or deferred print to any system printer using stock pre-printed forms (e.g. QuickBooks, Quicken, etc.). The system will require cross reference to any invoice, account distribution, cleared, reconciled, void statuses that apply.
Teaching and learning
Add description of sample transactions for each type of check processed.
@github-actions[bot] commented on GitHub (Feb 23, 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 👍!
@ccaffee1 commented on GitHub (Feb 23, 2026):
I'm sorry. I'm a newbie to this environment.
Is there something further I need to do for the idea to be considered ?
@db-src commented on GitHub (Feb 23, 2026):
Solicit upvotes and supportive comments on it, stake a bounty for someone to implement a PR for it, etc.
I can't imagine this will get far though as it sounds like something for an accounting/warehousing/DMS type of system, rather than for a relatively simple personal budgeting and account tracking system.