mirror of
https://github.com/Gnucash/gnucash.git
synced 2025-02-25 18:55:30 -06:00
Christopher Browne's doc updates.
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@2344 57a11ea4-9604-0410-9ed3-97b8803252fd
This commit is contained in:
parent
c1fa12bf8b
commit
ee14e57cd0
@ -1,41 +1,46 @@
|
||||
<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 2.0//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<title>Importing MYM Files</title>
|
||||
</head>
|
||||
<body>
|
||||
<h1>Managing Your Money --> GnuCash</h1>
|
||||
<head>
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
|
||||
I have finally put the Perl script that allowed me to use GnuCash
|
||||
up on a web site. I had a couple years of data in Managing Your
|
||||
Money 2.x that I didn't want to reenter. The script will output a
|
||||
single QIF file with all transactions, accounts, and categories.
|
||||
(Currently only non-investment transactions are handled.) The QIF
|
||||
file can be imported to xacc-1.0.18 if a small patch is applied to
|
||||
QIFIO.c. The site is
|
||||
<title>Importing MYM Files</title>
|
||||
</head>
|
||||
|
||||
<p> <a href="http://www-cad.eecs.berkeley.edu/~gooch/mymdump.html">
|
||||
MyMdump</a></p>
|
||||
<body>
|
||||
<h1>Managing Your Money --> GnuCash</h1>
|
||||
I have finally put the Perl script that allowed me to use
|
||||
GnuCash up on a web site. I had a couple years of data in
|
||||
Managing Your Money 2.x that I didn't want to reenter. The
|
||||
script will output a single QIF file with all transactions,
|
||||
accounts, and categories. (Currently only non-investment
|
||||
transactions are handled.) The QIF file can be imported to
|
||||
xacc-1.0.18 if a small patch is applied to QIFIO.c. The site is
|
||||
|
||||
|
||||
<h1>Duplicate Transactions</h1>
|
||||
<p><a href=
|
||||
"http://www-cad.eecs.berkeley.edu/~gooch/mymdump.html">
|
||||
MyMdump</a></p>
|
||||
|
||||
I also have a script that I use to remove duplicate transactions at
|
||||
the QIF level. I use this script because Xacc is very strict about
|
||||
duplicates (which is good) and because editing imported
|
||||
transactions will cause a re-import of the same transactions to
|
||||
produce duplicates. (I download the same month's transactions from
|
||||
my bank several times each month, so each downloaded QIF
|
||||
file--after the first--contains transactions I have already
|
||||
imported. I don't want to rely on the bank sending me the
|
||||
transactions in the same order or with the same formatting.) The
|
||||
site is
|
||||
<h1>Duplicate Transactions</h1>
|
||||
I also have a script that I use to remove duplicate
|
||||
transactions at the QIF level. I use this script because Xacc
|
||||
is very strict about duplicates (which is good) and because
|
||||
editing imported transactions will cause a re-import of the
|
||||
same transactions to produce duplicates. (I download the same
|
||||
month's transactions from my bank several times each month, so
|
||||
each downloaded QIF file--after the first--contains
|
||||
transactions I have already imported. I don't want to rely on
|
||||
the bank sending me the transactions in the same order or with
|
||||
the same formatting.) The site is
|
||||
|
||||
<p> <a href="http://www-cad.eecs.berkeley.edu/~gooch/qifuniq.html">
|
||||
qifuniq</a></p>
|
||||
<p><a href=
|
||||
"http://www-cad.eecs.berkeley.edu/~gooch/qifuniq.html">
|
||||
qifuniq</a></p>
|
||||
|
||||
<p> I hope others find these scripts useful.</p>
|
||||
<p>I hope others find these scripts useful.</p>
|
||||
|
||||
<p>Ken Yamaguchi October 1998</p>
|
||||
</body>
|
||||
<p>Ken Yamaguchi October 1998</p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
|
File diff suppressed because it is too large
Load Diff
@ -2,7 +2,8 @@
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>About GnuCash</title>
|
||||
@ -11,11 +12,11 @@
|
||||
<body>
|
||||
<h1>About GnuCash</h1>
|
||||
|
||||
<p> GnuCash is a program to keep track of your finances. Its
|
||||
<p>GnuCash is a program to keep track of your finances. Its
|
||||
features include:</p>
|
||||
|
||||
<ul>
|
||||
<li><b> Multiple accounts,</b> which can be open at the same
|
||||
<li><b>Multiple accounts,</b> which can be open at the same
|
||||
time. Create an GnuCash account for each of your bank
|
||||
accounts.</li>
|
||||
|
||||
@ -26,15 +27,15 @@
|
||||
<li>
|
||||
<b>A simple user interface.</b>
|
||||
|
||||
<p> If you can use the register in the back of your
|
||||
<p>If you can use the register in the back of your
|
||||
checkbook, you can use <tt>GnuCash.</tt></p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<b> <a href="xacc-recnwin.html"> Automated Tools for
|
||||
<b><a href="xacc-recnwin.html">Automated Tools for
|
||||
Reconciling Accounts.</a></b>
|
||||
|
||||
<p>At the end of the month, open up the <b> reconcile</b>
|
||||
<p>At the end of the month, open up the <b>reconcile</b>
|
||||
window, enter the ending balance from your bank statement,
|
||||
and check off the transactions that appear in the bank
|
||||
statement. This agrees what you have recorded in GnuCash
|
||||
@ -43,10 +44,10 @@
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<b> QuickFill.</b>
|
||||
<b>QuickFill.</b>
|
||||
|
||||
<p> If you begin typing in the description field, and the
|
||||
text matches a previous transaction, hitting <tt> TAB</tt>
|
||||
<p>If you begin typing in the description field, and the
|
||||
text matches a previous transaction, hitting <tt>TAB</tt>
|
||||
will copy in that previous transaction. This is a handy
|
||||
time saver if you regularly create similar
|
||||
transactions.</p>
|
||||
@ -55,20 +56,20 @@
|
||||
<li>
|
||||
<b>Stock/Mutual Fund Portfolios.</b>
|
||||
|
||||
<p> Track stocks individually (one per account) or in
|
||||
<p>Track stocks individually (one per account) or in
|
||||
portfolio of accounts (a group of accounts that can be
|
||||
displayed together).</p>
|
||||
|
||||
<p> There are tools to <a href="xacc-ticker.html">
|
||||
<p>There are tools to <a href="xacc-ticker.html">
|
||||
automatically collect stock quotes.</a></p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Support for <b> <a href="xacc-currency.html"> multiple
|
||||
currencies</a></b> and <b> currency trading accounts.</b>
|
||||
Support for <b><a href="xacc-currency.html">multiple
|
||||
currencies</a></b> and <b>currency trading accounts.</b>
|
||||
(partial, still broken).
|
||||
|
||||
<p> Bank accounts may be established in different
|
||||
<p>Bank accounts may be established in different
|
||||
currencies, and trades at varying exchange rates may be
|
||||
made, in much the same way stocks trade at varying
|
||||
prices.</p>
|
||||
@ -78,34 +79,35 @@
|
||||
<b><a href="xacc-quicken.html#QIF">Quicken File
|
||||
Import</a>.</b>
|
||||
|
||||
<p> Imports Quicken-style QIF files.</p>
|
||||
<p>Imports Quicken-style QIF files.</p>
|
||||
</li>
|
||||
|
||||
<li><b> <a href="xacc-reports.html">Reports</a>.</b> Display
|
||||
or output as HTML Balance, Transaction, and Profit/Loss reports,
|
||||
as well as graphical account balance tracking (requires gnuplot).</li>
|
||||
<li><b><a href="xacc-reports.html">Reports</a>.</b> Display
|
||||
or output as HTML Balance, Transaction, and Profit/Loss
|
||||
reports, as well as graphical account balance tracking
|
||||
(requires gnuplot).</li>
|
||||
</ul>
|
||||
|
||||
<h2>Advanced Features</h2>
|
||||
|
||||
<p> GnuCash offers some features not found in simpler
|
||||
accounting programs.</p>
|
||||
<p>GnuCash offers some features not found in simpler accounting
|
||||
programs.</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<b> <a href="xacc-groups.html"> Account Hierarchy</a></b>
|
||||
<b><a href="xacc-groups.html">Account Hierarchy</a></b>
|
||||
|
||||
<p>A master account can have a hierarchy of more detailed
|
||||
accounts arranged underneath it. This allows related
|
||||
account types (<em>e.g.</em> - Cash, Bank, Stock) to be
|
||||
grouped under one master account (<em> e.g.</em> -
|
||||
grouped under one master account ( <em>e.g.</em> -
|
||||
Assets).</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<b> <a href="xacc-double.html">Double Entry</a></b>
|
||||
<b><a href="xacc-double.html">Double Entry</a></b>
|
||||
|
||||
<p>Every transaction involves two accounts, and <em> each
|
||||
<p>Every transaction involves two accounts, and <em>each
|
||||
transaction</em> is required to balance. This provides
|
||||
assurance that the overall set of books will add up
|
||||
correctly, and prevents out-of-balance errors
|
||||
@ -113,63 +115,63 @@
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<b> <a href="xacc-expense.html"> Income/Expense Account
|
||||
<b><a href="xacc-expense.html">Income/Expense Account
|
||||
Types</a></b>
|
||||
|
||||
<p> Intuit's <a href="xacc-quicken.html"> Quicken</a>
|
||||
product has what they call "categories" that are used to
|
||||
track incomes and expenses. These may be used to create
|
||||
<p>Intuit's <a href="xacc-quicken.html">Quicken</a> product
|
||||
has what they call "categories" that are used to track
|
||||
incomes and expenses. These may be used to create
|
||||
Profit/Loss reports.</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<b> General Ledger</b>
|
||||
<b>General Ledger</b>
|
||||
|
||||
<p> Multiple accounts may be displayed in one register
|
||||
<p>Multiple accounts may be displayed in one register
|
||||
window at the same time. This can make it easier to track
|
||||
down data errors. It also provides a convenient way of
|
||||
viewing a portfolio of many stocks, by showing all
|
||||
transactions in that portfolio.</p>
|
||||
</li>
|
||||
|
||||
<li><b> Handling of <a href="xacc-currency.html"> multiple
|
||||
<li><b>Handling of <a href="xacc-currency.html">multiple
|
||||
currencies</a></b></li>
|
||||
</ul>
|
||||
|
||||
<h2>Versioning</h2>
|
||||
|
||||
<p> The versioning scheme for GnuCash parallels that of the
|
||||
<p>The versioning scheme for GnuCash parallels that of the
|
||||
Linux kernel, where "even" sub-versions indicate versions that
|
||||
are intended to be stable, only seeing maintenance to fix bugs,
|
||||
and "odd" sub-versions indicate an "experimental" stream that
|
||||
seeks to add enhancement.</p>
|
||||
|
||||
<p> The present "experimental" stream is gnucash-1.3.x, which
|
||||
is somewhat unstable.</p>
|
||||
<p>The present "experimental" stream is gnucash-1.3.x, which is
|
||||
somewhat unstable.</p>
|
||||
|
||||
<p> The latest stable release is 1.2.x; if you don't intend to
|
||||
<p>The latest stable release is 1.2.x; if you don't intend to
|
||||
do development work, you should be using either this version,
|
||||
or an older 1.0.x version. These versions are fairly stable,
|
||||
with all currently known bugs fixed.</p>
|
||||
|
||||
<p> Once the 1.3.x series stabilizes, the next stable series
|
||||
<p>Once the 1.3.x series stabilizes, the next stable series
|
||||
will be 1.4.x, and experimentation will likely continue on
|
||||
1.5.x.</p>
|
||||
|
||||
<p> If you wish to "hack" on the experimental version, you
|
||||
<p>If you wish to "hack" on the experimental version, you
|
||||
should first start by reading through the <a href=
|
||||
"projects.html"> GnuCash Project Goals</a> document in order to
|
||||
"projects.html">GnuCash Project Goals</a> document in order to
|
||||
get some perspective on the overall design.</p>
|
||||
|
||||
<h2>Lead Developers</h2>
|
||||
|
||||
<dl>
|
||||
<dt> <a href="mailto:rclark@hmc.edu"> Robin Clark</a></dt>
|
||||
<dt><a href="mailto:rclark@hmc.edu">Robin Clark</a></dt>
|
||||
|
||||
<dd>wrote the original X-Accountant in Motif as a school
|
||||
project, taking it to version 0.9 by October 1997.</dd>
|
||||
|
||||
<dt> <a href="mailto:linas@linas.org"> Linas Vepstas</a></dt>
|
||||
<dt><a href="mailto:linas@linas.org">Linas Vepstas</a></dt>
|
||||
|
||||
<dd>liked what he saw: the GUI was slick, the code was
|
||||
documented and well structured, and it was all GPL'ed. And so
|
||||
@ -183,7 +185,7 @@
|
||||
code completely redesigned and made mostly Motif-(and
|
||||
GUI-)independent. Did some prototype OFX work.</dd>
|
||||
|
||||
<dt> <a href="mailto:jcollins@gnucash.org"> Jeremy
|
||||
<dt><a href="mailto:jcollins@gnucash.org">Jeremy
|
||||
Collins</a></dt>
|
||||
|
||||
<dd>publicized the GnoMoney project widely and broadly, and
|
||||
@ -191,335 +193,343 @@
|
||||
gnucash.org web site, registered the domain, got the initial
|
||||
GTK/gnome code working.</dd>
|
||||
|
||||
<dt> <a href="mailto:rlb@cs.utexas.edu"> Rob
|
||||
Browning</a></dt>
|
||||
<dt><a href="mailto:rlb@cs.utexas.edu">Rob Browning</a></dt>
|
||||
|
||||
<dd>abused everyone for not using perl, and then after we added
|
||||
perl support, dumped perl in favor of
|
||||
guile/scheme support. Rob maintains the build infrastructure,
|
||||
is handling the whole guile/perl extension language thing,
|
||||
and is dealing with configuration and configurability.</dd>
|
||||
<dd>abused everyone for not using perl, and then after we
|
||||
added perl support, dumped perl in favor of guile/scheme
|
||||
support. Rob maintains the build infrastructure, is handling
|
||||
the whole guile/perl extension language thing, and is dealing
|
||||
with configuration and configurability.</dd>
|
||||
|
||||
<dt> <a href="mailto:peticola@cs.ucdavis.edu"> Dave
|
||||
<dt><a href="mailto:peticola@cs.ucdavis.edu">Dave
|
||||
Peticolas</a></dt>
|
||||
|
||||
<dd>hacks obsessively on GnuCash. But he can stop anytime he
|
||||
wants to. Really.</dd>
|
||||
|
||||
<dt> <a href="mailto:grib@billgribble.com"> Bill Gribble
|
||||
</a></dt>
|
||||
<dt><a href="mailto:grib@billgribble.com">Bill
|
||||
Gribble</a></dt>
|
||||
|
||||
<dd>works magic. If your checks print wrong, blame him.
|
||||
If you don't like the amount printed on your checks, blame him.
|
||||
<dd>works magic. If your checks print wrong, blame him. If
|
||||
you don't like the amount printed on your checks, blame him.
|
||||
If you don't like your your bank balances, your bank, or your
|
||||
life, blame him too.
|
||||
</dd>
|
||||
life, blame him too.</dd>
|
||||
</dl>
|
||||
|
||||
<h2>Fixers and Patchers</h2>
|
||||
|
||||
<p> The <em> cast of thousands</em> includes:</p>
|
||||
<p>The <em>cast of thousands</em> includes:</p>
|
||||
|
||||
<dl>
|
||||
<dt> <a href="mailto:arensb@cfar.umd.edu"> Andrew
|
||||
<dt><a href="mailto:arensb@cfar.umd.edu">Andrew
|
||||
Arensburger</a></dt>
|
||||
|
||||
<dd>for FreeBSD and other patches</dd>
|
||||
|
||||
<dt> <a href="mailto:matt_armstrong@bigfoot.com"> Matt
|
||||
<dt><a href="mailto:matt_armstrong@bigfoot.com">Matt
|
||||
Armstrong</a></dt>
|
||||
|
||||
<dd>for misc fixes</dd>
|
||||
|
||||
<dt> <a href="mailto:fred@moremagic.com"> Fred Baube</a></dt>
|
||||
<dt><a href="mailto:fred@moremagic.com">Fred Baube</a></dt>
|
||||
|
||||
<dd>for attempted Java port/MoneyDance</dd>
|
||||
|
||||
<dt> <a href="mailto:dennisb@cs.chalmers.se"> Dennis
|
||||
Björklund</a></dt>
|
||||
<dt><a href="mailto:dennisb@cs.chalmers.se">Dennis
|
||||
Björklund</a></dt>
|
||||
|
||||
<dd>Swedish translation</dd>
|
||||
|
||||
<dt> <a href="mailto:bojsen@worldnet.att.net"> Per Bojsen</a></dt>
|
||||
<dt><a href="mailto:bojsen@worldnet.att.net">Per
|
||||
Bojsen</a></dt>
|
||||
|
||||
<dd>several core dump fixes</dd>
|
||||
|
||||
<dt> <a href="simon.britnell@peace.com"> Simon Britnell</a></dt>
|
||||
<dt><a href="simon.britnell@peace.com">Simon
|
||||
Britnell</a></dt>
|
||||
|
||||
<dd>patch to RPM spec</dd>
|
||||
|
||||
<dt> <a href="http://www.hex.net/~cbbrowne"> Christopher B.
|
||||
<dt><a href="http://www.hex.net/~cbbrowne">Christopher B.
|
||||
Browne</a></dt>
|
||||
|
||||
<dd>for perl stock scripts, Guile-based QIF import code, lots
|
||||
of changes to English documentation, and lots of guile code</dd>
|
||||
of changes to English documentation, and lots of guile
|
||||
code</dd>
|
||||
|
||||
<dt> <a href="mailto:grahamc@zeta.org.au"> Graham
|
||||
<dt><a href="mailto:grahamc@zeta.org.au">Graham
|
||||
Chapman</a></dt>
|
||||
|
||||
<dd>for the xacc-rpts addon package</dd>
|
||||
|
||||
<dt> <a href="mailto:georgec@sco.com"> George Chen</a></dt>
|
||||
<dt><a href="mailto:georgec@sco.com">George Chen</a></dt>
|
||||
|
||||
<dd>for MS-Money QIF support</dd>
|
||||
|
||||
<dt> <a href="mailtochina@thewrittenword.com">Albert
|
||||
<dt><a href="mailtochina@thewrittenword.com">Albert
|
||||
Chin-A-Young</a></dt>
|
||||
|
||||
<dd>configure.in patch</dd>
|
||||
|
||||
<dt> <a href="mailto:jcollins@gnucash.org"> Jeremey
|
||||
<dt><a href="mailto:jcollins@gnucash.org">Jeremey
|
||||
Collins</a></dt>
|
||||
|
||||
<dd>for GnoMoney and GTK port</dd>
|
||||
|
||||
<dt> <a href="mailto:mcondell@bbn.com"> Matthew Condell</a></dt>
|
||||
<dt><a href="mailto:mcondell@bbn.com">Matthew
|
||||
Condell</a></dt>
|
||||
|
||||
<dd>FreeBSD patch</dd>
|
||||
|
||||
<dt> <a href="mailto:pcondon@rackspace.com"> Patrick
|
||||
<dt><a href="mailto:pcondon@rackspace.com">Patrick
|
||||
Condron</a></dt>
|
||||
|
||||
<dd>for webserver and T1 connection.</dd>
|
||||
|
||||
<dt> <a href="mailto:Ciaran.Deignan@bull.net"> Ciaran
|
||||
<dt><a href="mailto:Ciaran.Deignan@bull.net">Ciaran
|
||||
Deignan</a></dt>
|
||||
|
||||
<dd>for AIX binary version</dd>
|
||||
|
||||
<dt> <a href="mailto:tyson@tyse.net"> Tyson Dowd</a></dt>
|
||||
<dt><a href="mailto:tyson@tyse.net">Tyson Dowd</a></dt>
|
||||
|
||||
<dd>for config/make patches and debian maintenance</dd>
|
||||
|
||||
<dt> <a href="mailto:ripley@xs4all.nl"> Koen D'Hondt</a></dt>
|
||||
<dt><a href="mailto:ripley@xs4all.nl">Koen D'Hondt</a></dt>
|
||||
|
||||
<dd>for Solaris patches to XmHTML</dd>
|
||||
|
||||
<dt> <a href="mailto:bob@mostly.com"> Bob Drzyzgula</a></dt>
|
||||
<dt><a href="mailto:bob@mostly.com">Bob Drzyzgula</a></dt>
|
||||
|
||||
<dd>for budgeting design notes</dd>
|
||||
|
||||
<dt> <a href="mailto:pjf@schools.net.au"> Paul Fenwick</a></dt>
|
||||
<dt><a href="mailto:pjf@schools.net.au">Paul Fenwick</a></dt>
|
||||
|
||||
<dd>ASX support</dd>
|
||||
|
||||
<dt> <a href="mailto:hfiguiere@teaser.fr"> Hubert Figuiere</a></dt>
|
||||
<dt><a href="mailto:hfiguiere@teaser.fr">Hubert
|
||||
Figuiere</a></dt>
|
||||
|
||||
<dd>patch to gnc-prices</dd>
|
||||
|
||||
<dt> <a href="mailto:ju_finck@mail.netwave.de"> Jan-Uwe
|
||||
<dt><a href="mailto:ju_finck@mail.netwave.de">Jan-Uwe
|
||||
Finck</a></dt>
|
||||
|
||||
<dd>for German message translation</dd>
|
||||
|
||||
<dt> <a href="mailto:rjf@aracnet.com"> Ron Forrester</a></dt>
|
||||
<dt><a href="mailto:rjf@aracnet.com">Ron Forrester</a></dt>
|
||||
|
||||
<dd>for gnome patches</dd>
|
||||
|
||||
<dt> <a href="mailto:DFreese@osc.uscg.mil"> Dave
|
||||
<dt><a href="mailto:DFreese@osc.uscg.mil">Dave
|
||||
Freese</a></dt>
|
||||
|
||||
<dd>for leap-year fix</dd>
|
||||
|
||||
<dt> <a href="mailto:grib@billgribble.com"> Bill Gribble</a></dt>
|
||||
<dt><a href="mailto:grib@billgribble.com">Bill
|
||||
Gribble</a></dt>
|
||||
|
||||
<dd>qif importation code</dd>
|
||||
|
||||
<dt> <a href="mailto:otto@bug.redhat.com"> Otto
|
||||
<dt><a href="mailto:otto@bug.redhat.com">Otto
|
||||
Hammersmith</a></dt>
|
||||
|
||||
<dd>for RedHat RPM packaging</dd>
|
||||
|
||||
<dt> <a href="mailto:offby1@blarg.net"> Eric Hanchrow</a></dt>
|
||||
<dt><a href="mailto:offby1@blarg.net">Eric Hanchrow</a></dt>
|
||||
|
||||
<dd>updated currency documentation</dd>
|
||||
|
||||
<dt> <a href="mailto:haral@codec.ro"> Alexandru
|
||||
<dt><a href="mailto:haral@codec.ro">Alexandru
|
||||
Harsanyi</a></dt>
|
||||
|
||||
<dd>for fixing miscellaneous core dumps and lockups.</dd>
|
||||
|
||||
<dt> <a href="mailto:john@dhh.gt.org"> John Hasler</a></dt>
|
||||
<dt><a href="mailto:john@dhh.gt.org">John Hasler</a></dt>
|
||||
|
||||
<dd>engine patch</dd>
|
||||
|
||||
<dt> <a href="mailto:jk@isdn-a33.itea.ntnu.no"> Jon K}re
|
||||
<dt><a href="mailto:jk@isdn-a33.itea.ntnu.no">Jon K}re
|
||||
Hellan</a></dt>
|
||||
|
||||
<dd>for fixing miscellaneous core dumps and lockups.</dd>
|
||||
|
||||
<dt> <a href="mailto:PrakashK@bigfoot.com"> Prakash
|
||||
<dt><a href="mailto:PrakashK@bigfoot.com">Prakash
|
||||
Kailasa</a></dt>
|
||||
|
||||
<dd>for gnome build fixes</dd>
|
||||
|
||||
<dt> <a href="mailto:tkludy@csd.sgi.com"> Tom Kludy</a></dt>
|
||||
<dt><a href="mailto:tkludy@csd.sgi.com">Tom Kludy</a></dt>
|
||||
|
||||
<dd>for SGI Irix port</dd>
|
||||
|
||||
<dt> <a href="mailto:sk@xgm.de"> Sven Kuenzler</a></dt>
|
||||
<dt><a href="mailto:sk@xgm.de">Sven Kuenzler</a></dt>
|
||||
|
||||
<dd>for SuSE README file</dd>
|
||||
|
||||
<dt><a href="mailto:blarsen@ada-works.com"> Bryan Larsen</a></dt>
|
||||
<dt><a href="mailto:blarsen@ada-works.com">Bryan
|
||||
Larsen</a></dt>
|
||||
|
||||
<dd>guile budget report</dd>
|
||||
|
||||
<dt> <a href="mailto:mellon@andare.fugue.com"> Ted
|
||||
<dt><a href="mailto:mellon@andare.fugue.com">Ted
|
||||
Lemon</a></dt>
|
||||
|
||||
<dd>for NetBSD port</dd>
|
||||
|
||||
<dt> <a href="mailto:y-le-ny@ifrance.com"> Yannick Le
|
||||
<dt><a href="mailto:y-le-ny@ifrance.com">Yannick Le
|
||||
Ny</a></dt>
|
||||
|
||||
<dd>pour la traduction en Français</dd>
|
||||
|
||||
<dt> <a href="mailto:glikely@nortelnetworks.com"> Grant
|
||||
<dt><a href="mailto:glikely@nortelnetworks.com">Grant
|
||||
Likely</a></dt>
|
||||
|
||||
<dd>gnome and engine patches</dd>
|
||||
|
||||
<dt> <a href="mailto:martinh@pegasus.cc.ucf.edu"> Heath
|
||||
<dt><a href="mailto:martinh@pegasus.cc.ucf.edu">Heath
|
||||
Martin</a></dt>
|
||||
|
||||
<dd>major work on the gnome register</dd>
|
||||
|
||||
<dt> <a href="mailto:mgmartin@abacusnet.net"> Matt
|
||||
<dt><a href="mailto:mgmartin@abacusnet.net">Matt
|
||||
Martin</a></dt>
|
||||
|
||||
<dd>guile error handling code</dd>
|
||||
|
||||
<dt> <a href="mailto:rgmerk@mira.net"> Robert Graham
|
||||
<dt><a href="mailto:rgmerk@mira.net">Robert Graham
|
||||
Merkel</a></dt>
|
||||
|
||||
<dd>reporting, gnome, and configuration patches.</dd>
|
||||
|
||||
<dt> <a href="mailto:mooney@dogbert.cc.ndsu.NoDak.edu"> Tim
|
||||
<dt><a href="mailto:mooney@dogbert.cc.ndsu.NoDak.edu">Tim
|
||||
Mooney</a></dt>
|
||||
|
||||
<dd>port to alpha-dec-osf4.0f</dd>
|
||||
|
||||
<dt> <a href="mailto:gam3@ann.softgams.com"> G. Allen Morris
|
||||
<dt><a href="mailto:gam3@ann.softgams.com">G. Allen Morris
|
||||
III</a></dt>
|
||||
|
||||
<dd>for QIF core dump fix</dd>
|
||||
|
||||
<dt> <a href="mailto:brent@baton.phys.lsu.edu"> Brent Neal</a></dt>
|
||||
<dt><a href="mailto:brent@baton.phys.lsu.edu">Brent
|
||||
Neal</a></dt>
|
||||
|
||||
<dd>TIAA-CREF support.</dd>
|
||||
|
||||
<dt> <a href="mailto:spacey@inch.com"> Peter Norton</a></dt>
|
||||
<dt><a href="mailto:spacey@inch.com">Peter Norton</a></dt>
|
||||
|
||||
<dd>for a valiant attempt at a GTK port</dd>
|
||||
|
||||
<dt> <a href="mailto:webmaster@obsidian.uia.net">
|
||||
<dt><a href="mailto:webmaster@obsidian.uia.net">
|
||||
OmNiBuS</a></dt>
|
||||
|
||||
<dd>web site graphics and content</dd>
|
||||
|
||||
<dt> <a href="mailto:mopyr@IPM.Lviv.UA"> Myroslav
|
||||
Opyr</a></dt>
|
||||
<dt><a href="mailto:mopyr@IPM.Lviv.UA">Myroslav Opyr</a></dt>
|
||||
|
||||
<dd>for misc patches</dd>
|
||||
|
||||
<dt> <a href="mailto:laurent.pelecq@wanadoo.fr"> Laurent
|
||||
<dt><a href="mailto:laurent.pelecq@wanadoo.fr">Laurent
|
||||
P{'e}lecq</a></dt>
|
||||
|
||||
<dd>i18n patches with gettext</dd>
|
||||
|
||||
<dt> <a href="mailto:Alain.Peyrat@nmu.alcatel.fr"> Alain
|
||||
<dt><a href="mailto:Alain.Peyrat@nmu.alcatel.fr">Alain
|
||||
Peyrat</a></dt>
|
||||
|
||||
<dd>for <tt>configure.in</tt> patches</dd>
|
||||
|
||||
<dt> <a href="mailto:peter@wuzel.m.isar.de"> Peter
|
||||
<dt><a href="mailto:peter@wuzel.m.isar.de">Peter
|
||||
Pointner</a></dt>
|
||||
|
||||
<dd>motif and configuration patches</dd>
|
||||
|
||||
<dt> <a href="mailto:maufk@csv.warwick.ac.uk"> Gavin
|
||||
<dt><a href="mailto:maufk@csv.warwick.ac.uk">Gavin
|
||||
Porter</a></dt>
|
||||
|
||||
<dd>for euro style dates</dd>
|
||||
|
||||
<dt> <a href="mailto:tpo@spin.ch"> Tomas Pospisek</a></dt>
|
||||
<dt><a href="mailto:tpo@spin.ch">Tomas Pospisek</a></dt>
|
||||
|
||||
<dd>debian patches</dd>
|
||||
|
||||
<dt> <a href="mailto:rr@sco.com"> Ron Record</a></dt>
|
||||
<dt><a href="mailto:rr@sco.com">Ron Record</a></dt>
|
||||
|
||||
<dd>for SCO Unixware and OpenServer binaries</dd>
|
||||
|
||||
<dt> <a href="mailto:Keith.Refson@earth.ox.ac.uk"> Keith Refson</a></dt>
|
||||
<dt><a href="mailto:Keith.Refson@earth.ox.ac.uk">Keith
|
||||
Refson</a></dt>
|
||||
|
||||
<dd>Solaris fixes</dd>
|
||||
|
||||
<dt> <a href="mailto:schoenberger@signsoft.com"> Dirk
|
||||
<dt><a href="mailto:schoenberger@signsoft.com">Dirk
|
||||
Schoenberger</a></dt>
|
||||
|
||||
<dd>began the Qt/KDE port</dd>
|
||||
|
||||
<dt> <a href="mailto:jan.schrage@urz.uni-heidelberg.de"> Jan
|
||||
<dt><a href="mailto:jan.schrage@urz.uni-heidelberg.de">Jan
|
||||
Schrage</a></dt>
|
||||
|
||||
<dd>documentation patches</dd>
|
||||
|
||||
<dt> <a href="mailto:cls@seawood.org"> Christopher
|
||||
<dt><a href="mailto:cls@seawood.org">Christopher
|
||||
Seawood</a></dt>
|
||||
|
||||
<dd>for XbaeMatrix core dump</dd>
|
||||
|
||||
<dt> <a href="mailto:msimons@fsimons01.erols.com"> Mike
|
||||
<dt><a href="mailto:msimons@fsimons01.erols.com">Mike
|
||||
Simons</a></dt>
|
||||
|
||||
<dd>misc <tt> configure.in</tt> patches</dd>
|
||||
<dd>misc <tt>configure.in</tt> patches</dd>
|
||||
|
||||
<dt> <a href="mailto:rich@brake.demon.co.uk"> Richard
|
||||
<dt><a href="mailto:rich@brake.demon.co.uk">Richard
|
||||
Skelton</a></dt>
|
||||
|
||||
<dd>for Solaris cleanup</dd>
|
||||
|
||||
<dt> <a href="mailto:spruth@bigfoot.com"> Henning
|
||||
<dt><a href="mailto:spruth@bigfoot.com">Henning
|
||||
Spruth</a></dt>
|
||||
|
||||
<dd>for German text and euro date rework</dd>
|
||||
|
||||
<dt> <a href="mailto:robby.stephenson@usa.net"> Robby
|
||||
<dt><a href="mailto:robby.stephenson@usa.net">Robby
|
||||
Stephenson</a></dt>
|
||||
|
||||
<dd>register & file history patches</dd>
|
||||
<dd>register & file history patches</dd>
|
||||
|
||||
<dt> <a href="mailto:tma@iis.fhg.de"> Herbert Thoma</a></dt>
|
||||
<dt><a href="mailto:tma@iis.fhg.de">Herbert Thoma</a></dt>
|
||||
|
||||
<dd>gnome register & euro support patches</dd>
|
||||
<dd>gnome register & euro support patches</dd>
|
||||
|
||||
<dt> <a href="mailto:detrout@earthlink.net"> Diane
|
||||
<dt><a href="mailto:detrout@earthlink.net">Diane
|
||||
Trout</a></dt>
|
||||
|
||||
<dd>scheme qif import patch</dd>
|
||||
|
||||
<dt> <a href="mailto:rkw@dataplex.net"> Richard Wackerbarth</a></dt>
|
||||
<dt><a href="mailto:rkw@dataplex.net">Richard
|
||||
Wackerbarth</a></dt>
|
||||
|
||||
<dd>patch to gnc-prices</dd>
|
||||
|
||||
<dt> <a href="mailto:rob@valinux.com"> Rob Walker</a></dt>
|
||||
<dt><a href="mailto:rob@valinux.com">Rob Walker</a></dt>
|
||||
|
||||
<dd>guile and register patches</dd>
|
||||
|
||||
<dt> <a href="mailto:dwmw2@infradead.org"> David Woodhouse</a></dt>
|
||||
<dt><a href="mailto:dwmw2@infradead.org">David
|
||||
Woodhouse</a></dt>
|
||||
|
||||
<dd>Great Britain translations</dd>
|
||||
|
||||
<dt> <a href="mailto:gooch@ic.EECS.Berkeley.EDU"> Ken
|
||||
<dt><a href="mailto:gooch@ic.EECS.Berkeley.EDU">Ken
|
||||
Yamaguchi</a></dt>
|
||||
|
||||
<dd>QIF import fixes; MYM import</dd>
|
||||
|
||||
<dt> <a href="mailto:shimpei@gol.com"> Shimpei Yamashita</a></dt>
|
||||
<dt><a href="mailto:shimpei@gol.com">Shimpei
|
||||
Yamashita</a></dt>
|
||||
|
||||
<dd>Japanese translation</dd>
|
||||
|
||||
</dl>
|
||||
|
||||
<h2>Supported Operating Systems</h2>
|
||||
@ -544,15 +554,15 @@
|
||||
<li>NetBSD -- Intel</li>
|
||||
</ul>
|
||||
|
||||
<p> <a href="http://www.gnucash.org/"> <img src=
|
||||
<p><a href="http://www.gnucash.org/"><img src=
|
||||
"logos/linux.gif"></a> <a href="http://www.sco.com/skunkware">
|
||||
<img src="logos/skunkware.gif"></a> <a href=
|
||||
"http://www.bull.de/pub/"><img src="logos/bullogogross.gif">
|
||||
<a href="http://www.ibm.com"> <img src="logos/ibm.gif"></a>
|
||||
<a href="http://www.sgi.com"> <img src="logos/sgi.gif"></a>
|
||||
<a href="http://www.debian.org"> <img src="logos/debian.jpg"></a>
|
||||
<a href="http://www.netbsd.org"> <img src= "logos/NetBSD-banner.gif">
|
||||
</p>
|
||||
<img src="logos/skunkware.gif"></a> <a href=
|
||||
"http://www.bull.de/pub/"><img src="logos/bullogogross.gif"> <a
|
||||
href="http://www.ibm.com"><img src="logos/ibm.gif"></a> <a
|
||||
href="http://www.sgi.com"><img src="logos/sgi.gif"></a> <a
|
||||
href="http://www.debian.org"><img src="logos/debian.jpg"></a>
|
||||
<a href="http://www.netbsd.org"><img src=
|
||||
"logos/NetBSD-banner.gif"></a></a></p>
|
||||
|
||||
<h2>History</h2>
|
||||
The table below shows some historical lines-of-code and
|
||||
@ -562,7 +572,7 @@
|
||||
|
||||
<table border="1">
|
||||
<caption>
|
||||
Historical Development Stats
|
||||
Historical Development Stats
|
||||
</caption>
|
||||
|
||||
<tr align="center">
|
||||
@ -607,7 +617,8 @@
|
||||
<td>5 files<br>
|
||||
(0.4)</td>
|
||||
|
||||
<td>1 file<br>(0.1)</td>
|
||||
<td>1 file<br>
|
||||
(0.1)</td>
|
||||
|
||||
<td>40 files<br>
|
||||
(8.8)</td>
|
||||
@ -633,7 +644,8 @@
|
||||
<td>9 files<br>
|
||||
(0.8)</td>
|
||||
|
||||
<td>1 file<br>(0.1)</td>
|
||||
<td>1 file<br>
|
||||
(0.1)</td>
|
||||
|
||||
<td>61 files<br>
|
||||
(16.2)</td>
|
||||
@ -659,7 +671,8 @@
|
||||
<td>12 files<br>
|
||||
(1.4)</td>
|
||||
|
||||
<td>4 files<br>(0.3)</td>
|
||||
<td>4 files<br>
|
||||
(0.3)</td>
|
||||
|
||||
<td>68 files<br>
|
||||
(18.3)</td>
|
||||
@ -697,55 +710,102 @@
|
||||
(34.7)</td>
|
||||
</tr>
|
||||
|
||||
<tr align=center>
|
||||
<td>gnucash-1.2.2<br>Aug 99
|
||||
<td>41 files<br>(10.2+3.6)
|
||||
<td>28 files<br>(5.5+1.7)
|
||||
<td>14 files<br>(2.4+0.6)
|
||||
<td>26 files<br>(8.7+0.5)
|
||||
<td> -
|
||||
<td>14 files<br>(1.4)
|
||||
<td>30 files<br>(2.6)
|
||||
<td>15 files<br>(1.8)
|
||||
<td>168 files<br>(39.0)
|
||||
<tr align="center">
|
||||
<td>gnucash-1.2.2<br>
|
||||
Aug 99</td>
|
||||
|
||||
<tr align=center>
|
||||
<td>gnucash-1.3.6<br>April 2000
|
||||
<td>41 files<br>(12.9+4.0)
|
||||
<td>32 files<br>(6.8+2.1)
|
||||
<td>19 files<br>(4.0+0.8)
|
||||
<td> -
|
||||
<td>78 files<br>(32.2+3.0)
|
||||
<td>74 files<br>(17.0)
|
||||
<td>33 files<br>(7.8)
|
||||
<td>25 files<br>(4.5)
|
||||
<td>302 files<br>(95.1)
|
||||
<td>41 files<br>
|
||||
(10.2+3.6)</td>
|
||||
|
||||
<td>28 files<br>
|
||||
(5.5+1.7)</td>
|
||||
|
||||
<td>14 files<br>
|
||||
(2.4+0.6)</td>
|
||||
|
||||
<td>26 files<br>
|
||||
(8.7+0.5)</td>
|
||||
|
||||
<td>-</td>
|
||||
|
||||
<td>14 files<br>
|
||||
(1.4)</td>
|
||||
|
||||
<td>30 files<br>
|
||||
(2.6)</td>
|
||||
|
||||
<td>15 files<br>
|
||||
(1.8)</td>
|
||||
|
||||
<td>168 files<br>
|
||||
(39.0)</td>
|
||||
</tr>
|
||||
|
||||
<tr align="center">
|
||||
<td>gnucash-1.3.6<br>
|
||||
April 2000</td>
|
||||
|
||||
<td>41 files<br>
|
||||
(12.9+4.0)</td>
|
||||
|
||||
<td>32 files<br>
|
||||
(6.8+2.1)</td>
|
||||
|
||||
<td>19 files<br>
|
||||
(4.0+0.8)</td>
|
||||
|
||||
<td>-</td>
|
||||
|
||||
<td>78 files<br>
|
||||
(32.2+3.0)</td>
|
||||
|
||||
<td>74 files<br>
|
||||
(17.0)</td>
|
||||
|
||||
<td>33 files<br>
|
||||
(7.8)</td>
|
||||
|
||||
<td>25 files<br>
|
||||
(4.5)</td>
|
||||
|
||||
<td>302 files<br>
|
||||
(95.1)</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<p> Each cell displays the following:<br>
|
||||
<p>Each cell displays the following:<br>
|
||||
<br>
|
||||
number of *c and *.h files<br>
|
||||
(KLOCS in *.c + KLOCS in *.h)</p>
|
||||
(unless its the scheme directories, in which case its *scm files, etc)
|
||||
(unless its the scheme directories, in which case its *scm
|
||||
files, etc)
|
||||
|
||||
<p> where KLOC == kilo-lines-of-code, as reported by <tt>
|
||||
<p>where KLOC == kilo-lines-of-code, as reported by <tt>
|
||||
wc</tt>.</p>
|
||||
|
||||
<p>
|
||||
<ul>
|
||||
<li>engine -- contents of the src/engine and the include directories
|
||||
<li>register -- contents of the register directory
|
||||
<li>ledger -- *.c, *.h files in the src directory only
|
||||
<li>motif -- contents of src/motif directory
|
||||
<li>gnome -- src/gnome plus src/register/gnome
|
||||
<li>scheme -- scheme and guile code -- src/scm plus src/guile
|
||||
<li>docs -- english-only html docs (user documentation)
|
||||
<li>txt -- internal README and *.txt documentation files in all subdirs
|
||||
</ul>
|
||||
<ul>
|
||||
<li>engine -- contents of the src/engine and the include
|
||||
directories</li>
|
||||
|
||||
<li>register -- contents of the register directory</li>
|
||||
|
||||
<li>ledger -- *.c, *.h files in the src directory only</li>
|
||||
|
||||
<li>motif -- contents of src/motif directory</li>
|
||||
|
||||
<li>gnome -- src/gnome plus src/register/gnome</li>
|
||||
|
||||
<li>scheme -- scheme and guile code -- src/scm plus
|
||||
src/guile</li>
|
||||
|
||||
<li>docs -- english-only html docs (user documentation)</li>
|
||||
|
||||
<li>txt -- internal README and *.txt documentation files in
|
||||
all subdirs</li>
|
||||
</ul>
|
||||
<hr>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
@ -1,30 +1,38 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
|
||||
<title>Editing Account Parameters</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1>Editing Account Parameters</h1>
|
||||
<h1>Editing Account Parameters</h1>
|
||||
|
||||
<p>The "Edit Account" dialog box lets you change the properties of
|
||||
an account. You can access this via the "edit" button of the main
|
||||
window toolbar, the "Accounts" menu, or via the keyboard
|
||||
shortcuts. For a description of the uses of the various
|
||||
properties, see the information about <a
|
||||
href="xacc-accwin.html">new accounts</a>.</p>
|
||||
<p>The "Edit Account" dialog box lets you change the properties
|
||||
of an account. You can access this via the "edit" button of the
|
||||
main window toolbar, the "Accounts" menu, or via the keyboard
|
||||
shortcuts. For a description of the uses of the various
|
||||
properties, see the information about <a href=
|
||||
"xacc-accwin.html">new accounts</a>.</p>
|
||||
|
||||
<p><b>Account information</b> can be changed by typing in the appropriate
|
||||
field. The account type cannot be changed.</p>
|
||||
<p>A new <b>Parent Account</b> can be selected. Only those accounts that
|
||||
can legally become the parent of the present account are shown.</p>
|
||||
<p>The source for <b>Stock Quotes</b> can be selected. See
|
||||
<a href="xacc-ticker.html">the ticker</a> for more information.</p>
|
||||
<p><b>Notes</b> about the account can be edited.</p>
|
||||
<p><b>Account information</b> can be changed by typing in the
|
||||
appropriate field. The account type cannot be changed.</p>
|
||||
|
||||
<p>A new <b>Parent Account</b> can be selected. Only those
|
||||
accounts that can legally become the parent of the present
|
||||
account are shown.</p>
|
||||
|
||||
<hr><p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
<p>The source for <b>Stock Quotes</b> can be selected. See <a
|
||||
href="xacc-ticker.html">the ticker</a> for more
|
||||
information.</p>
|
||||
|
||||
<p><b>Notes</b> about the account can be edited.</p>
|
||||
<hr>
|
||||
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
|
||||
|
@ -11,9 +11,11 @@
|
||||
|
||||
<body>
|
||||
<h1>Account Types</h1>
|
||||
GnuCash supports a number of different account types. You should always
|
||||
choose the type that is appropriate for what you want to record. If
|
||||
you're not sure, the explanations below should help you decide.
|
||||
|
||||
<P> GnuCash supports a number of different account types. You should
|
||||
always choose the type that is appropriate for what you want to
|
||||
record. If you're not sure, the explanations below should help you
|
||||
decide.
|
||||
|
||||
<dl>
|
||||
<dt><b>Cash</b></dt>
|
||||
@ -27,7 +29,7 @@ you're not sure, the explanations below should help you decide.
|
||||
<dd>The <b>Bank</b> account type denotes a savings or
|
||||
checking account held at a bank or other financial
|
||||
institution.
|
||||
Such accounts sometimes bear interest.
|
||||
<dd> Such accounts sometimes bear interest.
|
||||
|
||||
<dt><b>Credit</b></dt>
|
||||
|
||||
@ -37,7 +39,6 @@ you're not sure, the explanations below should help you decide.
|
||||
American Express that do <em> not</em> permit you to maintain
|
||||
continuing balances.</dd>
|
||||
|
||||
<p>
|
||||
<dd>The introduction of <a href=
|
||||
"http://www.visa.com/pd/debit/checkcard.html"> Check
|
||||
Cards</a> where payments are withdrawn directly from a
|
||||
@ -47,6 +48,9 @@ you're not sure, the explanations below should help you decide.
|
||||
such an account, not really involving any granting of
|
||||
credit.</dd>
|
||||
|
||||
<DD> Note the ambiguity of AMEX and Check Cards. This shows that
|
||||
deciding where to put accounts is not an exact science.
|
||||
|
||||
<dt><b>Asset, Liability</b></dt>
|
||||
|
||||
<dd><b>Asset</b> and <b>Liability</b> accounts are used for
|
||||
@ -121,12 +125,12 @@ you're not sure, the explanations below should help you decide.
|
||||
|
||||
<dd><b> Income</b> and <b>Expense</b> account types are used to
|
||||
record income and expenses.
|
||||
For example, if you deposit a paycheck in your bank account, you
|
||||
<DD> For example, if you deposit a paycheck in your bank account, you
|
||||
should mark it as a transfer from an 'income' account type.
|
||||
Marking income in this way helps balance the books: the change in your
|
||||
<dd> Marking income in this way helps balance the books: the change in your
|
||||
net worth in the course of a few ekks, a few months, or a year, should
|
||||
exactly equal your income (minus expenses) for the same period.
|
||||
The value stored in the bank account contributes to your 'net worth';
|
||||
<DD> The value stored in the bank account contributes to your 'net worth';
|
||||
whereas the income contributes to your 'profits'.
|
||||
|
||||
</dd>
|
||||
@ -135,15 +139,23 @@ whereas the income contributes to your 'profits'.
|
||||
|
||||
<dd><b>Equity</b> accounts are used to
|
||||
store the opening balances when you first start using GnuCash
|
||||
(or start a new accounting period). Assuming that you've had a bank
|
||||
(or start a new accounting period).
|
||||
|
||||
|
||||
<dd>Assuming that you've had a bank
|
||||
account far longer than you've been using GnuCash, and assuming you
|
||||
don't want to type in old transactions, you will want to type in a
|
||||
non-zero 'opening balance' into your bank account. This opening balance
|
||||
non-zero <b> opening balance </b> into your bank account. This opening balance
|
||||
should be marked as a transfer from an account of type 'equity'.
|
||||
Alternately, if you close and reopen all your books at the end of every
|
||||
|
||||
<DD> Alternately, if you close and reopen all your books at the end of every
|
||||
quarter/year, the 'equity' will be your net-worth at the begining of the
|
||||
period: it equal all assets minus all liabilities. As time passes by,
|
||||
you will have both income and expenses. At the end of the year, your net
|
||||
period: it equal all assets minus all liabilities.
|
||||
|
||||
<DD> As time goes by,
|
||||
you will have both income and expenses.
|
||||
|
||||
<DD At the end of the year, your net
|
||||
worth will be the equity at the begining of the year, plus all income
|
||||
minus all expense. This value will become, of course, the equity for
|
||||
the next accounting period.
|
||||
|
@ -2,8 +2,10 @@
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
|
||||
<title></title>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>New Account Window</title>
|
||||
@ -12,26 +14,26 @@
|
||||
<body>
|
||||
<h1>New Account Window</h1>
|
||||
|
||||
<p> This is what a new account window looks like:</p>
|
||||
<p>This is what a new account window looks like:</p>
|
||||
|
||||
<p> <img src="newaccwin-code.gif"></p>
|
||||
<p><img src="newaccwin-code.gif"></p>
|
||||
|
||||
<p> Pick an <a href="xacc-acctypes.html"><b>Account
|
||||
<p>Pick an <a href="xacc-acctypes.html"><b>Account
|
||||
Type</b></a>.</p>
|
||||
|
||||
<p> The <b>Currency</b> field should typically be a <a href=
|
||||
"xacc-currency.html#ISOCURR"> three-letter ISO currency code</a>
|
||||
(<em>e.g.</em> - <tt> USD</tt> for U.S. Dollars). The <b>
|
||||
Account Code</b> is a number that determines the <a href=
|
||||
"xacc-groups.html#SORTORDER"> sort order</a> of the account
|
||||
when it appears in a report or in the <a href=
|
||||
"xacc-groups.html"><b>Chart of Accounts</b></a>.</p>
|
||||
<p>The <b>Currency</b> field should typically be a <a href=
|
||||
"xacc-currency.html#ISOCURR">three-letter ISO currency code</a>
|
||||
(<em>e.g.</em> - <tt>USD</tt> for U.S. Dollars). The <b>Account
|
||||
Code</b> is a number that determines the <a href=
|
||||
"xacc-groups.html#SORTORDER">sort order</a> of the account when
|
||||
it appears in a report or in the <a href="xacc-groups.html"><b>
|
||||
Chart of Accounts</b></a>.</p>
|
||||
|
||||
<p> The picture below shows an example for a stock or currency
|
||||
<p>The picture below shows an example for a stock or currency
|
||||
trading account. Note that the Security field is not grayed
|
||||
out, and that you can enter a value. That value is typically a
|
||||
<a href="xacc-ticker.html"> stock-ticker</a> symbol, or a <a
|
||||
href="xacc-currency.html#ISOCURR"> three-letter ISO currency
|
||||
<a href="xacc-ticker.html">stock-ticker</a> symbol, or a <a
|
||||
href="xacc-currency.html#ISOCURR">three-letter ISO currency
|
||||
code.</a></p>
|
||||
|
||||
<p><br>
|
||||
@ -39,7 +41,7 @@
|
||||
</p>
|
||||
<hr>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
@ -2,8 +2,10 @@
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
|
||||
<title></title>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Adjust Balance Window</title>
|
||||
@ -15,10 +17,10 @@
|
||||
dollar amount, and a register entry will be created that sets
|
||||
the balance to the new balance.
|
||||
|
||||
<p> <b> Add more documentation here.</b></p>
|
||||
<p><b>Add more documentation here.</b></p>
|
||||
<hr>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
@ -2,7 +2,8 @@
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Accounts Payable/Accounts Receivable</title>
|
||||
@ -11,46 +12,49 @@
|
||||
<body>
|
||||
<h1>Accounts Payable and Accounts Receivable</h1>
|
||||
|
||||
<p> A/R (Accounts Receivable) and A/P (Accounts Payable) are
|
||||
advanced concepts that are used by businesses to record sales for which
|
||||
they are not paid right away, or to record bills that they've received,
|
||||
but might not pay until a little while later. These types of accounts
|
||||
primarily when you've got a lot of bills and receipts flowing in and
|
||||
out, and don't want to loose track of them just because you don't
|
||||
pay/get paid right away. For almost all home users, A/R and A/P
|
||||
are too complicated and confusing to be worth the effort.
|
||||
<p>A/R (Accounts Receivable) and A/P (Accounts Payable) are
|
||||
advanced concepts that are used by businesses to record sales
|
||||
for which they are not paid right away, or to record bills that
|
||||
they have received, but might not pay until a little while
|
||||
later.</p>
|
||||
|
||||
</p>
|
||||
<p>These types of accounts are used primarily when you've got a
|
||||
lot of bills and receipts flowing in and out, and don't want to
|
||||
loose track of them just because you don't pay/get paid right
|
||||
away.</p>
|
||||
|
||||
<h1> Accounts Receivable</h1>
|
||||
<p>For almost all home users, A/R and A/P are too complicated
|
||||
and confusing to be worth the effort.</p>
|
||||
|
||||
<p> First, let us examine A/R. After all, we really shouldn't
|
||||
<h1>Accounts Receivable</h1>
|
||||
|
||||
<p>First, let us examine A/R. After all, we really shouldn't
|
||||
really <em>need</em> to relate to A/P because we always pay
|
||||
<em>our</em> bills on time, don't we ? :-)</p>
|
||||
|
||||
<p> As a first approximation, let us assume we don't require
|
||||
customers to pay <em> instantly,</em> in cash, but rather issue
|
||||
<p>As a first approximation, let us assume we don't require
|
||||
customers to pay <em>instantly,</em> in cash, but rather issue
|
||||
them an invoice, and give them 30 days to pay the bills. (After
|
||||
30 days, we can start charging interest and sending out
|
||||
harassing letters :-)).</p>
|
||||
|
||||
<p> When we make a sale, the two accounts affected are <b>
|
||||
<p>When we make a sale, the two accounts affected are <b>
|
||||
Sales</b> (an income account) and <b>Accounts Receivable.</b>
|
||||
Accounts Receivable is an asset, but it's not "liquid," as you
|
||||
can't readily sell it, and it's certainly not cash.</p>
|
||||
|
||||
<p> Then when they come by to pay their bill, dropping off a
|
||||
<p>Then when they come by to pay their bill, dropping off a
|
||||
large sack of twenty-dollar bills (or, more likely, a
|
||||
check/cheque), we transfer the amount from A/R to Cash.</p>
|
||||
|
||||
<p> The reason we do this in two steps is that we have decided
|
||||
<p>The reason we do this in two steps is that we have decided
|
||||
we need to do our accounting on an accrual basis and not on a
|
||||
cash basis, because most of our transactions are not solely
|
||||
based on cash changing hands, but rather based on <em>
|
||||
establishing obligations.</em></p>
|
||||
|
||||
<p> In more sophisticated operations, there may be a much
|
||||
larger sequence of documents generated and tracked:</p>
|
||||
<p>In more sophisticated operations, there may be a much more
|
||||
complex sequence of documents generated and tracked:</p>
|
||||
|
||||
<ul>
|
||||
<li>A customer sends in a <b>Purchase Order</b>, thus
|
||||
@ -63,26 +67,31 @@ are too complicated and confusing to be worth the effort.
|
||||
the customer</li>
|
||||
|
||||
<li>Once shipped, we issue an <b>Invoice</b>, representing
|
||||
the <em> request to pay</em></li>
|
||||
the <em>request to pay</em></li>
|
||||
</ul>
|
||||
|
||||
<p> We report sales in our sales figures as soon as we make
|
||||
<p>The fact of there being four documents leads to there being
|
||||
considerable wads of paper, and having these and other such
|
||||
processes explains why large organizations tend to have hefty
|
||||
bureaucracies.</p>
|
||||
|
||||
<p>We report sales in our sales figures as soon as we make
|
||||
them. Unfortunately, we may wind up selling some product to
|
||||
no-good shady operators that we didn't know were shady, and
|
||||
thus may get stuck with some "bad debts."</p>
|
||||
|
||||
<p> In order to determine which parts of Accounts Receivable
|
||||
<p>In order to determine which parts of Accounts Receivable
|
||||
appear to be most at risk, it is typical to arrange AR based on
|
||||
the "ages" of the debts, commonly segmenting it into several
|
||||
aging periods, of payments outstanding 0-30 days, those that
|
||||
outstanding 31-60 days, 61-90 days, and then those that are
|
||||
<em> way overdue.</em></p>
|
||||
<em>way overdue.</em></p>
|
||||
|
||||
<p> At some point, it may become clear that a customer is never
|
||||
<p>At some point, it may become clear that a customer is never
|
||||
going to pay what they owe, and we have to write it off as a
|
||||
<b> Bad Debt.</b></p>
|
||||
<b>Bad Debt.</b></p>
|
||||
|
||||
<p> At that point, it is typical to record an entry thus:</p>
|
||||
<p>At that point, it is typical to record an entry thus:</p>
|
||||
|
||||
<table summary="BADDEBT">
|
||||
<tr>
|
||||
@ -117,82 +126,80 @@ are too complicated and confusing to be worth the effort.
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<p> We could have reduced <b> Sales Income</b> instead, but
|
||||
<p>We could have reduced <b>Sales Income</b> instead, but
|
||||
companies tend to prefer to specifically track the amount that
|
||||
they're losing to bad customers.</p>
|
||||
|
||||
<p> <em> Warning: <b> Advanced Accounting Concept.</b> Bad Debt
|
||||
is an example of a "contra-account." That doesn't refer to <b>
|
||||
<p><em>Warning: <b>Advanced Accounting Concept.</b> Bad Debt is
|
||||
an example of a "contra-account." That doesn't refer to <b>
|
||||
amounts paid to Nicaraguan rebels,</b> but rather the notion
|
||||
that the account is an income account that is expected to hold
|
||||
a balance opposite to what is normally expected, to be
|
||||
counteract the balance in another income account. <a href=
|
||||
"xacc-apprdepr.html#depr"> Accumulated Depreciation,</a> used
|
||||
to diminish the value of an asset over time, is another example
|
||||
of a contra-account.</em></p>
|
||||
counteract the balance in another income account. <a href=
|
||||
"xacc-apprdepr.html#depr">Accumulated Depreciation,</a> used to
|
||||
diminish the value of an asset over time, is another example of
|
||||
a contra-account.</em></p>
|
||||
|
||||
<h1> Accounts Payable</h1>
|
||||
<h1>Accounts Payable</h1>
|
||||
|
||||
<p> The scenario for Accounts Receivable, reversed, reflects
|
||||
how Accounts Payables work; just switch customer with supplier,
|
||||
and see how the roles reverse.</p>
|
||||
<p>The scenario for Accounts Receivable, reversed, reflects how
|
||||
Accounts Payables work; just switch customer with supplier, and
|
||||
watch the roles reverse.</p>
|
||||
|
||||
<ul>
|
||||
<li>If we buy materials "on account," accrual accounting
|
||||
requires that we record that we incur the expense
|
||||
immediately, and rather than reducing cash, we put the
|
||||
"credit" into the <b> Accounts Payable</b> account.</li>
|
||||
"credit" into the <b>Accounts Payable</b> account.</li>
|
||||
|
||||
<li>Three weeks later, the invoice comes in, and we issue a
|
||||
payment, and so <em> Debit AP, Credit Cash.</em><br>
|
||||
payment, and so <em>Debit AP, Credit Cash.</em><br>
|
||||
<br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<h1> Prepaid Expenses</h1>
|
||||
<h1>Prepaid Expenses</h1>
|
||||
|
||||
<p> Analogous techniques are also used for expenses that are
|
||||
<p>Analogous techniques are also used for expenses that are
|
||||
pre-paid.</p>
|
||||
|
||||
<p> If you have to pay out down six months of rent in advance,
|
||||
<p>If you have to pay out down six months of rent in advance,
|
||||
that is treated as an "accrued asset."</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
At the time of payment, you <em> Debit</em> <b> Prepaid
|
||||
Rent</b> for the amount paid that is a <em> Credit</em> to
|
||||
<b> Cash.</b>
|
||||
At the time of payment, you <em>Debit</em> <b>Prepaid
|
||||
Rent</b> for the amount paid that is a <em>Credit</em> to
|
||||
<b>Cash.</b>
|
||||
|
||||
<p> While this puts an unfortunate dent in the Cash
|
||||
account, it <em> does</em> show on the books as an asset,
|
||||
and there are no more payments to make for the next six
|
||||
months.</p>
|
||||
<p>While this puts an unfortunate dent in the Cash account,
|
||||
it <em>does</em> show on the books as an asset, and there
|
||||
are no more payments to make for the next six months.</p>
|
||||
</li>
|
||||
|
||||
<li>Each month, the balance in <b> Prepaid Rent</b> would be
|
||||
down via <em> Debit</em> <b> Rent Expense</b>, <em>
|
||||
Credit</em> <b> Prepaid Rent</b>.</li>
|
||||
<li>Each month, the balance in <b>Prepaid Rent</b> would be
|
||||
down via <em>Debit</em> <b>Rent Expense</b>, <em>Credit</em>
|
||||
<b>Prepaid Rent</b>.</li>
|
||||
</ul>
|
||||
|
||||
<p> Similarly, companies collect payroll taxes on behalf of
|
||||
<p>Similarly, companies collect payroll taxes on behalf of
|
||||
employees, and keep them in a special bank account.</p>
|
||||
|
||||
<ul>
|
||||
<li><em> That</em> money is not the company's, so there is a
|
||||
<em> Debit</em> to the <b>Cash</b> account on one side, and a
|
||||
<em> Credit</em> to an Accrued Liability, namely, <b>Payroll
|
||||
<li><em>That</em> money is not the company's, so there is a
|
||||
<em>Debit</em> to the <b>Cash</b> account on one side, and a
|
||||
<em>Credit</em> to an Accrued Liability, namely, <b>Payroll
|
||||
Taxes Payable</b>, on the other side.</li>
|
||||
|
||||
<li>When the quarterly check to the Government so that they
|
||||
can make <em> their</em> payroll, <b> Payroll Taxes
|
||||
Payable</b> drops as does the balance in the <b>Checking
|
||||
Account</b>.<br>
|
||||
can make <em>their</em> payroll, <b>Payroll Taxes Payable</b>
|
||||
drops as does the balance in the <b>Checking Account</b>.<br>
|
||||
<br>
|
||||
</li>
|
||||
</ul>
|
||||
<hr>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
@ -2,61 +2,61 @@
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Depreciation and Capital Gains</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1> Depreciation and Capital Gains</h1>
|
||||
<h1>Depreciation and Capital Gains</h1>
|
||||
|
||||
<p> This section provides a treatment of the handling of
|
||||
<p>This section provides a treatment of the handling of
|
||||
depreciation and appreciation of assets in GnuCash.</p>
|
||||
|
||||
<p> It also provides a brief introduction to the related tax
|
||||
<p>It also provides a brief introduction to the related tax
|
||||
issues.</p>
|
||||
|
||||
<p> <b> Warning:</b> <em>Be aware that different countries can
|
||||
have <b> substantially</b> different tax policies for handling
|
||||
<p><b>Warning:</b> <em>Be aware that different countries can
|
||||
have <b>substantially</b> different tax policies for handling
|
||||
these things; all that this document can really provide is some
|
||||
of the underlying ideas to help you apply your "favorite"
|
||||
tax/depreciation policies.</em></p>
|
||||
|
||||
<p> Note that appreciation and depreciation of assets tend to
|
||||
be treated somewhat differently:</p>
|
||||
<p>Note that appreciation and depreciation of assets tend to be
|
||||
treated somewhat differently:</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<a href="#depr"> Depreciation</a> is <em> usually</em>
|
||||
recognized (the technical term is <b> accrued</b>) as an
|
||||
<a href="#depr">Depreciation</a> is <em>usually</em>
|
||||
recognized (the technical term is <b>accrued</b>) as an
|
||||
expense on an ongoing basis, gradually reducing the value
|
||||
of an asset towards zero.
|
||||
|
||||
<p> Depreciation tends to only get calculated on assets
|
||||
that are used for professional or business purposes, because
|
||||
governments
|
||||
don't generally allow you to claim depreciation deductions
|
||||
on personal assets, and it's pointless to bother with the
|
||||
procedure if it's not deductible. </p>
|
||||
<p>Depreciation tends to only get calculated on assets that
|
||||
are used for professional or business purposes, because
|
||||
governments don't generally allow you to claim depreciation
|
||||
deductions on personal assets, and it's pointless to bother
|
||||
with the procedure if it's not deductible.</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
In contrast, <a href="#appr"> Capital Gains,</a> which
|
||||
could be called <em>asset value appreciation,</em> are
|
||||
typically <em> not</em> recognized until some time down the
|
||||
road when the asset is sold, and at that <em> instant,</em>
|
||||
the entire gain becomes income.
|
||||
In contrast, <a href="#appr">Capital Gains,</a> which could
|
||||
be called <em>asset value appreciation,</em> are typically
|
||||
<em>not</em> recognized until some time down the road when
|
||||
the asset is sold, and at that <em>instant,</em> the entire
|
||||
gain becomes income.
|
||||
|
||||
<p> Unlike depreciation, governments tend to be <em> quite
|
||||
<p>Unlike depreciation, governments tend to be <em>quite
|
||||
interested</em> in taxing capital gains in one manner or
|
||||
another.</p>
|
||||
|
||||
<p> (As always, there are exceptions. If you hold a bond
|
||||
<p>(As always, there are exceptions. If you hold a bond
|
||||
that pays all of its interest at maturity, tax authorities
|
||||
will often require that you recognize interest each year,
|
||||
and refuse this to be treated as a capital gain. The
|
||||
phrases <em>accrued interest,</em> or <em> imputed
|
||||
phrases <em>accrued interest,</em> or <em>imputed
|
||||
interest</em> are often there to scare those that are
|
||||
sensitive to such things...)</p>
|
||||
</li>
|
||||
@ -65,30 +65,30 @@
|
||||
<h1>Capital Gains - Asset Appreciation</h1>
|
||||
<a name="appr"></a>
|
||||
|
||||
<p>Appreciation of assets is, in general, a fairly tricky matter
|
||||
to deal with. This is so because, for some sorts of assets, it
|
||||
is difficult to correctly estimate an increase in value <em>
|
||||
until you actually sell the asset.</em></p>
|
||||
<p>Appreciation of assets is, in general, a fairly tricky
|
||||
matter to deal with. This is so because, for some sorts of
|
||||
assets, it is difficult to correctly estimate an increase in
|
||||
value <em>until you actually sell the asset.</em></p>
|
||||
|
||||
<p> If you invest in <a href="xacc-ticker.html">securities</a>
|
||||
<p>If you invest in <a href="xacc-ticker.html">securities</a>
|
||||
that are traded on a daily basis on open markets such as stock
|
||||
exchanges, prices may be quite exact, and selling the asset at
|
||||
market prices may be as simple as calling a broker and issuing
|
||||
a <b> Market Order.</b></p>
|
||||
a <b>Market Order.</b></p>
|
||||
|
||||
<p> On the other hand, homes in your neighborhood are sold
|
||||
<p>On the other hand, homes in your neighborhood are sold
|
||||
somewhat less often, such sales tend to involve expending
|
||||
considerable effort, and involve negotiations, which means that
|
||||
estimates are likely to be less precise. Similarly, selling a
|
||||
used automobile involves a negotiation process that makes
|
||||
pricing a bit less predictable.</p>
|
||||
|
||||
<p> Harder to estimate are values of collectible objects such
|
||||
as jewelry, works of art, baseball cards, and "Beanie Babies."
|
||||
The markets for such objects are somewhat less open than the
|
||||
<p>Harder to estimate are values of collectible objects such as
|
||||
jewelry, works of art, baseball cards, and "Beanie Babies." The
|
||||
markets for such objects are somewhat less open than the
|
||||
securities markets.</p>
|
||||
|
||||
<p> Worse still are one-of-a-kind assets. Factories often
|
||||
<p>Worse still are one-of-a-kind assets. Factories often
|
||||
contain presses and dies customized to build a very specific
|
||||
product that cost tens or hundreds of thousands of dollars;
|
||||
this equipment may be <em>worthless</em> outside of that very
|
||||
@ -96,12 +96,12 @@
|
||||
values might be attached to the asset, <em>none</em> of them
|
||||
unambiguously correct.</p>
|
||||
|
||||
<p> Let's suppose you buy an asset expected to increase in
|
||||
<p>Let's suppose you buy an asset expected to increase in
|
||||
value, say a Degas painting, and want to track this. (The
|
||||
insurance company will care about this, even if nobody else
|
||||
does.)</p>
|
||||
|
||||
<p> Properly tracking the continually-increasing value of the
|
||||
<p>Properly tracking the continually-increasing value of the
|
||||
Degas will require at least three, quite possibly the following
|
||||
four accounts (plus a bank or cash account where the money for
|
||||
the purchase comes from):</p>
|
||||
@ -122,20 +122,20 @@
|
||||
asset.</li>
|
||||
</ul>
|
||||
|
||||
<p> The <em>accrued gains</em> likely won't affect your taxable
|
||||
income for <em> income</em> tax purposes, although it could
|
||||
have some effect on <em> property</em> taxes.</p>
|
||||
<p>The <em>accrued gains</em> likely won't affect your taxable
|
||||
income for <em>income</em> tax purposes, although it could have
|
||||
some effect on <em>property</em> taxes.</p>
|
||||
|
||||
<h2>The handling of capital gains in GnuCash</h2>
|
||||
|
||||
<h3> The Acquisition</h3>
|
||||
<h3>The Acquisition</h3>
|
||||
|
||||
<p>The first thing you have to do is to create the <em>asset
|
||||
cost account</em>, then transfer the sum you paid for this
|
||||
painting from your bank account to this asset account to record
|
||||
the purchase.</p>
|
||||
|
||||
<p> A month later, you have reason to suspect that the value of
|
||||
<p>A month later, you have reason to suspect that the value of
|
||||
your painting has increased by $1200. In order to record this
|
||||
you transfer $1200 from your <em>accrued gains on asset</em>
|
||||
income account to your asset account.</p>
|
||||
@ -148,25 +148,25 @@
|
||||
<img src="appr-asset1.gif" alt=
|
||||
"Asset account after purchase and appreciation">
|
||||
|
||||
<h3> While You Hold the Asset</h3>
|
||||
<h3>While You Hold the Asset</h3>
|
||||
|
||||
<p>Asset appreciation is a sort of income but it is <em>
|
||||
not</em> cash in hand.</p>
|
||||
|
||||
<p> The people that got "rich" in 1999 from IPOs of
|
||||
<p>The people that got "rich" in 1999 from IPOs of
|
||||
Linux-related companies like Red Hat Software and VA Linux
|
||||
Systems could verify this. They hold options or stock that are
|
||||
<em> theoretically</em> valued at millions of dollars USD.</p>
|
||||
<em>theoretically</em> valued at millions of dollars USD.</p>
|
||||
|
||||
<p> That doesn't mean that they are actually millionaires; the
|
||||
<p>That doesn't mean that they are actually millionaires; the
|
||||
principal participants have to hold their stock for at least
|
||||
six months before selling <em> any</em> of it. The fact that
|
||||
six months before selling <em>any</em> of it. The fact that
|
||||
they <em>can't</em> sell it means that while it may in theory
|
||||
be worth millions of dollars on paper, there is, as of late
|
||||
1999, no way for them to legally <em> get</em> those
|
||||
1999, no way for them to legally <em>get</em> those
|
||||
millions.</p>
|
||||
|
||||
<h3> Selling the Asset</h3>
|
||||
<h3>Selling the Asset</h3>
|
||||
|
||||
<p>Let´s say another month later prices for Degas
|
||||
paintings have gone up some more, in your case about $2500, you
|
||||
@ -180,8 +180,8 @@
|
||||
Your optimistic estimate of the painting´s value was
|
||||
correct.
|
||||
|
||||
<p> The income account is left alone (or perhaps gets
|
||||
transferred from an <em> Accrued Gain</em> income to a <em>
|
||||
<p>The income account is left alone (or perhaps gets
|
||||
transferred from an <em>Accrued Gain</em> income to a <em>
|
||||
Realized Gain</em> income account), and the recording is
|
||||
rather like:</p>
|
||||
|
||||
@ -211,9 +211,9 @@
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<p> And if any amounts had been accrued as <em> Accrued
|
||||
<p>And if any amounts had been accrued as <em>Accrued
|
||||
Gains,</em> the asset amount should be closed out, offset
|
||||
by a <em> negative</em> value for <em> Accrued Gain</em>
|
||||
by a <em>negative</em> value for <em>Accrued Gain</em>
|
||||
income. If the total that had been accrued was $5000, then
|
||||
the transaction might look like the following:</p>
|
||||
|
||||
@ -255,21 +255,21 @@
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<p> Note that the two income accounts offset one another so
|
||||
that the <em> current</em> income resulting from the
|
||||
<p>Note that the two income accounts offset one another so
|
||||
that the <em>current</em> income resulting from the
|
||||
transaction is only $55. The remaining $5000 had previously
|
||||
been recognized as <em> Accrued Gain Income.</em></p>
|
||||
been recognized as <em>Accrued Gain Income.</em></p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
You were over-optimistic about the value of the painting.
|
||||
|
||||
<p> Instead of the $16055 you thought the painting was
|
||||
worth are only offered $15000. But you still decide to
|
||||
sell, because you value $15000 more than you value the
|
||||
<p>Instead of the $16055 you thought the painting was worth
|
||||
are only offered $15000. But you still decide to sell,
|
||||
because you value $15000 more than you value the
|
||||
painting.</p>
|
||||
|
||||
<p> The numbers change a little bit, but not too
|
||||
<p>The numbers change a little bit, but not too
|
||||
dramatically.</p>
|
||||
|
||||
<table summary="SMALLGAINACCRUEDTOO">
|
||||
@ -310,9 +310,9 @@
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<p> Note that the two income accounts offset one another so
|
||||
that the <em> current</em> income resulting from the
|
||||
transaction turns out to be a <em> loss</em> of $1000.
|
||||
<p>Note that the two income accounts offset one another so
|
||||
that the <em>current</em> income resulting from the
|
||||
transaction turns out to be a <em>loss</em> of $1000.
|
||||
That's fine, as you had previously recognized $5000 in
|
||||
income.</p>
|
||||
</li>
|
||||
@ -321,7 +321,7 @@
|
||||
You manage to sell your painting for more than you thought
|
||||
in your wildest dreams.
|
||||
|
||||
<p> The extra value is, again, recorded as a gain, <em>
|
||||
<p>The extra value is, again, recorded as a gain, <em>
|
||||
i.e.</em> an income.</p>
|
||||
|
||||
<table summary="HUGEGAIN">
|
||||
@ -364,8 +364,8 @@
|
||||
</li>
|
||||
</ol>
|
||||
|
||||
<p> In practice, it truly is important to keep the <em> Accrued
|
||||
Gain Income</em> separate from the <em> Realized Gain
|
||||
<p>In practice, it truly is important to keep the <em>Accrued
|
||||
Gain Income</em> separate from the <em>Realized Gain
|
||||
Income,</em> as the former is likely to be ignored by your tax
|
||||
authorities, who will only care to charge you on the <em>
|
||||
Realized Gain.</em></p>
|
||||
@ -381,66 +381,66 @@
|
||||
be difficult to correctly estimate the ``true'' value of an
|
||||
asset.</p>
|
||||
|
||||
<p> It is quite easy to count yourself rich based on
|
||||
<p>It is quite easy to count yourself rich based on
|
||||
questionable estimates that do not reflect "money in the
|
||||
bank."</p>
|
||||
|
||||
<p> Thus, when dealing with appreciation of assets,</p>
|
||||
<p>Thus, when dealing with appreciation of assets,</p>
|
||||
|
||||
<ol>
|
||||
<li>
|
||||
Be careful with your estimation of values.
|
||||
|
||||
<p> Do not indulge in wishful thinking.</p>
|
||||
<p>Do not indulge in wishful thinking.</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Never, ever, count on money you do not have in your bank or
|
||||
as cash.
|
||||
|
||||
<p> Until you have actually sold your asset and got the
|
||||
<p>Until you have actually sold your asset and got the
|
||||
money, any numbers on paper (or magnetic patterns on your
|
||||
hard disk) are merely that.</p>
|
||||
|
||||
<p> If you could realistically convince a banker to lend
|
||||
you money, using the assets as collateral, that is a pretty
|
||||
<p>If you could realistically convince a banker to lend you
|
||||
money, using the assets as collateral, that is a pretty
|
||||
reasonable evidence that the assets have value, as lenders
|
||||
are professionally suspicious of dubious overestimations of
|
||||
value.</p>
|
||||
|
||||
<p> Be aware: all too many companies that appear
|
||||
<p>Be aware: all too many companies that appear
|
||||
"profitable" on paper go out of business as a result of
|
||||
running out of <em> cash,</em> precisely because "valuable
|
||||
running out of <em>cash,</em> precisely because "valuable
|
||||
assets" were not the same thing as cash.</p>
|
||||
</li>
|
||||
</ol>
|
||||
|
||||
<h2>Taxation of Capital Gains</h2>
|
||||
|
||||
<p> Taxation policies vary considerably between countries, so
|
||||
it is virtually impossible to say anything that will be
|
||||
<p>Taxation policies vary considerably between countries, so it
|
||||
is virtually impossible to say anything that will be
|
||||
universally useful.</p>
|
||||
|
||||
<p> However, it is <em> common</em> for income generated by
|
||||
<p>However, it is <em>common</em> for income generated by
|
||||
capital gains to not be subject to taxation until the date that
|
||||
the asset is actually sold, and sometimes not even then.</p>
|
||||
|
||||
<p> North American home owners <em> usually</em> find that when
|
||||
<p>North American home owners <em>usually</em> find that when
|
||||
they sell personal residences, capital gains that occur are
|
||||
exempt from taxation. It appears that other countries treat
|
||||
sale of homes differently, taxing people on such gains. German
|
||||
authorities, for example, tax those gains only if you owned the
|
||||
property for less than ten years.</p>
|
||||
|
||||
<p> <a href="mailto:cbbrowne@hex.net"> I have</a> one story
|
||||
from my professional tax preparation days where a family sold a
|
||||
<p><a href="mailto:cbbrowne@hex.net">I have</a> one story from
|
||||
my professional tax preparation days where a family sold a
|
||||
farm, and expected a <em>considerable</em> tax bill that turned
|
||||
out to be virtually nil due to having owned the property before
|
||||
1971 (wherein lies a critical "Valuation Day" date in Canada)
|
||||
and due to it being a <em> dairy</em> farm, with some <em>
|
||||
really peculiar</em> resulting deductions.</p>
|
||||
and due to it being a <em>dairy</em> farm, with some <em>really
|
||||
peculiar</em> resulting deductions.</p>
|
||||
|
||||
<p> In short, this presentation is fairly simple, but taxation
|
||||
<p>In short, this presentation is fairly simple, but taxation
|
||||
often gets terribly complicated...</p>
|
||||
|
||||
<h1>Depreciation of assets</h1>
|
||||
@ -459,22 +459,21 @@
|
||||
of use.</li>
|
||||
</ul>
|
||||
|
||||
<p> Since depreciation of assets is very often driven by tax
|
||||
<p>Since depreciation of assets is very often driven by tax
|
||||
policies, the discussion of depreciation will focus in that
|
||||
direction, on some of the more common depreciation calculation
|
||||
schemes.</p>
|
||||
|
||||
<p> While there has been some discussion about how to
|
||||
accomplish automated calculation and creation of transactions
|
||||
to handle things like depreciation, there is not yet any
|
||||
working code, so for now, you will have to do calculations by
|
||||
hand.</p>
|
||||
<p>While there has been some discussion about how to accomplish
|
||||
automated calculation and creation of transactions to handle
|
||||
things like depreciation, there is not yet any working code, so
|
||||
for now, you will have to do calculations by hand.</p>
|
||||
|
||||
<h2>Depreciation schemes</h2>
|
||||
|
||||
<h3>Linear depreciation</h3>
|
||||
|
||||
<p> Linear depreciation diminishes the value of an asset by a
|
||||
<p>Linear depreciation diminishes the value of an asset by a
|
||||
fixed amount each period until the net value is zero. This is
|
||||
the <em>simplest</em> calculation, as you estimate a useful
|
||||
lifetime, and simply divide the cost equally across that
|
||||
@ -541,16 +540,15 @@
|
||||
<p>Each period the asset is depreciated by a fixed percentage
|
||||
of its value in the previous period. In this scheme the rest
|
||||
value of an asset decreases exponentially leaving a value at
|
||||
the end that is larger than zero (<em> i.e.</em> - a resale
|
||||
the end that is larger than zero ( <em>i.e.</em> - a resale
|
||||
value).</p>
|
||||
|
||||
<p> <em> Beware: Tax authorities may require (or allow) a
|
||||
larger percentage in the first period.</em> On the other hand,
|
||||
in Canada, this is reversed, as they permit only a <em>
|
||||
half</em> share of "Capital Cost Allowance" in the first
|
||||
year.</p>
|
||||
<p><em>Beware: Tax authorities may require (or allow) a larger
|
||||
percentage in the first period.</em> On the other hand, in
|
||||
Canada, this is reversed, as they permit only a <em>half</em>
|
||||
share of "Capital Cost Allowance" in the first year.</p>
|
||||
|
||||
<p> The result of this approach is that asset value decreases
|
||||
<p>The result of this approach is that asset value decreases
|
||||
more rapidly at the beginning than at the end which is <em>
|
||||
probably</em> more realistic for most assets than a linear
|
||||
scheme. This is certainly true for automobiles.</p>
|
||||
@ -614,7 +612,7 @@
|
||||
is the "sum of digits" method. Here is an illustration:</p>
|
||||
|
||||
<p><strong>Example:</strong> First you divide the asset value
|
||||
by the sum of the years of use, <em> e.g.</em> for our example
|
||||
by the sum of the years of use, <em>e.g.</em> for our example
|
||||
from above with an asset worth $1500 that is used over a period
|
||||
of five years you get 1500/(1+2+3+4+5)=100. Depreciation and
|
||||
asset value are then calculated as follows:</p>
|
||||
@ -678,7 +676,7 @@
|
||||
<li>An <em>Asset Cost</em> asset account to keep track of the
|
||||
original value;</li>
|
||||
|
||||
<li>An <em> Accumulated Depreciation</em> asset account in
|
||||
<li>An <em>Accumulated Depreciation</em> asset account in
|
||||
which to collect the sum of all of the years' depreciation
|
||||
amounts;</li>
|
||||
|
||||
@ -703,13 +701,14 @@
|
||||
<h2>A word of caution</h2>
|
||||
|
||||
<p>Since depreciation and tax issues are closely related, you
|
||||
may not always be free in choosing your preferred method. Fixing
|
||||
wrong calculations will cost a whole lot more time and trouble
|
||||
than getting the calculations right the first time, so if you
|
||||
plan to depreciate assets, it is wise to make sure of the
|
||||
schemes you will be permitted <em> or required</em> to use.</p>
|
||||
may not always be free in choosing your preferred method.
|
||||
Fixing wrong calculations will cost a whole lot more time and
|
||||
trouble than getting the calculations right the first time, so
|
||||
if you plan to depreciate assets, it is wise to make sure of
|
||||
the schemes you will be permitted <em>or required</em> to
|
||||
use.</p>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
@ -1,17 +1,22 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
<head>
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Balance Tracking Report</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1>Balance Tracking Report</h1>
|
||||
<p><em>FIXME: Document this report!</em>
|
||||
<hr>
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
Page.</a></p>
|
||||
|
||||
<p><em>FIXME: Document this report!</em></p>
|
||||
<hr>
|
||||
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
|
@ -1,21 +1,26 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Balance Sheet</title>
|
||||
</head>
|
||||
<body>
|
||||
<h1>Balance Sheet</h1>
|
||||
|
||||
<p>This report summarizes your assets, liabilities, and equity.</p>
|
||||
|
||||
<p>There are currently no options for this report, but the option
|
||||
to specify a date for which the balance sheet is to be calculated
|
||||
will be added soon.</p>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
Page.</a></p>
|
||||
<body>
|
||||
<h1>Balance Sheet</h1>
|
||||
|
||||
<p>This report summarizes your assets, liabilities, and
|
||||
equity.</p>
|
||||
|
||||
<p>There are currently no options for this report, but the
|
||||
option to specify a date for which the balance sheet is to be
|
||||
calculated will be added soon.</p>
|
||||
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
|
@ -2,22 +2,24 @@
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
|
||||
<title></title>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Currency Handling and Double Entry Bookkeeping</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1> Currency Handling and Double Entry Bookkeeping</h1>
|
||||
<h1>Currency Handling and Double Entry Bookkeeping</h1>
|
||||
|
||||
<p>A <a href="xacc-double.html"> Double Entry bookkeeping
|
||||
<p>A <a href="xacc-double.html">Double Entry bookkeeping
|
||||
system</a> stores both values, and requires that all
|
||||
transactions balance, as described in the <a href=
|
||||
"xacc-double.html#IDENTITY"> Double Entry Identity.</a></p>
|
||||
transactions balance, as described in the <a href=
|
||||
"xacc-double.html#IDENTITY">Double Entry Identity.</a></p>
|
||||
|
||||
<p> When we introduce the notion of having multiple currencies,
|
||||
<p>When we introduce the notion of having multiple currencies,
|
||||
or stocks that may vary in price, the identities get a little
|
||||
more complicated, and we introduce the following formulae:</p>
|
||||
|
||||
@ -34,7 +36,7 @@
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<i> <b>SpendAcct:</b> (an ordinary bank/cash acct valued in
|
||||
<i><b>SpendAcct:</b> (an ordinary bank/cash acct valued in
|
||||
USD)</i>
|
||||
<pre>
|
||||
<i>Date xfer from memo cost
|
||||
@ -44,7 +46,7 @@
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<i> <b>JPYAcct</b>: (a currency trading account valued in
|
||||
<i><b>JPYAcct</b>: (a currency trading account valued in
|
||||
yen)</i>
|
||||
<pre>
|
||||
<i>Date xfer from memo purchase rate
|
||||
@ -55,16 +57,16 @@
|
||||
</ul>
|
||||
|
||||
<p>The engine links together all three of these values <tt>
|
||||
(1.0, 150, 0.00667)</tt> permanently and makes it impossible
|
||||
to change one without changing another, so that the grand total
|
||||
is always zero, thereby guaranteeing satisfaction of the <a
|
||||
href="xacc-double.html#IDENTITY"> double entry accounting
|
||||
(1.0, 150, 0.00667)</tt> permanently and makes it impossible to
|
||||
change one without changing another, so that the grand total is
|
||||
always zero, thereby guaranteeing satisfaction of the <a href=
|
||||
"xacc-double.html#IDENTITY">double entry accounting
|
||||
identity.</a></p>
|
||||
|
||||
<h1> ISO Currency Codes</h1>
|
||||
<h1>ISO Currency Codes</h1>
|
||||
<a name="ISOCURR"></a>
|
||||
|
||||
<p> More currencies than you thought possible...</p>
|
||||
<p>More currencies than you thought possible...</p>
|
||||
|
||||
<table border="1">
|
||||
<tr>
|
||||
@ -1202,7 +1204,7 @@
|
||||
</table>
|
||||
<hr>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
@ -2,8 +2,10 @@
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
|
||||
<title></title>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Date Data Input</title>
|
||||
@ -14,31 +16,31 @@
|
||||
The date cell handles the following accelerator keys:
|
||||
|
||||
<ul>
|
||||
<li><tt> +, =</tt> increment day</li>
|
||||
<li><tt>+, =</tt> increment day</li>
|
||||
|
||||
<li><tt> _ , -</tt> decrement day</li>
|
||||
<li><tt>_ , -</tt> decrement day</li>
|
||||
|
||||
<li><tt> } , ]</tt> increment month</li>
|
||||
<li><tt>} , ]</tt> increment month</li>
|
||||
|
||||
<li><tt> { , [</tt> decrement month</li>
|
||||
<li><tt>{ , [</tt> decrement month</li>
|
||||
|
||||
<li><tt> M , m</tt> beginning of month</li>
|
||||
<li><tt>M , m</tt> beginning of month</li>
|
||||
|
||||
<li><tt> H , h</tt> end of month</li>
|
||||
<li><tt>H , h</tt> end of month</li>
|
||||
|
||||
<li><tt> Y , y</tt> beginning of year</li>
|
||||
<li><tt>Y , y</tt> beginning of year</li>
|
||||
|
||||
<li><tt> R , r</tt> end of year</li>
|
||||
<li><tt>R , r</tt> end of year</li>
|
||||
|
||||
<li><tt> T , t</tt> today GnuCash can be compiled to use
|
||||
<li><tt>T , t</tt> today GnuCash can be compiled to use
|
||||
either European style dates or US Style dates.</li>
|
||||
|
||||
<li><tt>Grep</tt> for <var> UK_DATES</var> in <tt>
|
||||
<li><tt>Grep</tt> for <var>UK_DATES</var> in <tt>
|
||||
dates.h</tt></li>
|
||||
</ul>
|
||||
<hr>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
@ -2,8 +2,10 @@
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
|
||||
<title></title>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Understanding Double Entry Accounting</title>
|
||||
@ -11,88 +13,94 @@
|
||||
|
||||
<body>
|
||||
<h1>Why Use Double Entry Accounting?</h1>
|
||||
<p>If you are a beginner, a novice, you need double entry accounting
|
||||
to help you avoid beginner mistakes. It will keep you from creating
|
||||
an unauditable mess. It will make your life easier, and it will make
|
||||
this software easier to understand and to use.
|
||||
And if you are an experienced accountant, then you would only turn ill
|
||||
at the thought of life without it.
|
||||
|
||||
<p>If you are a novice to accounting, you <em>need</em> double
|
||||
entry accounting to help you keep your accounts straight. It
|
||||
will keep you from creating an unverifiable mess. It will make
|
||||
your life easier, and it will make this software easier to
|
||||
understand and to use.</p>
|
||||
|
||||
<p>And if you are an experienced accountant, you would likely
|
||||
feel <em>ill</em> at the thought of life without it.</p>
|
||||
|
||||
<h1>What is Double Entry Accounting?</h1>
|
||||
|
||||
<p> Double entry bookkeeping is an accounting methodology
|
||||
<p>Double entry bookkeeping is an accounting methodology
|
||||
introduced in the 13th century to to make sure that each
|
||||
accounts and indeed <em> each transaction</em> is properly
|
||||
accounts and indeed <em>each transaction</em> is properly
|
||||
balanced.</p>
|
||||
|
||||
<p> When these are all required to balance, the likelihood of
|
||||
<p>When these are all required to balance, the likelihood of
|
||||
data-entry errors is greatly reduced. For large, complex sets
|
||||
of accounts with many transactions, it is distressingly easy to
|
||||
make errors that may go undetected for a long time, and be
|
||||
appallingly difficult to track down, even when double-entry
|
||||
bookkeeping is used.</p>
|
||||
|
||||
<p> A double-entry transaction is a transaction that contains
|
||||
<p>A double-entry transaction is a transaction that contains
|
||||
entries for two (or more) accounts that balance against one
|
||||
another. One account is <em>debited</em> by an amount exactly
|
||||
equal to what the other is <em>credited.</em> By ensuring that
|
||||
each transaction balances, a balanced set of accounts is
|
||||
guaranteed. This doesn't prevent you from having errors, but
|
||||
certainly eliminates the large class of <b> I forgot to enter
|
||||
certainly eliminates the large class of <b>I forgot to enter
|
||||
that part of the transaction</b> errors.</p>
|
||||
|
||||
<p> Double-entry may be introduced in a more intuitive way via
|
||||
<p>Double-entry may be introduced in a more intuitive way via
|
||||
the notion of a transfer from one bank account to another,
|
||||
where an amount is taken out of one bank account and deposited
|
||||
in the other. This is effectively the "rule" of double entry
|
||||
accounting; if you add something in to one account, you <em>
|
||||
have</em> to have another component to that transaction to
|
||||
balance this.</p>
|
||||
balance it.</p>
|
||||
|
||||
<p> <b> Not-quite-an-aside:</b> If you look at your bank
|
||||
<p><b>Not-quite-an-aside:</b> If you look at your bank
|
||||
statements, they are typically written up from the <b>
|
||||
bank's</b> perspective, which is exactly <em> opposite</em> to
|
||||
bank's</b> perspective, which is exactly <em>opposite</em> to
|
||||
yours. For instance, when you put money in, establishing a
|
||||
deposit, this establishes a <b> DEBT</b> on their part.</p>
|
||||
deposit, this establishes a <b>DEBT</b> on their part.</p>
|
||||
As a result, "newcomers to accounting," who only see the terms
|
||||
"Debit" and "Credit" on statements from their bank seem to get
|
||||
fairly confused about this.
|
||||
|
||||
<p> The perhaps less obvious extension is the notion that
|
||||
double entry can be used to represent income and expenses as
|
||||
well as bank transfers. See the <a href="xacc-expense.html">
|
||||
<p>The perhaps less obvious extension is the notion that double
|
||||
entry can be used to represent income and expenses as well as
|
||||
bank transfers. See the <a href="xacc-expense.html">
|
||||
Income/Expense</a> page for a more detailed discussion of
|
||||
that.</p>
|
||||
|
||||
<p> <a name="IDENTITY"> In a traditional system that records
|
||||
<p><a name="IDENTITY">In a traditional system that records
|
||||
debits and credits separately, the identity that all
|
||||
transactions are required to satisfy is that <tt> Total of
|
||||
transactions are required to satisfy is that <tt>Total of
|
||||
Debits = Total of Credits.</tt></a></p>
|
||||
|
||||
<p> The fact that the identity requires merely that the <em>
|
||||
<p>The fact that the identity requires merely that the <em>
|
||||
total</em> balances means that it is a little bit misleading to
|
||||
call this <em> double</em>-entry bookkeeping; it would be
|
||||
somewhat more accurate to call it <em> multiple-</em>entry
|
||||
call this <em>double</em>-entry bookkeeping; it would be
|
||||
somewhat more accurate to call it <em>multiple-</em>entry
|
||||
bookkeeping. Unfortunately, there's 700 years of history of use
|
||||
of the term, which sufficiently discourages changing it. (And
|
||||
some people think that UNIX has some crufty old bits of
|
||||
oddness. Hah!)</p>
|
||||
of the term, which sufficiently discourages changing it. (To
|
||||
think some newcomers to UNIX think that it has some crufty old
|
||||
bits of oddness. Hah! We've got UNIX beat by the better part of
|
||||
a millennium!)</p>
|
||||
|
||||
<p> GnuCash treats "Debits" as positive values, and "Credits"
|
||||
as negative values, so that this identity simplifies to <tt>
|
||||
<p>GnuCash treats "Debits" as positive values, and "Credits" as
|
||||
negative values, so that this identity simplifies to <tt>
|
||||
value<sub>1</sub> + value<sub>2</sub> + value<sub>3</sub> + ...
|
||||
= 0</tt></p>
|
||||
|
||||
<h1>Using Double Entry</h1>
|
||||
|
||||
<h2> Creating Transactions</h2>
|
||||
<h2>Creating Transactions</h2>
|
||||
|
||||
<p> To create a double-entry transaction:</p>
|
||||
<p>To create a double-entry transaction:</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
Click on a box in the column marked <tt>Transfer From</tt>
|
||||
on the left-hand side of the register.
|
||||
|
||||
<p> A menu will drop down, listing all of the accounts from
|
||||
<p>A menu will drop down, listing all of the accounts from
|
||||
which a transfer may be made.</p>
|
||||
</li>
|
||||
|
||||
@ -106,31 +114,31 @@ at the thought of life without it.
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<h2> Changing Transactions</h2>
|
||||
<h2>Changing Transactions</h2>
|
||||
|
||||
<p> To <em> change</em> a double-entry transaction:</p>
|
||||
<p>To <em>change</em> a double-entry transaction:</p>
|
||||
|
||||
<p> Simply edit the transaction in any window in which it
|
||||
<p>Simply edit the transaction in any window in which it
|
||||
appears.</p>
|
||||
|
||||
<p> Any changes made will be automatically reflected in both
|
||||
<p>Any changes made will be automatically reflected in both
|
||||
accounts and all windows displaying the transaction.</p>
|
||||
|
||||
<p> Similarly, when a double-entry transaction is deleted, the
|
||||
<p>Similarly, when a double-entry transaction is deleted, the
|
||||
"splits" will be deleted from both accounts, and balances will
|
||||
automatically be recalculated for <em> both</em> accounts.</p>
|
||||
automatically be recalculated for <em>both</em> accounts.</p>
|
||||
|
||||
<p> To change the transfer account, simply select a new account
|
||||
<p>To change the transfer account, simply select a new account
|
||||
from the pull-down menu. When you record the transaction, it
|
||||
will automatically be selected from the old account, and
|
||||
inserted into the new account.</p>
|
||||
|
||||
<h1>Scrubbing Clean</h1>
|
||||
|
||||
<p> GnuCash can be configured to be strict about double entry,
|
||||
<p>GnuCash may be configured to be strict about double entry,
|
||||
or you may configure it to be "loose."</p>
|
||||
|
||||
<p> In "loose" mode, you can create <em>unbalanced
|
||||
<p>In "loose" mode, you can create <em>unbalanced
|
||||
transactions,</em> that is, transactions where the "splits"
|
||||
don't balance to zero. That discards the validation that comes
|
||||
from using the more strict double entry scheme, which is
|
||||
@ -138,27 +146,36 @@ at the thought of life without it.
|
||||
|
||||
<ul>
|
||||
<li>If you aren't sure of what you're doing, you likely do
|
||||
not want to discard the validation of <b> double entry,</b>
|
||||
as this helps you keep your accounts balanced even when
|
||||
you're not perfectly clear on this.</li>
|
||||
not want to discard the validation of <b>double entry,</b> as
|
||||
this helps you keep your accounts balanced even when you're
|
||||
not perfectly clear on this.</li>
|
||||
|
||||
<li>If you are an <em> accounting whiz,</em> you'll know that
|
||||
it's <em> really important</em> to keep things in balance,
|
||||
and again will prefer <b> double entry.</b></li>
|
||||
<li>If you are an <em>accounting whiz,</em> you'll know that
|
||||
it's <em>really important</em> to keep things in balance, and
|
||||
again will prefer <b>double entry.</b></li>
|
||||
</ul>
|
||||
|
||||
<p> But if you decide to "outsmart the system," and have a
|
||||
<p>But if you decide to "outsmart the system," and have a
|
||||
number of unbalanced transactions, you'll probably want to
|
||||
clean this up at some point. To clean up these unbalanced
|
||||
transactions, you <b> Scrub</b> the account clean by choosing
|
||||
<tt>Scrub</tt> from the window menu. This will examine each
|
||||
transaction; if the transaction doesn't balance, a split entry
|
||||
will be created and placed into an account named <b>
|
||||
Unbalanced.</b> You may then review these splits and move them
|
||||
to their proper accounts.</p>
|
||||
transactions, you <b>Scrub</b> the account clean by choosing
|
||||
<tt>Scrub</tt> from the window menu.</p>
|
||||
|
||||
<p>The process will examine each transaction; if the
|
||||
transaction doesn't balance, a split entry will be created and
|
||||
placed into an account named <b>Unbalanced.</b> You may then
|
||||
review these splits and move them to their proper accounts.</p>
|
||||
|
||||
<p><b>Warning: Functionality Changing...</b></p>
|
||||
|
||||
<p>At present, control over whether GnuCash is "strict" or
|
||||
"loose" is established at compile time, and defaults to <b>
|
||||
strict.</b></p>
|
||||
|
||||
<p>In the future, there will be no option of "looseness."</p>
|
||||
<hr>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
@ -2,49 +2,54 @@
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
|
||||
<title></title>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>GnuCash and the EURO</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1> GnuCash and the EURO</h1>
|
||||
<h1>GnuCash and the EURO</h1>
|
||||
|
||||
<h2> Introduction</h2>
|
||||
<h2>Introduction</h2>
|
||||
|
||||
<p>On January 1, 1999, eleven European Union countries formed
|
||||
an economic and monetary union (EMU) and started using a single
|
||||
currency - the euro. These countries locked the exchange rates
|
||||
of their national currencies to the euro and are sharing the
|
||||
new currency.</p>
|
||||
<p>However, euro notes and coins will not be available until
|
||||
|
||||
<p>However, euro notes and coins will not be available until
|
||||
January 1, 2001. Until then, the old national currency notes
|
||||
and coins (French francs, Deutschmarks etc) will continue to
|
||||
circulate. But in law they are part of the euro. Their value
|
||||
in euro is completely fixed. All kinds of cashless monetary
|
||||
circulate. But in law they are part of the euro. Their value in
|
||||
euro is completely fixed. All kinds of cashless monetary
|
||||
transactions like cheques or wire transfers are possible in
|
||||
euro</p>
|
||||
|
||||
<p>You can find more information about the euro at:
|
||||
<a href="http://europa.eu.int/euro"> http://europa.eu.int/euro
|
||||
</a>.</p>
|
||||
<p>You can find more information about the euro at: <a href=
|
||||
"http://europa.eu.int/euro">http://europa.eu.int/euro</a> .</p>
|
||||
|
||||
<h2> EMU Member Countries and Exchange Rates</h2>
|
||||
<h2>EMU Member Countries and Exchange Rates</h2>
|
||||
<a name="euro_iso_curr"></a>
|
||||
|
||||
<a name="euro_iso_curr"></a>
|
||||
|
||||
<p>The following table shows the EMU member countries and
|
||||
the respective exchange rates of the euro to the old national
|
||||
currencies. More countries are expected to join the EMU later.</p>
|
||||
<p>The following table shows the EMU member countries and the
|
||||
respective exchange rates of the euro to the old national
|
||||
currencies. More countries are expected to join the EMU
|
||||
later.</p>
|
||||
|
||||
<table border="1">
|
||||
<tr>
|
||||
<th>Country</th>
|
||||
|
||||
<th>ISO Code</th>
|
||||
<th>Full Description</th>
|
||||
<th>Exchange Rate</th>
|
||||
|
||||
<th>Full Description</th>
|
||||
|
||||
<th>Exchange Rate</th>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
@ -53,94 +58,128 @@
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Austria</td>
|
||||
<td>ATS</th>
|
||||
<td>Austrian Schilling</td>
|
||||
<td>1 euro = 13.7603 S</td>
|
||||
<td>Austria</td>
|
||||
|
||||
<td>ATS</td>
|
||||
|
||||
<td>Austrian Schilling</td>
|
||||
|
||||
<td>1 euro = 13.7603 S</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Belgium</td>
|
||||
<td>BEF</th>
|
||||
<td>Belgian Franc</td>
|
||||
<td>1 euro = 40.3399 bfrs</td>
|
||||
<td>Belgium</td>
|
||||
|
||||
<td>BEF</td>
|
||||
|
||||
<td>Belgian Franc</td>
|
||||
|
||||
<td>1 euro = 40.3399 bfrs</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Finland</td>
|
||||
<td>FIM</th>
|
||||
<td>Finnish Mark</td>
|
||||
<td>1 euro = 5.94573 Fmk</td>
|
||||
<td>Finland</td>
|
||||
|
||||
<td>FIM</td>
|
||||
|
||||
<td>Finnish Mark</td>
|
||||
|
||||
<td>1 euro = 5.94573 Fmk</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>France</td>
|
||||
<td>FRF</th>
|
||||
<td>French Franc</td>
|
||||
<td>1 euro = 6.55957 FF</td>
|
||||
<td>France</td>
|
||||
|
||||
<td>FRF</td>
|
||||
|
||||
<td>French Franc</td>
|
||||
|
||||
<td>1 euro = 6.55957 FF</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Germany</td>
|
||||
<td>DEM</th>
|
||||
<td>German Mark</td>
|
||||
<td>1 euro = 1.95538 DM</td>
|
||||
<td>Germany</td>
|
||||
|
||||
<td>DEM</td>
|
||||
|
||||
<td>German Mark</td>
|
||||
|
||||
<td>1 euro = 1.95538 DM</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Ireland</td>
|
||||
<td>IEP</th>
|
||||
<td>Irish Pound</td>
|
||||
<td>1 euro = 0.787564 Ir. £</td>
|
||||
<td>Ireland</td>
|
||||
|
||||
<td>IEP</td>
|
||||
|
||||
<td>Irish Pound</td>
|
||||
|
||||
<td>1 euro = 0.787564 Ir. £</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Italy</td>
|
||||
<td>ITL</th>
|
||||
<td>Italian Lira</td>
|
||||
<td>1 euro = 1936.27 Lit</td>
|
||||
<td>Italy</td>
|
||||
|
||||
<td>ITL</td>
|
||||
|
||||
<td>Italian Lira</td>
|
||||
|
||||
<td>1 euro = 1936.27 Lit</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Luxembourg</td>
|
||||
<td>LUF</th>
|
||||
<td>Luxembourgian Franc</td>
|
||||
<td>1 euro = 40.3399 lfrs</td>
|
||||
<td>Luxembourg</td>
|
||||
|
||||
<td>LUF</td>
|
||||
|
||||
<td>Luxembourgian Franc</td>
|
||||
|
||||
<td>1 euro = 40.3399 lfrs</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Netherlands</td>
|
||||
<td>NLG</th>
|
||||
<td>Dutch Guilder</td>
|
||||
<td>1 euro = 2.20371 hfl</td>
|
||||
<td>Netherlands</td>
|
||||
|
||||
<td>NLG</td>
|
||||
|
||||
<td>Dutch Guilder</td>
|
||||
|
||||
<td>1 euro = 2.20371 hfl</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Portugal</td>
|
||||
<td>PTE</th>
|
||||
<td>Portuguese Escudo</td>
|
||||
<td>1 euro = 200.482 Esc</td>
|
||||
<td>Portugal</td>
|
||||
|
||||
<td>PTE</td>
|
||||
|
||||
<td>Portuguese Escudo</td>
|
||||
|
||||
<td>1 euro = 200.482 Esc</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Spain</td>
|
||||
<td>ESP</th>
|
||||
<td>Spanish Peseta</td>
|
||||
<td>1 euro = 166.386 Ptas</td>
|
||||
<td>Spain</td>
|
||||
|
||||
<td>ESP</td>
|
||||
|
||||
<td>Spanish Peseta</td>
|
||||
|
||||
<td>1 euro = 166.386 Ptas</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<h2> EURO support in GnuCash</h2>
|
||||
<h2>EURO support in GnuCash</h2>
|
||||
|
||||
<p>You can enable euro support in GnuCash in the international
|
||||
category of the <a href="xacc-globalprefs.html">preferences</a>
|
||||
dialog box. If your system locale specifies one of the
|
||||
<a href="#euro_iso_curr">EMU member currencies</a>, euro support
|
||||
is enabled by default.</p>
|
||||
dialog box. If your system locale specifies one of the <a href=
|
||||
"#euro_iso_curr">EMU member currencies</a>, euro support is
|
||||
enabled by default.</p>
|
||||
|
||||
<p>FIXME: Actual documentation with screenshots and so on</p>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
|
@ -1,7 +1,9 @@
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Using Expense/Income Accounts</title>
|
||||
@ -10,53 +12,52 @@
|
||||
<body>
|
||||
<h1>What are Incomes and Expenses?</h1>
|
||||
|
||||
<p> The words "Income" and "Expense" are beguilingly simple;
|
||||
everyone <em> thinks</em> they know what they mean; this <em>
|
||||
usually</em> is that <b> When I spend something, this is an
|
||||
<p>The words "Income" and "Expense" are beguilingly simple;
|
||||
everyone <em>thinks</em> they know what they mean; this <em>
|
||||
usually</em> is that <b>When I spend something, this is an
|
||||
expense, and when I get money, this is an income.</b></p>
|
||||
|
||||
<p> This oversimplifies things somewhat; it is often a <em>
|
||||
<p>This oversimplifies things somewhat; it is often a <em>
|
||||
good-enough</em> approximation when doing personal accounting,
|
||||
but when running a business, incomes and expenses often have be
|
||||
recognized as having occurred when some "critical event" takes
|
||||
place that may not perfectly correspond to "when cash comes in
|
||||
or goes out."</p>
|
||||
|
||||
<p> For instance, companies usually have to recognize income
|
||||
<em> when the sale occurs.</em> That may mean that I have to
|
||||
recognize a $100,000 sale <em> at the moment I and the customer
|
||||
<p>For instance, companies usually have to recognize income
|
||||
<em>when the sale occurs.</em> That may mean that I have to
|
||||
recognize a $100,000 sale <em>at the moment I and the customer
|
||||
shake hands on the deal.</em></p>
|
||||
|
||||
<p> Since the money hasn't come in, the sale has to be
|
||||
estimated in other way; the way this is done is to <b>
|
||||
accrue</b> a sale at that time, and in making the transaction
|
||||
balance, rather than adding something in to cash, I'd add the
|
||||
$100,000 sale to <b> Accounts Receivable.</b></p>
|
||||
<p>Since the money hasn't come in, the sale has to be estimated
|
||||
in other way; the way this is done is to <b>accrue</b> a sale
|
||||
at that time, and in making the transaction balance, rather
|
||||
than adding something in to cash, I'd add the $100,000 sale to
|
||||
<b>Accounts Receivable.</b></p>
|
||||
|
||||
<p> In a double entry system, two kinds of accounts must be
|
||||
<p>In a double entry system, two kinds of accounts must be
|
||||
created: some of type "Income" and others of type "Expense."
|
||||
(There tend to be a lot more different kinds of expenses than
|
||||
there are of incomes.)</p>
|
||||
|
||||
<p> Income such as salary, wages, bank interest and stock
|
||||
<p>Income such as salary, wages, bank interest and stock
|
||||
dividends are then recorded as transfers from an income account
|
||||
to a bank (or, in general, some asset) account. Similarly,
|
||||
expenses are recorded as transfers from a credit card account
|
||||
(or, in general, a liability account).</p>
|
||||
|
||||
<p> Another way of describing the requirement for "double
|
||||
entry" is that when you receive an income, two things
|
||||
happen:</p>
|
||||
<p>Another way of describing the requirement for "double entry"
|
||||
is that when you receive an income, two things happen:</p>
|
||||
|
||||
<ul>
|
||||
<li>You receive a sum of <em> money,</em> and must record
|
||||
that effect on your bank account.</li>
|
||||
<li>You receive a sum of <em>money,</em> and must record that
|
||||
effect on your bank account.</li>
|
||||
|
||||
<li>You have received an income, and must record that effect
|
||||
on an income account.</li>
|
||||
</ul>
|
||||
|
||||
<p> When, for instance, salary is deposited in a bank account,
|
||||
<p>When, for instance, salary is deposited in a bank account,
|
||||
the bank account is credited, and the income account is
|
||||
debited, thus:</p>
|
||||
|
||||
@ -137,72 +138,72 @@
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<p> There may be a whole lot more than two entries in the
|
||||
<p>There may be a whole lot more than two entries in the
|
||||
transaction, but the total sum of the Debits, $1,600.00, still
|
||||
equals the total sum of the credits, $1,600.00.</p>
|
||||
|
||||
<p> If, as with <b>GnuCash,</b> everything is forced onto one
|
||||
column, so that <b> debits</b> are represented by positive
|
||||
values, and <b> credits</b> are represented by negative values,
|
||||
<p>If, as with <b>GnuCash,</b> everything is forced onto one
|
||||
column, so that <b>debits</b> are represented by positive
|
||||
values, and <b>credits</b> are represented by negative values,
|
||||
the income/expense accounts do a slightly non-intuitive thing
|
||||
and you see incomes as <em> negative</em> values. That <em>
|
||||
and you see incomes as <em>negative</em> values. That <em>
|
||||
appears</em> contrary to intuition, but is nonetheless
|
||||
necessary in order for the <a href="xacc-double.html#IDENTITY">
|
||||
double-entry bookkeeping identity to hold true.</a></p>
|
||||
double-entry bookkeeping identity to hold true.</a></p>
|
||||
|
||||
<p> Another way in which income and expense accounts are
|
||||
special is that their account totals do not directly appear on
|
||||
a balance sheet. A balance sheet shows "Net Worth": the sum of
|
||||
<p>Another way in which income and expense accounts are special
|
||||
is that their account totals do not directly appear on a
|
||||
balance sheet. A balance sheet shows "Net Worth": the sum of
|
||||
all assets minus all liabilities.</p>
|
||||
|
||||
<p> Income and expenses are neither assets nor liabilities, and
|
||||
<p>Income and expenses are neither assets nor liabilities, and
|
||||
so do not appear on the balance sheet. What appears on the
|
||||
balance sheet is their effects on <b> equity.</b></p>
|
||||
balance sheet is their effects on <b>equity.</b></p>
|
||||
|
||||
<p> There is a separate report, a "Profit and Loss" (P&L)
|
||||
<p>There is a separate report, a "Profit and Loss" (P&L)
|
||||
report, to analyze income and expenses. The total profit (or
|
||||
loss) is calculated as total income less total expenses. In a
|
||||
nicely symmetrical fashion, since assets and liabilities are
|
||||
neither income or expenses, <em> they</em> correspondingly do
|
||||
neither income or expenses, <em>they</em> correspondingly do
|
||||
not appear on a P&L statement.</p>
|
||||
|
||||
<p> Even though these accounts may be somewhat "special", you
|
||||
do not need to do anything particularly special to use income
|
||||
and expense accounts. GnuCash handles the values automatically,
|
||||
so that if you record properly the effects of the transactions
|
||||
on your bank account or credit card, the income/expense side of
|
||||
<p>Even though these accounts may be somewhat "special", you do
|
||||
not need to do anything particularly special to use income and
|
||||
expense accounts. GnuCash handles the values automatically, so
|
||||
that if you record properly the effects of the transactions on
|
||||
your bank account or credit card, the income/expense side of
|
||||
the transaction should also be handled correctly.</p>
|
||||
|
||||
<p> The time when things get "peculiar," and when you need to
|
||||
<p>The time when things get "peculiar," and when you need to
|
||||
more deeply understand this, is when amounts are transferred
|
||||
between income/expense accounts. (The <i> causes</i> for such
|
||||
between income/expense accounts. (The <i>causes</i> for such
|
||||
transfers tend to be somewhat peculiar, so it's pretty fair for
|
||||
this to be a pretty odd situation.)</p>
|
||||
|
||||
<h1>Using Income/Expense Accounts</h1>
|
||||
|
||||
<p> To use an income/expense account, simply create one from
|
||||
the "New Account" dialogue window, and then be sure to transfer
|
||||
<p>To use an income/expense account, simply create one from the
|
||||
"New Account" dialogue window, and then be sure to transfer
|
||||
income/expenses to it as you record paychecks, interest,
|
||||
etc.</p>
|
||||
|
||||
<p> You will doubtless wish to create quite a number of income
|
||||
and expense accounts; it may be worth looking at the <a href=
|
||||
"xacc-groups.html#SAMPLECHART"> Sample Chart of Accounts</a>
|
||||
for ideas.</p>
|
||||
<p>You will doubtless wish to create quite a number of income
|
||||
and expense accounts; it may be worth looking at the <a href=
|
||||
"xacc-groups.html#SAMPLECHART">Sample Chart of Accounts</a> for
|
||||
ideas.</p>
|
||||
|
||||
<p> This partitioning of incomes and expenses is likely to
|
||||
prove particularly useful for North Americans when <i>income
|
||||
tax time</i> rolls around.</p>
|
||||
<p>This partitioning of incomes and expenses is likely to prove
|
||||
particularly useful for North Americans when <i>income tax
|
||||
time</i> rolls around.</p>
|
||||
|
||||
<h1> Use of Terminology In Other Software</h1>
|
||||
<h1>Use of Terminology In Other Software</h1>
|
||||
|
||||
<p> If you have used other personal finance software, be aware
|
||||
that <a href="xacc-quicken.html#QUICKENCATS"> Quicken calls
|
||||
them "Categories."</a></p>
|
||||
<p>If you have used other personal finance software, be aware
|
||||
that <a href="xacc-quicken.html#QUICKENCATS">Quicken calls them
|
||||
"Categories."</a></p>
|
||||
<hr>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
@ -33,30 +33,46 @@
|
||||
<a name="overview"><h2>Overview</h2></a>
|
||||
|
||||
<p>The Find Transactions dialog allows you to search for
|
||||
transactions which match criteria that you specify, including
|
||||
account(s) affected by the transaction, the value of the transaction,
|
||||
the date, the memo, the description, etc. You can bring up the Find
|
||||
Transactions dialog by clicking on the "Find" button in the main
|
||||
GnuCash window or any register display window. The results of your
|
||||
search will be shown in a register display similar to the ones used to
|
||||
display your accounts, with the window title "Search Results".
|
||||
transactions which match criteria that you specify, including:
|
||||
<ul>
|
||||
<li> Account(s) affected by the transaction,
|
||||
<li> Value of the transaction,
|
||||
<li> Date
|
||||
<li> Memo field
|
||||
<li> Transaction description
|
||||
<ul>
|
||||
etc.
|
||||
|
||||
<P> You may bring up the <b> Find Transactions </b> dialog by clicking
|
||||
on the "Find" button in the main GnuCash window or any register
|
||||
display window.
|
||||
|
||||
<P> The results of your search will be shown in a register display
|
||||
similar to the ones used to display your accounts, with the window
|
||||
title "Search Results".
|
||||
|
||||
<p>Clicking the "Find" button again within a Search Results
|
||||
register window allows you to add additional terms to the query whose
|
||||
results are displayed in that window. By combining multiple searches,
|
||||
you can create very sophisticated queries to show you exactly the
|
||||
results are displayed in that window. <P> By combining multiple searches,
|
||||
you may construct rather sophisticated queries to display exactly the
|
||||
subset of your transactions that you want to see.
|
||||
|
||||
<a href="#toc">Table of Contents</a>
|
||||
|
||||
<a name="how-to"><h2>How to use the Find Transactions dialog</h2></a>
|
||||
|
||||
<p>The Find Transactions dialog has two main parts. The upper
|
||||
<p>The Find Transactions dialog has two main parts.
|
||||
|
||||
<ul>
|
||||
<li> The upper
|
||||
part of the dialog is a Notebook with tabs that allow you to specify
|
||||
the conditions of your search. See <a href="#setup">Setting up a
|
||||
search</a> for details on each search type. The lower part of the
|
||||
the conditions of your search. <p> See <a href="#setup">Setting up a
|
||||
search</a> for details on each search type.
|
||||
|
||||
<li>The lower part of the
|
||||
dialog is a selector which allows you to specify how the results of
|
||||
the search are to be combined with any previous search.
|
||||
</uL>
|
||||
|
||||
<p>If you get the Find Transactions dialog by clicking the Find
|
||||
button in the main GnuCash window or any normal account display
|
||||
@ -107,9 +123,9 @@ accounts is to be displayed.
|
||||
|
||||
<p>If you select "All" accounts from the picker at the top of the
|
||||
tab, the only transactions that will be show are those which affect
|
||||
all the selected accounts. For example, if you select "My Checking
|
||||
Account" and "My VISA Account" and then choose "All", only transfers
|
||||
from Checking to Visa will be shown.
|
||||
all the selected accounts. <P> For example, if you select <b>My
|
||||
Checking Account<b> and <b> My VISA Account</b> and then choose <B>
|
||||
All</b>, only transfers from Checking to Visa will be shown.
|
||||
|
||||
<p>If you select "Any" from the picker, transactions affecting any
|
||||
selected amount will be shown. For example, if you select "My
|
||||
@ -121,15 +137,15 @@ together in the Search Results window.
|
||||
|
||||
<p>In the Date tab, you can specify a date range for the
|
||||
transactions you wish to find. The year, month, and day fields are in
|
||||
the order you specify in Preferences:International:Date Format.
|
||||
the order you specify in <tt> Preferences:International:Date Format</tt>.
|
||||
|
||||
<p>If you want to locate any transaction before a certain date,
|
||||
specify your date in the second date entry and put a very early date
|
||||
in the first date entry. The default date is January 1, 1900, which
|
||||
should be early enough for most purposes. Similarly, if you want to
|
||||
find any transaction after a certain date, put the date in the first
|
||||
date entry and put a date after your last transaction in the second
|
||||
entry.
|
||||
specify your date in the second date entry and put a distant date in
|
||||
the past in the first date entry. The default date is January 1,
|
||||
1900, which should be distant enough for most peoples' purposes. <P>
|
||||
Similarly, if you want to find any transaction after a certain date,
|
||||
put the date in the first date entry and put a date after your last
|
||||
transaction in the second entry.
|
||||
|
||||
<a name="amount"><h3>Amount searches</a></h3>
|
||||
|
||||
@ -146,12 +162,12 @@ interested in debits, credits, or both.
|
||||
|
||||
<p>In the Description, Number, Memo, and Action tabs, you can
|
||||
specify a string which is matched against the respective fields of
|
||||
splits and transactions. By default, the match used is a
|
||||
case-insensitive substring match. If you select the "Case sensitive"
|
||||
toggle button, the search is a case-sensitive substring match. If the
|
||||
splits and transactions. <ul><li> By default, the match used is a
|
||||
case-insensitive substring match. <li> If you select the "Case sensitive"
|
||||
toggle button, the search is a case-sensitive substring match. <li>If the
|
||||
"Regular expression" button is selected, the match interprets the
|
||||
string you enter as a POSIX extended regular expression; case
|
||||
sensitivity is still determined by the "Case sensitive" button.
|
||||
sensitivity is still determined by the "Case sensitive" button.</ul>
|
||||
|
||||
<a href="#toc">Table of Contents</a>
|
||||
|
||||
|
@ -1,42 +1,50 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Preferences</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1>Preferences</h1>
|
||||
<p>You can customize the behavior of
|
||||
GnuCash by changing the settings in this dialog box.All settings
|
||||
are automatically saved so changes are preserved for future
|
||||
sessions.</p>
|
||||
<h1>Preferences</h1>
|
||||
|
||||
<p>You can customize the behavior of GnuCash by changing the
|
||||
settings in this dialog box.All settings are automatically
|
||||
saved so changes are preserved for future sessions.</p>
|
||||
|
||||
<p>To change settings, simply click to select the appropriate
|
||||
page, then make appropriate changes, and click the "Apply"
|
||||
button to see
|
||||
your changes take effect. Clicking "OK" applies changes, then
|
||||
closes the properties dialog box.
|
||||
them. The "Close" button simply closes the dialog box without
|
||||
applying the latest changes.</p>
|
||||
page, then make appropriate changes, and click the "Apply"
|
||||
button to see your changes take effect. Clicking "OK" applies
|
||||
changes, then closes the properties dialog box. them. The
|
||||
"Close" button simply closes the dialog box without applying
|
||||
the latest changes.</p>
|
||||
|
||||
<p>The settings are grouped into the following categories:</p>
|
||||
<ul><li><b>Account Fields:</b> sets which fields are displayed in
|
||||
the account list of the main window.</li>
|
||||
<li><b>Account Types:</b> sets which account types are displayed
|
||||
in the main window.</li>
|
||||
|
||||
<ul>
|
||||
<li><b>Account Fields:</b> sets which fields are displayed in
|
||||
the account list of the main window.</li>
|
||||
|
||||
<li><b>Account Types:</b> sets which account types are
|
||||
displayed in the main window.</li>
|
||||
|
||||
<li><b>General:</b> anything that doesn't fit anywhere
|
||||
else.</li>
|
||||
<li><b>International:</b> Options relating to date and time
|
||||
display formats.</li>
|
||||
<li><b>Register:</b> Options relating to the default appearance
|
||||
of account registers.</li>
|
||||
else.</li>
|
||||
|
||||
<li><b>International:</b> Options relating to date and time
|
||||
display formats.</li>
|
||||
|
||||
<li><b>Register:</b> Options relating to the default
|
||||
appearance of account registers.</li>
|
||||
</ul>
|
||||
<hr>
|
||||
|
||||
|
||||
<hr><p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
|
||||
|
@ -1,42 +1,50 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Preferences</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1>Preferences</h1>
|
||||
<p>You can customize the behavior of
|
||||
GnuCash by changing the settings in this dialog box.All settings
|
||||
are automatically saved so changes are preserved for future
|
||||
sessions.</p>
|
||||
<h1>Preferences</h1>
|
||||
|
||||
<p>You can customize the behavior of GnuCash by changing the
|
||||
settings in this dialog box.All settings are automatically
|
||||
saved so changes are preserved for future sessions.</p>
|
||||
|
||||
<p>To change settings, simply click to select the appropriate
|
||||
page, then make appropriate changes, and click the "Apply"
|
||||
button to see
|
||||
your changes take effect. Clicking "OK" applies changes, then
|
||||
closes the properties dialog box.
|
||||
them. The "Close" button simply closes the dialog box without
|
||||
applying the latest changes.</p>
|
||||
page, then make appropriate changes, and click the "Apply"
|
||||
button to see your changes take effect. Clicking "OK" applies
|
||||
changes, then closes the properties dialog box. them. The
|
||||
"Close" button simply closes the dialog box without applying
|
||||
the latest changes.</p>
|
||||
|
||||
<p>The settings are grouped into the following categories:</p>
|
||||
<ul><li><b>Account Fields:</b> sets which fields are displayed in
|
||||
the account list of the main window.</li>
|
||||
<li><b>Account Types:</b> sets which account types are displayed
|
||||
in the main window.</li>
|
||||
|
||||
<ul>
|
||||
<li><b>Account Fields:</b> sets which fields are displayed in
|
||||
the account list of the main window.</li>
|
||||
|
||||
<li><b>Account Types:</b> sets which account types are
|
||||
displayed in the main window.</li>
|
||||
|
||||
<li><b>General:</b> anything that doesn't fit anywhere
|
||||
else.</li>
|
||||
<li><b>International:</b> Options relating to date and time
|
||||
display formats.</li>
|
||||
<li><b>Register:</b> Options relating to the default appearance
|
||||
of account registers.</li>
|
||||
else.</li>
|
||||
|
||||
<li><b>International:</b> Options relating to date and time
|
||||
display formats.</li>
|
||||
|
||||
<li><b>Register:</b> Options relating to the default
|
||||
appearance of account registers.</li>
|
||||
</ul>
|
||||
<hr>
|
||||
|
||||
|
||||
<hr><p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
|
||||
|
@ -2,7 +2,8 @@
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>GNU General Public License</title>
|
||||
@ -17,14 +18,14 @@
|
||||
Copyright (C) 1989, 1991 Free Software Foundation, Inc. 675
|
||||
Mass Ave, Cambridge, MA 02139, USA
|
||||
|
||||
<p> Everyone is permitted to copy and distribute verbatim
|
||||
<p>Everyone is permitted to copy and distribute verbatim
|
||||
copies of this license document, but changing it is not
|
||||
allowed.</p>
|
||||
</center>
|
||||
|
||||
<h3><a name="SEC001">Preamble</a></h3>
|
||||
|
||||
<p> The licenses for most software are designed to take away
|
||||
<p>The licenses for most software are designed to take away
|
||||
your freedom to share and change it. By contrast, the GNU
|
||||
General Public License is intended to guarantee your freedom to
|
||||
share and change free software--to make sure the software is
|
||||
@ -35,53 +36,53 @@
|
||||
General Public License instead.) You can apply it to your
|
||||
programs, too.</p>
|
||||
|
||||
<p> When we speak of free software, we are referring to
|
||||
freedom, not price. Our General Public Licenses are designed to
|
||||
make sure that you have the freedom to distribute copies of
|
||||
free software (and charge for this service if you wish), that
|
||||
you receive source code or can get it if you want it, that you
|
||||
can change the software or use pieces of it in new free
|
||||
programs; and that you know you can do these things.</p>
|
||||
<p>When we speak of free software, we are referring to freedom,
|
||||
not price. Our General Public Licenses are designed to make
|
||||
sure that you have the freedom to distribute copies of free
|
||||
software (and charge for this service if you wish), that you
|
||||
receive source code or can get it if you want it, that you can
|
||||
change the software or use pieces of it in new free programs;
|
||||
and that you know you can do these things.</p>
|
||||
|
||||
<p> To protect your rights, we need to make restrictions that
|
||||
<p>To protect your rights, we need to make restrictions that
|
||||
forbid anyone to deny you these rights or to ask you to
|
||||
surrender the rights. These restrictions translate to certain
|
||||
responsibilities for you if you distribute copies of the
|
||||
software, or if you modify it.</p>
|
||||
|
||||
<p> For example, if you distribute copies of such a program,
|
||||
<p>For example, if you distribute copies of such a program,
|
||||
whether gratis or for a fee, you must give the recipients all
|
||||
the rights that you have. You must make sure that they, too,
|
||||
receive or can get the source code. And you must show them
|
||||
these terms so they know their rights.</p>
|
||||
|
||||
<p> We protect your rights with two steps: (1) copyright the
|
||||
<p>We protect your rights with two steps: (1) copyright the
|
||||
software, and (2) offer you this license which gives you legal
|
||||
permission to copy, distribute and/or modify the software.</p>
|
||||
|
||||
<p> Also, for each author's protection and ours, we want to
|
||||
make certain that everyone understands that there is no
|
||||
warranty for this free software. If the software is modified by
|
||||
someone else and passed on, we want its recipients to know that
|
||||
what they have is not the original, so that any problems
|
||||
introduced by others will not reflect on the original authors'
|
||||
<p>Also, for each author's protection and ours, we want to make
|
||||
certain that everyone understands that there is no warranty for
|
||||
this free software. If the software is modified by someone else
|
||||
and passed on, we want its recipients to know that what they
|
||||
have is not the original, so that any problems introduced by
|
||||
others will not reflect on the original authors'
|
||||
reputations.</p>
|
||||
|
||||
<p> Finally, any free program is threatened constantly by
|
||||
<p>Finally, any free program is threatened constantly by
|
||||
software patents. We wish to avoid the danger that
|
||||
redistributors of a free program will individually obtain
|
||||
patent licenses, in effect making the program proprietary. To
|
||||
prevent this, we have made it clear that any patent must be
|
||||
licensed for everyone's free use or not licensed at all.</p>
|
||||
|
||||
<p> The precise terms and conditions for copying, distribution
|
||||
<p>The precise terms and conditions for copying, distribution
|
||||
and modification follow.</p>
|
||||
<hr>
|
||||
|
||||
<h3><a name="SEC002">GNU GENERAL PUBLIC LICENSE TERMS AND
|
||||
CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</a></h3>
|
||||
|
||||
<p> 0. This License applies to any program or other work which
|
||||
<p>0. This License applies to any program or other work which
|
||||
contains a notice placed by the copyright holder saying it may
|
||||
be distributed under the terms of this General Public License.
|
||||
The "Program", below, refers to any such program or work, and a
|
||||
@ -92,15 +93,15 @@
|
||||
(Hereinafter, translation is included without limitation in the
|
||||
term "modification".) Each licensee is addressed as "you".</p>
|
||||
|
||||
<p> Activities other than copying, distribution and
|
||||
modification are not covered by this License; they are outside
|
||||
its scope. The act of running the Program is not restricted,
|
||||
and the output from the Program is covered only if its contents
|
||||
<p>Activities other than copying, distribution and modification
|
||||
are not covered by this License; they are outside its scope.
|
||||
The act of running the Program is not restricted, and the
|
||||
output from the Program is covered only if its contents
|
||||
constitute a work based on the Program (independent of having
|
||||
been made by running the Program). Whether that is true depends
|
||||
on what the Program does.</p>
|
||||
|
||||
<p> 1. You may copy and distribute verbatim copies of the
|
||||
<p>1. You may copy and distribute verbatim copies of the
|
||||
Program's source code as you receive it, in any medium,
|
||||
provided that you conspicuously and appropriately publish on
|
||||
each copy an appropriate copyright notice and disclaimer of
|
||||
@ -109,11 +110,11 @@
|
||||
recipients of the Program a copy of this License along with the
|
||||
Program.</p>
|
||||
|
||||
<p> You may charge a fee for the physical act of transferring a
|
||||
<p>You may charge a fee for the physical act of transferring a
|
||||
copy, and you may at your option offer warranty protection in
|
||||
exchange for a fee.</p>
|
||||
|
||||
<p> 2. You may modify your copy or copies of the Program or any
|
||||
<p>2. You may modify your copy or copies of the Program or any
|
||||
portion of it, thus forming a work based on the Program, and
|
||||
copy and distribute such modifications or work under the terms
|
||||
of Section 1 above, provided that you also meet all of these
|
||||
@ -124,13 +125,13 @@
|
||||
notices stating that you changed the files and the date of
|
||||
any change.
|
||||
|
||||
<p> b) You must cause any work that you distribute or
|
||||
publish, that in whole or in part contains or is derived from
|
||||
the Program or any part thereof, to be licensed as a whole at
|
||||
no charge to all third parties under the terms of this
|
||||
<p>b) You must cause any work that you distribute or publish,
|
||||
that in whole or in part contains or is derived from the
|
||||
Program or any part thereof, to be licensed as a whole at no
|
||||
charge to all third parties under the terms of this
|
||||
License.</p>
|
||||
|
||||
<p> c) If the modified program normally reads commands
|
||||
<p>c) If the modified program normally reads commands
|
||||
interactively when run, you must cause it, when started
|
||||
running for such interactive use in the most ordinary way, to
|
||||
print or display an announcement including an appropriate
|
||||
@ -155,17 +156,17 @@
|
||||
whole, and thus to each and every part regardless of who wrote
|
||||
it.
|
||||
|
||||
<p> Thus, it is not the intent of this section to claim rights
|
||||
<p>Thus, it is not the intent of this section to claim rights
|
||||
or contest your rights to work written entirely by you; rather,
|
||||
the intent is to exercise the right to control the distribution
|
||||
of derivative or collective works based on the Program.</p>
|
||||
|
||||
<p> In addition, mere aggregation of another work not based on
|
||||
<p>In addition, mere aggregation of another work not based on
|
||||
the Program with the Program (or with a work based on the
|
||||
Program) on a volume of a storage or distribution medium does
|
||||
not bring the other work under the scope of this License.</p>
|
||||
|
||||
<p> 3. You may copy and distribute the Program (or a work based
|
||||
<p>3. You may copy and distribute the Program (or a work based
|
||||
on it, under Section 2) in object code or executable form under
|
||||
the terms of Sections 1 and 2 above provided that you also do
|
||||
one of the following:</p>
|
||||
@ -176,7 +177,7 @@
|
||||
the terms of Sections 1 and 2 above on a medium customarily
|
||||
used for software interchange; or,
|
||||
|
||||
<p> b) Accompany it with a written offer, valid for at least
|
||||
<p>b) Accompany it with a written offer, valid for at least
|
||||
three years, to give any third party, for a charge no more
|
||||
than your cost of physically performing source distribution,
|
||||
a complete machine-readable copy of the corresponding source
|
||||
@ -184,7 +185,7 @@
|
||||
above on a medium customarily used for software interchange;
|
||||
or,</p>
|
||||
|
||||
<p> c) Accompany it with the information you received as to
|
||||
<p>c) Accompany it with the information you received as to
|
||||
the offer to distribute corresponding source code. (This
|
||||
alternative is allowed only for noncommercial distribution
|
||||
and only if you received the program in object code or
|
||||
@ -192,7 +193,7 @@
|
||||
b above.)</p>
|
||||
</blockquote>
|
||||
|
||||
<p> The source code for a work means the preferred form of the
|
||||
<p>The source code for a work means the preferred form of the
|
||||
work for making modifications to it. For an executable work,
|
||||
complete source code means all the source code for all modules
|
||||
it contains, plus any associated interface definition files,
|
||||
@ -204,7 +205,7 @@
|
||||
system on which the executable runs, unless that component
|
||||
itself accompanies the executable.</p>
|
||||
|
||||
<p> If distribution of executable or object code is made by
|
||||
<p>If distribution of executable or object code is made by
|
||||
offering access to copy from a designated place, then offering
|
||||
equivalent access to copy the source code from the same place
|
||||
counts as distribution of the source code, even though third
|
||||
@ -220,7 +221,7 @@
|
||||
licenses terminated so long as such parties remain in full
|
||||
compliance.
|
||||
|
||||
<p> 5. You are not required to accept this License, since you
|
||||
<p>5. You are not required to accept this License, since you
|
||||
have not signed it. However, nothing else grants you permission
|
||||
to modify or distribute the Program or its derivative works.
|
||||
These actions are prohibited by law if you do not accept this
|
||||
@ -230,16 +231,16 @@
|
||||
conditions for copying, distributing or modifying the Program
|
||||
or works based on it.</p>
|
||||
|
||||
<p> 6. Each time you redistribute the Program (or any work
|
||||
based on the Program), the recipient automatically receives a
|
||||
license from the original licensor to copy, distribute or
|
||||
modify the Program subject to these terms and conditions. You
|
||||
may not impose any further restrictions on the recipients'
|
||||
exercise of the rights granted herein. You are not responsible
|
||||
for enforcing compliance by third parties to this License.</p>
|
||||
<p>6. Each time you redistribute the Program (or any work based
|
||||
on the Program), the recipient automatically receives a license
|
||||
from the original licensor to copy, distribute or modify the
|
||||
Program subject to these terms and conditions. You may not
|
||||
impose any further restrictions on the recipients' exercise of
|
||||
the rights granted herein. You are not responsible for
|
||||
enforcing compliance by third parties to this License.</p>
|
||||
|
||||
<p> 7. If, as a consequence of a court judgment or allegation
|
||||
of patent infringement or for any other reason (not limited to
|
||||
<p>7. If, as a consequence of a court judgment or allegation of
|
||||
patent infringement or for any other reason (not limited to
|
||||
patent issues), conditions are imposed on you (whether by court
|
||||
order, agreement or otherwise) that contradict the conditions
|
||||
of this License, they do not excuse you from the conditions of
|
||||
@ -253,12 +254,12 @@
|
||||
License would be to refrain entirely from distribution of the
|
||||
Program.</p>
|
||||
|
||||
<p> If any portion of this section is held invalid or
|
||||
<p>If any portion of this section is held invalid or
|
||||
unenforceable under any particular circumstance, the balance of
|
||||
the section is intended to apply and the section as a whole is
|
||||
intended to apply in other circumstances.</p>
|
||||
|
||||
<p> It is not the purpose of this section to induce you to
|
||||
<p>It is not the purpose of this section to induce you to
|
||||
infringe any patents or other property right claims or to
|
||||
contest validity of any such claims; this section has the sole
|
||||
purpose of protecting the integrity of the free software
|
||||
@ -273,7 +274,7 @@
|
||||
This section is intended to make thoroughly clear what is
|
||||
believed to be a consequence of the rest of this License.
|
||||
|
||||
<p> 8. If the distribution and/or use of the Program is
|
||||
<p>8. If the distribution and/or use of the Program is
|
||||
restricted in certain countries either by patents or by
|
||||
copyrighted interfaces, the original copyright holder who
|
||||
places the Program under this License may add an explicit
|
||||
@ -282,13 +283,13 @@
|
||||
not thus excluded. In such case, this License incorporates the
|
||||
limitation as if written in the body of this License.</p>
|
||||
|
||||
<p> 9. The Free Software Foundation may publish revised and/or
|
||||
<p>9. The Free Software Foundation may publish revised and/or
|
||||
new versions of the General Public License from time to time.
|
||||
Such new versions will be similar in spirit to the present
|
||||
version, but may differ in detail to address new problems or
|
||||
concerns.</p>
|
||||
|
||||
<p> Each version is given a distinguishing version number. If
|
||||
<p>Each version is given a distinguishing version number. If
|
||||
the Program specifies a version number of this License which
|
||||
applies to it and "any later version", you have the option of
|
||||
following the terms and conditions either of that version or of
|
||||
@ -297,7 +298,7 @@
|
||||
you may choose any version ever published by the Free Software
|
||||
Foundation.</p>
|
||||
|
||||
<p> 10. If you wish to incorporate parts of the Program into
|
||||
<p>10. If you wish to incorporate parts of the Program into
|
||||
other free programs whose distribution conditions are
|
||||
different, write to the author to ask for permission. For
|
||||
software which is copyrighted by the Free Software Foundation,
|
||||
@ -309,8 +310,8 @@
|
||||
|
||||
<h3><a name="SEC003">NO WARRANTY</a></h3>
|
||||
|
||||
<p> 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE
|
||||
IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
|
||||
<p>11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS
|
||||
NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
|
||||
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE
|
||||
COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS
|
||||
IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
|
||||
@ -320,7 +321,7 @@
|
||||
WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE
|
||||
COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.</p>
|
||||
|
||||
<p> 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED
|
||||
<p>12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED
|
||||
TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO
|
||||
MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE,
|
||||
BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
|
||||
@ -334,7 +335,7 @@
|
||||
<h3>END OF TERMS AND CONDITIONS</h3>
|
||||
<hr>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
@ -2,7 +2,8 @@
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Chart of Accounts and Account Numbering</title>
|
||||
@ -11,14 +12,14 @@
|
||||
<body>
|
||||
<h1>Chart of Accounts</h1>
|
||||
|
||||
<p> Typically accounts are arranged as a tree, in hierarchical
|
||||
<p>Typically accounts are arranged as a tree, in hierarchical
|
||||
form.</p>
|
||||
|
||||
<p> The main branches represent entire categories or groups,
|
||||
<p>The main branches represent entire categories or groups,
|
||||
while the leaves of the tree denote individual bank accounts or
|
||||
expense categories.</p>
|
||||
|
||||
<p> When a summary report is requested, typically only the main
|
||||
<p>When a summary report is requested, typically only the main
|
||||
branches are shown in the report, rather than the individual
|
||||
accounts. For example, a chart of accounts might look like the
|
||||
following:</p>
|
||||
@ -38,47 +39,47 @@
|
||||
: :
|
||||
</pre>
|
||||
|
||||
<p> Note that accounts not only have names; they have <b>
|
||||
codes,</b> in order to provide <em> order.</em> When a report
|
||||
is generated, the <a name="SORTORDER"> sort order is determined
|
||||
by the numbering.</a></p>
|
||||
<p>Note that accounts not only have names; they have <b>
|
||||
codes,</b> in order to provide <em>order.</em> When a report is
|
||||
generated, the <a name="SORTORDER">sort order is determined by
|
||||
the numbering.</a></p>
|
||||
|
||||
<p> A sensible hierarchy generally will have the "leaf"
|
||||
accounts end in non-zero digits, whilst parent nodes have
|
||||
increasing numbers of zeros. For instance, "cash" accounts
|
||||
might logically be arranged thus:</p>
|
||||
<p>A sensible hierarchy generally will have the "leaf" accounts
|
||||
end in non-zero digits, whilst parent nodes have increasing
|
||||
numbers of zeros. For instance, "cash" accounts might logically
|
||||
be arranged thus:</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
Overall Assets: <tt> 100</tt>
|
||||
Overall Assets: <tt>100</tt>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
Overall Cash: <tt> 110</tt>
|
||||
Overall Cash: <tt>110</tt>
|
||||
|
||||
<ul>
|
||||
<li>Cash in Wallet: <tt> 111</tt></li>
|
||||
<li>Cash in Wallet: <tt>111</tt></li>
|
||||
|
||||
<li>Cash in Sock in Closet: <tt> 112</tt></li>
|
||||
<li>Cash in Sock in Closet: <tt>112</tt></li>
|
||||
|
||||
<li>Cash in Mattress: <tt> 113</tt></li>
|
||||
<li>Cash in Mattress: <tt>113</tt></li>
|
||||
|
||||
<li>Petty Cash Box: <tt> 114</tt></li>
|
||||
<li>Petty Cash Box: <tt>114</tt></li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Overall Banking Assets <tt> 120</tt>
|
||||
Overall Banking Assets <tt>120</tt>
|
||||
|
||||
<ul>
|
||||
<li>Checking Account <tt> 121</tt></li>
|
||||
<li>Checking Account <tt>121</tt></li>
|
||||
|
||||
<li>Savings Account <tt> 122</tt></li>
|
||||
<li>Savings Account <tt>122</tt></li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p> When you <a href="xacc-accwin.html">create a new
|
||||
<p>When you <a href="xacc-accwin.html">create a new
|
||||
account</a>, GnuCash offers a guess at what an appropriate
|
||||
account code might be; you are free to change this. GnuCash
|
||||
does not prevent duplicate numbering, although we would
|
||||
@ -89,7 +90,7 @@
|
||||
<h1>A Sample Chart of Accounts</h1>
|
||||
<a name="SAMPLECHART"></a>
|
||||
|
||||
<p> A "typical" chart of accounts is shown below. Each
|
||||
<p>A "typical" chart of accounts is shown below. Each
|
||||
account is of a given <a href="xacc-acctypes.html">account
|
||||
type</a>. This example is a combination of some typical
|
||||
business and personal accounts.</p>
|
||||
@ -369,7 +370,7 @@
|
||||
</ul>
|
||||
<hr>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
@ -2,14 +2,15 @@
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>GnuCash Help Main Window</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1> User Documentation Overview</h1>
|
||||
<h1>User Documentation Overview</h1>
|
||||
For help on a specific topic:
|
||||
|
||||
<ul>
|
||||
@ -27,7 +28,7 @@
|
||||
|
||||
<li><a href="xacc-date.html">Date Input</a></li>
|
||||
|
||||
<li><a href="xacc-apprdepr.html"> Depreciation and Capital
|
||||
<li><a href="xacc-apprdepr.html">Depreciation and Capital
|
||||
Gains</a></li>
|
||||
|
||||
<li><a href="xacc-currency.html">Foreign Currency
|
||||
@ -61,22 +62,26 @@
|
||||
|
||||
<li><a href="xacc-expense.html">Using Income/Expense
|
||||
Accounts</a></li>
|
||||
<li><a href="xacc-globalprefs.html">Customizing Gnucash's Appearance</a></li>
|
||||
<li><a href="xacc-accountedit.html">Changing Account Properties</a></li>
|
||||
|
||||
<li><a href="xacc-globalprefs.html">Customizing Gnucash's
|
||||
Appearance</a></li>
|
||||
|
||||
<li><a href="xacc-accountedit.html">Changing Account
|
||||
Properties</a></li>
|
||||
</ul>
|
||||
|
||||
<h1> Extended Help/System Documentation</h1>
|
||||
<h1>Extended Help/System Documentation</h1>
|
||||
|
||||
<p> The following documentation is about the <em>
|
||||
implementation</em> of GnuCash as opposed to being <em> user
|
||||
documentation</em> on how to <em> use</em> it.</p>
|
||||
<p>The following documentation is about the <em>
|
||||
implementation</em> of GnuCash as opposed to being <em>user
|
||||
documentation</em> on how to <em>use</em> it.</p>
|
||||
|
||||
<p> Some of it represents preliminary documentation for
|
||||
<p>Some of it represents preliminary documentation for
|
||||
subsystems that are not yet sufficiently functional for use by
|
||||
end users.</p>
|
||||
|
||||
<ul>
|
||||
<li><a href="projects.html"> GnuCash Project Goals</a></li>
|
||||
<li><a href="projects.html">GnuCash Project Goals</a></li>
|
||||
|
||||
<li><a href="xacc-print.html">Printing and Web
|
||||
Serving</a></li>
|
||||
@ -84,7 +89,7 @@
|
||||
<li>
|
||||
<a href="xacc-reports.html">Reports</a>
|
||||
|
||||
<p> The reporting subsystem is presently undergoing active
|
||||
<p>The reporting subsystem is presently undergoing active
|
||||
development; documentation should eventually include:</p>
|
||||
|
||||
<ul>
|
||||
|
@ -2,7 +2,8 @@
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Main Window</title>
|
||||
@ -11,20 +12,20 @@
|
||||
<body>
|
||||
<h1>Main GnuCash Window</h1>
|
||||
|
||||
<p> This is the main account window. You control your set of
|
||||
<p>This is the main account window. You control your set of
|
||||
accounts from here.</p>
|
||||
|
||||
<p> Below is a picture of the main window, with only the main
|
||||
accounts shown. Note how <b>Business Expenses</b> has been selected by
|
||||
highlighting. The box with a cross in it,
|
||||
immediately to its left, shows that it has one
|
||||
or more detail accounts that are not shown at present.
|
||||
To show them, click on this box.</p>
|
||||
<p>Below is a picture of the main window, with only the main
|
||||
accounts shown. Note how <b>Business Expenses</b> has been
|
||||
selected by highlighting. The box with a cross in it,
|
||||
immediately to its left, shows that it has one or more detail
|
||||
accounts that are not shown at present. To show them, click on
|
||||
this box.</p>
|
||||
|
||||
<p> <img src="contract.gif"><br>
|
||||
<p><img src="contract.gif"><br>
|
||||
</p>
|
||||
|
||||
<p> Here is the main window, with the detail accounts
|
||||
<p>Here is the main window, with the detail accounts
|
||||
showing.</p>
|
||||
|
||||
<p><br>
|
||||
@ -32,7 +33,7 @@
|
||||
</p>
|
||||
<hr>
|
||||
|
||||
<p> The <tt>Open Subaccounts</tt> menu item is interesting only
|
||||
<p>The <tt>Open Subaccounts</tt> menu item is interesting only
|
||||
if you choose an account with sub-accounts (detail accounts).
|
||||
Accounts with sub-accounts will always have a box on thier
|
||||
left. By choosing the <tt>Open Subaccounts</tt> menu item, a
|
||||
@ -44,7 +45,7 @@
|
||||
smaller space. Because of its increased complexity, it use is
|
||||
recommended only for accounting experts.</p>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
@ -1,20 +1,25 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Profit And Loss Statement</title>
|
||||
</head>
|
||||
<body>
|
||||
<h1>Profit and Loss Statement</h1>
|
||||
|
||||
<p>This report summarizes your sources of income and expenditure.</p>
|
||||
|
||||
<p>There are currently no options for this report, but the option
|
||||
to specify an accounting period will be added soon.</p>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
Page.</a></p>
|
||||
<body>
|
||||
<h1>Profit and Loss Statement</h1>
|
||||
|
||||
<p>This report summarizes your sources of income and
|
||||
expenditure.</p>
|
||||
|
||||
<p>There are currently no options for this report, but the
|
||||
option to specify an accounting period will be added soon.</p>
|
||||
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
|
@ -2,7 +2,8 @@
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Printing Checks</title>
|
||||
@ -11,87 +12,91 @@
|
||||
<body>
|
||||
<h1>Printing Checks</h1>
|
||||
|
||||
<p> You may print a GnuCash transaction as a check by selecting
|
||||
<p>You may print a GnuCash transaction as a check by selecting
|
||||
"Print Check" from the Transaction menu in a register display
|
||||
window.
|
||||
window.</p>
|
||||
|
||||
<p> In the Print Check dialog, select the style of check form that
|
||||
you wish to use, the position of the check on the page, and the
|
||||
format for printing the date on the check. Clicking <tt>OK</tt>
|
||||
will take you to the <a href="xacc-print.html">GnuCash Printing
|
||||
</a> dialog, which will allow you to preview the check, select a
|
||||
printer and paper size, and start the print job.
|
||||
<p>In the Print Check dialog, select the style of check form
|
||||
that you wish to use, the position of the check on the page,
|
||||
and the format for printing the date on the check. Clicking
|
||||
<tt>OK</tt> will take you to the <a href="xacc-print.html">
|
||||
GnuCash Printing</a> dialog, which will allow you to preview
|
||||
the check, select a printer and paper size, and start the print
|
||||
job.</p>
|
||||
|
||||
<h2>Check format</h2>
|
||||
|
||||
<p> In order to print a check, it is necessary to know where the
|
||||
pre-printed lines and boxes are on the check form. There are two
|
||||
widely-used standard check formats: Quicken/QuickBooks (tm)
|
||||
compatible, and Microsoft Money (tm) compatible.
|
||||
<p>In order to print a check, it is necessary to know where the
|
||||
pre-printed lines and boxes are on the check form. There are
|
||||
two widely-used standard check formats: Quicken/QuickBooks (tm)
|
||||
compatible, and Microsoft Money (tm) compatible.</p>
|
||||
|
||||
<p> By default, the check format is <tt>Quicken/QuickBooks</tt>,
|
||||
which prints to any Quicken-compatible check forms.
|
||||
<p>By default, the check format is <tt>Quicken/QuickBooks</tt>,
|
||||
which prints to any Quicken-compatible check forms.</p>
|
||||
|
||||
<h2>Custom Check Format</h2>
|
||||
|
||||
<p> If you wish to print to a type of check form that is not in
|
||||
the <tt>Check Format</tt> option menu, select <tt>Custom</tt> in
|
||||
the format menu and enter the positions of the various check
|
||||
fields in the entry boxes below.
|
||||
<p>If you wish to print to a type of check form that is not in
|
||||
the <tt>Check Format</tt> option menu, select <tt>Custom</tt>
|
||||
in the format menu and enter the positions of the various check
|
||||
fields in the entry boxes below.</p>
|
||||
|
||||
<p> Positions in the Custom Check Format entry area are specified
|
||||
with x = 0 at the left edge of the check with x increasing to the
|
||||
right, and y = 0 at the bottom edge of the check with y increasing
|
||||
as you travel up. Numbers may be entered as integer or floating
|
||||
point values. The length units specified in the <tt>Units</tt>
|
||||
option menu are used to interpret all values entered in the custom
|
||||
check format area.
|
||||
<p>Positions in the Custom Check Format entry area are
|
||||
specified with x = 0 at the left edge of the check with x
|
||||
increasing to the right, and y = 0 at the bottom edge of the
|
||||
check with y increasing as you travel up. Numbers may be
|
||||
entered as integer or floating point values. The length units
|
||||
specified in the <tt>Units</tt> option menu are used to
|
||||
interpret all values entered in the custom check format
|
||||
area.</p>
|
||||
|
||||
<p> If you arrive at a working set of Custom Check Format
|
||||
<p>If you arrive at a working set of Custom Check Format
|
||||
parameters for a commercially-available printable check form,
|
||||
please submit them to <tt>gnucash-devel@gnucash.org</tt> so we can
|
||||
include them as standard in a future release.
|
||||
please submit them to <tt>gnucash-devel@gnucash.org</tt> so we
|
||||
can include them as standard in a future release.</p>
|
||||
|
||||
<h2>Check position</h2>
|
||||
|
||||
<p> Printable check forms are available in several styles. In
|
||||
general, each printable sheet is divided into three sections, and
|
||||
each section can be either a check or a stub. The Check Position
|
||||
option menu allows you to select which section of the page
|
||||
contains the check you wish to print to. <tt>Top</tt>,
|
||||
<tt>Middle</tt>, and <tt>Bottom</tt> should be defined correctly
|
||||
for check forms using the paper size that you select in the
|
||||
printing dialog.
|
||||
<p>Printable check forms are available in several styles. In
|
||||
general, each printable sheet is divided into three sections,
|
||||
and each section can be either a check or a stub. The Check
|
||||
Position option menu allows you to select which section of the
|
||||
page contains the check you wish to print to. <tt>Top</tt>,
|
||||
<tt>Middle</tt>, and <tt>Bottom</tt> should be defined
|
||||
correctly for check forms using the paper size that you select
|
||||
in the printing dialog.</p>
|
||||
|
||||
<h2>Custom check position</h2>
|
||||
|
||||
<p> If the preset check positions do not work correctly for your
|
||||
<p>If the preset check positions do not work correctly for your
|
||||
check forms, you may choose <tt>Custom</tt> from the Check
|
||||
Position option menu and enter a position for the check in the
|
||||
<tt>Check Position</tt> entry. Enter the distance along the left
|
||||
edge of the paper from the lower left-hand corner of the page to
|
||||
the lower left-hand corner of the check. The units of this
|
||||
measurement are those selected in the "Units" option menu.
|
||||
<tt>Check Position</tt> entry. Enter the distance along the
|
||||
left edge of the paper from the lower left-hand corner of the
|
||||
page to the lower left-hand corner of the check. The units of
|
||||
this measurement are those selected in the "Units" option
|
||||
menu.</p>
|
||||
|
||||
<h2>Date format</h2>
|
||||
|
||||
<p> Select your preferred date format from the picker. The picker
|
||||
shows a sample date of "December 31, 2000" for all formats, but
|
||||
your date will be substituted when printing.
|
||||
|
||||
<p> The "MM/DD/YY" and "DD/MM/YY" formats are available, but they
|
||||
are strongly discouraged since they cannot always be
|
||||
distinguished from each other. Please use a format with a full
|
||||
or abbreviated month name instead of a number.
|
||||
|
||||
<p>Select your preferred date format from the picker. The
|
||||
picker shows examples using the date of <tt>December 31,
|
||||
2000</tt> for all formats, but your date will be substituted
|
||||
when printing.</p>
|
||||
|
||||
<p>The <tt>MM/DD/YY</tt> and <tt>DD/MM/YY</tt> formats are
|
||||
available, but they are strongly discouraged since they cannot
|
||||
always be distinguished from each other. Please use a format
|
||||
with a full or abbreviated month name instead of a number.</p>
|
||||
|
||||
<h2>Custom date format</h2>
|
||||
|
||||
<p> If you wish to use another date format besides those available
|
||||
in the picker, select <tt>Custom</tt> and enter a
|
||||
date-formatting string in the <tt>Date Format</tt> entry in the
|
||||
custom settings area. If custom date format is selected, this
|
||||
string is passed to <tt>strftime(3)</tt> as a format specifier.
|
||||
|
||||
<p>If you wish to use another date format besides those
|
||||
available in the picker, select <tt>Custom</tt> and enter a
|
||||
date-formatting string in the <tt>Date Format</tt> entry in the
|
||||
custom settings area. If custom date format is selected, this
|
||||
string is passed to <tt>strftime(3)</tt> as a format
|
||||
specifier.</p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
|
@ -2,7 +2,8 @@
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Printing and Web Serving</title>
|
||||
@ -11,33 +12,33 @@
|
||||
<body>
|
||||
<h1>Printing</h1>
|
||||
|
||||
<p> At present, the only type of printing directly supported by
|
||||
GnuCash is <a href="xacc-print-check.html">check printing</a>.
|
||||
Other types of printing are expected to be supported soon.
|
||||
<p>At present, the only type of printing directly supported by
|
||||
GnuCash is <a href="xacc-print-check.html">check printing</a>.
|
||||
Other types of printing are expected to be supported soon.</p>
|
||||
|
||||
<p> You may create a printout of the register
|
||||
window contents by opening a register window and selecting <tt>
|
||||
Print... To File</tt> from the <tt>File</tt> menu.
|
||||
<a href="xacc-reports.html">Reports</a> can also be
|
||||
<a href="xacc-reports.html">exported as HTML</a>.
|
||||
<p>You may create a printout of the register window contents by
|
||||
opening a register window and selecting <tt>Print... To
|
||||
File</tt> from the <tt>File</tt> menu. <a href=
|
||||
"xacc-reports.html">Reports</a> can also be <a href=
|
||||
"xacc-reports.html">exported as HTML</a>.</p>
|
||||
|
||||
<h1> GnuCash as Web Server</h1>
|
||||
<h1>GnuCash as Web Server</h1>
|
||||
|
||||
<p> Following the latest fashionable trends of <b> Internet
|
||||
<p>Following the latest fashionable trends of <b>Internet
|
||||
Hype,</b> GnuCash can also act as a cheesy web server!</p>
|
||||
|
||||
<ul>
|
||||
<li>From an open register window, select <tt>Print ... To
|
||||
WWW</tt> from the <tt> File</tt> menu.</li>
|
||||
WWW</tt> from the <tt>File</tt> menu.</li>
|
||||
|
||||
<li>Then aim your browser at <tt> http://localhost:1080/</tt>
|
||||
or <tt> http://yourmachinename.com:1080/</tt>and you will see
|
||||
<li>Then aim your browser at <tt>http://localhost:1080/</tt>
|
||||
or <tt>http://yourmachinename.com:1080/</tt>and you will see
|
||||
your register window.<br>
|
||||
<br>
|
||||
</li>
|
||||
|
||||
<li>But, remember, we said <em> cheesy;</em> in order to view
|
||||
the page a second time, you have to <em> pick the menu item
|
||||
<li>But, remember, we said <em>cheesy;</em> in order to view
|
||||
the page a second time, you have to <em>pick the menu item
|
||||
again</em> to "reload" things and allow prepare it for
|
||||
another data dump.<br>
|
||||
<br>
|
||||
@ -45,7 +46,7 @@
|
||||
</ul>
|
||||
<hr>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
@ -45,40 +45,62 @@ of keeping up with what people want the program to do.
|
||||
keep a Windows partition on their machine just so they can run Quicken
|
||||
and the latest shoot-em-up games. So of course we want to give you a
|
||||
way to suck all your Quicken data into GnuCash and remove one more
|
||||
barrier to putting a nice ext2 filesystem on that Windows partition.
|
||||
barrier to putting a nice <tt> ext2 </tt> filesystem on that Windows
|
||||
partition.
|
||||
|
||||
<p>The problem is that GnuCash is a real double-entry accounting
|
||||
system and Quicken has a pretty simplistic view about what an account
|
||||
is, what a transaction is, and what to save in data files. In short,
|
||||
QIF files just don't contain enough information to completely and
|
||||
accurately reconstruct your Quicken account hierarchy in the GnuCash
|
||||
double entry system without some guessing by the import code and some
|
||||
hand-holding by you. QIF files omit small things that can be easily
|
||||
guessed (for instance, are numbers in decimal-radix [1,000.00 == 1000]
|
||||
form or European comma-radix form [1.000,00 == 1000]? Are dates m/d/y
|
||||
or y/m/d?) and big things that can't be easily guessed, like, for
|
||||
example, what currency the file is denominated in, or what account the
|
||||
file describes.
|
||||
is, what a transaction is, and, most critically, is severely flawed in its datamodel, that is, <em> what it saves in
|
||||
data files.</em>
|
||||
|
||||
<p>For the most part, GnuCash's QIF importer does a good job of
|
||||
figuring this stuff out, but you do have to keep an eye on it. The
|
||||
system is designed so that you can correct problems BEFORE you make
|
||||
changes to your GnuCash accounts; nothing is done to your GnuCash
|
||||
accounts until you click the final "OK" button.
|
||||
<P> Briefly, QIF files just don't contain enough information to
|
||||
completely and accurately reconstruct your Quicken account hierarchy
|
||||
in the GnuCash double entry system without some educated guessing by
|
||||
the import code as well as some guidance, provided by you.
|
||||
<ul>
|
||||
|
||||
<li> QIF files omit small things that may be fairly accurately inferred by
|
||||
examining the data.
|
||||
|
||||
<P> For instance, are numbers in decimal-radix [1,000.00 ==
|
||||
1000] form or European comma-radix form [1.000,00 == 1000]?
|
||||
<P> Or are
|
||||
dates <tt> m/d/y </tt> or <tt> y/m/d</tt>?
|
||||
|
||||
<Ll> More problematic are major things where there is little way of
|
||||
guessing.
|
||||
|
||||
<P> For instance, determining the currency the file is denominated in.
|
||||
|
||||
<P> Or what <em> account </em> the file describes.
|
||||
|
||||
<p> GnuCash's QIF importer does a remarkably good job of guessing what
|
||||
it can, but you <em> do </em> have to keep an eye on it. Fortunately,
|
||||
the system is designed so that you can correct problems <em> before
|
||||
</em> you changes are dropped into your GnuCash accounts. Nothing is
|
||||
done to your GnuCash accounts until you click the final "OK" button.
|
||||
|
||||
<p>In the next section, I'll give an overview of the QIF file and
|
||||
its "features". This may seem unnecessarily technical, but if you
|
||||
will at least glance through it you will be much better able to
|
||||
understand what's going on if you are having to jump through hoops to
|
||||
make things work right, and how you might be able to jump right in and
|
||||
edit the QIF file to fix really tough problems.
|
||||
its "features". This may seem unnecessarily technical, but if you at
|
||||
least glance through it you will be much better able to understand
|
||||
what's going on if you are having to jump through hoops to make make a
|
||||
problematic file work right, and how you might be able to jump right
|
||||
in and edit the QIF file to fix really tough problems.
|
||||
|
||||
<p>There are two major "paths" for using the GnuCash QIF importer.
|
||||
One is the "I am a Quicken user just migrating to GnuCash" path; the
|
||||
other is the "I am downloading some updates from my bank as a QIF
|
||||
file" path. This document mainly focuses on the former case, since
|
||||
new users are likely to need the most help and you can't get started
|
||||
using GnuCash until you can get your old records in.
|
||||
<ul>
|
||||
|
||||
<li> One is the "I am a Quicken user just migrating to GnuCash" path.
|
||||
|
||||
<li> The other is the "I am downloading some updates from my bank as a
|
||||
QIF file" path.
|
||||
|
||||
</uL>
|
||||
|
||||
<P> This document mainly focuses on the former case, since new users
|
||||
are likely to need the most help and you really can't get started
|
||||
using GnuCash until you can get your old records in. Fortunately,
|
||||
once you learn to do the former, the latter should be a piece of cake.
|
||||
|
||||
<p><a href="#toc">Table of Contents</a>
|
||||
|
||||
@ -87,18 +109,19 @@ using GnuCash until you can get your old records in.
|
||||
<p>QIF files are plain text files formatted as "tag-value" pairs.
|
||||
At the beginning of each line there is a single character "tag"
|
||||
followed immediately by the "value", which extends to the end of the
|
||||
line. Don't be afraid to pop up a QIF file in "less" or the text
|
||||
editor of your choice if you are having problems getting some Quicken
|
||||
data imported correctly; chances are a simple search-and-replace will
|
||||
fix just about any problem you might have with a QIF file. And a
|
||||
regexp search-and-replace will get the rest.
|
||||
line.
|
||||
<P> Don't be afraid to pop up a QIF file using <tt> less </tt>
|
||||
or the text editor of your choice if you are having problems getting
|
||||
some Quicken data imported correctly; chances are a simple
|
||||
search-and-replace can fix just about any problem you might have with
|
||||
a QIF file. And a regexp search-and-replace will get the rest.
|
||||
|
||||
<p>Collections of tag-value pairs form records of various types.
|
||||
There are records to store the names and descriptions of your accounts
|
||||
and of expense and income categories that you have defined in Quicken.
|
||||
There are records to define Quicken "classes" (sort of like
|
||||
sub-accounts, sort of like categories, but not exactly like either).
|
||||
And there are records to describe transactions.
|
||||
And there are records to describe transactions.
|
||||
|
||||
<p>Here's a typical Quicken transaction record:
|
||||
<pre>
|
||||
@ -170,11 +193,12 @@ of all the $ fields in a transaction record should equal the T field.
|
||||
|
||||
<p>Note that nowhere in the transaction record, nor anywhere
|
||||
else in the file, does Quicken store the name of the account that the
|
||||
file describes. Don't ask me, I don't know why either. Microsoft
|
||||
Money (which also can save QIF files) started doing a "trick" to get
|
||||
the information in the file. If the very first Bank transaction in
|
||||
the file has a payee of "Opening Balance", the L line contains the
|
||||
name of the account that the file describes:
|
||||
file describes. Don't ask me why not, I don't know either. Microsoft
|
||||
Money (which also can save QIF files) uses a "trick" to get the
|
||||
information in the file. If the very first Bank transaction in the
|
||||
file has a payee of "Opening Balance", the L line contains the name of
|
||||
the account that the file describes:
|
||||
|
||||
<pre>
|
||||
!Type:Bank
|
||||
D12/03/95
|
||||
@ -184,36 +208,38 @@ name of the account that the file describes:
|
||||
L[New Bank]
|
||||
^
|
||||
</pre>
|
||||
<p>Opening Balance records are handled specially, since they don't
|
||||
mean what they appear to mean (if you interpret the record literally,
|
||||
as a transfer of $4706.57 from [New Bank] to [New Bank], your new
|
||||
balance is a whopping $0.00). In the
|
||||
<a href="#dialog-accounts">Accounts Tab</a> section there's a discussion
|
||||
|
||||
<p>Opening Balance records are handled specially, since they don't
|
||||
mean what the data appear to indicate (if you interpret the record
|
||||
literally, as a transfer of $4706.57 from [New Bank] to [New Bank],
|
||||
your new balance is a whopping $0.00). In the <a
|
||||
href="#dialog-accounts">Accounts Tab</a> section there's a discussion
|
||||
of what we do with them.
|
||||
|
||||
<h3>Multi-account Quicken exports</h3>
|
||||
|
||||
<p>Quicken and some other programs who use QIF as an export format
|
||||
<p>Quicken and some other programs who use QIF as an export format
|
||||
know how to put the history of multiple accounts into a single QIF
|
||||
file. They do this by prepending an "!Account" record before the
|
||||
set of transactions to/from that account.
|
||||
file. They do this by prepending an "!Account" record before the set
|
||||
of transactions to/from that account.
|
||||
|
||||
<p>The QIF Importer should be able to handle these files fine.
|
||||
You may notice that the "Default QIF Account" seems somewhat
|
||||
arbitrary; for multiple-account exports, the guessed account is the
|
||||
first one with an Opening Balance record. However, since Quicken
|
||||
explicitly lists the account for every transaction in multi-account
|
||||
exports, you aren't likely to get any transactions in the default
|
||||
account other than those that are supposed to be there.
|
||||
<p>The QIF Importer should be able to handle these files fine. You
|
||||
may notice that the "Default QIF Account" seems somewhat arbitrary;
|
||||
for multiple-account exports, the guessed account is the first one
|
||||
with an Opening Balance record. However, since Quicken explicitly
|
||||
lists the account for every transaction in multi-account exports, you
|
||||
aren't likely to get any transactions in the default account other
|
||||
than those that are supposed to be there.
|
||||
|
||||
<p><a href="#toc">Table of Contents</a>
|
||||
|
||||
<a name="how-to"><h2>How to use the QIF Import dialog</h2></a>
|
||||
|
||||
<p>The "Quick Start" guide: To load your files, click the "Select
|
||||
..." button in the Files tab to find the file, then click the "Load
|
||||
File" button at the bottom of the Files tab to actually load it.
|
||||
Repeat this until all your files are loaded (read the explanation
|
||||
<p>The "Quick Start" guide: To load your files, click the "Select ..."
|
||||
button in the Files tab to find the file, then click the "Load File"
|
||||
button at the bottom of the Files tab to actually load it.
|
||||
|
||||
<P>Repeat this until all your files are loaded (read the explanation
|
||||
below to see why you should load all your files at the same time).
|
||||
Check the Accounts and Categories dialogs and make corrections if
|
||||
necessary. Then click the big OK button.
|
||||
@ -230,7 +256,7 @@ will show up in multiple accounts. This means that if you aren't
|
||||
smart about catching duplicate transactions you will end up with wrong
|
||||
balances in GnuCash. Definitely a bad thing.
|
||||
|
||||
<p>In order to get the best possible replication of your Quicken
|
||||
<p>In order to get the best possible replication of your Quicken
|
||||
account tree, export everything you can from Quicken and then import
|
||||
it all in one session, either as a single QIF file representing all
|
||||
your accounts together or as a single file for each account. The
|
||||
@ -240,7 +266,7 @@ currency, Quicken account name, and so on are right for each one. The
|
||||
importer can do a really good job of catching cross-references (which
|
||||
and marking them.
|
||||
|
||||
<p>The importer is written mostly in Guile, and it can be a little
|
||||
<p>The importer is written mostly in Guile, and it can be a little
|
||||
slow on large QIF files. Load File takes 5-6 seconds for a QIF file
|
||||
with 1000 or so transactions on my machine.
|
||||
|
||||
@ -250,7 +276,7 @@ href="#dialog-categories">Categories tab</a>, and check that the
|
||||
importer is going to put your Quicken transactions in the right place.
|
||||
You can click to pop up a dialog and change the GnuCash destination
|
||||
account name/type for any QIF account. Don't be afraid to change
|
||||
these destination accounts; they are only guesses by the importer
|
||||
these destination accounts; they are merely guesses by the importer
|
||||
based on the name and type of the QIF account. Mappings of Quicken
|
||||
account to GnuCash account are written to a preferences file when you
|
||||
click "OK", so if you import other Quicken files describing these same
|
||||
@ -453,7 +479,7 @@ point if someone tells me how it's supposed to work.
|
||||
|
||||
<a name="brokerage-accounts"><h3>Brokerage accounts</h3></a>
|
||||
|
||||
<p>Brokerage accounts are really confusing to me. Basically, my
|
||||
<p>Brokerage accounts are really confusing to me. Basically, my
|
||||
thinking is that the brokerage account itself should probably be a
|
||||
Bank account. The only weirdness is in stuff like dividends paid from
|
||||
securities to the brokerage account. If you're using a Dividend
|
||||
|
@ -2,7 +2,8 @@
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>A Guide for Former Users of Quicken</title>
|
||||
@ -11,14 +12,14 @@
|
||||
<body>
|
||||
<h1>Quicken (TM) User's Guide</h1>
|
||||
|
||||
<p> Not all accounting systems use the same words to describe
|
||||
<p>Not all accounting systems use the same words to describe
|
||||
the same concepts. The following are some notes that may be
|
||||
helpful to users accustomed to Intuit's products.</p>
|
||||
|
||||
<h1>Quicken Categories</h1>
|
||||
<a name="QUICKENCATS"></a>
|
||||
|
||||
<p> What Quicken calls <tt>Categories</tt> are really just <a
|
||||
<p>What Quicken calls <tt>Categories</tt> are really just <a
|
||||
href="xacc-expense.html">Income/Expense accounts</a>. Thus, if
|
||||
you are used to specifying a category in Quicken, just create
|
||||
an income/expense account of the same name in GnuCash, and use
|
||||
@ -29,33 +30,33 @@
|
||||
Import Files (QIF). (Note: Only Quicken Version 3.0 QIF has
|
||||
been formally tested so far.)
|
||||
|
||||
<p> Note that the QIF format is representative of a somewhat
|
||||
<p>Note that the QIF format is representative of a somewhat
|
||||
peculiar data model that is not as expressive as one might
|
||||
wish; it requires dumping out a separate data file for each
|
||||
account, rather than permitting you to have one file that
|
||||
represents <em> all</em> of the accounts you might have had in
|
||||
represents <em>all</em> of the accounts you might have had in
|
||||
Quicken.</p>
|
||||
|
||||
<p> Furthermore, while there are plans to do so in the future,
|
||||
<p>Furthermore, while there are plans to do so in the future,
|
||||
there is not, at this point, a way of mapping the account or
|
||||
category names used in Quicken to a <em> different</em> set of
|
||||
category names used in Quicken to a <em>different</em> set of
|
||||
account names that you might be using in GnuCash.</p>
|
||||
|
||||
<p> As a result, please read this section carefully. You may be
|
||||
<p>As a result, please read this section carefully. You may be
|
||||
somewhat disappointed with the results of a QIF import; this
|
||||
will at least give you some more accurate expectations as to
|
||||
what will happen.</p>
|
||||
|
||||
<h2> Creating QIF Files</h2>
|
||||
<h2>Creating QIF Files</h2>
|
||||
|
||||
<p> To create a set of Quicken <tt>QIF</tt> files, perform the
|
||||
<p>To create a set of Quicken <tt>QIF</tt> files, perform the
|
||||
following procedure:</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
Start Quicken.
|
||||
|
||||
<p> It works on <a href="http://www.winehq.com/"> Wine,</a>
|
||||
<p>It works on <a href="http://www.winehq.com/">Wine,</a>
|
||||
Caldera's Wabi, and doubtless on VMWare, so this may not
|
||||
forcibly require that you run Windows.</p>
|
||||
</li>
|
||||
@ -63,10 +64,10 @@
|
||||
<li>
|
||||
Select the account that you wish to export.
|
||||
|
||||
<p> Quicken can only export one account to each data file,
|
||||
<p>Quicken can only export one account to each data file,
|
||||
which means that if you have many accounts, this may prove
|
||||
to be a somewhat tedious process. (On the other hand, it
|
||||
should be a whole lot <em> less</em> tedious than entering
|
||||
should be a whole lot <em>less</em> tedious than entering
|
||||
the data from scratch.)</p>
|
||||
</li>
|
||||
|
||||
@ -74,24 +75,24 @@
|
||||
Choose the menu <tt>File</tt> and select the <tt>
|
||||
Export...</tt> menu entry.
|
||||
|
||||
<p> This will provide a dialog that requests a filename,
|
||||
<p>This will provide a dialog that requests a filename,
|
||||
effective dates, as well as a series of checkboxes,
|
||||
including <tt>Transactions</tt>, <tt>Accounts List</tt>,
|
||||
<tt> Category List</tt>, and so forth.</p>
|
||||
<tt>Category List</tt>, and so forth.</p>
|
||||
|
||||
<p> For best results, you should make sure that those three
|
||||
<p>For best results, you should make sure that those three
|
||||
are checked.</p>
|
||||
|
||||
<p> If you do <em> not</em> check the <tt>Accounts
|
||||
List</tt> box, then the name of your account will likely be
|
||||
lost, and that will cause problems when you try to import
|
||||
the data into GnuCash later.</p>
|
||||
<p>If you do <em>not</em> check the <tt>Accounts List</tt>
|
||||
box, then the name of your account will likely be lost, and
|
||||
that will cause problems when you try to import the data
|
||||
into GnuCash later.</p>
|
||||
</li>
|
||||
</ul>
|
||||
Now you have a set of <tt>.QIF</tt> files, and should run
|
||||
GnuCash.
|
||||
|
||||
<h2> Loading QIF files into GnuCash</h2>
|
||||
<h2>Loading QIF files into GnuCash</h2>
|
||||
|
||||
<ul>
|
||||
<li>To import a Quicken QIF file, choose the menu <tt>
|
||||
@ -105,22 +106,22 @@
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<h2> Things To Note About QIF Import</h2>
|
||||
<h2>Things To Note About QIF Import</h2>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<b> Duplicate Entry Scanning</b>
|
||||
<b>Duplicate Entry Scanning</b>
|
||||
|
||||
<p> Note that during merge, a scan is made for duplicate
|
||||
<p>Note that during merge, a scan is made for duplicate
|
||||
transactions, and duplicates are removed. A duplicate
|
||||
transaction is one where the date, description (payee),
|
||||
memo, quantity, share price, and debited/credited accounts
|
||||
or categories match <em> exactly.</em> Thus, the merge <em>
|
||||
or categories match <em>exactly.</em> Thus, the merge <em>
|
||||
should</em> be safe unless you have multiple transactions
|
||||
on the same date, to the same account, for the same amount,
|
||||
with the same description and memo.</p>
|
||||
|
||||
<p> This unfortunately <em> can</em> occur, the typical
|
||||
<p>This unfortunately <em>can</em> occur, the typical
|
||||
scenario involving where you make multiple withdrawals of
|
||||
identical amounts from ATM machines on the same day.</p>
|
||||
</li>
|
||||
@ -140,32 +141,32 @@
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<b> QIF Mark II</b> An ongoing project is to build an
|
||||
<b>QIF Mark II</b> An ongoing project is to build an
|
||||
alternative import utility in Guile that will be more
|
||||
flexible, and which, by virtue of being stored as a set of
|
||||
Scheme scripts, may be modified without needing to
|
||||
recompile the whole application.
|
||||
|
||||
<p> At this point, it successfully parses <tt>QIF</tt>
|
||||
<p>At this point, it successfully parses <tt>QIF</tt>
|
||||
files; what remains is the (rather complex task) of
|
||||
determine appropriate correspondences between the Quicken
|
||||
<b> Categories</b> and the GnuCash equivalents. That is one
|
||||
<b>Categories</b> and the GnuCash equivalents. That is one
|
||||
of the most significant weaknesses with the present QIF
|
||||
import scheme.</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<b> More about QIF</b>
|
||||
<b>More about QIF</b>
|
||||
|
||||
<p> Further details about the QIF Interchange Format may be
|
||||
found <a href=
|
||||
<p>Further details about the QIF Interchange Format may be
|
||||
found <a href=
|
||||
"http://www.ntlug.org/~cbbrowne/financeformats.html#QIF">
|
||||
here.</a></p>
|
||||
</li>
|
||||
</ul>
|
||||
<hr>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
@ -2,7 +2,8 @@
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Reconciliation Window</title>
|
||||
@ -11,29 +12,29 @@
|
||||
<body>
|
||||
<h1>Reconciliation Window</h1>
|
||||
|
||||
<p> The Reconciliation window is used to reconcile cleared
|
||||
<p>The Reconciliation window is used to reconcile cleared
|
||||
transactions from a bank statement. Enter a dollar amount from
|
||||
your last bank statement in the box, and then click <tt>
|
||||
OK</tt> . The window will then show all unreconciled
|
||||
transactions since your last bank statement. The reconcile
|
||||
window looks like this:</p>
|
||||
your last bank statement in the box, and then click <tt>OK</tt>
|
||||
. The window will then show all unreconciled transactions since
|
||||
your last bank statement. The reconcile window looks like
|
||||
this:</p>
|
||||
|
||||
<p><br>
|
||||
<img src="recnwin.gif"><br>
|
||||
</p>
|
||||
|
||||
<p> The Reconciliation window is used to reconcile the user's
|
||||
<p>The Reconciliation window is used to reconcile the user's
|
||||
records at the end of the month. This involves validating the
|
||||
transactions in GnuCash against the transactions indicated on
|
||||
your bank statement.</p>
|
||||
|
||||
<p> For example, when you write a check for something, you
|
||||
<p>For example, when you write a check for something, you
|
||||
should enter the transaction into GnuCash.</p>
|
||||
|
||||
<p> At the end of the month, you receive your bank statement,
|
||||
perhaps including canceled checks. At <em> that</em> point,
|
||||
you should "reconcile" the account, that is, agree your
|
||||
personal records to the documentation provided by the bank.</p>
|
||||
<p>At the end of the month, you receive your bank statement,
|
||||
perhaps including canceled checks. At <em>that</em> point, you
|
||||
should "reconcile" the account, that is, agree your personal
|
||||
records to the documentation provided by the bank.</p>
|
||||
|
||||
<ul>
|
||||
<li>Open the reconcile window, and GnuCash will prompt you to
|
||||
@ -48,13 +49,13 @@
|
||||
<li>
|
||||
Now, examine each item on the bank statement.
|
||||
|
||||
<p> If a check has cleared, as indicated by your bank
|
||||
<p>If a check has cleared, as indicated by your bank
|
||||
statement, you should click the field between the
|
||||
description and payment fields, and it will then change
|
||||
from <tt>n</tt> to <tt>c</tt>, indicating the transaction
|
||||
has <b>c</b>cleared.</p>
|
||||
|
||||
<p> You then repeat this for each item that appears on the
|
||||
<p>You then repeat this for each item that appears on the
|
||||
bank statement, verifying that the amounts match with the
|
||||
amounts in GnuCash, and marking off transactions in GnuCash
|
||||
as they are reconciled.</p>
|
||||
@ -83,16 +84,16 @@
|
||||
unwise should pop up, but this doesn't seem to happen
|
||||
anymore.</p>
|
||||
|
||||
<p> Also, the "cleared" total at the bottom seems to display
|
||||
<p>Also, the "cleared" total at the bottom seems to display
|
||||
<tt>$0.00</tt> regardless of what transactions are cleared or
|
||||
reconciled.</p>
|
||||
|
||||
<p> The "cleared" total should display the total of only the
|
||||
<p>The "cleared" total should display the total of only the
|
||||
transactions that have been cleared (<tt>c</tt>) or reconciled
|
||||
(<tt>y</tt>).</p>
|
||||
<hr>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
@ -2,7 +2,8 @@
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Register Window</title>
|
||||
@ -10,95 +11,122 @@
|
||||
|
||||
<body>
|
||||
<h1>Register Window</h1>
|
||||
<img src="regwin-single.gif">
|
||||
<p> This is the "Register" or the "Ledger" window. Transactions are entered here.</p>
|
||||
<p>To enter a new transaction, just type into the last blank transaction.
|
||||
Use the mouse or the <a href="xacc-regwin_kbd.html">Register Keyboard Shortcuts</a>to move between fields, and hit the Enter key or click record to
|
||||
record the transaction:</p>
|
||||
<img src="regwin-single2.gif">
|
||||
<p> Notice how a the transaction has been recorded and a new, blank
|
||||
transaction has been created.</p>
|
||||
<p>You can edit existing transactions in a similar manner. GnuCash
|
||||
will prompt you to confirm any changes you make.</p>
|
||||
<img src="regwin-single.gif">
|
||||
|
||||
<p>This is the "Register" or the "Ledger" window. Transactions
|
||||
are entered here.</p>
|
||||
|
||||
<p>To enter a new transaction, just type into the last blank
|
||||
transaction. Use the mouse or the <a href=
|
||||
"xacc-regwin_kbd.html">Register Keyboard Shortcuts</a>to move
|
||||
between fields, and hit the Enter key or click record to record
|
||||
the transaction:</p>
|
||||
<img src="regwin-single2.gif">
|
||||
|
||||
<p>Notice how a the transaction has been recorded and a new,
|
||||
blank transaction has been created.</p>
|
||||
|
||||
<p>You can edit existing transactions in a similar manner.
|
||||
GnuCash will prompt you to confirm any changes you make.</p>
|
||||
|
||||
<h1>Manipulating transactions</h1>
|
||||
<p>You can manipulate transactions with the toolbar or the "Transaction"
|
||||
menu:
|
||||
<ul><li><b>Delete:</b> you can delete a transaction or an individual
|
||||
split.</li>
|
||||
<li><b>Cancel:</b> this reverts any changes you have made to the
|
||||
transaction you are currently entering/changing</li>
|
||||
|
||||
<p>You can manipulate transactions with the toolbar or the
|
||||
"Transaction" menu:</p>
|
||||
|
||||
<ul>
|
||||
<li><b>Delete:</b> you can delete a transaction or an
|
||||
individual split.</li>
|
||||
|
||||
<li><b>Cancel:</b> this reverts any changes you have made to
|
||||
the transaction you are currently entering/changing</li>
|
||||
|
||||
<li><b>New:</b> this moves the cursor to the last line of the
|
||||
register where new transactions are entered</li>
|
||||
<li><b>Jump:</b> When placed over an existing transaction, it takes
|
||||
you to the corresponding register entry in the other register entry
|
||||
that this
|
||||
transaction appears in</li>
|
||||
<li><b>Transfer:</b>This is an alternative way to enter a transaction.
|
||||
You can do a transfer between any two accounts without opening
|
||||
up other registers.</li>
|
||||
<li><b>Close:</b>Closes this register</li></ul>
|
||||
register where new transactions are entered</li>
|
||||
|
||||
<li><b>Jump:</b> When placed over an existing transaction, it
|
||||
takes you to the corresponding register entry in the other
|
||||
register entry that this transaction appears in</li>
|
||||
|
||||
<li><b>Transfer:</b>This is an alternative way to enter a
|
||||
transaction. You can do a transfer between any two accounts
|
||||
without opening up other registers.</li>
|
||||
|
||||
<li><b>Close:</b>Closes this register</li>
|
||||
</ul>
|
||||
|
||||
<h1>Viewing Transactions</h1>
|
||||
|
||||
|
||||
<p>The register can show transactions in a variety of different
|
||||
ways, controlled by entries on the "Register" menu.</p>
|
||||
ways, controlled by entries on the "Register" menu.</p>
|
||||
|
||||
<p>The register can display transactions in several different
|
||||
styles:</p>
|
||||
<ul><li><b>single-line mode:</b> transactions are displayed on a single line.</li>
|
||||
<li><b>double-line mode:</b> transactions are displayed over two lines,
|
||||
with more information about each transaction shown.</li>
|
||||
<li><b>multi-line mode:</b> transactions are displayed over multiple
|
||||
lines, allowing the display of multiple entries. This allows you
|
||||
to enter multi-split transactions (for instance, when you pay multiple bills with one check).</li>
|
||||
<li><b>auto-single and auto-double modes</b> are like single and
|
||||
double-line modes, except that the currently-edited transaction
|
||||
is displayed in multi-line form. This is a very convenient way
|
||||
of entering multi-account transactions.</li></ul>
|
||||
styles:</p>
|
||||
|
||||
<p>To change the display style, to go the "Register" menu and select
|
||||
"style".</p>
|
||||
<ul>
|
||||
<li><b>single-line mode:</b> transactions are displayed on a
|
||||
single line.</li>
|
||||
|
||||
<li><b>double-line mode:</b> transactions are displayed over
|
||||
two lines, with more information about each transaction
|
||||
shown.</li>
|
||||
|
||||
<li><b>multi-line mode:</b> transactions are displayed over
|
||||
multiple lines, allowing the display of multiple entries.
|
||||
This allows you to enter multi-split transactions (for
|
||||
instance, when you pay multiple bills with one check).</li>
|
||||
|
||||
<li><b>auto-single and auto-double modes</b> are like single
|
||||
and double-line modes, except that the currently-edited
|
||||
transaction is displayed in multi-line form. This is a very
|
||||
convenient way of entering multi-account transactions.</li>
|
||||
</ul>
|
||||
|
||||
<p>To change the display style, to go the "Register" menu and
|
||||
select "style".</p>
|
||||
|
||||
<p>Existing transactions are normally displayed in date order,
|
||||
but this can also be changed with "Sort Order". You can also
|
||||
select a date rate from which transactions will be displayed
|
||||
with "Date Range".</p>
|
||||
|
||||
<p>Existing transactions are normally displayed in date order, but
|
||||
this can also be changed with "Sort Order".
|
||||
You can also select a date rate from which transactions will be
|
||||
displayed with "Date Range".</p>
|
||||
<h1>Reconciliation</h1>
|
||||
<p>Transactions are typically checked against bank statements - a
|
||||
process known as "reconciliation". GnuCash keeps track of
|
||||
the reconciliation status of each transaction.</p>
|
||||
<p>The reconciliation status of a transaction is shown by the
|
||||
reconciliation (R) field. 'c' indicates that a transaction
|
||||
has been reconciled, 'n' indicates that it has not. You can
|
||||
change the reconciliation status by clicking on a the 'r' field
|
||||
of the transaction.</p>
|
||||
<p> At the bottom of the account window, there are two running
|
||||
|
||||
<p>Transactions are typically checked against bank statements -
|
||||
a process known as "reconciliation". GnuCash keeps track of the
|
||||
reconciliation status of each transaction.</p>
|
||||
|
||||
<p>The reconciliation status of a transaction is shown by the
|
||||
reconciliation (R) field. 'c' indicates that a transaction has
|
||||
been reconciled, 'n' indicates that it has not. You can change
|
||||
the reconciliation status by clicking on a the 'r' field of the
|
||||
transaction.</p>
|
||||
|
||||
<p>At the bottom of the account window, there are two running
|
||||
balances, the "cleared and reconciled" balance, and the "total"
|
||||
balance... the "cleared and reconciled" balance should
|
||||
correspond to how much money the bank thinks you have in your
|
||||
account, and the "total" balance includes outstanding
|
||||
transactions.</p>
|
||||
|
||||
<p> Reconciliation can be done in the <a href=
|
||||
<p>Reconciliation can be done in the <a href=
|
||||
"xacc-recnwin.html">Reconcile Window</a></p>
|
||||
|
||||
|
||||
|
||||
<h1>Stock Portfolios</h1>
|
||||
|
||||
<p> You can do stock transactions either from a single-stock
|
||||
<p>You can do stock transactions either from a single-stock
|
||||
window, or from a portfolio-view window, shown below.</p>
|
||||
|
||||
<p> <img src="foliowin.gif"><br>
|
||||
<p><img src="foliowin.gif"><br>
|
||||
<img src="foliowin-single.gif"></p>
|
||||
|
||||
<p> The portfolio ledger can seem a bit daunting at first
|
||||
<p>The portfolio ledger can seem a bit daunting at first
|
||||
sight.</p>
|
||||
|
||||
<p> If you have trouble understanding it, then you may wish to
|
||||
<p>If you have trouble understanding it, then you may wish to
|
||||
create an account for each stock you wish to track.</p>
|
||||
|
||||
<p> Some important points to remember about the portfolio
|
||||
<p>Some important points to remember about the portfolio
|
||||
window:</p>
|
||||
|
||||
<ul>
|
||||
@ -106,14 +134,14 @@
|
||||
It shows <em>all</em> stocks in your portfolio, not just
|
||||
one.
|
||||
|
||||
<p> The share amounts shown are for each particular
|
||||
<p>The share amounts shown are for each particular
|
||||
stock.</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Note that it uses a two line display.
|
||||
|
||||
<p> Debited accounts and debited amounts are on the upper
|
||||
<p>Debited accounts and debited amounts are on the upper
|
||||
line, and credited amounts and accounts are on the lower
|
||||
line.</p>
|
||||
</li>
|
||||
@ -141,7 +169,7 @@
|
||||
window may be provided.</li>
|
||||
</ul>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
@ -2,7 +2,8 @@
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Reports</title>
|
||||
@ -11,58 +12,87 @@
|
||||
<body>
|
||||
<h1>Reports</h1>
|
||||
|
||||
<p>A variety of financial reports can be selected on the "Extensions"
|
||||
menu":
|
||||
<ul><li><a href="xacc-balsheet.html">Balance Sheet:</a>shows Assets,
|
||||
Liabilities and Equity.</li>
|
||||
<li><a href="xacc-pnl.html">Profit And Loss State:</a>shows Income
|
||||
and expenses over a selectable period <em>well, it will when
|
||||
I get around to adding period support</em>
|
||||
<li><a href="xacc-trans_report.html">Transaction Report</a>shows
|
||||
transactions in an account, presented in a variety of ways.</li>
|
||||
<li><a href="xacc-bal_tracker.html">Balance Tracker</a> tracks
|
||||
the balance of one or more accounts over time, and supports
|
||||
graphical output (if you have gnuplot installed).</li></ul>
|
||||
<p>A variety of financial reports can be selected on the
|
||||
"Extensions" menu":</p>
|
||||
|
||||
<ul>
|
||||
<li><a href="xacc-balsheet.html">Balance Sheet:</a>shows
|
||||
Assets, Liabilities and Equity.</li>
|
||||
|
||||
<li><a href="xacc-pnl.html">Profit And Loss State:</a>shows
|
||||
Income and expenses over a selectable period <em>well, it
|
||||
will when I get around to adding period support</em></li>
|
||||
|
||||
<li><a href="xacc-trans_report.html">Transaction
|
||||
Report</a>shows transactions in an account, presented in a
|
||||
variety of ways.</li>
|
||||
|
||||
<li><a href="xacc-bal_tracker.html">Balance Tracker</a>
|
||||
tracks the balance of one or more accounts over time, and
|
||||
supports graphical output (if you have gnuplot
|
||||
installed).</li>
|
||||
</ul>
|
||||
|
||||
<h1>The Report Window</h1>
|
||||
Once you select a report, a report window will appear:
|
||||
<p><img src="reportwin.gif"></p>
|
||||
<p>The report is displayed in a resizable, scrollable window. To
|
||||
control the report, you can use the toolbar buttons at the
|
||||
top of the window:
|
||||
<ul><li><b>Back</b> and <b>Forward</b> allow you to view the previous
|
||||
contents of the window, just like a web browser</li>
|
||||
<li><b>Parameters</b> pops up a dialog box allowing you to change the
|
||||
information presented in the report:
|
||||
<p><img src="report-option.gif"></p>
|
||||
<p>See the help for the individual reports for details of options
|
||||
available.</p></li>
|
||||
<li><b>Export</b> allows you to export the contents of the report
|
||||
as a HTML file for later viewing or printing.</li>
|
||||
<li><b>Close</b> closes the report window.</li></ul>
|
||||
<h1>Constructing custom reports</h1>
|
||||
Once you select a report, a report window will appear:
|
||||
|
||||
It is possible to write your own reports to meet your own needs, if
|
||||
you can program a little.
|
||||
You will need to know Scheme (a LISP-like programming language),
|
||||
and it is an excellent idea to have a copy of the Gnucash source code
|
||||
available.
|
||||
<P>The reporting interface is presently undocumented, but you can
|
||||
get a good idea of how it works by examining the file
|
||||
src/scm/report/hello-world.scm in the GnuCash source distribution.
|
||||
<P>You will also need to access data from the "engine" to get
|
||||
information for your report. This is performed by a set of Scheme
|
||||
wrapper functions that are documented in the file src/g-wrap/gnc.html.
|
||||
You may wish to examine some of the other reports in src/scm/report
|
||||
for an indication of how they are used.
|
||||
<P>At present, reports are produced by internally creating HTML and
|
||||
rendering this with a HTML widget. (Future versions of GnuCash
|
||||
will hopefully support a more flexible system).
|
||||
<P>If you need more information, or have developed a new report that
|
||||
may be of use to others, please contact the GnuCash development
|
||||
mailing list at <a href="mailto:gnucash-devel@gnucash.org">gnucash-devel@gnucash.org</a>.
|
||||
<p><img src="reportwin.gif"></p>
|
||||
|
||||
<p>The report is displayed in a resizable, scrollable window.
|
||||
To control the report, you can use the toolbar buttons at the
|
||||
top of the window:</p>
|
||||
|
||||
<ul>
|
||||
<li><b>Back</b> and <b>Forward</b> allow you to view the
|
||||
previous contents of the window, just like a web browser</li>
|
||||
|
||||
<li>
|
||||
<b>Parameters</b> pops up a dialog box allowing you to
|
||||
change the information presented in the report:
|
||||
|
||||
<p><img src="report-option.gif"></p>
|
||||
|
||||
<p>See the help for the individual reports for details of
|
||||
options available.</p>
|
||||
</li>
|
||||
|
||||
<li><b>Export</b> allows you to export the contents of the
|
||||
report as a HTML file for later viewing or printing.</li>
|
||||
|
||||
<li><b>Close</b> closes the report window.</li>
|
||||
</ul>
|
||||
|
||||
<h1>Constructing custom reports</h1>
|
||||
It is possible to write your own reports to meet your own
|
||||
needs, if you can program a little. You will need to know
|
||||
Scheme (a LISP-like programming language), and it is an
|
||||
excellent idea to have a copy of the Gnucash source code
|
||||
available.
|
||||
|
||||
<p>The reporting interface is presently undocumented, but you
|
||||
can get a good idea of how it works by examining the file
|
||||
src/scm/report/hello-world.scm in the GnuCash source
|
||||
distribution.</p>
|
||||
|
||||
<p>You will also need to access data from the "engine" to get
|
||||
information for your report. This is performed by a set of
|
||||
Scheme wrapper functions that are documented in the file
|
||||
src/g-wrap/gnc.html. You may wish to examine some of the other
|
||||
reports in src/scm/report for an indication of how they are
|
||||
used.</p>
|
||||
|
||||
<p>At present, reports are produced by internally creating HTML
|
||||
and rendering this with a HTML widget. (Future versions of
|
||||
GnuCash will hopefully support a more flexible system).</p>
|
||||
|
||||
<p>If you need more information, or have developed a new report
|
||||
that may be of use to others, please contact the GnuCash
|
||||
development mailing list at <a href=
|
||||
"mailto:gnucash-devel@gnucash.org">
|
||||
gnucash-devel@gnucash.org</a>.</p>
|
||||
<hr>
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
@ -2,11 +2,12 @@
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
<meta http-equiv="Content-Type" content=
|
||||
"text/html; charset=iso-8859-1">
|
||||
|
||||
<title>Stock Ticker</title>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
</head>
|
||||
|
||||
@ -33,36 +34,39 @@
|
||||
|
||||
<li>Select a quote source from the pull-down menu. Currently
|
||||
supported quote sources include <b>Yahoo</b>, <b>Yahoo
|
||||
Europe</b>, <b>Fidelity Investments</b>, <b>T. Rowe Price</b>,
|
||||
the <b>Vanguard Group</b>, <b>the Australian Stock
|
||||
Europe</b>, <b>Fidelity Investments</b>, <b>T. Rowe
|
||||
Price</b>, the <b>Vanguard Group</b>, <b>the Australian Stock
|
||||
Exchange</b> (ASX) and <b>TIAA-CREF</b>. Note that Yahoo will
|
||||
provide price quotes for many mutual funds <i>including</i>
|
||||
Fidelity, T.Rowe Price and Vanguard, and that the quoted prices
|
||||
at Yahoo <i>should</i> be identical to those that may be found
|
||||
at the source sites (otherwise, somebody's reporting wrong
|
||||
information!). If you choose Yahoo Europe, you should append the
|
||||
market code for the security, such as PA for Paris, BE for
|
||||
Berlin, etc. Example: 12150.PA (a Peugeot security in the Paris
|
||||
market).
|
||||
Fidelity, T.Rowe Price and Vanguard, and that the quoted
|
||||
prices at Yahoo <i>should</i> be identical to those that may
|
||||
be found at the source sites (otherwise, somebody's reporting
|
||||
wrong information!). If you choose Yahoo Europe, you should
|
||||
append the market code for the security, such as PA for
|
||||
Paris, BE for Berlin, etc. Example: 12150.PA (a Peugeot
|
||||
security in the Paris market).</li>
|
||||
|
||||
<li>
|
||||
Ensure that the currency of the account matches the source
|
||||
of the stock you have selected. This means:
|
||||
|
||||
<li>Ensure that the currency of the account matches the source
|
||||
of the stock you have selected. This means:
|
||||
<ul>
|
||||
<li>Quotes from the <b>Australian Stock Exchange</b> (ASX)
|
||||
should be in Australian dollars (AUD).</li>
|
||||
|
||||
<li>Quotes from <b>Yahoo Europe</b> should be in Euros (ECU)</li>
|
||||
<li>Quotes from the <b>Australian Stock Exchange</b>
|
||||
(ASX) should be in Australian dollars (AUD).</li>
|
||||
|
||||
<li>Quotes from <b>Yahoo</b>, <b>Fidelity Investments</b>,
|
||||
<b>T. Rowe Price</b> and the <b>Vanguard Group</b>
|
||||
should be in US Dollars (USD).</li>
|
||||
<li>Quotes from <b>Yahoo Europe</b> should be in Euros
|
||||
(ECU)</li>
|
||||
|
||||
<li>Quotes from <b>Yahoo</b>, <b>Fidelity
|
||||
Investments</b>, <b>T. Rowe Price</b> and the <b>Vanguard
|
||||
Group</b> should be in US Dollars (USD).</li>
|
||||
</ul>
|
||||
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<table>
|
||||
<caption>
|
||||
Code list for European markets
|
||||
Code list for European markets
|
||||
</caption>
|
||||
|
||||
<tr>
|
||||
@ -196,58 +200,82 @@
|
||||
<caption>
|
||||
Pseudo-symbols that can be used for TIAA-CREF quotes.
|
||||
</caption>
|
||||
|
||||
<tr>
|
||||
<th>Name</th>
|
||||
|
||||
<th>Pseudo-symbol</th>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Stock</td>
|
||||
|
||||
<td>CREFstok</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Money Market</td>
|
||||
|
||||
<td>CREFmony</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Equity Index</td>
|
||||
|
||||
<td>CREFequi</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Inflation-Linked Bond</td>
|
||||
|
||||
<td>CREFinfb</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Bond Market</td>
|
||||
|
||||
<td>CREFbond</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>TIAA Real Estate</td>
|
||||
|
||||
<td>TIAAreal</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Social Choice</td>
|
||||
|
||||
<td>CREFsoci</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Teachers PA Stock Index</td>
|
||||
|
||||
<td>TIAAsndx</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Global Equities</td>
|
||||
|
||||
<td>CREFglob</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Teachers PA Select Stock</td>
|
||||
|
||||
<td>TIAAsele</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Growth</td>
|
||||
|
||||
<td>CREFgrow</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<p>A sample image is shown below:<br>
|
||||
<img src="ticker-a.gif" alt="Sample Diagram"></p>
|
||||
<img src="ticker-a.gif" alt="Sample Diagram"></p>
|
||||
|
||||
<p>To update the prices stored in a gnucash account file, run
|
||||
the command line command <tt>gnc-price</tt>, specifying the
|
||||
@ -279,10 +307,11 @@
|
||||
|
||||
<p>After running <tt>gnc-prices</tt> for a few days, your
|
||||
accounts will begin to resemble the following:<br>
|
||||
<img src="ticker-b.gif" alt="Later Ticker Listing"></p>
|
||||
<img src="ticker-b.gif" alt="Later Ticker Listing"></p>
|
||||
<hr>
|
||||
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
|
@ -1,33 +1,46 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
<head>
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Transaction Report</title>
|
||||
</head>
|
||||
|
||||
|
||||
<body>
|
||||
<h1>Transaction Report</h1>
|
||||
|
||||
<p>Transaction reports list details for transactions in a specified
|
||||
account over a specified period, in a convenient format for
|
||||
viewing and exporting.</p>
|
||||
|
||||
<p>Transaction reports list details for transactions in a
|
||||
specified account over a specified period, in a convenient
|
||||
format for viewing and exporting.</p>
|
||||
|
||||
<p>Options specifiable for this report include:</p>
|
||||
<ul><li><b>Account:</b> the account to do the report on.</li>
|
||||
<li><b>Date To and Date From:</b> the date range for the report
|
||||
to cover.</li>
|
||||
|
||||
<ul>
|
||||
<li><b>Account:</b> the account to do the report on.</li>
|
||||
|
||||
<li><b>Date To and Date From:</b> the date range for the
|
||||
report to cover.</li>
|
||||
|
||||
<li><b>Primary Sort Key:</b> the field to sort on first.</li>
|
||||
<li><b>Primary Sort Order:</b> the order in which to sort. "Ascending"
|
||||
specifies smallest/largest, alphabetical ordering, earliest->latest,
|
||||
or smallest amounts first. Descending produces the opposite effects.</li>
|
||||
<li><b>Secondary Sort Key:</b> the field to sort on if the primary
|
||||
sort keys are equal</li>
|
||||
<li><b>Secondary Sort Order:</b> the ordering on which to sort the
|
||||
secondary key.</b>
|
||||
|
||||
<li><b>Primary Sort Order:</b> the order in which to sort.
|
||||
"Ascending" specifies smallest/largest, alphabetical
|
||||
ordering, earliest->latest, or smallest amounts first.
|
||||
Descending produces the opposite effects.</li>
|
||||
|
||||
<li><b>Secondary Sort Key:</b> the field to sort on if the
|
||||
primary sort keys are equal</li>
|
||||
|
||||
<li><b>Secondary Sort Order:</b> the ordering on which to
|
||||
sort the secondary key.</li>
|
||||
</ul>
|
||||
<hr>
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
|
@ -2,7 +2,8 @@
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
<meta name="generator" content="HTML Tidy, see www.w3.org">
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>GnuCash Y2K Readiness</title>
|
||||
@ -11,42 +12,42 @@
|
||||
<body>
|
||||
<h1>GnuCash Y2K Readiness</h1>
|
||||
|
||||
<p> GnuCash versions 1.1.25 and later store all dates as
|
||||
seconds and nanoseconds, where the seconds are stored in a
|
||||
64-bit signed integer. This should suffice to store dates into
|
||||
both the distant past as well as the distant future, so long as
|
||||
they fall not <em> too</em> many orders of magnitude outside
|
||||
<p>GnuCash versions 1.1.25 and later store all dates as seconds
|
||||
and nanoseconds, where the seconds are stored in a 64-bit
|
||||
signed integer. This should suffice to store dates into both
|
||||
the distant past as well as the distant future, so long as they
|
||||
fall not <em>too</em> many orders of magnitude outside
|
||||
cosmologists' estimations of the age of the universe.</p>
|
||||
|
||||
<p> The file format for version 1.1.25 and later stores dates
|
||||
in the above-described fashion.</p>
|
||||
<p>The file format for version 1.1.25 and later stores dates in
|
||||
the above-described fashion.</p>
|
||||
|
||||
<p> Some internal routines use the <tt>time_t</tt> type to
|
||||
<p>Some internal routines use the <tt>time_t</tt> type to
|
||||
express seconds. Note that on most OSes, this is a 32-bit
|
||||
quantity, and is thus limited to the Unix epoch, roughly
|
||||
December 1901 thru Jan 2038. It is reasonable to expect that
|
||||
<tt> time_t</tt> will migrate to the use of 64 bit values by
|
||||
<tt>time_t</tt> will migrate to the use of 64 bit values by
|
||||
that time.</p>
|
||||
|
||||
<p> Backup and log files are time-stamped using the standard
|
||||
<p>Backup and log files are time-stamped using the standard
|
||||
Unix <tt>ctime()</tt> routine, which takes a <tt>time_t</tt>
|
||||
argument. Thus, the backup and log mechanism may experience
|
||||
trouble in 2038, assuming your present Unix continues to be in
|
||||
service at that time without any remediation.</p>
|
||||
|
||||
<p> Note that GnuCash also correctly recognizes February 29th,
|
||||
<p>Note that GnuCash also correctly recognizes February 29th,
|
||||
2000 as a "leap day," another of the "critical Y2K dates."</p>
|
||||
|
||||
<p> This is all highly suggestive that GnuCash should cope
|
||||
<p>This is all highly suggestive that GnuCash should cope
|
||||
reasonably well with the transition to the new millennium,
|
||||
whether that take place in 2000 or in 2001...</p>
|
||||
|
||||
<p>Y2K issues are described in more detail at <a href=
|
||||
"http://www.ntlug.org/~cbbrowne/linuxy2k.html"> Linux and Year
|
||||
<p>Y2K issues are described in more detail at <a href=
|
||||
"http://www.ntlug.org/~cbbrowne/linuxy2k.html">Linux and Year
|
||||
2000.</a></p>
|
||||
<hr>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
Loading…
Reference in New Issue
Block a user