mirror of
https://github.com/Gnucash/gnucash.git
synced 2025-02-25 18:55:30 -06:00
*** empty log message ***
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@2139 57a11ea4-9604-0410-9ed3-97b8803252fd
This commit is contained in:
Dave Peticolas
parent
9f7e27f5d4
commit
a0c79dc561
@ -1,41 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 2.0//EN">
|
||||
<html>
|
||||
<head>
|
||||
<title>Importing MYM Files</title>
|
||||
</head>
|
||||
<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
|
||||
|
||||
<p> <a href="http://www-cad.eecs.berkeley.edu/~gooch/mymdump.html">
|
||||
MyMdump</a></p>
|
||||
|
||||
<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> I hope others find these scripts useful.</p>
|
||||
|
||||
<p>Ken Yamaguchi October 1998</p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 11 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 13 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 9.6 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 7.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 7.6 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 33 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 12 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 7.4 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 34 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 14 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 13 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 7.4 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 7.6 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 4.5 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 66 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 14 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 14 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 64 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 65 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 9.7 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 7.0 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 9.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 9.8 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 43 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 5.5 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 14 KiB |
1578
Docs/C/projects.html
1578
Docs/C/projects.html
File diff suppressed because it is too large
Load Diff
@ -1,7 +0,0 @@
|
||||
#!/bin/ksh
|
||||
# $ID$
|
||||
# If you have Dave Raggett's "tidy" utility, this will tidy up
|
||||
# the HTML files here.
|
||||
for i in *.html ; do
|
||||
tidy -m -i $i
|
||||
done
|
||||
@ -1,673 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>About GnuCash</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1>About GnuCash</h1>
|
||||
|
||||
<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
|
||||
time. Create an GnuCash account for each of your bank
|
||||
accounts.</li>
|
||||
|
||||
<li>Each account maintains both a running balance and a
|
||||
reconciled balance, so you can keep track of the checks that
|
||||
have cleared your account.</li>
|
||||
|
||||
<li>
|
||||
<b>A simple user interface.</b>
|
||||
|
||||
<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
|
||||
Reconciling Accounts.</a></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
|
||||
with what your bank has reported, and makes it easier to
|
||||
track down any discrepancies.</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<b> QuickFill.</b>
|
||||
|
||||
<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>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<b>Stock/Mutual Fund Portfolios.</b>
|
||||
|
||||
<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">
|
||||
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>
|
||||
(partial, still broken).
|
||||
|
||||
<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>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<b><a href="xacc-quicken.html#QIF">Quicken File
|
||||
Import</a>.</b>
|
||||
|
||||
<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, andProfit/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>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<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> -
|
||||
Assets).</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<b> <a href="xacc-double.html">Double Entry</a></b>
|
||||
|
||||
<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
|
||||
altogether.</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<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
|
||||
Profit/Loss reports.</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<b> General Ledger</b>
|
||||
|
||||
<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
|
||||
currencies</a></b></li>
|
||||
</ul>
|
||||
|
||||
<h2>Versioning</h2>
|
||||
|
||||
<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 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
|
||||
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
|
||||
should first start by reading through the <a href=
|
||||
"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>
|
||||
|
||||
<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>
|
||||
|
||||
<dd>liked what he saw: the GUI was slick, the code was
|
||||
documented and well structured, and it was all GPL'ed. And so
|
||||
he re-wrote it: adding cell-widgets to XbaeMatrix, so that
|
||||
the combobox and arrows would make an even slicker GUI,
|
||||
rewrote the X-Accountant internals to add double-entry, an
|
||||
account hierarchy, split out a transaction mini-engine, add
|
||||
support for stocks, and spiff up the help menus. This was
|
||||
version 1.0 as of January 1998. Since then, for version 1.1,
|
||||
the engine was expanded and refined, and the register window
|
||||
code completely redesigned and made mostly Motif-(and
|
||||
GUI-)independent. Did some prototype OFX work.</dd>
|
||||
|
||||
<dt> <a href="mailto:jcollins@gnucash.org"> Jeremy
|
||||
Collins</a></dt>
|
||||
|
||||
<dd>publicized the GnoMoney project widely and broadly, and
|
||||
then changed its name to GnuCash. Jeremy created the
|
||||
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>
|
||||
|
||||
<dd>abused everyone for not using perl, and then added
|
||||
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:schoenberger@signsoft.com"> Dirk
|
||||
Schoenberger</a></dt>
|
||||
|
||||
<dd>is working on the Qt/KDE port</dd>
|
||||
|
||||
<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>
|
||||
</dl>
|
||||
|
||||
<h2>Fixers and Patchers</h2>
|
||||
|
||||
<p> The <em> cast of thousands</em> includes:</p>
|
||||
|
||||
<dl>
|
||||
<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
|
||||
Armstrong</a></dt>
|
||||
|
||||
<dd>for misc fixes</dd>
|
||||
|
||||
<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>
|
||||
|
||||
<dd>Swedish translation</dd>
|
||||
|
||||
<dt> <a href="mailto:bojsen@worldnet.att.net"> Per Bojsen</a></dt>
|
||||
|
||||
<dd>several core dump fixes</dd>
|
||||
|
||||
<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>
|
||||
|
||||
<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>
|
||||
|
||||
<dd>for MS-Money QIF support</dd>
|
||||
|
||||
<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
|
||||
Collins</a></dt>
|
||||
|
||||
<dd>for GnoMoney and GTK port</dd>
|
||||
|
||||
<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
|
||||
Deignan</a></dt>
|
||||
|
||||
<dd>for AIX binary version</dd>
|
||||
|
||||
<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>
|
||||
|
||||
<dd>for Solaris patches to XmHTML</dd>
|
||||
|
||||
<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>
|
||||
|
||||
<dd>ASX support</dd>
|
||||
|
||||
<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>
|
||||
|
||||
<dd>for gnome patches</dd>
|
||||
|
||||
<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>
|
||||
|
||||
<dd>qif importation code</dd>
|
||||
|
||||
<dt> <a href="mailto:otto@bug.redhat.com"> Otto
|
||||
Hammersmith</a></dt>
|
||||
|
||||
<dd>for RedHat RPM packaging</dd>
|
||||
|
||||
<dt> <a href="mailto:haral@codec.ro"> Alexandru
|
||||
Harsanyi</a></dt>
|
||||
|
||||
<dd>for fixing miscellaneous core dumps and lockups.</dd>
|
||||
|
||||
<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
|
||||
Kailasa</a></dt>
|
||||
|
||||
<dd>for gnome build fixes</dd>
|
||||
|
||||
<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>
|
||||
|
||||
<dd>for SuSE README file</dd>
|
||||
|
||||
<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
|
||||
Lemon</a></dt>
|
||||
|
||||
<dd>for NetBSD port</dd>
|
||||
|
||||
<dt> <a href="mailto:y-le-ny@ifrance.com"> Yannick Le
|
||||
Ny</a></dt>
|
||||
|
||||
<dd>pour la traduction en francais</dd>
|
||||
|
||||
<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
|
||||
Martin</a></dt>
|
||||
|
||||
<dd>major work on the gnome register</dd>
|
||||
|
||||
<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
|
||||
Merkel</a></dt>
|
||||
|
||||
<dd>reporting, gnome, and configuration patches.</dd>
|
||||
|
||||
<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
|
||||
III</a></dt>
|
||||
|
||||
<dd>for QIF core dump fix</dd>
|
||||
|
||||
<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">
|
||||
OmNiBuS</a></dt>
|
||||
|
||||
<dd>web site graphics and content</dd>
|
||||
|
||||
<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
|
||||
P{'e}lecq</a></dt>
|
||||
|
||||
<dd>i18n patches with gettext</dd>
|
||||
|
||||
<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
|
||||
Pointner</a></dt>
|
||||
|
||||
<dd>motif and configuration patches</dd>
|
||||
|
||||
<dt> <a href="mailto:maufk@csv.warwick.ac.uk"> Gavin
|
||||
Porter</a></dt>
|
||||
|
||||
<dd>for euro style dates</dd>
|
||||
|
||||
<dt> <a href="mailto:rr@sco.com"> Ron Record</a></dt>
|
||||
|
||||
<dd>for SCO Unixware and OpenServer binaries</dd>
|
||||
|
||||
<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
|
||||
Seawood</a></dt>
|
||||
|
||||
<dd>for XbaeMatrix core dump</dd>
|
||||
|
||||
<dt> <a href="mailto:msimons@fsimons01.erols.com"> Mike
|
||||
Simons</a></dt>
|
||||
|
||||
<dd>misc <tt> configure.in</tt> patches</dd>
|
||||
|
||||
<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
|
||||
Spruth</a></dt>
|
||||
|
||||
<dd>for German text and euro date rework</dd>
|
||||
|
||||
<dt> <a href="mailto:parys@freewwweb.com"> Robby Stephenson</a></dt>
|
||||
|
||||
<dd>register patch</dd>
|
||||
|
||||
<dt> <a href="mailto:tma@iis.fhg.de"> Herbert Thoma</a></dt>
|
||||
|
||||
<dd>gnome register patch</dd>
|
||||
|
||||
<dt> <a href="mailto:detrout@earthlink.net"> Diane
|
||||
Trout</a></dt>
|
||||
|
||||
<dd>scheme qif import patch</dd>
|
||||
|
||||
<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>
|
||||
|
||||
<dd>Great Britain translations</dd>
|
||||
|
||||
<dt> <a href="mailto:gooch@ic.EECS.Berkeley.EDU"> Ken
|
||||
Yamaguchi</a></dt>
|
||||
|
||||
<dd>QIF import fixes; MYM import</dd>
|
||||
</dl>
|
||||
|
||||
<h2>Supported Operating Systems</h2>
|
||||
gnucash-1.0.18 (xacc-1.0.18) is known to work on the following
|
||||
systems:
|
||||
|
||||
<ul>
|
||||
<li>Linux 2.0.x -- Intel w/ RedHat Motif</li>
|
||||
|
||||
<li>Linux 2.0.x -- Intel w/ Lesstif v0.81</li>
|
||||
|
||||
<li>Linux Debian -- Intel w/ Lesstif v0.81</li>
|
||||
|
||||
<li>SGI IRIX -- MIPS</li>
|
||||
|
||||
<li>IBM AIX 4.1.5 -- RS/6000</li>
|
||||
|
||||
<li>SCO Unixware 7 -- Intel</li>
|
||||
|
||||
<li>SCO OpenServer 5.0.4 -- Intel</li>
|
||||
|
||||
<li>NetBSD -- Intel</li>
|
||||
</ul>
|
||||
|
||||
<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>
|
||||
|
||||
<h2>History</h2>
|
||||
The table below shows some historical lines-of-code and
|
||||
number-of-files counts for the X-Accountant/GnuCash development
|
||||
project <br>
|
||||
|
||||
|
||||
<table border="1">
|
||||
<caption>
|
||||
Historical Development Stats
|
||||
</caption>
|
||||
|
||||
<tr align="center">
|
||||
<th>Version</th>
|
||||
|
||||
<th>engine</th>
|
||||
|
||||
<th>register</th>
|
||||
|
||||
<th>ledger</th>
|
||||
|
||||
<th>motif</th>
|
||||
|
||||
<th>gnome</th>
|
||||
|
||||
<th>qt</th>
|
||||
|
||||
<th>prefs (scm)</th>
|
||||
|
||||
<th>docs (html)</th>
|
||||
|
||||
<th>misc</th>
|
||||
|
||||
<th>Total</th>
|
||||
</tr>
|
||||
|
||||
<tr align="center">
|
||||
<td>xacc-0.9<br>
|
||||
Sept 97</td>
|
||||
|
||||
<td>-</td>
|
||||
|
||||
<td>-</td>
|
||||
|
||||
<td>-</td>
|
||||
|
||||
<td>34 files<br>
|
||||
(7.5+0.9)</td>
|
||||
|
||||
<td>-</td>
|
||||
|
||||
<td>-</td>
|
||||
|
||||
<td>-</td>
|
||||
|
||||
<td>5 files<br>
|
||||
(0.4)</td>
|
||||
|
||||
<td>-</td>
|
||||
|
||||
<td>39 files<br>
|
||||
(8.8)</td>
|
||||
</tr>
|
||||
|
||||
<tr align="center">
|
||||
<td>xacc-0.9w<br>
|
||||
Dec 97</td>
|
||||
|
||||
<td>-</td>
|
||||
|
||||
<td>-</td>
|
||||
|
||||
<td>-</td>
|
||||
|
||||
<td>51 files<br>
|
||||
(13.8+1.5)</td>
|
||||
|
||||
<td>-</td>
|
||||
|
||||
<td>-</td>
|
||||
|
||||
<td>-</td>
|
||||
|
||||
<td>9 files<br>
|
||||
(0.8)</td>
|
||||
|
||||
<td>-</td>
|
||||
|
||||
<td>60 files<br>
|
||||
(16.1)</td>
|
||||
</tr>
|
||||
|
||||
<tr align="center">
|
||||
<td>xacc-1.0.17<br>
|
||||
Feb 98</td>
|
||||
|
||||
<td>-</td>
|
||||
|
||||
<td>-</td>
|
||||
|
||||
<td>-</td>
|
||||
|
||||
<td>52 files<br>
|
||||
(14.8+1.8)</td>
|
||||
|
||||
<td>-</td>
|
||||
|
||||
<td>-</td>
|
||||
|
||||
<td>-</td>
|
||||
|
||||
<td>12 files<br>
|
||||
(1.4)</td>
|
||||
|
||||
<td>-</td>
|
||||
|
||||
<td>64 files<br>
|
||||
(18.0)</td>
|
||||
</tr>
|
||||
|
||||
<tr align="center">
|
||||
<td>gnucash-1.1.15<br>
|
||||
Aug 98</td>
|
||||
|
||||
<td>24 files<br>
|
||||
(6.2+1.5)</td>
|
||||
|
||||
<td>31 files<br>
|
||||
(6.1+1.7)</td>
|
||||
|
||||
<td>5 files<br>
|
||||
(1.4+0.4)</td>
|
||||
|
||||
<td>30 files<br>
|
||||
(7.4+0.7)</td>
|
||||
|
||||
<td>17 files<br>
|
||||
(3.4+0.5)</td>
|
||||
|
||||
<td>16 files<br>
|
||||
(1.2+0.2)</td>
|
||||
|
||||
<td>3 files<br>
|
||||
(0.3)</td>
|
||||
|
||||
<td>16 files<br>
|
||||
(1.9)</td>
|
||||
|
||||
<td>not counted<br>
|
||||
(>1.0)</td>
|
||||
|
||||
<td>142 files<br>
|
||||
(32.9)</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<p> Each cell contains:<br>
|
||||
<br>
|
||||
number of *c and *.h files<br>
|
||||
(KLOCS in *.c + KLOCS in *.h),</p>
|
||||
|
||||
<p> where KLOC == kilo-lines-of-code, as reported by <tt>
|
||||
wc</tt>.</p>
|
||||
<hr>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -1,30 +0,0 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
||||
<html>
|
||||
<head>
|
||||
<title>Editing Account Parameters</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<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><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. <EM>FIXME:
|
||||
could somebody who uses this feature please document it?</EM>></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>
|
||||
@ -1,151 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<title></title>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Account Types</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1>Account Types</h1>
|
||||
|
||||
<dl>
|
||||
<dt><b>Cash</b></dt>
|
||||
|
||||
<dd>The <b>cash</b> account type is used to denote the cash
|
||||
that you store in your wallet, shoebox, piggybank, or
|
||||
mattress.</dd>
|
||||
|
||||
<dt><b>Bank</b></dt>
|
||||
|
||||
<dd>The <b>Bank</b> account type denotes a savings or
|
||||
checking account held at a bank or other financial
|
||||
institution.</dd>
|
||||
|
||||
<dd>Such accounts sometimes bear interest.</dd>
|
||||
|
||||
<dt><b>Credit</b></dt>
|
||||
|
||||
<dd>The <b> Credit</b> card account is used to denote credit
|
||||
card accounts, whether involving floating lines of credit as
|
||||
with VISA, MasterCard, or Discover, as well as others like
|
||||
American Express that do <em> not</em> permit you to maintain
|
||||
continuing balances.</dd>
|
||||
|
||||
<dd>The introduction of <a href=
|
||||
"http://www.visa.com/pd/debit/checkcard.html"> Check
|
||||
Cards</a> where payments are withdrawn directly from a
|
||||
checking account makes the selection less clear; it is
|
||||
probably more appropriate to treat a "Check Card" as a <b>
|
||||
Bank</b> account, as it does withdraw amounts directly from
|
||||
such an account, not really involving any granting of
|
||||
credit.</dd>
|
||||
|
||||
<dt><b>Asset, Liability</b></dt>
|
||||
|
||||
<dd><b>Asset</b> and <b>Liability</b> accounts are used for
|
||||
tracking things that are of value, but that are not so
|
||||
directly translated into <em> cash</em> .</dd>
|
||||
|
||||
<dd>For instance, you might collect the costs of purchasing a
|
||||
house into an asset account entitled <b> My House,</b> or the
|
||||
cost of a car into <b> My Car,</b> or collect together the
|
||||
value of your <b> Computer Equipment.</b></dd>
|
||||
|
||||
<dd>And the home mortgage or car loan would be represented by
|
||||
liability accounts, <b> Home Mortgage</b> and <b> Car
|
||||
Loan</b>, to be drawn down as payments are made on these
|
||||
loans.</dd>
|
||||
|
||||
<dd>If you hold assets for business purposes, their decline
|
||||
in value over time might be treated as a deduction for tax
|
||||
purposes, that deduction being called <a href=
|
||||
"xacc-apprdepr.html#depr">Depreciation.</a></dd>
|
||||
|
||||
<dd>On the other hand, if you own assets that <em>
|
||||
appreciate</em> in value over time, such as real estate,
|
||||
collectibles like paintings, and investments like shares in
|
||||
companies, you may see them appreciate in value, and have to
|
||||
recognize, for tax purposes, what are called <a href=
|
||||
"xacc-apprdepr.html#appr"> Capital Gains.</a></dd>
|
||||
|
||||
<dt><a name="stockacct"></a><b>Stock, Mutual Fund</b></dt>
|
||||
|
||||
<dd>Securities that you invest in are a form of asset that
|
||||
are normally acquired with the express purpose of receiving
|
||||
income either in the form of dividends, interest, or <a href=
|
||||
"xacc-apprdepr.html#appr"> Capital Gains.</a> There are a
|
||||
multitude of securities markets around the world, and
|
||||
securities that are widely enough traded can have pretty
|
||||
concrete values that may be analyzed on a day-to-day
|
||||
basis.</dd>
|
||||
|
||||
<dd>
|
||||
Stock and Mutual Fund accounts are typically tracked in
|
||||
registers having three main columns:
|
||||
|
||||
<ul>
|
||||
<li>Price</li>
|
||||
|
||||
<li>Number of shares</li>
|
||||
|
||||
<li>Cost</li>
|
||||
</ul>
|
||||
</dd>
|
||||
|
||||
<dd>
|
||||
In order to get <em> useful</em> information out of the
|
||||
register, it is necessary to have multiple "views" on the
|
||||
data so that you may assess such things as:
|
||||
|
||||
<ul>
|
||||
<li>Total Values by security</li>
|
||||
|
||||
<li>Gains/Losses by security</li>
|
||||
|
||||
<li>Return On Investment rates by security</li>
|
||||
</ul>
|
||||
</dd>
|
||||
|
||||
<dd>More details may be found in the <a href=
|
||||
"xacc-ticker.html">Stock Ticker</a> section.</dd>
|
||||
|
||||
<dt><b><a href="xacc-expense.html"> Income,
|
||||
Expense</a></b></dt>
|
||||
|
||||
<dd><b> Income</b> and <b>Expense</b> accounts are used to
|
||||
collect incomes and expenses.</dd>
|
||||
|
||||
<dt><b>Equity</b></dt>
|
||||
|
||||
<dd><b>Equity</b> accounts are used to balance the balance
|
||||
sheet, indicating the portion of the "corporate" value
|
||||
represents <em> the net amount that the owners own.</em></dd>
|
||||
|
||||
<dd>On a year-by-year basis, a computed value called <b>
|
||||
Retained Earnings</b> indicates the net value of the
|
||||
enterprise; it is generally considered a good thing when this
|
||||
value increases.</dd>
|
||||
|
||||
<dt><a href="xacc-currency.html"> <b>Currency</b></a></dt>
|
||||
|
||||
<dd><b> Currency Accounts</b> are used for trading
|
||||
currencies.</dd>
|
||||
|
||||
<dd>In most ways, they behave like stocks, except that the
|
||||
only way that "income" may be gotten from them is from
|
||||
fluctuations in the relative values of currencies. Note that
|
||||
transfers cannot be made directly between two accounts
|
||||
denominated in different currencies. Such transfers may only
|
||||
be made into currency trading accounts.</dd>
|
||||
</dl>
|
||||
<hr>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -1,46 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<title></title>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>New Account Window</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1>New Account Window</h1>
|
||||
|
||||
<p> This is what a new account window looks like:</p>
|
||||
|
||||
<p> <img src="newaccwin-code.gif"></p>
|
||||
|
||||
<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 curency 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 picure below shows an example for a stock or currency
|
||||
trading account. Note that the Security field is not greyed
|
||||
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
|
||||
code.</a></p>
|
||||
|
||||
<p><br>
|
||||
<img src="newaccwin-trade.gif"><br>
|
||||
</p>
|
||||
<hr>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -1,25 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<title></title>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Adjust Balance Window</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1>Adjust Balance Window</h1>
|
||||
Adjust Balance window. Use this to adjust the balance. Enter a
|
||||
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>
|
||||
<hr>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -1,192 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Accounts Payable/Accounts Receivable</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1>Accounts Payable and Accounts Receivable</h1>
|
||||
|
||||
<p> A/R (Accounts Receivable) and A/P (Accounts Payable) are
|
||||
somewhat deep, and require thought to fully understand
|
||||
them.</p>
|
||||
|
||||
<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
|
||||
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>
|
||||
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
|
||||
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
|
||||
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>
|
||||
|
||||
<ul>
|
||||
<li>A customer sends in a <b>Purchase Order</b>, thus
|
||||
authorizing a purchase.</li>
|
||||
|
||||
<li>We set up a <b>Work Order</b> to schedule production of
|
||||
whatever the customer is buying</li>
|
||||
|
||||
<li>We issue a <b>Shipping Notice</b>, to ship to goods to
|
||||
the customer</li>
|
||||
|
||||
<li>Once shipped, we issue an <b>Invoice</b>, representing
|
||||
the <em> request to pay</em></li>
|
||||
</ul>
|
||||
|
||||
<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
|
||||
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>
|
||||
|
||||
<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>
|
||||
|
||||
<p> At that point, it is typical to record an entry thus:</p>
|
||||
|
||||
<table summary="BADDEBT">
|
||||
<tr>
|
||||
<th>Account</th>
|
||||
|
||||
<th>DR</th>
|
||||
|
||||
<th>CR</th>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Bad Debt Expense</td>
|
||||
|
||||
<td>$10,000</td>
|
||||
|
||||
<td>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Accounts Receivable</td>
|
||||
|
||||
<td>
|
||||
</td>
|
||||
|
||||
<td>$10,000</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<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>
|
||||
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>
|
||||
|
||||
<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>
|
||||
|
||||
<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>
|
||||
|
||||
<li>Three weeks later, the invoice comes in, and we issue a
|
||||
payment, and so <em> Debit AP, Credit Cash.</em><br>
|
||||
<br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<h1> Prepaid Expenses</h1>
|
||||
|
||||
<p> Analagous techniques are also used for expenses that are
|
||||
prepaid.</p>
|
||||
|
||||
<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>
|
||||
|
||||
<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>
|
||||
</ul>
|
||||
|
||||
<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
|
||||
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>
|
||||
<br>
|
||||
</li>
|
||||
</ul>
|
||||
<hr>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -1,716 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<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>
|
||||
|
||||
<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
|
||||
issues.</p>
|
||||
|
||||
<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>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<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>
|
||||
</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.
|
||||
|
||||
<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
|
||||
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
|
||||
interest</em> are often there to scare those that are
|
||||
sensitive to such things...)</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<h1>Capital Gains - Asset Appreciation</h1>
|
||||
<a name="appr"></a>
|
||||
|
||||
<p>Appreciaton 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>
|
||||
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>
|
||||
|
||||
<p> On the other hand, homes in your neighbourhood 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
|
||||
securities markets.</p>
|
||||
|
||||
<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
|
||||
specific context. In such cases, there several conflicting
|
||||
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
|
||||
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
|
||||
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>
|
||||
|
||||
<ul>
|
||||
<li>An <em>Asset Cost</em> asset account to track the
|
||||
original cost of the painting,</li>
|
||||
|
||||
<li>An <em>Accrued Unrealized Gains on Asset</em> asset
|
||||
account to keep track of increases in value, and</li>
|
||||
|
||||
<li>An <em>Accrued Gain On Asset Income</em> income account
|
||||
in which to record the income side of the annual gains in
|
||||
your riches, and</li>
|
||||
|
||||
<li>A <em>Realized Gain On Asset Income</em> income account
|
||||
in which to record the realized income when you sell the
|
||||
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>
|
||||
|
||||
<h2>The handling of capital gains in GnuCash</h2>
|
||||
|
||||
<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
|
||||
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>
|
||||
|
||||
<p>Your main window will resemble this:</p>
|
||||
<img src="appr-main1.gif" alt=
|
||||
"Main window after purchase and appreciation">
|
||||
|
||||
<p>and your asset account will resemble this:</p>
|
||||
<img src="appr-asset1.gif" alt=
|
||||
"Asset account after purchase and appreciation">
|
||||
|
||||
<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
|
||||
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>
|
||||
|
||||
<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
|
||||
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
|
||||
millions.</p>
|
||||
|
||||
<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
|
||||
estimate. You duly record these $2500 as an income like above,
|
||||
then decide to sell the painting.</p>
|
||||
|
||||
<p>Now there arise three possibilities:</p>
|
||||
|
||||
<ol>
|
||||
<li>
|
||||
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>
|
||||
Realized Gain</em> income account), and the recording is
|
||||
rather like:</p>
|
||||
|
||||
<table summary="BIGGAIN">
|
||||
<tr>
|
||||
<th>Account</th>
|
||||
|
||||
<th>Amount</th>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Cash</td>
|
||||
|
||||
<td>$16055</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Painting</td>
|
||||
|
||||
<td>-$11000</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Realized Gain Income</td>
|
||||
|
||||
<td>-$5055</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<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>
|
||||
income. If the total that had been accrued was $5000, then
|
||||
the transaction might look like the following:</p>
|
||||
|
||||
<table summary="BIGGAINACCRUEDTOO">
|
||||
<tr>
|
||||
<th>Account</th>
|
||||
|
||||
<th>Amount</th>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Cash</td>
|
||||
|
||||
<td>$16055</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Painting</td>
|
||||
|
||||
<td>-$11000</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Accrued Gain Asset</td>
|
||||
|
||||
<td>-$5000</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Realized Gain Income</td>
|
||||
|
||||
<td>-$5055</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Accrued Gain Income</td>
|
||||
|
||||
<td>$5000</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<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>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
You were overoptimistic 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
|
||||
painting.</p>
|
||||
|
||||
<p> The numbers change a little bit, but not too
|
||||
dramatically.</p>
|
||||
|
||||
<table summary="SMALLGAINACCRUEDTOO">
|
||||
<tr>
|
||||
<th>Account</th>
|
||||
|
||||
<th>Amount</th>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Cash</td>
|
||||
|
||||
<td>$15000</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Painting</td>
|
||||
|
||||
<td>-$11000</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Accrued Gain Asset</td>
|
||||
|
||||
<td>-$5000</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Realized Gain Income</td>
|
||||
|
||||
<td>-$4000</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Accrued Gain Income</td>
|
||||
|
||||
<td>$5000</td>
|
||||
</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.
|
||||
That's fine, as you had previously recognized $5000 in
|
||||
income.</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
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>
|
||||
i.e.</em> an income.</p>
|
||||
|
||||
<table summary="HUGEGAIN">
|
||||
<tr>
|
||||
<th>Account</th>
|
||||
|
||||
<th>Amount</th>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Cash</td>
|
||||
|
||||
<td>$50000</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Painting</td>
|
||||
|
||||
<td>-$11000</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Accrued Gain Asset</td>
|
||||
|
||||
<td>-$5000</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Realized Gain Income</td>
|
||||
|
||||
<td>-$39000</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Accrued Gain Income</td>
|
||||
|
||||
<td>$5000</td>
|
||||
</tr>
|
||||
</table>
|
||||
</li>
|
||||
</ol>
|
||||
|
||||
<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>
|
||||
|
||||
<p>Below, we show the second case discussed.</p>
|
||||
<img src="appr-main2.gif" alt="Main window after sale"><br
|
||||
clear="ALL">
|
||||
<img src="appr-asset2.gif" alt="Asset account after sale">
|
||||
|
||||
<h2>Caution about Valuation</h2>
|
||||
|
||||
<p>As we see in this example, for non-financial assets, it may
|
||||
be difficult to correctly estimate the ``true'' value of an
|
||||
asset.</p>
|
||||
|
||||
<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>
|
||||
|
||||
<ol>
|
||||
<li>
|
||||
Be careful with your estimation of values.
|
||||
|
||||
<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
|
||||
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
|
||||
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
|
||||
"profitable" on paper go out of business as a result of
|
||||
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
|
||||
universally useful.</p>
|
||||
|
||||
<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
|
||||
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
|
||||
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>
|
||||
|
||||
<p> In short, this presentation is fairly simple, but taxation
|
||||
often gets terribly complicated...</p>
|
||||
|
||||
<h1>Depreciation of assets</h1>
|
||||
<a name="depr"></a>
|
||||
|
||||
<p>Compared to the often uncertain estimates one has to do
|
||||
where appreciation of assets is concerned, we are on somewhat
|
||||
firmer ground here.</p>
|
||||
|
||||
<ul>
|
||||
<li>Governments tend to set up precise rules as to how you
|
||||
are required to calculate depreciation for tax purposes.</li>
|
||||
|
||||
<li>It is easy to look up in references such as "Blue Books"
|
||||
estimates of what an automobile should be worth after 3 years
|
||||
of use.</li>
|
||||
</ul>
|
||||
|
||||
<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>
|
||||
|
||||
<h2>Depreciation schemes</h2>
|
||||
|
||||
<h3>Linear depreciation</h3>
|
||||
|
||||
<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
|
||||
lifetime.</p>
|
||||
|
||||
<p><b>Example:</b> You have bought a computer for $1500 and
|
||||
wish to depreciate it over a period of 5 years. Each year the
|
||||
amount of depreciation is $300, leading to the following
|
||||
calculations:<br clear="ALL">
|
||||
</p>
|
||||
|
||||
<table summary="Example 1">
|
||||
<tr>
|
||||
<th>Year</th>
|
||||
|
||||
<th>Depreciation</th>
|
||||
|
||||
<th>Remaining Value</th>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>1</td>
|
||||
|
||||
<td>300</td>
|
||||
|
||||
<td>1200</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>2</td>
|
||||
|
||||
<td>300</td>
|
||||
|
||||
<td>900</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>3</td>
|
||||
|
||||
<td>300</td>
|
||||
|
||||
<td>600</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>4</td>
|
||||
|
||||
<td>300</td>
|
||||
|
||||
<td>300</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>5</td>
|
||||
|
||||
<td>300</td>
|
||||
|
||||
<td>0</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<h3>Geometric Depreciation</h3>
|
||||
|
||||
<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
|
||||
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> 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>
|
||||
|
||||
<p><strong>Example:</strong> We take the same example as above,
|
||||
with an annual depreciation of 30%.</p>
|
||||
|
||||
<table summary="Example 2">
|
||||
<tr>
|
||||
<th>Year</th>
|
||||
|
||||
<th>Depreciation</th>
|
||||
|
||||
<th>Remaining Value</th>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>1</td>
|
||||
|
||||
<td>450</td>
|
||||
|
||||
<td>1050</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>2</td>
|
||||
|
||||
<td>315</td>
|
||||
|
||||
<td>735</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>3</td>
|
||||
|
||||
<td>220.50</td>
|
||||
|
||||
<td>514.50</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>4</td>
|
||||
|
||||
<td>154.35</td>
|
||||
|
||||
<td>360.15</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>5</td>
|
||||
|
||||
<td>108.05</td>
|
||||
|
||||
<td>252.10</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<h3>Sum of digits</h3>
|
||||
|
||||
<p>A third method most often employed in Anglo/Saxon countries
|
||||
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
|
||||
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>
|
||||
|
||||
<table summary="Example 3">
|
||||
<tr>
|
||||
<th>Year</th>
|
||||
|
||||
<th>Depreciation</th>
|
||||
|
||||
<th>Remaining Value</th>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>1</td>
|
||||
|
||||
<td>100*5=500</td>
|
||||
|
||||
<td>1000</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>2</td>
|
||||
|
||||
<td>100*4=400</td>
|
||||
|
||||
<td>600</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>3</td>
|
||||
|
||||
<td>100*3=300</td>
|
||||
|
||||
<td>300</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>4</td>
|
||||
|
||||
<td>100*2=200</td>
|
||||
|
||||
<td>100</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>5</td>
|
||||
|
||||
<td>100*1=100</td>
|
||||
|
||||
<td>0</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<h2>The handling of depreciation in gnucash</h2>
|
||||
|
||||
<p>In order to keep track of the depreciation of an asset, you
|
||||
need :</p>
|
||||
|
||||
<ul>
|
||||
<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
|
||||
which to collect the sum of all of the years' depreciation
|
||||
amounts;</li>
|
||||
|
||||
<li>A <em>Depreciation Expense</em> expense account in which
|
||||
to record periodic depreciation expenses.</li>
|
||||
</ul>
|
||||
|
||||
<p>The first step, again, is to record the purchase of your
|
||||
asset by transferring the money from bank bank account to the
|
||||
<em>asset cost</em> account. Afterwards, in each accounting
|
||||
period you record the depreciation as an expense in the
|
||||
appropriate account.</p>
|
||||
|
||||
<p>The two windows below show your asset account and the main
|
||||
window after the third year of depreciation using a "sum of
|
||||
digits" scheme for the example above.</p>
|
||||
<img src="depr-asset.gif" alt=
|
||||
"Asset account after depreciation"><br clear="ALL">
|
||||
<img src="depr-main.gif" alt="Main window after depreciation">
|
||||
|
||||
|
||||
<h2>A word of caution</h2>
|
||||
|
||||
<p>Since depreciation and tax issues are closely related, you
|
||||
may not always be free in chosing 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
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -1,17 +0,0 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
||||
<html>
|
||||
<head>
|
||||
<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>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@ -1,21 +0,0 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
||||
<html>
|
||||
<head>
|
||||
<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>
|
||||
</html>
|
||||
File diff suppressed because it is too large
Load Diff
@ -1,45 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<title></title>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Date Data Input</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1>Date Input</h1>
|
||||
The date cell handles the following accelerator keys:
|
||||
|
||||
<ul>
|
||||
<li><tt> +, =</tt> increment day</li>
|
||||
|
||||
<li><tt> _ , -</tt> decrement day</li>
|
||||
|
||||
<li><tt> } , ]</tt> increment month</li>
|
||||
|
||||
<li><tt> { , [</tt> decrment month</li>
|
||||
|
||||
<li><tt> M , m</tt> begining of month</li>
|
||||
|
||||
<li><tt> H , h</tt> end of month</li>
|
||||
|
||||
<li><tt> Y , y</tt> begining of year</li>
|
||||
|
||||
<li><tt> R , r</tt> end of year</li>
|
||||
|
||||
<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>
|
||||
dates.h</tt></li>
|
||||
</ul>
|
||||
<hr>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -1,156 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<title></title>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Understanding Double Entry Accounting</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1>What is Double Entry Accounting?</h1>
|
||||
|
||||
<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
|
||||
balanced.</p>
|
||||
|
||||
<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
|
||||
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
|
||||
that part of the transaction</b> errors.</p>
|
||||
|
||||
<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>
|
||||
|
||||
<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
|
||||
yours. For instance, when you put money in, establishing a
|
||||
deposit, this establishes a <b> DEBT</b> on their part.</p>
|
||||
|
||||
<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
|
||||
debits and credits separately, the identity that all
|
||||
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>
|
||||
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
|
||||
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>
|
||||
|
||||
<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>
|
||||
|
||||
<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
|
||||
which a transfer may be made.</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Select one.
|
||||
|
||||
<p>When you record the transaction, the double-entry will
|
||||
automatically be made, and the transaction automatically
|
||||
appear in all windows showing the transferred-from and the
|
||||
transferred-to accounts.</p>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<h2> Changing Transactions</h2>
|
||||
|
||||
<p> To <em> change</em> a double-entry transaction:</p>
|
||||
|
||||
<p> Simply edit the transaction in any window in which it
|
||||
appears.</p>
|
||||
|
||||
<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
|
||||
"splits" will be deleted from both accounts, and balances will
|
||||
automatically be recalculated for <em> both</em> accounts.</p>
|
||||
|
||||
<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,
|
||||
or you may configure it to be "loose."</p>
|
||||
|
||||
<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
|
||||
probably not a really wise move. In effect:</p>
|
||||
|
||||
<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>
|
||||
|
||||
<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
|
||||
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>
|
||||
<hr>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -1,209 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Using Expense/Income Accounts</title>
|
||||
</head>
|
||||
|
||||
<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
|
||||
expense, and when I get money, this is an income.</b></p>
|
||||
|
||||
<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
|
||||
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> 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
|
||||
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>
|
||||
|
||||
<ul>
|
||||
<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,
|
||||
the bank account is credited, and the income account is
|
||||
debited, thus:</p>
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
<th>Account</th>
|
||||
|
||||
<th>Debit</th>
|
||||
|
||||
<th>Credit</th>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Chequing Account</td>
|
||||
|
||||
<td>1,600.00</td>
|
||||
|
||||
<td>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Salary</td>
|
||||
|
||||
<td>
|
||||
</td>
|
||||
|
||||
<td>1,600.00</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<p>This may be readily extended to a greater number of "split"
|
||||
items thus:</p>
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
<th>Account</th>
|
||||
|
||||
<th>Debit</th>
|
||||
|
||||
<th>Credit</th>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Chequing Account</td>
|
||||
|
||||
<td>1,300.00</td>
|
||||
|
||||
<td>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Income Taxes</td>
|
||||
|
||||
<td>200.00</td>
|
||||
|
||||
<td>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Health Plan</td>
|
||||
|
||||
<td>100.00</td>
|
||||
|
||||
<td>
|
||||
</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Salary</td>
|
||||
|
||||
<td>
|
||||
</td>
|
||||
|
||||
<td>1,600.00</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<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,
|
||||
the income/expense accounts do a slightly non-intuitive thing
|
||||
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>
|
||||
|
||||
<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
|
||||
so do not appear on the balance sheet. What appears on the
|
||||
balance sheet is their effects on <b> equity.</b></p>
|
||||
|
||||
<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
|
||||
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
|
||||
the transaction should also be handled correctly.</p>
|
||||
|
||||
<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
|
||||
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
|
||||
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> 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>
|
||||
|
||||
<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
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -1,42 +0,0 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
<title>Preferences</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1>Preferences</h1>
|
||||
<p>You can customize the behaviour 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>
|
||||
|
||||
<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>
|
||||
<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>
|
||||
</ul>
|
||||
|
||||
|
||||
<hr><p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
Page.</a></p>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@ -1,42 +0,0 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
<title>Preferences</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1>Preferences</h1>
|
||||
<p>You can customize the behaviour 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>
|
||||
|
||||
<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>
|
||||
<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>
|
||||
</ul>
|
||||
|
||||
|
||||
<hr><p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
Page.</a></p>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@ -1,341 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//IETF//DTD HTML//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>GNU General Public License</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1>GNU General Public License</h1>
|
||||
|
||||
<h2>Version 2, June 1991</h2>
|
||||
|
||||
<center>
|
||||
Copyright (C) 1989, 1991 Free Software Foundation, Inc. 675
|
||||
Mass Ave, Cambridge, MA 02139, USA
|
||||
|
||||
<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
|
||||
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
|
||||
free for all its users. This General Public License applies to
|
||||
most of the Free Software Foundation's software and to any
|
||||
other program whose authors commit to using it. (Some other
|
||||
Free Software Foundation software is covered by the GNU Library
|
||||
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> 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,
|
||||
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
|
||||
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'
|
||||
reputations.</p>
|
||||
|
||||
<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
|
||||
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
|
||||
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
|
||||
"work based on the Program" means either the Program or any
|
||||
derivative work under copyright law: that is to say, a work
|
||||
containing the Program or a portion of it, either verbatim or
|
||||
with modifications and/or translated into another language.
|
||||
(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
|
||||
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
|
||||
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
|
||||
warranty; keep intact all the notices that refer to this
|
||||
License and to the absence of any warranty; and give any other
|
||||
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
|
||||
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
|
||||
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
|
||||
conditions:</p>
|
||||
|
||||
<blockquote>
|
||||
a) You must cause the modified files to carry prominent
|
||||
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
|
||||
License.</p>
|
||||
|
||||
<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
|
||||
copyright notice and a notice that there is no warranty (or
|
||||
else, saying that you provide a warranty) and that users may
|
||||
redistribute the program under these conditions, and telling
|
||||
the user how to view a copy of this License. (Exception: if
|
||||
the Program itself is interactive but does not normally print
|
||||
such an announcement, your work based on the Program is not
|
||||
required to print an announcement.)</p>
|
||||
</blockquote>
|
||||
<hr>
|
||||
These requirements apply to the modified work as a whole. If
|
||||
identifiable sections of that work are not derived from the
|
||||
Program, and can be reasonably considered independent and
|
||||
separate works in themselves, then this License, and its terms,
|
||||
do not apply to those sections when you distribute them as
|
||||
separate works. But when you distribute the same sections as
|
||||
part of a whole which is a work based on the Program, the
|
||||
distribution of the whole must be on the terms of this License,
|
||||
whose permissions for other licensees extend to the entire
|
||||
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
|
||||
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
|
||||
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
|
||||
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>
|
||||
|
||||
<blockquote>
|
||||
a) Accompany it with the complete corresponding
|
||||
machine-readable source code, which must be distributed under
|
||||
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
|
||||
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
|
||||
code, to be distributed under the terms of Sections 1 and 2
|
||||
above on a medium customarily used for software interchange;
|
||||
or,</p>
|
||||
|
||||
<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
|
||||
executable form with such an offer, in accord with Subsection
|
||||
b above.)</p>
|
||||
</blockquote>
|
||||
|
||||
<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,
|
||||
plus the scripts used to control compilation and installation
|
||||
of the executable. However, as a special exception, the source
|
||||
code distributed need not include anything that is normally
|
||||
distributed (in either source or binary form) with the major
|
||||
components (compiler, kernel, and so on) of the operating
|
||||
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
|
||||
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
|
||||
parties are not compelled to copy the source along with the
|
||||
object code.</p>
|
||||
<hr>
|
||||
4. You may not copy, modify, sublicense, or distribute the
|
||||
Program except as expressly provided under this License. Any
|
||||
attempt otherwise to copy, modify, sublicense or distribute the
|
||||
Program is void, and will automatically terminate your rights
|
||||
under this License. However, parties who have received copies,
|
||||
or rights, from you under this License will not have their
|
||||
licenses terminated so long as such parties remain in full
|
||||
compliance.
|
||||
|
||||
<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
|
||||
License. Therefore, by modifying or distributing the Program
|
||||
(or any work based on the Program), you indicate your
|
||||
acceptance of this License to do so, and all its terms and
|
||||
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> 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
|
||||
this License. If you cannot distribute so as to satisfy
|
||||
simultaneously your obligations under this License and any
|
||||
other pertinent obligations, then as a consequence you may not
|
||||
distribute the Program at all. For example, if a patent license
|
||||
would not permit royalty-free redistribution of the Program by
|
||||
all those who receive copies directly or indirectly through
|
||||
you, then the only way you could satisfy both it and this
|
||||
License would be to refrain entirely from distribution of the
|
||||
Program.</p>
|
||||
|
||||
<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
|
||||
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
|
||||
distribution system, which is implemented by public license
|
||||
practices. Many people have made generous contributions to the
|
||||
wide range of software distributed through that system in
|
||||
reliance on consistent application of that system; it is up to
|
||||
the author/donor to decide if he or she is willing to
|
||||
distribute software through any other system and a licensee
|
||||
cannot impose that choice.</p>
|
||||
<hr>
|
||||
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
|
||||
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
|
||||
geographical distribution limitation excluding those countries,
|
||||
so that distribution is permitted only in or among countries
|
||||
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
|
||||
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
|
||||
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
|
||||
any later version published by the Free Software Foundation. If
|
||||
the Program does not specify a version number of this License,
|
||||
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
|
||||
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,
|
||||
write to the Free Software Foundation; we sometimes make
|
||||
exceptions for this. Our decision will be guided by the two
|
||||
goals of preserving the free status of all derivatives of our
|
||||
free software and of promoting the sharing and reuse of
|
||||
software generally.</p>
|
||||
|
||||
<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
|
||||
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,
|
||||
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
|
||||
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE
|
||||
ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS
|
||||
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
|
||||
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,
|
||||
INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR
|
||||
INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS
|
||||
OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED
|
||||
BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE
|
||||
WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY
|
||||
HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.</p>
|
||||
|
||||
<h3>END OF TERMS AND CONDITIONS</h3>
|
||||
<hr>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -1,377 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//IETF//DTD HTML//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Chart of Accounts and Account Numbering</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1>Chart of Accounts</h1>
|
||||
|
||||
<p> Typically accounts are arranged as a tree, in hierarchical
|
||||
form.</p>
|
||||
|
||||
<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
|
||||
branches are shown in the report, rather than the individual
|
||||
accounts. For example, a chart of accounts might look like the
|
||||
following:</p>
|
||||
<pre>
|
||||
300 Expenses
|
||||
|
|
||||
+--310 Living Expenses
|
||||
| |
|
||||
| +--311 Beer
|
||||
| |
|
||||
| +--312 Cable
|
||||
|
|
||||
+--320 Business Expenses
|
||||
| |
|
||||
| +--321 8-inch Floppies
|
||||
| |
|
||||
: :
|
||||
</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> 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>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
Overall Cash: <tt> 110</tt>
|
||||
|
||||
<ul>
|
||||
<li>Cash in Wallet: <tt> 111</tt></li>
|
||||
|
||||
<li>Cash in Sock in Closet: <tt> 112</tt></li>
|
||||
|
||||
<li>Cash in Mattress: <tt> 113</tt></li>
|
||||
|
||||
<li>Petty Cash Box: <tt> 114</tt></li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Overall Banking Assets <tt> 120</tt>
|
||||
|
||||
<ul>
|
||||
<li>Checking Account <tt> 121</tt></li>
|
||||
|
||||
<li>Savings Account <tt> 122</tt></li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<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
|
||||
encourage you to avoid this. Account codes are treated as
|
||||
numbers in base-36, thus, if you run out of numbers, you
|
||||
can use the letters, <tt>a</tt> through <tt>z</tt>.</p>
|
||||
|
||||
<h1>A Sample Chart of Accounts</h1>
|
||||
<a name="SAMPLECHART"></a>
|
||||
|
||||
<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>
|
||||
>>>>>>> 1.2
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
Assets
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
Cash On Hand
|
||||
|
||||
<ul>
|
||||
<li>Checking account</li>
|
||||
|
||||
<li>Money Market Account</li>
|
||||
|
||||
<li>Certificate of Deposit</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Fixed Assets
|
||||
|
||||
<ul>
|
||||
<li>Furniture</li>
|
||||
|
||||
<li>Computers</li>
|
||||
|
||||
<li>Jewelry, Collectibles</li>
|
||||
|
||||
<li>Tools, Machinery</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Investments
|
||||
|
||||
<ul>
|
||||
<li>Stocks</li>
|
||||
|
||||
<li>Bonds</li>
|
||||
|
||||
<li>Mutual Funds</li>
|
||||
|
||||
<li>Real Estate</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Liabilities
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
Taxes
|
||||
|
||||
<ul>
|
||||
<li>Federal Income Tax</li>
|
||||
|
||||
<li>Social Security</li>
|
||||
|
||||
<li>Medicare</li>
|
||||
|
||||
<li>FUTA</li>
|
||||
|
||||
<li>State Income Tax</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Accounts Payable
|
||||
|
||||
<ul>
|
||||
<li>MasterCard</li>
|
||||
|
||||
<li>Visa</li>
|
||||
|
||||
<li>American Express</li>
|
||||
|
||||
<li>Diner's Club</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Loans
|
||||
|
||||
<ul>
|
||||
<li>Debentures</li>
|
||||
|
||||
<li>School Loan</li>
|
||||
|
||||
<li>Uncle Harry's Tide-me-over</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Equity
|
||||
|
||||
<ul>
|
||||
<li>Retained Earnings</li>
|
||||
|
||||
<li>Current Year Earnings</li>
|
||||
|
||||
<li>Historical Adjustments</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Income
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
Interest Income
|
||||
|
||||
<ul>
|
||||
<li>Bank Account Interest</li>
|
||||
|
||||
<li>Certificate of Deposit</li>
|
||||
|
||||
<li>Bond Interest</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Dividends
|
||||
|
||||
<ul>
|
||||
<li>Stock</li>
|
||||
|
||||
<li>Mutual Fund</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Consulting
|
||||
|
||||
<ul>
|
||||
<li>ABC Design</li>
|
||||
|
||||
<li>PQR Infomatics</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Salary
|
||||
|
||||
<ul>
|
||||
<li>My Day Job</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Commissions
|
||||
|
||||
<ul>
|
||||
<li>Royalties</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Expenses
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
Rent and Utilities
|
||||
|
||||
<ul>
|
||||
<li>Rent</li>
|
||||
|
||||
<li>Rent Late Fees</li>
|
||||
|
||||
<li>Electricity</li>
|
||||
|
||||
<li>Gas</li>
|
||||
|
||||
<li>Phone</li>
|
||||
|
||||
<li>Internet</li>
|
||||
|
||||
<li>Cable TV</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Office Expenses
|
||||
|
||||
<ul>
|
||||
<li>Accounting</li>
|
||||
|
||||
<li>Legal</li>
|
||||
|
||||
<li>Software</li>
|
||||
|
||||
<li>Postage</li>
|
||||
|
||||
<li>Bank Charges</li>
|
||||
|
||||
<li>Credit Card Charges</li>
|
||||
|
||||
<li>Toner, Paper, Paper Clips</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Auto Expenses
|
||||
|
||||
<ul>
|
||||
<li>Gas</li>
|
||||
|
||||
<li>Insurance</li>
|
||||
|
||||
<li>Repair</li>
|
||||
|
||||
<li>Rental</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Taxes
|
||||
|
||||
<ul>
|
||||
<li>Social Security</li>
|
||||
|
||||
<li>Unemployment</li>
|
||||
|
||||
<li>IRS penalties</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Wages and Salaries
|
||||
|
||||
<ul>
|
||||
<li>Consulting</li>
|
||||
|
||||
<li>Wages</li>
|
||||
|
||||
<li>Health Insurance</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Travel
|
||||
|
||||
<ul>
|
||||
<li>Air</li>
|
||||
|
||||
<li>Hotel</li>
|
||||
|
||||
<li>Meals</li>
|
||||
|
||||
<li>Auto</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Marketing
|
||||
|
||||
<ul>
|
||||
<li>Advertising</li>
|
||||
|
||||
<li>Trade Shows</li>
|
||||
|
||||
<li>Give Aways</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
<hr>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -1,105 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//IETF//DTD HTML//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>GnuCash Help Main Window</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1> User Documentation Overview</h1>
|
||||
For help on a specific topic:
|
||||
|
||||
<ul>
|
||||
<li><a href="xacc-about.html">About GnuCash</a></li>
|
||||
|
||||
<li><a href="xacc-acctypes.html">Account Types</a></li>
|
||||
|
||||
<li><a href="xacc-apar.html">Accounts Payable and Accounts
|
||||
Receivable</a></li>
|
||||
|
||||
<li><a href="xacc-groups.html">Chart of Accounts</a></li>
|
||||
|
||||
<li><a href="xacc-accwin.html">Creating a new
|
||||
account</a></li>
|
||||
|
||||
<li><a href="xacc-date.html">Date Input</a></li>
|
||||
|
||||
<li><a href="xacc-apprdepr.html"> Depreciation and Capital
|
||||
Gains</a></li>
|
||||
|
||||
<li><a href="xacc-currency.html">Foreign Currency
|
||||
Accounts</a></li>
|
||||
|
||||
<li><a href="bofa-mym.html">Importing MYM (Managing Your
|
||||
Money) Files</a></li>
|
||||
|
||||
<li><a href="xacc-quicken.html">A Guide for Former Users of
|
||||
Quicken(TM)</a></li>
|
||||
|
||||
<li>
|
||||
<a href="xacc-gpl.html">License - GPL</a>
|
||||
|
||||
<ul>
|
||||
<li><a href="xacc-gpl.html#SEC003">Warranty</a></li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li><a href="xacc-mainwin.html">The Main Window</a></li>
|
||||
|
||||
<li><a href="xacc-recnwin.html">The Reconcile Window</a></li>
|
||||
|
||||
<li><a href="xacc-regwin.html">The Register Window</a></li>
|
||||
|
||||
<li><a href="xacc-ticker.html">Stock Ticker</a></li>
|
||||
|
||||
<li><a href="xacc-double.html">Using Double Entry</a></li>
|
||||
|
||||
<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>
|
||||
</ul>
|
||||
|
||||
<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> 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="xacc-print.html">Printing and Web
|
||||
Serving</a></li>
|
||||
|
||||
<li>
|
||||
<a href="xacc-reports.html">Reports</a>
|
||||
|
||||
<p> The reporting subsystem is presently undergoing active
|
||||
development; documentation should eventually include:</p>
|
||||
|
||||
<ul>
|
||||
<li>User documentation on how to use built-in
|
||||
reports</li>
|
||||
|
||||
<li>"Power User" documentation on how to create new
|
||||
reports</li>
|
||||
|
||||
<li>A design overview describing the reporting
|
||||
architecture</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li><a href="xacc-y2k.html">Y2K Considerations</a></li>
|
||||
</ul>
|
||||
<hr>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -1,51 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//IETF//DTD HTML//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Main Window</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1>Main GnuCash Window</h1>
|
||||
|
||||
<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> <img src="contract.gif"><br>
|
||||
</p>
|
||||
|
||||
<p> Here is the main window, with the detail accounts
|
||||
showing.</p>
|
||||
|
||||
<p><br>
|
||||
<img src="expand.gif"><br>
|
||||
</p>
|
||||
<hr>
|
||||
|
||||
<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
|
||||
general ledger window is opened, which displays all
|
||||
transactions for the lead and the detail accounts. Note that
|
||||
the general ledger window is more complicated and harder to use
|
||||
than the individual account registers. The general ledger
|
||||
window allows a more comprehensive overview of accounts in a
|
||||
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
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -1,20 +0,0 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
||||
<html>
|
||||
<head>
|
||||
<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>
|
||||
</html>
|
||||
@ -1,97 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//IETF//DTD HTML//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Printing Checks</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1>Printing Checks</h1>
|
||||
|
||||
<p> You may print a GnuCash transaction as a check by selecting
|
||||
"Print Check" from the Transaction menu in a register display
|
||||
window.
|
||||
|
||||
<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.
|
||||
|
||||
<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> By default, the check format is <tt>Quicken/QuickBooks</tt>,
|
||||
which prints to any Quicken-compatible check forms.
|
||||
|
||||
<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> 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> 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.
|
||||
|
||||
<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.
|
||||
|
||||
<h2>Custom check position</h2>
|
||||
|
||||
<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.
|
||||
|
||||
<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.
|
||||
|
||||
<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.
|
||||
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -1,52 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//IETF//DTD HTML//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Printing and Web Serving</title>
|
||||
</head>
|
||||
|
||||
<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> 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>.
|
||||
|
||||
<h1> GnuCash as Web Server</h1>
|
||||
|
||||
<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>
|
||||
|
||||
<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
|
||||
again</em> to "reload" things and allow prepare it for
|
||||
another data dump.<br>
|
||||
<br>
|
||||
</li>
|
||||
</ul>
|
||||
<hr>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -1,455 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<title>Importing Quicken Data Into GnuCash</title>
|
||||
<meta name="description" content=
|
||||
"Importing Quicken data into GnuCash isn't the simplest thing in the world, but if you pay attention and have some patience you can get a very close approximation of what you want.">
|
||||
<meta name="keywords" content=
|
||||
"QIF, Quicken, importing">
|
||||
</head>
|
||||
|
||||
<body bgcolor="#eeeeee">
|
||||
<h1>Importing Quicken data into GnuCash</h1>
|
||||
<h3>Bill Gribble <grib@billgribble.com></h3>
|
||||
|
||||
<a name="toc"><h2>Table of Contents</h2></a>
|
||||
<ul>
|
||||
<li> <a href="#overview">Overview
|
||||
<li> <a href="#intro">Introduction to the QIF file</a>
|
||||
<li> <a href="#how-to">How to use the Import QIF dialog</a>
|
||||
<li> <a href="#dialog-files">The "Files" tab</a>
|
||||
<li> <a href="#dialog-accounts">The "Accounts" and "Categories" tabs</a>
|
||||
<li> <a href="#dialog-picker">The Account Picker dialog</a>
|
||||
<li> <a href="#ok-button">The "OK" button
|
||||
<li> <a href="#hints">Hints</a>
|
||||
<ul><li> <a href="#opening-balance">Opening balances</a>
|
||||
<li> <a href="#empty-category">Empty category</a>
|
||||
<li> <a href="#dividend-category">Dividend category</a>
|
||||
<li> <a href="#fund-families">Fund families</a>
|
||||
<li> <a href="#brokerage-accounts">Brokerage accounts</a>
|
||||
</ul>
|
||||
</ul>
|
||||
|
||||
|
||||
<a name="overview"><h2>Overview</h2></a>
|
||||
|
||||
<p>Quicken is one of the best-selling programs in the history of
|
||||
the Universe. Pretty much everyone that has owned a PC or Mac since
|
||||
the late 80's has had a copy of it lying around somewhere, and lots of
|
||||
people actually use it to keep track of their finances. Why? Because
|
||||
it works pretty well and Intuit has (to their credit) done a good job
|
||||
of keeping up with what people want the program to do.
|
||||
|
||||
<p>They've done such a good job, in fact, that lots of Linux folks
|
||||
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.
|
||||
|
||||
<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
|
||||
handholding 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.
|
||||
|
||||
<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>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.
|
||||
|
||||
<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.
|
||||
|
||||
<p><a href="#toc">Table of Contents</a>
|
||||
|
||||
<a name="intro"><h2>Introduction to the QIF file</h2></a>
|
||||
|
||||
<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 immedately 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.
|
||||
|
||||
<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.
|
||||
|
||||
<p>Here's a typical Quicken transaction record:
|
||||
<pre>
|
||||
!Type:Bank
|
||||
D6/20/97
|
||||
T-500
|
||||
N1012
|
||||
C*
|
||||
M
|
||||
P
|
||||
L[Visa]
|
||||
^
|
||||
</pre>
|
||||
|
||||
<p>The ! tag denotes the start of a section of records of a
|
||||
certain type. In this case, Bank transactions. Type:Cat means
|
||||
a section of Category descriptions, Account means account
|
||||
descriptions, and so on.
|
||||
|
||||
<p>The D tag denotes the date. Note y2k compliance "issue".
|
||||
Here's a lovely "feature" of some version of Quicken and dates in
|
||||
2000:
|
||||
<pre>
|
||||
D1/ 1' 0
|
||||
T-640.00
|
||||
CX
|
||||
N511
|
||||
PJoe Bob
|
||||
LRent:Apartment
|
||||
^
|
||||
</pre>
|
||||
|
||||
<p>Ouch! Fortunately the GnuCash QIF importer can handle all of
|
||||
the wacky date formats that the gnucash-devel list can find.
|
||||
|
||||
<p>The T field is the "Total" amount of the transaction. If there
|
||||
are splits, the sum of all the split amounts is in a T field. Money
|
||||
going out of the account is negative.
|
||||
|
||||
<p>The N field is a "Number", which is usually a check number or
|
||||
some other identifying number for the transaction.
|
||||
|
||||
<p>The C field represents the clearing/reconciliation state of the
|
||||
transaction. An x or X in this field means the transaction is
|
||||
"Cleared", a * means the transaction is Reconciled.
|
||||
|
||||
<p>The M field is the transaction memo.
|
||||
|
||||
<p>The P field is the Payee.
|
||||
|
||||
<p>The L field is the Category/Account line. If the value in this
|
||||
field is enclosed in square brackets, like [Visa], this transaction is
|
||||
a transfer to the Quicken account named Visa. If there are no square
|
||||
brackets, the transaction is in the named Category (like
|
||||
Rent:Apartment).
|
||||
|
||||
<p>The ^ tag means End of Record.
|
||||
|
||||
<p>Quicken users taking advantage of Classes will see a slash (/)
|
||||
character followed by the class name appended on the Category line
|
||||
(like [Visa]/Project)
|
||||
|
||||
<p>If a transaction has "splits", meaning that it is a single
|
||||
transaction with "this" account but is "split" into multiple
|
||||
source/destination accounts, the splits are described with S fields
|
||||
for the category/account/class of each split, an $ field for the
|
||||
amount of the split, and an E field for a per-split memo. The total
|
||||
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:
|
||||
<pre>
|
||||
!Type:Bank
|
||||
D12/03/95
|
||||
T4,706.57
|
||||
CX
|
||||
POpening Balance
|
||||
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
|
||||
of what we do with them.
|
||||
|
||||
<p><a href="#toc">Table of Contents</a>
|
||||
|
||||
<a name="how-to"><h2>How to use the QIF Import dialog</h2></a>
|
||||
|
||||
<p>QIF files describe only one account, and try to be "complete"
|
||||
in representing all the transactions involving that account. This is
|
||||
fine if you only have one account, but if you have multiple Quicken
|
||||
accounts and transfers between them, transactions will show up in
|
||||
multiple files. 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
|
||||
account tree, export everything you can from Quicken and then import
|
||||
it all in one session. The importer's
|
||||
<a href="#dialog-files">Files tab</a> will allow you to load
|
||||
as many QIF files as you want, and to make sure that the currency,
|
||||
Quicken account name, and so on are right for each one. Then the
|
||||
importer can do a really good job of catching cross-references and
|
||||
marking them.
|
||||
|
||||
<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.
|
||||
|
||||
<p>Once you have loaded all the files into the importer, go to the
|
||||
<a href="#dialog-accounts">Accounts tab</a>, and then to the
|
||||
<a 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
|
||||
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
|
||||
accounts you won't have to correct the importer again.
|
||||
|
||||
<p>Make sure (especially in the Accounts tab) that the QIF account
|
||||
names and transaction counts make sense to you. If you see that one
|
||||
QIF account is mentioned by two different names, make sure that the
|
||||
"QIF Account" for every file in the Files tab is what you meant it to
|
||||
be. If the QIF Account for a file is wrong, the importer won't be
|
||||
able to match up transfers correctly and your balances will be wrong.
|
||||
If a QIF Account for a file is wrong, select the file in the Files tab,
|
||||
unmark the "Auto" checkbox, and edit the text box to contain the right
|
||||
name, then click "Load File" again. You will be asked to confirm a
|
||||
reload of the file and then it will be done. Flip back to the
|
||||
Accounts tab, see if that fixed the problem, repeat as necessary.
|
||||
|
||||
<p>When you are happy with the account mappings (double check
|
||||
them, and make sure to save your GnuCash session first just to be
|
||||
sure), then and only then click OK. If you click Cancel at any time,
|
||||
your accounts will not be touched.
|
||||
|
||||
<p>Again, the importer is written mostly in Guile, and it can be a
|
||||
little slow on large QIF files. It takes 3-4 seconds to stuff 1000
|
||||
transactions into GnuCash on a Celeron 433, proportionately longer on
|
||||
slower CPUs. You only have to do a large import like that a few
|
||||
times, fortunately, so I'm not too worried about it.
|
||||
|
||||
<p><a href="#toc">Table of Contents</a>
|
||||
|
||||
<a name=dialog-files><h2>The "Files" Tab</h2>
|
||||
|
||||
<p>The first thing to do is load all your files. Click "Select
|
||||
File", pick your file, then set the account, currency, radix, and date
|
||||
fields, then click "Load File". The Currency field defaults to the
|
||||
GnuCash default currency (set in the International tab of the
|
||||
Preferences dialog). Try autodetecting radix, date format, and
|
||||
account name first. The radix and date formats will stay on
|
||||
"Autodetect" if the autodetector is not 100 percent sure of the right
|
||||
answer; in that case, you will have to make a manual selection. You
|
||||
probably know what the correct radix format is; if you're in the US or
|
||||
the UK, it's definitely "decimal". Almost every QIF file I have seen
|
||||
in the US is m/d/y for the date format, so try that if autodetect
|
||||
doesn't work.
|
||||
|
||||
<p>To go back to a file that you have previously loaded, select
|
||||
its name in the file list on the left. If you change settings for a
|
||||
previously-loaded file, click "Load File" again to reload it with new
|
||||
settings. Don't forget to turn off "Auto" on the QIF Account entry if
|
||||
you manually enter it.
|
||||
|
||||
<p>If there's no Opening Balance record in the file, the account
|
||||
name is guessed from the file name: any .qif extension is removed, and
|
||||
all dashes and underscores are changed to spaces. If you want to save
|
||||
yourself manually re-entering the name, save the file with a name that
|
||||
will get guessed correctly (i.e. save the account "My Bank Account" as
|
||||
My-Bank-Account.qif or My_Bank_Account.qif).
|
||||
|
||||
<p>GnuCash makes a hearty effort to interpret any QIF file that
|
||||
you throw at it, but you need to make sure that it's a normal DOS or
|
||||
Unix text file before trying to import. The Mac version of Quicken
|
||||
saves files with Macintosh newline conventions, which really confuses
|
||||
the Guile reader. Macintoshes use the carriage-return only (which
|
||||
usually prints as ^M), and the Unix convention requires a line feed
|
||||
(usually prints as ^J). You can use "tr" to fix this problem, or a
|
||||
search and replace in your favorite text editor. With tr,
|
||||
the command might look like
|
||||
<pre>
|
||||
cat macfile | tr 015 012 > unixfile
|
||||
</pre>
|
||||
|
||||
<p><a href="#toc">Table of Contents</a>
|
||||
|
||||
<a name=dialog-accounts><h2>The "Accounts" and "Categories" Tabs</h2>
|
||||
|
||||
<p>Each line in the Accounts tab display represents a mapping from
|
||||
a Quicken account to a GnuCash account. Similarly, the Categories tab
|
||||
display shows mappings from Quicken categories to GnuCash
|
||||
accounts. Only QIF accounts referenced by one or more transaction
|
||||
records are displayed. The name of the GnuCash account is displayed
|
||||
in "full name" format, including the names of all parent accounts
|
||||
separated by your default separator character (generally ":").
|
||||
|
||||
<p>The first thing to check is the column of Quicken account
|
||||
names. Make sure there are no duplicates with slightly-different
|
||||
names. If a QIF transaction makes a transfer to [My Checking], and
|
||||
you imported a file called my-checking.qif, you might have one account
|
||||
entry for "my checking" and one for "My Checking". If these are the
|
||||
same account, you need to go back to the Files tab and reload
|
||||
my-checking.qif with the correct Quicken account name, My Checking.
|
||||
|
||||
<p>Once you have all the Quicken accounts making sense, check the
|
||||
GnuCash account column. The default GnuCash account for a given
|
||||
Quicken account is determined by a fallback procedure which makes the
|
||||
best guess it can given the available information. The guesses that
|
||||
are tried are (in order of preference):
|
||||
|
||||
<ul>
|
||||
<li>Saved mappings from previous import sessions. Each time you
|
||||
click "OK" in the import dialog, the mappings that you have selected
|
||||
are saved for the next time you import files. At the moment, the file
|
||||
is always called ~/.gnucash/qif-accounts-map. If you get some weird
|
||||
default mappings (for instance, if you change an account name and the
|
||||
importer wants to keep creating a new account with the old name) just
|
||||
delete this file. It's on my wishlist to make this work a little
|
||||
more smoothly.
|
||||
|
||||
<li>Similar accounts from your existing GnuCash account tree.
|
||||
"Similar" means that the account types are compatible and the names
|
||||
could reasonably be assumed to refer to the same thing. Full-path
|
||||
exact name matches are preferred most, followed by case-insensitive
|
||||
matches, followed by matches with prepended account parents (i.e.
|
||||
QIF account Visa matches GnuCash account Credit Cards:Visa), followed
|
||||
by various substring matches. If you think of a good heuristic
|
||||
for this, let me know.
|
||||
|
||||
<li>New account. The name of the new account is currently just
|
||||
the same as the name of the Quicken account; again, if you think of a
|
||||
good heuristic to make this better let me know. I've thought about
|
||||
making it look for subtrees to insert into (if all existing credit
|
||||
card accounts are children of an account, make the new account a child
|
||||
of that account, etc). On the wishlist.
|
||||
</ul>
|
||||
|
||||
<p>Check both the name of the GnuCash account for each QIF account
|
||||
and the type. If you are unhappy with either, click on the row in the
|
||||
display containing the offensive mapping. You will see the
|
||||
<a href="#dialog-picker">Account Picker</a> dialog which will allow you
|
||||
to change it.
|
||||
|
||||
<p><a href="#toc">Table of Contents</a>
|
||||
|
||||
<a name=dialog-picker><h2>The Account Picker</h2>
|
||||
|
||||
<p>This account picker is sort of broken. The idea is that you
|
||||
can select an existing account from the tree display, or enter
|
||||
information for a new account in the boxes below. However, right now
|
||||
it's possible to do Very Bad things like specify a subaccount of an
|
||||
existing account with a type that's not compatible with the parent.
|
||||
As soon as I figure out how I want this dialog to work I'll fix it. I
|
||||
have tested out the worst things that you can do and nothing terrible
|
||||
happens, except your account tree might be in a state that you could
|
||||
never have created through the GUI (a Credit Card account as a child
|
||||
of a Bank account, for example). Don't do that. I'll fix it Real
|
||||
Soon.
|
||||
|
||||
<p><a href="#toc">Table of Contents</a>
|
||||
|
||||
<a name=ok-button><h2>The "OK" Button</h2></a>
|
||||
|
||||
<p>Everything really happens when you hit the "OK" button, so it
|
||||
gets a section to itself.
|
||||
<ul>
|
||||
<li>First we do a "mark and sweep" to eliminate the duplicated
|
||||
halves of transfers in the loaded Quicken transactions.
|
||||
<li>A GnuCash account tree is created which mirrors
|
||||
your existing tree and includes any new accounts added by your
|
||||
Accounts and Categories mappings.
|
||||
<li>All the QIF transactions are converted into GnuCash splits and
|
||||
stuffed into the new account tree.
|
||||
<li>Finally, the GnuCash engine is asked to merge the old account
|
||||
tree with the new account tree.
|
||||
</ul>
|
||||
|
||||
<p><a href="#toc">Table of Contents</a>
|
||||
|
||||
<a name="hints"><h2>A few hints</h2></a>
|
||||
|
||||
<a name="opening-balance"><h3>Opening Balance</h3></a>
|
||||
<p>If your Quicken files have "Opening Balance" records, you will
|
||||
see an account called "Opening Balance" in the Accounts tab.
|
||||
Accounting for the source of opening balances is sort of a hassle,
|
||||
when you think about it, because they come from accounts that are
|
||||
outside the scope of the GnuCash universe. The suggestion I've seen
|
||||
on the gnucash-devel list is to make Opening Balances point to a
|
||||
GnuCash account called "Retained Earnings", of type Equity. I don't
|
||||
exactly understand this but it seems reasonable, and it's the default
|
||||
for accounts called "Opening Balance".
|
||||
|
||||
<a name="empty-category"><h3>Empty category</h3></a>
|
||||
|
||||
<p>In the Categories display, you may notice a blank QIF Category
|
||||
entry. Quicken transactions are not required to have a Category, but
|
||||
GnuCash transactions are required to have a source and a destination.
|
||||
The blank category lets you select which GnuCash account all
|
||||
uncategorized transactions go to. This will generally be
|
||||
miscellaneous checks you have written, cash withdrawals, and so on, so
|
||||
you probably want to put these in a "Misc Expenses" account or
|
||||
something similar. It may make sense to put this in an equity
|
||||
account; let me know if there's a good explanation for how it should
|
||||
be.
|
||||
|
||||
<a name="dividend-category"><h3>Dividend category</h3></a>
|
||||
|
||||
<p>Quicken stock transactions have a recognizable pattern for
|
||||
dividend payments. If the importer can definitely tell that a
|
||||
transaction is a transfer from dividends then it will default to
|
||||
creating a "Dividend" income account. This category is usually not
|
||||
present in the Quicken file, so it's being manufactured out of
|
||||
nowhere.
|
||||
|
||||
<a name="fund-families"><h3>Fund families</h3></a>
|
||||
|
||||
<p>Quicken has the abstraction of a single account representing a
|
||||
"fund family" for the purpose of allowing smooth transfers between the
|
||||
various accounts administered within the family. The GnuCash Importer
|
||||
will ALWAYS get this wrong the first time, because Quicken explicitly
|
||||
puts the wrong information in the file. The "blanket" account
|
||||
representing the fund family as a whole should probably be a Bank
|
||||
account, since the transfers to and from it in the Quicken file are
|
||||
denominated in currency, not shares. The balance of such an account
|
||||
is supposed to always be 0 since you just use it as an intermediary
|
||||
between two accounts in the family. Hopefully I'll fix this at some
|
||||
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
|
||||
thinking is that the brokerage account itself should probably be a
|
||||
Bank account. The only wierdness is in stuff like dividends paid from
|
||||
securities to the brokerage account. If you're using a Dividend
|
||||
account, you can lose the information about where the dividend came
|
||||
from. The importer tries to save this information by putting the
|
||||
security name in the Payee slot (which shows up in the GnuCash
|
||||
Description field for the transaction). If you have a better idea,
|
||||
let me know.
|
||||
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -1,172 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//IETF//DTD HTML//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>A Guide for Former Users of Quicken</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1>Quicken (TM) User's Guide</h1>
|
||||
|
||||
<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
|
||||
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
|
||||
that as the name of the account.</p>
|
||||
|
||||
<h1>Quicken QIF File Import</h1>
|
||||
<a name="QIF"></a> GnuCash supports the import of Quicken
|
||||
Import Files (QIF). (Note: Only Quicken Version 3.0 QIF has
|
||||
been formally tested so far.)
|
||||
|
||||
<p> Note that the QIF format is representive 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
|
||||
Quicken.</p>
|
||||
|
||||
<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
|
||||
account names that you might be using in GnuCash.</p>
|
||||
|
||||
<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>
|
||||
|
||||
<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>
|
||||
Caldera's Wabi, and doubtless on VMWare, so this may not
|
||||
forcibly require that you run Windows.</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Select the account that you wish to export.
|
||||
|
||||
<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
|
||||
the data from scratch.)</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Choose the menu <tt>File</tt> and select the <tt>
|
||||
Export...</tt> menu entry.
|
||||
|
||||
<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>
|
||||
|
||||
<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>
|
||||
</li>
|
||||
</ul>
|
||||
Now you have a set of <tt>.QIF</tt> files, and should run
|
||||
GnuCash.
|
||||
|
||||
<h2> Loading QIF files into GnuCash</h2>
|
||||
|
||||
<ul>
|
||||
<li>To import a Quicken QIF file, choose the menu <tt>
|
||||
File</tt> and select the entry <tt>Import QIF</tt>.</li>
|
||||
|
||||
<li>The imported file will be merged with whatever other data
|
||||
you currently have in GnuCash. The merge allows multiple
|
||||
Quicken accounts to be imported and merged into one account
|
||||
group.<br>
|
||||
<br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<h2> Things To Note About QIF Import</h2>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<b> Duplicate Entry Scanning</b>
|
||||
|
||||
<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>
|
||||
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
|
||||
scenario involving where you make multiple withdrawals of
|
||||
identical amounts from ATM machines on the same day.</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<b>Empty Accounts</b>
|
||||
|
||||
<p>Note that when the <tt>Accounts List</tt> and <tt>
|
||||
Category List</tt> is exported from Quicken, <b>all</b>
|
||||
accounts and categories will be exported, even if they are
|
||||
empty and contain no transactions. When these are imported,
|
||||
they will appear as accounts with a balance of zero. If you
|
||||
do not plan to use such accounts, feel free to delete them.
|
||||
Future enhancements may allow you to delete them "en
|
||||
masse," or to make them invisible without deleting
|
||||
them.</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<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>
|
||||
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
|
||||
of the most significant weaknesses with the present QIF
|
||||
import scheme.</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<b> More about QIF</b>
|
||||
|
||||
<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
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -1,99 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//IETF//DTD HTML//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Reconciliation Window</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1>Reconciliation Window</h1>
|
||||
|
||||
<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 statment. 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
|
||||
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
|
||||
should enter the transaction into GnuCash.</p>
|
||||
|
||||
<p> At the end of the month, you receive your bank statement,
|
||||
perhaps including cancelled 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
|
||||
enter the ending balance from the bank statement.</li>
|
||||
|
||||
<li>Then the reconcile window will pop-up, and you will see a
|
||||
credit and a debit column that lists all the non-reconciled
|
||||
transactions.<br>
|
||||
<br>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
Now, examine each item on the bank statement.
|
||||
|
||||
<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>leared.</p>
|
||||
|
||||
<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>
|
||||
</li>
|
||||
|
||||
<li>At the bottom of the window is a difference field, which
|
||||
should be $0.00 when you are done reconciling. If it isn't,
|
||||
then you have either missed transactions, or some amounts may
|
||||
be incorrect in GnuCash. (Or, probably rather less likely,
|
||||
the bank may have made an error.)<br>
|
||||
<br>
|
||||
</li>
|
||||
|
||||
<li>When you have completed marking off all the items on the
|
||||
bank statement, and when the difference heads to $0.00, you
|
||||
should press <tt>Ok</tt>, then the <tt>n</tt> or <tt>c</tt>
|
||||
in the transactions that were checked off will change to a
|
||||
<tt>y</tt>, indicating that they have been validated to agree
|
||||
between the bank statement and your own records.<br>
|
||||
<br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<p>When you change anything in a transaction that has been
|
||||
reconciled, a dialog box warning you that such changes are
|
||||
unwise should pop up, but this doesn't seem to happen
|
||||
anymore.</p>
|
||||
|
||||
<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
|
||||
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
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -1,148 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//IETF//DTD HTML//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Register Window</title>
|
||||
</head>
|
||||
|
||||
<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>
|
||||
|
||||
<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>
|
||||
<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>
|
||||
|
||||
<h1>Viewing Transactions</h1>
|
||||
|
||||
<p>The register can show transactions in a variety of different
|
||||
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>
|
||||
|
||||
<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>
|
||||
<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
|
||||
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=
|
||||
"xacc-recnwin.html">Reconcile Window</a></p>
|
||||
|
||||
|
||||
|
||||
<h1>Stock Portfolios</h1>
|
||||
|
||||
<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>
|
||||
<img src="foliowin-single.gif"></p>
|
||||
|
||||
<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
|
||||
create an account for each stock you wish to track.</p>
|
||||
|
||||
<p> Some important points to remember about the portfolio
|
||||
window:</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
It shows <em>all</em> stocks in your portfolio, not just
|
||||
one.
|
||||
|
||||
<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
|
||||
line, and credited amounts and accounts are on the lower
|
||||
line.</p>
|
||||
</li>
|
||||
|
||||
<li>If you buy or sell a stock with money from the brokerage
|
||||
account, the total balance will not change, since the value
|
||||
of the stock equals the amount of money exchanged.</li>
|
||||
|
||||
<li>If you buy or sell a stock with money from the brokerage
|
||||
account, the value of the transaction will appear twice, once
|
||||
in red, and once in black. If shares are purchased, the
|
||||
amount of money debited from the brokerage account will be in
|
||||
red, and the value of the shares in black. If shares are
|
||||
sold, then value of the shares is in red, and the money
|
||||
credited to the brokerage account in black.</li>
|
||||
|
||||
<li>If you are having trouble indicating a share
|
||||
purchase/sale in the portfolio ledger, then make sure that
|
||||
<b>Transfer From</b> and <b>Transfer To</b> accounts are in
|
||||
the right order. A transfer from a stock account is always
|
||||
interpreted as a sale, even if you entered the data as a
|
||||
purchase. The vice-versa is also true.</li>
|
||||
|
||||
<li>Eventually, an alternative simpler portfolio ledger
|
||||
window may be provided.</li>
|
||||
</ul>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -1,69 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//IETF//DTD HTML//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>Reports</title>
|
||||
</head>
|
||||
|
||||
<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>
|
||||
|
||||
<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>
|
||||
|
||||
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>.
|
||||
<hr>
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -1,219 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//w3c//dtd html 4.0 transitional//en">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<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=
|
||||
"gnucash.css">
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1>Stock Pricing and Ticker Symbols</h1>
|
||||
GnuCash provides a somewhat rudimentary automated stock quote
|
||||
gathering system.
|
||||
|
||||
<p>If a GnuCash <a href="xacc-acctypes.html#stockacct">stock
|
||||
account</a> is suitably configured, and the host computer is
|
||||
connected to the internet, the program <tt>gnc-prices</tt> may
|
||||
be used to load stock and mutual fund price quotes from various
|
||||
web sites directly into GnuCash.</p>
|
||||
|
||||
<p>To make use of this facility, the following must be
|
||||
done:</p>
|
||||
|
||||
<ul>
|
||||
<li>Create an account and mark it as being of type "Mutual
|
||||
Fund" or "Stock".</li>
|
||||
|
||||
<li>Enter a valid ticker symbol in the box marked
|
||||
"Security:"</li>
|
||||
|
||||
<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>
|
||||
and the <b>Vanguard Group</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 Peugot security in the
|
||||
Paris market).</li>
|
||||
</ul>
|
||||
|
||||
<table>
|
||||
<caption>
|
||||
Code list for European markets
|
||||
</caption>
|
||||
|
||||
<tr>
|
||||
<th>Code</th>
|
||||
|
||||
<th>Market</th>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>PA</td>
|
||||
|
||||
<td>Paris</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>BC</td>
|
||||
|
||||
<td>Barcelona</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>BE</td>
|
||||
|
||||
<td>Berlin</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>BI</td>
|
||||
|
||||
<td>Bilbao</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>BR</td>
|
||||
|
||||
<td>Brême</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>CO</td>
|
||||
|
||||
<td>Copenhagen</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>D</td>
|
||||
|
||||
<td>Dusseldorf</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>F</td>
|
||||
|
||||
<td>Frankfurt</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>H</td>
|
||||
|
||||
<td>Hambourg</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>HA</td>
|
||||
|
||||
<td>Hanover</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>L</td>
|
||||
|
||||
<td>London</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>MA</td>
|
||||
|
||||
<td>Madrid</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>MC</td>
|
||||
|
||||
<td>Madrid (M.C.)</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>MI</td>
|
||||
|
||||
<td>Milan</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>MU</td>
|
||||
|
||||
<td>Munich</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>O</td>
|
||||
|
||||
<td>Oslo</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>ST</td>
|
||||
|
||||
<td>Stockholm</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>SG</td>
|
||||
|
||||
<td>Stuttgart</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>VA</td>
|
||||
|
||||
<td>Valence</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>FX</td>
|
||||
|
||||
<td>Xetra</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<p>A sample image is shown below:<br>
|
||||
<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
|
||||
filename; for example:</p>
|
||||
<pre>
|
||||
gnc-prices myaccts.xac
|
||||
</pre>
|
||||
|
||||
<p>Running this command will print various diagnostic messages
|
||||
to the screen while it loads data. It will work only when the
|
||||
host computer is attached to the internet. It can function in
|
||||
conjunction with masquerading-style firewalls and proxy
|
||||
servers.</p>
|
||||
|
||||
<p>The command can be run many times in one day; however, it
|
||||
will update the accounts at most once with the most recent
|
||||
trading days price data.</p>
|
||||
|
||||
<p>Thus, if <tt>gnc-prices</tt> is run on Friday, Saturday,
|
||||
Sunday and Monday, only two price entires will be made: one
|
||||
containing Friday's data, and one containing Monday's data,
|
||||
since the Saturday and Sunday runs will only retrieve the
|
||||
Friday closing price.</p>
|
||||
|
||||
<p>To keep <tt>gnc-prices</tt> from updating one account, while
|
||||
allowing it to update another account, merely mark the data
|
||||
source for that account as <tt>(none)</tt>. You can do this
|
||||
from the <tt>Edit Account</tt> window.</p>
|
||||
|
||||
<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>
|
||||
<hr>
|
||||
|
||||
<p>Return to <a href="xacc-main.html">Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
@ -1,33 +0,0 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
||||
<html>
|
||||
<head>
|
||||
<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>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>
|
||||
<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>
|
||||
</ul>
|
||||
<hr>
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
@ -1,53 +0,0 @@
|
||||
<!DOCTYPE html PUBLIC "-//IETF//DTD HTML//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href=
|
||||
"gnucash.css">
|
||||
|
||||
<title>GnuCash Y2K Readiness</title>
|
||||
</head>
|
||||
|
||||
<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
|
||||
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> 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
|
||||
that time.</p>
|
||||
|
||||
<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,
|
||||
2000 as a "leap day," another of the "critical Y2K dates."</p>
|
||||
|
||||
<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
|
||||
2000.</a></p>
|
||||
<hr>
|
||||
|
||||
<p> Return to <a href="xacc-main.html"> Main Documentation
|
||||
Page.</a></p>
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -1,39 +0,0 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
|
||||
<META NAME="GENERATOR" CONTENT="Mozilla/4.06 [fr] (Win98; I) [Netscape]">
|
||||
<TITLE>Importation des fichiers MYM</TITLE>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href="gnucash.css">
|
||||
</HEAD>
|
||||
<BODY>
|
||||
|
||||
<H1>
|
||||
Managing Your Money --> GNUCash</H1>
|
||||
J'ai finallement produit le script Perl qui me permet d'utiliser GNUCash
|
||||
jusque sur un site web. J'ai deux années de données dans
|
||||
Managing Your Money 2.x que je ne veux pas réentrer. Le script sortira
|
||||
un simple fichier QIF avec toutes les transactions, comptes, et catégories.
|
||||
(Actuellement seulement les transactions de non-investissement sont traitées.)
|
||||
Le fichier QIF peut être importé vers xacc-1.0.18 si un petit
|
||||
patch est appliqué à QIFIO.c. Le site est:
|
||||
<P>http://www-cad.eecs.berkeley.edu/~gooch/mymdump.html
|
||||
<H1>
|
||||
Transactions dupliquées</H1>
|
||||
J'ai aussi un script que j'utilise pour enlever les transactions dupliquées
|
||||
au niveau du QIF. J'utilise ce script parce que Xacc est très strict
|
||||
à propos des duplications (ce qui est très bon) et parce
|
||||
qu'éditer des transactions importées causera une ré-importation
|
||||
des mêmes transactions qui produiront des doubles. (Je télécharge
|
||||
les transactions du même mois depuis ma banque plusieurs fois
|
||||
chaque mois, alors chaque fichier QIF téléchargé --après
|
||||
le premier--contient des transactions que j'ai déjà
|
||||
importé. Je ne veux pas compter sur ma banque pour m'envoyer les
|
||||
transactions dans le même ordre ou avec le même formatage.)
|
||||
Le site est
|
||||
<P>http://www-cad.eecs.berkeley.edu/~gooch/qifuniq.html
|
||||
<P>J'espère que les autres trouveront ces scripts facile à
|
||||
utiliser.
|
||||
<P>Ken Yamaguchi Octobre 1998
|
||||
</BODY>
|
||||
</HTML>
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 11 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 13 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 9.6 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 7.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 7.6 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 7.6 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 12 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 7.4 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 9.0 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 15 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 13 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 8.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 8.3 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 8.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 11 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 18 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 15 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 16 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 65 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 9.7 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 7.0 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 9.1 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 9.8 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 43 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 5.5 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 14 KiB |
File diff suppressed because it is too large
Load Diff
@ -1,7 +0,0 @@
|
||||
#!/bin/ksh
|
||||
# $ID$
|
||||
# If you have Dave Raggett's "tidy" utility, this will tidy up
|
||||
# the HTML files here.
|
||||
for i in *.html ; do
|
||||
tidy -m -i $i
|
||||
done
|
||||
@ -1,725 +0,0 @@
|
||||
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
|
||||
<meta name="GENERATOR" content="Mozilla/4.7 [fr] (Win98; I) [Netscape]">
|
||||
<title>A propos de Gnucash</title>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href="gnucash.css">
|
||||
<X-SAS-WINDOW TOP=25 BOTTOM=475 LEFT=4 RIGHT=534>
|
||||
</head>
|
||||
<body bgcolor="#EEEEEE">
|
||||
|
||||
<h1>
|
||||
A propos de GnuCash</h1>
|
||||
GnuCash est un programme de suivis de vos finances personnelles. Quelques
|
||||
une de ces fonctions sont :
|
||||
<ul>
|
||||
<li>
|
||||
<b>Des comptes multiples</b> , qui peuvent être ouverts en même
|
||||
temps. Créez un compte Gnucash pour chacun de vos comptes bancaires.</li>
|
||||
|
||||
<li>
|
||||
Chaque compte garde un solde actuel en plus d'un solde de rapprochement,
|
||||
alors vous pouvez suivre les transactions qui n'ont pas encore été
|
||||
pointés, comme les chèques en cours de règlement qui
|
||||
n'ont pas encore été débités de votre compte.</li>
|
||||
|
||||
<li>
|
||||
<b>Interface facile à utiliser</b>.</li>
|
||||
</ul>
|
||||
Si vous savez utiliser
|
||||
le talon de votre carnet de chèques , vous savez utiliser Gnucash.
|
||||
<ul>
|
||||
<li>
|
||||
<b><a href="xacc-recnwin.html">Rapprochement automatique du compte</a></b>.</li>
|
||||
</ul>
|
||||
A la fin du mois
|
||||
, ouvrez la fenêtre de <b>rapprochement</b> , entrez le solde final
|
||||
de votre relevé bancaire, et pointez les
|
||||
<br> transactions
|
||||
qui apparaissent sur le relevé bancaire. Celà permet de faire
|
||||
concorder ce que vous avez enregistré dans
|
||||
<br> GnuCash avec
|
||||
ce que votre vous a rendu-compte, celà rend facile le dépistage
|
||||
de n'importe quelle écart ou erreurs.
|
||||
<ul>
|
||||
<li>
|
||||
<b>QuickFill</b> (saisie rapide)...</li>
|
||||
</ul>
|
||||
Lorsque vous
|
||||
commencez une saisie dans les champs de description , s'il retrouve une
|
||||
précédente transaction, il vous
|
||||
<br> la propose,
|
||||
frappez <TAB> copiera alors la précédente transaction.
|
||||
Commode si vous avez des transactions
|
||||
<br> semblables
|
||||
assez régulierement .
|
||||
<ul>
|
||||
<li>
|
||||
<b>Portefeuille d'actions/de societes d'investissements</b> (n.d.t: pour
|
||||
ces dernieres FCP et SICAV en France).</li>
|
||||
</ul>
|
||||
Suivis d'actions
|
||||
individuellement (une par compte)ou dans un portefeuille de comptes (un
|
||||
groupe de comptes
|
||||
<br> qui peuvent
|
||||
etre affichés ensemble ).
|
||||
<br> Il ya
|
||||
des outils pour <a href="xacc-ticker.html">automatiser la collecte des
|
||||
cours des actions.</a>
|
||||
<ul>
|
||||
<li>
|
||||
Support pour de <b><a href="xacc-currency.html">multiples monnaies</a></b>
|
||||
et <b>comptes de<i> </i>marché des changes/devises</b> . (partiel,
|
||||
toujours défaillant)</li>
|
||||
</ul>
|
||||
Les comptes
|
||||
bancaires peuvent être établient dans différentes monnaies,
|
||||
et des ventes/achats à des taux d'échange
|
||||
<br> variables
|
||||
peuvent çetre fait ,comme les actions peuvent vendus/achetés
|
||||
à des prix variables.
|
||||
<ul>
|
||||
<li>
|
||||
<a href="xacc-quicken.html">Importation des fichiers de Quicken</a> .</li>
|
||||
</ul>
|
||||
Importation
|
||||
des fichiers QIF au format Quicken .
|
||||
<ul>
|
||||
<li>
|
||||
<a href="xacc-reports.html">Rapports</a>. Affiche ou produit en HTML les
|
||||
rapports du solde, transaction et pertes/profits, aussi bien qu'un
|
||||
suivi du solde du compte en graphique (requiert gnuplot)..</li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
Fonctions Avancées</h2>
|
||||
X-Accountant possède quelques une des fonctions qui ne se trouve
|
||||
pas habituellement dans un simple logiciel de gestion de finances personnelles:
|
||||
<ul>
|
||||
<li>
|
||||
<a href="xacc-groups.html">Une hiérarchie de compte</a></li>
|
||||
</ul>
|
||||
Un compte principal
|
||||
peut avoir un classement de petits comptes ou de comptes specialisés
|
||||
au-dessous de lui. Cela
|
||||
<br> permet d'avoir
|
||||
des types de comptes semblables (par exemple : Espèces, Banque,
|
||||
Actions) qui peuvent etre groupés
|
||||
<br> dans un compte
|
||||
principal (par exemple: Possessions ou Avoirs).
|
||||
<ul>
|
||||
<li>
|
||||
<a href="xacc-double.html">Double livret</a></li>
|
||||
</ul>
|
||||
Chaque transaction
|
||||
implique deux comptes, et <i>chaque transaction</i> est requise pour équilibrer.
|
||||
Celà donne l'assurance
|
||||
<br> que l'ensemble
|
||||
total des livres sera lié correctement, et prévient entièrement
|
||||
les erreurs de déséquilibre de soldes.
|
||||
<br> (Chaque
|
||||
transaction peut apparaitre dans deux comptes; un compte est debité
|
||||
et l'autre est credité avec exactement le
|
||||
<br> même
|
||||
montant. Avec le double livret , une transaction affichée dans une
|
||||
fenêtre sera automatiquement mise à jour dans
|
||||
<br> toutes
|
||||
les autres fenêtres montrant cette transaction, et dans les deux
|
||||
comptes.)
|
||||
<ul>
|
||||
<li>
|
||||
<a href="xacc-expense.html">Types de comptes revenus/dépenses (Catégories)</a>.</li>
|
||||
</ul>
|
||||
Le produit <a href="xacc-quicken.html">Quicken</a>
|
||||
d'Intuit a ce qu'ils appellent "catégories" qui sont utilisés
|
||||
pour suivre les revenus et dépenses.
|
||||
<br> Ils devraient
|
||||
être utilisés pour créer des rapports Profits/Pertes.
|
||||
<br> (Correctement
|
||||
utilisés avec la fonction du double livret, ils peuvent être
|
||||
utilisés pour créer un Bilan et un rapport des
|
||||
<br>
|
||||
Profits et des Pertes Par example, l'épargne des interets du compte,
|
||||
les dividendes d'actions, ou la feuille de paie
|
||||
<br>
|
||||
peuvent etre marqué l'un et l'autre comme depot dans un compte bancaire
|
||||
, et comme gains/revenus dans un compte
|
||||
<br>
|
||||
de type Revenus, utilisant la fonction du double livret (transfert). De
|
||||
la même manière, les paiements par la carte de
|
||||
<br>
|
||||
credit peuvent etre notés dans un compte de carte de crédit
|
||||
, en plus du compte correspondant aux dépenses.
|
||||
<ul>
|
||||
<li>
|
||||
<b>Registre general/Grand livre</b></li>
|
||||
</ul>
|
||||
Des comptes multiples
|
||||
peuvent être affichés dans une fenetre registre au même
|
||||
moment. Cela peut soulager de l'ennui
|
||||
<br> du depistage
|
||||
d'erreurs de saisie ou d'enregistrement .Il permet aussi une vision pratique
|
||||
d'un portefeuile de beaucoup
|
||||
<br> d'actions, en
|
||||
y montrant toutes les transactions dans ce portefeuille.
|
||||
<br>
|
||||
<ul>
|
||||
<li>
|
||||
<b>Traitement de <a href="xacc-currency.html">multiple monnaies/devises</a></b></li>
|
||||
</ul>
|
||||
|
||||
<h2>
|
||||
Version</h2>
|
||||
Le schéma de numérotage pour GnuCash est semblabe à
|
||||
celui du noyau Linux, où "même" les sous-versions indiquent
|
||||
des versions qui sont prévus pour être stable, seulement la
|
||||
vision de maintenance pour corriger les bugs, et les sous-versions "temporaire"
|
||||
indique un flux "experimental" qui poursuit le but d'ajout d'améliorations
|
||||
et d'extensions.
|
||||
<p>Le courant "experimental" actuel est gnucash-1.3.x, qui est en quelque
|
||||
sorte instable.
|
||||
<p>La dernière version stable est la 1.2.x; si vous n'avez pas l'intention
|
||||
de participer au travail de développement , vous ne devriez
|
||||
utiliser que cette version, ou une vieille version 1.0.x. Ces versions
|
||||
sont assez stable, avec tous les bugs couramment connus corrigés.
|
||||
<p>Une fois les séries 1.3.x stabilisées, les prochaines
|
||||
séries stables seront les 1.4.x, et l'expérimentation devrait
|
||||
probablement
|
||||
<br>continuer sur les 1.5.x.
|
||||
<p>Si tu es intéressé pour "hacker" sur la version expérimentale,tu
|
||||
devrais premièrement commencer par lire de bout en bout le document
|
||||
<a href="projects.html">GnuCash
|
||||
Project Goals(buts du projet Gnucash)</a> afin d'acquérir
|
||||
quelques perspectives sur la conception globale.
|
||||
<br>
|
||||
<h2>
|
||||
Développeurs principaux</h2>
|
||||
|
||||
<dl>
|
||||
<dt>
|
||||
<a href="mailto:rclark@hmc.edu">Robin Clark</a></dt>
|
||||
|
||||
<dd>
|
||||
a écrit le X-Accountant originel en Motif comme un projet scolaire,
|
||||
l'amenant jusqu'à la version 0.9 en Octobre 1997.</dd>
|
||||
|
||||
<dt>
|
||||
<a href="mailto:linas@linas.org">Linas Vepstas</a></dt>
|
||||
|
||||
<dd>
|
||||
comme il le dit: le GUI était léger, le code était
|
||||
documenté et bien structuré, et il était entièrement
|
||||
sous GPL. Et aussi il le ré-écrit : ajoutant des widgets
|
||||
de cellules avec XbaeMatrix, alors que les combobox et flèches devaient
|
||||
faire de nouveau une même GUI légère, réécrivant
|
||||
le code interne de X-Accountant pour lui ajouter la double-entrée,
|
||||
une hiérarchie de comptes, l'augmenta d'un mini moteur de transaction,
|
||||
ajouta le support pour les actions, et ajouta les menus d'aide. C'était
|
||||
la version 1.0 de Janvier 1998. Depuis lors, pour la version 1.1, le moteur
|
||||
fut étandu et redéfini , et le code de la fenêtre d'enregistrement
|
||||
fut completement reconçu et fait pour la plupart en Motif et independent
|
||||
du GUI. Présentant un certain prototype de OFX fonctionnant.</dd>
|
||||
|
||||
<dt>
|
||||
<a href="mailto:jcollins@gnucash.org">Jeremy Collins</a></dt>
|
||||
|
||||
<dd>
|
||||
fit connaitre au public largement et grandement le projet GnoMoney, et
|
||||
alors changea son nom en GnuCash. Jeremy créa le site web de gnucash.org,
|
||||
enregistra le domaine, fit fonctionner le code initial en GTK/gnome.</dd>
|
||||
|
||||
<dt>
|
||||
<a href="mailto:rlb@cs.utexas.edu">Rob Browning</a></dt>
|
||||
|
||||
<dd>
|
||||
abusa tout le monde pour ne pas utiliser perl, et alors ajouta le support
|
||||
guile/scheme. Rob maintient l'infrastructure de construction, traite de
|
||||
toute chose qui touche au langage d'extension guile/perl, et traite de
|
||||
configuration et configurabilité.</dd>
|
||||
|
||||
<dt>
|
||||
<a href="mailto:schoenberger@signsoft.com">Dirk Schoenberger</a></dt>
|
||||
|
||||
<br> travaillle sur
|
||||
le portage en Qt/KDE
|
||||
<br>
|
||||
<dt>
|
||||
<a href="mailto:peticola@cs.ucdavis.edu">Dave Peticolas</a></dt>
|
||||
|
||||
<br> travaille d'une
|
||||
manière obsédante sur GnuCash. Mais il peut s'arrêter
|
||||
à tout moment s'il le veut . Vraiment.
|
||||
<p><a href="mailto:y-le-ny@ifrance.com">Yannick Le Ny</a>
|
||||
<br> Localise
|
||||
(traduction et adaptation) de Xacc et Gnucash pour la France et les pays
|
||||
francophones.
|
||||
<br> Travail
|
||||
effectué :traduction du Readme, des messages et de l'aide en ligne
|
||||
de Gnucash en français
|
||||
<br> A finis
|
||||
de traduire tout le site web de Gnucash en français sauf la liste
|
||||
de courriers et le maintient à jour</dl>
|
||||
|
||||
<h2>
|
||||
Correctifs et patches</h2>
|
||||
L<i>' équipe des milliers</i> inclut:
|
||||
<br>
|
||||
<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 Armstrong</a></dt>
|
||||
|
||||
<dd>
|
||||
for misc fixes</dd>
|
||||
|
||||
<dt>
|
||||
<a href="mailto:fred@moremagic.com">Fred Baube</a></dt>
|
||||
|
||||
<dd>
|
||||
for attempted Java port/MoneyDance</dd>
|
||||
|
||||
<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</dd>
|
||||
|
||||
<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>
|
||||
|
||||
<dd>
|
||||
for MS-Money QIF support</dd>
|
||||
|
||||
<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 Collins</a></dt>
|
||||
|
||||
<dd>
|
||||
for GnoMoney and GTK port</dd>
|
||||
|
||||
<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 Deignan</a></dt>
|
||||
|
||||
<dd>
|
||||
for AIX binary version</dd>
|
||||
|
||||
<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>
|
||||
|
||||
<dd>
|
||||
for Solaris patches to XmHTML</dd>
|
||||
|
||||
<dt>
|
||||
<a href="mailto:bob@mostly.com">Bob Drzyzgula</a></dt>
|
||||
|
||||
<dd>
|
||||
for budgeting design notes</dd>
|
||||
|
||||
<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>
|
||||
|
||||
<dd>
|
||||
for gnome patches</dd>
|
||||
|
||||
<dt>
|
||||
<a href="mailto:DFreese@osc.uscg.mil">Dave Freese</a></dt>
|
||||
|
||||
<dd>
|
||||
for leap-year fix</dd>
|
||||
|
||||
<dt>
|
||||
<a href="mailto:otto@bug.redhat.com">Otto Hammersmith</a></dt>
|
||||
|
||||
<dd>
|
||||
for RedHat RPM packaging</dd>
|
||||
|
||||
<dt>
|
||||
<a href="mailto:haral@codec.ro">Alexandru Harsanyi</a></dt>
|
||||
|
||||
<dd>
|
||||
for fixing miscellaneous core dumps and lockups.</dd>
|
||||
|
||||
<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 Kailasa</a></dt>
|
||||
|
||||
<dd>
|
||||
for gnome build fixes</dd>
|
||||
|
||||
<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>
|
||||
|
||||
<dd>
|
||||
for SuSE README file</dd>
|
||||
|
||||
<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 Ny</a></dt>
|
||||
|
||||
<dd>
|
||||
pour la traduction en francais</dd>
|
||||
|
||||
<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 Martin</a></dt>
|
||||
|
||||
<dd>
|
||||
gnome and register patches</dd>
|
||||
|
||||
<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 Merkel</a></dt>
|
||||
|
||||
<dd>
|
||||
reporting, gnome, and configuration patches.</dd>
|
||||
|
||||
<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 III</a></dt>
|
||||
|
||||
<dd>
|
||||
for QIF core dump fix</dd>
|
||||
|
||||
<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">OmNiBuS</a></dt>
|
||||
|
||||
<dd>
|
||||
web site graphics and content</dd>
|
||||
|
||||
<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 P{'e}lecq</a></dt>
|
||||
|
||||
<dd>
|
||||
i18n patches with gettext</dd>
|
||||
|
||||
<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 Pointner</a></dt>
|
||||
|
||||
<dd>
|
||||
motif and configuration patches</dd>
|
||||
|
||||
<dt>
|
||||
<a href="mailto:maufk@csv.warwick.ac.uk">Gavin Porter</a></dt>
|
||||
|
||||
<dd>
|
||||
for euro style dates</dd>
|
||||
|
||||
<dt>
|
||||
<a href="mailto:rr@sco.com">Ron Record</a></dt>
|
||||
|
||||
<dd>
|
||||
for SCO Unixware and OpenServer binaries</dd>
|
||||
|
||||
<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 Seawood</a></dt>
|
||||
|
||||
<dd>
|
||||
for XbaeMatrix core dump</dd>
|
||||
|
||||
<dt>
|
||||
<a href="mailto:msimons@fsimons01.erols.com">Mike Simons</a></dt>
|
||||
|
||||
<dd>
|
||||
misc <tt>configure.in</tt> patches</dd>
|
||||
|
||||
<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 Spruth</a></dt>
|
||||
|
||||
<dd>
|
||||
for German text and euro date rework</dd>
|
||||
|
||||
<dt>
|
||||
<a href="mailto:detrout@earthlink.net">Diane Trout</a></dt>
|
||||
|
||||
<dd>
|
||||
scheme qif import patch</dd>
|
||||
|
||||
<dt>
|
||||
<a href="mailto:rob@valinux.com">Rob Walker</a></dt>
|
||||
|
||||
<dd>
|
||||
guile and register patches</dd>
|
||||
|
||||
<dt>
|
||||
<a href="mailto:gooch@ic.EECS.Berkeley.EDU">Ken Yamaguchi</a></dt>
|
||||
|
||||
<br>QIF import fixes; MYM import
|
||||
<br>
|
||||
<h2>
|
||||
Systèmes d'exploitation supportés</h2>
|
||||
gnucash-1.0.18 (ex xacc-1.0.18) est conu pour fonctioner dans ces différentes
|
||||
configurations:
|
||||
<br>Linux 2.0.x -- Intel w/ RedHat Motif
|
||||
<br>Linux 2.0.x -- Intel w/ Lesstif v0.81
|
||||
<br>Linux Debian -- Intel w/ Lesstif v0.81
|
||||
<br>SGI IRIX -- MIPS
|
||||
<br>IBM AIX 4.1.5 -- RS/6000
|
||||
<br>SCO Unixware 7 -- Intel
|
||||
<br>SCO OpenServer 5.0.4 -- Intel
|
||||
<br>NetBSD -- Intel
|
||||
<br>
|
||||
<p><a href="http://www.gnucash.org/"><img SRC="../LOGOS/Linux.gif" NOSAVE height=102 width=121></a><a href="http://www.sco.com/skunkware"><img SRC="../LOGOS/skunkware.gif" NOSAVE height=80 width=108></a><a href="http://www.bull.de/pub/"><img SRC="../LOGOS/bullogogross.gif" NOSAVE height=75 width=75></a><a href="http://www.bull.de/pub/"><img SRC="../LOGOS/Ibm.gif" NOSAVE height=54 width=93></a><a href="http://www.sgi.com/"><img SRC="../LOGOS/Sgi.gif" NOSAVE height=43 width=151></a><a href="http://www.debian.org/"><img SRC="../LOGOS/Debian.jpg" NOSAVE height=140 width=114></a><img SRC="../LOGOS/NetBSD-banner.gif" NOSAVE height=44 width=98>
|
||||
<h2>
|
||||
Historique</h2>
|
||||
Le tableau ci-dessous montre quelques historiques de lignes de code et
|
||||
le nombre de fichiers comptés pour le dévelopement du projet
|
||||
X-Accountant/GnuCash
|
||||
<table BORDER >
|
||||
<caption>Statistiques de l'historique du dévelopement</caption>
|
||||
|
||||
<tr ALIGN=CENTER>
|
||||
<th>Version </th>
|
||||
|
||||
<th>moteur </th>
|
||||
|
||||
<th>registre </th>
|
||||
|
||||
<th>grand livre </th>
|
||||
|
||||
<th>motif </th>
|
||||
|
||||
<th>prefs (scm) </th>
|
||||
|
||||
<th>docs (html) </th>
|
||||
|
||||
<th>divers </th>
|
||||
|
||||
<th>Total </th>
|
||||
</tr>
|
||||
|
||||
<tr ALIGN=CENTER>
|
||||
<td>xacc-0.9
|
||||
<br>Sept 97 </td>
|
||||
|
||||
<td>- </td>
|
||||
|
||||
<td>- </td>
|
||||
|
||||
<td>- </td>
|
||||
|
||||
<td>34 fichiers
|
||||
<br>(7.5+0.9) </td>
|
||||
|
||||
<td>- </td>
|
||||
|
||||
<td>5 fichiers
|
||||
<br>(0.4) </td>
|
||||
|
||||
<td>- </td>
|
||||
|
||||
<td>39 fichiers
|
||||
<br>(8.8) </td>
|
||||
</tr>
|
||||
|
||||
<tr ALIGN=CENTER>
|
||||
<td>xacc-0.9w
|
||||
<br>Dec 97 </td>
|
||||
|
||||
<td>- </td>
|
||||
|
||||
<td>- </td>
|
||||
|
||||
<td>- </td>
|
||||
|
||||
<td>51 fichiers
|
||||
<br>(13.8+1.5) </td>
|
||||
|
||||
<td>- </td>
|
||||
|
||||
<td>9 fichiers
|
||||
<br>(0.8) </td>
|
||||
|
||||
<td>- </td>
|
||||
|
||||
<td>60 fichiers
|
||||
<br>(16.1) </td>
|
||||
</tr>
|
||||
|
||||
<tr ALIGN=CENTER>
|
||||
<td>xacc-1.0.17
|
||||
<br>Fev 98</td>
|
||||
|
||||
<td>- </td>
|
||||
|
||||
<td>- </td>
|
||||
|
||||
<td>- </td>
|
||||
|
||||
<td>52 files
|
||||
<br>(14.8+1.8) </td>
|
||||
|
||||
<td>- </td>
|
||||
|
||||
<td>12 files
|
||||
<br>(1.4) </td>
|
||||
|
||||
<td>- </td>
|
||||
|
||||
<td>64 files
|
||||
<br>(18.0) </td>
|
||||
</tr>
|
||||
|
||||
<tr ALIGN=CENTER>
|
||||
<td>gnucash-1.1.15
|
||||
<br>Aou 98 </td>
|
||||
|
||||
<td>24 fichiers
|
||||
<br>(6.2+1.5) </td>
|
||||
|
||||
<td>31 fichiers
|
||||
<br>(6.1+1.7) </td>
|
||||
|
||||
<td>5 fichiers
|
||||
<br>(1.4+0.4) </td>
|
||||
|
||||
<td>30 fichiers
|
||||
<br>(7.4+0.7) </td>
|
||||
|
||||
<td>3 fichiers
|
||||
<br>(0.3) </td>
|
||||
|
||||
<td>16 fichiers
|
||||
<br>(1.9) </td>
|
||||
|
||||
<td>non compté
|
||||
<br>(>1.0) </td>
|
||||
|
||||
<td>109 fichiers
|
||||
<br>(32.9) </td>
|
||||
</tr>
|
||||
|
||||
<tr ALIGN=CENTER>
|
||||
<td>gnucash-1.2.2
|
||||
<br>Aou 99 </td>
|
||||
|
||||
<td>41 fichiers
|
||||
<br>(10.2+3.6) </td>
|
||||
|
||||
<td>28 fichiers
|
||||
<br>(5.5+1.7) </td>
|
||||
|
||||
<td>14 fichiers
|
||||
<br>(2.4+0.6) </td>
|
||||
|
||||
<td>26 fichiers
|
||||
<br>(8.7+0.5) </td>
|
||||
|
||||
<td>14 fichiers
|
||||
<br>(1.4) </td>
|
||||
|
||||
<td>30 fichiers
|
||||
<br>(2.6) </td>
|
||||
|
||||
<td>non compté
|
||||
<br>(>1.0) </td>
|
||||
|
||||
<td>153 fichiers
|
||||
<br>(37.2) </td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<p>Chaque cellule contient:
|
||||
<p>nombre de fichiers *c et *.h
|
||||
<br>(KLOCS dans *.c + KLOCS dans *.h),
|
||||
<p>où KLOC == kilo-lignes-de-code, comme rapported par <tt>wc</tt>.
|
||||
<p>
|
||||
<hr WIDTH="100%">
|
||||
<br>Retour à la <a href="xacc-main.html">Page principale de la documentation.</a>
|
||||
</body>
|
||||
</html>
|
||||
@ -1,34 +0,0 @@
|
||||
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
|
||||
<meta name="GENERATOR" content="Mozilla/4.7 [fr] (Win98; I) [Netscape]">
|
||||
<title>Edition des paramètres du compte</title>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href="gnucash.css">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<h1>
|
||||
Modification des paramètres du compte</h1>
|
||||
La boîte de dialogue "Modification du compte" vous permet de changer
|
||||
les propriétés d'un compte. Vous pouvez accéder à
|
||||
celle-ci via le bouton "Modifier" de la barre d'outils de la fenêtre
|
||||
principale, le menu "Comptes" , ou via les raccourcis clavier. Pour une
|
||||
description des utilisations des différentes propriétées,
|
||||
regardez l'information à propos de <a href="xacc-accwin.html">nouveau
|
||||
comptes</a>.
|
||||
<p><b>L'Information du compte </b>peut être changée en tapant
|
||||
dans le champ approprié. Le type de compte ne peut pas être
|
||||
changé.
|
||||
<p>Un nouveau <b>Compte parent </b>peut être sélectionné.Seulement
|
||||
ceux de ces comptes qui peuvent légalement devenir le parent du
|
||||
compte actuel sont montrés.
|
||||
<p>La source pour le <b>Cours des actions</b> peut être sélectionné.
|
||||
<i>FIXME: Pourrait-il y avoir quelqu'un qui utilise cette fonction la documente,s'il
|
||||
vous plait ?</i>>
|
||||
<p><b>Les notes</b> à propos du comptes peuvent être modifiées.
|
||||
<br>
|
||||
<hr>
|
||||
<p>Retour à la <a href="xacc-main.html">Page principale de la documentation.</a>
|
||||
</body>
|
||||
</html>
|
||||
@ -1,225 +0,0 @@
|
||||
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
|
||||
<meta name="GENERATOR" content="Mozilla/4.7 [fr] (Win98; I) [Netscape]">
|
||||
<title>Types de comptes</title>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href="gnucash.css">
|
||||
</head>
|
||||
<body bgcolor="#EEEEEE">
|
||||
|
||||
<h1>
|
||||
Types de comptes</h1>
|
||||
|
||||
<dl>
|
||||
<dt>
|
||||
<b>Liquidités</b></dt>
|
||||
|
||||
<dt>
|
||||
Le type de
|
||||
compte <b>liquidités</b> est utilisé pour contenir l'argent
|
||||
que vous stockez dans votre porte-monnaie, une boite</dt>
|
||||
|
||||
<dt>
|
||||
à chaussures
|
||||
, tirelire ou matelas .</dt>
|
||||
|
||||
<dt>
|
||||
<b>Banque</b></dt>
|
||||
|
||||
<dd>
|
||||
Le type de compte <b>banque</b> contient l'épargne ou le compte
|
||||
chèques détenu dans une banque. Ces comptes sont parfois</dd>
|
||||
|
||||
<dd>
|
||||
rémunéré (n.d.t : pas en france).</dd>
|
||||
|
||||
<dt>
|
||||
<b>Carte de crédit</b></dt>
|
||||
|
||||
<dd>
|
||||
Le compte <b>carte de crédit</b> est utilisé pour contenir
|
||||
des comptes de carte de credit (par exemple american express) et debit
|
||||
(par exemple visa, eurocard/mastercard, carte bleue).Si bien qu'il nécessite
|
||||
des lignes flottante de crédit comme avec VISA, MasterCard/Eurocard
|
||||
, ou Discover( aux USA pour ce dernier), ausssi bien que les autres comme
|
||||
American Express qui ne vous permettent pas de maintenir des soldes
|
||||
prolongés.En france, on peut utiliser ce compte uniquement avec
|
||||
des cartes bancaires à débit différé et pour
|
||||
certains rares posesseurs de cartes American Express.</dd>
|
||||
|
||||
<dd>
|
||||
(n.d.t: ce qui suit ne concerne que les U.S.A)</dd>
|
||||
|
||||
<dd>
|
||||
L'introduction des <a href="http://www.visa.com/pd/debit/checkcard.html">Check
|
||||
Cards</a> où les paiements sont débités (withdrawn)
|
||||
directement depuis un compte chèques rend la sélection moins
|
||||
claire; il est probablement plus approprier de traiter un "Check Card"
|
||||
( carte chèque) comme un compte <b>banque</b>, comme il débite
|
||||
les montants directement depuis de tel compte, ne nécessite pas
|
||||
réellement aucune garantie de crédit.</dd>
|
||||
|
||||
<dt>
|
||||
<b>Avoir, Dette</b></dt>
|
||||
|
||||
<dd>
|
||||
Les comptes <b>avoir</b> et <b>dette</b> indiquent des comptes généralisés,
|
||||
génériques qui ne sont dans aucun de ceux ci-dessus.</dd>
|
||||
|
||||
<dd>
|
||||
Les comptes <b>avoir</b> et <b>dette</b> sont utilisés pour le suivi
|
||||
de choses qui ont de la valeur, mais qui ne sont pas comme ça</dd>
|
||||
|
||||
<dd>
|
||||
directement transposable en <i>espèces/argent comptant</i>
|
||||
.</dd>
|
||||
|
||||
<dd>
|
||||
Par exemple, vous devriez rassembler les coùts d'achat d'une maison
|
||||
dans un compte avoir intitulé <b>Ma maison,</b> ou le coùt
|
||||
d'une voiture dans <b>Ma voiture,</b> ou rassembler ensemble la valeur
|
||||
de votre <b>Equipement Informatique.</b></dd>
|
||||
|
||||
<dd>
|
||||
Et l'hypothèque de la maison ou l'emprunt de la voiture devraient
|
||||
être représentés par des comptes dettes, <b>Hypothèque
|
||||
de la maison </b> et l' <b>Emprunt de la voiture</b>, et être
|
||||
vu (drawn down) comme des paiements qui sont faits sur/pour ces emprunts.</dd>
|
||||
|
||||
<dd>
|
||||
Si vous possédez des avoirs à buts commerciaux/professionnels,
|
||||
leur déclin en valeur dans le temps devrait être traité
|
||||
comme une déduction pour des buts fiscaux, cette déduction
|
||||
est appelée <a href="xacc-apprdepr.html#depr">Dépréciation.</a></dd>
|
||||
|
||||
<dd>
|
||||
D'un autre côté, si vous possédez des avoirs qui s'<i>apprécient
|
||||
</i>en
|
||||
valeur avec le temps, tel que des biens immobiliers,</dd>
|
||||
|
||||
<dd>
|
||||
des collections comme des tableaux de peinture, et des investissements
|
||||
comme des actions dans des sociétés, vous devrez les voir
|
||||
s'apprécier en valeur, aet être forcé de reconnaitre,
|
||||
en vue d'impots, ce qui est appelé <a href="xacc-apprdepr.html#appr">Gains
|
||||
en capital ou Plus-values.</a></dd>
|
||||
|
||||
<dt>
|
||||
<b>Actions, OPCVM (SICAV et FCP)</b></dt>
|
||||
|
||||
<dd>
|
||||
Les comptes d'actions et OPCVM seront typiquement montrés dans des
|
||||
registres qui montreront trois colonnes: cours, nombre de titres, et montant.</dd>
|
||||
|
||||
<dd>
|
||||
Les valeurs/titres dans lesquels vous investissez sont une forme d'avoirs
|
||||
qui sont normallement acquis avec le but express</dd>
|
||||
|
||||
<dd>
|
||||
de recevoir des revenus soit dans l'une ou l'autre forme de dividendes,
|
||||
intérêts, ou <a href="xacc-apprdepr.html#appr">Gains en Capital
|
||||
ou Plus-values.</a> Il y a une multitude de marchés de valeurs dans
|
||||
le monde, et les valeurs qui sont assez largement échangées
|
||||
peuvent avoir de jolies valeurs concrètes qui peuvent être
|
||||
analysées sur une base de jour-à-jour.</dd>
|
||||
|
||||
<dd>
|
||||
Les comptes Actions et OPCVM sont typiquement suivis dans des registres
|
||||
qui ont trois colonnes principales:</dd>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
Cours</li>
|
||||
|
||||
<li>
|
||||
Nombre de titres</li>
|
||||
|
||||
<li>
|
||||
Montant</li>
|
||||
</ul>
|
||||
|
||||
<dd>
|
||||
Afin d'obtenir de l'information <i>utile</i> information en dehors du registre,
|
||||
il est nécessaire d'avoir de multiples "vues" sur les données
|
||||
de tel façon à ce que vous puissiez évaluer de telles
|
||||
choses comme:</dd>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
Valeur totale par valeur</li>
|
||||
|
||||
<li>
|
||||
Gains/Pertes par valeur</li>
|
||||
|
||||
<li>
|
||||
Taux de Retour Sur Investissement par valeur</li>
|
||||
</ul>
|
||||
|
||||
<dd>
|
||||
Plus de détails peuvent être trouvé dans la section
|
||||
<a href="xacc-ticker.html">Stock
|
||||
Ticker</a> .</dd>
|
||||
|
||||
<dt>
|
||||
<b><a href="xacc-expense.html">Revenus, Dépenses</a></b></dt>
|
||||
|
||||
<dd>
|
||||
Les comptes de <b>revenus</b> et <b>dépenses</b> sont utilisés
|
||||
pour contenir les revenus et dépenses. Ainsi, quand les données
|
||||
dans ces comptes sont affichées, le signe des entrées est
|
||||
inversé par rapport à l'usage habituel.</dd>
|
||||
|
||||
<dt>
|
||||
<b>Capitaux propres</b></dt>
|
||||
|
||||
<dd>
|
||||
Le compte capitaux propres est utilisé pour équilibrer la
|
||||
feuille du bilan, indiquant la portion de la valeur "collective"</dd>
|
||||
|
||||
<dd>
|
||||
représentant <i>le montant net que les propriétaires possèdent.</i></dd>
|
||||
|
||||
<dd>
|
||||
Sur une base d'année-par-année, une valeur calculée
|
||||
appelée <b>Reste de profits</b> indique la valeur nette de l'entreprise;</dd>
|
||||
|
||||
<dd>
|
||||
il est générallement considéré comme étant
|
||||
une bonne chose quand cette valeur augmente.</dd>
|
||||
|
||||
<dt>
|
||||
<b><a href="xacc-currency.html">Devises</a></b></dt>
|
||||
|
||||
<dd>
|
||||
Les <b>comptes de devises</b> sont utilisés pour faire du commerce/spéculer
|
||||
sur les devises.</dd>
|
||||
|
||||
<dd>
|
||||
Dans beaucoup de cas, ils se comportent comme les actions, (excepter que
|
||||
le calcul de la valeur est différent)</dd>
|
||||
|
||||
<dd>
|
||||
et que la seule voie qui permette d'avoir des "revenus" à partir
|
||||
d'elles est celle à partir des fluctuations dans les valeurs relatives
|
||||
des devises/monnaies.Noter que les transferts ne peuvent pas être
|
||||
fait directement entre deux comptes libellés dans des monnaies/devises
|
||||
différentes. De tel transferts ne peuvent être seulement fait
|
||||
qu'à l'intérieur de comptes de commerce de devises.</dd>
|
||||
|
||||
<dd>
|
||||
</dd>
|
||||
|
||||
<dd>
|
||||
|
||||
<hr></dd>
|
||||
|
||||
<dd>
|
||||
</dd>
|
||||
|
||||
<dd>
|
||||
Retour à la <a href="xacc-main.html">Page principale de la documentation.</a></dd>
|
||||
</dl>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@ -1,41 +0,0 @@
|
||||
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
|
||||
<meta name="GENERATOR" content="Mozilla/4.7 [fr] (Win98; I) [Netscape]">
|
||||
<title>Fenêtre nouveau compte</title>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href="gnucash.css">
|
||||
<X-SAS-WINDOW TOP=0 BOTTOM=481 LEFT=0 RIGHT=786>
|
||||
</head>
|
||||
<body bgcolor="#EEEEEE">
|
||||
|
||||
<h1>
|
||||
Fenêtre Nouveau Compte</h1>
|
||||
|
||||
<p><br>Ci-dessous se trouve à quoi ressemble une fenêtre nouveau
|
||||
compte :
|
||||
<br>
|
||||
<p><img SRC="newaccwin-code.gif" NOSAVE height=550 width=494>
|
||||
<br>
|
||||
<p>Choisissez un <b><a href="xacc-acctypes.html">Type de compte</a></b>.
|
||||
<p>Le champ <b>Monnaie</b> devrait être typiquement un <a href="xacc-currency.html#ISOCURR">code
|
||||
monétaire ISO à trois lettres ISO</a> (par exemple <tt>USD</tt>
|
||||
pour les dollars US). Le <b>code du compte </b>est un numéro qui
|
||||
détermine l' <a href="xacc-groups.html#SORTORDER">ordre de tri</a>
|
||||
pour le compte quand il apparait dans un rapport ou dans le <b><a href="xacc-groups.html">Tableau
|
||||
de comptes</a></b>.
|
||||
<p>L'image ci-dessus montre un exemple pour un compte d'actions ou de d'achat/ventes
|
||||
de monnaies/devises. Noter que le champ valeur n'est pas grisé,
|
||||
et que vous pouvez entrer une valeur. Cette valeur est typiquement un <a href="xacc-ticker.html">code
|
||||
de valeur d'une action</a>, ou un <a href="xacc-currency.html#ISOCURR" ISOCURR>code
|
||||
monétaire à trois lettres ISO</a>.
|
||||
<br>
|
||||
<p><img SRC="newaccwin-trade.gif" NOSAVE height=550 width=494>
|
||||
<p>
|
||||
<hr WIDTH="100%">
|
||||
<p>Retour à la <a href="xacc-main.html">Page principale de la documentation.</a>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
</body>
|
||||
</html>
|
||||
@ -1,21 +0,0 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>Fenêtre d'ajustement du solde</TITLE>
|
||||
<META NAME=GENERATOR CONTENT="Claris Home Page 2.0">
|
||||
<X-SAS-WINDOW TOP=25 BOTTOM=475 LEFT=4 RIGHT=534>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href="gnucash.css">
|
||||
</HEAD>
|
||||
<BODY BGCOLOR="#EEEEEE">
|
||||
|
||||
<H1>CE FICHIER EST VIDE</H1>
|
||||
|
||||
<P>Fenêtre d'ajustement du solde. Utiliser la pour ajuster le
|
||||
solde. Entrez le montant en francs , et une entrée dans le
|
||||
registre sera créée qui mettra le solde courant
|
||||
équivalent à ce nouveau solde. Ajouter plus de
|
||||
documentation ici.
|
||||
<HR>
|
||||
</P>
|
||||
</BODY>
|
||||
</HTML>
|
||||
@ -1,188 +0,0 @@
|
||||
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
|
||||
<meta name="GENERATOR" content="Mozilla/4.7 [fr] (Win98; I) [Netscape]">
|
||||
<link rel="stylesheet" title="normal" type="text/css" href="gnucash.css">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<h1>
|
||||
Dettes (dus aux) fournisseurs et crédits ( à recevevoir des)
|
||||
fournisseurs</h1>
|
||||
Dettes (D/F)(dettes dus aux fournisseurs) et crédit (C/F) (crédit
|
||||
à recevoir des fournisseurs) sont en quelque sorte complexe, et
|
||||
requiert de la réflexion pour bien les comprendre.
|
||||
<h1>
|
||||
<font size=+3>Crédits fournisseurs</font></h1>
|
||||
|
||||
<p><br>En tous cas, considérons Crédits fournisseurs. Après
|
||||
tout, nous ne devrions à vrai dire <i>avoir besoin</i> de rien raconter
|
||||
sur les D/F parce que nous payons toujours <i>nos</i> factures à
|
||||
temps, n'est ce pas ? :-)
|
||||
<p>Aussi comme première considération, allons et supposons
|
||||
que nous ne demandons pas aux clients de payer <i>instantanément,</i>
|
||||
en liquide, mais plutôt envoyons leur une facture, et donnons leur
|
||||
30 jours pour payer les factures. (Après 30 jours, nous pouvons
|
||||
commencer à faire payer des intérêts et leur envoyer
|
||||
des lettres de harcèlement :-)).
|
||||
<p>Quand nous faisons une vente, les deux comptes affectés sont
|
||||
les <b>Ventes</b> (un compte revenus) et <b>Crédit fournisseurs</b>.
|
||||
Crédit fournisseurs est un avoir, mais il n'est pas liquide, comme
|
||||
vous ne pouvez pas volontairement le vendre, et il n'est pas forcément
|
||||
en espèces/argent comptant.
|
||||
<p>Alors quand ils réusissent à payer leurs factures, déposant
|
||||
un gros sac de vingt dollars de factures,(ou, plus probablement, un chèque)
|
||||
nous transférons le montant depuis Crédit fournisseurs vers
|
||||
Liquidités.
|
||||
<p>La raison pour laquelle nous le faisons en deux étapes est que
|
||||
nous avons decidés de faire notre comptabilité sur une base
|
||||
d'accumulation et non sur une base de liquidités, parce que la plupart
|
||||
de nos transactions ne sont pas seulement basées sur un changement
|
||||
de main de liquidités, mais plutôt basé sur l'<i>établisement
|
||||
d'obligations, </i>ce sont des engagements.
|
||||
<p>Dans des opérations plus sophistiqués, il peut y avoir
|
||||
une plus large séquence de documents générés
|
||||
et suivis:
|
||||
<ul>
|
||||
<li>
|
||||
Un client envoie un <b>Ordre d'achat</b>, ainsi il autorise un achat.</li>
|
||||
|
||||
<li>
|
||||
Nous créons un <b>Ordre de travail</b> pour planifier la production
|
||||
de tout ce qu'un client achète</li>
|
||||
|
||||
<li>
|
||||
Nous créons un <b>Avis d'expédition</b>, pour expédier
|
||||
les biens au client</li>
|
||||
|
||||
<li>
|
||||
Une fois expédié, nous émettons une <b>Facture</b>,
|
||||
représentant la <i>demande à payer</i></li>
|
||||
</ul>
|
||||
Nous reportons les ventes dans nos chiffres de ventes au moment où
|
||||
nous les faisons.Malheureusement, nous devons terminer
|
||||
<br>de vendre certains produits à des opérateurs douteux
|
||||
qui n'en valent pas la peine et que nous ne savons pas qu'ils sont douteux,
|
||||
et ainsi resté coincé avec quelques "dettes perdues."
|
||||
<p>Afin de determiner quelles parts de Crédit fournisseurs apparait
|
||||
être à plus de risque, il est typique d'arranger les Crédits
|
||||
fournisseurs basé sur les "ages" des débits, généralement
|
||||
en le segmentant en plusieurs periodes d'ages différents, de paiements
|
||||
qui sont en cours de règlement de 0-30 jours, ceux qui sont en cours
|
||||
de règlement de 31-60 jours, puis 61-90 jours, et ensuite ceux qui
|
||||
<i>n'ont
|
||||
pas été payés à l'échéance.</i>
|
||||
<p>A un certain point, il peut devenir clair qu'un client ne va jamais
|
||||
aller payer ce qu'il doit, et nous devons l'inscrire comme un <b>Mauvais
|
||||
débiteur.</b>
|
||||
<p>A ce point, il est typique d'enregistrer une entrée ainsi:
|
||||
<br>
|
||||
<table summary="BADDEBT" >
|
||||
<tr>
|
||||
<th>Compte</th>
|
||||
|
||||
<th>DR</th>
|
||||
|
||||
<th>CR</th>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Dépense mauvais débiteurs </td>
|
||||
|
||||
<td>10,000F</td>
|
||||
|
||||
<td></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Crédit fournisseurs </td>
|
||||
|
||||
<td></td>
|
||||
|
||||
<td>10,000F</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<p>Nous pouvons avoir <b>Revenus de ventes</b> réduits à
|
||||
la place, mais les sociétés tendent à préférer
|
||||
specifiquement le suivi de montants qu'ils ont perdus avec de mauvais clients.
|
||||
<p><i>Attention: <b>Concept de comptabilité avancée.</b>
|
||||
Les dettes perdues / créances douteuses sont un exemple d' un "contre-compte."
|
||||
Qui ne se réfère pas au <b>montants payés aux
|
||||
rebelles nicaraguyens (ndt:!!!) ,</b> mais plutôt à la notion
|
||||
que le compte est un compte de revenus qui espère conserver un solde
|
||||
opposé à ce qui est normalement espéré, pour
|
||||
annuler le solde dans un autre compte de revenus. <a href="xacc-apprdepr.html#depr">La
|
||||
dépréciation accumulée ,</a> utilisée pour
|
||||
diminuer la valeur d'un avoir au cours du temps, est un autre exemple de
|
||||
contre-compte.</i>
|
||||
<br>
|
||||
<h1>
|
||||
Dettes fournisseurs</h1>
|
||||
Le scénario pour les dettes fournisseurs, inversement, reflète
|
||||
comment les dettes fournisseurs fonctionnent; changer juste le client par
|
||||
le fournisseur, et voyez comment les roles sont inversés.
|
||||
<ul>
|
||||
<li>
|
||||
Si nous achetons des choses "sur notre compte," la comptabilité
|
||||
accumulative requiert que nous enregistrons ce que nous mettons dans les
|
||||
dépenses immédiatement, et rather than reducing cash, we
|
||||
put the "credit" into the <b>Accounts Payable</b> account.</li>
|
||||
|
||||
<li>
|
||||
Trois semaines plus tard, la facture arrive, et nous émettons un
|
||||
paiement, et ainsi pour <i>Dettes fournisseurs en débit, Liquidités
|
||||
en crédit.</i></li>
|
||||
|
||||
<br> </ul>
|
||||
|
||||
<h1>
|
||||
Avances aux clients/ Dépenses prépayées</h1>
|
||||
Des techniques analogues sont aussi utilisés pour les dépenses
|
||||
qui sont prépayées.
|
||||
<p>Si vous devez payer six mois de loyer en avance, c'est traité
|
||||
comme un "avoir accumulé."
|
||||
<ul>
|
||||
<li>
|
||||
Au moment du paiement, vous <i>débitez</i> <b>Location prépayée</b>
|
||||
du montant payé qui est un <i>Crédit</i> de <b>Liquidités.</b></li>
|
||||
|
||||
<p><br>Tandis que celà impose un malheureux préjudice dans
|
||||
le compte de Liquidités, il <i>apparait sur les livres </i>comme
|
||||
un avoir, et il n'y a pas plus de paiements à faire pour les six
|
||||
prochains mois.
|
||||
<br>
|
||||
<li>
|
||||
Chaque mois , le solde dans <b>Loyer prépayé</b> devrait
|
||||
diminuer via un <i>Débit de </i><b>Dépense de loyer</b>,
|
||||
<i>Crédit
|
||||
de </i><b>Loyer prépayé</b>.</li>
|
||||
</ul>
|
||||
De la même manière, les sociétés collectent
|
||||
les impôts sur la paie au nom des employées, et les garde
|
||||
dans un compte bancaire spécial.
|
||||
<ul>
|
||||
<li>
|
||||
<i>Cet </i>argent n'est pas celui de la société, ainsi il
|
||||
y a un <i>Débit</i> du compte <b>Liquidités</b> d'un coté,
|
||||
et un <i>Crédit</i> de Dettes Accumulées, c'est-à-dire,
|
||||
<b>des
|
||||
impôts sur le revenu payés</b>, d'un autre coté.</li>
|
||||
|
||||
<li>
|
||||
Quand le chèque trimestriel va au gouvernement afin qu'ils puissent
|
||||
faire <i>leur</i> paie, <b>les impôts sur le revenu payés</b>
|
||||
tombent comme le fait le solde dans le <b>compte chèques</b></li>
|
||||
|
||||
<br> </ul>
|
||||
|
||||
<hr>
|
||||
<p>Retour à la <a href="xacc-main.html">Page principale de la documentation.</a>
|
||||
<br>
|
||||
</body>
|
||||
</html>
|
||||
@ -1,682 +0,0 @@
|
||||
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
|
||||
<meta name="GENERATOR" content="Mozilla/4.7 [fr] (Win98; I) [Netscape]">
|
||||
<title>Dépréciation et gains en capital/plus-values</title>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href="gnucash.css">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<h1>
|
||||
Dépréciation et gains en capital/plus-values</h1>
|
||||
Cette section fournit une analyse du traitement de la dépréciation
|
||||
et l'appréciation des avoirs dans GnuCash.
|
||||
<p>Il fournit aussi une brève introduction au sujet relatif aux
|
||||
impôts.
|
||||
<p><b>Attention:</b> <i>Soyez conscients que les différents pays
|
||||
peuvent avoir des politiques fiscales <b>considérablement </b>différentes
|
||||
pour le traitement de ces choses; tout ce que ce document peut réellement
|
||||
fournir est quelques idées fondamentales pour vous aider
|
||||
à appliquer votre méthode "favorite"d'impots/dépréciation.</i>
|
||||
<p>Notez que l'appréciation et la dépréciation des
|
||||
avoirs tend à être traitées quelque peu différemment:
|
||||
<ul>
|
||||
<li>
|
||||
<a href="#depr">La dépréciation</a> est <i>habituellement</i>
|
||||
reconnue (le terme technique est <b>accru/accumulé</b>) comme une
|
||||
dépense sur une base continue, réduisant graduellement la
|
||||
valeur d'un avoir vers zéro.</li>
|
||||
|
||||
<p><br>La dépréciation tend à uniquement à
|
||||
s'obtenir calculée sur les avoirs qui sont utilisés par des
|
||||
professionnels ou à objectifs professionnels, parce que les gouvernements
|
||||
ne vous permettent générallement pas de réclamer des
|
||||
déductions de dépréciation sur les avoirs personnels,
|
||||
et c'est inutile de s'ennuyer avec la procédure si ce n'est pas
|
||||
déductible.
|
||||
<li>
|
||||
En contraste, <a href="#appr">les gains en capital,</a> qui pourraient
|
||||
être appelés <i>appréciation de la valeur des avoirs,</i>
|
||||
ne sont typiquement <i>pas</i> reconnus jusqu'à un certain moment
|
||||
qui arrête ce fait quand les avoirs sont vendus, et à cet
|
||||
<i>instant,</i>
|
||||
le gain en entier devient revenus.</li>
|
||||
|
||||
<br>Différent de la dépréciation, les gouvernements
|
||||
tendent à être <i>très intéressés </i>par
|
||||
la taxation des gains en capital d'une manière ou l'autre.
|
||||
<p>(Comme toujours, ils y a des exceptions. Si vous possédez une
|
||||
obligation qui paie tous ces intérêts en fin de vie, les autoritées
|
||||
fiscales requéreront souvent que vous reconnaissez/percevez des
|
||||
intérêts chaque année, et refuser celà pour
|
||||
être traité comme un gain en capital. L'expression <i>intérêts
|
||||
accumulés,</i> ou <i>intérêts imputés</i> sont
|
||||
souvent là pour effayer ceux qui sont sensibles à de telles
|
||||
choses...)</ul>
|
||||
|
||||
<h1>
|
||||
Gains en capital/Plus-values - Appréciation des avoirs</h1>
|
||||
<a NAME="appr"></a>
|
||||
<p>L'appréciaton des avoirs est, en général, une question
|
||||
assez astucieuse à traiter avec. C'est ainsi parce que, pour quelques
|
||||
types d'avoirs, il est difficile de correctement estimer une augmentation
|
||||
en valeur <i>jusqu'à ce que réellement vous vendiez les avoirs.</i>
|
||||
<p>Si vous investissez dans des <a href="xacc-ticker.html">valeurs</a>
|
||||
qui sont échangées sur une base journalière sur des
|
||||
marchés ouverts tel que des bourses d'actions, les cours peuvent
|
||||
être assez exacts, et vendre l'avoir aux prix du marché peut
|
||||
être aussi simple que d'appeler un courtier et d'émettre un
|
||||
<b>Ordre
|
||||
de bourse.</b>
|
||||
<p>D'un autre coté, les maisons que vos voisins ont vendus en quelque
|
||||
sorte moins souvent, tel que les ventes tendent à entrainer un effort
|
||||
considérable de dépenses, et entraine des négociations,
|
||||
ce qui veut dire que les estimations sont probablement moins précises.
|
||||
De la même manière, vendre une automobile utilisée
|
||||
implique un processus de négociation qui rend la tarification un
|
||||
peu moins prédictible.
|
||||
<p>Plus difficile à estimer sont les valeurs de collections d'objets
|
||||
tel que les bijoux, création d'Art, cartes de baseball, et
|
||||
"Beanie Babies." Les marchés pour de tels objets sont quelque peu
|
||||
moins ouvert/accessible que les marchés de valeurs.
|
||||
<p>Les pires choses poutant sont une sorte de biens. Les usines contiennent
|
||||
souvent des presses et font des produits personnalisés pour
|
||||
construire un produit très spécifique qui coûte dix
|
||||
ou cent de milliers de dollars; cet équipement peut-être <i>de
|
||||
moins de valeur</i> en dehors de ce contexte très spécifique.
|
||||
Dans de tels cas, il y a plusieurs valeurs contracdictoires qui peuvent
|
||||
être attaché au bien, <i>aucune</i> d'elles sans ambiguité
|
||||
ne sont correctes.
|
||||
<p>Supposons que vous achetez un avoir prévu pour augmenter en valeur,
|
||||
disons un tableau de Degas, et vous voulez suivre celà. (La compagnie
|
||||
d'assurances se souciera de celà, même si personne d'autre
|
||||
le fait.)
|
||||
<p>Le suivi correctement de la valeur en augmentation continuelle du Degas
|
||||
requèrera au moins trois, plutôt peut-être les quatre
|
||||
comptes suivants (plus un compte bancaire ou de liquidités d'où
|
||||
l'argent pour l'argent pour l'achat provient):
|
||||
<ul>
|
||||
<li>
|
||||
Un compte avoirs <i>Coût de l'avoir</i> pour suivre le coût
|
||||
original du tableau,</li>
|
||||
|
||||
<li>
|
||||
An compte avoirs <i>Gains accumulés non réalisés
|
||||
sur Avoir</i> pour suivre les augmentations en valeur, et</li>
|
||||
|
||||
<li>
|
||||
Un compte revenus <i>Gains accumulés sur les revenus de l'avoir</i>
|
||||
dans lequel l'enregistrement du coté revenus des gains annuels dans
|
||||
votre richesse, et</li>
|
||||
|
||||
<li>
|
||||
Un compte revenus <i>Gains réalisés sur les revenus
|
||||
de l'avoir </i>qui enregistre le revenu réalisé quand vouys
|
||||
vendez l'avoir.</li>
|
||||
</ul>
|
||||
Les <i>gains accumulés </i> n'affecte sûrement pas vos
|
||||
revenus imposables en ayant objectif d'impots sur le <i>revenu</i>, bien
|
||||
qu'il puisse avoir quelque effet sur les impôts sur les <i>biens</i>.
|
||||
<h2>
|
||||
Le traitement des gains en capital dans GnuCash</h2>
|
||||
|
||||
<h3>
|
||||
L'acquisition</h3>
|
||||
La première chose que vous devez faire est de créer le <i>compte
|
||||
coût de l'avoir</i>, alors transférez la somme que vous avez
|
||||
payé pour ce tableau depuis votre compte bancaire vers ce compte
|
||||
avoirs pour enregistrer l'achat.
|
||||
<p>Un mois plus tard, vous avez raison de suspecter que la valeur de votre
|
||||
tableau a augmenté de 1200F. Afin d'enregistrer celà
|
||||
vous transférez 1200F depuis votre compte revenus <i>gains accumulés
|
||||
sur un avoir vers votre compte avoirs</i>.
|
||||
<p>Votre fenêtre principale ressemblera à celà:
|
||||
<br><img SRC="appr-main1.gif" ALT="Main window after purchase and appreciation" NOSAVE height=281 width=586>
|
||||
<p>et votre compte avoirs ressemblera à celà:
|
||||
<br><img SRC="appr-asset1.gif" ALT="Asset account after purchase and appreciation" NOSAVE height=372 width=683>
|
||||
<h3>
|
||||
Jusqu'à ce que vous possédiez l'avoir</h3>
|
||||
L'appréciation de l'avoir est une sorte de revenus mais il n'est
|
||||
<i>pas</i>
|
||||
en espèces dans votre main.
|
||||
<p>Les gens qui sont devenus "riches" en 1999 grâce à
|
||||
l'offre initiale au public en bourse (IPO) de sociétés ayant
|
||||
rapport à Linux comme Red Hat Software et VA Linux Systems permettent
|
||||
de vérifier celà. Ils détiennent des options ou des
|
||||
actions qui sont <i>théoriquement </i>évaluées
|
||||
à des millions de dollars USD.
|
||||
<p>Ce qui ne veut pas dire qu'ils sont actuellement millionnaires; les
|
||||
participants principaux ont possédé leurs actions au moins
|
||||
six mois auparavant avant de vendre <i>n'importe lesquelles</i> d'entre
|
||||
elles. Le fait qu'ils <i>ne pouvait</i> les vendre veut dire que tant qu'
|
||||
elles doivent en théorie être d'une valeur de millions de
|
||||
dollars sur le papier, il y a, comme à la fin de 1999, aucune voie
|
||||
pour eux pour légallement <i>recevoir ces </i>millions.
|
||||
<h3>
|
||||
Vendre l'avoir</h3>
|
||||
Disons q'un autre mois plus tard les prix des tableaux de Degas ont montés
|
||||
encore, dans votre cas de d'environ 2500F, que vous estimez. Vous enregistrez
|
||||
dûment ces 2500F comme un revenu comme ci-dessus, alors vous décidez
|
||||
de vendre le tableau.
|
||||
<p>Maintenant il se produit trois possibilitées:
|
||||
<ol>
|
||||
<li>
|
||||
Votre estimation optimiste de la valeur du tableau était correcte.</li>
|
||||
|
||||
<br>Le compte revenus est laissé tranquille (ou peut-être
|
||||
recevta des transferts depuis un compte revenus <i>Gain</i> <i>accumulé
|
||||
</i>vers
|
||||
un compte revenus <i>Gain réalisé </i>), et l'enregistrement
|
||||
est plutôt comme celà:
|
||||
<br>
|
||||
<table summary="BIGGAIN" >
|
||||
<tr>
|
||||
<th>Compte</th>
|
||||
|
||||
<th>Montant</th>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Liquidités</td>
|
||||
|
||||
<td>16055F</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Tableau</td>
|
||||
|
||||
<td>-11000F</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Revenu du gain réalisé</td>
|
||||
|
||||
<td>-5055F</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<p>Et si n'importe lequel des montants a été accumulé
|
||||
comme des <i>Gains accumulés,</i> le montant de l'avoir devrait
|
||||
être augmenté(closed out), compensé par une valeur
|
||||
<i>négative</i>
|
||||
pour le revenu <i>Gain accumulés</i>. Si le total qui a été
|
||||
accumulé était de 5000F, alors la transaction devrait ressembler
|
||||
à ce qui suit :
|
||||
<br>
|
||||
<table summary="BIGGAINACCRUEDTOO" >
|
||||
<tr>
|
||||
<th>Compte</th>
|
||||
|
||||
<th>Montant</th>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Liquidités</td>
|
||||
|
||||
<td>16055F</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Tableau</td>
|
||||
|
||||
<td>-11000F</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Avoir du gain accumulé</td>
|
||||
|
||||
<td>-5000F</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Revenu du gain réalisé</td>
|
||||
|
||||
<td>-5055F</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Revenu du gain accumulé</td>
|
||||
|
||||
<td>5000F</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<p>Notez que les deux comptes de revenus compense un autre ainsi que le
|
||||
revenu <i>actuel</i> resultant de la transaction est seulement de 55F.
|
||||
Le reste de 5000F a précédemment été reconnu
|
||||
comme un <i>Revenu de gain accumulé.</i>
|
||||
<li>
|
||||
Vous étiez suroptimiste à propos de la valeur du tableau.</li>
|
||||
|
||||
<p><br>A la place de 16055F que vous pensiez que le tableau était
|
||||
évalué, il est seulement proposé à 15000F.
|
||||
Mais vous décidez poutant de le vendre, parce que vous l'évaluez
|
||||
à 15000F de plus que ce que vous évaluez le tableau.
|
||||
<p>Les chiffres changent un petit peu, mais pas aussi dramatiquement.
|
||||
<br>
|
||||
<table summary="SMALLGAINACCRUEDTOO" >
|
||||
<tr>
|
||||
<th>Compte</th>
|
||||
|
||||
<th>Montant</th>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Liquidités</td>
|
||||
|
||||
<td>15000F</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Tableau</td>
|
||||
|
||||
<td>-11000F</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Avoir du gain accumulé</td>
|
||||
|
||||
<td>-5000F</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Revenu du gain réalisé</td>
|
||||
|
||||
<td>-4000F</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Revenu du gain accumulé</td>
|
||||
|
||||
<td>5000F</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<p>Notez que les deux comptes de revenus compensent un autre ainsi que
|
||||
le revenu <i>actuel</i> résultant de la transaction fait ressortir
|
||||
une <i>pertes</i> de 1000F. C'est formidable, comme vous avez précédemment
|
||||
reconnu 5000F de revenus.
|
||||
<li>
|
||||
Vous avez réussi à vendre votre tableau pour plus que vous
|
||||
pensiez dans vos rêves délirants.</li>
|
||||
|
||||
<p><br>La valeur supplémentaire est, encore, enregistré comme
|
||||
un gain, par exemple un revenu.
|
||||
<br>
|
||||
<table summary="HUGEGAIN" >
|
||||
<tr>
|
||||
<th>Compte</th>
|
||||
|
||||
<th>Montant</th>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Liquidités</td>
|
||||
|
||||
<td>50000F</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Tableau</td>
|
||||
|
||||
<td>-11000F</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Avoir du gain accumulé</td>
|
||||
|
||||
<td>-5000F</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Revenus du gain réalisé</td>
|
||||
|
||||
<td>-39000F</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Revenus du gain accumulé</td>
|
||||
|
||||
<td>5000F</td>
|
||||
</tr>
|
||||
</table>
|
||||
</ol>
|
||||
En pratique, il est vraiment important de garder le <i>Revenu du gain accumulé</i>
|
||||
séparé du <i>Revenu du gain réalisé,</i> comme
|
||||
ci-dessus il est sûrement ignoré par vos autorités
|
||||
fiscales, qui voudront seulement vous faire payer quelque chose sur le
|
||||
<i>Gain
|
||||
réalisé.</i>
|
||||
<p>En bas, nous montrons le second cas à discuter.
|
||||
<br><img SRC="appr-main2.gif" ALT="Main window after sale" NOSAVE height=281 width=586>
|
||||
<br><img SRC="appr-asset2.gif" ALT="Asset account after sale" NOSAVE height=372 width=683>
|
||||
<h2>
|
||||
Précaution à propos de l'évaluation</h2>
|
||||
Comme nous le voyons dans cette example, pour des biens non-financier,
|
||||
il peut être difficile d'estimer correctement la ``vraie'' valeur
|
||||
d'un bien.
|
||||
<p>Il est tout à fait facile de compter vous-même votre richesse
|
||||
en vous basant sur des estimations discutables qui ne reflètent
|
||||
pas "l'argent à la banque."
|
||||
<p>Ainsi, quand vous traitez de l'appreciation des avoirs,
|
||||
<ol>
|
||||
<li>
|
||||
Soyez prudent avec l'estimation de valeurs.</li>
|
||||
|
||||
<p><br>Ne vous adonnez pas à un espoir secret.
|
||||
<li>
|
||||
Jamais, au grand jamais, ne compter pas sur l'argent que vous n'avez pas
|
||||
à votre banque ou en espèces.</li>
|
||||
|
||||
<p><br>Jusqu'à ce que vous ayez réellement vendu vos avoirs
|
||||
et récupérez l'argent, n'importe quel chiffres sur le papier
|
||||
(ou une preuve magnetique sur votre dique dur) sont simplement celà.
|
||||
<p>Si vous pouvez convaincre avec réalisme un banquier de vous prêter
|
||||
de l'argent, utilisant les biens comme garantie, ce qui est une évidence
|
||||
très raisonnable qui est que les biens ont de la valeurs, comme
|
||||
les prêteurssont professionnellement suspicieux des surestimations
|
||||
douteuses de valeurs.
|
||||
<p>Soyez conscient: toutes les trop nombreuses sociétés qui
|
||||
apparaissent "profitable" sur le papier quittent les affaires à
|
||||
la suite d'un épuisement des <i>liquidités,</i> précisément
|
||||
parce que les "biens de valeur" ne seront pas la même chose que l'argent
|
||||
comptant.</ol>
|
||||
|
||||
<h2>
|
||||
Taxation des gains en capital/plus-values</h2>
|
||||
Les politiques fiscales varient considérablement entre les pays,
|
||||
ainsi il est virtuellement impossible de dire quelque chose qui sera universellement
|
||||
utile.
|
||||
<p>Pourtant, il est <i>commun</i> pour les revenus générés
|
||||
par des gains en capital de n'être pas sujet à la taxation
|
||||
jusqu'à la date où le bien est réellement vendu, et
|
||||
quelque fois pas même alors.
|
||||
<p>Les ropriétaires de maisons nord américain <i>habituellement
|
||||
</i>trouve
|
||||
que quand ils vendent leurs résidences personnelles, les gains en
|
||||
capital qui surviennent sont exempt de taxation. Il apparait que d'autres
|
||||
pays traitent les ventes de maisons différemment, taxant les gens
|
||||
sur de tels gains. Les autoritées allemandes, par exemple, taxent
|
||||
ces gains seulement si vous possédez la propriété
|
||||
depuis moins de dix ans.
|
||||
<p><a href="mailto:cbbrowne@hex.net">J'ai</a> une histoire de mes jours
|
||||
de préparation de taxe en tant que professionnel où une famille
|
||||
vendit une ferme, et s'attendit à une facture fiscale <i>considérable</i>
|
||||
qui se trouva être virtuellement en raison de nul en raison de la
|
||||
posession de la propriété avant 1971 (en quoi les mensonges
|
||||
sont une critique de la date du "Jour de l'évaluation" au Canada)
|
||||
et en raison qu'étant une ferme <i>laitière,</i> avec
|
||||
quelquesdéductions résultant d'un régime <i>réellement
|
||||
singulier</i>.
|
||||
<p>En résumé, cette présentation est assez simple,
|
||||
mais la taxation souvent devient terriblement compliquée...
|
||||
<h1>
|
||||
Dépréciation des avoirs/biens</h1>
|
||||
<a NAME="depr"></a>
|
||||
<p>Comparé à des estimations souvent incertaines une à
|
||||
faire où l'appréciation des avoirs est concernée,
|
||||
nous sommes en quelque sorte en terrain solide ici.
|
||||
<ul>
|
||||
<li>
|
||||
Les gouvernements tendent à installer des règles précises
|
||||
sur comment il vous est demandé de calculer la dépréciation
|
||||
à objectifs fiscaux.</li>
|
||||
|
||||
<li>
|
||||
Il est facile d'aller voir les références tel que les "Livres
|
||||
bleus" estimant de combien une automobile devrait être évalué
|
||||
après 3 années d'utilisation.</li>
|
||||
</ul>
|
||||
Depuis que la dépréciation des avoirs est très souvent
|
||||
conduite par des politiques fiscales, la discussion de la dépréciation
|
||||
se concentrera dans cette direction, sur certains des plus communs schémas
|
||||
de calcul de la dépréciation.
|
||||
<p>Tandis qu'il a eu quelques discussions à propos de comment accomplir
|
||||
des calculs automatisés et la création de transactions pour
|
||||
traiter des choses comme la dépréciation, il n'y a pas encore
|
||||
aucun code fonctionnel, ainsi pour maintenant, vous devrez faire les calculs
|
||||
à la main.
|
||||
<h2>
|
||||
Systèmes de dépréciation</h2>
|
||||
|
||||
<h3>
|
||||
Dépréciation linéaire</h3>
|
||||
La dépréciation linéaire diminue la valeur d'un bien
|
||||
par un montant fixé pour chaque période jusqu'à ce
|
||||
que la valeur nette est de zéro. C'est le calcul le plus <i>simple</i>,
|
||||
comme vous estimez une durée de vie utile, et simplement diviser
|
||||
le coût également au cours de la durée de vie.
|
||||
<p><b>Exemple:</b> Vous avez acheté un ordinateur pour $1500 et
|
||||
souhaité le déprécier sur une période de 5
|
||||
années. Chaque année le montant de dépréciation
|
||||
est de $300, aboutissant aux calculs suivants:
|
||||
<br>
|
||||
<table summary="Example 1" >
|
||||
<tr>
|
||||
<th>Année</th>
|
||||
|
||||
<th>Dépréciation</th>
|
||||
|
||||
<th>Valeur restante</th>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>1</td>
|
||||
|
||||
<td>300</td>
|
||||
|
||||
<td>1200</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>2</td>
|
||||
|
||||
<td>300</td>
|
||||
|
||||
<td>900</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>3</td>
|
||||
|
||||
<td>300</td>
|
||||
|
||||
<td>600</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>4</td>
|
||||
|
||||
<td>300</td>
|
||||
|
||||
<td>300</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>5</td>
|
||||
|
||||
<td>300</td>
|
||||
|
||||
<td>0</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<h3>
|
||||
Dépréciation géométrique</h3>
|
||||
A chaque période, le bien est déprécié d'un
|
||||
pourcentage fixé dans la précédente période
|
||||
de sa valeur. Dans ce système le reste de la valeur d'un bien diminuant
|
||||
exponentiellement est ce qui reste de la valeur à la fin et qui
|
||||
est plus grand que zéro (par exemple - une valeur de revente).
|
||||
<p><i>Faites attention: les autorités fiscales peuvent demander
|
||||
(orpermettre) un plus large pourcentage dans la première période.</i>
|
||||
D'un autre côté, au Canada, c'est changé/inversé,
|
||||
comme ils permettent seulement une <i>moitié </i>de la part
|
||||
of "Remise du coût du capital" dans la première année.
|
||||
<p>Le résultat de cette approche est que la valeur du bien diminue
|
||||
plus rapidement au départ qu'à la fin ce qui est <i>probablement</i>
|
||||
plus réaliste pour la plupart des biens qu'un système linéaire.
|
||||
C'est certainement vrai pour les automobiles.
|
||||
<p><b>Exemple:</b> Nous prenons le même exemple comme ci-dessus,
|
||||
avec une dépréciation annuelle de 30%.
|
||||
<br>
|
||||
<table summary="Example 2" >
|
||||
<tr>
|
||||
<th>Année</th>
|
||||
|
||||
<th>Dépréciation</th>
|
||||
|
||||
<th>Valeur restante</th>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>1</td>
|
||||
|
||||
<td>450</td>
|
||||
|
||||
<td>1050</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>2</td>
|
||||
|
||||
<td>315</td>
|
||||
|
||||
<td>735</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>3</td>
|
||||
|
||||
<td>220.50</td>
|
||||
|
||||
<td>514.50</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>4</td>
|
||||
|
||||
<td>154.35</td>
|
||||
|
||||
<td>360.15</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>5</td>
|
||||
|
||||
<td>108.05</td>
|
||||
|
||||
<td>252.10</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<h3>
|
||||
Somme de chiffres</h3>
|
||||
Une troisième méthode la plus souvent employé dans
|
||||
les pays Anglo/Saxon est la méthode de la "somme de chiffres". Ici
|
||||
se trouve une illustration:
|
||||
<p><b>Exemple:</b> Premièrement vous divisez la valeurs des biens
|
||||
par la somme des années d'utilisation, par exemple pour notre exemple
|
||||
avec ci-dessus une valeur du bien de $1500 qui est utilisé sur une
|
||||
période de cinq années vous avez 1500/(1+2+3+4+5)=100. La
|
||||
dépréciation et la valeur du bien sont alors calculés
|
||||
comme suivant:
|
||||
<br>
|
||||
<table summary="Example 3" >
|
||||
<tr>
|
||||
<th>Année</th>
|
||||
|
||||
<th>Dépréciation</th>
|
||||
|
||||
<th>Valeur restante</th>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>1</td>
|
||||
|
||||
<td>100*5=500</td>
|
||||
|
||||
<td>1000</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>2</td>
|
||||
|
||||
<td>100*4=400</td>
|
||||
|
||||
<td>600</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>3</td>
|
||||
|
||||
<td>100*3=300</td>
|
||||
|
||||
<td>300</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>4</td>
|
||||
|
||||
<td>100*2=200</td>
|
||||
|
||||
<td>100</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>5</td>
|
||||
|
||||
<td>100*1=100</td>
|
||||
|
||||
<td>0</td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<h2>
|
||||
Le traitement de la dépréciation dans gnucash</h2>
|
||||
Afin de suivre la dépréciation d'un bien, vous avez besoin
|
||||
:
|
||||
<ul>
|
||||
<li>
|
||||
Un compte avoirs <i>Coût de l'avoir</i> pour suivre la valeur originale;</li>
|
||||
|
||||
<li>
|
||||
Un compte avoirs <i>Dépréciation accumulée</i> dans
|
||||
lequel est collecté la somme de tous les montants de dépréciation
|
||||
des années;</li>
|
||||
|
||||
<li>
|
||||
Un compte dépenses <i>Dépense de dépréciation
|
||||
</i>dans
|
||||
lequel enregistrer les dépenses periodiques de dépréciation.</li>
|
||||
</ul>
|
||||
La première étape, encore, est d'enregistrer l'achat de vos
|
||||
biens en transférrant l'argent d'un compte bancaire vers le compte
|
||||
<i>coût de bien</i>. Après, dans chaque période comptable
|
||||
vous enregistrez la dépréciation comme une dépense
|
||||
dans le compte approprié.
|
||||
<p>Les deux fenêtres ci-dessous montre votre compte avoirs et la
|
||||
fenêtre principale après la troisième année
|
||||
de dépréciation en utilisant un système de "somme
|
||||
de chiffres" pour l'exemple ci-dessous.
|
||||
<br><img SRC="depr-asset.gif" ALT="Asset account after depreciation" NOSAVE height=372 width=683>
|
||||
<br><img SRC="depr-main.gif" ALT="Main window after depreciation" NOSAVE height=281 width=586>
|
||||
<h2>
|
||||
Un mot d'avertissement</h2>
|
||||
Depuis que la dépréciation et le sujet des impôts sont
|
||||
minitieusement raconté, vous ne pouvez pas toujours être libre
|
||||
dans le choix de votre méthode préférrée. La
|
||||
correction de mauvais calculs coutera une quantité entière
|
||||
de plus de temps et d'ennui que d'obtenir des calculs bon la première
|
||||
fois, ainsi si vous planifiez de déprécier les biens, il
|
||||
est prudent d'être sûr du système que vous serez permit
|
||||
<i>ou
|
||||
requis</i> d'utiliser
|
||||
<br>
|
||||
<hr WIDTH="100%">
|
||||
<br>Retour à la <a href="xacc-main.html">Page principale de la documentation.</a>.
|
||||
<br>
|
||||
<br>
|
||||
</body>
|
||||
</html>
|
||||
@ -1,16 +0,0 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href="gnucash.css">
|
||||
<title>Rapport de suivi du solde/bilan</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>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@ -1,20 +0,0 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
|
||||
<html>
|
||||
<head>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href="gnucash.css">
|
||||
|
||||
<title>Feuille du solde/bilan</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>
|
||||
</html>
|
||||
File diff suppressed because it is too large
Load Diff
@ -1,49 +0,0 @@
|
||||
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
|
||||
<meta name="GENERATOR" content="Mozilla/4.7 [fr] (Win98; I) [Netscape]">
|
||||
<link rel="stylesheet" title="normal" type="text/css" href="gnucash.css">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<h1>
|
||||
L'entrée de date</h1>
|
||||
La cellule/case de la date fonctionne avec les raccourcis clavier suivant
|
||||
:
|
||||
<ul>
|
||||
<li>
|
||||
<tt>+, = </tt> incrémente d'un jour</li>
|
||||
|
||||
<li>
|
||||
<tt>_ , -</tt> décremente d'un jour</li>
|
||||
|
||||
<li>
|
||||
<tt>} , ]</tt> incrémente d'un mois</li>
|
||||
|
||||
<li>
|
||||
<tt>{ , [</tt> décrémente d'un mois</li>
|
||||
|
||||
<li>
|
||||
<tt>M , m</tt> début du mois</li>
|
||||
|
||||
<li>
|
||||
<tt>H , h</tt> fin du mois</li>
|
||||
|
||||
<li>
|
||||
<tt>Y , y</tt> début de l'année</li>
|
||||
|
||||
<li>
|
||||
<tt>R , r</tt> fin de l'année</li>
|
||||
|
||||
<li>
|
||||
<tt>T , t</tt> aujourd'hui</li>
|
||||
</ul>
|
||||
GnuCash peut-être compiler pour utiliser soit les dates au format
|
||||
européen ou les dates au format américain.
|
||||
<br>Chercher <i>UK_DATES</i> dans dates.h
|
||||
<br>
|
||||
<hr WIDTH="100%">
|
||||
<p>Retour à la <a href="xacc-main.html">Page principale de la documentation.</a>
|
||||
</body>
|
||||
</html>
|
||||
@ -1,149 +0,0 @@
|
||||
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
|
||||
<meta name="GENERATOR" content="Mozilla/4.7 [fr] (Win98; I) [Netscape]">
|
||||
<title>Utilisation de la fonction de la double entrée</title>
|
||||
<link rel="stylesheet" title="normal" type="text/css" href="gnucash.css">
|
||||
<X-SAS-WINDOW TOP=25 BOTTOM=475 LEFT=4 RIGHT=534>
|
||||
</head>
|
||||
<body bgcolor="#EEEEEE">
|
||||
|
||||
<h1>
|
||||
<font size=+3>Qu'est-ce que la comptabilité du double livret/double
|
||||
entrée?</font></h1>
|
||||
La comptabilité du double livret est une méthodologie comptable
|
||||
introduite au 13ème siècle pour s'assurer que chaque transaction
|
||||
est correctement equilibrée/égale.
|
||||
<p>Quand celles-ci sont toutes requises pour s'équilibrer, la probabilité
|
||||
qu'une erreur sur les données entrées est été
|
||||
faite est beaucoup moindre. Pour les grands et complexes ensembles de comptes
|
||||
avec beaucoup de transactions , il est d'une manière navrante facile
|
||||
de faire des erreurs qui peuvent continuer à rester undétectées
|
||||
pendant longtemps, et être épouvantablement
|
||||
<br>difficile à localiser, même quand la comptabilité
|
||||
du double livret est utilisé.
|
||||
<p>Une transaction à double entrée est une transaction qui
|
||||
contient des entrées pour deux (ou plus) comptes qui s'annule l'un
|
||||
et l'autre. Un compte est <i>débité</i> d'un montant exactement
|
||||
égal à celui dont l'autre <i>est crédité</i>.En
|
||||
s'assurant que chaque transaction
|
||||
<br>s'équilibre/s'annule, un ensemble équilibré de
|
||||
comptes est garanti. Celà ne vous empêche pas d'avoir des
|
||||
errors, mais certainement il élimine le grand type d'erreurs du
|
||||
genre :<b>J'ai oublié d'entrer cette partie de la transaction</b>.
|
||||
<p>La double entrée peut être introduite d'une façon
|
||||
plus grâce à la notion de transfert d'un compte bancaire vers
|
||||
un autre , où le montant est retiré d'un compte et déposé
|
||||
dans un autre. C'est effectivement le "rôle" de la comptabilité
|
||||
du double livret; si vous avez ajouté quelque chose dans un compte,
|
||||
vous <i>devez</i> avoir un autre composant de cette transaction pour équilibrer
|
||||
celà.
|
||||
<p><b>Pas forcément un aparté:</b> Si vous regardez votre
|
||||
relevé de compte, il est typiquement décrit en détail
|
||||
à partir du <b>point de vue de la banque</b>, qui est exactement
|
||||
l'<i>opposé</i> du votre. Par exemple, quand vous y mettez de l'argent,
|
||||
effectuant un dépôt, qui établit un <b>DEBIT</b> de
|
||||
leur part/pour eux.
|
||||
<p>Peut-être moins évident est la notion que la double entrée
|
||||
peut être utilisée pour représenter les revenus et
|
||||
dépenses aussi bien que les transferts bancaires . Regardez la fenêtre
|
||||
d'aide "<a href="xacc-expense.html">Revenu/Dépense</a>" pour plus
|
||||
d'informations sur celà
|
||||
<p><a NAME="IDENTITY"></a>Dans un système traditionnel qui enregistre
|
||||
les débits et crédits séparément, l'identité
|
||||
que toutes les transactions sont
|
||||
<br> requises pour satisfaire que <tt>Total de débits = Total
|
||||
de crédits.</tt>
|
||||
<p>Le fait que l'identité requiert seulement que le <i>total</i>
|
||||
des soldes veut dire que c'est un petit peu trompeux d'appeler celle-ci
|
||||
comptabilité de la <i>double</i>-entée; il devrait être
|
||||
quelque peu plus exact de l'appeler comptabilité <i>multiple-</i>entrée.
|
||||
Malheureusement, il y a 700 ans d'histoire d'utilisation de ce terme, ce
|
||||
qui sufisamment décourageant pour le changer.
|
||||
<br>(Et quelques gens pensent qu' UNIX a quelques croustillants et
|
||||
vieux morceau d'étrangeté. Hah!)
|
||||
<p>GnuCash traite les "Débits" comme valeurs positives, et "Crédits"
|
||||
comme valeurs négatives, de telle façon à ce que cette
|
||||
<br>identité simplifie en <tt>value<sub>1</sub> + value<sub>2</sub>
|
||||
+ value<sub>3</sub> + ... = 0</tt>.
|
||||
<h1>
|
||||
Utiliser la double entrée/double livret</h1>
|
||||
|
||||
<h2>
|
||||
Creation de transactions</h2>
|
||||
Pour créer une transaction à double-entrée:
|
||||
<ul>
|
||||
<li>
|
||||
Cliquez sur une boîte dans la colonne marqué <tt>Transfert
|
||||
depuis</tt> sur le côté gauche du registre.</li>
|
||||
|
||||
<p><br>Un menu se déroulera , listant tous les comptes depuis lequel
|
||||
un transfert peut être réalisé.
|
||||
<li>
|
||||
Sélectionnez-en un.</li>
|
||||
|
||||
<p><br>Quand vous enregistrez la transaction, la double entrée sera
|
||||
automatiquement réalisée, et la transaction apparaîtra
|
||||
automatiquement dans toutes les fenêtres montrant les comptes transféré-depuis
|
||||
et transféré-vers.</ul>
|
||||
|
||||
<h2>
|
||||
Changement des transactions</h2>
|
||||
|
||||
<p><br>Pour <i>changer</i> une transaction à double entrée:
|
||||
<p>Afficher simplement la transaction dans n'importe quelle fenêtre
|
||||
dans laquelle elle apparait
|
||||
<p>N'importe quels changements effectués seront automatiquement
|
||||
reflétés dans l'ensemble des comptes et dans toutes les fenêtres
|
||||
affichant la transaction.
|
||||
<p>De la même manière, quand une transaction à double
|
||||
entrée est supprimée , les répartitions seront supprimés
|
||||
depuis l'ensemble des comptes ; et les soldes seront automatiquement recalculés
|
||||
pour l'<i>ensemble</i> des comptes .
|
||||
<p>Pour changer le compte de transfert, sélectionnez simplement
|
||||
un nouveau compte depuis le menu déroulant . Quand vous enregistrez
|
||||
la transaction, elle sera automatiquement selectionnée depuis le
|
||||
vieux compte , et insérée dans le nouveau compte .
|
||||
<h1>
|
||||
Nettoyage impeccable</h1>
|
||||
GnuCash peut être configuré pour être strict à
|
||||
propos de la double entrée, ou vous pouvez le configurer pour être
|
||||
"relaché".
|
||||
<p>En mode "relaché", vous pouvez créer des <i>transactions
|
||||
anormales/non équilibrées</i>, c'est à dire, des transactions
|
||||
où les répartitions ne s'équilibrent pas pour faire
|
||||
zéro.Celà met de coté la validation qui vient en utilisant
|
||||
le schema le plus strict
|
||||
<br>de la double entrée, qui n'est pas probablement réellement
|
||||
une prudent modification. En effet:
|
||||
<ul>
|
||||
<li>
|
||||
Si vous n'êtes pas sûr de ce que vous faites, vous ne voulez
|
||||
probablement pas mettre de côté la validation de la <b>double
|
||||
entrée,</b> comme celà vous aides à garder vos comptes
|
||||
équilibrés même quand tout celà n'est pas clair.</li>
|
||||
|
||||
<li>
|
||||
Si vous êtes une <i>"bête"/expert de la comptabilité,</i>
|
||||
vous serez ce qui est <i>réellement important</i> de garder comme
|
||||
choses en équilibre et préférerez encore la <b>double
|
||||
entrée.</b></li>
|
||||
</ul>
|
||||
Mais si vous décidez de "dépasser le système," et
|
||||
avoir un nombre de transactions non équilibrées, vous voudrez
|
||||
probablement
|
||||
<br>nettoyer ce travail à certain point. Pour nettoyer ces transactions
|
||||
anormales/non équilibrées, vous pouvez <b>nettoyer</b> le
|
||||
compte pour être net en choisissant "Nettoyage" à partir de
|
||||
la fenêtre du menu. Celà examinera chaque transaction; si
|
||||
la transaction ne s'équilibre pas, une entrée divisée/répartie
|
||||
sera créée et placée dans un compte nommé "<b>Anormal/Unbalanced</b>".
|
||||
Vous pouvez alors revoir ces divisions/répartitions et les déplacer
|
||||
vers leurs comptes appropriés.
|
||||
<br>
|
||||
<hr>
|
||||
<p>Retour à la <a href="xacc-main.html">Page principale de la documentation.</a>
|
||||
<br>
|
||||
</body>
|
||||
</html>
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue
Block a user