aherman
/
gnucash
mirror of https://github.com/Gnucash/gnucash
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

updates to scheduled transactions

Browse Source 
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@2305 57a11ea4-9604-0410-9ed3-97b8803252fd
zzzoldreleases/1.4
Linas Vepstas 26 years ago
parent 58e39d730c
commit d47efdbfdb
1 changed files with 176 additions and 42 deletions
Show Stats Download Patch File Download Diff File

218
doc/html/C/projects.html
Unescape View File

@ -450,13 +450,6 @@
<td>Medium</td>
</tr>
<tr>
<td><a href="#bond">Bonds and Interest Bearing
Instruments</a></td>
<td>Small</td>
</tr>
<tr>
<td><a href="#401K">401K etc.</a></td>
@ -481,6 +474,12 @@
<td>Medium</td>
</tr>
<tr>
<td><a href="#overdraft">Overdraft Alerts</a></td>
<td>Small</td>
</tr>
<tr>
<td><a href="#alerts">Alerts, Recurring
Transactions</a></td>
@ -791,6 +790,18 @@ we've been, and where we're going.
</dd>
<dt><b>Documentation</b></dt>
<dd>
Need to add a 'meta keyword' tag to the documetnatin pages,
this will help the search engine (e.g.
<a href="http://www.htdig.org/">htdig</a>) better categorize
the help.
<a href="http:///www.senga.org/mifluz/html/">Mifluz</a> might
be more embeddable ...
<p>
</p>
</dd>
<a name="glitz">
<dt><b>Themes, Icons, Glitz</b></dt>
</a>
@ -853,6 +864,58 @@ we've been, and where we're going.
should be treated.</p>
</li>
<li>
<p>
<b>More account types</b>
Introduce more 'fundamental' account types: (ammortized) Loan,
Mortgage, ESOP, House, Line of Credit.
</p>
</li>
<li>
<p>
<b>Bank name in combo-box pull-down</b>
When user enters a new bank name, should be presented with
a combo-box listing other bank-account names ...
(note this may require implementation of engine callbacks
so that relevent code can be informed when there are new
bank names?)
</p>
</li>
<li>
<p>
<b>Currency Selection Popup</b>
Currency field should get preplaced by menu of long-hand
currency names, three-letter ISO abbreviations, and symbols.
User should be able to add new currency types.
Should also keep a static exchange-rate table.
</p>
</li>
<li>
<p>
<b>Popup Calculator</b>
All price/amount fields should pop up a calculator widget;
output of calculator gets entered in field.
</p>
</li>
<li>
<p>
<b>Popup Calender</b>
All date fields should pop up a calender widget;
selected date should get entered in field.
</p>
</li>
<li>
<p>
<b>Register View</b>
Allow user to view only non-reconciled transactions ...
</p>
</li>
<li>
<p>
<b>Wizards/Context sensitive help</b>.
@ -944,6 +1007,11 @@ we've been, and where we're going.
multiple charts ...
</ul>
</p>
<p> <b>Status:</b>
<ul>
<li>A mini-design doc exists in src/engine/future.txt
</ul>
</p>
</dd>
@ -1034,31 +1102,19 @@ we've been, and where we're going.
</dd>
<a name="bond">
<dt><b>Bonds and Interest Bearing Instruments</b></dt>
</a>
<dd>
Support should be added for Mortgages, Bonds, CD's and
other instruments (e.g. savings accounts) that pay interest
on a regular basis. It should be possible to specify the
interest rate, the payment schedule, and other regularly
recurring transactions.
<p> This should be handled by having a way of bouncing out
to some Guile code to generate transactions with computed
values.
</p>
</dd>
<a name="401K">
<dt><b>401(k), RSP</b></dt>
</a>
<dd>Retirement Savings Plans often do not put a high priority
<dd>
401K, 403, IRA, Roth IRA, SEP, Keogh ... "Retirement Savigs
Plans"
<p>
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.
necessity to track capital gains. (huh??)
</p>
</dd>
<dt><a name="note"><b>Annotate with News Stories</b></a></dt>
@ -1068,6 +1124,8 @@ we've been, and where we're going.
Provide a way of storing news stories with accounts, and
possibly annotating individual transactions in the same
way.
<p>
</p>
</dd>
@ -1087,31 +1145,107 @@ we've been, and where we're going.
</dd>
<dt><a name="alerts"><b>Alerts, Recurring Transactions</b></a></dt>
<dt><a name="overdraft"><b>Overdraft Alerts</b></a></dt>
<dd>
Provide pop-up notification of deadlines, events, upcoming
payments.
Overdraft alerts are popups that pop up whenever the user
enters a transaction that would move an account below some
minimum balance, or above some max balance (for a bank account)
or an expense/spending limit is reached (on an expense account).
A similar but different alert can be implenmented for price highs
&amp; lows. Note that these alerts do *not* require any sort of
calendering or recurring transaction support.
<p>
Design requirements: implement multiple (not just two) alerts
for any account type. Alert should consist of (1) value point
or price point, (2) movement direction (3) 'is active' boolean
flag (i.e. Should be possible to 'turn off alert' without
deleting it) (4) memo text.
</p>
<p> <b>Status:</b>
<p> Add support for automatic, recurring transactions, <em>
e.g.</em> mortgage payments, fixed-interest bonds, bank
accounts, etc.</p>
<ul>
<li>Not Started.</li>
</ul>
</p>
<p> Note that the design for this could be very different,
depending on whether the multi-user functions are available
or not.</p>
</dd>
<p> Design/implementation for this is tricky. It should
probably leverage <tt>crontab</tt>, but this can lead to
difficulties and bugs.</p>
<dt><a name="alerts">
<b>Recurring Transactions, Calander Alerts</b></a></dt>
<dd>
Add support for automatic, recurring transactions, <em>
e.g.</em> mortgage payments, fixed-interest bonds, regular
salary checks, regular gas/phone/electric bills, <em>etc.</em>
<p>
Loans & mortgages are one of the more complicated recurring
transactions. Consider the following dialogue layout:
<pre>
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
</pre>
Note that in the above, not all fields are independent:
some can be calculated from others.
The <tt>other payment</tt> should bring up a mini-register,
allowing user to add any number of splits.
</p>
<p>
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).
</p>
<p>
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 due,
insurance renewal dates, domain registration renewal dates,
ISP contract expiration date :-). These may or may not
be associated with transactions. Memoes should be possible.
Popups should happen when dates get close. Technology:
need to find/evaluate gnome-calender/dayplanner for
integration.
</p>
<p>
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 (!?)
</p>
<p><b>Design Notes:</b>
Most alerts & data storage should be driven out of the engine.
This will enable multi-user, distributed use.
<b>Note:</b> alerts should be piggy-backed on a general alert
infrastructure within the engine, viz, registered callbacks
when balances change, so that windows can be redrawn.
Not clear on if/how calander events might be server-ified.
(On the other hand, a good calander should be server-ified,
and thus viewable by secretaries, co-orkers, etc.)
</p>
<p>More complex financial instrucments may need a guile-based
extension mechanism to compute values .... simple
interest/mortgage calculators should be done in C in
the engine ...
<p> May need interfaces to email for emailed alerts.</p>
<p> Interfaces into calendaring systems?
<p>Plot forcast graphs based on scheduled income & opayments ...
is this tied into budgeting ????
<p><b>Status:</b>
<ul>
<li>Duhh ...
<li>Need to create design doc, need to implement engine
pieces, need to hunt down gnome-calandering bonobo.
</ul>
</p>
@ -1511,7 +1645,7 @@ etc ...
<li>Binary file I/O mostly detangled into a separate
module.</li>
<li>Crude transaction logging in place; should be
<li>Crude transaction logging/auditing in place; should be
suitable for error/crash recovery but has not been "tried
by fire."</li>

Write Preview
Loading…
Cancel
Save