+ 
+ 
+ 
+ 
+ I hope others find these scripts useful.
+ +Ken Yamaguchi October 1998
+ + + diff --git a/doc/html/C/pix/appr-asset1.gif b/doc/html/C/pix/appr-asset1.gif new file mode 100644 index 0000000000..3d0a6d5bd8 Binary files /dev/null and b/doc/html/C/pix/appr-asset1.gif differ diff --git a/doc/html/C/pix/appr-asset2.gif b/doc/html/C/pix/appr-asset2.gif new file mode 100644 index 0000000000..8ecf19ebe1 Binary files /dev/null and b/doc/html/C/pix/appr-asset2.gif differ diff --git a/doc/html/C/pix/appr-income.gif b/doc/html/C/pix/appr-income.gif new file mode 100644 index 0000000000..5800f6a954 Binary files /dev/null and b/doc/html/C/pix/appr-income.gif differ diff --git a/doc/html/C/pix/appr-main1.gif b/doc/html/C/pix/appr-main1.gif new file mode 100644 index 0000000000..87cae7c15a Binary files /dev/null and b/doc/html/C/pix/appr-main1.gif differ diff --git a/doc/html/C/pix/appr-main2.gif b/doc/html/C/pix/appr-main2.gif new file mode 100644 index 0000000000..86351f1149 Binary files /dev/null and b/doc/html/C/pix/appr-main2.gif differ diff --git a/doc/html/C/pix/contract.gif b/doc/html/C/pix/contract.gif new file mode 100644 index 0000000000..695ca476c1 Binary files /dev/null and b/doc/html/C/pix/contract.gif differ diff --git a/doc/html/C/pix/depr-asset.gif b/doc/html/C/pix/depr-asset.gif new file mode 100644 index 0000000000..8f3fb79e51 Binary files /dev/null and b/doc/html/C/pix/depr-asset.gif differ diff --git a/doc/html/C/pix/depr-main.gif b/doc/html/C/pix/depr-main.gif new file mode 100644 index 0000000000..666c55fe5d Binary files /dev/null and b/doc/html/C/pix/depr-main.gif differ diff --git a/doc/html/C/pix/expand.gif b/doc/html/C/pix/expand.gif new file mode 100644 index 0000000000..1ee1ee3719 Binary files /dev/null and b/doc/html/C/pix/expand.gif differ diff --git a/doc/html/C/pix/foliowin-single.gif b/doc/html/C/pix/foliowin-single.gif new file mode 100644 index 0000000000..8004491ac6 Binary files /dev/null and b/doc/html/C/pix/foliowin-single.gif differ diff --git a/doc/html/C/pix/foliowin.gif b/doc/html/C/pix/foliowin.gif new file mode 100644 index 0000000000..e8a9e52c79 Binary files /dev/null and b/doc/html/C/pix/foliowin.gif differ diff --git a/doc/html/C/pix/newaccwin-code.gif b/doc/html/C/pix/newaccwin-code.gif new file mode 100644 index 0000000000..3de25b520c Binary files /dev/null and b/doc/html/C/pix/newaccwin-code.gif differ diff --git a/doc/html/C/pix/newaccwin-trade.gif b/doc/html/C/pix/newaccwin-trade.gif new file mode 100644 index 0000000000..90572e8d90 Binary files /dev/null and b/doc/html/C/pix/newaccwin-trade.gif differ diff --git a/doc/html/C/pix/newaccwin.gif b/doc/html/C/pix/newaccwin.gif new file mode 100644 index 0000000000..9054787138 Binary files /dev/null and b/doc/html/C/pix/newaccwin.gif differ diff --git a/doc/html/C/pix/recnwin.gif b/doc/html/C/pix/recnwin.gif new file mode 100644 index 0000000000..f23d07982c Binary files /dev/null and b/doc/html/C/pix/recnwin.gif differ diff --git a/doc/html/C/pix/regwin-double.gif b/doc/html/C/pix/regwin-double.gif new file mode 100644 index 0000000000..438c0371f3 Binary files /dev/null and b/doc/html/C/pix/regwin-double.gif differ diff --git a/doc/html/C/pix/regwin-multi.gif b/doc/html/C/pix/regwin-multi.gif new file mode 100644 index 0000000000..c267aabfba Binary files /dev/null and b/doc/html/C/pix/regwin-multi.gif differ diff --git a/doc/html/C/pix/regwin-single.gif b/doc/html/C/pix/regwin-single.gif new file mode 100644 index 0000000000..4a12317f67 Binary files /dev/null and b/doc/html/C/pix/regwin-single.gif differ diff --git a/doc/html/C/pix/regwin-single2.gif b/doc/html/C/pix/regwin-single2.gif new file mode 100644 index 0000000000..62df99ba85 Binary files /dev/null and b/doc/html/C/pix/regwin-single2.gif differ diff --git a/doc/html/C/pix/regwin.gif b/doc/html/C/pix/regwin.gif new file mode 100644 index 0000000000..b0adac908d Binary files /dev/null and b/doc/html/C/pix/regwin.gif differ diff --git a/doc/html/C/pix/report-baln.gif b/doc/html/C/pix/report-baln.gif new file mode 100644 index 0000000000..4a217ddae6 Binary files /dev/null and b/doc/html/C/pix/report-baln.gif differ diff --git a/doc/html/C/pix/report-folio.gif b/doc/html/C/pix/report-folio.gif new file mode 100644 index 0000000000..ee783f9a01 Binary files /dev/null and b/doc/html/C/pix/report-folio.gif differ diff --git a/doc/html/C/pix/report-option.gif b/doc/html/C/pix/report-option.gif new file mode 100644 index 0000000000..5c56f978cb Binary files /dev/null and b/doc/html/C/pix/report-option.gif differ diff --git a/doc/html/C/pix/reportwin.gif b/doc/html/C/pix/reportwin.gif new file mode 100644 index 0000000000..4e67ad8f61 Binary files /dev/null and b/doc/html/C/pix/reportwin.gif differ diff --git a/doc/html/C/pix/ticker-a.gif b/doc/html/C/pix/ticker-a.gif new file mode 100644 index 0000000000..929d67a516 Binary files /dev/null and b/doc/html/C/pix/ticker-a.gif differ diff --git a/doc/html/C/pix/ticker-b.gif b/doc/html/C/pix/ticker-b.gif new file mode 100644 index 0000000000..f0e86e075c Binary files /dev/null and b/doc/html/C/pix/ticker-b.gif differ diff --git a/doc/html/C/projects.html b/doc/html/C/projects.html new file mode 100644 index 0000000000..fbef2c5a90 --- /dev/null +++ b/doc/html/C/projects.html @@ -0,0 +1,1578 @@ + + + + +The people behind GnuCash aim + to create a world-class GPL'ed Open Source Personal Financial + Application for GNU/Linux and other Unix's. This page aims to + review some of the technical and development issues surrounding + this product, representing a sort of FAQ for developers and + contributors, to suggest directions when developers are trying to + determine how to implement new functionality.
+ +To get a better idea of what + GnuCash is and what it does, visit its home page.
+ +There are currently several different versions of + GnuCash.
+ +The latest Gnome version, and latest versions in general, + are currently available only via CVS.
+ +Precompiled versions are available, but usually + only for the stable releases. Don't use the unstable versions + unless you are ready for excitement and adventure, and are + prepared to cope with a need to keep extensive backups.
+ +This document is divided into several sections.
+ +Thus, the Motif or Gnome GUIs are merely two possible + manipulators of the data; others, based on e.g. + Qt/KDE, emacs, Java applets or Java servlets ought to be + possible.
+GnuCash also needs to deal with multiple distributed data + sources: stock quotations from the net or transaction + confirmations from online banks and brokerage houses, or from + more mundane sources, such as file imports, or merger of data + from several users.
+ +Amongst these terms, the concept of a global Model-View is + dated, and somewhat inappropriate. Rather, we need to be + concerned about how data is represented in the local address + space of the GUI, how the GUI manipulates it, how data is + brought in and merged from external sources, and how that data + is again output, whether to a file or a local or remote + database.
+ +Thus, the View essentially represents a local data + cache of the data that is immediately present and being + displayed, reported, and manipulated. The Model is the + abstraction of that data that the GUI (the controller) can act + on.
+ +Currently, the Engine is fairly poor, and is tightly tied + to the data structures that the GUI manipulates. These data + structures include:
+ +The Engine currently handles only a small set of data + sources:
+ +However, since the Engine is meant to be the interface + between the GUI and the financial data, it is really intended + to be able to do much more.
+ +In particular, it should be possible to back the Engine + onto an SQL database, and thereby enable multiple users and/or + interface to more complex accounting systems. The engine should + also be expandable to handle other sources of data, such as + OFX, Integrion GOLD, the Open Trading Protocol, the OMG CORBA + General Ledger submission, the IBM San Francisco business + objects, or closer to home, Linux Kontor. In particular, it + should be possible to use GnuCash not only to view data from + these sources, but also to manipulate it and send it back.
+ +The above structure should leads us to view GnuCash not so + much as a tightly integrated application, but rather as a loose + confederation of component objects, libraries and + interfaces.
+ +In order to facilitate the gluing together of these parts, + as well as simplify the questions of customizability, change + and rapid development, GnuCash makes use of an extension + language to glue the pieces together.
+ +The extension language that is most central to Gnucash is + + Scheme, and in particular, the FSF implementation, Guile, + although some of the interfaces are also available through Perl.
+ +Important properties of a personal finance system + include:
+ +A seemingly contradictory factor is that the kinds of + sophistication that are required vary considerably. + Consider:
+ +Thus, home users don't need much of the + sophistication of an Accounts Receivable or Payable system, + or the bizarre depreciation policies that crop up + in Asset Management systems.
+It may be that these will require completely + different systems, and that GnuCash cannot be "all things to + all people." This remains to be seen.
+ +The right hand column shows a sizing guesstimate. pm == + person-months
+ +| Feature | + +Sizing | +
|---|---|
| + | +|
| Enhanced Engine, Financial + Objects | + +Large | +
| SQL I/O | + +Medium | +
| Multi-User Support | + +Medium | +
| A/R, A/P Accounts Payable, + Receivable | + +Medium | +
| Payroll | + +Medium | +
| Invoicing | + +Medium | +
| Job Costing | + +Medium | +
| Expense Accounts | + +Large | +
Current status:
+ +Other output format possibilities include SGML and Extensible + Markup Language - XML. In the long run, these are + preferable to HTML, since DSSSL tools such as Jade (James DSSSL + Engine) can be used to convert to RTF, Postscript, + etc.
+ +Add to this the consideration that XML is the basis for + the Document Object + Model, which is being integrated into many web-based + applications, and we can see that XML is an increasingly + significant format as we look to the future.
+ +The Report Generator should be a separate but + "dockable" subsystem of the whole.
+ +Thus, it should be possible to run the report generator + in a stand-alone, read-only fashion without having to start + up the main application.
+ +Graphs, charts, etc. too ...
+ +Asset allocation pie chart.
+ +Graph portfolio value vs. cost
+ +One difficult aspect of reporting is designing a + configurable interface, so that people can build custom + reports. The New + Reporting Infrastructure is seeking to build this up + using Guile.
+ +Stock portfolio tools should include a Cost Averaging + report, Market Index report, Stock Option values, + Estimation of capital gains tax liabilities.
+ +Status:
+ +Question: How to most simply allow the user to + enter loads and fees?
+ +Answer: Through splits. Unfortunately, some + users may not properly understand splits, at least not + initially. Thus, a little popup is needed to allow the user + to type in the sales load or fee and such, and then + auto-create the needed splits.
+ +Note the current transfer window does NOT + allow a share price to be specified !! Needs fixing ...
+ + +A set of themes would be desirable for the Gnome + version.
+A user-configurable button-bar would be nice + too.
+Provide a default list of "Categories" + (Income/Expense Accounts). These are categories such as + "Automobile Expense", "Bank Interest Income", and + "Employment Income". The user should be able to select + a default set of accounts, and have those created + automatically.
+ +To actually implement this, it might be best to + simply create a file with these in them, and load that + file. A mechanism should be provided to allow the user + to weed out undesired accounts whilst not preventing + them from using them at a later date, if desired.
+Add an example showing how regular household assets + (house, car, jewelry, etc.) should be treated. In + particular, show how appreciation and depreciation + should be treated.
+Menu navigation using the keyboard should be + possible.
+ +Although menu mnemonics exist, they seem to be + broken.
+ +Similarly, tab-key navigation should be possible. + Currently, it is possible to use the tab key to + navigate from field to field in the register window, to + user arrow keys to navigate menus, and quick-fill to + automatically complete fields. However, it is not + possible to tab over to the "Commit" button.
+ +It should be.
+Currently, Income/Expense accounts can be shown or + hidden by selecting from a menu. It would be nice to be + able to examine different account types (Asset, + Liability, Income, Expense, Payables, Receivables, + Inventory) by selecting a tab folder.
+When the user pauses the mouse over a button, + "fly-over" pop-up help windows should appear.
+Create grayed out entries in the ledger, titled + "Memo", "Description", etc, helping users understand + what should be typed into each field.
+Make sure that text fields can handle the vi and + emacs key bindings, so that e.g. emacs-style + ctrl-a, ctrl-k does the right thing.
+i.e. Ability to permanently lock records as + non-editable. This should be straight-forward by using the + reconciled field to indicate a locked + value, and not allowing the GUI to edit locked records.
+ +Also need to report closed books slightly differently. + Need to bring balances forward too...
+ + +Preferences include things like showing/not showing + categories, forcing double-entry, etc.
+ +Current status:
+ +The overall architecture is envisioned thus:
+ +All code, including the transaction engine, the file + I/O routines, the menus, and the ledger, will be abstracted + into compact modules that can function independently of + each other. At the highest level, there will be a + infrastructure with extension language interfaces that will + "wire together" the various modules.
+ +Such "wiring together" will consist of a dispatch + infrastructure that will allow arbitrary menu entries to be + hooked to arbitrary modules. The configuration for menu + entries, and their associated callbacks, will be specified + in an extension-language configuration file. At the final + stages, it is highly desirable to be able to, in + some manner, import new modules without requiring + that the application itself be recompiled and relinked.
+ +Status:
+ +This should be handled by having a way of bouncing out + to some Guile code to generate transactions with computed + values.
+Status:
+ +Add support for automatic, recurring transactions, + e.g. mortgage payments, fixed-interest bonds, bank + accounts, etc.
+ +Note that the design for this could be very different, + depending on whether the multi-user functions are available + or not.
+ +Design/implementation for this is tricky. It should + probably leverage crontab, but this can lead to + difficulties and bugs.
+ +May need interfaces to email for emailed alerts.
+ +Interfaces into calendaring systems? Current + status:
+ +Note that the above 'step-by-step' budgeters will have + a very very different GUI than what the budgeting system + required for a small-business might look like.
+ +Status:
+ +Status:
+ +Right now, this is a stand-alone perl script run + from crontab.
+OFX is an open spec from Microsoft, Intuit, and + Checkfree, and which will be supported by Integrion. The + OFX DTD's are included in the 1.1 distributions. See OFX Home Page for + details.
+ +There are two ways to build an OFX parser. One way is + to build a compile-time DTD parser that treats the DTD as + if it were an IDL, and generates C language stubs for a + parser.
+ +This approach was attempted and abandoned because it + leads to fragile C code and a very large binary.
+ +Run-time parsing may be slower, but on the OFX client + side, this should not be a bottleneck.
+ +Status:
+ +Note that the organizations developing OFX are looking + to use XML as their "formats of the future;" this may + encourage the use of one of the many XML parsers available + for UNIX.
+Double-entry is a powerful way of ensuring the + integrity of of the financial data. Currently, while + double-entry is supported, its use is not enforced: the + user can create dangling transactions, where only + one account is indicated.
+ +Although this is acceptable for home use (even + desirable, since it allows the casual user the simplicity + they desire), it is not acceptable for business use.
+ +It must be possible to enable forced-double entry, so + that a transaction cannot be completed until two accounts + have been specified.
+ +Current status:
+ +The tab-delimited format should be compatible with that + of /rdb, aka RAND/Hobbs /rdb or + + NoSQL. (NoSQL is available as part of the Debian GNU/Linux distribution, + for instance.)
+ +The /rdb format is thus:
++field-name tab fieldname tab fieldname \n +------------------------------------------ \n +value tab value tab value \n +value tab value tab value \n +etc ... ++ +
It is a very simple, very basic flat table format. The + use of /rdb with GnuCash should try to match with + SQL schemas as much as possible in order to minimize I/O + complexity and incompatibility.
+categorize items according to different tax + schedules
+The current engine is rather simple: it provides + support for accounts, account hierarchies and transactions + consisting of multiple entries.
+ +Many of the features described elsewhere will require + that the engine have a far richer, more sophisticated data + model, including such things as:
+ +Note: it makes no sense at this point to make the + engine API much richer than what the GUI can currently + support.
+ +In a business environment, the auditors may have + "signed off" on the validity of the data; at that + point, the ability to modify audited data should be + very tightly controlled, or even downright + forbidden.
+Current Status:
+ +These "Transaction processing constructs" should + simplify creation of an SQL back end, or some other + more sophisticated database engine.
+There has been much discussion about this on + mailing lists both for GnuCash and CBB. Major + points have included:
+ +This may be a minor cost to a business enterprise + that hires DataBase Administrators.
+ +It is not acceptable to require this of + naive users that may find "simple" things like
++% su - +Password: +# cd /tmp +# rpm -i gnucash-4.1.3.i386.rpm +# exit ++ to be challenging. +
Changing GnuCash to be suited to use a DBMS in + other than a "load-it-all" / "dump-it-all" manner, but + to rather update the database in a transactional + manner.
+ +That being said, it may be possible to recast the + GnuCash engine functionality so as to handle + storage in a transactional manner.
+The following industrial-strength features are + needed:
+ +While the GnuCash "engine" might remain free, + maintenance of payroll functionality would require + "subscribing" to an update scheme; it might be troublesome + to try to provide such a "subscription" free of charge.
+Linas Vepstas
+ linas@linas.org
+
Christopher Browne
+ cbbrowne@ntlug.org
+
GnuCash is a program to keep track of your finances. Its + features include:
+ +If you can use the register in the back of your + checkbook, you can use GnuCash.
+At the end of the month, open up the reconcile + 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.
+If you begin typing in the description field, and the + text matches a previous transaction, hitting TAB + will copy in that previous transaction. This is a handy + time saver if you regularly create similar + transactions.
+Track stocks individually (one per account) or in + portfolio of accounts (a group of accounts that can be + displayed together).
+ +There are tools to + automatically collect stock quotes.
+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.
+Imports Quicken-style QIF files.
+GnuCash offers some features not found in simpler + accounting programs.
+ +A master account can have a hierarchy of more detailed + accounts arranged underneath it. This allows related + account types (e.g. - Cash, Bank, Stock) to be + grouped under one master account ( e.g. - + Assets).
+Every transaction involves two accounts, and each + transaction is required to balance. This provides + assurance that the overall set of books will add up + correctly, and prevents out-of-balance errors + altogether.
+Intuit's Quicken + product has what they call "categories" that are used to + track incomes and expenses. These may be used to create + Profit/Loss reports.
+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.
+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.
+ +The present "experimental" stream is gnucash-1.3.x, which + is somewhat unstable.
+ +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.
+ +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.
+ +If you wish to "hack" on the experimental version, you + should first start by reading through the GnuCash Project Goals document in order to + get some perspective on the overall design.
+ +The cast of thousands includes:
+ +| Version | + +engine | + +register | + +ledger | + +motif | + +gnome | + +qt | + +prefs (scm) | + +docs (html) | + +misc | + +Total | +
|---|---|---|---|---|---|---|---|---|---|---|
| xacc-0.9 + Sept 97 |
+
+ - | + +- | + +- | + +34 files + (7.5+0.9) |
+
+ - | + +- | + +- | + +5 files + (0.4) |
+
+ - | + +39 files + (8.8) |
+
| xacc-0.9w + Dec 97 |
+
+ - | + +- | + +- | + +51 files + (13.8+1.5) |
+
+ - | + +- | + +- | + +9 files + (0.8) |
+
+ - | + +60 files + (16.1) |
+
| xacc-1.0.17 + Feb 98 |
+
+ - | + +- | + +- | + +52 files + (14.8+1.8) |
+
+ - | + +- | + +- | + +12 files + (1.4) |
+
+ - | + +64 files + (18.0) |
+
| gnucash-1.1.15 + Aug 98 |
+
+ 24 files + (6.2+1.5) |
+
+ 31 files + (6.1+1.7) |
+
+ 5 files + (1.4+0.4) |
+
+ 30 files + (7.4+0.7) |
+
+ 17 files + (3.4+0.5) |
+
+ 16 files + (1.2+0.2) |
+
+ 3 files + (0.3) |
+
+ 16 files + (1.9) |
+
+ not counted + (>1.0) |
+
+ 142 files + (32.9) |
+
Each cell contains:
+
+ number of *c and *.h files
+ (KLOCS in *.c + KLOCS in *.h),
where KLOC == kilo-lines-of-code, as reported by + wc.
+Return to Main Documentation + Page.
+ + + diff --git a/doc/html/C/xacc-accountedit.html b/doc/html/C/xacc-accountedit.html new file mode 100644 index 0000000000..14f1ca97ff --- /dev/null +++ b/doc/html/C/xacc-accountedit.html @@ -0,0 +1,30 @@ + + + +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 new accounts.
+ +Account information can be changed by typing in the appropriate + field. The account type cannot be changed.
+A new Parent Account can be selected. Only those accounts that + can legally become the parent of the present account are shown.
+The source for Stock Quotes can be selected. FIXME: + could somebody who uses this feature please document it?>
+Notes about the account can be edited.
+ + +Return to Main Documentation + Page.
+ + + diff --git a/doc/html/C/xacc-acctypes.html b/doc/html/C/xacc-acctypes.html new file mode 100644 index 0000000000..eb0473b746 --- /dev/null +++ b/doc/html/C/xacc-acctypes.html @@ -0,0 +1,151 @@ + + + + +Return to Main Documentation + Page.
+ + + diff --git a/doc/html/C/xacc-accwin.html b/doc/html/C/xacc-accwin.html new file mode 100644 index 0000000000..50f0993abd --- /dev/null +++ b/doc/html/C/xacc-accwin.html @@ -0,0 +1,46 @@ + + + + +This is what a new account window looks like:
+ + 
Pick an Account + Type.
+ +The Currency field should typically be a three-letter ISO curency code + (e.g. - USD for U.S. Dollars). The + Account Code is a number that determines the sort order of the account + when it appears in a report or in the Chart of Accounts.
+ +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 + stock-ticker symbol, or a three-letter ISO currency + code.
+ +
+ 
+
Return to Main Documentation + Page.
+ + + diff --git a/doc/html/C/xacc-adjbwin.html b/doc/html/C/xacc-adjbwin.html new file mode 100644 index 0000000000..892705e9a4 --- /dev/null +++ b/doc/html/C/xacc-adjbwin.html @@ -0,0 +1,25 @@ + + + + +Add more documentation here.
+Return to Main Documentation + Page.
+ + + diff --git a/doc/html/C/xacc-apar.html b/doc/html/C/xacc-apar.html new file mode 100644 index 0000000000..b4a074fcbd --- /dev/null +++ b/doc/html/C/xacc-apar.html @@ -0,0 +1,192 @@ + + + + + + +A/R (Accounts Receivable) and A/P (Accounts Payable) are + somewhat deep, and require thought to fully understand + them.
+ +First, let us examine A/R. After all, we really shouldn't + really need to relate to A/P because we always pay + our bills on time, don't we ? :-)
+ +As a first approximation, let us assume we don't require + customers to pay instantly, 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 :-)).
+ +When we make a sale, the two accounts affected are + Sales (an income account) and Accounts Receivable. + Accounts Receivable is an asset, but it's not "liquid," as you + can't readily sell it, and it's certainly not cash.
+ +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.
+ +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 + establishing obligations.
+ +In more sophisticated operations, there may be a much + larger sequence of documents generated and tracked:
+ +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."
+ +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 + way overdue.
+ +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 + Bad Debt.
+ +At that point, it is typical to record an entry thus:
+ +| Account | + +DR | + +CR | +
|---|---|---|
| Bad Debt Expense | + +$10,000 | + ++ | +
| + | +||
| Accounts Receivable | + ++ | + +$10,000 | +
We could have reduced Sales Income instead, but + companies tend to prefer to specifically track the amount that + they're losing to bad customers.
+ +Warning: Advanced Accounting Concept. Bad Debt + is an example of a "contra-account." That doesn't refer to + amounts paid to Nicaraguan rebels, 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. Accumulated Depreciation, used + to diminish the value of an asset over time, is another example + of a contra-account.
+ +The scenario for Accounts Receivable, reversed, reflects + how Accounts Payables work; just switch customer with supplier, + and see how the roles reverse.
+ +Analagous techniques are also used for expenses that are + prepaid.
+ +If you have to pay out down six months of rent in advance, + that is treated as an "accrued asset."
+ +While this puts an unfortunate dent in the Cash + account, it does show on the books as an asset, + and there are no more payments to make for the next six + months.
+Similarly, companies collect payroll taxes on behalf of + employees, and keep them in a special bank account.
+ +Return to Main Documentation + Page.
+ + + diff --git a/doc/html/C/xacc-apprdepr.html b/doc/html/C/xacc-apprdepr.html new file mode 100644 index 0000000000..1b14b79fab --- /dev/null +++ b/doc/html/C/xacc-apprdepr.html @@ -0,0 +1,716 @@ + + + + + + +This section provides a treatment of the handling of + depreciation and appreciation of assets in GnuCash.
+ +It also provides a brief introduction to the related tax + issues.
+ +Warning: Be aware that different countries can + have substantially 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.
+ +Note that appreciation and depreciation of assets tend to + be treated somewhat differently:
+ +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.
+Unlike depreciation, governments tend to be quite + interested in taxing capital gains in one manner or + another.
+ +(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 accrued interest, or imputed + interest are often there to scare those that are + sensitive to such things...)
+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 + until you actually sell the asset.
+ +If you invest in securities + 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 Market Order.
+ +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.
+ +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.
+ +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 worthless outside of that very + specific context. In such cases, there several conflicting + values might be attached to the asset, none of them + unambiguously correct.
+ +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.)
+ +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):
+ +The accrued gains likely won't affect your taxable + income for income tax purposes, although it could + have some effect on property taxes.
+ +The first thing you have to do is to create the asset + cost account, then transfer the sum you paid for this + painting from your bank account to this asset account to record + the purchase.
+ +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 accrued gains on asset + income account to your asset account.
+ +Your main window will resemble this:
+
+
+ and your asset account will resemble this:
+
+
+ Asset appreciation is a sort of income but it is + not cash in hand.
+ +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 + theoretically valued at millions of dollars USD.
+ +That doesn't mean that they are actually millionaires; the + principal participants have to hold their stock for at least + six months before selling any of it. The fact that + they can't 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 get those + millions.
+ +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.
+ +Now there arise three possibilities:
+ +The income account is left alone (or perhaps gets + transferred from an Accrued Gain income to a + Realized Gain income account), and the recording is + rather like:
+ +| Account | + +Amount | +
|---|---|
| Cash | + +$16055 | +
| Painting | + +-$11000 | +
| Realized Gain Income | + +-$5055 | +
And if any amounts had been accrued as Accrued + Gains, the asset amount should be closed out, offset + by a negative value for Accrued Gain + income. If the total that had been accrued was $5000, then + the transaction might look like the following:
+ +| Account | + +Amount | +
|---|---|
| Cash | + +$16055 | +
| Painting | + +-$11000 | +
| Accrued Gain Asset | + +-$5000 | +
| Realized Gain Income | + +-$5055 | +
| Accrued Gain Income | + +$5000 | +
Note that the two income accounts offset one another so + that the current income resulting from the + transaction is only $55. The remaining $5000 had previously + been recognized as Accrued Gain Income.
+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.
+ +The numbers change a little bit, but not too + dramatically.
+ +| Account | + +Amount | +
|---|---|
| Cash | + +$15000 | +
| Painting | + +-$11000 | +
| Accrued Gain Asset | + +-$5000 | +
| Realized Gain Income | + +-$4000 | +
| Accrued Gain Income | + +$5000 | +
Note that the two income accounts offset one another so + that the current income resulting from the + transaction turns out to be a loss of $1000. + That's fine, as you had previously recognized $5000 in + income.
+The extra value is, again, recorded as a gain, + i.e. an income.
+ +| Account | + +Amount | +
|---|---|
| Cash | + +$50000 | +
| Painting | + +-$11000 | +
| Accrued Gain Asset | + +-$5000 | +
| Realized Gain Income | + +-$39000 | +
| Accrued Gain Income | + +$5000 | +
In practice, it truly is important to keep the Accrued + Gain Income separate from the Realized Gain + Income, as the former is likely to be ignored by your tax + authorities, who will only care to charge you on the + Realized Gain.
+ +Below, we show the second case discussed.
+
+
+ As we see in this example, for non-financial assets, it may + be difficult to correctly estimate the ``true'' value of an + asset.
+ +It is quite easy to count yourself rich based on + questionable estimates that do not reflect "money in the + bank."
+ +Thus, when dealing with appreciation of assets,
+ +Do not indulge in wishful thinking.
+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.
+ +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.
+ +Be aware: all too many companies that appear + "profitable" on paper go out of business as a result of + running out of cash, precisely because "valuable + assets" were not the same thing as cash.
+Taxation policies vary considerably between countries, so + it is virtually impossible to say anything that will be + universally useful.
+ +However, it is common 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.
+ +North American home owners usually 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.
+ +I have one story + from my professional tax preparation days where a family sold a + farm, and expected a considerable 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 dairy farm, with some + really peculiar resulting deductions.
+ +In short, this presentation is fairly simple, but taxation + often gets terribly complicated...
+ +Compared to the often uncertain estimates one has to do + where appreciation of assets is concerned, we are on somewhat + firmer ground here.
+ +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.
+ +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.
+ +Linear depreciation diminishes the value of an asset by a + fixed amount each period until the net value is zero. This is + the simplest calculation, as you estimate a useful + lifetime, and simply divide the cost equally across that + lifetime.
+ +Example: 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:
+
| Year | + +Depreciation | + +Remaining Value | +
|---|---|---|
| 1 | + +300 | + +1200 | +
| 2 | + +300 | + +900 | +
| 3 | + +300 | + +600 | +
| 4 | + +300 | + +300 | +
| 5 | + +300 | + +0 | +
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 ( i.e. - a resale + value).
+ +Beware: Tax authorities may require (or allow) a + larger percentage in the first period. On the other hand, + in Canada, this is reversed, as they permit only a + half share of "Capital Cost Allowance" in the first + year.
+ +The result of this approach is that asset value decreases + more rapidly at the beginning than at the end which is + probably more realistic for most assets than a linear + scheme. This is certainly true for automobiles.
+ +Example: We take the same example as above, + with an annual depreciation of 30%.
+ +| Year | + +Depreciation | + +Remaining Value | +
|---|---|---|
| 1 | + +450 | + +1050 | +
| 2 | + +315 | + +735 | +
| 3 | + +220.50 | + +514.50 | +
| 4 | + +154.35 | + +360.15 | +
| 5 | + +108.05 | + +252.10 | +
A third method most often employed in Anglo/Saxon countries + is the "sum of digits" method. Here is an illustration:
+ +Example: First you divide the asset value + by the sum of the years of use, e.g. 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:
+ +| Year | + +Depreciation | + +Remaining Value | +
|---|---|---|
| 1 | + +100*5=500 | + +1000 | +
| 2 | + +100*4=400 | + +600 | +
| 3 | + +100*3=300 | + +300 | +
| 4 | + +100*2=200 | + +100 | +
| 5 | + +100*1=100 | + +0 | +
In order to keep track of the depreciation of an asset, you + need :
+ +The first step, again, is to record the purchase of your + asset by transferring the money from bank bank account to the + asset cost account. Afterwards, in each accounting + period you record the depreciation as an expense in the + appropriate account.
+ +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.
+
+
+
+ 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 or required to use.
+ +Return to Main Documentation + Page.
+ + + diff --git a/doc/html/C/xacc-bal_tracker.html b/doc/html/C/xacc-bal_tracker.html new file mode 100644 index 0000000000..b62444939b --- /dev/null +++ b/doc/html/C/xacc-bal_tracker.html @@ -0,0 +1,17 @@ + + + + +FIXME: Document this report! +
Return to Main Documentation + Page.
+ + + diff --git a/doc/html/C/xacc-balsheet.html b/doc/html/C/xacc-balsheet.html new file mode 100644 index 0000000000..daecaefe26 --- /dev/null +++ b/doc/html/C/xacc-balsheet.html @@ -0,0 +1,21 @@ + + + + + +This report summarizes your assets, liabilities, and equity.
+ +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.
+ +Return to Main Documentation + Page.
+ + diff --git a/doc/html/C/xacc-currency.html b/doc/html/C/xacc-currency.html new file mode 100644 index 0000000000..2d37e1d143 --- /dev/null +++ b/doc/html/C/xacc-currency.html @@ -0,0 +1,1209 @@ + + + + +A Double Entry bookkeeping + system stores both values, and requires that all + transactions balance, as described in the Double Entry Identity.
+ +When we introduce the notion of having multiple currencies, + or stocks that may vary in price, the identities get a little + more complicated, and we introduce the following formulae:
+ +Thus, buying a widget in Japan (JPY) and using US Dollars + (USD) to pay for it would appear thus:
+ ++Date xfer from memo cost +1/5/99 [JPYAcct] Buy widget $1.00 + ++
+Date xfer from memo purchase rate +1/5/99 [SpendAcct] Buy widget Y150 0.00667 + ++
The engine links together all three of these values + (1.0, 150, 0.00667) permanently and makes it imposssible + to change one without changing another, so that the grand total + is always zero, thereby guaranteeing satisfaction of the double entry accounting + identity.
+ +More currencies than you thought possible...
+ +| ISO Code | + +Full Description | +
|---|---|
| + | +|
| ADP | + +Andoran peseta | +
| AED | + +United Arab Emirates Dirham | +
| AFA | + +Afghani | +
| ALL | + +Albanian Lek | +
| AMD | + +Armenian Dram | +
| ANG | + +West Indian Guilder | +
| AOK | + +Angolan Kwanza | +
| ARA | + +Argentinian Austral | +
| ARS | + +Argentina Peso | +
| ATS | + +Austrian Schilling | +
| AUD | + +Australian Dollar | +
| AWG | + +Aruban Guilder | +
| AZM | + +Azerbaijan Manat | +
| BAD | + +Bosnia-Herzogovinian Dinar | +
| BBD | + +Barbados Dollar | +
| BDT | + +Bangladesh Taka | +
| BEF | + +Belgian Franc | +
| BGL | + +Bulgarian Lev | +
| BHD | + +Bahrain Dinar | +
| BIF | + +Burundi Franc | +
| BMD | + +Bermudan Dollar | +
| BND | + +Brunei Dollar | +
| BOB | + +Bolivian Boliviano | +
| BRL | + +Brazilian Real | +
| BRR | + +Brazil | +
| BSD | + +Bahaman Dollar | +
| BWP | + +Botswana Pula | +
| BYR | + +Belorussian Ruble | +
| BZD | + +Belize Dollar | +
| CAD | + +Canadian Dollar | +
| CDP | + +Santo Domiongo | +
| CHF | + +Swiss Franc | +
| CLP | + +CHILEAN PESO | +
| CNY | + +China | +
| COP | + +Colombian Peso | +
| CRC | + +Costa Rica Colon | +
| CUP | + +Cuban Peso | +
| CVE | + +Cape Verde Escudo | +
| CYP | + +Cyprus Pound | +
| CZK | + +Czech Krona | +
| DEM | + +German Mark | +
| DJF | + +Djibouti Franc | +
| DKK | + +Danish Krone | +
| DOP | + +Dominican Peso | +
| DRP | + +Dominican Republic Peso | +
| DZD | + +Algerian Dinar | +
| ECS | + +ECUADORIAN SUCRE | +
| ECS | + +Ecuador Sucre | +
| ECU | + +European Currency Unit | +
| EEK | + +Estonian Krone | +
| EGP | + +Egyptian Pound | +
| ESP | + +Spanish Peseta | +
| ETB | + +Ethiopian Birr | +
| EUR | + +Currency of EMU member states | +
| FIM | + +Finnish Mark | +
| FJD | + +Fiji Dollar | +
| FKP | + +Falkland Pound | +
| FRF | + +French Franc | +
| GBP | + +British Pound | +
| GEK | + +Georgian Kupon | +
| GHC | + +Ghanian Cedi | +
| GIP | + +Gibraltar Pound | +
| GMD | + +Gambian Dalasi | +
| GNF | + +Guinea Franc | +
| GRD | + +Greek Drachma | +
| GTQ | + +Guatemalan Quedzal | +
| GWP | + +Guinea Peso | +
| GYD | + +Guyanese Dollar | +
| HKD | + +Hong Kong Dollar | +
| HNL | + +Honduran Lempira | +
| HRD | + +Croatian Dinar | +
| HTG | + +Haitian Gourde | +
| HUF | + +Hungarian forint | +
| IDR | + +Indeonesian Rupiah | +
| IEP | + +Irish Pound | +
| ILS | + +Israeli Scheckel | +
| INR | + +Indian Rupee | +
| IQD | + +Iraqui Dinar | +
| IRR | + +Iranian Rial | +
| ISK | + +Iceland Krona | +
| ITL | + +Italian Lira | +
| JMD | + +JAMAICAN DOLLAR | +
| JOD | + +Jordanian Dinar | +
| JPY | + +Japanese Yen | +
| KES | + +Kenyan Shilling | +
| KHR | + +Cambodian Riel | +
| KIS | + +Kirghizstan Som | +
| KMF | + +Comoros Franc | +
| KPW | + +North Korean Won | +
| KRW | + +South Korean Won | +
| KWD | + +Kuwaiti Dinar | +
| KYD | + +Cayman Dollar | +
| KZT | + +Kazakhstani Tenge | +
| LAK | + +Laotian Kip | +
| LBP | + +Lebanese Pound | +
| LKR | + +Sri Lankan Rupee | +
| LRD | + +Liberian Dollar | +
| LSL | + +Lesotho Loti | +
| LTL | + +Lithuanian Lita | +
| LUF | + +Luxembourgian Franc | +
| LVL | + +Latvian Lat | +
| LYD | + +Libyan Dinar | +
| MAD | + +Moroccan Dirham | +
| MDL | + +Moldavian Lei | +
| MGF | + +Madagascan Franc | +
| MNC | + +Monaco | +
| MNT | + +Mongolian Tugrik | +
| MOP | + +Macao Pataca | +
| MRO | + +Mauritanian Ouguiya | +
| MTL | + +Maltese Lira | +
| MUR | + +Mauritius Rupee | +
| MVR | + +Maldive Rufiyaa | +
| MWK | + +Malawi Kwacha | +
| MXN | + +Mexican Peso (new) | +
| MXP | + +Mexican Peso (old) | +
| MYR | + +Malaysian Ringgit | +
| MZM | + +Mozambique Metical | +
| NGN | + +Nigerian Naira | +
| NIC | + +Nicaragua | +
| NIO | + +Nicaraguan Cordoba | +
| NIS | + +Isreal | +
| NLG | + +Dutch Guilder | +
| NOK | + +Norwegian Krone | +
| NPR | + +Nepalese Rupee | +
| NZD | + +New Zealand Dollars | +
| OMR | + +Omani Rial | +
| PAB | + +Panamanian Balboa | +
| PEI | + +Peruvian Inti | +
| PEN | + +Peruvian Sol - New | +
| PES | + +Peruvian Sol | +
| PGK | + +Papua New Guinea Kina | +
| PHP | + +Philippino Peso | +
| PKR | + +Pakistan Rupee | +
| PLN | + +Polish Zloty | +
| PLZ | + +Poland | +
| PTE | + +Portuguese Escudo | +
| PYG | + +Paraguayan Guarani | +
| QAR | + +Qatar Riyal | +
| RMB | + +Chinese Renminbi Yuan | +
| ROL | + +Roumanian Lei | +
| RUR | + +Russian Rouble | +
| RWF | + +Rwanda Franc | +
| SAR | + +Saudi Riyal | +
| SBD | + +Solomon Islands Dollar | +
| SCR | + +Seychelles Rupee | +
| SDP | + +Sudanese Pound | +
| SEK | + +Swedish Krona | +
| SGD | + +Singapore Dollar | +
| SHP | + +St.Helena Pound | +
| SIT | + +Slovenian Tolar | +
| SKK | + +Slovakian Krona | +
| SLL | + +Leone | +
| SOL | + +Peru | +
| SOS | + +Somalian Shilling | +
| SRG | + +Surinam Guilder | +
| STD | + +Sao Tome / Principe Dobra | +
| SUR | + +Russian Ruble (old) | +
| SVC | + +El Salvador Colon | +
| SYP | + +Syrian Pound | +
| SZL | + +Swaziland Lilangeni | +
| THB | + +Thailand Baht | +
| TJR | + +Tadzhikistani Ruble | +
| TMM | + +Turkmenistani Manat | +
| TND | + +Tunisian Dinar | +
| TOP | + +Tongan Pa'anga | +
| TPE | + +Timor Escudo | +
| TRL | + +Turkish Lira | +
| TTD | + +Trinidad and Tobago Dollar | +
| TWD | + +New Taiwan Dollar | +
| TZS | + +Tanzanian Shilling | +
| UAK | + +Ukrainian Karbowanez | +
| UGS | + +Ugandan Shilling | +
| USD | + +American Dollar | +
| UYP | + +Uruguayan New Peso | +
| UYU | + +Uruguay | +
| VEB | + +Venezuelan Bolivar | +
| VND | + +Vietnamese Dong | +
| VUV | + +Vanuatu Vatu | +
| WST | + +Samoan Tala | +
| XAF | + +Gabon C.f.A Franc | +
| XCD | + +East Carribean Dollar | +
| XOF | + +Benin C.f.A. Franc | +
| YER | + +Yemeni Ryal | +
| ZAR | + +South African Rand | +
| ZMK | + +Zambian Kwacha | +
| ZRZ | + +Zaire | +
| ZWD | + +Zimbabwean Dollar | +
Return to Main Documentation + Page.
+ + + diff --git a/doc/html/C/xacc-date.html b/doc/html/C/xacc-date.html new file mode 100644 index 0000000000..8231fcb877 --- /dev/null +++ b/doc/html/C/xacc-date.html @@ -0,0 +1,45 @@ + + + + +Return to Main Documentation + Page.
+ + + diff --git a/doc/html/C/xacc-double.html b/doc/html/C/xacc-double.html new file mode 100644 index 0000000000..5ada2964fa --- /dev/null +++ b/doc/html/C/xacc-double.html @@ -0,0 +1,156 @@ + + + + +Double entry bookkeeping is an accounting methodology + introduced in the 13th century to to make sure that each + accounts and indeed each transaction is properly + balanced.
+ +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.
+ +A double-entry transaction is a transaction that contains + entries for two (or more) accounts that balance against one + another. One account is debited by an amount exactly + equal to what the other is credited. 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 I forgot to enter + that part of the transaction errors.
+ +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 + have to have another component to that transaction to + balance this.
+ +Not-quite-an-aside: If you look at your bank + statements, they are typically written up from the + bank's perspective, which is exactly opposite to + yours. For instance, when you put money in, establishing a + deposit, this establishes a DEBT on their part.
+ +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 + Income/Expense page for a more detailed discussion of + that.
+ + + +The fact that the identity requires merely that the + total balances means that it is a little bit misleading to + call this double-entry bookkeeping; it would be + somewhat more accurate to call it multiple-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!)
+ +GnuCash treats "Debits" as positive values, and "Credits" + as negative values, so that this identity simplifies to + value1 + value2 + value3 + ... + = 0
+ +To create a double-entry transaction:
+ +A menu will drop down, listing all of the accounts from + which a transfer may be made.
+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.
+To change a double-entry transaction:
+ +Simply edit the transaction in any window in which it + appears.
+ +Any changes made will be automatically reflected in both + accounts and all windows displaying the transaction.
+ +Similarly, when a double-entry transaction is deleted, the + "splits" will be deleted from both accounts, and balances will + automatically be recalculated for both accounts.
+ +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.
+ +GnuCash can be configured to be strict about double entry, + or you may configure it to be "loose."
+ +In "loose" mode, you can create unbalanced + transactions, 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:
+ +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 Scrub the account clean by choosing + Scrub 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 + Unbalanced. You may then review these splits and move them + to their proper accounts.
+Return to Main Documentation + Page.
+ + + diff --git a/doc/html/C/xacc-expense.html b/doc/html/C/xacc-expense.html new file mode 100644 index 0000000000..4a5174f652 --- /dev/null +++ b/doc/html/C/xacc-expense.html @@ -0,0 +1,209 @@ + + + + + +The words "Income" and "Expense" are beguilingly simple; + everyone thinks they know what they mean; this + usually is that When I spend something, this is an + expense, and when I get money, this is an income.
+ +This oversimplifies things somewhat; it is often a + good-enough 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."
+ +For instance, companies usually have to recognize income + when the sale occurs. That may mean that I have to + recognize a $100,000 sale at the moment I and the customer + shake hands on the deal.
+ +Since the money hasn't come in, the sale has to be + estimated in other way; the way this is done is to + accrue 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 Accounts Receivable.
+ +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.)
+ +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).
+ +Another way of describing the requirement for "double + entry" is that when you receive an income, two things + happen:
+ +When, for instance, salary is deposited in a bank account, + the bank account is credited, and the income account is + debited, thus:
+ +| Account | + +Debit | + +Credit | +
|---|---|---|
| Chequing Account | + +1,600.00 | + ++ | +
| Salary | + ++ | + +1,600.00 | +
This may be readily extended to a greater number of "split" + items thus:
+ +| Account | + +Debit | + +Credit | +
|---|---|---|
| Chequing Account | + +1,300.00 | + ++ | +
| Income Taxes | + +200.00 | + ++ | +
| Health Plan | + +100.00 | + ++ | +
| Salary | + ++ | + +1,600.00 | +
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.
+ +If, as with GnuCash, everything is forced onto one + column, so that debits are represented by positive + values, and credits are represented by negative values, + the income/expense accounts do a slightly non-intuitive thing + and you see incomes as negative values. That + appears contrary to intuition, but is nonetheless + necessary in order for the + double-entry bookkeeping identity to hold true.
+ +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.
+ +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 equity.
+ +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, they correspondingly do + not appear on a P&L statement.
+ +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.
+ +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 causes for such + transfers tend to be somewhat peculiar, so it's pretty fair for + this to be a pretty odd situation.)
+ +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.
+ +You will doubtless wish to create quite a number of income + and expense accounts; it may be worth looking at the Sample Chart of Accounts + for ideas.
+ +This partitioning of incomes and expenses is likely to + prove particularly useful for North Americans when income + tax time rolls around.
+ +If you have used other personal finance software, be aware + that Quicken calls + them "Categories."
+Return to Main Documentation + Page.
+ + + diff --git a/doc/html/C/xacc-globalprefs.html b/doc/html/C/xacc-globalprefs.html new file mode 100644 index 0000000000..7adc8b9d21 --- /dev/null +++ b/doc/html/C/xacc-globalprefs.html @@ -0,0 +1,42 @@ + + + + +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.
+ +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.
+ +The settings are grouped into the following categories:
+Return to Main Documentation + Page.
+ + + diff --git a/doc/html/C/xacc-globalprops.html b/doc/html/C/xacc-globalprops.html new file mode 100644 index 0000000000..7adc8b9d21 --- /dev/null +++ b/doc/html/C/xacc-globalprops.html @@ -0,0 +1,42 @@ + + + + +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.
+ +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.
+ +The settings are grouped into the following categories:
+Return to Main Documentation + Page.
+ + + diff --git a/doc/html/C/xacc-gpl.html b/doc/html/C/xacc-gpl.html new file mode 100644 index 0000000000..491ba2c470 --- /dev/null +++ b/doc/html/C/xacc-gpl.html @@ -0,0 +1,341 @@ + + + + + + +Everyone is permitted to copy and distribute verbatim + copies of this license document, but changing it is not + allowed.
+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.
+ +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.
+ +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.
+ +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.
+ +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.
+ +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.
+ +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.
+ +The precise terms and conditions for copying, distribution + and modification follow.
+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".
+ +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.
+ +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.
+ +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.
+ +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:
+ ++ a) You must cause the modified files to carry prominent + notices stating that you changed the files and the date of + any change. + ++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.
+ +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.)
+
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.
+ +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.
+ +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:
+ ++ 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, + ++ +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,
+ +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.)
+
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.
+ +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.
+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.
+ +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.
+ +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.
+ +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.
+ +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.
+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.
+ +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.
+ +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.
+ +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.
+ +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.
+ +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.
+ +Return to Main Documentation + Page.
+ + + diff --git a/doc/html/C/xacc-groups.html b/doc/html/C/xacc-groups.html new file mode 100644 index 0000000000..050a83db1f --- /dev/null +++ b/doc/html/C/xacc-groups.html @@ -0,0 +1,377 @@ + + + + + + +Typically accounts are arranged as a tree, in hierarchical + form.
+ +The main branches represent entire categories or groups, + while the leaves of the tree denote individual bank accounts or + expense categories.
+ +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:
++ 300 Expenses + | + +--310 Living Expenses + | | + | +--311 Beer + | | + | +--312 Cable + | + +--320 Business Expenses + | | + | +--321 8-inch Floppies + | | + : : ++ +
Note that accounts not only have names; they have + codes, in order to provide order. When a report + is generated, the sort order is determined + by the numbering.
+ +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:
+ +When you create a new + account, 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, a through z.
+ +A "typical" chart of accounts is shown below. Each + account is of a given account + type. This example is a combination of some typical + business and personal accounts.
+ >>>>>>> 1.2 + +Return to Main Documentation + Page.
+ + + diff --git a/doc/html/C/xacc-main.html b/doc/html/C/xacc-main.html new file mode 100644 index 0000000000..84d6fe7347 --- /dev/null +++ b/doc/html/C/xacc-main.html @@ -0,0 +1,105 @@ + + + + + + +The following documentation is about the + implementation of GnuCash as opposed to being user + documentation on how to use it.
+ +Some of it represents preliminary documentation for + subsystems that are not yet sufficiently functional for use by + end users.
+ +The reporting subsystem is presently undergoing active + development; documentation should eventually include:
+ +This is the main account window. You control your set of + accounts from here.
+ +Below is a picture of the main window, with only the main + accounts shown. Note how Business Expenses 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.
+ + 
+
Here is the main window, with the detail accounts + showing.
+ +
+ 
+
The Open Subaccounts 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 Open Subaccounts 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.
+ +Return to Main Documentation + Page.
+ + + diff --git a/doc/html/C/xacc-pnl.html b/doc/html/C/xacc-pnl.html new file mode 100644 index 0000000000..1f41177748 --- /dev/null +++ b/doc/html/C/xacc-pnl.html @@ -0,0 +1,20 @@ + + + + + +This report summarizes your sources of income and expenditure.
+ +There are currently no options for this report, but the option + to specify an accounting period will be added soon.
+ +Return to Main Documentation + Page.
+ + diff --git a/doc/html/C/xacc-print-check.html b/doc/html/C/xacc-print-check.html new file mode 100644 index 0000000000..7c148ece69 --- /dev/null +++ b/doc/html/C/xacc-print-check.html @@ -0,0 +1,97 @@ + + + + + + +You may print a GnuCash transaction as a check by selecting + "Print Check" from the Transaction menu in a register display + window. + +
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 OK + will take you to the GnuCash Printing + dialog, which will allow you to preview the check, select a + printer and paper size, and start the print job. + +
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. + +
By default, the check format is Quicken/QuickBooks, + which prints to any Quicken-compatible check forms. + +
If you wish to print to a type of check form that is not in + the Check Format option menu, select Custom in + the format menu and enter the positions of the various check + fields in the entry boxes below. + +
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 Units + option menu are used to interpret all values entered in the custom + check format area. + +
If you arrive at a working set of Custom Check Format + parameters for a commercially-available printable check form, + please submit them to gnucash-devel@gnucash.org so we can + include them as standard in a future release. + +
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. Top, + Middle, and Bottom should be defined correctly + for check forms using the paper size that you select in the + printing dialog. + +
If the preset check positions do not work correctly for your + check forms, you may choose Custom from the Check + Position option menu and enter a position for the check in the + Check Position 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. + +
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. + +
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. + +
If you wish to use another date format besides those available + in the picker, select Custom and enter a + date-formatting string in the Date Format entry in the + custom settings area. If custom date format is selected, this + string is passed to strftime(3) as a format specifier. + + + + diff --git a/doc/html/C/xacc-print.html b/doc/html/C/xacc-print.html new file mode 100644 index 0000000000..4e85d84e49 --- /dev/null +++ b/doc/html/C/xacc-print.html @@ -0,0 +1,52 @@ + + + +
+ + +At present, the only type of printing directly supported by + GnuCash is check printing. + Other types of printing are expected to be supported soon. + +
You may create a printout of the register + window contents by opening a register window and selecting + Print... To File from the File menu. + Reports can also be + exported as HTML. + +
Following the latest fashionable trends of Internet + Hype, GnuCash can also act as a cheesy web server!
+ +Return to Main Documentation + Page.
+ + + diff --git a/doc/html/C/xacc-qif-import.html b/doc/html/C/xacc-qif-import.html new file mode 100644 index 0000000000..340d41279f --- /dev/null +++ b/doc/html/C/xacc-qif-import.html @@ -0,0 +1,455 @@ + + + + +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. + +
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. + +
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. + +
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. + +
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. + +
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. + +
Table of Contents
+
+ Introduction to the QIF file
+
+
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. + +
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. + +
Here's a typical Quicken transaction record: +
+ !Type:Bank + D6/20/97 + T-500 + N1012 + C* + M + P + L[Visa] + ^ ++ +
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. + +
The D tag denotes the date. Note y2k compliance "issue". +Here's a lovely "feature" of some version of Quicken and dates in +2000: +
+ D1/ 1' 0 + T-640.00 + CX + N511 + PJoe Bob + LRent:Apartment + ^ ++ +
Ouch! Fortunately the GnuCash QIF importer can handle all of +the wacky date formats that the gnucash-devel list can find. + +
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. + +
The N field is a "Number", which is usually a check number or +some other identifying number for the transaction. + +
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. + +
The M field is the transaction memo. + +
The P field is the Payee. + +
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). + +
The ^ tag means End of Record. + +
Quicken users taking advantage of Classes will see a slash (/) +character followed by the class name appended on the Category line +(like [Visa]/Project) + +
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. + +
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: +
+ !Type:Bank + D12/03/95 + T4,706.57 + CX + POpening Balance + L[New Bank] + ^ ++
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 +Accounts Tab section there's a discussion +of what we do with them. + +
Table of Contents
+
+ How to use the QIF Import dialog
+
+
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. + +
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 +Files tab 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. + +
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. + +
Once you have loaded all the files into the importer, go to the +Accounts tab, and then to the +Categories tab, 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. + +
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. + +
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. + +
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. + +
Table of Contents
+
+ 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.
+
+ 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.
+
+ 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).
+
+ 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
+ Table of Contents
+
+ 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 ":").
+
+ 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.
+
+ 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):
+
+ 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
+Account Picker dialog which will allow you
+to change it.
+
+ Table of Contents
+
+ 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.
+
+ Table of Contents
+
+ Everything really happens when you hit the "OK" button, so it
+gets a section to itself.
+ Table of Contents
+
+ 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".
+
+ 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.
+
+ 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.
+
+ 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.
+
+ 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.
+
+
+
+
diff --git a/doc/html/C/xacc-quicken.html b/doc/html/C/xacc-quicken.html
new file mode 100644
index 0000000000..0b6c6a7bf3
--- /dev/null
+++ b/doc/html/C/xacc-quicken.html
@@ -0,0 +1,172 @@
+
+
+
+ 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. What Quicken calls Categories are really just Income/Expense accounts. 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. 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 all of the accounts you might have had in
+ Quicken. 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 different set of
+ account names that you might be using in GnuCash. 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. To create a set of Quicken QIF files, perform the
+ following procedure: It works on Wine,
+ Caldera's Wabi, and doubtless on VMWare, so this may not
+ forcibly require that you run Windows. 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 less tedious than entering
+ the data from scratch.) This will provide a dialog that requests a filename,
+ effective dates, as well as a series of checkboxes,
+ including Transactions, Accounts List,
+ Category List, and so forth. For best results, you should make sure that those three
+ are checked. If you do not check the Accounts
+ List 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. 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 exactly. Thus, the merge
+ should 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. This unfortunately can occur, the typical
+ scenario involving where you make multiple withdrawals of
+ identical amounts from ATM machines on the same day. Note that when the Accounts List and
+ Category List is exported from Quicken, all
+ 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. At this point, it successfully parses QIF
+ files; what remains is the (rather complex task) of
+ determine appropriate correspondences between the Quicken
+ Categories and the GnuCash equivalents. That is one
+ of the most significant weaknesses with the present QIF
+ import scheme. Further details about the QIF Interchange Format may be
+ found
+ here. Return to Main Documentation
+ Page. 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
+ OK . The window will then show all unreconciled
+ transactions since your last bank statment. The reconcile
+ window looks like this: 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. For example, when you write a check for something, you
+ should enter the transaction into GnuCash. At the end of the month, you receive your bank statement,
+ perhaps including cancelled checks. At that point,
+ you should "reconcile" the account, that is, agree your
+ personal records to the documentation provided by the bank. 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 n to c, indicating the transaction
+ has cleared. 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. 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. Also, the "cleared" total at the bottom seems to display
+ $0.00 regardless of what transactions are cleared or
+ reconciled. The "cleared" total should display the total of only the
+ transactions that have been cleared (c) or reconciled
+ (y). Return to Main Documentation
+ Page. This is the "Register" or the "Ledger" window. Transactions are entered here. To enter a new transaction, just type into the last blank transaction.
+ Use the mouse or the Register Keyboard Shortcutsto move between fields, and hit the Enter key or click record to
+ record the transaction: Notice how a the transaction has been recorded and a new, blank
+ transaction has been created. You can edit existing transactions in a similar manner. GnuCash
+ will prompt you to confirm any changes you make. You can manipulate transactions with the toolbar or the "Transaction"
+ menu:
+ The register can show transactions in a variety of different
+ ways, controlled by entries on the "Register" menu. The register can display transactions in several different
+ styles: To change the display style, to go the "Register" menu and select
+ "style". 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". Transactions are typically checked against bank statements - a
+ process known as "reconciliation". GnuCash keeps track of
+ the reconciliation status of each transaction. 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. 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. Reconciliation can be done in the Reconcile Window You can do stock transactions either from a single-stock
+ window, or from a portfolio-view window, shown below. The portfolio ledger can seem a bit daunting at first
+ sight. If you have trouble understanding it, then you may wish to
+ create an account for each stock you wish to track. Some important points to remember about the portfolio
+ window: The share amounts shown are for each particular
+ stock. Debited accounts and debited amounts are on the upper
+ line, and credited amounts and accounts are on the lower
+ line. Return to Main Documentation
+ Page. A variety of financial reports can be selected on the "Extensions"
+ menu":
+ 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:
+ See the help for the individual reports for details of options
+ available. 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.
+ 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.
+ 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).
+ 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 gnucash-devel@gnucash.org.
+ Return to Main Documentation
+ Page. If a GnuCash stock
+ account is suitably configured, and the host computer is
+ connected to the internet, the program gnc-prices may
+ be used to load stock and mutual fund price quotes from various
+ web sites directly into GnuCash. To make use of this facility, the following must be
+ done:The "Files" Tab
+
+
+ cat macfile | tr 015 012 > unixfile
+
+
+ The "Accounts" and "Categories" Tabs
+
+
+
+
+ The Account Picker
+
+ The "OK" Button
+
+
+
+
+A few hints
+
+ Opening Balance
+ Empty category
+
+ Dividend category
+
+ Fund families
+
+ Brokerage accounts
+
+ Quicken (TM) User's Guide
+
+ Quicken Categories
+
+
+ Quicken QIF File Import
+ GnuCash supports the import of Quicken
+ Import Files (QIF). (Note: Only Quicken Version 3.0 QIF has
+ been formally tested so far.)
+
+ Creating QIF Files
+
+
+
+ Now you have a set of .QIF files, and should run
+ GnuCash.
+
+ Loading QIF files into GnuCash
+
+
+
+
+
+
+ Things To Note About QIF Import
+
+
+
+
+
+ Reconciliation Window
+
+
+ 
+
+
+
+
+
+
+
+
+
+
+
+ Register Window
+ 
+ 
+ Manipulating transactions
+
+
+ Viewing Transactions
+
+
+
+ Reconciliation
+ Stock Portfolios
+
+ 
+ 
+
+
+ Reports
+
+
+
+ The Report Window
+ Once you select a report, a report window will appear:
+ 
+ 
Constructing custom reports
+
+ 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.
+
+ Stock Pricing and Ticker Symbols
+ GnuCash provides a somewhat rudimentary automated stock quote
+ gathering system.
+
+
+
+
+
| Code | + +Market | +
|---|---|
| PA | + +Paris | +
| BC | + +Barcelona | +
| BE | + +Berlin | +
| BI | + +Bilbao | +
| BR | + +Brême | +
| CO | + +Copenhagen | +
| D | + +Dusseldorf | +
| F | + +Frankfurt | +
| H | + +Hambourg | +
| HA | + +Hanover | +
| L | + +London | +
| MA | + +Madrid | +
| MC | + +Madrid (M.C.) | +
| MI | + +Milan | +
| MU | + +Munich | +
| O | + +Oslo | +
| ST | + +Stockholm | +
| SG | + +Stuttgart | +
| VA | + +Valence | +
| FX | + +Xetra | +
A sample image is shown below:
+ 
To update the prices stored in a gnucash account file, run + the command line command gnc-price, specifying the + filename; for example:
++ gnc-prices myaccts.xac ++ +
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.
+ +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.
+ +Thus, if gnc-prices 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.
+ +To keep gnc-prices from updating one account, while + allowing it to update another account, merely mark the data + source for that account as (none). You can do this + from the Edit Account window.
+ +After running gnc-prices for a few days, your
+ accounts will begin to resemble the following:
+ 
Return to Main Documentation + Page.
+ + diff --git a/doc/html/C/xacc-trans_report.html b/doc/html/C/xacc-trans_report.html new file mode 100644 index 0000000000..7bf0033934 --- /dev/null +++ b/doc/html/C/xacc-trans_report.html @@ -0,0 +1,33 @@ + + + + + +Transaction reports list details for transactions in a specified + account over a specified period, in a convenient format for + viewing and exporting.
+Options specifiable for this report include:
+Return to Main Documentation + Page.
+ + diff --git a/doc/html/C/xacc-y2k.html b/doc/html/C/xacc-y2k.html new file mode 100644 index 0000000000..ef16947461 --- /dev/null +++ b/doc/html/C/xacc-y2k.html @@ -0,0 +1,53 @@ + + + + + + +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 too many orders of magnitude outside + cosmologists' estimations of the age of the universe.
+ +The file format for version 1.1.25 and later stores dates + in the above-described fashion.
+ +Some internal routines use the time_t 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 + time_t will migrate to the use of 64 bit values by + that time.
+ +Backup and log files are time-stamped using the standard + Unix ctime() routine, which takes a time_t + 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.
+ +Note that GnuCash also correctly recognizes February 29th, + 2000 as a "leap day," another of the "critical Y2K dates."
+ +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...
+ +Y2K issues are described in more detail at Linux and Year + 2000.
+Return to Main Documentation + Page.
+ + + diff --git a/doc/html/fr/bofa-mym.html b/doc/html/fr/bofa-mym.html new file mode 100644 index 0000000000..963221de91 --- /dev/null +++ b/doc/html/fr/bofa-mym.html @@ -0,0 +1,39 @@ + + + + + +http://www-cad.eecs.berkeley.edu/~gooch/mymdump.html +
http://www-cad.eecs.berkeley.edu/~gooch/qifuniq.html +
J'espère que les autres trouveront ces scripts facile à +utiliser. +
Ken Yamaguchi Octobre 1998 + + diff --git a/doc/html/fr/pix/appr-asset1.gif b/doc/html/fr/pix/appr-asset1.gif new file mode 100644 index 0000000000..3d0a6d5bd8 Binary files /dev/null and b/doc/html/fr/pix/appr-asset1.gif differ diff --git a/doc/html/fr/pix/appr-asset2.gif b/doc/html/fr/pix/appr-asset2.gif new file mode 100644 index 0000000000..8ecf19ebe1 Binary files /dev/null and b/doc/html/fr/pix/appr-asset2.gif differ diff --git a/doc/html/fr/pix/appr-income.gif b/doc/html/fr/pix/appr-income.gif new file mode 100644 index 0000000000..5800f6a954 Binary files /dev/null and b/doc/html/fr/pix/appr-income.gif differ diff --git a/doc/html/fr/pix/appr-main1.gif b/doc/html/fr/pix/appr-main1.gif new file mode 100644 index 0000000000..87cae7c15a Binary files /dev/null and b/doc/html/fr/pix/appr-main1.gif differ diff --git a/doc/html/fr/pix/appr-main2.gif b/doc/html/fr/pix/appr-main2.gif new file mode 100644 index 0000000000..86351f1149 Binary files /dev/null and b/doc/html/fr/pix/appr-main2.gif differ diff --git a/doc/html/fr/pix/contract.gif b/doc/html/fr/pix/contract.gif new file mode 100644 index 0000000000..fe672fc3b5 Binary files /dev/null and b/doc/html/fr/pix/contract.gif differ diff --git a/doc/html/fr/pix/depr-asset.gif b/doc/html/fr/pix/depr-asset.gif new file mode 100644 index 0000000000..8f3fb79e51 Binary files /dev/null and b/doc/html/fr/pix/depr-asset.gif differ diff --git a/doc/html/fr/pix/depr-main.gif b/doc/html/fr/pix/depr-main.gif new file mode 100644 index 0000000000..666c55fe5d Binary files /dev/null and b/doc/html/fr/pix/depr-main.gif differ diff --git a/doc/html/fr/pix/expand.gif b/doc/html/fr/pix/expand.gif new file mode 100644 index 0000000000..7af4876747 Binary files /dev/null and b/doc/html/fr/pix/expand.gif differ diff --git a/doc/html/fr/pix/foliowin-single.gif b/doc/html/fr/pix/foliowin-single.gif new file mode 100644 index 0000000000..3a18e56a0b Binary files /dev/null and b/doc/html/fr/pix/foliowin-single.gif differ diff --git a/doc/html/fr/pix/foliowin.gif b/doc/html/fr/pix/foliowin.gif new file mode 100644 index 0000000000..e8a9e52c79 Binary files /dev/null and b/doc/html/fr/pix/foliowin.gif differ diff --git a/doc/html/fr/pix/newaccwin-code.gif b/doc/html/fr/pix/newaccwin-code.gif new file mode 100644 index 0000000000..ba004075d2 Binary files /dev/null and b/doc/html/fr/pix/newaccwin-code.gif differ diff --git a/doc/html/fr/pix/newaccwin-trade.gif b/doc/html/fr/pix/newaccwin-trade.gif new file mode 100644 index 0000000000..c71bba0f7c Binary files /dev/null and b/doc/html/fr/pix/newaccwin-trade.gif differ diff --git a/doc/html/fr/pix/newaccwin.gif b/doc/html/fr/pix/newaccwin.gif new file mode 100644 index 0000000000..ba004075d2 Binary files /dev/null and b/doc/html/fr/pix/newaccwin.gif differ diff --git a/doc/html/fr/pix/recnwin.gif b/doc/html/fr/pix/recnwin.gif new file mode 100644 index 0000000000..83899b8357 Binary files /dev/null and b/doc/html/fr/pix/recnwin.gif differ diff --git a/doc/html/fr/pix/regwin-double.gif b/doc/html/fr/pix/regwin-double.gif new file mode 100644 index 0000000000..f0a4ea3469 Binary files /dev/null and b/doc/html/fr/pix/regwin-double.gif differ diff --git a/doc/html/fr/pix/regwin-multi.gif b/doc/html/fr/pix/regwin-multi.gif new file mode 100644 index 0000000000..2e0a51527f Binary files /dev/null and b/doc/html/fr/pix/regwin-multi.gif differ diff --git a/doc/html/fr/pix/regwin-single.gif b/doc/html/fr/pix/regwin-single.gif new file mode 100644 index 0000000000..55d901d4b4 Binary files /dev/null and b/doc/html/fr/pix/regwin-single.gif differ diff --git a/doc/html/fr/pix/regwin-single2.gif b/doc/html/fr/pix/regwin-single2.gif new file mode 100644 index 0000000000..62df99ba85 Binary files /dev/null and b/doc/html/fr/pix/regwin-single2.gif differ diff --git a/doc/html/fr/pix/regwin.gif b/doc/html/fr/pix/regwin.gif new file mode 100644 index 0000000000..b0adac908d Binary files /dev/null and b/doc/html/fr/pix/regwin.gif differ diff --git a/doc/html/fr/pix/report-baln.gif b/doc/html/fr/pix/report-baln.gif new file mode 100644 index 0000000000..4a217ddae6 Binary files /dev/null and b/doc/html/fr/pix/report-baln.gif differ diff --git a/doc/html/fr/pix/report-folio.gif b/doc/html/fr/pix/report-folio.gif new file mode 100644 index 0000000000..ee783f9a01 Binary files /dev/null and b/doc/html/fr/pix/report-folio.gif differ diff --git a/doc/html/fr/pix/report-option.gif b/doc/html/fr/pix/report-option.gif new file mode 100644 index 0000000000..5c56f978cb Binary files /dev/null and b/doc/html/fr/pix/report-option.gif differ diff --git a/doc/html/fr/pix/reportwin.gif b/doc/html/fr/pix/reportwin.gif new file mode 100644 index 0000000000..4e67ad8f61 Binary files /dev/null and b/doc/html/fr/pix/reportwin.gif differ diff --git a/doc/html/fr/pix/ticker-a.gif b/doc/html/fr/pix/ticker-a.gif new file mode 100644 index 0000000000..929d67a516 Binary files /dev/null and b/doc/html/fr/pix/ticker-a.gif differ diff --git a/doc/html/fr/pix/ticker-b.gif b/doc/html/fr/pix/ticker-b.gif new file mode 100644 index 0000000000..f0e86e075c Binary files /dev/null and b/doc/html/fr/pix/ticker-b.gif differ diff --git a/doc/html/fr/projects.html b/doc/html/fr/projects.html new file mode 100644 index 0000000000..f8182424d0 --- /dev/null +++ b/doc/html/fr/projects.html @@ -0,0 +1,1558 @@ + + + +
+The people behind GnuCash aim + to create a world-class GPL'ed Open Source Personal Financial + Application for GNU/Linux and other Unix's. This page aims to + review some of the technical and development issues surrounding + this product, representing a sort of FAQ for developers and + contributors, to suggest directions when developers are trying to + determine how to implement new functionality.
+ +To get a better idea of what + GnuCash is and what it does, visit its home page.
+ +There are currently several different versions of + GnuCash.
+ +The latest Gnome version, and latest versions in general, + are currently available only via CVS.
+ +Precompiled versions are available, but usually + only for the stable releases. Don't use the unstable versions + unless you are ready for excitement and adventure, and are + prepared to cope with a need to keep extensive backups.
+ +This document is divided into several sections.
+ +Thus, the Motif or Gnome GUIs are merely two possible + manipulators of the data; others, based on e.g. + Qt/KDE, emacs, Java applets or Java servlets ought to be + possible.
+GnuCash also needs to deal with multiple distributed data + sources: stock quotations from the net or transaction + confirmations from online banks and brokerage houses, or from + more mundane sources, such as file imports, or merger of data + from several users.
+ +Amongst these terms, the concept of a global Model-View is + dated, and somewhat inappropriate. Rather, we need to be + concerned about how data is represented in the local address + space of the GUI, how the GUI manipulates it, how data is + brought in and merged from external sources, and how that data + is again output, whether to a file or a local or remote + database.
+ +Thus, the View essentially represents a local data + cache of the data that is immediately present and being + displayed, reported, and manipulated. The Model is the + abstraction of that data that the GUI (the controller) can act + on.
+ +Currently, the Engine is fairly poor, and is tightly tied + to the data structures that the GUI manipulates. These data + structures include:
+ +The Engine currently handles only a small set of data + sources:
+ +However, since the Engine is meant to be the interface + between the GUI and the financial data, it is really intended + to be able to do much more.
+ +In particular, it should be possible to back the Engine + onto an SQL database, and thereby enable multiple users and/or + interface to more complex accounting systems. The engine should + also be expandable to handle other sources of data, such as + OFX, Integrion GOLD, the Open Trading Protocol, the OMG CORBA + General Ledger submission, the IBM San Francisco business + objects, or closer to home, Linux Kontor. In particular, it + should be possible to use GnuCash not only to view data from + these sources, but also to manipulate it and send it back.
+ +The above structure should leads us to view GnuCash not so + much as a tightly integrated application, but rather as a loose + confederation of component objects, libraries and + interfaces.
+ +In order to facilitate the gluing together of these parts, + as well as simplify the questions of customizability, change + and rapid development, GnuCash makes use of an extension + language to glue the pieces together.
+ +The extension language that is most central to Gnucash is + + Scheme, and in particular, the FSF implementation, Guile, + although some of the interfaces are also available through Perl.
+ +Important properties of a personal finance system + include:
+ +A seemingly contradictory factor is that the kinds of + sophistication that are required vary considerably. + Consider:
+ +Thus, home users don't need much of the + sophistication of an Accounts Receivable or Payable system, + or the bizarre depreciation policies that crop up + in Asset Management systems.
+It may be that these will require completely + different systems, and that GnuCash cannot be "all things to + all people." This remains to be seen.
+ +The right hand column shows a sizing guesstimate. pm == + person-months
+ +| Feature | + +Sizing | +
|---|---|
| + | +|
| Enhanced Engine, Financial + Objects | + +Large | +
| SQL I/O | + +Medium | +
| Multi-User Support | + +Medium | +
| A/R, A/P Accounts Payable, + Receivable | + +Medium | +
| Payroll | + +Medium | +
| Invoicing | + +Medium | +
| Job Costing | + +Medium | +
| Expense Accounts | + +Large | +
Current status:
+ +Other output format possibilities include SGML and Extensible + Markup Language - XML. In the long run, these are + preferable to HTML, since DSSSL tools such as Jade (James DSSSL + Engine) can be used to convert to RTF, Postscript, + etc.
+ +Add to this the consideration that XML is the basis for + the Document Object + Model, which is being integrated into many web-based + applications, and we can see that XML is an increasingly + significant format as we look to the future.
+ +The Report Generator should be a separate but + "dockable" subsystem of the whole.
+ +Thus, it should be possible to run the report generator + in a stand-alone, read-only fashion without having to start + up the main application.
+ +Graphs, charts, etc. too ...
+ +Asset allocation pie chart.
+ +Graph portfolio value vs. cost
+ +One difficult aspect of reporting is designing a + configurable interface, so that people can build custom + reports. The New + Reporting Infrastructure is seeking to build this up + using Guile.
+ +Stock portfolio tools should include a Cost Averaging + report, Market Index report, Stock Option values, + Estimation of capital gains tax liabilities.
+ +Status:
+ +Question: How to most simply allow the user to + enter loads and fees?
+ +Answer: Through splits. Unfortunately, some + users may not properly understand splits, at least not + initially. Thus, a little popup is needed to allow the user + to type in the sales load or fee and such, and then + auto-create the needed splits.
+ +Note the current transfer window does NOT + allow a share price to be specified !! Needs fixing ...
+ + +A set of themes would be desirable for the Gnome + version.
+A user-configurable button-bar would be nice + too.
+Provide a default list of "Categories" + (Income/Expense Accounts). These are categories such as + "Automobile Expense", "Bank Interest Income", and + "Employment Income". The user should be able to select + a default set of accounts, and have those created + automatically.
+ +To actually implement this, it might be best to + simply create a file with these in them, and load that + file. A mechanism should be provided to allow the user + to weed out undesired accounts whilst not preventing + them from using them at a later date, if desired.
+Add an example showing how regular household assets + (house, car, jewelry, etc.) should be treated. In + particular, show how appreciation and depreciation + should be treated.
+Menu navigation using the keyboard should be + possible.
+ +Although menu mnemonics exist, they seem to be + broken.
+ +Similarly, tab-key navigation should be possible. + Currently, it is possible to use the tab key to + navigate from field to field in the register window, to + user arrow keys to navigate menus, and quick-fill to + automatically complete fields. However, it is not + possible to tab over to the "Commit" button.
+ +It should be.
+Currently, Income/Expense accounts can be shown or + hidden by selecting from a menu. It would be nice to be + able to examine different account types (Asset, + Liability, Income, Expense, Payables, Receivables, + Inventory) by selecting a tab folder.
+When the user pauses the mouse over a button, + "fly-over" pop-up help windows should appear.
+Create grayed out entries in the ledger, titled + "Memo", "Description", etc, helping users understand + what should be typed into each field.
+Make sure that text fields can handle the vi and + emacs key bindings, so that e.g. emacs-style + ctrl-a, ctrl-k does the right thing.
+i.e. Ability to permanently lock records as + non-editable. This should be straight-forward by using the + reconciled field to indicate a locked + value, and not allowing the GUI to edit locked records.
+ +Also need to report closed books slightly differently. + Need to bring balances forward too...
+ + +Preferences include things like showing/not showing + categories, forcing double-entry, etc.
+ +Current status:
+ +The overall architecture is envisioned thus:
+ +All code, including the transaction engine, the file + I/O routines, the menus, and the ledger, will be abstracted + into compact modules that can function independently of + each other. At the highest level, there will be a + infrastructure with extension language interfaces that will + "wire together" the various modules.
+ +Such "wiring together" will consist of a dispatch + infrastructure that will allow arbitrary menu entries to be + hooked to arbitrary modules. The configuration for menu + entries, and their associated callbacks, will be specified + in an extension-language configuration file. At the final + stages, it is highly desirable to be able to, in + some manner, import new modules without requiring + that the application itself be recompiled and relinked.
+ +Status:
+ +This should be handled by having a way of bouncing out + to some Guile code to generate transactions with computed + values.
+Status:
+ +Add support for automatic, recurring transactions, + e.g. mortgage payments, fixed-interest bonds, bank + accounts, etc.
+ +Note that the design for this could be very different, + depending on whether the multi-user functions are available + or not.
+ +Design/implementation for this is tricky. It should + probably leverage crontab, but this can lead to + difficulties and bugs.
+ +May need interfaces to email for emailed alerts.
+ +Interfaces into calendaring systems? Current + status:
+ +Note that the above 'step-by-step' budgeters will have + a very very different GUI than what the budgeting system + required for a small-business might look like.
+ +Status:
+ +Status:
+ +Right now, this is a stand-alone perl script run + from crontab.
+OFX is an open spec from Microsoft, Intuit, and + Checkfree, and which will be supported by Integrion. The + OFX DTD's are included in the 1.1 distributions. See OFX Home Page for + details.
+ +There are two ways to build an OFX parser. One way is + to build a compile-time DTD parser that treats the DTD as + if it were an IDL, and generates C language stubs for a + parser.
+ +This approach was attempted and abandoned because it + leads to fragile C code and a very large binary.
+ +Run-time parsing may be slower, but on the OFX client + side, this should not be a bottleneck.
+ +Status:
+ +Note that the organizations developing OFX are looking + to use XML as their "formats of the future;" this may + encourage the use of one of the many XML parsers available + for UNIX.
+Double-entry is a powerful way of ensuring the + integrity of of the financial data. Currently, while + double-entry is supported, its use is not enforced: the + user can create dangling transactions, where only + one account is indicated.
+ +Although this is acceptable for home use (even + desirable, since it allows the casual user the simplicity + they desire), it is not acceptable for business use.
+ +It must be possible to enable forced-double entry, so + that a transaction cannot be completed until two accounts + have been specified.
+ +Current status:
+ +The tab-delimited format should be compatible with that + of /rdb, aka RAND/Hobbs /rdb or + + NoSQL. (NoSQL is available as part of the Debian GNU/Linux distribution, + for instance.)
+ +The /rdb format is thus:
++field-name tab fieldname tab fieldname \n +------------------------------------------ \n +value tab value tab value \n +value tab value tab value \n +etc ... ++ +
It is a very simple, very basic flat table format. The + use of /rdb with GnuCash should try to match with + SQL schemas as much as possible in order to minimize I/O + complexity and incompatibility.
+categorize items according to different tax + schedules
+The current engine is rather simple: it provides + support for accounts, account hierarchies and transactions + consisting of multiple entries.
+ +Many of the features described elsewhere will require + that the engine have a far richer, more sophisticated data + model, including such things as:
+ +Note: it makes no sense at this point to make the + engine API much richer than what the GUI can currently + support.
+ +In a business environment, the auditors may have + "signed off" on the validity of the data; at that + point, the ability to modify audited data should be + very tightly controlled, or even downright + forbidden.
+Current Status:
+ +These "Transaction processing constructs" should + simplify creation of an SQL back end, or some other + more sophisticated database engine.
+There has been much discussion about this on + mailing lists both for GnuCash and CBB. Major + points have included:
+ +This may be a minor cost to a business enterprise + that hires DataBase Administrators.
+ +It is not acceptable to require this of + naive users that may find "simple" things like
++% su - +Password: +# cd /tmp +# rpm -i gnucash-4.1.3.i386.rpm +# exit ++ to be challenging. +
Changing GnuCash to be suited to use a DBMS in + other than a "load-it-all" / "dump-it-all" manner, but + to rather update the database in a transactional + manner.
+ +That being said, it may be possible to recast the + GnuCash engine functionality so as to handle + storage in a transactional manner.
+The following industrial-strength features are + needed:
+ +While the GnuCash "engine" might remain free, + maintenance of payroll functionality would require + "subscribing" to an update scheme; it might be troublesome + to try to provide such a "subscription" free of charge.
+Mostly aimed at mainframes, middleware, high + transaction volumes and data integrity.
+Linas Vepstas
+ linas@linas.org
+
Christopher Browne
+ cbbrowne@ntlug.org
+
Le courant "experimental" actuel est gnucash-1.3.x, qui est en quelque +sorte instable. +
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. +
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
+
continuer sur les 1.5.x.
+
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
+GnuCash
+Project Goals(buts du projet Gnucash) afin d'acquérir
+quelques perspectives sur la conception globale.
+
+
Yannick Le Ny
+
Localise
+(traduction et adaptation) de Xacc et Gnucash pour la France et les pays
+francophones.
+
Travail
+effectué :traduction du Readme, des messages et de l'aide en ligne
+de Gnucash en français
+
A finis
+de traduire tout le site web de Gnucash en français sauf la liste
+de courriers et le maintient à jour
+
| Version | + +moteur | + +registre | + +grand livre | + +motif | + +prefs (scm) | + +docs (html) | + +divers | + +Total | +
|---|---|---|---|---|---|---|---|---|
| xacc-0.9
+ Sept 97 |
+
+- | + +- | + +- | + +34 fichiers
+ (7.5+0.9) |
+
+- | + +5 fichiers
+ (0.4) |
+
+- | + +39 fichiers
+ (8.8) |
+
| xacc-0.9w
+ Dec 97 |
+
+- | + +- | + +- | + +51 fichiers
+ (13.8+1.5) |
+
+- | + +9 fichiers
+ (0.8) |
+
+- | + +60 fichiers
+ (16.1) |
+
| xacc-1.0.17
+ Fev 98 |
+
+- | + +- | + +- | + +52 files
+ (14.8+1.8) |
+
+- | + +12 files
+ (1.4) |
+
+- | + +64 files
+ (18.0) |
+
| gnucash-1.1.15
+ Aou 98 |
+
+24 fichiers
+ (6.2+1.5) |
+
+31 fichiers
+ (6.1+1.7) |
+
+5 fichiers
+ (1.4+0.4) |
+
+30 fichiers
+ (7.4+0.7) |
+
+3 fichiers
+ (0.3) |
+
+16 fichiers
+ (1.9) |
+
+non compté
+ (>1.0) |
+
+109 fichiers
+ (32.9) |
+
| gnucash-1.2.2
+ Aou 99 |
+
+41 fichiers
+ (10.2+3.6) |
+
+28 fichiers
+ (5.5+1.7) |
+
+14 fichiers
+ (2.4+0.6) |
+
+26 fichiers
+ (8.7+0.5) |
+
+14 fichiers
+ (1.4) |
+
+30 fichiers
+ (2.6) |
+
+non compté
+ (>1.0) |
+
+153 fichiers
+ (37.2) |
+
Chaque cellule contient: +
nombre de fichiers *c et *.h
+
(KLOCS dans *.c + KLOCS dans *.h),
+
où KLOC == kilo-lignes-de-code, comme rapported par wc. +
+
L'Information du compte peut être changée en tapant +dans le champ approprié. Le type de compte ne peut pas être +changé. +
Un nouveau Compte parent peut être sélectionné.Seulement +ceux de ces comptes qui peuvent légalement devenir le parent du +compte actuel sont montrés. +
La source pour le Cours des actions peut être sélectionné. +FIXME: Pourrait-il y avoir quelqu'un qui utilise cette fonction la documente,s'il +vous plait ?> +
Les notes à propos du comptes peuvent être modifiées.
+
+
Retour à la Page principale de la documentation. + + diff --git a/doc/html/fr/xacc-acctypes.html b/doc/html/fr/xacc-acctypes.html new file mode 100644 index 0000000000..6a56112f4a --- /dev/null +++ b/doc/html/fr/xacc-acctypes.html @@ -0,0 +1,225 @@ + + +
+ + +
Ci-dessous se trouve à quoi ressemble une fenêtre nouveau
+compte :
+
+
+
+
Choisissez un Type de compte. +
Le champ Monnaie devrait être typiquement un code +monétaire ISO à trois lettres ISO (par exemple USD +pour les dollars US). Le code du compte est un numéro qui +détermine l' ordre de tri +pour le compte quand il apparait dans un rapport ou dans le Tableau +de comptes. +
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 code
+de valeur d'une action, ou un code
+monétaire à trois lettres ISO.
+
+
+
+
Retour à la Page principale de la documentation.
+
+
+
+
+
diff --git a/doc/html/fr/xacc-adjbwin.html b/doc/html/fr/xacc-adjbwin.html
new file mode 100644
index 0000000000..ec10717abc
--- /dev/null
+++ b/doc/html/fr/xacc-adjbwin.html
@@ -0,0 +1,21 @@
+
+
+
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. +
En tous cas, considérons Crédits fournisseurs. Après
+tout, nous ne devrions à vrai dire avoir besoin de rien raconter
+sur les D/F parce que nous payons toujours nos factures à
+temps, n'est ce pas ? :-)
+
Aussi comme première considération, allons et supposons +que nous ne demandons pas aux clients de payer instantanément, +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 :-)). +
Quand nous faisons une vente, les deux comptes affectés sont +les Ventes (un compte revenus) et Crédit fournisseurs. +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. +
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. +
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'établisement +d'obligations, ce sont des engagements. +
Dans des opérations plus sophistiqués, il peut y avoir +une plus large séquence de documents générés +et suivis: +
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 +n'ont +pas été payés à l'échéance. +
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 Mauvais +débiteur. +
A ce point, il est typique d'enregistrer une entrée ainsi:
+
+
| Compte | + +DR | + +CR | +
|---|---|---|
| Dépense mauvais débiteurs | + +10,000F | + ++ |
| + | ||
| Crédit fournisseurs | + ++ + | 10,000F | +
Nous pouvons avoir Revenus de ventes 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. +
Attention: Concept de comptabilité avancée.
+Les dettes perdues / créances douteuses sont un exemple d' un "contre-compte."
+Qui ne se réfère pas au montants payés aux
+rebelles nicaraguyens (ndt:!!!) , 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. La
+dépréciation accumulée , utilisée pour
+diminuer la valeur d'un avoir au cours du temps, est un autre exemple de
+contre-compte.
+
+
Si vous devez payer six mois de loyer en avance, c'est traité +comme un "avoir accumulé." +
Tandis que celà impose un malheureux préjudice dans
+le compte de Liquidités, il apparait sur les livres comme
+un avoir, et il n'y a pas plus de paiements à faire pour les six
+prochains mois.
+
+
Retour à la Page principale de la documentation.
+
+
+
diff --git a/doc/html/fr/xacc-apprdepr.html b/doc/html/fr/xacc-apprdepr.html
new file mode 100644
index 0000000000..a4e3d264b9
--- /dev/null
+++ b/doc/html/fr/xacc-apprdepr.html
@@ -0,0 +1,682 @@
+
+
+
Il fournit aussi une brève introduction au sujet relatif aux +impôts. +
Attention: Soyez conscients que les différents pays +peuvent avoir des politiques fiscales considérablement 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. +
Notez que l'appréciation et la dépréciation des +avoirs tend à être traitées quelque peu différemment: +
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.
+
(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 intérêts +accumulés, ou intérêts imputés sont +souvent là pour effayer ceux qui sont sensibles à de telles +choses...)
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 jusqu'à ce que réellement vous vendiez les avoirs. +
Si vous investissez dans des valeurs +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 +Ordre +de bourse. +
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. +
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. +
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 de +moins de valeur 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, aucune d'elles sans ambiguité +ne sont correctes. +
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.) +
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): +
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 gains accumulés +sur un avoir vers votre compte avoirs. +
Votre fenêtre principale ressemblera à celà:
+
+
et votre compte avoirs ressemblera à celà:
+
+
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 théoriquement évaluées +à des millions de dollars USD. +
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 n'importe lesquelles d'entre +elles. Le fait qu'ils ne pouvait 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 recevoir ces millions. +
Maintenant il se produit trois possibilitées: +
| Compte | + +Montant | +
|---|---|
| Liquidités | + +16055F | +
| Tableau | + +-11000F | +
| Revenu du gain réalisé | + +-5055F | +
Et si n'importe lequel des montants a été accumulé
+comme des Gains accumulés, le montant de l'avoir devrait
+être augmenté(closed out), compensé par une valeur
+négative
+pour le revenu Gain accumulés. Si le total qui a été
+accumulé était de 5000F, alors la transaction devrait ressembler
+à ce qui suit :
+
+
| Compte | + +Montant | +
|---|---|
| Liquidités | + +16055F | +
| Tableau | + +-11000F | +
| Avoir du gain accumulé | + +-5000F | +
| Revenu du gain réalisé | + +-5055F | +
| Revenu du gain accumulé | + +5000F | +
Notez que les deux comptes de revenus compense un autre ainsi que le +revenu actuel resultant de la transaction est seulement de 55F. +Le reste de 5000F a précédemment été reconnu +comme un Revenu de gain accumulé. +
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.
+
Les chiffres changent un petit peu, mais pas aussi dramatiquement.
+
+
| Compte | + +Montant | +
|---|---|
| Liquidités | + +15000F | +
| Tableau | + +-11000F | +
| Avoir du gain accumulé | + +-5000F | +
| Revenu du gain réalisé | + +-4000F | +
| Revenu du gain accumulé | + +5000F | +
Notez que les deux comptes de revenus compensent un autre ainsi que +le revenu actuel résultant de la transaction fait ressortir +une pertes de 1000F. C'est formidable, comme vous avez précédemment +reconnu 5000F de revenus. +
La valeur supplémentaire est, encore, enregistré comme
+un gain, par exemple un revenu.
+
+
| Compte | + +Montant | +
|---|---|
| Liquidités | + +50000F | +
| Tableau | + +-11000F | +
| Avoir du gain accumulé | + +-5000F | +
| Revenus du gain réalisé | + +-39000F | +
| Revenus du gain accumulé | + +5000F | +
En bas, nous montrons le second cas à discuter.
+
+
+
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." +
Ainsi, quand vous traitez de l'appreciation des avoirs, +
Ne vous adonnez pas à un espoir secret.
+
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à.
+
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. +
Soyez conscient: toutes les trop nombreuses sociétés qui +apparaissent "profitable" sur le papier quittent les affaires à +la suite d'un épuisement des liquidités, précisément +parce que les "biens de valeur" ne seront pas la même chose que l'argent +comptant.
Pourtant, il est commun 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. +
Les ropriétaires de maisons nord américain habituellement +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. +
J'ai 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 considérable +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 laitière, avec +quelquesdéductions résultant d'un régime réellement +singulier. +
En résumé, cette présentation est assez simple, +mais la taxation souvent devient terriblement compliquée... +
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. +
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. +
Exemple: 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:
+
+
| Année | + +Dépréciation | + +Valeur restante | +
|---|---|---|
| 1 | + +300 | + +1200 | +
| 2 | + +300 | + +900 | +
| 3 | + +300 | + +600 | +
| 4 | + +300 | + +300 | +
| 5 | + +300 | + +0 | +
Faites attention: les autorités fiscales peuvent demander +(orpermettre) un plus large pourcentage dans la première période. +D'un autre côté, au Canada, c'est changé/inversé, +comme ils permettent seulement une moitié de la part +of "Remise du coût du capital" dans la première année. +
Le résultat de cette approche est que la valeur du bien diminue +plus rapidement au départ qu'à la fin ce qui est probablement +plus réaliste pour la plupart des biens qu'un système linéaire. +C'est certainement vrai pour les automobiles. +
Exemple: Nous prenons le même exemple comme ci-dessus,
+avec une dépréciation annuelle de 30%.
+
+
| Année | + +Dépréciation | + +Valeur restante | +
|---|---|---|
| 1 | + +450 | + +1050 | +
| 2 | + +315 | + +735 | +
| 3 | + +220.50 | + +514.50 | +
| 4 | + +154.35 | + +360.15 | +
| 5 | + +108.05 | + +252.10 | +
Exemple: 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:
+
+
| Année | + +Dépréciation | + +Valeur restante | +
|---|---|---|
| 1 | + +100*5=500 | + +1000 | +
| 2 | + +100*4=400 | + +600 | +
| 3 | + +100*3=300 | + +300 | +
| 4 | + +100*2=200 | + +100 | +
| 5 | + +100*1=100 | + +0 | +
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.
+
+
+
FIXME: Document this report! +
Return to Main Documentation + Page.
+ + + diff --git a/doc/html/fr/xacc-balsheet.html b/doc/html/fr/xacc-balsheet.html new file mode 100644 index 0000000000..ffd689481f --- /dev/null +++ b/doc/html/fr/xacc-balsheet.html @@ -0,0 +1,20 @@ + + + + + +This report summarizes your assets, liabilities, and equity.
+ +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.
+ +Return to Main Documentation + Page.
+ + diff --git a/doc/html/fr/xacc-currency.html b/doc/html/fr/xacc-currency.html new file mode 100644 index 0000000000..46f0adcaf9 --- /dev/null +++ b/doc/html/fr/xacc-currency.html @@ -0,0 +1,1203 @@ + + + + + + + + + +Quand nous introduisons la notion d'avoir de multiples monnaies, ou +actions qui peuvent varier en cours/prix, les identitées deviennent +un peu plus compliquées, et nous introduisons la formule suivante: +
Date transfert depuis mémo coût +1/5/99 [JPYAcct] Achat gadget $1.00 + ++ +
+
Date transfert depuis
+mémo
+achat taux
+
1/5/99 [SpendAcct]
+Achat gadget Y150
+0.00667
+
+
+Le moteur lie ,toutes les trois, ces valeurs ensemble (1.0, 150, 0.00667)
+en permanence et les rend imposssible à changer sans en changer
+une autre, ainsi que la grande addition est toujours zéro, de ce
+fait garantissant le respect de l'
+identité de la comptabilité du double livret.
+
+
Plus de monnaies que vous pensez possible...
+
+
| Code ISO | + +Description complète | +
|---|---|
| + | |
| ADP | + +Andoran peseta | +
| AED | + +United Arab Emirates Dirham | +
| AFA | + +Afghani | +
| ALL | + +Albanian Lek | +
| AMD | + +Armenian Dram | +
| ANG | + +West Indian Guilder | +
| AOK | + +Angolan Kwanza | +
| ARA | + +Argentinian Austral | +
| ARS | + +Argentina Peso | +
| ATS | + +Austrian Schilling | +
| AUD | + +Australian Dollar | +
| AWG | + +Aruban Guilder | +
| AZM | + +Azerbaijan Manat | +
| BAD | + +Bosnia-Herzogovinian Dinar | +
| BBD | + +Barbados Dollar | +
| BDT | + +Bangladesh Taka | +
| BEF | + +Belgian Franc | +
| BGL | + +Bulgarian Lev | +
| BHD | + +Bahrain Dinar | +
| BIF | + +Burundi Franc | +
| BMD | + +Bermudan Dollar | +
| BND | + +Brunei Dollar | +
| BOB | + +Bolivian Boliviano | +
| BRL | + +Brazilian Real | +
| BRR | + +Brazil | +
| BSD | + +Bahaman Dollar | +
| BWP | + +Botswana Pula | +
| BYR | + +Belorussian Ruble | +
| BZD | + +Belize Dollar | +
| CAD | + +Canadian Dollar | +
| CDP | + +Santo Domiongo | +
| CHF | + +Swiss Franc | +
| CLP | + +CHILEAN PESO | +
| CNY | + +China | +
| COP | + +Colombian Peso | +
| CRC | + +Costa Rica Colon | +
| CUP | + +Cuban Peso | +
| CVE | + +Cape Verde Escudo | +
| CYP | + +Cyprus Pound | +
| CZK | + +Czech Krona | +
| DEM | + +German Mark | +
| DJF | + +Djibouti Franc | +
| DKK | + +Danish Krone | +
| DOP | + +Dominican Peso | +
| DRP | + +Dominican Republic Peso | +
| DZD | + +Algerian Dinar | +
| ECS | + +ECUADORIAN SUCRE | +
| ECS | + +Ecuador Sucre | +
| ECU | + +European Currency Unit | +
| EEK | + +Estonian Krone | +
| EGP | + +Egyptian Pound | +
| ESP | + +Spanish Peseta | +
| ETB | + +Ethiopian Birr | +
| EUR | + +Currency of EMU member states | +
| FIM | + +Finnish Mark | +
| FJD | + +Fiji Dollar | +
| FKP | + +Falkland Pound | +
| FRF | + +French Franc/ Franc Français | +
| GBP | + +British Pound | +
| GEK | + +Georgian Kupon | +
| GHC | + +Ghanian Cedi | +
| GIP | + +Gibraltar Pound | +
| GMD | + +Gambian Dalasi | +
| GNF | + +Guinea Franc | +
| GRD | + +Greek Drachma | +
| GTQ | + +Guatemalan Quedzal | +
| GWP | + +Guinea Peso | +
| GYD | + +Guyanese Dollar | +
| HKD | + +Hong Kong Dollar | +
| HNL | + +Honduran Lempira | +
| HRD | + +Croatian Dinar | +
| HTG | + +Haitian Gourde | +
| HUF | + +Hungarian forint | +
| IDR | + +Indeonesian Rupiah | +
| IEP | + +Irish Pound | +
| ILS | + +Israeli Scheckel | +
| INR | + +Indian Rupee | +
| IQD | + +Iraqui Dinar | +
| IRR | + +Iranian Rial | +
| ISK | + +Iceland Krona | +
| ITL | + +Italian Lira | +
| JMD | + +JAMAICAN DOLLAR | +
| JOD | + +Jordanian Dinar | +
| JPY | + +Japanese Yen | +
| KES | + +Kenyan Shilling | +
| KHR | + +Cambodian Riel | +
| KIS | + +Kirghizstan Som | +
| KMF | + +Comoros Franc | +
| KPW | + +North Korean Won | +
| KRW | + +South Korean Won | +
| KWD | + +Kuwaiti Dinar | +
| KYD | + +Cayman Dollar | +
| KZT | + +Kazakhstani Tenge | +
| LAK | + +Laotian Kip | +
| LBP | + +Lebanese Pound | +
| LKR | + +Sri Lankan Rupee | +
| LRD | + +Liberian Dollar | +
| LSL | + +Lesotho Loti | +
| LTL | + +Lithuanian Lita | +
| LUF | + +Luxembourgian Franc | +
| LVL | + +Latvian Lat | +
| LYD | + +Libyan Dinar | +
| MAD | + +Moroccan Dirham | +
| MDL | + +Moldavian Lei | +
| MGF | + +Madagascan Franc | +
| MNC | + +Monaco | +
| MNT | + +Mongolian Tugrik | +
| MOP | + +Macao Pataca | +
| MRO | + +Mauritanian Ouguiya | +
| MTL | + +Maltese Lira | +
| MUR | + +Mauritius Rupee | +
| MVR | + +Maldive Rufiyaa | +
| MWK | + +Malawi Kwacha | +
| MXN | + +Mexican Peso (new) | +
| MXP | + +Mexican Peso (old) | +
| MYR | + +Malaysian Ringgit | +
| MZM | + +Mozambique Metical | +
| NGN | + +Nigerian Naira | +
| NIC | + +Nicaragua | +
| NIO | + +Nicaraguan Cordoba | +
| NIS | + +Isreal | +
| NLG | + +Dutch Guilder | +
| NOK | + +Norwegian Krone | +
| NPR | + +Nepalese Rupee | +
| NZD | + +New Zealand Dollars | +
| OMR | + +Omani Rial | +
| PAB | + +Panamanian Balboa | +
| PEI | + +Peruvian Inti | +
| PEN | + +Peruvian Sol - New | +
| PES | + +Peruvian Sol | +
| PGK | + +Papua New Guinea Kina | +
| PHP | + +Philippino Peso | +
| PKR | + +Pakistan Rupee | +
| PLN | + +Polish Zloty | +
| PLZ | + +Poland | +
| PTE | + +Portuguese Escudo | +
| PYG | + +Paraguayan Guarani | +
| QAR | + +Qatar Riyal | +
| RMB | + +Chinese Renminbi Yuan | +
| ROL | + +Roumanian Lei | +
| RUR | + +Russian Rouble | +
| RWF | + +Rwanda Franc | +
| SAR | + +Saudi Riyal | +
| SBD | + +Solomon Islands Dollar | +
| SCR | + +Seychelles Rupee | +
| SDP | + +Sudanese Pound | +
| SEK | + +Swedish Krona | +
| SGD | + +Singapore Dollar | +
| SHP | + +St.Helena Pound | +
| SIT | + +Slovenian Tolar | +
| SKK | + +Slovakian Krona | +
| SLL | + +Leone | +
| SOL | + +Peru | +
| SOS | + +Somalian Shilling | +
| SRG | + +Surinam Guilder | +
| STD | + +Sao Tome / Principe Dobra | +
| SUR | + +Russian Ruble (old) | +
| SVC | + +El Salvador Colon | +
| SYP | + +Syrian Pound | +
| SZL | + +Swaziland Lilangeni | +
| THB | + +Thailand Baht | +
| TJR | + +Tadzhikistani Ruble | +
| TMM | + +Turkmenistani Manat | +
| TND | + +Tunisian Dinar | +
| TOP | + +Tongan Pa'anga | +
| TPE | + +Timor Escudo | +
| TRL | + +Turkish Lira | +
| TTD | + +Trinidad and Tobago Dollar | +
| TWD | + +New Taiwan Dollar | +
| TZS | + +Tanzanian Shilling | +
| UAK | + +Ukrainian Karbowanez | +
| UGS | + +Ugandan Shilling | +
| USD | + +American Dollar | +
| UYP | + +Uruguayan New Peso | +
| UYU | + +Uruguay | +
| VEB | + +Venezuelan Bolivar | +
| VND | + +Vietnamese Dong | +
| VUV | + +Vanuatu Vatu | +
| WST | + +Samoan Tala | +
| XAF | + +Gabon C.f.A Franc | +
| XCD | + +East Carribean Dollar | +
| XOF | + +Benin C.f.A. Franc | +
| YER | + +Yemeni Ryal | +
| ZAR | + +South African Rand | +
| ZMK | + +Zambian Kwacha | +
| ZRZ | + +Zaire | +
| ZWD | + +Zimbabwean Dollar | +
Retour à la Page principale de la documentation. + + diff --git a/doc/html/fr/xacc-double.html b/doc/html/fr/xacc-double.html new file mode 100644 index 0000000000..c50b94996d --- /dev/null +++ b/doc/html/fr/xacc-double.html @@ -0,0 +1,149 @@ + + +
+ + +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
+
difficile à localiser, même quand la comptabilité
+du double livret est utilisé.
+
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 débité d'un montant exactement
+égal à celui dont l'autre est crédité.En
+s'assurant que chaque transaction
+
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 :J'ai oublié d'entrer cette partie de la transaction.
+
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 devez avoir un autre composant de cette transaction pour équilibrer +celà. +
Pas forcément un aparté: Si vous regardez votre +relevé de compte, il est typiquement décrit en détail +à partir du point de vue de la banque, qui est exactement +l'opposé du votre. Par exemple, quand vous y mettez de l'argent, +effectuant un dépôt, qui établit un DEBIT de +leur part/pour eux. +
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 "Revenu/Dépense" pour plus +d'informations sur celà +
Dans un système traditionnel qui enregistre
+les débits et crédits séparément, l'identité
+que toutes les transactions sont
+
requises pour satisfaire que Total de débits = Total
+de crédits.
+
Le fait que l'identité requiert seulement que le total
+des soldes veut dire que c'est un petit peu trompeux d'appeler celle-ci
+comptabilité de la double-entée; il devrait être
+quelque peu plus exact de l'appeler comptabilité multiple-entrée.
+Malheureusement, il y a 700 ans d'histoire d'utilisation de ce terme, ce
+qui sufisamment décourageant pour le changer.
+
(Et quelques gens pensent qu' UNIX a quelques croustillants et
+vieux morceau d'étrangeté. Hah!)
+
GnuCash traite les "Débits" comme valeurs positives, et "Crédits"
+comme valeurs négatives, de telle façon à ce que cette
+
identité simplifie en value1 + value2
++ value3 + ... = 0.
+
Un menu se déroulera , listant tous les comptes depuis lequel
+un transfert peut être réalisé.
+
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.
Pour changer une transaction à double entrée:
+
Afficher simplement la transaction dans n'importe quelle fenêtre +dans laquelle elle apparait +
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. +
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'ensemble des comptes . +
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 . +
En mode "relaché", vous pouvez créer des transactions
+anormales/non équilibrées, 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
+
de la double entrée, qui n'est pas probablement réellement
+une prudent modification. En effet:
+
Retour à la Page principale de la documentation.
+
+
+
diff --git a/doc/html/fr/xacc-expense.html b/doc/html/fr/xacc-expense.html
new file mode 100644
index 0000000000..1f1dbda56c
--- /dev/null
+++ b/doc/html/fr/xacc-expense.html
@@ -0,0 +1,195 @@
+
+
+
Celà simplifie trop les choses en quelque sorte; il est souvent
+une assez-bonne approximation quand je fais de la comptabilité
+
personelle, mais quand je fais fonctionner un commerce, revenus et
+dépenses ont souvent été reconnu/identifié
+comme ayant lieu quand quelques "évènement critique" ont
+lieu et qui peut-être ne corresponde pas parfaitement à "quand
+l'argent comptant rentre ou sort."
+
Par exemple, les sociétés habituellement doivent reconnaitre +revenus quand une vente se passe. Celà veut dire que j'ai +reconnu une vente de 100 000F sur le moment avec moi et le client +nous serrant la main lors de l'accord. +
Depuis que l'argent ne rentre pas, les ventes ont été
+estimé d'une autre manière; la manière qui est faite
+est de cumuler une vente à ce moment, et la faire mettre
+dans le solde de la transaction, plutôt que d'ajouter quelque chose
+en argent comptant,
+
j'ajoute les 100 000F de la vente dans Crédit fournisseurs.
+
Dans un système à double entrée, deux sortes de +comptes doivent être créés: certains de type "Revenus" +et d'autres de type "Dépenses ". (Il tend à y avoir beaucoup +plus de différents sortes de dépenses qu'il y a de revenus.) +
Les Revenus de ce genre: salaire, primes , intérêt bancaire +et les dividendes d'actions sont alors enregistrés comme transferts +depuis un compte revenus vers un compte bancaire (ou, en général, +quelques avoirs (actif) ) . De la même manière, les dépenses +sont enregistrés comme des transferts depuis un compte de carte +de crédit (ou, en général, un compte de passif(dettes)). +
Une autre voie pour décrire la nécessité de la +"double entrée" est que quand vous recevez un revenu, deux choses +se passent: +
| Compte | + +Débit | + +Crédit | +
|---|---|---|
| Compte chèques | + +1.600,00 | + ++ |
| Salaire | + ++ + | 1.600,00 | +
Celà peut être volontairement étendu à un
+grand nombre d'éléments "réparti" ainsi:
+
+
| Compte | + +Débit | + +Crédit | +
|---|---|---|
| Compte chèques | + +1.300,00 | + ++ |
| Impôts sur le revenu | + +200.00 | + ++ |
| Sécurité sociale | + +100.00 | + ++ |
| Salaire | + ++ + | 1.600,00 | +
Il peut y avoir un lot entier de plus de deux entrées dans la +transaction, mais la somme totale des débits, de 1.600,.00F, pourtant +égalera la somme totale des crédits, 1.600,00F. +
Si, comme avec GnuCash, tout est forcé sur une colonne, +de telle façon à ce que les débits soit représentés +par des valeurs positives, et les crédits sont représentés +par des valeurs négatives, les comptes revenus/dépenses font +légèrement une chose non-intuitive et vous voyez des revenus +comme valeurs négatives. Celà +apparait +contraire à l'intuition, mais c'est néanmoins nécessaire +pour que l'ordre de l' identité +de la comptabilité de la double-entrée se maintienne vraie. +
Une autre manière de voir la façon dont les comptes revenus +et dépenses sont spéciaux est que leurs totaux de comptes +n'apparaissent pas directement sur la feuille du solde/bilan. Une feuille +du solde montre la "Valeur nette": la somme de tous les avoirs moins +toutes les dettes. +
Les revenus et dépenses ne sont ni des avoirs ni des dettes, +et ainsi n'apparaissent pas sur la feuille du solde. Ce qui apparait sur +la feuille du solde est leurs effets sur les capitaux propres. +
Il y a un rapport séparé, un rapport "Pertes et profits" +(P&P), pour analyser les revenus et dépenses. Le profit total +(ou pertes) est calculé comme le total des revenus moins le total +des dépenses. D'une manière agréablement symétrique, +étant donné que les avoirs et les dettes ne sont ni des revenus +et ni des dépenses, ils n' apparaissent pas également +sur l'état des Pertes et Profits. +
Même si malgré tout ces comptes peuvent être en quelque +sorte "spéciaux", vous n'avez pas besoin de faire quelque chose +de particulièrement spécial pour utiliser les comptes de +revenus et dépenses. GnuCash traite les valeurs automatiquement, +de telle façon à ce que si vous enregistrez proprement les +effets des transactions sur votre compte bancaire ou de carte de crédit, +la face revenus/dépenses de la transaction devrait aussi être +chargé traité correctement. +
Le temps quand les choses deviennent "particulières," et quand +vous avez besoin de plus de compréhension profonde de celles-ci, +est quand les montants sont transférés entre les comptes +revenus/dépenses. (Les causes pour de tels transferts tendent +à être en quelque sorte particulières, ainsi c'est +une jolie exposition pour celui-ci d'être une jolie situation singulière.) +
Vous souhaitez sans doute créer un certain nombre de comptes +de revenus et dépenses; I peut être valable de regarder le +Tableau de comptes d'exemple pour des idées. +
Ce partitionnement de revenus et dépenses est surement prouvé +être particulièrement utile quand .le temps des impôts +arrive. +
Retour à la Page principale de la documentation. + + diff --git a/doc/html/fr/xacc-globalprefs.html b/doc/html/fr/xacc-globalprefs.html new file mode 100644 index 0000000000..d1351b6c4c --- /dev/null +++ b/doc/html/fr/xacc-globalprefs.html @@ -0,0 +1,50 @@ + + +
+ + +Pour changer les paramètres, cliquez simplement pour sélectionner +la page appropriée, alors faites les changements appropriées, +et cliquez sur le bouton "Appliquer" pour voir vos changements prendre +effet. Cliquer sur "OK" applique les changement, alors fermez la boîte +de dialogue propriétées. Le bouton "Fermer" ferme simplement +la boîte de dialogue sans appliquer les derniers changements. +
Les paramètres sont groupés dans les catégories +suivantes: +
Retour à la Page principale de la documentation. + + diff --git a/doc/html/fr/xacc-gpl.html b/doc/html/fr/xacc-gpl.html new file mode 100644 index 0000000000..863bed904e --- /dev/null +++ b/doc/html/fr/xacc-gpl.html @@ -0,0 +1,335 @@ + + +
++ Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed.
+
+
+ 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. + +
+ 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. + +
+ 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. + +
+ 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. + +
+ 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. + +
+ 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. + +
+ 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. + +
+ The precise terms and conditions for copying, distribution and + modification follow. +
++ 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". + +
+ 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. + +
+ 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. + +
+ 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. + +
+ 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: + +
+ a) You must cause the modified files to carry prominent notices + stating that you changed the files and the date of any change. ++ ++ 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. +
+ 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.) +
+
+ 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. + +
+ 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. + +
+ 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: + +
+ 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, ++ ++ 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, +
+ 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.) +
+ 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. + +
+ 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. +
+ ++ 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. + +
+ 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. + +
+ 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. + +
+ 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. + +
+ 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. +
+ ++ 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. + +
+ 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. + +
+ 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. + +
+ 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. +
+ +
+ 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. + +
+ 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. + +
Le tronc principal représente les catégories ou groupes +en entier, tandis que les feuillles de l'arbre contiennent des comptes +bancaires individuels ou des catégories de dépenses. +
Quand un rapport sommaire est demandé, typiquement seulement +les branches principales sont montrés dans le rapport, plutôt +que les comptes individuels. Par example, un tableau de comptes devrait +ressembler à ce qui suit: +
300 Dépenses + | + +--310 Dépenses en cours + | | + | +--311 Bière + | | + | +--312 Cable + | + +--320 Dépenses commerciales + | | + | +--321 Disquettes 8 pouces + | | + : :+Noter que les comptes n'ont pas seulement des noms; ils ont des codes,afin +de fournir un ordre. Quand un rapport est généré, +l'ordre de tri est déterminé entièrement par la numérotation. +
Une arborescence logique générallement aura la fin des +comptes "feuilles" en chiffre différent de zéro, tandis que +les noeuds parents ont des numéros croissant de zéro. +Par exemple, les comptes "liquidités" devraient logiquement être +arrangés ainsi: +
Un exemple de tableaux +de comptes +
Un
+tableau "typique" de comptes est montré ci-dessous. Chaque compte
+est un type de compte donné.C'est
+une
+
+combinaison de quelques comptes commerciaux et personnels typiques.
+
+>>>>>>> 1.2
+
Retour à la Page principale de la documentation.
Pour l'aide sur un sujet en particulier: +
Ces quelques pages représentent la documentation préliminaire +pour les sous-systemes qui ne sont pas encore suffisamment fonctionnel +pour être utilisé par les utilisateurs finaux. +
Ci dessous se trouve une image de la fenêtre principale , avec +seulement les comptes principaux affichés . Notez comment Business +Expenses a été sélectionné par surbrillance +. La boîte avec une croix à l'intérieur d'elle, immediatement +à sa gauche, montre qu'il y a un un ou plus de comptes detaillés +qui ne sont pas montrés en ce moment. Pour le voir, cliquez sur +cette boîte. +
+
Ci-dessous se trouve la fenêtre principale , avec les détails
+des comptes affichés.
+
+
+
+
+
This report summarizes your sources of income and expenditure.
+ +There are currently no options for this report, but the option + to specify an accounting period will be added soon.
+ +Return to Main Documentation + Page.
+ + diff --git a/doc/html/fr/xacc-print.html b/doc/html/fr/xacc-print.html new file mode 100644 index 0000000000..5ae845b9ba --- /dev/null +++ b/doc/html/fr/xacc-print.html @@ -0,0 +1,46 @@ + + + + + +
Suivant la dernière tendance à la mode de l'exagération
+internet, GnuCash peut aussi agir comme un serveur web sans valeur!
+
+
Retour à la Page principale de la documentation + + diff --git a/doc/html/fr/xacc-quicken.html b/doc/html/fr/xacc-quicken.html new file mode 100644 index 0000000000..2dba01fdd1 --- /dev/null +++ b/doc/html/fr/xacc-quicken.html @@ -0,0 +1,156 @@ + + +
+ + +Ce que Quicken appelle "Catégories" sont juste réellement +des comptes Revenus/Dépenses . Ainsi, +si vous utilisez les spécifications d'une catégorie dans +Quicken, créez juste un compte revenus/dépenses du même +nom dans Gnucash, et utilisez le comme le nom d'un compte. +
Notez que le format QIF est representif dans une certaine mesure d'un +modèle de données particulier qui n'est pas aussi expressif:adapté +que l'on aurait voulu; il requiert pour chaque compte de se faire enregistrer +dans un fichier de données séparé, plutôt que +de vous permettre d'avoir un fichier qui représente tous +les comptes que vous pouvez avoir eu dans Quicken. +
De plus, tandis qu'il y a des plans pour faire ainsi dans le futur,
+il n'y a pas, à ce point, une solution pour organiser les noms de
+catégories ou comptes utilisés dans Quicken vers un différent
+ensemble de noms de compte que vous puissiez utiliser dans
+
GnuCash.
+
En conséquence de, s'il vous plaît lisez cette section +avec attention. Il se peut en quelque sorte que vous soyez déçu +avec les résultats d'une importation de fichier QIF; celà +vous donnera au moins quelques espérances plus précises quant +à ce qui se passera. +
Il fonctionne avec Wine, Wabi
+de Caldera, et sans doute sur VMWare, ainsi il n'est pas requis que vous
+démarreriez Windows.
+
Quicken ne peut exporter seulement qu'un compte pour chaque
+fichier de données, ce qui veut dire que si vous avez plusieurs
+comptes, ce là se révèlera être un procesus
+quelquesc peu pénible. (D'un autre coté, il devrait être
+en globalité
+
moins pénible que d'entrer les données depuis
+zéro/rien.)
+
Celà fournira une boite de dialogue qui demandera un nom
+de fichier, les dates effectives, en plus d'une série de
+
boite à cocher, incluant Transactions, Liste
+de comptes, Liste de catégories, et ainsi dorénavant.
+
Pour de meilleurs résultats, vous devrez etre sûr +d'avoir ces trois dernières qui soit vérifiées/activées. +
Si vous ne vérifiez pas la boite Listes de Comptes,
+alors le nom de votre compte sera probablement perdu., et que
+
celà causera des problèmes quand vous essairez d'importer
+des données dans GnuCash plus tard.
Notez que durant la fusion, une analyse est effectuée pour
+les transactions dupliquées , et les doubles sont enlevés.
+Une transaction dupliquée est où la date, la description
+(bénéficiaire), mémo, quantitée, prix du titre
+, et les comptes ou catégories débités/crédités
+se retrouve exactement. Ainsi, la fusion devrait être
+sûr à moins que vous ayez de multiples transactions à
+la même date, au même compte , pour le même montant ,
+avec la même description et mémo.
+
Celà malheureusement peut se produire, le scénario +typique se produit quand vous faites de multiples retraits d'argent liquide +de montants identiques à partir de DAB (distributeur automatique +de billets) le même jour. +
Notez que quand la "Liste des Comptes " et la "Liste de Catégories"
+est exporté depuis Quicken, tous les comptes et catégories
+seront exportés, même s'ils sont vides et ne contiennent pas
+de transactions. Quand ceux-ci sont importés, ils apparaitront comme
+des comptes avec un solde de zéro. Si vous n'avez pas besoin ou
+n'utilisez pas ces comptes , soyez libre de les supprimer . Les futures
+améliorations de Gnucash vous permettront de les supprimer "en-masse",
+ou de les rendre invisible sans les supprimer.
+
Pour plus de détails à propos du format d'échange
+QIF peuvent être trouvés ici.
+
+
Retour à la Page principale de la documentation.
+
La fenêtre de rapprochement est pour le rapprochement des enregistrements +des utilisateurs à la fin du mois quand le relevé bancaire +arrive. Par example, si vous écrivez un chèque pour quelqu'un +, entrez la transaction. Quand vous savez que que le chèque a été +pointé (débité de votre compte) , vous pouvez cliquez +le champ entre les champs de description et de paiement , et le changer +depuis 'n' vers 'c', indiquant que la transaction a été pointée +A la fin du mois , ouvrez la fenêtre de rapprochement , et xacc vous +suggèrera /soufflera l'entrée du solde final à partir +du relevé bancaire . Alors la fenêtre de rapprochement apparaitra +, et vous verrez une colonne de crédit et de débit qui listera +toutes les transactions non rapprochés . Vous pouvez alors pointer +les transactions qui apparaissent dans le relevé bancaire , et vérifier +que le montant des champs soit correct. En bas de la fenêtre se trouve +un champ différence , qui devrait être de 0.00F quand vous +avez fait le rapprochement . Si'il ne l'est pas alors vous avez laisser +échapper une transaction, ou un des montants est erroné (ou +faux). Quand vous cliquez sur "Ok", alors le 'n' ou 'c' dans les transactions +qui ont été pointé se changera en un 'y'. Quand vous +changez quelque chose dans une transaction de rapprochement , une boite +de dialogue de verification devrait apparaitre , mais celà ne semble +pas être encore un évènement. Aussi , le total "pointé" +en bas semble afficher F0.00 sans se soucier de ces transactions qui ont +été pointés ou rapprochés . Le total"pointé" +devrait afficher le total de seulement les transactions qui ont été +pointés ('c') ou rapprochés ('y'). +
+
+C'est la fenêtre du Registre/Grand Livre(ou d'enregistrement ). +Les transactions sont entrées ici . +
Pour entrer une nouvelle transaction, tapez juste à l'intérieur +de la dernière transaction vierge. Utilisez la souris (ndt : ou +le mulot pour ce qui préfère) ou les Raccourcis +clavier du registre pour se déplacer entre les champs, et frappez +la touche Entrée ou cliquez sur Enregistrer pour enregistrer la +transaction: +
+
Remarquez comment la transaction a été enregistrée +et une transaction vierge, nouvelle a été créée. +
Vous pouvez affichez des transactions existantes de la même manière.
+GnuCash vous demandera de confirmer n'importe quel
+
changements que vous ayez fait.
+
Le registre peut afficher les transactions dans plusieurs styles différents: +
Les transactions existantes sont normallement affichées dans
+l'ordre de la date, mais celà peut auusi être changé
+avec
+
"Trier par ordre". Vous pouvez aussi sélectionner une échelle
+de date durant laquelle les transactions seront affichées avec
+"Echelle de date".
+
L'état du rapprochement d'une transaction est montré par
+le champ rapprochement (R) . 'c' indique qu'une transaction a été
+
rapprochée, 'n' indique qu'elle ne l'est pas. Vous pouvez changer
+l'état du rapprochement en cliquant sur le champ 'r' de la
+
transaction.
+
En bas de la fenêtre du compte, il y a deux soldes en cours, le +solde "pointé et rapproché", et le solde "total"... le solde +"pointé et rapproché " devrait correspondre à la totalité +de l'argent que la banque pense que vous ayez sur votre compte, et le solde +"total" inclut les transactions en cours de règlement. +
Le rapprochement peut être fait dans la fenêtre +de rapprochement +
+
+
Le registre du porte-feuille peut intimidé un peu au premier +abord . +
Si vous avez de la peine à le comprendre , alors tournez vous +vers la création de comptes qui contiennent une seule valeur d'action. +
Quelques points importants à se souvenir à propos de la +fenêtre du porte-feuille: +
+
Le rapport est affiché dans une fenêtre redimensionnable +et déroulante. Pour controler le rapport, vous pouvez utilisez les +boutons de la barre d'outils en haut de la fenêtre: +
+
+
Voyez l'aide pour les rapports individuels pour les détails des +options disponibles. +
L'interface de rapport est actuellement non documenté, mais vous +pouvez obtenir une bonne idée de comment il fonctionne en +examinant le fichier src/scm/report/hello-world.scm dans la distribution +du source de GnuCash. +
Vous aurez aussi besoin pour accédez aux données du "moteur" +d'obtenir de l'information pour votre rapport. Celà est accompli +par un ensemble de fonctions d'encapsulage Scheme qui sont documentés +dans le fichier src/g-wrap/gnc.html. Vous pouvez souhaiter examiner quelques +uns des autres rapports dans src/scm/report pour une indication de comment +ils sont utilisés. +
A présent, les rapports sont produit intérieurement en +créant du HTML et en présentant celà avec un widget +HTML. (Les futures versions de GnuCash supporteront si tout va bien un +système plus flexible). +
Si vous avez besoin plus d'information, ou avez développé +un nouveau rapport qui peut être utilisé par les autres, s'il +vous plait contactez la liste de courriers de développement +de GnuCash (mailing list) à gnucash-devel@gnucash.org. +
Retour à la Page principale de la documentation. + + diff --git a/doc/html/fr/xacc-ticker.html b/doc/html/fr/xacc-ticker.html new file mode 100644 index 0000000000..2c0f1d6dbe --- /dev/null +++ b/doc/html/fr/xacc-ticker.html @@ -0,0 +1,102 @@ + + +
+ + +Si un compte d'actions de +Gnucash est convenablement configuré, et l'ordinateur hôte +est connecté sur internet, le programme gnc-prices peut +être utilisé pour récupérer les cotations +des cours d'actions et de fonds communs (pas de FCP et de SICAV pour la +france) à partir de divers sites web directement dans GnuCash. +
Pour utiliser cette fonctionnalité, ce qui suit doit être +fait: +
Un exemple d'image est montré ci-dessous: +
+
Pour mettre à jour les cours stockés dans un fichier de +compte de gnucash, lancez en ligne de commande gnc-price, en specifiant +le nom du fichier; par exemple: +
gnc-prices myaccts.xac+En lançant cette commande, elle affichera divers messages de diagnostic +vers l'écran tandis qu'elle chargera les données. Elle fonctionnera +seulement quand l'ordinateur hôte est connecté à internet. +Elle peut fonctionner ensemble avec un parefeu/firewall de style +masqué. Elle ne fonctionne pas actuellement depuis derrière +des parefeu de style socks. +
La commande peut être lancée plusieurs fois dans une journée; +pourtant, elle mettra les comptes à jour au maximum une fois avec +les plus récentes données du cours des échanges de +la journée. +
Ainsi, si gnc-prices est lancé le vendredi, samedi, +dimanche et lundi, seulement deux chargement de cours seront effectués: +un contenant les données du vendredi, et un contenant les données +du lundi, tandis que celui lancé le samedi et dimanche retrouvera +seulement les cours de clôture du vendredi. +
Pour empêcher gnc-prices de mettre à jour un compte, +tandis que vous lui permettez de mettre à jour un autre compte, +marquez simplement les données source pour ce compte comme "(aucun)". +Vous pouvez le faire depuis la fenêtre "Afficher un compte". +
Après avoir lancé gnc-prices pendant quelques jours, vos +comptes commenceront à ressembler à ce qui suit: +
+
Transaction reports list details for transactions in a specified + account over a specified period, in a convenient format for + viewing and exporting.
+Options specifiable for this report include:
+Return to Main Documentation + Page.
+ + diff --git a/doc/html/fr/xacc-y2k.html b/doc/html/fr/xacc-y2k.html new file mode 100644 index 0000000000..134307f458 --- /dev/null +++ b/doc/html/fr/xacc-y2k.html @@ -0,0 +1,45 @@ + + + + + +Le format de fichier pour la version 1.1.25 et suivantes stocke les +dates de la manière cité ci-dessus. +
Quelques routines internes utilisent le type time_t pour exprimer +les secondes. Noter que sur la plupart des OS, c'est une longueur de 32-bit, +et elle est limité à l'ère Unix (Déc 1901 à +Jan 2038).Il est résonnable d'espérer que time_t +sera migré vers l'utilisation de valeurs de 64 bit à ce moment +là. +
Les fichiers de sauvegarde et log sont estampillé temporellement +en utilisant la routine standard Unix ctime(), qui prend comme +argument time_t. Ainsi, le mécanisme de sauvegarde et de +log pourrait éprouver des troubles en 2038.Supposant que votre Unix +actuel continue à être en service à ce moment là +sans aucune correction. +
Notez aussi que GnuCash reconnait correctement le 29 février +2000 comme une "année bissextile," une autre des "dates critiques +de l'année 2000." +
Il est très fortement suggéré que GnuCash devrait +faire face raisonnablement bien à la transition vers le nouveau +millénaire, ou qu'il prend place en 2000 ou en 2001... +
Les éléments de l'an 2000 sont décrits en plus
+de détails à Linux
+et l'an 2000.
+
+
Retour à la Page principale de la documentation. + + diff --git a/doc/html/gnucash.css b/doc/html/gnucash.css new file mode 100644 index 0000000000..148c57cfbc --- /dev/null +++ b/doc/html/gnucash.css @@ -0,0 +1,35 @@ +/* Style Sheet */ +/* $Id$ */ + +BODY{ background-color:#EEFFEE; +/* background-image: url(http://www.isomedia.com/homes/tboyle/greenpaper.gif); */ + background-repeat: repeat-y;} + +SPAN.indent{margin-left:0.4in;} + +/* This may be a bit excessively loud... */ +H1, H2, H3, H4 {font-family: Optima, Lucida, Helvetica, sans-serif; + color: green; background-color: transparent; + font-weight: bolder; } + +/* Utopia, Helvetica, Optima, Lucida Typewriter */ + +H1{ font-size: 18pt;} +H2{ font-size: 16pt;} +H3{ font-size: 14pt;} +H4{ font-size: 12pt;} + +/* And make the main title big, centre it */ + +H1.title {font-size: 24pt; text-align: center; color: maroon; +background-color: transparent; font-family: Optima, Lucida, Helvetica, +sans-serif;} + +DEL {font-weight: bold} +INS {background-color: white} + +/* Zowie way of presenting PRE stuff */ + +PRE,TT.LITERAL,P.LITERALLAYOUT{ font-family:Lucida Typewriter, Courier, +monospace; font-weight: normal; background-color: gray; color: white; +border-width: thin; white-space:pre; } diff --git a/doc/html/logos/NetBSD-banner.gif b/doc/html/logos/NetBSD-banner.gif new file mode 100644 index 0000000000..8796228cde Binary files /dev/null and b/doc/html/logos/NetBSD-banner.gif differ diff --git a/doc/html/logos/bullogogross.gif b/doc/html/logos/bullogogross.gif new file mode 100644 index 0000000000..6acdfdb605 Binary files /dev/null and b/doc/html/logos/bullogogross.gif differ diff --git a/doc/html/logos/debian.jpg b/doc/html/logos/debian.jpg new file mode 100644 index 0000000000..906ecffb71 Binary files /dev/null and b/doc/html/logos/debian.jpg differ diff --git a/doc/html/logos/ibm.gif b/doc/html/logos/ibm.gif new file mode 100644 index 0000000000..2ee97f792e Binary files /dev/null and b/doc/html/logos/ibm.gif differ diff --git a/doc/html/logos/linux.gif b/doc/html/logos/linux.gif new file mode 100644 index 0000000000..6a136a030f Binary files /dev/null and b/doc/html/logos/linux.gif differ diff --git a/doc/html/logos/sgi.gif b/doc/html/logos/sgi.gif new file mode 100644 index 0000000000..bb00dce8f1 Binary files /dev/null and b/doc/html/logos/sgi.gif differ diff --git a/doc/html/logos/skunkware.gif b/doc/html/logos/skunkware.gif new file mode 100644 index 0000000000..a19d9baabb Binary files /dev/null and b/doc/html/logos/skunkware.gif differ