From c285636a4d77dad91bcc216c0d3f2a3c42abcf47 Mon Sep 17 00:00:00 2001
From: Linas Vepstas
Feature
-
Sizing
+ Responsible
@@ -388,152 +388,198 @@
Internationalization
Small
+ Dave
Reports
Small
+
Graphs
Medium
+ Guppi/Bill
-
Simplified Stock Ledger
+ Simplified Ledger
Small
+ Dave,Linas
Themes, Icons, Glitz
Medium
+
-
Books, Accounting Periods
+ Miscellaneous Small Tasks
- Small
+ Medium
+
-
Check Printing
+ Alerts, Recurring
+ Transactions
- Small
+ Medium
+ RLB
-
User Preferences
+ Budgeting
Medium
+ Dave
-
+
+ Extension Language Support
+ Check Printing
+
+ Small
+ Grib
+
+
User Preferences/Session Mgmt.
Medium
+
-
401K etc.
+ Quicken(TM) Import
Small
+ Grib
-
Annotate with Investment News
+ Quicken(TM) Export
Small
+ Grib
-
Loan and Mortgage Calculators
+ Books, Accounting Periods
Small
+ Linas
-
Budgeting
+ Multiple Currencies
Medium
+ Rethink Requirements-Linas
-
+
+ Overdraft Alerts
+ Extension Language Support
+
+ Medium
+ RLB
+
+
Stock Quotes, Price Quotes
Small
+ RLB
-
Alerts, Recurring
- Transactions
+ Install
- Medium
+ Small ?
+
-
Quicken(TM) Import
+ Forced Double Entry
Small
+
-
Quicken(TM) Export
+ 401K etc.
Small
+
-
Stock Quotes, Price Quotes
+ Documentation
Small
+
-
Technical Stock Analysis
+ Annotate with Investment News
- Medium
+ Small
+
-
Depreciation, Sinking Funds
+ Loan and Mortgage Calculators
- Medium
+ Small
+
-
OFX, Online Banking, Trading,
- Bill-pay
+ Overdraft Alerts
- Large
+ Small
+
-
Multiple Currencies
+ Technical Stock Analysis
Medium
+
-
+
+ Double Entry Accounting
+ Depreciation, Sinking Funds
- Small
+ Medium
+
+
+
OFX, Online Banking, Trading,
+ Bill-pay
+
+ Large
+ Dave
Tab-delimited ASCII export
Small
+
Tax Preparation
Large
+
@@ -541,12 +587,14 @@
organizers
Medium
+
@@ -559,6 +607,7 @@
Emergency Records Organizer
Small
+
Feature
Sizing
+ Responsible
@@ -571,18 +620,21 @@
Objects
Large
+
SQL I/O
Medium
+ Linas
Multi-User Support
Medium
+
@@ -590,30 +642,35 @@
Receivable
Medium
+
Payroll
Medium
+
Invoicing
Medium
+
Job Costing
Medium
+
Expense Accounts
Large
+
@@ -697,6 +754,8 @@
report, Market Index report, Stock Option values,
Estimation of capital gains tax liabilities.
Reports should be printable to printer.
+Status:
Graphs should be printable to printer.
Status:
Multi-Line splits look confusing when viewed from + Income/Expense Accounts. +
+Stock splits & reverse splits are not displayed correctly. +
+Currency trading Ledger is confusing. +
+Stocks and Mutual funds are handled by placing them each in their own account. Each account can be viewed individually. If all of the stock accounts are children of a master @@ -790,21 +862,22 @@ general ledger window is a bit obtuse, and difficult to understand and use. A simplified but still powerful ledger window is desperately needed. +
-Question: How to most simply allow the user to - enter loads and fees?
- -Answer: Through splits. Unfortunately, some users - may not properly understand splits, at least not initially. +
How to most simply allow the user to + enter loads and fees? + Through multi-line transactions. Unfortunately, some users + may not properly understand multi-line transactions, + at least not initially. Thus, a little popup is needed to allow the user to type in the sales load or fee and such, and then auto-create the - needed splits.
+ needed journal entries.Note the current transfer window does NOT allow a share price to be specified !! Needs fixing ...
Hint-of-the-Day. A collection of a some 50-100 hints-of-the-day: short (2-4 sentance) hints/tips on how to use gnucash. Every time the user - starts gnucash, an new hint shows up ...
+ starts gnucash, an new hint shows up ... + Status: Dave volunteers... +Cut-n-paste Cut-n-paste of items in the - regsiter window...
+Cut-n-paste Cut-n-paste of whole transactions + in the regsiter window... Status:Dave... Done. (in + 1.4.0)
File Format. Rework miscellaneous file storage to + use Sleepy Cat DB. + Status: RLB, 2 weeks. +
+Reconcile Window. + Status: Dave. +
+Print Register Window. Output register window to + printer. + Status: none +
+gtkhtml. Grib. +
+print. Grib. +
+key-val pairs. Grib. +
+guid in fileio. Dave. +
+Engine validity test suite. +
+Reconcile groups. +
+# of decimal places in prices (penny stock). +
+Retirement Savings Plans often do not put a high - priority on tracking costs, as the tax implication is that - amounts are taxable upon withdrawal, meaning that there is - little necessity to track capital gains. (huh??)
-Provide a way of storing news stories with accounts, and - possibly annotating individual transactions in the same - way.
-Status:
- -Design requirements: implement multiple (not just two) - alerts for any account type. Alert should consist of
- -Status:
- -Loans & mortgages are one of the more complicated - recurring transactions. Consider the following dialogue - layout:
--loan amount $_____________ currency _________ (pull-down menu) -Remaining balance $___________ -Payment amount $___________ -balloon payment $_____________ -other payment $________ (e.g. escrow, tax) -Payment frequency (weekly/monthly/bimonthly/quarterly/yearly) -loan start date mm/dd/yy length -----(weeks/months/years/peyments) -loan time left (number of days/weeks/months, rounded) -number of payments left -interest rate %__________________ -payee ____________ -pay-from account __________________ -next due date mm/dd/yy -- Note that in the above, not all fields are independent: - some can be calculated from others. The other - payment should bring up a mini-register, allowing user - to add any number of splits.
Recurring bills, salary income, etc. are simpler to +
(2) Recurring bills, salary income, etc. are simpler to handle, since they don't have intersest rates, balloons, etc. They do/will have multiple splits (e.g. payroll gross, fica, futa, income taxes, payroll net).
-Provide a calender-display of upcoming & past +
(3)Provide list of upcoming & recently paid + bills/scheduled payments/scheduled deposits for the next + 1,2,3,6,12 months. Historical view shows payments crossed + out (!?)
+ +(4)Loans & mortgages are one of the more complicated + recurring transactions. Typically, there might be a years + worth of smaller payments, then a long string of larger + payments, followed by a baloon. +
+ +(5)Provide a calender-display of upcoming & past scheduled payments. Clicking on a calander day should raise up editable list of transactions. Calendering should include generic red-lettering of important dates: taxes @@ -1276,11 +1317,6 @@ next due date mm/dd/yy Technology: need to find/evaluate gnome-calender/dayplanner for integration.
-Provide list of upcoming & recently paid - bills/scheduled payments/scheduled deposits for the next - 1,2,3,6,12 months. Historical view shows payments crossed - out (!?)
-Design Notes: Most alerts & data storage should be driven out of the engine. This will enable multi-user, distributed use. Note: alerts should be @@ -1308,6 +1344,7 @@ next due date mm/dd/yy
Status:
Note that since banks use QIF, the correct + Note that since banks use QIF, the correct way to reconcile bank accounts on-line is through - QIF.
- -On one side, we have existing recorded transactions; + QIF. + On one side, we have existing recorded transactions; on the other, the latest bank statement, in QIF - format.
- -Now, just put them together ...
+ format. + Now, just put them together ... + Grib estimates 2 weeks for this. +A simplfied way of dealing with one-shot currency + exchanges needs to be implemented, essentially just a + simple calculator popup.
+ ++ Status: Need to rethink wether the one-shot exchanges + should in fact be recorded full-fledged in the engine. + Also: EURO support is currently hacked in: the EURO is treated as + a 'special' currency. Virtually all the euro code can be fully + generalized (and should be). +
+ +Double-entry is a powerful way of ensuring the integrity + of of the financial data. Currently, while double-entry is + supported, its use is not enforced: the user can + create dangling transactions, where only one account is + indicated.
+ +Although this is acceptable for home use (arguably + desirable, since it allows the casual user the simplicity + they desire), it is not acceptable for business use. (The + counterargument is that casual users that aren't + accountants need all the help at getting things right that + they can get.)
+ +It must be possible to enforce double entry, so that a + transaction cannot be completed until two accounts have + been specified.
+ +Restricted Double Note that sometimes, the words + 'single-entry' have a an alternate meaning: they can mean + 'a double entry account which can only be credited, or + debited, but not both'. We need to implement this.
+ +Current status:
+ +Retirement Savings Plans often do not put a high + priority on tracking costs, as the tax implication is that + amounts are taxable upon withdrawal, meaning that there is + little necessity to track capital gains. (huh??)
+Provide a way of storing news stories with accounts, and + possibly annotating individual transactions in the same + way.
+Consider the following dialogue layout:
++loan amount $_____________ currency _________ (pull-down menu) +Remaining balance $___________ +Payment amount $___________ +balloon payment $_____________ +other payment $________ (e.g. escrow, tax) +Payment frequency (weekly/monthly/bimonthly/quarterly/yearly) +loan start date mm/dd/yy length -----(weeks/months/years/payments) +loan time left (number of days/weeks/months, rounded) +number of payments left +interest rate %__________________ +payee ____________ +pay-from account __________________ +next due date mm/dd/yy ++ Note that in the above, not all fields are independent: + some can be calculated from others. The other + payment should bring up a mini-register, allowing user + to add any number of splits.
Status:
+ +Design requirements: implement multiple (not just two) + alerts for any account type. Alert should consist of
+ +Status:
+ +Work is needed in the GUI. The engine currently supports - multiple currencies by treating them as securities, thus - allowing currency trading. The currency-trading register - needs a complete overhaul as it is obtuse and - unintuitive.
- -A simplfied way of dealing with one-shot currency - exchanges needs to be implemented, essentially just a - simple calculator popup.
-Double-entry is a powerful way of ensuring the integrity - of of the financial data. Currently, while double-entry is - supported, its use is not enforced: the user can - create dangling transactions, where only one account is - indicated.
- -Although this is acceptable for home use (arguably - desirable, since it allows the casual user the simplicity - they desire), it is not acceptable for business use. (The - counterargument is that casual users that aren't - accountants need all the help at getting things right that - they can get.)
- -It must be possible to enforce double entry, so that a - transaction cannot be completed until two accounts have - been specified.
- -Restricted Double Note that sometimes, the words - 'single-entry' have a an alternate meaning: they can mean - 'a double entry account which can only be credited, or - debited, but not both'. We need to implement this.
- -Current status:
- -Linas Vepstas
+ Draft version 0.38 -- June 2000
+ Linas Vepstas
linas@linas.org
-
updates by Christopher Browne cbbrowne@ntlug.org
-