gnucash-docs master: Multiple changes pushed
Frank H. Ellenberger
fell at code.gnucash.org
Wed Dec 30 20:23:33 EST 2015
Updated via https://github.com/Gnucash/gnucash-docs/commit/719cd6ee (commit)
via https://github.com/Gnucash/gnucash-docs/commit/7a724a44 (commit)
via https://github.com/Gnucash/gnucash-docs/commit/ea21315d (commit)
via https://github.com/Gnucash/gnucash-docs/commit/6f7266df (commit)
via https://github.com/Gnucash/gnucash-docs/commit/959c8f96 (commit)
via https://github.com/Gnucash/gnucash-docs/commit/3d64029b (commit)
via https://github.com/Gnucash/gnucash-docs/commit/f608b33c (commit)
via https://github.com/Gnucash/gnucash-docs/commit/9ca3fae2 (commit)
via https://github.com/Gnucash/gnucash-docs/commit/09046088 (commit)
via https://github.com/Gnucash/gnucash-docs/commit/c4361a37 (commit)
via https://github.com/Gnucash/gnucash-docs/commit/1d0d4e9c (commit)
via https://github.com/Gnucash/gnucash-docs/commit/27032cfd (commit)
via https://github.com/Gnucash/gnucash-docs/commit/451f2e3c (commit)
via https://github.com/Gnucash/gnucash-docs/commit/d3e3d415 (commit)
via https://github.com/Gnucash/gnucash-docs/commit/e92d1a48 (commit)
via https://github.com/Gnucash/gnucash-docs/commit/bb2edbe6 (commit)
via https://github.com/Gnucash/gnucash-docs/commit/19262a6c (commit)
via https://github.com/Gnucash/gnucash-docs/commit/62870011 (commit)
via https://github.com/Gnucash/gnucash-docs/commit/1cc18dbd (commit)
via https://github.com/Gnucash/gnucash-docs/commit/63bf8337 (commit)
from https://github.com/Gnucash/gnucash-docs/commit/959ec94f (commit)
commit 719cd6eeaed7d66b85b05e6738968d138949c1ff
Merge: 959ec94 7a724a4
Author: fell <f.ellenberger at online.de>
Date: Thu Dec 31 02:17:51 2015 +0100
Merge branch 'maint'
commit 7a724a441a218093e6596f8e08c3d584b72944cf
Author: fell <f.ellenberger at online.de>
Date: Thu Dec 31 02:13:09 2015 +0100
Add Eclipse specific files to gitignore
diff --git a/.gitignore b/.gitignore
index 78e3971..9b9ef9d 100644
--- a/.gitignore
+++ b/.gitignore
@@ -54,3 +54,7 @@ omf_timestamp
*/*.html
*/*/*/*.html
*/*/*.html
+/.settings/
+/.autotools
+/.cproject
+/.project
commit ea21315de596dde68022a78f5dd942a6c039b827
Author: fell <f.ellenberger at online.de>
Date: Thu Dec 31 02:06:42 2015 +0100
Improve german wordening around the last commit
diff --git a/guide/de/ch_basics.xml b/guide/de/ch_basics.xml
index b56b935..d028d37 100644
--- a/guide/de/ch_basics.xml
+++ b/guide/de/ch_basics.xml
@@ -176,8 +176,10 @@
Die Bezeichnung <emphasis>doppelte</emphasis> Buchführung ist für neue Nutzer etwas
irreführend, weil <application>&app;</application> Ihnen
erlaubt die allgemeinen Begriffe <guilabel>Einzahlung</guilabel> und
- <guilabel>Auszahlung</guilabel> zu nutzen. Wenn Sie die formalen Buchhaltungsausdrücke vorziehen, können Sie die Kopfzeilen in der Kontenansicht ändern, um sie im
- <guilabel>Konten</guilabel>-Reiter unter <guilabel>Eigenschaften</guilabel> nutzen.</para>
+ <guilabel>Auszahlung</guilabel> zu nutzen. Wenn Sie die formalen Buchhaltungsausdrücke vorziehen,
+ können Sie die Kopfzeilen der Kontenansicht ändern, indem sie <guilabel>Buchungsüberschriften aus dem Rechnungswesen</guilabel>
+ auf dem <guilabel>Konten</guilabel>-Reiter unter <menuchoice><guimenu>Bearbeiten</guimenu>
+ <guimenuitem>Eigenschaften</guimenuitem></menuchoice> markieren.</para>
</note>
<warning>
commit 6f7266df3cdcc4a125ef227c350da8da8133f62d
Author: fell <f.ellenberger at online.de>
Date: Thu Dec 31 01:50:41 2015 +0100
Formal accounting terms are selectable on the preferences accounts tab
Thanks to omni on IRC
diff --git a/guide/C/ch_basics.xml b/guide/C/ch_basics.xml
index 3c95f25..c6e2cc5 100644
--- a/guide/C/ch_basics.xml
+++ b/guide/C/ch_basics.xml
@@ -175,7 +175,7 @@
common terms <guilabel>Deposit</guilabel> and
<guilabel>Withdrawal</guilabel>. If you prefer the formal accounting
terms, you can change the account register column headings to use
- them in the <guilabel>General</guilabel> tab under
+ them in the <guilabel>Accounts</guilabel> tab under
<guilabel>Preferences</guilabel> (see the
<application>&app;</application> Help Manual for more information on
setting preferences).</para>
diff --git a/guide/de/ch_basics.xml b/guide/de/ch_basics.xml
index 83255d0..b56b935 100644
--- a/guide/de/ch_basics.xml
+++ b/guide/de/ch_basics.xml
@@ -177,7 +177,7 @@
irreführend, weil <application>&app;</application> Ihnen
erlaubt die allgemeinen Begriffe <guilabel>Einzahlung</guilabel> und
<guilabel>Auszahlung</guilabel> zu nutzen. Wenn Sie die formalen Buchhaltungsausdrücke vorziehen, können Sie die Kopfzeilen in der Kontenansicht ändern, um sie im
- <guilabel>Allgemein</guilabel>-Reiter unter <guilabel>Eigenschaften</guilabel> nutzen.</para>
+ <guilabel>Konten</guilabel>-Reiter unter <guilabel>Eigenschaften</guilabel> nutzen.</para>
</note>
<warning>
commit 959c8f963a9fccefc2940c3a015f1dfe13fdc31b
Author: fell <f.ellenberger at online.de>
Date: Thu Dec 31 01:44:26 2015 +0100
Add missing file to guide/de/Makefile.am
diff --git a/guide/de/Makefile.am b/guide/de/Makefile.am
index 4b9ce4e..05451a4 100644
--- a/guide/de/Makefile.am
+++ b/guide/de/Makefile.am
@@ -15,6 +15,7 @@ entities = \
ch_cbook.xml \
ch_cc.xml \
ch_currency.xml \
+ ch_dep.xml \
ch_import_business_data.xml \
ch_loans.xml \
ch_invest.xml \
commit 3d64029b5ceb3e1110595c9b3ffa5c3c3d2ceeae
Author: John Ralls <jralls at ceridwen.us>
Date: Wed Dec 30 10:10:04 2015 -0800
Add missing sect1 element.
diff --git a/guide/de/ch_bus_ap.xml b/guide/de/ch_bus_ap.xml
index b88c7e0..627aaee 100644
--- a/guide/de/ch_bus_ap.xml
+++ b/guide/de/ch_bus_ap.xml
@@ -18,17 +18,17 @@ A lot of the following text is duplicated in the GnuCash help. The text here in
corrected to be less describing of the interface and more tutorial oriented
-->
- <chapter id="chapter_bus_ap">
- <title>Kreditorenbuchhaltung</title>
- <para>Die Kreditorenbuchhaltung bezieht sich auf Lieferungen und Leistungen, die ein Unternehmen gekauft hat und nun bezahlen muss.</para>
-
+<chapter id="chapter_bus_ap">
+ <title>Kreditorenbuchhaltung</title>
+ <para>Die Kreditorenbuchhaltung bezieht sich auf Lieferungen und Leistungen, die ein Unternehmen gekauft hat und nun bezahlen muss.</para>
+ <sect1 id="bus_ap_setup1">
<title>Starteinrichtung</title>
<para>Durchführung der Einrichtung ist in <xref linkend="chapter_bus_setup" />
beschrieben.
</para>
-
+ </sect1>
<sect1 id="bus-ap-components1">
<title>Systemkomponenten</title>
<para><application>&app;</application> hat eine integrierte Kreditorenbuchhaltung.
commit f608b33c7c3db5a6f5653a5dbc95a7ee08a15415
Author: Mechtilde <ooo at mechtilde.de>
Date: Wed Dec 30 15:45:05 2015 +0100
add als few corrections
diff --git a/guide/de/ch_budgets.xml b/guide/de/ch_budgets.xml
index 568a623..f35c7a6 100644
--- a/guide/de/ch_budgets.xml
+++ b/guide/de/ch_budgets.xml
@@ -43,7 +43,7 @@ guide will help you make some of those decisions.</para>
<listitem>
<para><emphasis>Cash Budget</emphasis> - A budget planning for
expected cash receipts and cash disbursements. This type of
- budget tracks cash flow -- where your money comes from, where it
+ budget tracks cash flow — where your money comes from, where it
goes, and, of course, how much.</para>
</listitem>
<listitem>
diff --git a/guide/de/ch_bus_ap.xml b/guide/de/ch_bus_ap.xml
index 9a9dafa..b88c7e0 100644
--- a/guide/de/ch_bus_ap.xml
+++ b/guide/de/ch_bus_ap.xml
@@ -28,7 +28,6 @@ corrected to be less describing of the interface and more tutorial oriented
<para>Durchführung der Einrichtung ist in <xref linkend="chapter_bus_setup" />
beschrieben.
</para>
- </sect1>
<sect1 id="bus-ap-components1">
<title>Systemkomponenten</title>
diff --git a/guide/de/gnucash-guide.xml b/guide/de/gnucash-guide.xml
index 46d2cae..42e9530 100644
--- a/guide/de/gnucash-guide.xml
+++ b/guide/de/gnucash-guide.xml
@@ -25,7 +25,7 @@
<!ENTITY chapter14 SYSTEM "ch_bus_ap.xml">
<!ENTITY chapter15 SYSTEM "ch_bus_pay.xml">
<!ENTITY chapter16 SYSTEM "ch_budgets.xml">
-<!ENTITY chapter17 SYSTEM "ch_oth_assets.xml">
+<!ENTITY chapter17 SYSTEM "ch_oth_assets.xml">
<!ENTITY chapter18 SYSTEM "ch_dep.xml">
<!ENTITY chapter19 SYSTEM "ch_python_bindings.xml">
<!ENTITY chapter20 SYSTEM "ch_import_business_data.xml">
commit 9ca3fae26d0ec10958ae268b49a2a5d1b2c8cda9
Author: Mechtilde <ooo at mechtilde.de>
Date: Wed Dec 30 15:09:02 2015 +0100
add some more files needed translation
diff --git a/guide/de/Makefile.am b/guide/de/Makefile.am
index a1891a6..4b9ce4e 100644
--- a/guide/de/Makefile.am
+++ b/guide/de/Makefile.am
@@ -22,7 +22,12 @@ entities = \
ch_oview.xml \
ch_python_bindings.xml \
ch_txns.xml \
+ appendixa.xml \
+ appendixb.xml \
+ appendixc.xml \
+ appendixd.xml \
appendixe.xml \
+ fdl-appendix.xml \
glossary.xml
DISTCLEANFILES = $(docname)-de.omf.out
CLEANFILES = $(DISTCLEANFILES)
diff --git a/guide/de/appendixa.xml b/guide/de/appendixa.xml
new file mode 100644
index 0000000..7098da7
--- /dev/null
+++ b/guide/de/appendixa.xml
@@ -0,0 +1,130 @@
+<!--
+ (Do not remove this comment block.)
+ Version: 2.0.0
+ Last modified: July 9th 2006
+ Maintainers:
+ Chris Lyttle <chris at wilddev.net>
+ Author:
+ Jon Lapham <lapham at extracta.com.br>
+ Originally designed by Carol Champagne.
+ Translators:
+ (translators put your name and email here)
+-->
+ <appendix id="appendixa">
+ <title>Migration Guide</title>
+ <para>&untranslated;</para>
+ <!--
+ <para>
+This appendix is to help current users of other financial software packages in their migration to <application>&app;</application>. We address the conceptual differences between the layout of <application>&app;</application> accounts versus other software packages.
+ </para>
+
+<sect1 id="appendixa_accts_vs_cats1">
+<title>Using Accounts vs. Categories</title>
+<para>
+If you are familiar with other personal finance programs, you are already accustomed to tracking your income and expenses as categories. Since <application>&app;</application> is a double-entry system (refer to section 2.1), incomes and expenses are tracked in accounts. The basic concept is the same, but the account structure allows more consistency with accepted business practices. So, if you are a business user as well as a home user, <application>&app;</application> makes it easy to keep track of your business as well as your personal accounts.
+</para>
+<para>
+Income and expense accounts give you the same information you would get with categories, but they also give you more flexibility in entering your transactions. In <application>&app;</application>, you have the option to enter transactions directly into income and expense accounts through their account registers. Other programs that use categories do not offer this option, because there is no <quote>account register</quote> for a category.
+</para>
+<para>
+You also have the option in <application>&app;</application> to treat income and expense accounts exactly as you would treat categories, if you are more comfortable with that method. In <trademark class="registered">Quicken</trademark> and similar programs, transactions require an account and a category. Substitute an income or expense account name in <application>&app;</application> where you would normally enter a category name in the other programs, and the result should be the same. We will discuss transaction entry in Chapter 4 in greater detail.
+</para>
+</sect1>
+
+ <sect1 id="appendixa_qif1">
+ <title>Organization of <acronym>QIF</acronym> Files (Discussion)</title>
+ <para>
+ </para>
+ </sect1>
+ <sect1 id="appendixa_entercharge1">
+ <title>Common Duplication Issues (Discussion)</title>
+ <para>
+ </para>
+ </sect1>
+ <sect1 id="appendixa_enterpay1">
+ <title>Checking <acronym>QIF</acronym> Data (Discussion)</title>
+ <para>
+ </para>
+ </sect1>
+
+<sect1 id="appendixa_xmlconvert1">
+<title>Converting <acronym>XML</acronym> <application>&app;</application> File</title>
+ <para>The <application>&app;</application> <acronym>XML</acronym> data file can be transformed to almost any other data
+format (e.g., <acronym>QIF</acronym>, <acronym>CSV</acronym>...) quite easily if one is familiar with <acronym>XSLT</acronym>.
+The <application>&app;</application> data file is well-formed <acronym>XML</acronym>, and it can therefore be run
+through an <acronym>XSLT</acronym> parser with an associated stylesheet. This allows one
+to transform the file to just about any format that can be designed,
+given a properly written stylesheet.</para>
+
+ <para>A few steps need to be followed. The writing of a stylesheet is a task
+for a different time, but if you can get one written, here’s what you
+need to do:</para>
+ <orderedlist>
+ <listitem>
+ <para>Copy the <application>&app;</application> <acronym>XML</acronym> data file to a working file.</para>
+ <note>
+ <para>If the file was last modified by a version of <application>&app;</application> older than 2.0, then
+before to continue to the next step you will need to modify the working file’s <gnc-v2>
+tag to read something like this:</para>
+ <literallayout>
+<gnc-v2 xmlns:cd="http://www.gnucash.org/XML/cd"
+ xmlns:book="http://www.gnucash.org/XML/book"
+ xmlns:gnc="http://www.gnucash.org/XML/gnc"
+ xmlns:cmdty="http://www.gnucash.org/XML/cmdty"
+ xmlns:trn="http://www.gnucash.org/XML/trn"
+ xmlns:split="http://www.gnucash.org/XML/split"
+ xmlns:act="http://www.gnucash.org/XML/act"
+ xmlns:price="http://www.gnucash.org/XML/price"
+ xmlns:ts="http://www.gnucash.org/XML/ts"
+ xmlns:slot="http://www.gnucash.org/XML/kvpslot"
+ xmlns:cust="http://www.gnucash.org/XML/cust"
+ xmlns:entry="http://www.gnucash.org/XML/entry"
+ xmlns:lot="http://www.gnucash.org/XML/lot"
+ xmlns:invoice="http://www.gnucash.org/XML/invoice"
+ xmlns:owner="http://www.gnucash.org/XML/owner"
+ xmlns:job="http://www.gnucash.org/XML/job"
+ xmlns:billterm="http://www.gnucash.org/XML/billterm"
+ xmlns:bt-days="http://www.gnucash.org/XML/bt-days"
+ xmlns:sx="http://www.gnucash.org/XML/sx"
+ xmlns:fs="http://www.gnucash.org/XML/fs"
+ xmlns:addr="http://www.gnucash.org/XML/custaddr">
+ </literallayout>
+ <para>You can put pretty much anything you want behind the equal signs, but a <acronym>URL</acronym>
+is what is typically used.</para>
+ </note>
+ </listitem>
+ <listitem>
+ <para>Create an <acronym>XSLT</acronym> stylesheet containing the transformation your desire,
+or obtain one that’s already written (AFAIK, there aren’t any, but I’m
+working on a <acronym>CSV</acronym> one).</para>
+ </listitem>
+ <listitem>
+<para>Install an <acronym>XSLT</acronym> processor such as Saxon
+(http://saxon.sourceforge.net/) or Xalan-J (http://xml.apache.org/).
+Any conforming processor will do, really...</para>
+ </listitem>
+ <listitem>
+<para>Run the work file and the stylesheet through the processor according
+to the processor’s instructions.</para>
+ </listitem>
+ <listitem>
+<para>You will now have a file in the desired output format. An
+enterprising individual could go so far as to write a stylesheet to
+transform the <application>&app;</application> data file to an OpenOffice spreadsheet (or
+vice-versa, for that matter). Such things as <acronym>QIF</acronym> ought to be a little
+less work.</para>
+ </listitem>
+ </orderedlist>
+
+<para>Benefits are that you don’t need to write a Scheme module or a new C
+routine to do this transformation. Anyone who knows or can learn <acronym>XML</acronym>
+and <acronym>XSLT</acronym> can perform this task. Not much harder, really, than writing a
+Web page....</para>
+
+<para>Anyhow, I just wanted this tidbit to be captured somewhere permanently.
+The process works on &vers-stable; datafiles, and ought to
+work on earlier versions, too.</para>
+
+ </sect1>
+-->
+ </appendix>
diff --git a/guide/de/appendixb.xml b/guide/de/appendixb.xml
new file mode 100644
index 0000000..ba039f8
--- /dev/null
+++ b/guide/de/appendixb.xml
@@ -0,0 +1,140 @@
+<!--
+ (Do not remove this comment block.)
+ Version: 2.0.0
+ Last modified: July 9th 2006
+ Maintainers:
+ Chris Lyttle <chris at wilddev.net>
+ Author:
+ Jon Lapham <lapham at extracta.com.br>
+ Originally designed by Carol Champagne.
+ Translators:
+ (translators put your name and email here)
+-->
+ <appendix id="appendixb">
+ <title>Frequently Asked Questions</title>
+ <para>&untranslated;</para>
+ <!--
+ <para>This is a list of questions asked on the mailing lists for which there really is no section in the documentation covering the subject.</para>
+ <sect1 id="appendixb_info">
+ <title>Sources of Information</title>
+
+ <sect2 id="appendixb_info_where">
+ <title>Q: Where’s the FAQ?</title>
+ <para>A: You’re looking at it. The most up-to-date copy can be found <ulink url="http://wiki.gnucash.org/wiki/FAQ">within the <application>&app;</application> Wiki</ulink>.</para>
+ </sect2>
+
+ <sect2 id="appendixb_info_mail">
+ <title>Q: Are there mailing lists for <application>&app;</application>?</title>
+ <para>A: Yes. Go to <ulink url="http://lists.gnucash.org/mailman/listinfo/gnucash-user">http://lists.gnucash.org/mailman/listinfo/gnucash-user</ulink> and <ulink url="http://lists.gnucash.org/mailman/listinfo/gnucash-devel">http://lists.gnucash.org/mailman/listinfo/gnucash-devel</ulink> to subscibe.</para>
+ </sect2>
+
+ <sect2 id="appendixb_info_mailarchive">
+ <title>Q: Is there a searchable archive for the mailing lists?</title>
+ <para>A: Yes, you can search the mail list archives at <ulink url="http://news.gmane.org/gmane.comp.gnome.apps.gnucash.devel"></ulink> and <ulink url="http://news.gmane.org/gmane.comp.gnome.apps.gnucash.user"></ulink> (and <ulink url="http://news.gmane.org/gmane.comp.gnome.apps.gnucash.german"></ulink> if you speak German).</para>
+ </sect2>
+
+ <sect2 id="appendixb_info_other">
+ <title>Q: Are there other means of obtaining support for <application>&app;</application>?</title>
+ <para>A: Yes. Many of the developers hang out on icq in the #gnucash discussion on irc.gnome.org. Also, there is a wiki online at <ulink url="http://wiki.gnucash.org/wiki/&app;">http://wiki.gnucash.org/wiki/&app;</ulink>.</para>
+ </sect2>
+ </sect1>
+
+ <sect1 id="appendixb_general">
+ <title>General Information</title>
+
+ <sect2 id="appendixb_software_windows">
+ <title>Q: Can I run <application>&app;</application> on Windows?</title>
+ <para>A: Yes. Starting with release 2.2.0, <application>&app;</application> is also available on Windows.</para>
+ <para>Other related options would be colinux, VMWare and a windows-based X-server hosting a remote <application>&app;</application> session.</para>
+ </sect2>
+
+ <sect2 id="appendixb_general_hard2compile">
+ <title>Q: I heard it is too hard to compile <application>&app;</application>!</title>
+ <para>A: This was probably true at the time when 1.6.0 was released. It is no longer true today, as almost every distribution ships with all the necessary libraries (except g-wrap, which means there is in fact <quote>one</quote> extra library to be installed before compiling <application>&app;</application>). However, by default, distributions won’t install the development packages of the required libraries, so you might need to start your distribution’s installer program and tell it to install not only the library packages but also the -devel packages. In general, it was noted that this problem concerns many applications in the gnome domain, and this also boils down to the fact that there is no such thing as <quote>one monolithic gnome package</quote>.</para>
+ </sect2>
+
+ <sect2 id="appendixb_general_batchmode">
+ <title>Q: Is there a batch mode (non-interactive) available for <application>&app;</application>, for building reports, etc?</title>
+ <para>A: No, for now <application>&app;</application> must be run interactively.</para>
+ </sect2>
+
+ <sect2 id="appendixb_general_multuser">
+ <title>Q: Can multiple people access the same datafile in <application>&app;</application>?</title>
+ <para>A: You can have multiple people with access to the same datafile, but they cannot use the data file simultaneously.</para>
+ <para>To setup multi-person access, all the people must have read/write access to the directory containing the file (to read the other’s created files, and to create new files). One way to do this is by creating a user group and setting the data directory to be owned by the shared group and set to mode 2775. The <quote>2</quote> makes the directory setgid which copies the permissions to all files.</para>
+ </sect2>
+
+ <sect2 id="appendixb_general_WhyC">
+ <title>Q: Why is <application>&app;</application> written in C?</title>
+ <para>A: The core functionality of <application>&app;</application> is written in C, but do not forget that much of this can be accessed through Guile (scheme). There are a number of reasons for why <application>&app;</application> is written in C. The first is historical, <application>&app;</application> was started in 1996 (or maybe even earlier!) and many of the OOP (C++, Java, Python) compilers were not yet mature and standarized enough on the variety of platforms considered at that time, so C was the only option at that time. A second reason is because the standard GUI <application>&app;</application> uses is GTK, which is written in C.</para>
+ </sect2>
+
+ <sect2 id="appendixb_general_rewrite">
+ <title>Q: Why don’t you rewrite <application>&app;</application> in programming language xyz so that I can contribute easily?</title>
+ <para>A: The quick answer is <quote>We won’t</quote>. The longer answer is complex but still amounts to <quote>We won’t</quote>. <application>&app;</application> is a large body of code maintained by a small group of developers who are comfortable in C and Scheme (Guile). Actually, 80% of it is in C and approx. 13% is in Scheme/Lisp. There is no valid reason that would justify rewriting this amount of existing code in a newer language. Also, creating language bindings to recent languages such as Python or Ruby or (insert your favourite language here) is labor intensive, and we’re already stretched pretty thin maintaining and developing the existing code.</para>
+ <para>Having said that, this is an open source project and you’re free to do with it or contribute what you want. Just don’t expect much support if the reason for your changes is that you’re not willing to learn C or Scheme. Also, <application>&app;</application> used to have SWIG bindings (<ulink url="http://www.swig.org"></ulink>) which have been used for some perl programming code. According to a list discussion, these SWIG bindings might still be a way to include other languages into <application>&app;</application>, but currently they are unused and unmaintained.</para>
+ </sect2>
+
+ <sect2 id="appendixb_general_newFeatures">
+ <title>Q: I really want feature XYZ but <application>&app;</application> doesn’t have it. How do I get it added?</title>
+ <para>A: Ask nicely. :-) You can file an enhancement request at <ulink url="http://bugzilla.gnome.org/enter_bug.cgi?product=&app;"></ulink>. Please bear in mind to describe your proposed enhancement as verbosely as possible. The trick here is to learn how to give the best information to the programmers about what your proposed new feature should do. If you want to speed up development significantly, consider donating some money as described on <application>&app;</application>Development.</para>
+ </sect2>
+
+ <sect2 id="appendixb_software_web">
+ <title>Q: Is there a web interface available for <application>&app;</application>?</title>
+ <para>A: No</para>
+ </sect2>
+
+ <sect2 id="appendixb_software_security">
+ <title>Q: How can I provide security for <application>&app;</application> data using CFS, etc.)</title>
+ <para>A: Unanswered</para>
+ </sect2>
+
+ <sect2 id="appendixb_software_contribute">
+ <title>Q: How can I contribute to the <application>&app;</application> project?</title>
+ <para>A: We’re working on a more formal process, but for now you should subscribe to the mailing list at <ulink url="http://lists.gnucash.org/mailman/listinfo/gnucash-user">http://lists.gnucash.org/mailman/listinfo/gnucash-user</ulink> and <ulink url="http://lists.gnucash.org/mailman/listinfo/gnucash-devel">http://lists.gnucash.org/mailman/listinfo/gnucash-devel</ulink> and discuss what you can contribute with the participants on the lists. Please be aware that <application>&app;</application> is a large body of code written in C and Scheme (see the FAQ above, <quote>Why is <application>&app;</application> written in C?</quote> if you want to know why). If these are languages that you are not willing to work with, consider contributing in other ways.</para>
+ </sect2>
+
+ <sect2 id="appendixb_software_bugs">
+ <title>Q: I think I found a bug. How do I report it?</title>
+ <para>A: First of all, try to verify that it is indeed a bug and that it has not been reported before. Search the mail list archives (see FAQ above). Then search the <ulink url="http://bugzilla.gnome.org">Gnome Bugzilla</ulink> database.</para>
+ <para>If you feel you have indeed found a bug, you can then report it at <ulink url="http://bugzilla.gnome.org/enter_bug.cgi?product=&app;"></ulink>. Please bear in mind to report your bug as verbosely as possible. The trick here is to learn how to give the best information to the programmers about how to reproduce bugs. A Programmer will usually only be able to fix a bug they can see, if you can’t make the programmer see your bug, it won’t get fixed!</para>
+ </sect2>
+
+ </sect1>
+ <sect1 id="appendixb_using">
+ <title>Using <application>&app;</application></title>
+
+ <sect2 id="appendixb_using_moveAtoB">
+ <title>Q: How can I move the transactions from account <quote>A</quote> into account <quote>B</quote>, thus combining them?</title>
+ <para>A: At present, <application>&app;</application> does not offer a way to move groups of splits from one account to another. You will need to move them one at a time. Open the register for account <quote>A</quote> and select the pulldown menu item <menuchoice><guimenu>View</guimenu><guimenuitem>Transaction Journal</guimenuitem></menuchoice> to expose all the splits. For every split where the <quote>Account</quote> field shows account <quote>A</quote> reset it to account <quote>B</quote>. To do this quickly and safely, first use <keycombo><keycap>Ctrl</keycap><keycap>C</keycap></keycombo> to copy the destination account name (<quote>account B</quote>) to the clipboard. Then highlight each reference to account <quote>A</quote> by double clicking on it and use <keycombo><keycap>Ctrl</keycap><keycap>V</keycap></keycombo> to paste the destination account name. Pressing <keycap function="enter">Enter</keycap> after each paste, silently moves the transaction out of the register.</para>
+ <para>Be careful! If you inadvertently set the <quote>Account</quote> field to an unintended location, you will need to search through all your accounts to find the lost transaction to correct your mistake.</para>
+ </sect2>
+
+ <sect2 id="appendixb_using_merge2files">
+ <title>Q: Is it possible to merge two <application>&app;</application> files?</title>
+ <para>A: At present this is not possible.</para>
+ </sect2>
+
+ <sect2 id="appendixb_using_SaveAcctTemplate">
+ <title>Q: How can I save a template of my account structure?</title>
+ <para>A: This is available from the menu: <menuchoice><guimenu>File</guimenu><guisubmenu>Export</guisubmenu><guimenuitem>Export Accounts</guimenuitem></menuchoice></para>
+ </sect2>
+ <sect2 id="appendixb_using_ListAll">
+ <title>Q: When I search for customers (or anything else for that matter), how can I return a list of everything?</title>
+ <para>A: Enter a search criteria of <guilabel>matches regex</guilabel>, and place a single dot <quote>.</quote> in the text field area. Then, click <guibutton>Find</guibutton>. The regular expression <quote>.</quote> means to match anything.</para>
+ </sect2>
+ <sect2 id="appendixb_using_Dates">
+ <title>Q: How can I record a transaction on different dates (actual date and bank date)?</title>
+ <para>A: You record the transaction on the date you write the check or initiate the transaction. When it <quote>clears</quote> the bank, you can click in the <quote>Reconciled</quote> field to <quote>clear</quote> the transaction (change the <quote>n</quote>on-reconciled to <quote>c</quote>leared).</para>
+ </sect2>
+ </sect1>
+ <sect1 id="appendixb_accounting">
+ <title>Accounting</title>
+ <sect2 id="appendixb_accounting_Taxes">
+ <title>Q: How do I treat taxes? As an account payable or as an expense?</title>
+ <para>A: This is a loaded question, and you should really talk to your accountant. How you treat taxes really depends on what kind of taxes they are, and how you WANT to treat them.. In some cases they are expenses, in some cases they are liabilities.</para>
+ </sect2>
+ </sect1>
+ -->
+ </appendix>
diff --git a/guide/de/appendixc.xml b/guide/de/appendixc.xml
new file mode 100644
index 0000000..014eaf6
--- /dev/null
+++ b/guide/de/appendixc.xml
@@ -0,0 +1,144 @@
+<!--
+ (Do not remove this comment block.)
+ Version: 2.0.0
+ Last modified: July 9th 2006
+ Maintainers:
+ Chris Lyttle <chris at wilddev.net>
+ Author:
+ Jon Lapham <lapham at extracta.com.br>
+ Originally designed by Carol Champagne.
+ Translators:
+ (translators put your name and email here)
+-->
+ <appendix id="appendixc">
+ <title>Contributed Account Trees</title>
+ <para>&untranslated;</para>
+ <!--
+ <para>
+ </para>
+ <sect1 id="appendixc_vat1">
+ <title>UK Vat</title>
+ <para>
+Account types (only shown if different to parent type)
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>[E] Expense</para>
+ </listitem>
+ <listitem>
+<para>[I] Income</para>
+ </listitem>
+ <listitem>
+<para>[A] Asset</para>
+ </listitem>
+ <listitem>
+<para>[L] Liability</para>
+ </listitem>
+ <listitem>
+<para>[Q] Equity</para>
+ </listitem>
+ <listitem>
+<para>[B] Bank accounts</para>
+ </listitem>
+ <listitem>
+<para>[C] Credit Cards</para>
+ </listitem>
+ <listitem>
+<para>[R] Accounts Receivable</para>
+ </listitem>
+ <listitem>
+<para>[P] Accounts Payable</para>
+ </listitem>
+ </itemizedlist>
+
+<para>(Box n) refers to VAT form box number (I actually have these as
+descriptions to the account to remind me)</para>
+
+<para>Add all the (Box n -part) together to get the whole (Box n)
+The VAT shows you liability - if its negative they owe you.</para>
+
+<para>Capital Equipment (Box 7 - part) and (Box 6 - part) is the value of all *additions* (purchases) made over the VAT return period - not the absolute value, nor the difference in value unless that difference is wholly due to new purchases. Depreciation, losses (e.g a write off of faulty item) and other reductions in capital value are not included. If you sell a capital item then that sale and its VAT is recorded under Income. The asset is <quote>converted to cash</quote>, so the <quote>net of VAT</quote> increase in your bank account, when the invoice is payed, is matched by a decrease in capital.</para>
+
+<literallayout>
+Bank Accounts [B]
+ |___ Main Account
+ |___ Reserve Account
+
+Cash [A]
+
+Assets [A]
+ |___ Capital Equipment (Box 7 - Part) - additions only, not absolute value
+ | |___ Computers Can be depreciated to zero this year
+ | |___ EEC reverse VAT purchase (Box 6 - Part) create sub-accounts if needed
+ |___ Other
+
+Receivable [R] Customers to whom you give credit - (business section)
+
+
+Cards [C]
+ |___ Card 1
+
+Liabilities [L]
+ |___ Owed Corp Tax
+ |___ Owed Fees
+ |___ Owed Tax / NI
+ |___ Other
+
+VAT [L] Net (Box 5)
+ |___ i/p [A] purchases (Box4)
+ |___ o/p [L] (Box3)
+ |___EEC on reverse VAT purchases (Box 2)
+ |___Sales all including zero rate UK/ EEC and World (Box1)
+
+Payable [P] Suppliers who give you credit (business section)
+
+Equity [Q]
+ |___ Corp Tax
+ |___ Director’s Loan
+ |___ Dividends
+ | |___ Director1
+ | |___ Director2
+ | |___ Shareholder 1
+ |___ Grants (and stuff that does not count as income)
+ |___Opening Balances
+
+Income [I] (Box 6 - part)
+ |___ Interest
+ |___ Misc
+ | ___ Sales
+ |___ EEC
+ | |____ goods (Box 8) (sub accounts as needed)
+ | |____ services includes software (sub accounts as needed)
+ | ___ UK
+ |____ World
+
+Expenses [E]
+ |__Depreciation
+ |__ Emoluments
+ | |___ Directors Fees
+ | |___ NI Employer
+ | |___ Employee 1
+ | |___NI
+ | |___Net Salary
+ | |___Stakeholder
+ | |___Tax
+ |___ Other Non VAT Expenses
+ |___ VAT Purchases (Box 7 - part)
+ |___ Accountancy
+ |___ Bank Charges
+ |___ Consumables
+ |___ EEC reverse VAT purchases (Box 6 - Part)
+ | |___ goods (Box 9) (sub accounts as needed)
+ | |___ services includes software (sub accounts as needed)
+ |___ Office
+ |___ Phone and Internet
+ |___ Software
+ |___ Subscriptions
+ |___ Sundry
+ |___ Travel / Accom
+
+</literallayout>
+
+ </sect1>
+ -->
+ </appendix>
diff --git a/guide/de/appendixd.xml b/guide/de/appendixd.xml
new file mode 100644
index 0000000..53247ba
--- /dev/null
+++ b/guide/de/appendixd.xml
@@ -0,0 +1,444 @@
+<!--
+ (Do not remove this comment block.)
+ Version: 2.0.0
+ Last modified: March 18th, 2007
+ Maintainers:
+ Chris Lyttle <chris at wilddev.net>
+ Author:
+ David Hampton <hampton at employees.org>
+ Translators:
+ (translators put your name and email here)
+-->
+ <appendix id="appendixd">
+ <title>Auxiliary File Formats</title>
+ <para>&untranslated;</para>
+ <!--
+ <para>These are the formats of some auxiliary files used by <application>&app;</application>.</para>
+ <sect1 id="check_format_info">
+ <title>Check Format Files (<filename>*.chk</filename>)</title>
+
+ <sect2 id="check_format_overview">
+ <title>Overview</title>
+ <para>The check format file is used to tell <application>&app;</application> how to print a check or checks onto a page of paper. This file first describes the overall layout of a page (number of checks, orientation, etc) and then describes the layout of the specific items on a single check. The file is organized as a typical Key/Value file used by many Linux applications. Keys/values pairs are grouped into sections that begin with the group name enclosed in square brackets.</para>
+ <para><application>&app;</application> looks for check format files in two different locations when you bring up the check printing dialog. The first location is typically <filename class="directory">/usr/share/gnucash/checks</filename>, where check files distributed with the application can be found. The second location is the user private <filename class="directory">~/.gnucash/checks</filename> directory. Users may add check formats at any time (even while <application>&app;</application> is running) simply by dropping a new <filename>*.chk</filename> file in this directory. The next time the check printing dialog is opened the new check format will appear in the list of available check formats.</para>
+ <note>
+ <para>Printing functions differently depending on the version of GTK that is installed on your system. When <application>&app;</application> is using a version of GTK prior to 2.10 all offsets are measured from the lower left corner of the page or check. When using GTK 2.10 or later, all offsets are measured from the upper left corner of the page or check.</para>
+ </note>
+ </sect2>
+ <sect2>
+ <title>Example file</title>
+ <para>A typical <application>&app;</application> check file is presented below. The contents of this file will be described in the next sections.</para>
+
+ <programlisting>
+[Top]
+Guid = 67b144d1-96a5-48d5-9337-0e1083bbf229
+Title = Quicken/QuickBooks (tm) US-Letter
+Rotation = 0.0
+Translation = 0.0;4.0
+Show_Grid = false
+Show_Boxes = false
+
+[Check Positions]
+Height = 252.0
+Names = Top;Middle;Bottom
+
+[Check Items]
+Type_1 = PAYEE
+Coords_1 = 90.0;102.0;400.0;20.0
+
+Type_2 = AMOUNT_WORDS
+Coords_2 = 90.0;132.0
+
+Type_3 = AMOUNT_NUMBER
+Blocking_Chars_3 = true
+Coords_3 = 500.0;102.0
+
+Type_4 = DATE
+Coords_4 = 500.0;67.0
+
+Type_5 = NOTES
+Coords_5 = 50.0;212.0
+ </programlisting>
+ </sect2>
+ <sect2>
+ <title>Field Descriptions</title>
+ <sect3>
+ <title>Top Group</title>
+ <para>This section of the check file describes the overall layout of a page of checks (or check) that goes into the printer.</para>
+ <table id="check_table_top">
+ <title>Overall Page Description Fields</title>
+ <tgroup cols="4">
+ <thead>
+ <row>
+ <entry>Name</entry>
+ <entry>Type</entry>
+ <entry>Required</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>Guid</entry>
+ <entry>string</entry>
+ <entry>mandatory</entry>
+ <entry>The guid is used to uniquely identify a check format to <application>&app;</application>. It must be unique across the entire set of application supplied and user supplied check formats. If you copy an application check file as the basis of your own check format, you must change this value. The <emphasis>uuidgen</emphasis> program may be used to generate these identifiers.</entry>
+ </row>
+ <row>
+ <entry>Title</entry>
+ <entry>string</entry>
+ <entry>mandatory</entry>
+ <entry>The title is used to uniquely identify a check format to the user. This value is presented verbatim in the check format list of the check printing dialog. If you copy an application check file as the basis of your own check format, you should change this value. The title may be any utf-8 string.</entry>
+ </row>
+ <row>
+ <entry>Font</entry>
+ <entry>string</entry>
+ <entry>optional</entry>
+ <entry>If supplied, this is the default font used to print all text items on this check. This field can contain any string that is acceptable by gtk as a font specifier. If this field is omitted, the default font is the font specified in the <application>&app;</application> preferences dialog. A typical string would be <quote>sans 12</quote>.</entry>
+ </row>
+ <row>
+ <entry>Blocking_Chars</entry>
+ <entry>boolean</entry>
+ <entry>optional</entry>
+ <entry>If supplied, this is the default used when printing all <emphasis>TEXT</emphasis> items on this check. When set to true, will print <emphasis>***</emphasis> before and after each text field on the check. Blocking characters are printed to protect check fields from alteration. For example, the amount field may be printed as <emphasis>***100.00***</emphasis></entry>
+ </row>
+ <row>
+ <entry>DateFormat</entry>
+ <entry>boolean</entry>
+ <entry>optional</entry>
+ <entry>If supplied, this is the default used when printing all <emphasis>DATE</emphasis> items on this check. When set to true, will print the format of the DATE in 8 point type, centered and below the actual DATE. For example DDMMYYYY.</entry>
+ </row>
+ <row>
+ <entry>Rotation</entry>
+ <entry>double</entry>
+ <entry>optional</entry>
+ <entry>This value specified the rotation of the entire page (in degrees) around the origin point. For gtk versions prior to 2.10, the origin point is in the lower left corner of the page and rotation values increase in the counter-clockwise direction. For gtk version 2.10 and later, the origin point is in the upper left corner of the page and rotation values increase in the clockwise direction. Rotation of the page is applied before translation.</entry>
+ </row>
+ <row>
+ <entry>Translation</entry>
+ <entry>list of 2 doubles</entry>
+ <entry>optional</entry>
+ <entry>These values specify the x and y translation of the entire page (in points) relative to the origin point. For gtk versions prior to 2.10, the origin point is in the lower left corner of the page and translation values increase moving up and to the right. For gtk version 2.10 and later, the origin point is in the upper left corner of the page and translation values increase moving down and to the right. Rotation of the page is applied before translation.</entry>
+ </row>
+ <row>
+ <entry>Show_Grid</entry>
+ <entry>boolean</entry>
+ <entry>optional</entry>
+ <entry>If this value is set to <emphasis>true</emphasis> then <application>&app;</application> will draw a grid on the page, starting at the origin with the lines spaced every 50 points. This can be helpful when creating a check format file.</entry>
+ </row>
+ <row>
+ <entry>Show_Boxes</entry>
+ <entry>boolean</entry>
+ <entry>optional</entry>
+ <entry>If this value is set to <emphasis>true</emphasis> then for each item where the width and height have been specified, <application>&app;</application> will draw a box showing location and maximum size of that item . This can be helpful when creating a check format file.</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ <note><para>The Blocking_Chars and DateFormat options are defined for all check formats in Edit->Preferences->Printing. It is recommened that these global options be set to false (the default), and that the options be set for individual Check Items as described below.</para></note>
+ </sect3>
+ <sect3>
+ <title>Check Positions Group</title>
+ <para>This group of items specifies how multiple checks are laid out on the same sheet of paper, and gives names to each of these check locations so that a user can specify which check location that <application>&app;</application> should print. This entire group of key/value pairs is optional, and should be omitted if the format file only specifies a single check per page of paper.</para>
+ <table id="check_table_positions">
+ <title>Multiple Checks Per Page Fields</title>
+ <tgroup cols="4">
+ <thead>
+ <row>
+ <entry>Name</entry>
+ <entry>Type</entry>
+ <entry>Required</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>Height</entry>
+ <entry>double</entry>
+ <entry>mandatory</entry>
+ <entry>This field specifies the height of a single check on the page. If there are multiple checks per page then this item is mandatory. If there is only a single check per page, this entire section should be omitted.</entry>
+ </row>
+ <row>
+ <entry>Names</entry>
+ <entry>list of strings</entry>
+ <entry>mandatory</entry>
+ <entry>This field specifies the names of the check locations that can be printed on each page. These names represent the check positions starting from the top of the page and moving downward. The names are presented verbatim in the check position list of the check printing dialog. A typical value for this field is "Top;Middle;Bottom", but it could also be "First;Second;Third" or any other set of strings that clearly identify the check locations. If there are multiple checks per page then this item is mandatory. If there is only a single check per page, this entire section should be omitted.</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </sect3>
+ <sect3>
+ <title>Check Items Group</title>
+ <para>This section specifies the individual items that are printed on the check. There is no limit to the number of items that may be present in this section, and any given type of item can be repeated multiple times. This allows for the printing of checks that have a side stub, or for the one-per-page business checks that have both the check and multiple check stubs on the same page. For example, to print the payee name on a business check and on both stubs, simply specify three payee items with differing print coordinates.</para>
+ <para>Each key names in this section explicitly includes the item number to which it applies. E.G. The key named <guilabel>Type_1</guilabel> applies to the first item to be printed, and the key <guilabel>Coords_3</guilabel> applies to the third item to be printed. Item numbers start at one and increase sequentially. Any gap in the numbering sequence is interpreted by <application>&app;</application> as the end of the item list. Items are printed in the order of their item numbers, not in the order in which they appear in the file.</para>
+ <para>Each item specified must include a type declaration. The rest of the parameters for that item depend upon the particular type of that item. See <xref linkend="check_table_types"></xref> for a list of valid item types and their required parameters.</para>
+ <table id="check_table_items">
+ <title>Individual Check Item Fields</title>
+ <tgroup cols="4">
+ <thead>
+ <row>
+ <entry>Name</entry>
+ <entry>Type</entry>
+ <entry>Required</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>Type_<emphasis>n</emphasis></entry>
+ <entry>string</entry>
+ <entry>mandatory</entry>
+ <entry>This field specifies the type of a single item to be printed on a check. See <xref linkend="check_table_types"></xref> for a list of valid item types.</entry>
+ </row>
+ <row>
+ <entry>Coords_<emphasis>n</emphasis></entry>
+ <entry>list of 2 or 4 doubles</entry>
+ <entry>mandatory</entry>
+ <entry>This field specifies the coordinates where the item should be placed on a check, and optionally also specifies the width and height of the item. The numbers in order are the X and Y offset of the lower left corner of the item, and optionally the width and height of the item. If the width is supplied then the height must also be supplied, so this field will always contain two or four numbers. For gtk versions prior to 2.10, the origin point is in the lower left corner of the page and translation values increase moving up and to the right. For gtk version 2.10 and later, the origin point is in the upper left corner of the page and translation values increase moving down and to the right.<note><para>Regardless of whether the origin is at the top or the bottom of the page, the coordinates always specify the lower left point of the item.</para></note></entry>
+ </row>
+ <row>
+ <entry>Font_<emphasis>n</emphasis></entry>
+ <entry>string</entry>
+ <entry>optional</entry>
+ <entry>If supplied, this is the font used to print this specific text item. This field can contain any string that is acceptable by gtk as a font specifier. If this field is omitted, the default font is the font specified in the <emphasis>Top</emphasis> section of the check description file, or if that was omitted the font specified in the <application>&app;</application> preferences dialog. This field is only recognized when using gtk version 2.10 or later.</entry>
+ </row>
+ <row>
+ <entry>Align_<emphasis>n</emphasis></entry>
+ <entry>string</entry>
+ <entry>optional</entry>
+ <entry>If supplied, this is the alignment used to print this specific text item. This field must contain one of the strings <quote>left</quote>, <quote>center</quote> or <quote>right</quote>. If this field is omitted, the text will be left aligned. This field is only recognized when using gtk version 2.10 or later.</entry>
+ </row>
+ <row>
+ <entry>Text_<emphasis>n</emphasis></entry>
+ <entry>string</entry>
+ <entry>optional</entry>
+ <entry>This field is only used when the item type is <emphasis>TEXT</emphasis>. It specifies the utf-8 text that should be printed on the check.</entry>
+ </row>
+ <row>
+ <entry>Filename_<emphasis>n</emphasis></entry>
+ <entry>string</entry>
+ <entry>optional</entry>
+ <entry>This field is only used when the item type is <emphasis>PICTURE</emphasis>. It specifies the filename of the image that should be printed on the check. The string may specify either an absolute path name or as a relative path name. If a relative path name is specified, <application>&app;</application> first looks in in the application check format folder (typically <filename class="directory">/usr/share/gnucash/checks</filename>) for the image file, and if it isn’t found there then it looks in the user private <filename class="directory">~/.gnucash/checks</filename> directory for the image. This field is only recognized when using gtk version 2.10 or later.</entry>
+ </row>
+ <row>
+ <entry>Blocking_Chars_<emphasis>n</emphasis></entry>
+ <entry>boolean</entry>
+ <entry>optional</entry>
+ <entry>If supplied, this will set the print <emphasis>Blocking_Chars</emphasis> option for this item.</entry>
+ </row>
+ <row>
+ <entry>DateFormat_<emphasis>n</emphasis></entry>
+ <entry>boolean</entry>
+ <entry>optional</entry>
+ <entry>If supplied, this will set the print <emphasis>DateFormat</emphasis> option for this item.</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ <para>These are the individual items that can be printed on a check. All items require the coordinates on the page where the item should be printed. The majority of these items result in text being printed on the page, and these items may have individual font and alignments specified. For example, the numerical amount of a check could be printed right justified while everything else is printed left justified. Other types may have unique parameters.</para>
+ <table id="check_table_types">
+ <title>Individual Check Item Types</title>
+ <tgroup cols="4">
+ <thead>
+ <row>
+ <entry>Name</entry>
+ <entry>Required Fields</entry>
+ <entry>Optional Fields</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>PAYEE</entry>
+ <entry>Coords</entry>
+ <entry>
+ <literallayout>Font
+Align
+Blocking_Chars
+ </literallayout>
+ </entry>
+ <entry>This type value tells <application>&app;</application> to print the check payee name at the specified coordinates.</entry>
+ </row>
+ <row>
+ <entry>DATE</entry>
+ <entry>Coords</entry>
+ <entry>
+ <literallayout>Font
+Align
+Blocking_Chars
+DateFormat
+ </literallayout>
+ </entry>
+ <entry>This type value tells <application>&app;</application> to print the check date at the specified coordinates.</entry>
+ </row>
+ <row>
+ <entry>NOTES</entry>
+ <entry>Coords</entry>
+ <entry>
+ <literallayout>Font
+Align
+Blocking_Chars
+ </literallayout>
+ </entry>
+ <entry>This type value tells <application>&app;</application> to print the transaction notes field at the specified coordinates.</entry>
+ </row>
+ <row>
+ <entry>CHECK_NUMBER</entry>
+ <entry>Coords</entry>
+ <entry>
+ <literallayout>Font
+Align
+Blocking_Chars
+ </literallayout>
+ </entry>
+ <entry>This type value tells <application>&app;</application>
+ to print the check number at the specified coordinates. The
+ check number reflects the book option selection under
+ <menuchoice><guimenu>File</guimenu><guimenuitem>Properties
+ </guimenuitem></menuchoice> for number source (transaction
+ number or anchor-split action - see <ulink type="help"
+ url="ghelp:gnucash-help?num-action-book-option">Use Split
+ Action Field for Number</ulink> in the Book Options section
+ of the <application>&app;</application> Help Manual).
+ </entry>
+ </row>
+ <row>
+ <entry>MEMO</entry>
+ <entry>Coords</entry>
+ <entry>
+ <literallayout>Font
+Align
+Blocking_Chars
+ </literallayout>
+ </entry>
+ <entry>This type value tells <application>&app;</application> to print the split memo field at the specified coordinates.</entry>
+ </row>
+ <row>
+ <entry>ACTION</entry>
+ <entry>Coords</entry>
+ <entry>
+ <literallayout>Font
+Align
+Blocking_Chars
+ </literallayout>
+ </entry>
+ <entry>This type value tells <application>&app;</application>
+ to print the split action field at the specified coordinates.
+ However, the printed field reflects the book option selection
+ under <menuchoice><guimenu>File</guimenu><guimenuitem>
+ Properties</guimenuitem></menuchoice> for number source
+ (transaction number or anchor-split action - see <ulink
+ type="help" url="ghelp:gnucash-help?num-action-book-option">
+ Use Split Action Field for Number</ulink> in the Book
+ Options section of the <application>&app;</application> Help
+ Manual). If number source for the book is specified as
+ anchor-split action, this field will instead print the
+ transaction number field.
+ </entry>
+ </row>
+ <row>
+ <entry>AMOUNT_WORDS</entry>
+ <entry>Coords</entry>
+ <entry>
+ <literallayout>Font
+Align
+Blocking_Chars
+ </literallayout>
+ </entry>
+ <entry>This type value tells <application>&app;</application> to print the check amount in words at the specified coordinates. The amount will appear similar to the string "One thousand, two hundred thirty four and 56/100".</entry>
+ </row>
+ <row>
+ <entry>AMOUNT_NUMBER</entry>
+ <entry>Coords</entry>
+ <entry>
+ <literallayout>Font
+Align
+Blocking_Chars
+ </literallayout>
+ </entry>
+ <entry>This type value tells <application>&app;</application> to print the check amount in numbers at the specified coordinates. The amount will appear similar to the number "$1,234.56".</entry>
+ </row>
+ <row>
+ <entry>ADDRESS</entry>
+ <entry>Coords</entry>
+ <entry>
+ <literallayout>Font
+Align
+Blocking_Chars
+ </literallayout>
+ </entry>
+ <entry>This type value tells <application>&app;</application> to print the address at the specified coordinates.</entry>
+ </row>
+ <row>
+ <entry>SPLITS_ACCOUNT</entry>
+ <entry>Coords</entry>
+ <entry>
+ <literallayout>Font
+Align
+Blocking_Chars
+ </literallayout>
+ </entry>
+ <entry>This type value tells <application>&app;</application> to print the account names for each split entry stating at the specified coordinates. See the note on splits printing.</entry>
+ </row>
+ <row>
+ <entry>SPLITS_AMOUNT</entry>
+ <entry>Coords</entry>
+ <entry>
+ <literallayout>Font
+Align
+Blocking_Chars
+ </literallayout>
+ </entry>
+ <entry>This type value tells <application>&app;</application> to print the amount for each split entry stating at the specified coordinates. Amounts are printed with currency symbols. See the note on splits printing.</entry>
+ </row>
+ <row>
+ <entry>SPLITS_MEMO</entry>
+ <entry>Coords</entry>
+ <entry>
+ <literallayout>Font
+Align
+Blocking_Chars
+ </literallayout>
+ </entry>
+ <entry>This type value tells <application>&app;</application> to print the memo text for each split entry stating at the specified coordinates. See the note on splits printing.</entry>
+ </row>
+ <row>
+ <entry>TEXT</entry>
+ <entry>Coords, Text</entry>
+ <entry>
+ <literallayout>Font
+Align
+Blocking_Chars
+ </literallayout>
+ </entry>
+ <entry>This type value tells <application>&app;</application> to print an arbitrary string at the specified coordinates. The string to be printed is specified with the <emphasis>Text_n</emphasis> key.</entry>
+ </row>
+ <row>
+ <entry>PICTURE</entry>
+ <entry>Coords, Filename</entry>
+ <entry>(none)</entry>
+ <entry>This type value tells <application>&app;</application> to print an image at the specified coordinates. The image to be printed is specified with the <emphasis>Filename_n</emphasis> key. This type is only recognized when using gtk version 2.10 or later.</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ <note>
+ <para>SPLIT items include all split entries for the transaction
+ except for the split that applies to the current account register
+ (referred to as the anchor-split). This is usually the last split
+ listed when splits are displayed in the register. The coordinate
+ location defines the lower left location for the split information.
+ </para>
+ </note>
+ </sect3>
+ </sect2>
+ <sect2 id="check_format_notes">
+ <title>Creating Check Format Files</title>
+ <para>Creating your own check format file is a fairly simple task. The easiest way to start is to copy an existing check format file from the application directory (typically <filename class="directory">/usr/share/gnucash/checks</filename>) to the directory <filename class="directory">~/.gnucash/checks</filename>. Make sure to change the guid so the new file will be accepted by gnucash, and change the title to something descriptive. Then change or add individual item fields as necessary. You can also create a new check file by clicking the <guibutton>Save Format</guibutton> button on the <guilabel>Custom format</guilabel> page of the check printing dialog.</para>
+ <note>
+ <para>Key names are case sensitive. If you’re having problems with a check format file, ensure that all key names have capital letters as documented above.</para>
+ </note>
+ </sect2>
+ </sect1>
+ -->
+ </appendix>
diff --git a/guide/de/fdl-appendix.xml b/guide/de/fdl-appendix.xml
new file mode 100644
index 0000000..c043d2c
--- /dev/null
+++ b/guide/de/fdl-appendix.xml
@@ -0,0 +1,667 @@
+<!--
+ The GNU Free Documentation License 1.1 in DocBook
+ Markup by Eric Baudais <baudais at okstate.edu>
+ Maintained by the GNOME Documentation Project
+ http://developer.gnome.org/projects/gdp
+ Version: 1.0.1
+ Last Modified: Nov 16, 2000
+-->
+
+<appendix id="fdl">
+ <appendixinfo>
+ <releaseinfo>
+ Version 1.1, March 2000
+ </releaseinfo>
+ <copyright>
+ <year>2000</year><holder>Free Software Foundation, Inc.</holder>
+ </copyright>
+ <legalnotice id="fdl-legalnotice">
+ <para>
+ <address>Free Software Foundation, Inc. <street>59 Temple Place,
+ Suite 330</street>, <city>Boston</city>, <state>MA</state>
+ <postcode>02111-1307</postcode> <country>USA</country></address>
+ Everyone is permitted to copy and distribute verbatim copies of this
+ license document, but changing it is not allowed.
+ </para>
+ </legalnotice>
+ </appendixinfo>
+ <title>GNU Free Documentation License</title>
+
+ <sect1 id="fdl-preamble">
+ <title>0. PREAMBLE</title>
+ <para>
+ The purpose of this License is to make a manual, textbook, or
+ other written document <quote>free</quote> in the sense of
+ freedom: to assure everyone the effective freedom to copy and
+ redistribute it, with or without modifying it, either
+ commercially or noncommercially. Secondarily, this License
+ preserves for the author and publisher a way to get credit for
+ their work, while not being considered responsible for
+ modifications made by others.
+ </para>
+
+ <para>
+ This License is a kind of <quote>copyleft</quote>, which means
+ that derivative works of the document must themselves be free in
+ the same sense. It complements the GNU General Public License,
+ which is a copyleft license designed for free software.
+ </para>
+
+ <para>
+ We have designed this License in order to use it for manuals for
+ free software, because free software needs free documentation: a
+ free program should come with manuals providing the same
+ freedoms that the software does. But this License is not limited
+ to software manuals; it can be used for any textual work,
+ regardless of subject matter or whether it is published as a
+ printed book. We recommend this License principally for works
+ whose purpose is instruction or reference.
+ </para>
+ </sect1>
+ <sect1 id="fdl-section1">
+ <title>1. APPLICABILITY AND DEFINITIONS</title>
+ <para id="fdl-document">
+ This License applies to any manual or other work that contains a
+ notice placed by the copyright holder saying it can be
+ distributed under the terms of this License. The
+ <quote>Document</quote>, below, refers to any such manual or
+ work. Any member of the public is a licensee, and is addressed
+ as <quote>you</quote>.
+ </para>
+
+ <para id="fdl-modified">
+ A <quote>Modified Version</quote> of the Document means any work
+ containing the Document or a portion of it, either copied
+ verbatim, or with modifications and/or translated into another
+ language.
+ </para>
+
+ <para id="fdl-secondary">
+ A <quote>Secondary Section</quote> is a named appendix or a
+ front-matter section of the <link
+ linkend="fdl-document">Document</link> that deals exclusively
+ with the relationship of the publishers or authors of the
+ Document to the Document’s overall subject (or to related
+ matters) and contains nothing that could fall directly within
+ that overall subject. (For example, if the Document is in part a
+ textbook of mathematics, a Secondary Section may not explain any
+ mathematics.) The relationship could be a matter of historical
+ connection with the subject or with related matters, or of
+ legal, commercial, philosophical, ethical or political position
+ regarding them.
+ </para>
+
+ <para id="fdl-invariant">
+ The <quote>Invariant Sections</quote> are certain <link
+ linkend="fdl-secondary"> Secondary Sections</link> whose titles
+ are designated, as being those of Invariant Sections, in the
+ notice that says that the <link
+ linkend="fdl-document">Document</link> is released under this
+ License.
+ </para>
+
+ <para id="fdl-cover-texts">
+ The <quote>Cover Texts</quote> are certain short passages of
+ text that are listed, as Front-Cover Texts or Back-Cover Texts,
+ in the notice that says that the <link
+ linkend="fdl-document">Document</link> is released under this
+ License.
+ </para>
+
+ <para id="fdl-transparent">
+ A <quote>Transparent</quote> copy of the <link
+ linkend="fdl-document"> Document</link> means a machine-readable
+ copy, represented in a format whose specification is available
+ to the general public, whose contents can be viewed and edited
+ directly and straightforwardly with generic text editors or (for
+ images composed of pixels) generic paint programs or (for
+ drawings) some widely available drawing editor, and that is
+ suitable for input to text formatters or for automatic
+ translation to a variety of formats suitable for input to text
+ formatters. A copy made in an otherwise Transparent file format
+ whose markup has been designed to thwart or discourage
+ subsequent modification by readers is not Transparent. A copy
+ that is not <quote>Transparent</quote> is called
+ <quote>Opaque</quote>.
+ </para>
+
+ <para>
+ Examples of suitable formats for Transparent copies include
+ plain ASCII without markup, Texinfo input format, LaTeX input
+ format, <acronym>SGML</acronym> or <acronym>XML</acronym> using a publicly available <acronym>DTD</acronym>, and
+ standard-conforming simple <acronym>HTML</acronym> designed for human
+ modification. Opaque formats include PostScript, PDF,
+ proprietary formats that can be read and edited only by
+ proprietary word processors, <acronym>SGML</acronym> or <acronym>XML</acronym> for which the <acronym>DTD</acronym>
+ and/or processing tools are not generally available, and the
+ machine-generated <acronym>HTML</acronym> produced by some word processors for
+ output purposes only.
+ </para>
+
+ <para id="fdl-title-page">
+ The <quote>Title Page</quote> means, for a printed book, the
+ title page itself, plus such following pages as are needed to
+ hold, legibly, the material this License requires to appear in
+ the title page. For works in formats which do not have any title
+ page as such, <quote>Title Page</quote> means the text near the
+ most prominent appearance of the work’s title, preceding the
+ beginning of the body of the text.
+ </para>
+ </sect1>
+
+ <sect1 id="fdl-section2">
+ <title>2. VERBATIM COPYING</title>
+ <para>
+ You may copy and distribute the <link
+ linkend="fdl-document">Document</link> in any medium, either
+ commercially or noncommercially, provided that this License, the
+ copyright notices, and the license notice saying this License
+ applies to the Document are reproduced in all copies, and that
+ you add no other conditions whatsoever to those of this
+ License. You may not use technical measures to obstruct or
+ control the reading or further copying of the copies you make or
+ distribute. However, you may accept compensation in exchange for
+ copies. If you distribute a large enough number of copies you
+ must also follow the conditions in <link
+ linkend="fdl-section3">section 3</link>.
+ </para>
+
+ <para>
+ You may also lend copies, under the same conditions stated
+ above, and you may publicly display copies.
+ </para>
+ </sect1>
+
+ <sect1 id="fdl-section3">
+ <title>3. COPYING IN QUANTITY</title>
+ <para>
+ If you publish printed copies of the <link
+ linkend="fdl-document">Document</link> numbering more than 100,
+ and the Document’s license notice requires <link
+ linkend="fdl-cover-texts">Cover Texts</link>, you must enclose
+ the copies in covers that carry, clearly and legibly, all these
+ Cover Texts: Front-Cover Texts on the front cover, and
+ Back-Cover Texts on the back cover. Both covers must also
+ clearly and legibly identify you as the publisher of these
+ copies. The front cover must present the full title with all
+ words of the title equally prominent and visible. You may add
+ other material on the covers in addition. Copying with changes
+ limited to the covers, as long as they preserve the title of the
+ <link linkend="fdl-document">Document</link> and satisfy these
+ conditions, can be treated as verbatim copying in other
+ respects.
+ </para>
+
+ <para>
+ If the required texts for either cover are too voluminous to fit
+ legibly, you should put the first ones listed (as many as fit
+ reasonably) on the actual cover, and continue the rest onto
+ adjacent pages.
+ </para>
+
+ <para>
+ If you publish or distribute <link
+ linkend="fdl-transparent">Opaque</link> copies of the <link
+ linkend="fdl-document">Document</link> numbering more than 100,
+ you must either include a machine-readable <link
+ linkend="fdl-transparent">Transparent</link> copy along with
+ each Opaque copy, or state in or with each Opaque copy a
+ publicly-accessible computer-network location containing a
+ complete Transparent copy of the Document, free of added
+ material, which the general network-using public has access to
+ download anonymously at no charge using public-standard network
+ protocols. If you use the latter option, you must take
+ reasonably prudent steps, when you begin distribution of Opaque
+ copies in quantity, to ensure that this Transparent copy will
+ remain thus accessible at the stated location until at least one
+ year after the last time you distribute an Opaque copy (directly
+ or through your agents or retailers) of that edition to the
+ public.
+ </para>
+
+ <para>
+ It is requested, but not required, that you contact the authors
+ of the <link linkend="fdl-document">Document</link> well before
+ redistributing any large number of copies, to give them a chance
+ to provide you with an updated version of the Document.
+ </para>
+ </sect1>
+
+ <sect1 id="fdl-section4">
+ <title>4. MODIFICATIONS</title>
+ <para>
+ You may copy and distribute a <link
+ linkend="fdl-modified">Modified Version</link> of the <link
+ linkend="fdl-document">Document</link> under the conditions of
+ sections <link linkend="fdl-section2">2</link> and <link
+ linkend="fdl-section3">3</link> above, provided that you release
+ the Modified Version under precisely this License, with the
+ Modified Version filling the role of the Document, thus
+ licensing distribution and modification of the Modified Version
+ to whoever possesses a copy of it. In addition, you must do
+ these things in the Modified Version:
+ </para>
+
+ <itemizedlist mark="opencircle">
+ <listitem>
+ <formalpara>
+ <title>A</title>
+ <para>
+ Use in the <link linkend="fdl-title-page">Title
+ Page</link> (and on the covers, if any) a title distinct
+ from that of the <link
+ linkend="fdl-document">Document</link>, and from those of
+ previous versions (which should, if there were any, be
+ listed in the History section of the Document). You may
+ use the same title as a previous version if the original
+ publisher of that version gives permission.
+ </para>
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+ <title>B</title>
+ <para>
+ List on the <link linkend="fdl-title-page">Title
+ Page</link>, as authors, one or more persons or entities
+ responsible for authorship of the modifications in the
+ <link linkend="fdl-modified">Modified Version</link>,
+ together with at least five of the principal authors of
+ the <link linkend="fdl-document">Document</link> (all of
+ its principal authors, if it has less than five).
+ </para>
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+ <title>C</title>
+ <para>
+ State on the <link linkend="fdl-title-page">Title
+ Page</link> the name of the publisher of the <link
+ linkend="fdl-modified">Modified Version</link>, as the
+ publisher.
+ </para>
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+ <title>D</title>
+ <para>
+ Preserve all the copyright notices of the <link
+ linkend="fdl-document">Document</link>.
+ </para>
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+ <title>E</title>
+ <para>
+ Add an appropriate copyright notice for your modifications
+ adjacent to the other copyright notices.
+ </para>
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+ <title>F</title>
+ <para>
+ Include, immediately after the copyright notices, a
+ license notice giving the public permission to use the
+ <link linkend="fdl-modified">Modified Version</link> under
+ the terms of this License, in the form shown in the
+ Addendum below.
+ </para>
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+ <title>G</title>
+ <para>
+ Preserve in that license notice the full lists of <link
+ linkend="fdl-invariant"> Invariant Sections</link> and
+ required <link linkend="fdl-cover-texts">Cover
+ Texts</link> given in the <link
+ linkend="fdl-document">Document’s</link> license notice.
+ </para>
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+ <title>H</title>
+ <para>
+ Include an unaltered copy of this License.
+ </para>
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+ <title>I</title>
+ <para>
+ Preserve the section entitled <quote>History</quote>, and
+ its title, and add to it an item stating at least the
+ title, year, new authors, and publisher of the <link
+ linkend="fdl-modified">Modified Version </link>as given on
+ the <link linkend="fdl-title-page">Title Page</link>. If
+ there is no section entitled <quote>History</quote> in the
+ <link linkend="fdl-document">Document</link>, create one
+ stating the title, year, authors, and publisher of the
+ Document as given on its Title Page, then add an item
+ describing the Modified Version as stated in the previous
+ sentence.
+ </para>
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+ <title>J</title>
+ <para>
+ Preserve the network location, if any, given in the <link
+ linkend="fdl-document">Document</link> for public access
+ to a <link linkend="fdl-transparent">Transparent</link>
+ copy of the Document, and likewise the network locations
+ given in the Document for previous versions it was based
+ on. These may be placed in the <quote>History</quote>
+ section. You may omit a network location for a work that
+ was published at least four years before the Document
+ itself, or if the original publisher of the version it
+ refers to gives permission.
+ </para>
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+ <title>K</title>
+ <para>
+ In any section entitled <quote>Acknowledgements</quote> or
+ <quote>Dedications</quote>, preserve the section’s title,
+ and preserve in the section all the substance and tone of
+ each of the contributor acknowledgements and/or
+ dedications given therein.
+ </para>
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+ <title>L</title>
+ <para>
+ Preserve all the <link linkend="fdl-invariant">Invariant
+ Sections</link> of the <link
+ linkend="fdl-document">Document</link>, unaltered in their
+ text and in their titles. Section numbers or the
+ equivalent are not considered part of the section titles.
+ </para>
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+ <title>M</title>
+ <para>
+ Delete any section entitled
+ <quote>Endorsements</quote>. Such a section may not be
+ included in the <link linkend="fdl-modified">Modified
+ Version</link>.
+ </para>
+ </formalpara>
+ </listitem>
+
+ <listitem>
+ <formalpara>
+ <title>N</title>
+ <para>
+ Do not retitle any existing section as
+ <quote>Endorsements</quote> or to conflict in title with
+ any <link linkend="fdl-invariant">Invariant
+ Section</link>.
+ </para>
+ </formalpara>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ If the <link linkend="fdl-modified">Modified Version</link>
+ includes new front-matter sections or appendices that qualify as
+ <link linkend="fdl-secondary">Secondary Sections</link> and
+ contain no material copied from the Document, you may at your
+ option designate some or all of these sections as invariant. To
+ do this, add their titles to the list of <link
+ linkend="fdl-invariant">Invariant Sections</link> in the
+ Modified Version’s license notice. These titles must be
+ distinct from any other section titles.
+ </para>
+
+ <para>
+ You may add a section entitled <quote>Endorsements</quote>,
+ provided it contains nothing but endorsements of your <link
+ linkend="fdl-modified">Modified Version</link> by various
+ parties--for example, statements of peer review or that the text
+ has been approved by an organization as the authoritative
+ definition of a standard.
+ </para>
+
+ <para>
+ You may add a passage of up to five words as a <link
+ linkend="fdl-cover-texts">Front-Cover Text</link>, and a passage
+ of up to 25 words as a <link
+ linkend="fdl-cover-texts">Back-Cover Text</link>, to the end of
+ the list of <link linkend="fdl-cover-texts">Cover Texts</link>
+ in the <link linkend="fdl-modified">Modified Version</link>.
+ Only one passage of Front-Cover Text and one of Back-Cover Text
+ may be added by (or through arrangements made by) any one
+ entity. If the <link linkend="fdl-document">Document</link>
+ already includes a cover text for the same cover, previously
+ added by you or by arrangement made by the same entity you are
+ acting on behalf of, you may not add another; but you may
+ replace the old one, on explicit permission from the previous
+ publisher that added the old one.
+ </para>
+
+ <para>
+ The author(s) and publisher(s) of the <link
+ linkend="fdl-document">Document</link> do not by this License
+ give permission to use their names for publicity for or to
+ assert or imply endorsement of any <link
+ linkend="fdl-modified">Modified Version </link>.
+ </para>
+ </sect1>
+
+ <sect1 id="fdl-section5">
+ <title>5. COMBINING DOCUMENTS</title>
+ <para>
+ You may combine the <link linkend="fdl-document">Document</link>
+ with other documents released under this License, under the
+ terms defined in <link linkend="fdl-section4">section 4</link>
+ above for modified versions, provided that you include in the
+ combination all of the <link linkend="fdl-invariant">Invariant
+ Sections</link> of all of the original documents, unmodified,
+ and list them all as Invariant Sections of your combined work in
+ its license notice.
+ </para>
+
+ <para>
+ The combined work need only contain one copy of this License,
+ and multiple identical <link linkend="fdl-invariant">Invariant
+ Sections</link> may be replaced with a single copy. If there are
+ multiple Invariant Sections with the same name but different
+ contents, make the title of each such section unique by adding
+ at the end of it, in parentheses, the name of the original
+ author or publisher of that section if known, or else a unique
+ number. Make the same adjustment to the section titles in the
+ list of Invariant Sections in the license notice of the combined
+ work.
+ </para>
+
+ <para>
+ In the combination, you must combine any sections entitled
+ <quote>History</quote> in the various original documents,
+ forming one section entitled <quote>History</quote>; likewise
+ combine any sections entitled <quote>Acknowledgements</quote>,
+ and any sections entitled <quote>Dedications</quote>. You must
+ delete all sections entitled <quote>Endorsements.</quote>
+ </para>
+ </sect1>
+
+ <sect1 id="fdl-section6">
+ <title>6. COLLECTIONS OF DOCUMENTS</title>
+ <para>
+ You may make a collection consisting of the <link
+ linkend="fdl-document">Document</link> and other documents
+ released under this License, and replace the individual copies
+ of this License in the various documents with a single copy that
+ is included in the collection, provided that you follow the
+ rules of this License for verbatim copying of each of the
+ documents in all other respects.
+ </para>
+
+ <para>
+ You may extract a single document from such a collection, and
+ dispbibute it individually under this License, provided you
+ insert a copy of this License into the extracted document, and
+ follow this License in all other respects regarding verbatim
+ copying of that document.
+ </para>
+ </sect1>
+
+ <sect1 id="fdl-section7">
+ <title>7. AGGREGATION WITH INDEPENDENT WORKS</title>
+ <para>
+ A compilation of the <link
+ linkend="fdl-document">Document</link> or its derivatives with
+ other separate and independent documents or works, in or on a
+ volume of a storage or distribution medium, does not as a whole
+ count as a <link linkend="fdl-modified">Modified Version</link>
+ of the Document, provided no compilation copyright is claimed
+ for the compilation. Such a compilation is called an
+ <quote>aggregate</quote>, and this License does not apply to the
+ other self-contained works thus compiled with the Document , on
+ account of their being thus compiled, if they are not themselves
+ derivative works of the Document. If the <link
+ linkend="fdl-cover-texts">Cover Text</link> requirement of <link
+ linkend="fdl-section3">section 3</link> is applicable to these
+ copies of the Document, then if the Document is less than one
+ quarter of the entire aggregate, the Document’s Cover Texts may
+ be placed on covers that surround only the Document within the
+ aggregate. Otherwise they must appear on covers around the whole
+ aggregate.
+ </para>
+ </sect1>
+
+ <sect1 id="fdl-section8">
+ <title>8. TRANSLATION</title>
+ <para>
+ Translation is considered a kind of modification, so you may
+ distribute translations of the <link
+ linkend="fdl-document">Document</link> under the terms of <link
+ linkend="fdl-section4">section 4</link>. Replacing <link
+ linkend="fdl-invariant"> Invariant Sections</link> with
+ translations requires special permission from their copyright
+ holders, but you may include translations of some or all
+ Invariant Sections in addition to the original versions of these
+ Invariant Sections. You may include a translation of this
+ License provided that you also include the original English
+ version of this License. In case of a disagreement between the
+ translation and the original English version of this License,
+ the original English version will prevail.
+ </para>
+ </sect1>
+
+ <sect1 id="fdl-section9">
+ <title>9. TERMINATION</title>
+ <para>
+ You may not copy, modify, sublicense, or distribute the <link
+ linkend="fdl-document">Document</link> except as expressly
+ provided for under this License. Any other attempt to copy,
+ modify, sublicense or distribute the Document is void, and will
+ automatically terminate your rights under this License. However,
+ parties who have received copies, or rights, from you under this
+ License will not have their licenses terminated so long as such
+ parties remain in full compliance.
+ </para>
+ </sect1>
+
+ <sect1 id="fdl-section10">
+ <title>10. FUTURE REVISIONS OF THIS LICENSE</title>
+ <para>
+ The <ulink type="http"
+ url="http://www.gnu.org/fsf/fsf.html">Free Software
+ Foundation</ulink> may publish new, revised versions of the GNU
+ Free Documentation 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. See <ulink
+ type="http"
+ url="http://www.gnu.org/copyleft">http://www.gnu.org/copyleft/</ulink>.
+ </para>
+
+ <para>
+ Each version of the License is given a distinguishing version
+ number. If the <link linkend="fdl-document">Document</link>
+ specifies that a particular numbered version of this License
+ <quote>or any later version</quote> applies to it, you have the
+ option of following the terms and conditions either of that
+ specified version or of any later version that has been
+ published (not as a draft) by the Free Software Foundation. If
+ the Document does not specify a version number of this License,
+ you may choose any version ever published (not as a draft) by
+ the Free Software Foundation.
+ </para>
+ </sect1>
+
+ <sect1 id="fdl-using">
+ <title>Addendum</title>
+ <para>
+ To use this License in a document you have written, include a copy of
+ the License in the document and put the following copyright and
+ license notices just after the title page:
+ </para>
+
+ <blockquote>
+ <para>
+ Copyright YEAR YOUR NAME.
+ </para>
+ <para>
+ Permission is granted to copy, distribute and/or modify this
+ document under the terms of the GNU Free Documentation
+ License, Version 1.1 or any later version published by the
+ Free Software Foundation; with the <link
+ linkend="fdl-invariant">Invariant Sections</link> being LIST
+ THEIR TITLES, with the <link
+ linkend="fdl-cover-texts">Front-Cover Texts</link> being LIST,
+ and with the <link linkend="fdl-cover-texts">Back-Cover
+ Texts</link> being LIST. A copy of the license is included in
+ the section entitled <quote>GNU Free Documentation
+ License</quote>.
+ </para>
+ </blockquote>
+
+ <para>
+ If you have no <link linkend="fdl-invariant">Invariant
+ Sections</link>, write <quote>with no Invariant Sections</quote>
+ instead of saying which ones are invariant. If you have no
+ <link linkend="fdl-cover-texts">Front-Cover Texts</link>, write
+ <quote>no Front-Cover Texts</quote> instead of
+ <quote>Front-Cover Texts being LIST</quote>; likewise for <link
+ linkend="fdl-cover-texts">Back-Cover Texts</link>.
+ </para>
+
+ <para>
+ If your document contains nontrivial examples of program code,
+ we recommend releasing these examples in parallel under your
+ choice of free software license, such as the <ulink type="http"
+ url="http://www.gnu.org/copyleft/gpl.html"> GNU General Public
+ License</ulink>, to permit their use in free software.
+ </para>
+ </sect1>
+</appendix>
+
+
diff --git a/guide/de/gnucash-guide.xml b/guide/de/gnucash-guide.xml
index 21771cc..46d2cae 100644
--- a/guide/de/gnucash-guide.xml
+++ b/guide/de/gnucash-guide.xml
@@ -29,16 +29,13 @@
<!ENTITY chapter18 SYSTEM "ch_dep.xml">
<!ENTITY chapter19 SYSTEM "ch_python_bindings.xml">
<!ENTITY chapter20 SYSTEM "ch_import_business_data.xml">
-<!--
<!ENTITY appendixa SYSTEM "appendixa.xml">
<!ENTITY appendixb SYSTEM "appendixb.xml">
<!ENTITY appendixc SYSTEM "appendixc.xml">
<!ENTITY appendixd SYSTEM "appendixd.xml">
-<!ENTITY legal SYSTEM "legal.xml">
+<!ENTITY appendixe SYSTEM "appendixe.xml">
<!ENTITY GFDL SYSTEM "fdl-appendix.xml">
--->
<!ENTITY glossary SYSTEM "glossary.xml">
-<!ENTITY appendixe SYSTEM "appendixe.xml">
<!--
Some global declarations which are used in the files. For easier
@@ -532,16 +529,16 @@
<title>Berichte</title>
&chapter20;
</part>
+-->
<part>
<title>Anhänge</title>
&appendixa;
&appendixb;
&appendixc;
&appendixd;
-
+&appendixe;
&GFDL;
--->
&glossary;
-&appendixe;
+
</part>
</book>
commit 090460887983b265085ac9fc52a459d8ec86cfc5
Author: Mechtilde <ooo at mechtilde.de>
Date: Wed Dec 30 14:54:25 2015 +0100
add inforamtion about chapter import_business_data
diff --git a/guide/de/Makefile.am b/guide/de/Makefile.am
index 56135be..a1891a6 100644
--- a/guide/de/Makefile.am
+++ b/guide/de/Makefile.am
@@ -15,6 +15,7 @@ entities = \
ch_cbook.xml \
ch_cc.xml \
ch_currency.xml \
+ ch_import_business_data.xml \
ch_loans.xml \
ch_invest.xml \
ch_oth_assets.xml \
diff --git a/guide/de/ch_import_business_data.xml b/guide/de/ch_import_business_data.xml
new file mode 100644
index 0000000..48d3e4c
--- /dev/null
+++ b/guide/de/ch_import_business_data.xml
@@ -0,0 +1,348 @@
+<!-- (Do not remove this comment block.)
+
+Version: 2.4.0
+Last modified: 2013-11-21
+
+Maintainers:
+
+Author:
+ Mike Evans <mikee at saxicola.co.uk>
+
+ Translators:
+ (translators put your name and email here)
+-->
+
+<chapter id="ch_import_bus_data">
+ <title>Importing Business Data</title>
+ <para>&untranslated;</para>
+ <!--
+
+ <sect1 id="import-invoices">
+ <title>Import Bills or Invoices</title>
+ <para>This functionality is only available by default for versions greater than 2.6</para>
+ <para>For 2.4.13 the Customers and Vendors importer is an optional module and needs to enabled by editing the file <filename>$HOME/.gnucash/config.user</filename>,
+ adding the line:</para>
+ <para><code>(gnc:module-load "gnucash/plugins/bi_import" 0)</code></para>
+ <para>On Linux systems this file is found at <filename>$HOME/.gnucash/config.user</filename>
+ and on Mac OSX it is <filename>~/Library/Application Support/Gnucash/config.user</filename>.
+ If the file doesn’t already exist you will have to create it.
+ After restarting <application>&app;</application>, the item will appear at the bottom
+ of the business menu.</para>
+
+
+ <para>In order for the importer to work the data must be in a fixed field
+ length, comma separated line format. A example <application>Python</application> script to convert
+ a downloaded order is shown below.
+ </para>
+
+ <para>
+ <programlisting language="python" linenumbering="unnumbered">
+import sys
+import csv
+
+VENDOR_ID="000013"
+INFILE=sys.argv[1]
+INV_ID=sys.argv[2]
+try:
+ ACCOUNT=sys.argv[3]
+except:
+ ACCOUNT="Expenses:Materials General"
+
+Reader = csv.reader(open(INFILE), delimiter=',')
+
+# Need to ignore 1st and last rows
+
+for row in Reader:
+ if row[0].isdigit(): # We only use numbered lines
+ outline=(INV_ID + ",," + VENDOR_ID + ",,,," + row[1] + " > " + row[4] + ",ea," +
+ ACCOUNT + "," + row[2] + "," + row[5].replace("GBP", "") + ",,,,no,,,,,,,")
+ print outline
+ </programlisting>
+ </para>
+
+ <para>Example of a downloaded vendor order from <emphasis>Rapid Electronics</emphasis> (UK).
+ <programlisting language="python" linenumbering="unnumbered">
+line number,product code,quantity,availability,product description,unit price,discounts,line total,delivery,sub total,vat,grand total
+1,47-3524,100,100 Available,BC848C SOT-23 NPN TRANSISTOR (INF) (RC),GBP0.03,GBP0.00,GBP0.03
+2,47-3278,30,30 Available,L78L05ACZ 0.1A +5V VOLTAGE REG (ST) (RC),GBP0.18,GBP0.00,GBP0.18
+3,22-0120,1,1 Available,Tube 34 14pin DIL socket, narrow7.62mm, without central support,GBP1.05,GBP0.00,GBP1.05
+4,22-0127,1,0 Available<br />1 on Back Order,Tube 17 28pin DIL socket, wide15.24mm, without central support,GBP1.22,GBP0.00,GBP1.22
+5,62-0368,1,1 Available,820R CR25 0.25W CF Resistor Pk 100,GBP0.50,GBP0.00,GBP0.50
+6,47-3130,100,100 Available,1N4001 1A 50V SILICON RECTIFIER DIODE RC,GBP0.01,GBP0.00,GBP0.01
+7,17-0310,1,1 Available,PROFESSIONAL MINATURE PROBE HOOK RED RC,GBP0.90,GBP0.00,GBP0.90
+8,17-0312,1,1 Available,PROFESSIONAL MINATURE PROBE HOOK BLACKRC,GBP0.90,GBP0.00,GBP0.90
+9,34-0655,1,1 Available,PROTOBLOC 2 BREADBOARD,GBP4.39,GBP0.00,GBP4.39
+10,18-0200,1,1 Available,PP3 9V ALKALINE BATTERY "Not For Retail Sale",GBP1.37,GBP0.00,GBP1.37
+,,,,,,,,GBP4.95,GBP24.93,GBP4.35,GBP29.28
+ </programlisting>
+ </para>
+
+ <para>A similar file after processing with the <application>Python</application> script.</para>
+
+ <para>
+ <programlisting language="python">
+MEC-0071,,000013,,,,34-0655 > PROTOBLOC 2 BREADBOARD,ea,Expenses:Materials General,1,4.39,,,,no,,,,,,,
+MEC-0071,,000013,,,,18-0105 > PP3 / PP6 BATTERY CLIP 150MM (RC),ea,Expenses:Materials General,10,0.06,,,,no,,,,,,,
+MEC-0071,,000013,,,,62-0370 > 1k CR25 0.25W CF Resistor Pk 100,ea,Expenses:Materials General,1,0.50,,,,no,,,,,,,
+MEC-0071,,000013,,,,62-0354 > 220R CR25 0.25W CF Resistor Pk 100,ea,Expenses:Materials General,1,0.50,,,,no,,,,,,,
+MEC-0071,,000013,,,,34-5548 > PLAIN DOCUMENT WALLET ASSORTED PK 50 RE,ea,Expenses:Materials General,1,6.95,,,,no,,,,,,,
+MEC-0071,,000013,,,,62-0386 > 4k7 CR25 0.25W CF Resistor Pk 100,ea,Expenses:Materials General,1,0.50,,,,no,,,,,,,
+MEC-0071,,000013,,,,34-0860 > COPPER CLAD SRBP SS 100 X 160 (RC),ea,Expenses:Materials General,5,0.50,,,,no,,,,,,,
+MEC-0071,,000013,,,,18-0163 > PP3 BATTERY HOLDER WITH FLYING LEADS RC,ea,Expenses:Materials General,5,0.23,,,,no,,,,,,,
+MEC-0071,,000013,,,,73-4290 > ATMEGA8-16PU 8-BIT MICRO 8K DIL-28 (RC),ea,Expenses:Materials General,3,1.99,,,,no,,,,,,,
+MEC-0071,,000013,,,,81-0014 > BC108 NPN GP TRANSISTOR RC,ea,Expenses:Materials General,20,0.16,,,,no,,,,,,,
+MEC-0071,,000013,,,,DELIVERY,ea,Expenses:Postage,1,4.95,,,,no,,,,,,,
+MEC-0071,,000013,,,,VAT,tax,Expenses:VAT,1,4.35,,,,no,,,,,,,
+ </programlisting>
+ </para>
+
+ <para>
+ As can be seen there are some fields that are absent and some that
+ are not required for import. The first line is not required and the last
+ line is superfluous as <application>&app;</application> will total the order for us. All that is
+ required is to take what we want and produce an output file with the
+ correct format to import into <application>&app;</application>. In this case we join the part
+ number and description fields and these become description in <application>&app;</application>
+ invoice/bill. We need the qty and part price fields. Contrary to the
+ header line <acronym>VAT</acronym> is not included by line and is always zero, the <acronym>VAT</acronym> is
+ calculated on the last line as <acronym>VAT</acronym> on the order total.
+ <note>
+ <para>This will cause problems later.</para>
+ </note>
+ In this example I have assigned the
+ <emphasis>Expenses:Materials General</emphasis> account to be the target account. This can be
+ changed after import in the usual way, along with any other data. If there
+ is no such account as <emphasis>Expenses:Materials General</emphasis> then that field will be
+ left blank on import and will have to be set manually. Lines beginning
+ with a <quote>#</quote> are regarded as comment lines and ignored.
+ </para>
+
+ <para>The script is called with the following command:</para>
+ <para> <command>python importer.py <replaceable>file_to_import</replaceable>,
+ <replaceable>invoice_id</replaceable> > <replaceable>file_to_save_as.csv</replaceable></command>
+ </para>
+ <para>This short script can easily be
+ changed to suit any downloaded format. The only restriction is that the
+ final number of field is fixed, at least at the moment. The importer will
+ ignore lines with the wrong number of fields. (This may be fixed in future
+ version). Vendor ID is simply the ID assigned to the specific vendor, or
+ client. The row[N] items refer to the position in the line where the
+ correct data lies. Note that the first field is row[0] NOT row[1].
+ </para>
+
+ <para>Once you have converted the file navigate to <menuchoice><guimenu>Business</guimenu>
+ <guimenuitem>Invoice & Bill Import</guimenuitem></menuchoice> to open a new import window.
+ Select the file you have just created, select <guilabel>Bill</guilabel>
+ or <guilabel>Invoice</guilabel> and <guilabel>Comma separated</guilabel> format. At this
+ point the data should show up in the preview window. Check that the field
+ data are in the correct columns before selecting <guibutton>OK</guibutton>. Once imported the
+ invoice can be opened for editing and posting in the usual way.
+ </para>
+
+ <para>A note on <acronym>VAT</acronym>, or any purchase tax. As previously mentioned <emphasis>Rapid
+ Electronics</emphasis> calculate the <acronym>VAT</acronym> on the bill total not line by line. <application>&app;</application>
+ calculated the <acronym>VAT</acronym> per line then totals the <acronym>VAT</acronym>. This can lead to
+ inaccuracies in the <acronym>VAT</acronym> of the region of a few pennies and is enough to
+ cause problems when reconciling the purchase with your bank or credit card
+ account used to make the purchase. As to how you overcome that, for the
+ moment, is a problem for you to use whatever method suits your conscience
+ or accountant best. Personally I add the <acronym>VAT</acronym> as a separate line along with
+ delivery charges manually. So some work is left to the user but the tedium
+ of entering each item eliminated.
+ </para>
+
+ <para>Future: Currently the import format is quite strict and many users
+ may have problems with the conversion process. Adding a template for every
+ possible vendor <acronym>CSV</acronym> format would be mammoth and likely impossible task
+ notwithstanding the fact the vendors are likely to change the format
+ without informing the <application>&app;</application> team. Future import enhancements will be
+ based on user feedback and hopefully the process can be made simpler or
+ more flexible. Note that often <quote>simple</quote> is incompatible with
+ <quote>flexible</quote>.
+ </para>
+
+ <note>
+ <para>If <application>Python</application> (other languages are avaialble) is not your thing then
+ post a request to <ulink url="https://lists.gnucash.org/mailman/listinfo/gnucash-user"><citetitle>&app; user list</citetitle></ulink>,
+ with an example of your downloaded <acronym>CSV</acronym>, and someone may write you a <application>Python</application> script to do the
+ translation.
+ </para>
+ </note>
+
+ <sect2 id="python-author-notes">
+ <title>Notes for <application>Python</application> authors</title>
+
+ <para>In order for the import to succeed the number of fields must be
+ adhered to, so the trailing commas are important.
+ </para>
+
+ <para>A complete list of the required fields is:</para>
+
+ <para>id, date_opened, owner_id, billingid, notes, date, desc, action,
+ account, quantity, price, disc_type, disc_how, discount, taxable,
+ taxincluded, tax_table, date_posted, due_date, account_posted,
+ memo_posted, accu_splits,
+ </para>
+ <note>
+ <para>Mind the trailing comma.</para>
+ </note>
+ </sect2>
+
+ <sect2 id="python-import-fields">
+ <title>A brief description of each field</title>
+
+ <itemizedlist>
+ <listitem>
+ <para><emphasis>id</emphasis> -
+ The invoice number. All lines must
+ contain this or the line will be rejected.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>date_opened</emphasis> -
+ Use the same date format as setup in Preferences. Today's date is inserted if this is blank.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>owner_id</emphasis> -
+ ID number of the vendor or customer. All lines must
+ contain this or the line will be rejected.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>billingid</emphasis> -
+ Billing ID.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>notes</emphasis> -
+ Invoice notes.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>date</emphasis> -
+ The date of the item line. Can be left blank for todays
+ date.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>desc</emphasis> -
+ Description as per normal invoice or bill.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>action</emphasis> -
+ For bills usually <quote>ea</quote>.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>account</emphasis> -
+ Account to which the item is attributed.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>quantity</emphasis> -
+ Quantity of each item. Must contain a value or the line
+ will be rejected.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>price</emphasis> -
+ Price of each item. Must contain a value or the line will be
+ rejected.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>disc_type</emphasis> -
+ Type of discount, either <quote>%</quote> or <quote>TODO</quote>, only applies to
+ invoices. Some experimentation may be required here as may be currency
+ dependent.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>disc_how</emphasis> -
+ Only applies to invoices.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>discount</emphasis> -
+ Amount of discount to be applied. only applies to
+ invoices.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>taxable</emphasis> -
+ Will tax be applied to the item? <quote>yes</quote> or blank.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>taxincluded</emphasis> -
+ Is tax included in the item price? <quote>yes</quote> or blank.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>tax_table</emphasis> -
+ Tax table to apply to item.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>date_posted</emphasis> -
+ If posted, what date. Normally left blank for manual
+ posting after editing the invoice. Use the same date format as setup in Preferences.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>due_date</emphasis> -
+ Date payment is due. Use the same date format as setup in Preferences.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>account_posted</emphasis> -
+ Posted to what account.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>memo_posted </emphasis> -
+ If posted insert memo here.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>accu_splits</emphasis> -
+ Accumulate splits? <quote>yes</quote> or blank.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </sect2>
+
+ </sect1>
+
+<sect1 id="import-customers-vendors">
+ <title>Importing Customers and Vendors</title>
+ <para>This functionality is only available in the 2.6 versions of GnuCash and is only loaded by default for versions greater than 2.6.</para>
+ <para>For versions lower than 2.6 the Customers and Vendors importer is an optional module and needs to
+ enabled by editing the file <filename>$HOME/.gnucash/config.user</filename>,
+ adding the line:</para>
+ <para><code>(gnc:module-load "gnucash/plugins/customer_import" 0)
+ </code></para>
+ <para>On Linux systems this file is found at <filename>$HOME/.gnucash/config.user</filename>
+ and on Mac OSX it is <filename>~/Library/Application Support/Gnucash/config.user</filename>.
+ If the file doesn’t already exist you will have to create it.
+ After restarting <application>&app;</application> the item will appear at the bottom
+ of the business menu.</para>
+ <para>In order for the importer to work each line in the input file must have the following structure.
+ </para>
+ <para><code>
+ id, company, name, addr1, addr2, addr3, addr4, phone, fax, email, notes, shipname, shipaddr1, shipaddr2, shipaddr3, shipaddr4, shiphone, shipfax, shipmail
+ </code> </para>
+
+ <para>
+ Fields can be separated with commas or semicolons and each field can be in quotes. These options are selectable in the import dialog. Vendors don’t have shipping information so even though the fields have to exist, leave them empty.
+ The id field is optional and if it is empty a new id will be chosen. If the id field has a value this will UPDATE any vendor/customer with the same id. This may not be what you want. Note that in your input file the data must be a single line for each customer/vendor.
+ </para>
+ <para>
+ The importer does not currently import billing information for customers or vendors, these will have to be edited individually after importing.
+ </para>
+ </sect1>
+-->
+
+</chapter>
diff --git a/guide/de/gnucash-guide.xml b/guide/de/gnucash-guide.xml
index 795d232..21771cc 100644
--- a/guide/de/gnucash-guide.xml
+++ b/guide/de/gnucash-guide.xml
@@ -28,8 +28,8 @@
<!ENTITY chapter17 SYSTEM "ch_oth_assets.xml">
<!ENTITY chapter18 SYSTEM "ch_dep.xml">
<!ENTITY chapter19 SYSTEM "ch_python_bindings.xml">
-<!--
<!ENTITY chapter20 SYSTEM "ch_import_business_data.xml">
+<!--
<!ENTITY appendixa SYSTEM "appendixa.xml">
<!ENTITY appendixb SYSTEM "appendixb.xml">
<!ENTITY appendixc SYSTEM "appendixc.xml">
@@ -525,9 +525,9 @@
&chapter17;
&chapter18;
&chapter19;
-<!--
&chapter20;
</part>
+<!--
<part>
<title>Berichte</title>
&chapter20;
commit c4361a3792f2616cd1f154733e671a5773c35f5f
Author: Mechtilde <ooo at mechtilde.de>
Date: Wed Dec 30 14:49:24 2015 +0100
add inforamtion about chapter python_bindings
diff --git a/guide/de/Makefile.am b/guide/de/Makefile.am
index 4e0b245..56135be 100644
--- a/guide/de/Makefile.am
+++ b/guide/de/Makefile.am
@@ -19,6 +19,7 @@ entities = \
ch_invest.xml \
ch_oth_assets.xml \
ch_oview.xml \
+ ch_python_bindings.xml \
ch_txns.xml \
appendixe.xml \
glossary.xml
diff --git a/guide/de/ch_python_bindings.xml b/guide/de/ch_python_bindings.xml
new file mode 100644
index 0000000..3442fae
--- /dev/null
+++ b/guide/de/ch_python_bindings.xml
@@ -0,0 +1,55 @@
+<!-- (Do not remove this comment block.)
+
+Version: 2.4.0
+Last modified: 2011-01-01
+
+Maintainers:
+
+Author:
+ Mike Evans <mikee at saxicola.co.uk>
+
+ Translators:
+ (translators put your name and email here)
+-->
+
+<chapter id="ch_python_bindings">
+ <title>Python Bindings</title>
+ <para>&untranslated;</para>
+ <!--
+ <para>
+ <application>&app;</application> historically has always been a
+ traditional application in the sense that you open it, use it to
+ manipulate your financial data via the windows it presents, save your
+ data and close the windows again. This has the inherent limitation that
+ you can only do whatever the windows, menus and toolbars allow you to do.
+ </para>
+ <para>
+ Sometimes you might need a little more flexibility. For example, you
+ need a report with just a little different information than what the
+ built-in reports provide, or you want to automate a frequently recurring
+ action. Such custom manipulations are ideal candidates to write in one
+ or the other scripting language.
+ </para>
+ <para>
+ Starting with <application>&app;</application> version 2.4 you can
+ write <application>Python</application> scripts to manipulate your financial data.
+ </para>
+ <note>
+ <para>The <application>Python</application> extensions are an optional feature in the source code.
+ To be able to use <application>Python</application> scripts, <application>&app;</application> must
+ have been compiled with this option enabled, otherwise all what follows
+ won’t work. At present this option is not enabled by default, so if you
+ need this, you may have to compile <application>&app;</application> from
+ source yourself.
+ </para>
+ </note>
+ <para>The <application>Python</application> extensions come with a couple of ready to use scripts. This
+ chapter will show you how to use some of these.
+ </para>
+ <note>
+ <para>This chapter is not about how to write your own <application>Python</application> scripts.
+ Refer to the developer documentation for that instead.
+ </para>
+ </note>
+ -->
+</chapter>
diff --git a/guide/de/gnucash-guide.xml b/guide/de/gnucash-guide.xml
index 81aa0d1..795d232 100644
--- a/guide/de/gnucash-guide.xml
+++ b/guide/de/gnucash-guide.xml
@@ -27,8 +27,8 @@
<!ENTITY chapter16 SYSTEM "ch_budgets.xml">
<!ENTITY chapter17 SYSTEM "ch_oth_assets.xml">
<!ENTITY chapter18 SYSTEM "ch_dep.xml">
-<!--
<!ENTITY chapter19 SYSTEM "ch_python_bindings.xml">
+<!--
<!ENTITY chapter20 SYSTEM "ch_import_business_data.xml">
<!ENTITY appendixa SYSTEM "appendixa.xml">
<!ENTITY appendixb SYSTEM "appendixb.xml">
@@ -524,8 +524,8 @@
&chapter16;
&chapter17;
&chapter18;
-<!--
&chapter19;
+<!--
&chapter20;
</part>
<part>
commit 1d0d4e9ce20370201d82fc77726297b054569bb3
Author: Mechtilde <ooo at mechtilde.de>
Date: Wed Dec 30 14:41:51 2015 +0100
add inforamtion about chapter oth_assets and dep
diff --git a/guide/de/Makefile.am b/guide/de/Makefile.am
index a0bfb19..4e0b245 100644
--- a/guide/de/Makefile.am
+++ b/guide/de/Makefile.am
@@ -5,6 +5,7 @@ omffile = $(docname)-de.omf
entities = \
ch_accts.xml \
ch_basics.xml \
+ ch_budgets.xml \
ch_bus_ap.xml \
ch_bus_ar.xml \
ch_bus_intro.xml \
diff --git a/guide/de/ch_dep.xml b/guide/de/ch_dep.xml
new file mode 100644
index 0000000..ac94151
--- /dev/null
+++ b/guide/de/ch_dep.xml
@@ -0,0 +1,601 @@
+<!--
+ (Do not remove this comment block.)
+ Version: 2.0.0
+ Last modified: July 9th 2006
+ Maintainers:
+ Chris Lyttle <chris at wilddev.net>
+ Author:
+ Jon Lapham <lapham at extracta.com.br>
+ Updated Bengt Thuree <bengt at thuree.com>
+ Originally designed by Carol Champagne.
+ Translators:
+ (translators put your name and email here)
+-->
+<chapter id="chapter_dep">
+ <title>Depreciation</title>
+ <para>&untranslated;</para>
+ <!--
+ <para>This chapter will introduce the concept of depreciation in accounting
+ and give some real life examples for using it.</para>
+
+ <sect1 id="dep_concepts1">
+ <title>Basic Concepts</title>
+
+ <para>Depreciation is the accounting method for expensing capital
+ purchases over time. There are two reasons that you may want to record
+ depreciation; you are doing bookkeeping for your own personal finances and
+ would like to keep track of your net worth, or you are doing bookkeeping
+ for a small busines and need to produce a financial statement from which
+ you will prepare your tax return.</para>
+
+ <para>The method of recording depreciation is the same in either case. but
+ the end goal is different. This section will discuss the differences
+ between the two. But first, some terminology.</para>
+
+ <itemizedlist>
+ <listitem>
+ <para><emphasis>Accumulated depreciation</emphasis> - the accumulated
+ total of book depreciation taken over the life of the asset. This is
+ accumulated in the depreciation account in the asset section.</para>
+ </listitem>
+
+ <listitem>
+ <para><emphasis>Book depreciation</emphasis> - this is the amount of
+ depreciation that you record in your financial statements per
+ accounting period.</para>
+ </listitem>
+
+ <listitem>
+ <para><emphasis>Fair market value</emphasis> - the amount for which an
+ asset could be sold at a given time.</para>
+ </listitem>
+
+ <listitem>
+ <para><emphasis>Net book value</emphasis> - this is the difference
+ between the original cost and the depreciation taken to date.</para>
+ </listitem>
+
+ <listitem>
+ <para><emphasis>Original cost</emphasis> - this is the amount that the
+ asset cost you to purchase. It includes any cost to get the asset into
+ a condition in which you can use it. For example - shipping,
+ installation costs, special training.</para>
+ </listitem>
+
+ <listitem>
+ <para><emphasis>Salvage value</emphasis> - this is the value that you
+ estimate the asset can be sold for at the end of it’s useful life (to
+ you).</para>
+ </listitem>
+
+ <listitem>
+ <para><emphasis>Tax depreciation</emphasis> - this is the amount of
+ depreciation that you take for income tax purposes.</para>
+ </listitem>
+ </itemizedlist>
+
+ <sect2 id="dep_concepts_personal2">
+ <title>Personal Finances</title>
+
+ <para>Depreciation is used in personal finances to periodically lower an
+ asset’s value to give you an accurate estimation of your current net
+ worth. For example, if you owned a car you could keep track of its
+ current value by recording depreciation every year. To accomplish this,
+ you record the original purchase as an asset, and then record a
+ depreciation expense each year (See <xref linkend="dep_example1" /> for
+ an example). This would result in the net book value being approximately
+ equal to the fair market value of the asset at the end of the
+ year.</para>
+
+ <para>Depreciation for personal finance has no tax implications, it is
+ simply used to help you estimate your net worth. Because of this, there
+ are no rules for how you estimate depreciation, use your best
+ judgement.</para>
+
+ <para>For which assets should you estimate depreciation? Since the idea
+ of depreciation for personal finances is to give you an estimate of your
+ personal net worth, you need only track depreciation on assets of
+ notable worth that you could potentially sell, such as a car or
+ boat.</para>
+ </sect2>
+
+ <sect2 id="dep_concepts_business2">
+ <title>Business</title>
+
+ <para>As opposed to personal finance where the goal is tracking personal
+ worth, business is concerned with matching the expense of purchasing
+ capital assets with the revenue generated by them. This is done through
+ book depreciation. Businesses must also be concerned with local tax laws
+ covering depreciation of assets. This is known as tax depreciation. The
+ business is free to choose whatever scheme it wants to record book
+ depreciation, but the scheme used for tax depreciation is fixed. More
+ often than not this results in differences between book and tax
+ depreciation, but steps can be taken to reduce these differences.</para>
+
+ <para>Now, what purchases should be capitalized? If you expect something
+ that you purchase to help you earn income for more than just the current
+ year, then it should be capitalized. This includes things like land,
+ buildings, equipment, automobiles, and computers - as long as they are
+ used for business purposes. It does not include items that would be
+ considered inventory. So if you made a purchase with the intent to
+ resell the item, it should not be capitalized.</para>
+
+ <para>In addition to the purchase of the asset itself, any costs
+ associated with getting the asset into a condition so that you can use
+ it should be capitalized. For example, if you buy a piece of equipment
+ and it needs to be shipped from out of town, and then some electrical
+ work needs to be done so you can plug the machine in, and some
+ specialized training is needed so you know how to use the machine, all
+ these costs would be included in the cost of the equipment.</para>
+
+ <para>You also need to know the estimated salvage value of the asset.
+ Generally, this is assumed to be zero. The idea behind knowing the
+ salvage value is that the asset will be depreciated untill the net book
+ value (cost less depreciation) equals the salvage value. Then, when the
+ asset is written off, you will not have a gain or loss resulting from
+ the disposal of the asset.</para>
+
+ <para>The last step is to determine the method of depreciation that you
+ want to use. This will be discussed on the next few pages.</para>
+
+ <note>
+ <para>Warning: Be aware that different countries can have
+ substantially different tax policies for depreciation; all that this
+ document can really provide is some of the underlying ideas to help
+ you apply your <quote>favorite</quote> tax/depreciation policies.</para>
+ </note>
+ </sect2>
+ </sect1>
+
+ <sect1 id="dep_value1">
+ <title>Estimating Valuation</title>
+
+ <para>A central issue with depreciation is to determine how you will
+ estimate the future value of the asset. Compared to the often uncertain
+ estimates one has to do where appreciation of assets is concerned, we are
+ on somewhat firmer ground here. Using sources listed below should make it
+ fairly straight forward to estimate the future value of your depreciating
+ assets.</para>
+
+ <itemizedlist>
+ <listitem>
+ <para><emphasis>Tax Codes:</emphasis> For businesses that want to use
+ depreciation for tax purposes, governments tend to set up precise
+ rules as to how you are required to calculate depreciation. Consult
+ your local tax codes, which should explicitly state how to estimate
+ depreciation.</para>
+ </listitem>
+
+ <listitem>
+ <para><emphasis>Car Blue Book:</emphasis> For automobiles, it is easy
+ to look up in references such as <quote>Blue Books</quote> estimates of what an
+ automobile should be worth after some period of time in the future.
+ From this you will be able to develop a model of the
+ depreciation.</para>
+ </listitem>
+ </itemizedlist>
+
+ <sect2 id="dep_valueschemes2">
+ <title>Depreciation Schemes</title>
+
+ <para>A <emphasis>depreciation scheme</emphasis> is a mathematical model
+ of how an asset will be expensed over time. For every asset which
+ undergoes depreciation, you will need to decide on a depreciation
+ scheme. An important point to keep in mind is that, for tax purposes,
+ you will need to depreciate your assets at a certain rate. This is
+ called tax depreciation. For financial statement purposes you are free
+ to choose whatever method you want. This is book depreciation. Most
+ small businesses use the same rate for tax and book depreciation. This
+ way there is less of a difference between your net income on the
+ financial statements and your taxable income.</para>
+
+ <para>This section will present 3 of the more popular depreciation
+ schemes: <emphasis>linear</emphasis>, <emphasis>geometric</emphasis>,
+ and <emphasis>sum of digits</emphasis>. To simplify the examples, we
+ will assume the salvage value of the asset being depreciated is zero. If
+ you choose to use a salvage value, you would stop depreciating the asset
+ once the net book value equals the salvage value.</para>
+
+ <orderedlist>
+ <listitem>
+ <para><emphasis>Linear depreciation</emphasis> 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.</para>
+
+ <para>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:</para>
+
+ <para><table>
+ <title>Linear Depreciation Scheme Example</title>
+
+ <tgroup cols="3">
+ <tbody>
+ <row>
+ <entry><emphasis>Year</emphasis></entry>
+
+ <entry><emphasis>Depreciation</emphasis></entry>
+
+ <entry><emphasis>Remaining Value</emphasis></entry>
+ </row>
+
+ <row>
+ <entry>0</entry>
+
+ <entry>-</entry>
+
+ <entry>1500</entry>
+ </row>
+
+ <row>
+ <entry>1</entry>
+
+ <entry>300</entry>
+
+ <entry>1200</entry>
+ </row>
+
+ <row>
+ <entry>2</entry>
+
+ <entry>300</entry>
+
+ <entry>900</entry>
+ </row>
+
+ <row>
+ <entry>3</entry>
+
+ <entry>300</entry>
+
+ <entry>600</entry>
+ </row>
+
+ <row>
+ <entry>4</entry>
+
+ <entry>300</entry>
+
+ <entry>300</entry>
+ </row>
+
+ <row>
+ <entry>5</entry>
+
+ <entry>300</entry>
+
+ <entry>0</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table></para>
+ </listitem>
+
+ <listitem>
+ <para><emphasis>Geometric depreciation</emphasis> is depreciated by
+ a fixed percentage of the asset value in the previous period. This
+ is a front-weighted depreciation scheme, more depreciation being
+ applied early in the period. In this scheme the value of an asset
+ decreases exponentially leaving a value at the end that is larger
+ than zero (i.e.: a resale value).</para>
+
+ <para>Example: We take the same example as above, with an annual
+ depreciation of 30%.</para>
+
+ <para><table>
+ <title>Geometric Depreciation Scheme Example</title>
+
+ <tgroup cols="3">
+ <tbody>
+ <row>
+ <entry><emphasis>Year</emphasis></entry>
+
+ <entry><emphasis>Depreciation</emphasis></entry>
+
+ <entry><emphasis>Remaining Value</emphasis></entry>
+ </row>
+
+ <row>
+ <entry>0</entry>
+
+ <entry>-</entry>
+
+ <entry>1500</entry>
+ </row>
+
+ <row>
+ <entry>1</entry>
+
+ <entry>450</entry>
+
+ <entry>1050</entry>
+ </row>
+
+ <row>
+ <entry>2</entry>
+
+ <entry>315</entry>
+
+ <entry>735</entry>
+ </row>
+
+ <row>
+ <entry>3</entry>
+
+ <entry>220.50</entry>
+
+ <entry>514.50</entry>
+ </row>
+
+ <row>
+ <entry>4</entry>
+
+ <entry>154.35</entry>
+
+ <entry>360.15</entry>
+ </row>
+
+ <row>
+ <entry>5</entry>
+
+ <entry>108.05</entry>
+
+ <entry>252.10</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table></para>
+
+ <note>
+ <para>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 <quote>Capital Cost
+ Allowance</quote> 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.</para>
+ </note>
+ </listitem>
+
+ <listitem>
+ <para><emphasis>Sum of digits</emphasis> is a front-weighted
+ depreciation scheme similar to the geometric depreciation, except
+ that the value of the asset reaches zero at the end of the period.
+ This is a front-weighted depreciation scheme, more depreciation
+ being applied early in the period. This method is most often
+ employed in Anglo/Saxon countries. Here is an illustration:</para>
+
+ <para>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:</para>
+
+ <para><table>
+ <title>Sum of Digits Depreciation Scheme Example</title>
+
+ <tgroup cols="3">
+ <tbody>
+ <row>
+ <entry><emphasis>Year</emphasis></entry>
+
+ <entry><emphasis>Depreciation</emphasis></entry>
+
+ <entry><emphasis>Remaining Value</emphasis></entry>
+ </row>
+
+ <row>
+ <entry>0</entry>
+
+ <entry>-</entry>
+
+ <entry>1500</entry>
+ </row>
+
+ <row>
+ <entry>1</entry>
+
+ <entry>100*5=500</entry>
+
+ <entry>1000</entry>
+ </row>
+
+ <row>
+ <entry>2</entry>
+
+ <entry>100*4=400</entry>
+
+ <entry>600</entry>
+ </row>
+
+ <row>
+ <entry>3</entry>
+
+ <entry>100*3=300</entry>
+
+ <entry>300</entry>
+ </row>
+
+ <row>
+ <entry>4</entry>
+
+ <entry>100*2=200</entry>
+
+ <entry>100</entry>
+ </row>
+
+ <row>
+ <entry>5</entry>
+
+ <entry>100*1=100</entry>
+
+ <entry>0</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table></para>
+ </listitem>
+ </orderedlist>
+ </sect2>
+ </sect1>
+
+ <sect1 id="dep_accounts1">
+ <title>Account Setup</title>
+
+ <para>As with most accounting practices, there are a number of different
+ ways to setup depreciation accounts. We will present here a general method
+ which should be flexible enough to handle most situations. The first
+ account you will need is an <emphasis>Asset Cost</emphasis> account
+ (<application>&app;</application> account type <guilabel>Asset</guilabel>), which is simply a place where you record
+ the original purchase of the asset. Usually this purchase is accomplished
+ by a transaction from your bank account.</para>
+
+ <para>In order to keep track of the depreciation of the asset, you will
+ need two depreciation accounts. The first is an <emphasis>Accumulated
+ Depreciation</emphasis> account in which to collect the sum of all of the
+ depreciation amounts, and will contain negative values. In <application>&app;</application>, this
+ is an account type <emphasis>asset</emphasis>. The <emphasis>Accumulated Depreciation</emphasis>
+ account is balanced by a <emphasis>Depreciation Expense</emphasis> account,
+ in which all periodic depreciation expenses
+ are recorded. In <application>&app;</application>, this is an account type
+ <emphasis>expense</emphasis>.</para>
+
+ <para>Below is a generic account hierarchy for tracking the depreciation
+ of 2 assets, <emphasis>ITEM1</emphasis> and <emphasis>ITEM2</emphasis>. The <emphasis>Asset Cost</emphasis> accounts are balanced by
+ the <emphasis>Bank</emphasis> account, the <emphasis>Accumulated Depreciation</emphasis> account is balanced by
+ the <emphasis>Expenses:Depreciation</emphasis> account.</para>
+
+ <literallayout>
+-Assets
+ -Fixed Assets
+ -ITEM1
+ -Cost (Asset Cost account)
+ -Depreciation (Accumulated Depreciation account)
+ -ITEM2
+ -Cost (Asset Cost account)
+ -Depreciation (Accumulated Depreciation account)
+ -Current Assets
+ -Bank
+-Expense
+ -Depreciation (Depreciation Expense account)
+ </literallayout>
+
+ <para>One of the features of the account hierarchy shown above is that you
+ can readily see some important summary values about your depreciating
+ asset. The <emphasis>Assets:Fixed Assets:ITEM1</emphasis> account total shows you the current
+ estimated value for item1, the <emphasis>Assets:Fixed Assets:ITEM1:Cost</emphasis> shows you
+ what you originally paid for item1, <emphasis>Assets:Fixed Assets:ITEM1:Depreciation</emphasis>
+ shows you your accrued depreciation for item1,
+ and finally, <emphasis>Expenses:Depreciation</emphasis> demonstrates the total accrued
+ depreciation of all your assets.</para>
+
+ <para>It is certainly possible to use a different account hierarchy. One
+ popular account setup is to combine the <emphasis>Asset Cost</emphasis>
+ and <emphasis>Accrued Depreciation</emphasis> asset accounts. This has the
+ advantage of having fewer accounts cluttering your account hierarchy, but
+ with the disadvantage that to determine some of the summary details
+ mentioned in the paragraph above you will have to open the account
+ register windows. As with most things, there are many ways to do it, find
+ a way that works best for you.</para>
+
+ <para>The actual input of the depreciation amounts is done by hand every
+ accounting period. There is no way in <application>&app;</application> (as of yet) to perform the
+ depreciation scheme calculations automatically, or to input the values
+ automatically into the appropriate accounts. However, since an accounting
+ period is typically one year, this really is not much work to do by
+ hand.</para>
+ </sect1>
+
+ <sect1 id="dep_example1">
+ <title>Example</title>
+
+ <para>Let’s go ahead and step through an example. Imagine you are a
+ photographer and you use a car and an expensive camera for your personal
+ business. You will want to track the depreciation on these items, because
+ you can probably deduct the depreciation from your business taxes.</para>
+
+ <para>The first step is to build the account hierarchy (as shown in the
+ previous section, replace <emphasis>ITEM1</emphasis> and <emphasis>ITEM2</emphasis> with <quote>car</quote> and <quote>camera</quote>). Now,
+ record the purchase of your assets by transferring the money from your
+ bank account to the appropriate <emphasis>Asset Cost</emphasis> accounts
+ for each item (eg: the <emphasis>Assets:Fixed Assets:Car:Cost</emphasis> account for the
+ car). In this example, you start with $30k in the bank, the car cost $20k
+ and the camera cost $10k and were both purchased on January 1,
+ 2000.</para>
+
+ <screenshot id="dep_example">
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="figures/dep_example.png" format="PNG"
+ srccredit="Bengt Thuree" />
+ </imageobject>
+
+ <textobject>
+ <phrase>Asset Depreciation Example1</phrase>
+ </textobject>
+
+ <caption><para>The asset depreciation example main window, before
+ depreciation </para></caption>
+ </mediaobject>
+ </screenshot>
+
+ <para>Looking at the tax codes, we realize that we must report
+ depreciation on these items using the <quote>sum of digits</quote> scheme, over a 5
+ year period. So, the yearly depreciation amounts for the car come to
+ $6667, $5333, $4000, $2667, $1333 for years 1 to 5 respectively, rounded
+ to the nearest dollar. The yearly depreciation amounts for the camera are
+ $3333, $2667, $2000, $1333, $667. Consult the previous section on
+ Depreciation Schemes for the formula for calculating these values.</para>
+
+ <para>For each accounting period (IE: fiscal year) you record the
+ depreciation as an expense in the appropriate <emphasis>Accrued
+ Depreciation</emphasis> account (eg: the <emphasis>Assets:Fixed Assets:Car:Depreciation</emphasis>
+ account for the car). The two windows below show
+ your car’s accrued depreciation account and the main window after the
+ third year (IE: three periods) of depreciation using this <guilabel>sum of digits</guilabel>
+ scheme.</para>
+
+ <screenshot id="dep_assetreg">
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="figures/dep_assetreg.png" format="PNG"
+ srccredit="Bengt Thuree" />
+ </imageobject>
+
+ <textobject>
+ <phrase>Asset Depreciation Register Window</phrase>
+ </textobject>
+
+ <caption><para>The asset depreciation register window
+ </para></caption>
+ </mediaobject>
+ </screenshot>
+
+ <screenshot id="dep_assetmain">
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="figures/dep_assetmain.png" format="PNG"
+ srccredit="Bengt Thuree" />
+ </imageobject>
+
+ <textobject>
+ <phrase>Asset Depreciation Main Window</phrase>
+ </textobject>
+
+ <caption><para>The asset depreciation main window </para></caption>
+ </mediaobject>
+ </screenshot>
+
+ <note>
+ <para>A Word of Caution: Since depreciation and tax issues are closely
+ related, you may not always be free in choosing your preferred method.
+ Fixing wrong calculations will cost a whole lot more time and trouble
+ than getting the calculations right the first time, so if you plan to
+ depreciate assets, it is wise to make sure of the schemes you will be
+ permitted or required to use.</para>
+ </note>
+ </sect1>
+ -->
+</chapter>
diff --git a/guide/de/ch_oth_assets.xml b/guide/de/ch_oth_assets.xml
index 599f5e2..fdfdd44 100644
--- a/guide/de/ch_oth_assets.xml
+++ b/guide/de/ch_oth_assets.xml
@@ -1,5 +1,445 @@
-<chapter id="chapter_other_assets">
+<!--
+ (Do not remove this comment block.)
+ Version: 2.2.9
+ Last modified: October 19, 2010
+
+ Maintainers:
+ Tom Bullock <tbullock at nd.edu>
+
+ Author:
+ Tom Bullock <tbullock at nd.edu>
+
+Translators:
+ (translators put your name and email here)
+-->
+
+<chapter id="chapter_other_assets">
<title>Andere Aktiva</title>
<para>&untranslated;</para>
-</chapter>
+ <!--
+ <sect1 id="accts-oa1">
+ <title>General Concepts</title>
+ <para>This chapter presents many additional accounting treatments for
+ frequently encountered business and less-frequently found personal activities
+ that need recording in accounting books. The explanations below cover both the
+ description and purpose of the activity, and they include also the usual
+ accounting treatments (bookings or recordings) for these transactions.</para>
+
+ <para>These concepts have evolved over centuries of experience by those
+ keeping accounting records and will help you maximize your record keeping’s
+ utility and meaningfulness.</para>
+
+ <para>This section introduces categorization of assets in the balance sheet
+ based on time or the asset’s useful life (current and long-term). Sometimes
+ assets are also considered from the standpoint of their <emphasis>liquidity
+ </emphasis>, which is regarded as how close or distant the asset is from
+ being turned into cash. Near-cash assets are relatively quickly converted
+ to cash (e.g., accounts receivable), while assets requiring rather a long
+ time to convert to cash are considered to be relatively <emphasis>fixed
+ </emphasis> in their non-cash state (e.g., heavy equipment, buildings, land).
+ (Fixed does not mean they were repaired!)</para>
+
+ <para>You should find that current assets parallel those with more liquidity,
+ while long-term and fixed assets are those with much less liquidity. Finally,
+ below you will find a few assets that could be either current or long-term
+ based on the nature of the facts constituting them.</para>
+ </sect1>
+ <sect1 id="accts-oa2">
+ <title>Other Assets Described</title>
+ <sect2 id="accts-oa3">
+ <title>Current Assets</title>
+ <para>Current Assets are those activities whose
+ normal expected life would be one year or less. Such activities could
+ be tracking reimbursable expenses, travel advances, short-term loans
+ to a friend or family member, prepaid expenses, annual insurance
+ premium amortization, and so on. The individual entity could have
+ many other kinds of short term activities that reflect what it is
+ doing. (These asset types are explained individually below.)
+ </para>
+ </sect2>
+ <sect2 id="accts-oa4">
+ <title>Long-term (Fixed) Assets</title>
+ <para>Long-term (Fixed) Assets are those
+ activities whose normal expected life exceeds one or more years. This
+ grouping covers both tangible and intangible assets. Examples of
+ tangible assets are land, buildings, and vehicles (cars, trucks,
+ construction equipment, factory presses, etc.) Intangible assets
+ include such things as patents, copy rights, goodwill, etc. Because
+ the lives of some of these assets show wear and tear and deterioration
+ in value over time, businesses and individuals can allow for that
+ diminution in value by calculating depreciation on such assets. For
+ example, land normally does not depreciate, but buildings do, as do
+ equipment and vehicles. (These asset types are explained individually
+ below.)</para>
+ </sect2>
+ </sect1>
+ <sect1 id="accts-oa5">
+ <title>Current Assets</title>
+ <para>This section explains short-term receivables, reimbursable expenses,
+ travel advances, prepaid premiums, prepaid rent, suspense or wash accounts.
+ </para>
+ <sect2 id="accts-oa6">
+ <title>Short-term Receivables</title>
+ <para>This kind of account
+ is useful to reflect an agreement made with someone you trust.
+ Suppose you lent someone $500 and he agreed to repay you $50 a month.
+ If he paid on time, the loan you made would be paid off within a year,
+ which is why it is classified as a short-term receivable. So you
+ could record that loan initially in this account tree: <emphasis>OtherAssets:Current Assets:LoanToJoe.</emphasis>
+ At the time you give him the money: your
+ entry is debit (increase) LoanToJoe $500 and credit (decrease) Bank
+ $500. Each time you receive Joe’s payment you record $50 debit
+ (increase) to Bank and credit (decrease) LoanToJoe.</para>
+
+ <tip>
+ <para>Don’t become confused by the use of the word <quote>Loan</quote>.
+ <quote>Loan-To</quote> is the tipoff that you really have a receivable, that is,
+ you will receive from Joe, the money you previously loaned. Until he
+ actually pays the money owed you, you reflect his debt in your books
+ by an account describing your expectation–you will receive the
+ money owed you, hence the word <quote>receivable</quote>.</para>
+ </tip>
+ </sect2>
+ <sect2 id="accts-oa7">
+ <title>Reimbursable Expenses</title>
+ <para>This kind of activity
+ is one in which you spend your own money on behalf of someone else
+ (your employer, perhaps) and later you receive repayment of what you
+ spent. The case might be a business trip. The employer has a policy
+ of covering (paying for) all authorized expenses. After the
+ trip is over, the employee submits a report listing dates and amounts
+ spent with receipts for all the expenditures. The employer reviews
+ the report and pays for all items that it considers as having a valid business reason.
+ (Normally, employees know in advance what the employer will
+ reimburse, so only those items are recorded as a reimbursable expense
+ on the employee’s books.)</para>
+
+ <para>Because a business trip can involve different kinds of expenditures
+ (air travel, lodging, transportation at the destination, etc.),
+ different kinds of expenditures would be recorded in the one account
+ as long as the expenditures all related to the same trip. In other
+ words, if a second trip is made before the first is fully settled, a
+ second account for a different event could be set up. It would make
+ sense to do this, if it would help to keep separate all the details of
+ one trip from those of another. It is up to the person making the
+ trip to decide how much trouble it would be to put separate trips in
+ separate accounts or to put them all in the same account. The trip
+ taker should remember that the account must be reconciled in order to
+ know with certainty that all expenses have been reimbursed.</para>
+
+ <para>Recording the expenditures on the trip would be much the same.
+ That is, if you paid trip expenses by cash you would debit (increase) the
+ reimburseable expense account for the money paid in cash, because it
+ is a receivable to you until it has been reimbursed to you. The credit
+ offsetting your expenditure would decrease the account that shows the
+ cash in your pocket or the account from which you drew the cash for
+ the payment made. If you paid by credit card, the debit side would be
+ the same as just described, but the credit would be an increase to the
+ credit card company account on your books.</para>
+
+ <para>When you received your reimbursement, then the journal entry (or
+ transaction) to record receipt of the funds from the employer would be:
+ debit (increase) Bank for the check amount and credit (decrease) the
+ reimbursable expense account for the check amount.</para>
+
+ <para>If it turns out that the reimbursable expense account is not
+ zero balance after processing the employer’s payment, then it means that
+ there is a difference between you and the employer in handling the expense,
+ which needs to be investigated. If the balance is a debit
+ (a positive balance), your account has some money that was not reimbursed.
+ If the balance is a credit (a negative balance), you were paid for more
+ than what you recorded as due you. In both of those situations you should
+ reconcile the difference between what you recorded and what was paid.
+ That effort should disclose exactly what is causing the discrepancy.
+ You will need to contact the employer’s bookkeeper to know what was paid,
+ if the reimbursement check was not accompanied by a detailed list of the
+ items being paid you.</para>
+
+ <para>In the event the employer refused to reimburse you for an
+ expenditure, that effectively makes it your expense. In that case, you
+ would make this entry: debit (increase) your own Expense
+ (appropriately named) and credit (decrease) the Reimbursable Expense
+ account. That entry should result in a zero balance in the
+ Reimbursable Expense account. If not, reconcile until you identify
+ the difference.</para>
+
+ <tip>
+ <para>Sometimes there are small differences that don’t match an
+ individual entry. In those cases divide the amount by 2 or by 9. If
+ the unresolved amount is divisible by two, it suggests that both you
+ and the employer entered the item in the same manner: both as debits
+ or both as credits. If it is divisible by 9, then likely one of you
+ transposed adjoining numbers; e.g., one entered 69 and the other
+ entered 96. If the difference is divisible neither by 2 or by 9, then
+ it could be that more than one error is present.</para>
+ </tip>
+ </sect2>
+ <sect2 id="accts-oa8">
+ <title>Travel Advances</title>
+ <para>These are very similar to
+ Reimbursable Expenses. The difference is that someone gives you
+ money first; you spend it, and then you give a report accounting for
+ what you spent it on. The report is supported by invoices establishing
+ who, what, where, when, and how much for each expenditure. In the
+ Reimbursable Expense case, you spent your money first and later
+ recovered it.</para>
+
+ <para>In the Travel Advance case when you receive the advance, you
+ record on your books this entry: debit (increase) Bank for the travel
+ advance amount received (say, $500); credit (increase) the short-term
+ liability Travel Advance ($500). This is a liability, because
+ you are not gifted with the money, but only loaned it for the purpose
+ of having funds to spend when doing the employer’s business.</para>
+
+ <para>Frequently, the way these monetary arrangements work is that at
+ the beginning of for example a salesperson’s employment, he or she receives the advance
+ and monthly (or more frequently) turns in a report about who, what,
+ where, when, and how much he spent. The money in the report is
+ reimbursed if approved.
+ </para>
+
+ <para>During the period after receiving the advance and before filing
+ a request for reimbursement report, the salesperson can record his or her expenditures into
+ the advance liability account. In that case, the balance
+ in the account will show how much of the advance has not yet been spent
+ (assuming the Travel Advance balance is a credit). If no mistakes have
+ been made and all expenses are approved, then the sum of the unspent
+ account balance and the reimbursing check amount will equal the original
+ travel advance amount.</para>
+
+ <para>It makes sense for the salesperson to record the travel expenses to this advance account (and
+ not to his or her own expense accounts), because the money is being spent
+ on behalf of the employer, for the employer’s authorized expenses. It
+ is not the employee’s own money, and therefore not his or her own expense.
+ </para>
+
+ <para>When the salesperson receives the report reimbursement (say, $350), he or she debits
+ (increases) Bank, and credits (increases) again the Travel Advance
+ liability account, assuming that previously he or she had been recording
+ expenditures to the travel advance account. Tracking activity in this
+ manner causes the account to always show the amount that is owed the
+ employer.</para>
+
+ <para>See <xref linkend="accts-oa7"/> above for what to do if
+ the employer does not accept an item the employee put on the travel
+ advance reimbursement request report. The difference resolution effort
+ is essentially the same for both types of accounts.</para>
+ </sect2>
+ <sect2 id="accts-oa9">
+ <title>Prepaid Premiums or Prepaid Rent</title>
+ <para>Some types of
+ expenses are usually billed as semi-annual or annual amounts. For
+ example, the insurance industry will bill home insurance annually,
+ while car insurance premiums can be annual or semi-annual. For those
+ that pay an amount that covers several months or a full year, the
+ proper accounting treatment is to reflect in each accounting period
+ the amount that expresses the benefit applying to that period.</para>
+
+ <para>In the case of someone who pays a full-year’s insurance premium
+ at the beginning of the insurance period, the entry to record this is
+ debit (increase) Prepaid Insurance Premium for say, $1,200, and credit
+ (decrease) Bank for $1,200.</para>
+
+ <para>Then a monthly recurring journal entry (scheduled transaction)
+ is created that debits (increases) Insurance Expense $100 and credits
+ (decreases) Prepaid Insurance Premium $100. This technique spreads
+ the cost over the periods that receive the insurance coverage benefit.
+ Businesses following generally accepted accounting practices would
+ normally use this technique, especially if they had to present
+ financial statements to banks or other lenders. Whether individuals do
+ depends on the person and how concerned they are to match cost with
+ benefit across time periods. Another factor influencing use of this
+ technique would be the number of such situations the person encounters.
+ It is relatively easy to remember one or two, but more difficult if
+ having to manage 10 to 20. You would set up as many or as few as proved
+ useful and important to you.</para>
+ </sect2>
+ <sect2 id="accts-oa10">
+ <title>Suspense or Wash Accounts</title>
+ <para>The purpose of
+ these accounts is to provide a device to track <quote>change of mind</quote> situations.
+ The objective of these accounts is to provide a temporary location to
+ record charges and credits that are not to be included permanently in
+ your books of record. When the transactions reflected in these accounts
+ have been fully completed, Wash/Suspense accounts will normally carry
+ a zero balance.</para>
+
+ <para>For example, say in the grocery store you see canned vegetables on sale,
+ so you buy 6 cans at $1 per can. Say that the total purchases were $50.
+ When you come home and are putting things in the cupboard you discover
+ you already had 12 cans. You decide to return the 6 you just bought.
+ Some persons in this situation would charge (increase) the whole bill
+ to Grocery Expense; and when they returned the cans, they would credit
+ (decrease) Grocery Expense. That is one way of handling that. The effect
+ of this method is to leave recorded on your books the cost of items that
+ you really did not purchase from a permanent standpoint. It is only
+ when the items have actually been returned and the vendor’s return
+ receipt has also been recorded that the distortion this method generates
+ will then be removed.</para>
+
+ <para>Actually, there are several treatments, depending on when and how
+ the original transaction was booked/recorded and when you decided to
+ return the items purchased. Basically, did you change your mind before
+ you recorded the transaction or after doing so?</para>
+
+ <para>If you decided to return the items after recording the purchase
+ transaction, you may originally have charged Grocery Expense for the full
+ amount ($50) of all items. In that scenario, what you kept and the amount of
+ the items to be returned were grouped into one account. You could edit the
+ original transaction and restate the amount charged to the Grocery Expense
+ account to be the difference ($44) between the total paid ($50) for groceries
+ and the value of the items to be returned. That leaves the returned-item
+ value as the amount ($6) you should record to the Suspense account.</para>
+
+ <para>Obviously, if you decided to return items before you recorded your
+ purchase, then you would book the original entry as a charge to Grocery
+ Expense for the amount kept ($44) and as a charge to Suspense for the
+ amount returned ($6). The off-setting credit ($50) to cash or credit
+ card is not affected by these treatments.</para>
+
+ <para>When there are several persons shopping and at different vendors,
+ there can be a case where there are several returns happening at once
+ and in overlapping time frames. In that case the Wash Account is
+ charged (increased) at time of changing the mind, and either Bank or
+ Credit Card is credited. When the return occurs, the reverse happens:
+ Bank or Credit Card is debited for the cash value of the returned items
+ and the Wash/Suspense Account is credited in the same amount.</para>
+
+ <para>If the wash account has a non-zero balance, scanning the debit
+ and credit entries in the account will show the non-matched items.
+ That is, debits not matched by offsetting credits indicate items
+ intended to be returned but not actually returned yet. The reverse
+ (credits not matched by offsetting debits) indicates that returns were
+ made but the original charge was not recorded in the Wash Account.</para>
+
+ <para>These differences can be cleared up by returning unreturned items
+ or recording charges (debits) for items already returned. The mechanics
+ of doing that likely will be finding the original expense account the
+ item was charged to and making an entry like: debit Wash Account, credit
+ original expense. It also could be as described above where the original
+ recording is adjusted by adding a charge to Wash/Suspense account and
+ decreasing the amount charged to the original account.</para>
+ </sect2>
+ </sect1>
+ <sect1 id="accts-oa11">
+ <title>Short or Long-term Assets</title>
+ <para>This section explains why some types of assets may be short or
+ long-term and presents an example.</para>
+
+ <para>An example is deposits (e.g., utility, rental, security). If the
+ deposit agreement contains a provision to recover the deposit at the
+ end of a year, the treatment could be that of a short-term asset.
+ However, when the agreement is that the deposit holder returns the
+ funds only upon successful inspection at the end of the relationship,
+ then at the start of the relationship or agreement, the person paying
+ the deposit has to decide whether to write it off as a current expense
+ or to track it for eventual recovery at the end of the agreement
+ (not infrequently, moving to a new location).</para>
+
+ <para>Whichever decision is made, the accounting treatment is to debit
+ (increase) expense (assuming the write-off decision) or debit (increase)
+ Deposits Receivable (assuming the intent is to recover the deposit in
+ the future) and credit (decrease) Bank for the amount of the deposit
+ (if paid by cash) or credit (increase) credit card if paid using that
+ payment method.</para>
+ </sect1>
+ <sect1 id="accts-oa12">
+ <title>Long-term (Fixed) Assets</title>
+ <para>This section illustrates long-term assets (those whose useful lives
+ exceed a year) and discusses these types: land, buildings, leasehold
+ improvements, intangibles, vehicles and other equipment.</para>
+ <sect2 id="accts-oa13">
+ <title>Land</title>
+ <para>Land is not a wasting asset. That is, it
+ does not get used up over time and rarely suffers damage such that it
+ loses value. For that reason, it usually is recorded at cost at the
+ time of purchase. Appreciation in its value over decades is not recorded
+ and is not recognized in any way on the books of the owner. It is only
+ after land has been sold that sale price and purchase cost are compared
+ to calculate gain or loss on sale.</para>
+
+ <para>Land is frequently sold/purchased in combination with structures
+ upon it. That means that the cost has to become separated from the
+ cost of structures on it. Land valuation is usually part of the transfer
+ of ownership process and its value is shown on the purchase documents
+ separately from that of any structures it supports.</para>
+
+ <para>Land values shown on purchase documents frequently arise from the
+ process of value determination managed by assessors whose job it is
+ to assign values to land for tax purposes. Local and regional areas of
+ a state or province use the values determined by assessors in their tax
+ formulas, which provide revenues for local and regional governing
+ authorities to finance their required community services.</para>
+
+ <para>Should land be acquired in a situation not subject to a history of
+ land valuation by a formal valuation system, then the purchaser can appeal
+ to real estate agents and an examination of recent sale transactions for
+ information that would allow calculating a reasonable amount to express
+ the value of the land.</para>
+ </sect2>
+ <sect2 id="accts-oa14">
+ <title>Buildings</title>
+ <para>Buildings are the man-made <quote>caves</quote> in which
+ much of life’s human interaction occurs. These structures are wasting
+ assets, because in their use they or their components gradually wear.
+ Over time they begin to lose some of their function and they can suffer
+ damage due to planetary elements or human action.</para>
+
+ <para>Accepted accounting practice is to record the cost of the building
+ determined at time of ownership transfer (purchase) or at conclusion of all
+ costs of construction. Because buildings are frequently used for decades,
+ and due to the need to be able to calculate gain or loss on sale,
+ accounting practice preserves the original cost by not recording declines
+ in value in the account containing the original purchase or construction
+ cost.</para>
+
+ <para>Instead, the depreciation technique is used to show (in the
+ balance sheet) the structure’s net book value (original cost reduced by
+ accumulated depreciation). Depreciation is a separate topic treated
+ elsewhere in this Guide.</para>
+ </sect2>
+ <sect2 id="accts-oa15">
+ <title>Leasehold Improvements</title>
+ <para>When a business does
+ not own the building where it operates, and instead has a long-term
+ lease, it is not uncommon for the business tenant to make improvements to
+ the premises so that the structure obtains both function and appearance
+ that enhances conducting its business activities.</para>
+
+ <para>In these cases, the expenditures that the business incurs are recorded
+ in a Leasehold Improvements account: increase (debit) Leasehold Improvements,
+ decrease (credit) Bank or increase (credit) a suitable liability account
+ (which could be a liability to a contractor or a bank or a credit card,
+ etc.).</para>
+ </sect2>
+
+ <sect2 id="accts-oa16">
+ <title>Vehicles or Equipment</title>
+ <para>Vehicles or Equipment of all kinds usually
+ last for several years, but their useful lives are much shorter than
+ that of assets that have little movement in their functioning. Because
+ they do wear out over time, common accounting practice in business is
+ to record depreciation using life spans and depreciation methods
+ appropriate to the nature and use of the asset. Frequently, the life
+ and depreciation methods chosen are influenced by what is permitted per
+ national tax regulations for the kind of asset being depreciated.</para>
+ <para>Usually, businesses depreciate their assets. Individuals can
+ do so as well to the degree that taxing authorities permit. Very wealthy
+ persons employ accountants and attorneys to track and manage their
+ investments and assets holdings to take advantage of all tax benefits
+ permitted by law.</para>
+ </sect2>
+ <sect2 id="accts-oa17">
+ <title>Intangibles</title>
+ <para>The mechanics of accounting (debiting
+ and crediting appropriate accounts) for these assets are relatively simple,
+ much the same as for any of the above assets. Where the difficulty lies
+ is in their valuation, which is an advanced topic and not something that
+ individual persons and small businesses would likely encounter. For that
+ reason further discussion of items such as patents, copyrights, goodwill,
+ etc. are left out of this Guide.</para>
+ </sect2>
+ </sect1>
+ -->
+ </chapter>
diff --git a/guide/de/figures/dep_assetmain.png b/guide/de/figures/dep_assetmain.png
new file mode 100644
index 0000000..8e1bffd
Binary files /dev/null and b/guide/de/figures/dep_assetmain.png differ
diff --git a/guide/de/figures/dep_assetreg.png b/guide/de/figures/dep_assetreg.png
new file mode 100644
index 0000000..25ae8ac
Binary files /dev/null and b/guide/de/figures/dep_assetreg.png differ
diff --git a/guide/de/figures/dep_example.png b/guide/de/figures/dep_example.png
new file mode 100644
index 0000000..5b61000
Binary files /dev/null and b/guide/de/figures/dep_example.png differ
diff --git a/guide/de/gnucash-guide.xml b/guide/de/gnucash-guide.xml
index 1bf43a4..81aa0d1 100644
--- a/guide/de/gnucash-guide.xml
+++ b/guide/de/gnucash-guide.xml
@@ -23,13 +23,11 @@
<!ENTITY chapter12 SYSTEM "ch_bus_setup.xml">
<!ENTITY chapter13 SYSTEM "ch_bus_ar.xml">
<!ENTITY chapter14 SYSTEM "ch_bus_ap.xml">
-
<!ENTITY chapter15 SYSTEM "ch_bus_pay.xml">
-<!--
-<!ENTITY chapter16 SYSTEM "ch_budgets.xml"> -->
+<!ENTITY chapter16 SYSTEM "ch_budgets.xml">
<!ENTITY chapter17 SYSTEM "ch_oth_assets.xml">
-<!--
<!ENTITY chapter18 SYSTEM "ch_dep.xml">
+<!--
<!ENTITY chapter19 SYSTEM "ch_python_bindings.xml">
<!ENTITY chapter20 SYSTEM "ch_import_business_data.xml">
<!ENTITY appendixa SYSTEM "appendixa.xml">
@@ -522,13 +520,11 @@
&chapter12;
&chapter13;
&chapter14;
-
&chapter15;
-<!--
-&chapter16;-->
+&chapter16;
&chapter17;
-<!--
&chapter18;
+<!--
&chapter19;
&chapter20;
</part>
commit 27032cfd5221a952b0af247592d30b59bffa9898
Author: Mechtilde <ooo at mechtilde.de>
Date: Wed Dec 30 14:16:28 2015 +0100
add inforamtion about chapter budgets
diff --git a/guide/de/ch_budgets.xml b/guide/de/ch_budgets.xml
new file mode 100644
index 0000000..568a623
--- /dev/null
+++ b/guide/de/ch_budgets.xml
@@ -0,0 +1,206 @@
+<!--
+ (Do not remove this comment block.)
+ Version: 2.0.0
+ Last modified: July 9th 2006
+ Maintainers:
+ Chris Shoemaker <c.shoemaker at cox.net>
+ Author:
+ Chris Shoemaker <c.shoemaker at cox.net>
+ Translators:
+ (translators put your name and email here)
+-->
+ <chapter id="chapter_budgets">
+ <title>Budgets</title>
+ <para>&untranslated;</para>
+ <!--
+ <para>
+ This chapter explains how to create and use budgets with <application>&app;</application>.
+ </para>
+ <sect1 id="budget_concepts1">
+ <title>Basic Concepts</title>
+
+ <para>A budget is a tool for estimating expected income and expenses.
+ You can use it to help you plan how you intend for your finances to
+ change over a period of time, and to examine how your actual
+ financial transactions for the period compare to your planned
+ transactions.</para>
+
+ <para>The budgeting concept is quite general, so <application>&app;</application> offers a
+budgeting tool that is both simple and flexible. You, the user, have
+to decide how complex or simple you want to make your budget. This
+guide will help you make some of those decisions.</para>
+
+ <sect2 id="budget_conceptsterms2">
+ <title>Terminology</title> <para>There are a few helpful terms listed
+ below that will be used to discuss budgeting.</para>
+
+ <itemizedlist>
+ <listitem>
+ <para><emphasis>Budget</emphasis> - A financial plan describing
+ the expected revenues and/or disbursements for a particular time
+ period</para>
+ </listitem>
+ <listitem>
+ <para><emphasis>Cash Budget</emphasis> - A budget planning for
+ expected cash receipts and cash disbursements. This type of
+ budget tracks cash flow -- where your money comes from, where it
+ goes, and, of course, how much.</para>
+ </listitem>
+ <listitem>
+
+ <para><emphasis>Expense Budget</emphasis> - A budget chiefly for
+ planning what you spend your money on. This type of budget tracks
+ your expenses. It is typically not concerned with things like
+ appreciation or repayment of liabilities. However, it would
+ account for interest charges. For example, if you buy $100 worth
+ of groceries with your credit card, you incur an $100 expense for
+ groceries, and a $100 liability to your credit card company. When
+ you pay the credit card bill for $110, you are incurring an
+ additional interest expense of $10. An expense budget plans for
+ the transaction of buying the groceries and paying the interest,
+ but not the transaction of repaying the credit card
+ company.</para>
+
+ </listitem>
+ <listitem>
+ <para><emphasis>Capital Budget</emphasis> - A budget that
+ describes a plan for paying for a large future expense, often
+ through a combination of saving and borrowing money. Note:
+ Capital budgets can sometimes get quite complex because they can
+ try to answer the question "Can we afford to do such-and-such?" by
+ exploring various hypothetical scenarios that can involve
+ hypothetical accounts. </para>
+
+ </listitem>
+ <listitem>
+ <para><emphasis>Budget Period</emphasis> - The period of time
+ during which the plan is expected to take place. The most common
+ budget periods are annual and monthly. Sometimes, you may budget
+ for several consecutive periods at once, for convenience or for
+ finer-grained planning. For example, an annual budget may include
+ 12 monthly budget periods.</para> </listitem>
+
+ </itemizedlist>
+
+ </sect2>
+ </sect1>
+
+ <sect1 id="budget_creation1">
+ <title>Creating a Budget</title>
+ <para>Even before you begin to make a budget, it’s important to
+ have given some thought to your account hierarchy. For example, if
+ you want to budget a certain amount for your electric bill and a
+ certain amount for your water bill, you can’t have only an
+ <emphasis>Expenses:Utilities</emphasis> account. Your accounts must be at least as
+ specific as your budget. </para>
+
+
+ <sect2 id="budget_creation2">
+ <title>Choose Which Accounts To Budget For</title>
+ <para>The first step in creating a budget is to decide what it is
+ you want to plan for. This decision will affect which accounts
+ you include in your budget. For example, if you are only
+ interested in tracking your expenses, you may create an expense
+ budget by only entering amounts for expense accounts. On the
+ other hand, if you want to track all of your cash flow, you may
+ create a cash flow budget by entering amounts for asset,
+ liability, income and expense accounts.</para>
+
+ <para>Before you begin to create your budget, you need to make
+ two decisions: What accounts do I want to budget for? and When
+ do I want my budget to be for? You can always change your mind
+ later, after you’ve created a budget, but you need to start with
+ something.</para>
+
+ <tip><para>As a rule of thumb, if you mostly care about
+ <emphasis>what</emphasis> you spend your money on, you may want
+ to make an expense report. If you’re also concerned about having
+ enough money in the right places at the right times, you may want
+ to use a cash-flow budget.</para></tip>
+
+ </sect2>
+ <sect2>
+ <title>Choosing a Budget Period</title>
+ <para>Before creating a budget you must also decide what period of
+ time you want to plan for. The most common budget periods are
+ monthly and annual. If you want your budget to plan for changes
+ in financial patterns over time, then you should include multiple
+ budget periods in your budget. For example, if you want to plan
+ on having higher utility expenses in the winter than in the
+ summer, then you might break your annual budget into 4 quarters or
+ even 12 months, and budget a higher value for the winter periods
+ than for the summer periods.</para>
+ </sect2>
+
+ <sect2>
+ <title>Getting Started</title>
+ <para>To create your first budget click on <menuchoice><guimenu>Actions</guimenu>
+ <guisubmenu>Budget</guisubmenu><guimenuitem>New Budget</guimenuitem></menuchoice>. You will
+ immediately see a new budget with the default settings and no entries.
+ Then click on the <guibutton>Options</guibutton> button. The most important options are
+ the budget period and the number of periods. For the budget period,
+ choose the beginning date and the smallest period of time that you
+ want to plan for. Then, for the number of periods, choose how many
+ periods you want to plan for.</para>
+
+ <para>The budget page now shows a list of accounts with a column
+ for each budget period. The date shown in the title of each
+ column is the beginning of that budget period.</para>
+
+ </sect2>
+ <sect2>
+ <title>Entering Budget Values</title>
+ <para>Now, you must enter the budget values - the amounts that you
+ expect the account balances to change during the budget period.
+ There are two ways to enter budget values. The first way is to
+ simply click on the cell and enter an amount.</para>
+
+ <para>If you have past transactions recorded in <application>&app;</application>, the
+ second way is to let <application>&app;</application> estimate the budget values by looking
+ at those transactions. First, select the accounts you want
+ <application>&app;</application> to estimate. Then click on the <guibutton>Estimate</guibutton> <emphasis>Toolbar</emphasis> button.
+ In the <guilabel>Estimate Budget Values</guilabel> dialog, select the date past which
+ <application>&app;</application> should look for past transactions. <application>&app;</application> will start at
+ that date and look forward for the duration of your budget. For
+ example, if you are making an annual budget, and you select
+ Jan. 1, 2005, <application>&app;</application> will look at all the transactions in that
+ account from Jan. 1, 2005 through Dec. 31, 2005.</para>
+ </sect2>
+ </sect1>
+
+ <sect1 id="budget_reporting1">
+ <title>Budget Reporting</title>
+ <para>You’ve already done the hardest part - creating your budget.
+ But now you want to know how your actual financial transactions
+ compare to your plan. You need to run the Budget Report.</para>
+ <para>Click on <menuchoice><guimenu>Reports</guimenu><guisubmenu>Budget</guisubmenu>
+ <guimenuitem>Budget Report</guimenuitem></menuchoice>. For each
+ account, the Budget Report will show the budgeted and the actual
+ amounts in two adjacent columns for each period in the budget. If
+ you have created multiple budgets, you can use the Budget Report
+ Options to select which budget to use in the report.
+ </para>
+ <para>Two other types of budget reports are commonly used in the
+ small business setting. They are the <emphasis>Budgeted Income
+ Statement</emphasis> and the <emphasis>Budgeted Balance
+ Sheet</emphasis>.</para>
+ <sect2>
+ <title>Budgeted Income Statement</title>
+ <para>The budgeted income statement is similar to the income
+ statement. Both show the revenues and expenses for a given period
+ as well as the profit, which is the difference revenue - expenses.
+ The income statement is based on historical data, but the
+ <emphasis>budgeted</emphasis> income statement is based on the
+ predictions made in the budget.</para>
+ </sect2>
+ <sect2>
+ <title>Budgeted Balance Sheet</title>
+ <para>The budgeted balance sheet is similar to the balance sheet.
+ Both show the assets, liabilities, and equity. The difference is
+ that the balance sheet is based on historical data, and the
+ <emphasis>budgeted</emphasis> balance sheet is based on the
+ predictions made in the budget.</para>
+ </sect2>
+ </sect1>
+ -->
+ </chapter>
commit 451f2e3c9639fd53d3a1c47d83234820fb1dff15
Author: Mechtilde <ooo at mechtilde.de>
Date: Wed Dec 30 14:11:42 2015 +0100
ad inforamtion about chapter bus_pay
diff --git a/guide/de/Makefile.am b/guide/de/Makefile.am
index 9eff599..a0bfb19 100644
--- a/guide/de/Makefile.am
+++ b/guide/de/Makefile.am
@@ -8,6 +8,7 @@ entities = \
ch_bus_ap.xml \
ch_bus_ar.xml \
ch_bus_intro.xml \
+ ch_bus_pay.xml \
ch_bus_setup.xml \
ch_capgain.xml \
ch_cbook.xml \
diff --git a/guide/de/ch_bus_pay.xml b/guide/de/ch_bus_pay.xml
new file mode 100644
index 0000000..2c61459
--- /dev/null
+++ b/guide/de/ch_bus_pay.xml
@@ -0,0 +1,301 @@
+<!--
+ (Do not remove this comment block.)
+ Version: 2.0.0
+ Last modified: July 9th 2006
+ Maintainers:
+ Chris Lyttle <chris at wilddev.net>
+ Author:
+ Jon Lapham <lapham at extracta.com.br>
+ updated Patrick Schweiger <pks at spiffykitty.com>
+ Originally designed by Carol Champagne.
+ Translators:
+ (translators put your name and email here)
+-->
+ <chapter id="chapter_bus_pay">
+ <title>Payroll</title>
+ <para>&untranslated;</para>
+ <!--
+ <para>Payroll is a financial record of wages, net pay, paid vacations, and deductions for an employee. This chapter demonstrates how to track payroll using <application>&app;</application></para>
+ <sect1 id="bus-pay-concepts1">
+ <title>Basic Concepts</title>
+ <para>Payroll is a financial record of wages, net pay, paid vacations, and deductions for an employee. Basically, anything that relates to giving money or benefits to an employee. Payroll is one of the more complex tasks in accounting, because there are many different accounts, people, and agencies involved in paying salaries.</para>
+ <para>Payroll is typically accounted for as an expense. Sometimes accountants <quote>store</quote> some payroll expenses in a short term liability account. This is useful for things such as payroll taxes, which may be paid at a different time than the employee. The employee might get paid biweekly, while taxes are paid quarterly. This chapter presents a methodology which expenses payroll immediately for salaries, but stores taxes in liability accounts.</para>
+ <note>
+ <para><application>&app;</application> does not have an integrated payroll system. While you can track payroll expenses in <application>&app;</application>, the calculation of taxes and deductions has to be done outside of <application>&app;</application>.</para>
+ </note>
+ </sect1>
+
+ <sect1 id="bus-pay-acct1">
+ <title>Account Setup</title>
+
+ <para>Local tax law must be considered when setting up accounts. Because there are many different ways payroll taxes are handled throughout the world, this section presents a very simple structure. From this, you should be able to adapt your particular payroll deductions setup.</para>
+ <para>Assume that you must pay 2 taxes, Tax1 and Tax2 and that each has an employee contributed and an employer contributed component.</para>
+ <para>The employee’s salary and these two taxes are expense accounts. The tax components are liability accounts. The tax liability accounts are where you accumulate the taxes withheld for all of your employees. The taxes are later paid to the appropriate government agency.</para>
+ <para>
+ <literallayout>
+Simple Payroll Account Layout:
+
+-Assets
+ -Checking
+-Liabilities
+ -Tax1 (short term <quote>storage</quote> account)
+ -Tax2 (short term <quote>storage</quote> account)
+-Expenses
+ -Salaries
+ -Tax1
+ -Tax2
+ </literallayout>
+
+ <note>
+ <para>Resist the temptation to create per-employee sub-accounts to track individual salaries. Creating a sub-account for each employee leads to unmanageably large lists of accounts. Imagine the account structure after a few years of employees coming and going. It is much simpler to keep all of your employees’ payroll records within a single account (<emphasis>Expenses:Salaries</emphasis> for example) and use reports to view per-employee information.</para>
+ </note>
+ </para>
+
+ </sect1>
+
+ <sect1 id="bus-pay-protocol1">
+ <title>Protocol</title>
+ <para><application>&app;</application> does not have an integrated payroll system. <application>&app;</application> can track your payroll expenses, but you need to develop a payroll protocol and perform the calculations outside of <application>&app;</application>, in a spreadsheet for example. In this section, one such protocol is presented. You can use the sample protocol as a model.</para>
+
+ <sect2 id="bus-pay-protocolone2">
+ <title>Step 1: Deductions list</title>
+ <para>The first step to the payroll protocol is to create a list of all the possible taxes and deductions for each employee. Each entry should include definitions and formulas for calculating each value. Once the protocol is established it needs to be changed only when payroll laws or tax rates change.</para>
+
+ <para>In the proposed scenario, such a list would look like this:</para>
+ <itemizedlist spacing="compact">
+ <listitem>
+ <para><emphasis>E_GROSS_SALARY</emphasis> - Employee gross salary</para>
+ </listitem>
+ <listitem>
+ <para><emphasis>E_TAX1</emphasis> - Employee contribution to tax1 (X% of E_GROSS_SALARY)</para>
+ </listitem>
+ <listitem>
+ <para><emphasis>E_TAX2</emphasis> - Employee contribution to tax2 (X% of E_GROSS_SALARY)</para>
+ </listitem>
+ <listitem>
+ <para><emphasis>C_TAX1</emphasis> - Company contribution to tax1 (X% of E_GROSS_SALARY)</para>
+ </listitem>
+ <listitem>
+ <para><emphasis>C_TAX2</emphasis> - Company contribution to tax2 (X% of E_GROSS_SALARY)</para>
+ </listitem>
+ </itemizedlist>
+ <note>
+ <para>The employee’s net salary (E_NET_SALARY) is defined as E_GROSS_SALARY - E_TAX1 - E_TAX2 and need not be placed in this list since it is composed of items that already exist.</para>
+ </note>
+ <para>Place the actual formulas for calculating each deduction in this list. Sometimes these formulas are quite complex, and sometimes they simply say "look it up in table XYZ of the tax codes".</para>
+ <para>Notice that you can calculate some interesting values using the above definitions. One such value is the total cost to the company: E_GROSS_SALARY + C_TAX1 + C_TAX2.</para>
+ </sect2>
+
+ <sect2 id="bus-pay-protocoltwo2">
+ <title>Step 2: Create the Transaction Map</title>
+ <para>When you record payroll in <application>&app;</application>, do so with a single split transaction. This split transaction populates the appropriate expense and liability accounts. If you need to look the payroll details at a later time, open the split transaction.</para>
+ <para>With the deductions list from above, an employee split transaction map can be generated. Each of the items in the list is mapped to a <application>&app;</application> account.</para>
+
+ <para>
+ <table>
+ <title>Transaction Map</title>
+ <tgroup cols="3">
+ <thead>
+ <row>
+<entry>Account</entry><entry>Increase</entry><entry>Decrease</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+<entry>Assets:Checking</entry><entry></entry><entry>E_NET_SALARY</entry>
+ </row>
+ <row>
+<entry>Expenses:Salaries</entry><entry>E_GROSS_SALARY</entry><entry></entry>
+ </row>
+ <row>
+<entry>Liabilities:Tax1</entry><entry></entry><entry>E_TAX1</entry>
+ </row>
+ <row>
+<entry>Liabilities:Tax2</entry><entry></entry><entry>E_TAX2</entry>
+ </row>
+ <row>
+<entry>Expenses:Tax1</entry><entry>C_TAX1</entry><entry></entry>
+ </row>
+ <row>
+<entry>Liabilities:Tax1</entry><entry></entry><entry>C_TAX1</entry>
+ </row>
+ <row>
+<entry>Expenses:Tax2</entry><entry>C_TAX2</entry><entry></entry>
+ </row>
+ <row>
+<entry>Liabilities:Tax2</entry><entry></entry><entry>C_TAX2</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </para>
+
+ <para>Note that the C_TAX1 and C_TAX2 components have entries in the both the liability and expense accounts. The company component of each tax is expensed at the time of payroll, but remains a liability until taxes are due.</para>
+ </sect2>
+
+ <sect2 id="bus-pay-protocolthree2">
+ <title>Step 3: Pay the Employee</title>
+ <para>Go to the account from which the employee will be paid, for example your <emphasis>Assets:Checking</emphasis> account. Open a split transaction and enter the real values using the Transaction Map above as a guide. Repeat this for all employees.</para>
+ <tip>
+ <para>This manual process is tedious, especially if you have a large number of employees.</para>
+ <para>One <application>&app;</application> tool you certainly want use when entering employee payroll is duplicate transaction (use the <guibutton>Duplicate</guibutton> <emphasis>Toolbar</emphasis> button). This saves you from having to enter all the transaction splits for each employee. You still need to change the amounts of money to match each employee’s real payroll values, but you will not have to build the split for each employee.</para>
+ <para>If payroll transactions do not change significantly every pay period, you can also use the duplicate transaction feature to duplicate each employee’s most recent payroll transaction for the current pay period. If you find you are doing so all the time, read about the Schedule Transactions feature and save even more time!</para>
+ </tip>
+ </sect2>
+
+ <sect2 id="bus-pay-protocolfour2">
+ <title>Step 4: Pay the Government</title>
+ <para>The final thing to do is to pay the taxes to the government. The liability accounts have been collecting the taxes for various government agencies, and periodically you need to send a check to the government to pay this charge. To do so, you simply enter a 2 account transaction in (for example) your checking account to pay off the tax liability. The transaction is between the checking account and the liability account, no expense account is involved. The expense accounts are charged at the time the tax liability is recorded.</para>
+ </sect2>
+
+ </sect1>
+
+ <sect1 id="bus-pay-example1">
+ <title>Example</title>
+ <para>Using the account setup seen previously, let’s go through an example. Assume that there are 2 employees (E1 and E2) which each earn $1000 per month gross salary. The employee contribution to Tax1 and Tax2 are 10% and 5% respectively. The company contribution to Tax1 and Tax2 are 15% and 10% each on top of the employees gross salary.</para>
+ <para>Staring with $50k in the bank, and before doing any payroll, the account hierarchy looks like this:</para>
+ <screenshot id="bus-pay-ex1">
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="figures/bus_pay_ex1.png"
+ srccredit="Patrick Schweiger" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase>Payroll Example 1</phrase>
+ </textobject>
+ <caption>
+ <para>Payroll Initial Setup
+ </para>
+ </caption>
+ </mediaobject>
+ </screenshot>
+
+ <sect2 id="bus-pay-exampleprotocol2">
+ <title>Build Protocol</title>
+ <para>The deductions list for employee 1:</para>
+ <itemizedlist>
+ <listitem>
+ <para><emphasis>E_GROSS_SALARY</emphasis> - Employee gross salary - <emphasis>$1000</emphasis></para>
+ </listitem>
+ <listitem>
+ <para><emphasis>E_TAX1</emphasis> - Employee contribution to tax1 - <emphasis>$100</emphasis> (10% of E_GROSS_SALARY)</para>
+ </listitem>
+ <listitem>
+ <para><emphasis>E_TAX2</emphasis> - Employee contribution to tax2 - <emphasis>$50</emphasis> (5% of E_GROSS_SALARY)</para>
+ </listitem>
+ <listitem>
+ <para><emphasis>C_TAX1</emphasis> - Company contribution to tax1 - <emphasis>$150</emphasis> (15% of E_GROSS_SALARY)</para>
+ </listitem>
+ <listitem>
+ <para><emphasis>C_TAX2</emphasis> - Company contribution to tax2 - <emphasis>$100</emphasis> (10% of E_GROSS_SALARY)</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ <table>
+ <title>Transaction Map for Employee 1</title>
+ <tgroup cols="3">
+ <thead>
+ <row>
+<entry>Account</entry><entry>Increase</entry><entry>Decrease</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+<entry>Assets:Checking</entry><entry></entry><entry>$850 (E_NET_SALARY)</entry>
+ </row>
+ <row>
+<entry>Expenses:Salaries</entry><entry>$1000 (E_GROSS_SALARY)</entry><entry></entry>
+ </row>
+ <row>
+<entry>Liabilities:Tax1</entry><entry></entry><entry>$100 (E_TAX1)</entry>
+ </row>
+ <row>
+<entry>Liabilities:Tax2</entry><entry></entry><entry>$50 (E_TAX2)</entry>
+ </row>
+ <row>
+<entry>Expenses:Tax1</entry><entry>$150 (C_TAX1)</entry><entry></entry>
+ </row>
+ <row>
+<entry>Liabilities:Tax1</entry><entry></entry><entry>$150 (C_TAX1)</entry>
+ </row>
+ <row>
+<entry>Expenses:Tax2</entry><entry>$100 (C_TAX2)</entry><entry></entry>
+ </row>
+ <row>
+<entry>Liabilities:Tax2</entry><entry></entry><entry>$100 (C_TAX2)</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </para>
+
+ </sect2>
+
+
+ <sect2 id="bus-pay-examplepay2">
+ <title>Pay an Employee</title>
+
+ <para>Now, enter the first split transaction for employee 1 in the checking account. The split transaction looks like this:</para>
+
+ <screenshot id="bus-pay-ex2">
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="figures/bus_pay_ex2.png"
+ srccredit="Patrick Schweiger" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase>Payroll Example 2</phrase>
+ </textobject>
+ <caption>
+ <para>Employee 1 Split Transaction
+ </para>
+ </caption>
+ </mediaobject>
+ </screenshot>
+
+ <tip>
+ <para>When paying employees, enter only the employee name in the Description area. If you decide to use <application>&app;</application>’s check printing capabilities, the check is automatically made out to the correct employee. If you want to record other information in the transaction besides the employee name, use the Notes area, available when viewing the Register in double-line mode.</para>
+ </tip>
+ <para>Repeat this for the second employee, which leaves the account hierarchy looking like this:</para>
+
+ <screenshot id="bus-pay-ex3">
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="figures/bus_pay_ex3.png"
+ srccredit="Patrick Schweiger" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase>Payroll Example 3</phrase>
+ </textobject>
+ <caption>
+ <para>Account Tree After Salaries Paid
+ </para>
+ </caption>
+ </mediaobject>
+ </screenshot>
+ </sect2>
+ <sect2 id="bus-pay-examplegovt2">
+ <title>Pay the Government</title>
+ <para>The <emphasis>Liabilities:Tax1</emphasis> and <emphasis>Liabilities:Tax2</emphasis> accounts continue to track how much you must pay to the government agencies responsible for each. When it is time to pay these agencies, make a transaction from the checking account to the liability accounts. No expense accounts are involved. The main account will then appear like this for this example:</para>
+
+ <screenshot id="bus-pay-ex4">
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="figures/bus_pay_ex4.png"
+ srccredit="Patrick Schweiger" format="PNG"/>
+ </imageobject>
+ <textobject>
+ <phrase>Payroll Example 4</phrase>
+ </textobject>
+ <caption>
+ <para>Accounts After Paying Government
+ </para>
+ </caption>
+ </mediaobject>
+ </screenshot>
+
+ </sect2>
+ </sect1>
+-->
+ </chapter>
diff --git a/guide/de/gnucash-guide.xml b/guide/de/gnucash-guide.xml
index 6a02ba0..1bf43a4 100644
--- a/guide/de/gnucash-guide.xml
+++ b/guide/de/gnucash-guide.xml
@@ -23,8 +23,9 @@
<!ENTITY chapter12 SYSTEM "ch_bus_setup.xml">
<!ENTITY chapter13 SYSTEM "ch_bus_ar.xml">
<!ENTITY chapter14 SYSTEM "ch_bus_ap.xml">
-<!--
+
<!ENTITY chapter15 SYSTEM "ch_bus_pay.xml">
+<!--
<!ENTITY chapter16 SYSTEM "ch_budgets.xml"> -->
<!ENTITY chapter17 SYSTEM "ch_oth_assets.xml">
<!--
@@ -521,9 +522,9 @@
&chapter12;
&chapter13;
&chapter14;
-<!--
-&chapter15;
+&chapter15;
+<!--
&chapter16;-->
&chapter17;
<!--
commit d3e3d415296ef78def99e4ee27c4b84d792ddc11
Author: Mechtilde <ooo at mechtilde.de>
Date: Wed Dec 30 13:57:15 2015 +0100
adapt chapter bus_ap after translation chapter bus_setup
diff --git a/guide/de/ch_bus_ap.xml b/guide/de/ch_bus_ap.xml
index a87ee7a..9a9dafa 100644
--- a/guide/de/ch_bus_ap.xml
+++ b/guide/de/ch_bus_ap.xml
@@ -2,12 +2,13 @@
(Do not remove this comment block.)
Originally designed by Carol Champagne.
Version: 2.0.0
- Last modified: July 9th 2006
+ Last modified: Sep 19th 2015 (Englisch 20.09.2015)
Maintainers:
Chris Lyttle <chris at wilddev.net>
Author:
- Jon Lapham <lapham at extracta.com.br>
+ Jon Lapham <lapham at extracta.com.br>
updated Patrick Schweiger <pks at spiffykitty.com>
+ Chris Good <chris.good at ozemail.com.au>
Translators:
Mechtilde Stehmann<ooo at mechtilde.de>
-->
@@ -21,76 +22,12 @@ corrected to be less describing of the interface and more tutorial oriented
<title>Kreditorenbuchhaltung</title>
<para>Die Kreditorenbuchhaltung bezieht sich auf Lieferungen und Leistungen, die ein Unternehmen gekauft hat und nun bezahlen muss.</para>
- <sect1 id="bus-ap-concepts1">
- <title>Grundgedanken</title>
- <para>Dieses Kapitel konzentriert sich auf die Kreditorenbuchhaltung. Diese bezieht sich auf Lieferungen und Leistungen, die ein Unternehmen gekauft hat, für die eine Zahlung geplant werden muss.</para>
- </sect1>
-
- <sect1 id="bus-ap-setup1">
- <title>Starteinrichtung</title>
- <para>Um die Kreditorenbuchhaltung in <application>&app;</application> einzurichten, müssen zunächst zwei Dinge getan werden.
- Das Erste ist die Erstellung einer zweckdienlichen Kontenhierarchie, und das Zweite ist die Registrierung des Unternehmens in <application>&app;</application>.</para>
-
- <sect2 id="bus-ap-setupacct2">
- <title>Konteneinrichtung</title>
-
- <para>Es gibt viele verschiedene Möglichkeiten, eine Geschäftskontenhierarchie
- einzurichten. Sie können mit der Einrichtung der Geschäftskonten anfangen,
- die mit dem Neuen Kontenplan erstellen Assistenten zur Verfügung gestellt wird, oder einen Kontenplan
- händisch erstellen. Um auf die vorgefertigten Geschäftskontenpläne zuzugreifen,
- starten Sie<application>&app;</application> und
- Klicken auf <menuchoice><guimenu>Datei</guimenu><guimenuitem>Neue Datei</guimenuitem></menuchoice> und
- fahren fort, bis Sie eine Liste der verfügbaren Kontenpläne sehen. Dort wählen Sie
- den gewünschten Kontenrahmen (z.B. SKR03 und SKR04) aus.</para>
-
- <para>Die vorgefertigte Geschäftskontenhierarchie wird nicht exakt Ihren Bedürfnissen
- entsprechen. Sie werden Anpassungen an der Kontenhierarchie durchführen, damit diese Ihre
- spezielle Situation wiedergibt. Wahrscheinlich wird sie soweit passen, dass empfohlen werden kann, damit anzufangen.</para>
-
- <para>Die Kreditorenbuchhaltung bezieht sich auf von Ihrem
- Unternehmen gekaufte Lieferungen und Leistungen, für die noch keine Zahlung
- erfolgte. Dies wird in der Bilanz als Verbindlichkeit dargestellt, weil Sie
- dafür zahlen müssen. Um <application>&app;</application>’s eingebaute
- Kreditorenbuchhaltung nutzen zu können, müssen Sie zuerst, ein Konto mit
- der Kontoart <emphasis>Verbindlichkeit</emphasis> einrichten. Das <emphasis>Verbindlichkeitskonto</emphasis> ist üblicherweise ein Unterkonto unter Passiva. Innerhalb dieses Kontos wird die integrierte
- Kreditorenbuchhaltung Geschäftsvorfälle buchen.</para>
- <literallayout>
-Basishierarchie für Kreditorenbuchhaltung:
-
--Aktiva
- -Bank
--Verbindlichkeiten
- -Verbindlichkeiten aus Lieferungen und Leistungen
--Ausgaben
- -AP Ausgaben
- </literallayout>
-
- <para>Sie benötigen zusätzlich hinzugefügte Aktiva- und Aufwandskonten, um die
- Hierarchie nutzbar zu machen. Diese wichtigen Aspekte dieser Hierarchie sind die Nutzung
- eines Aufwandkontos und eines Verbindlichkeitskonto mit der Kontoart <emphasis>Offene Verbindlichkeit</emphasis>.</para>
- </sect2>
-
- <sect2 id="bus-ap-setupcname2">
- <title>Registrierung des Unternehmens</title>
-
- <para>Nachdem Sie die Kontenstruktur abgebildet haben, registrieren Sie <application>&app;</application>
- Datei als zu Ihrem Unternehmen gehörend. Für die Registrierung Ihres Unternehmens wählen Sie in
- <menuchoice><guimenu>Datei</guimenu><guimenuitem>Eigenschaften</guimenuitem><guimenuitem>Geschäft</guimenuitem></menuchoice>:</para>
+ <title>Starteinrichtung</title>
- <itemizedlist>
- <listitem>
- <para>den Namen Ihres Unternehmens mit den Kontaktinformationen
- wie Telefon-, Faxnummern, E-Mail Adresse und URL der Webseite</para>
- </listitem>
-
- <listitem>
- <para>die Identifikationsnummer Ihres Unternehmens (z.b die UStID)
- im Feld <guilabel>Firmennummer</guilabel>.</para>
- </listitem>
-
- </itemizedlist>
- </sect2>
+ <para>Durchführung der Einrichtung ist in <xref linkend="chapter_bus_setup" />
+ beschrieben.
+ </para>
</sect1>
<sect1 id="bus-ap-components1">
diff --git a/guide/de/ch_bus_ar.xml b/guide/de/ch_bus_ar.xml
index adcced7..48a1514 100644
--- a/guide/de/ch_bus_ar.xml
+++ b/guide/de/ch_bus_ar.xml
@@ -27,7 +27,7 @@ corrected to be less describing of the interface and more tutorial oriented
<title>Starteinrichtung</title>
<para>Durchführung der Einrichtung ist in <xref linkend="chapter_bus_setup" />
- aufgeführt.
+beschrieben.
</para>
</sect1>
commit e92d1a48201daa397ac8fb2092e3e05d4f240970
Author: Mechtilde <ooo at mechtilde.de>
Date: Wed Dec 30 13:51:54 2015 +0100
adapt chapter bus_ar after translation chapter bus_setup
diff --git a/guide/de/ch_bus_ar.xml b/guide/de/ch_bus_ar.xml
index 6b25602..adcced7 100644
--- a/guide/de/ch_bus_ar.xml
+++ b/guide/de/ch_bus_ar.xml
@@ -1,12 +1,12 @@
<!--
(Do not remove this comment block.)
Version: 2.0.0
- Last modified: July 9th 2006
+ Last modified: July 9th 2006 (English 20.09.2015)
Maintainers:
Chris Lyttle <chris at wilddev.net>
Author:
- Jon Lapham <lapham at extracta.com.br>
- updated Patrick Schweiger <pks at spiffykitty.com>
+ Jon Lapham <lapham at extracta.com.br>
+ updated Patrick Schweiger <pks at spiffykitty.com>
Originally designed by Carol Champagne.
Translators:
Mechtilde Stehmann<ooo at mechtilde.de>
@@ -23,115 +23,16 @@ corrected to be less describing of the interface and more tutorial oriented
<para>Die Debitorenbuchhaltung (OP = Offene Posten) bezieht sich auf Lieferungen oder Leistungen,
die von Ihrem Unternehmen bereitgestellt, aber bisher noch nicht bezahlt wurden.</para>
- <sect1 id="bus-ar-overview1">
- <title>Übersicht über geschäftliche Funktionen</title>
-
- <para>Die Buchhaltungsanforderungen unterscheiden sich sehr von der einer
- Privatperson. Im Wirtschaftsleben gibt es Kunden, die Geld schulden (Debitoren), Lieferanten, denen Geld
- geschuldet wird (Kreditoren), eine Lohn- und Gehaltsliste, komplexere Steuergesetze
- usw. <application>&app;</application> bietet
- geschäftlich orientierte Funktionen, diese Bedürfnisse zu befriedigen.</para>
-
- <para>Die Debitorenbuchhaltung (OP) wird im Wirtschaftsleben genutzt, um die Umsätze aufzuzeichnen,
- die nicht sofort bezahlt werden. Die Kreditorenbuchhaltung zeichnet eingegangene
- Rechnungen auf, die später zahlbar sind. Diese Varianten der Buchhaltung
- werden in erster Linie dann genutzt, wenn Sie viele Ausgangs- und Eingangsrechnungen
- haben und Sie den Überblick über die Zahlungsziele nicht verlieren wollen.
- Für die meisten privaten Nutzer lohnt sich der Aufwand einer Debitoren- und
- Kreditorenbuchhaltung nicht.</para>
- </sect1>
-
- <sect1 id="bus-ar-concepts1">
- <title>Grundgedanken</title>
-
- <para>Die Debitorenbuchhaltung (OP) bezieht sich auf Lieferungen oder Leistungen, die von Ihrem Unternehmen bereitgestellt, aber bisher nicht bezahlt wurden. Diese werden in der
- Bilanz als Aktiva ausgewiesen, weil die Erwartung besteht,
- dass man demnächst eine Zahlung erhält.</para>
- </sect1>
-
- <sect1 id="bus-ar-setup1">
+ <sect1 id="bus-ar-setup1">
<title>Starteinrichtung</title>
- <para>Um <application>&app;</application> für die Debitorenbuchhaltung für ein
- Unternehmen einzurichten, müssen zu Beginn zwei Dinge
- getan werden. Das Erste ist die Erstellung einer zweckdienlichen
- Kontenhierarchie, und das Zweite ist die Registrierung des Unternehmens in
- <application>&app;</application>.</para>
-
- <sect2 id="bus-ar-setupacct2">
- <title>Konteneinrichtung</title>
-
- <para>Es gibt viele verschiedene Möglichkeiten, eine Geschäftskontenhierarchie
- einzurichten. Sie können mit der Einrichtung der Geschäftskonten anfangen,
- die mit dem Neuen Kontenplan erstellen Assistenten zur Verfügung gestellt wird, oder einen Kontenplan
- händisch erstellen. Um auf die vorgefertigten Geschäftskontenpläne zuzugreifen,
- starten Sie <application>&app;</application> und
- klicken auf <menuchoice><guimenu>Datei</guimenu><guimenuitem>Neue Datei</guimenuitem></menuchoice> und
- fahren fort, bis Sie eine Liste der verfügbaren Kontenpläne sehen. Dort wählen Sie
- den gewünschten Kontenrahmen (z.B. SKR03 und SKR04)aus.</para>
-
- <para>Die vorgefertigte Geschäftskontenhierarchie wird nicht exakt Ihren Bedürfnissen
- entsprechen. Sie werden Anpassungen an der Kontenhierarchie durchführen, damit diese Ihre
- spezielle Situation wiedergibt. Sie sollten aber tauglich genug sein, um zu empfehlen,
- mit einem von Ihnen zu beginnen.</para>
-
- <para>Ddie Debitorenbuchhaltung bezieht sich auf Lieferungen oder Leistungen, die von
- Ihrem Unternehmen auf Kredit erbracht, aber noch nicht bezahlt wurden.
- Diese werden in der Bilanz als Aktiva ausgewiesen, weil die Erwartung besteht,
- dass demnächst eine Zahlung erfolgt. Um <application>&app;</application>’s integrierte Debitorenbuchhaltung
- zu nutzen, müssen Sie zuerst ein Konto einrichten (üblicherweise als Unterkonto
- unter Aktiva) mit dem Kontenart
- <emphasis>Offene Forderungen</emphasis>. Innerhalb dieses Kontos wird die integrierte
- Debitorenbuchhaltung Geschäftsvorfälle buchen.</para>
-
- <literallayout>
-Basis Hierarchie für Debitorenbuchhaltung:
-
--Aktiva
- -Bankkonto
- -Forderungen
--Einnahmen
- -Verkäufe
- </literallayout>
-
- <para>Sie benötigen zusätzlich folgende Konten in dieser Hierarchie: Aktivposten,
- Aufwendungen und Einnahmen. Die wesentlichen Gesichtspunkte dieser
- Hierarchie sind die Nutzung eines Einnahmekontos und des Forderungsaktivakontos
- mit der festgelegten Kontenart <emphasis>Offene Forderungen</emphasis>.</para>
-
- <note>
- <para>Sie brauchen keine individuellen Konten für Forderunen aus Lieferungen und Leistungen für jeden
- Kunden anzulegen. <application>&app;</application> behält den einzelnen Kunden intern im Auge und liefert
- einen Bericht für jeden Kunden auf der Grundlage der internen Verfolgung.</para>
- </note>
- </sect2>
+ <para>Durchführung der Einrichtung ist in <xref linkend="chapter_bus_setup" />
+ aufgeführt.
+ </para>
- <sect2 id="bus-ar-setupcname2">
- <title>Registrierung des Unternehmens</title>
-
- <para>Nachdem Sie die Kontenstruktur aufgebaut haben, registrieren Sie in <application>&app;</application>
- Ihr Unternehmen. Um Ihr Unternehmen zu registrieren, wählen Sie den <guilabel>Geschäft</guilabel>-Button
- in den <guilabel>Buch-Optionen</guilabel> Fenster, welches Sie ereichen unter
- <menuchoice><guimenu>Datei</guimenu><guimenuitem>Eigenschaften</guimenuitem></menuchoice>. Hier können Sie:</para>
-
- <itemizedlist>
- <listitem>
- <para>den Namen Ihres Unternehmens mit den Kontaktinformationen
- wie Telefon-, Faxnummern, E-Mail Adresse und URL der Webseite angeben.</para>
- </listitem>
-
- <listitem>
- <para>die Identifikationsnummer Ihres Unternehmens (z.b die UStID) im Feld
- <guilabel>Firmennummer</guilabel>.</para>
- </listitem>
-
- <listitem>
- <para>die Standardsteuertabellen für die üblichen Kunden und Lieferanten hinterlegen.</para>
- </listitem>
- </itemizedlist>
- </sect2>
</sect1>
+
<sect1 id="bus-ar-components1">
<title>Systemkomponenten</title>
@@ -447,7 +348,7 @@ Basis Hierarchie für Debitorenbuchhaltung:
</sect2>
<sect2 id="bus-ar-invoicestarting2">
- <title>Assign Starting Invoice Number</title>
+ <title>Erste Rechnungsnummer zuweisen</title>
<para>Standardmäßig startet <application>&app;</application> mit der Rechnungmmer 1 und zählt ab da hoch.
Sie können eine Rechnungsnummer jedesmal händisch in die Textbox eingeben, wenn Sie
diff --git a/guide/de/figures/bus_ar_jobnew.png b/guide/de/figures/bus_ar_jobnew.png
new file mode 100644
index 0000000..b99c7f1
Binary files /dev/null and b/guide/de/figures/bus_ar_jobnew.png differ
commit bb2edbe6c97fee161403b768f33ec9fb7ae2c9b3
Author: Mechtilde <ooo at mechtilde.de>
Date: Wed Dec 30 13:37:02 2015 +0100
finishing German translation of chapter bus_setup
diff --git a/guide/de/ch_bus_setup.xml b/guide/de/ch_bus_setup.xml
index ea13424..7cb1b83 100644
--- a/guide/de/ch_bus_setup.xml
+++ b/guide/de/ch_bus_setup.xml
@@ -18,7 +18,7 @@
und Kreditorenkonten für Unternehmen zu händeln, müssen diese
vorbreitende Schritte durchgeführt werden.
<itemizedlist>
- <listitem><para>Erstellen Sie eine sachgemäße Kontenhierarchiey.</para></listitem>
+ <listitem><para>Erstellen Sie eine sachgemäße Kontenhierarchie.</para></listitem>
<listitem><para>Richten Sie Steuertabellen ein.</para></listitem>
<listitem><para>Tragen Sie das Unternehmen in <application>&app;</application> ein.</para></listitem>
<listitem><para>Setzen Sie die geschäftlichen Eigenschaften.</para></listitem>
@@ -32,20 +32,20 @@
<para>Es gibt viele verschiedene Möglichkeiten, eine Geschäftskontenhierarchie
einzurichten. Sie können mit der Einrichtung der Geschäftskonten anfangen,
die mit dem Neuen Kontenplan erstellen Assistenten zur Verfügung
- gestellt wird, oder einen Kontenplan händisch erstellen. Um auf
+ gestellt werden oder einen Kontenplan händisch erstellen. Um auf
die vorgefertigten Geschäftskontenpläne zuzugreifen,
starten Sie <application>&app;</application> und
klicken auf <menuchoice><guimenu>Datei</guimenu><guimenuitem>Neue Datei
- </guimenuitem></menuchoice> fahren fort, bis Sie eine Liste der
+ </guimenuitem></menuchoice> und fahren fort, bis Sie eine Liste der
verfügbaren Kontenpläne sehen. Dort wählen Sie
- den gewünschten Kontenrahmen (z.B. SKR03 und SKR04)aus.</para>
+ den gewünschten Kontenrahmen (z.B. SKR03 und SKR04) aus.</para>
<para>Die vorgefertigte Geschäftskontenhierarchie wird nicht exakt Ihren Bedürfnissen
entsprechen. Sie werden Anpassungen an der Kontenhierarchie durchführen, damit diese Ihre
- spezielle Situation wiedergibt. Sie sollten aber tauglich genug sein, um zu empfehlen,
- mit einem von Ihnen zu beginnen.</para>
+ spezielle Situation wiedergibt. Sie sollte aber tauglich genug sein, um zu empfehlen,
+ damit zu beginnen.</para>
- <para>Um <application>&app;</application>’s integriertes Debitorenbuchhaltung
+ <para>Um <application>&app;</application>’s eingebaute Debitorenbuchhaltung
zu nutzen, müssen Sie zunächst ein Konto (üblicherweise als Unterkonto
unter Aktiva) mit der Kontenart <emphasis>Offene Forderungen</emphasis> einrichten.
Innerhalb dieses Kontos wird die integrierte Debitorenbuchhaltung Geschäftsvorfälle buchen.
@@ -189,44 +189,50 @@ Basis Kontenhierarchie für Debitoren- und Kreditorenbuchhaltung:
<itemizedlist>
<listitem>
- <para><guilabel>Name</guilabel> Dies ist der NAme der Steuertabelle.</para>
+ <para><guilabel>Name:</guilabel> Dies ist der Name der Steuertabelle.</para>
</listitem>
<listitem>
- <para><guilabel>Typ</guilabel> Entweder <guilabel>Prozent %</guilabel>
+ <para><guilabel>Typ:</guilabel> Entweder <guilabel>Prozent %</guilabel>
oder <guilabel>Wert €
</guilabel>.</para>
</listitem>
<listitem>
- <para><guilabel>Wert
+ <para><guilabel>Wert:
</guilabel>Dies ist der Prozentsatz oder der Wert abhängig vom <guilabel>Typ</guilabel>.</para>
</listitem>
<listitem>
- <para><guilabel>Konto</guilabel> Dies ist das Konto, aus welches die Steuer gebucht werden wird.
- For tax collected from customers, this should probably be a Liability account as it must be payed to the government.
- For tax paid to vendors, if tax laws allow tax paid to vendors to offset tax collected from customers, this should probably
- also be a Liability account (even though it will usually have a debit balance)
- so that the net tax owed to the government can be easily observed.
+ <para><guilabel>Konto:</guilabel> Dies ist das Konto, aus welches die Steuer gebucht werden wird.
+ Für Steuer, die von Kunden erhoben werden, sollte dies wohl ein Verbindlichkeitskonto sein, weil dies an die Steuerverwaltung bezahlt werden muss.
+ Für Steuer, die an Lieferanten gezahlt werden, sollte dies,
+ wenn die Steuergesetze Vorsteuerabzug ermöglichen, wohl auch
+ ein Verbindlichkeitskonto sein (auch wenn es üblicherweise einen
+ negativen Stand aufweist). So kann der Nettobetrag der Steuer,
+ die der Verwaltung geschuldet wird, einfach festgestellt werden,
</para>
- <para>If you set up Tax on Purchases and Tax on Sales as subaccounts of Liabilities:Tax then the net tax will be rolled up
- and can be seen in the <application>&app;</application> Accounts tab.
+ <para>Wenn Sie Umsatzsteuer und Vorsteuer als Unterkonten von
+ Verbindlichkeiten:Steuern einrichten, wird die Nettosteuer ständig
+ berechnet und erscheint im <application>&app;</application> Kontenreiter.
</para>
- <para><emphasis>If unsure about tax law requirements, get professional advise. </emphasis></para>
+ <para><emphasis>Wenn Sie unsicher sind wegen steuergesetzlicher
+ Anforderungen, holen Sie professionellen Rat ein! </emphasis></para>
</listitem>
</itemizedlist>
</sect1>
<sect1 id="bus-setupcname">
- <title>Company Registration</title>
-
- <para>After you have built the account structure and defined your tax tables, register the <application>&app;</application>
- file as belonging to your company. To register your company, select the <guilabel>Business</guilabel> tab
- in the <guilabel>Book Options</guilabel> window accessible by selecting
- <menuchoice><guimenu>File</guimenu><guimenuitem>Properties</guimenuitem>
- </menuchoice>.
+ <title>Unternehmensregistrierung</title>
+
+ <para>Nachdem Sie die Kontenstruktur erstellt und die Steuertabellen
+ eingerichtet haben, registrieren Sie die <application>&app;</application>
+ Datei als zum Unternehmen gehörig. Um Ihr Unternehmen zu registrieren,
+ wählen Sie den Reiter <guilabel>Geschäft</guilabel> in dem Fenster
+ <guilabel>Buch-Optionen</guilabel>, auf das Sie unter
+ <menuchoice><guimenu>Datei</guimenu><guimenuitem>Eigenschaften</guimenuitem>
+ </menuchoice> zugreifen können.
</para>
<figure pgwide="1">
- <title>Company Registration</title>
+ <title>Unternehmensregistrierung</title>
<screenshot id="bus-co-reg">
<mediaobject>
<imageobject role="html">
@@ -239,87 +245,104 @@ Basis Kontenhierarchie für Debitoren- und Kreditorenbuchhaltung:
</imageobject>
<textobject>
- <phrase>Company Registration</phrase>
+ <phrase>Unternehmensregistrierung</phrase>
</textobject>
</mediaobject>
</screenshot>
</figure>
- <para>Here you can:</para>
+ <para>Hier können Sie:</para>
<itemizedlist>
<listitem>
- <para>Enter the name of your company along with contact information
- such as your phone number, fax number, e-mail address and website
- URL.</para>
+ <para>Geben sie den Namen Ihres Unternehmens mit den Kontaktinformationen
+ wie Telefon-, Faxnummern, E-Mail Adresse und URL der Webseite ein.</para>
</listitem>
<listitem>
- <para>Enter your company’s tax payer id number in the
- <guilabel>Company ID</guilabel> field.</para>
+ <para>Geben Sie die Identifikationsnummer Ihres Unternehmens
+ (z.b die UStID) im Feld <guilabel>Firmennummer</guilabel> ein.</para>
</listitem>
<listitem>
- <para>Select default tax tables applicable to your most common
- customers and vendors.</para>
+ <para>Wählen Sie die Standardsteuertabellen für die üblichen
+ Kunden und Lieferanten aus.</para>
</listitem>
</itemizedlist>
</sect1>
<sect1 id="bus_setup_pref">
- <title>Business Preferences</title>
- <para>Set options on the Business tab of the <application>&app;</application> preferences, which is
- accessed via <menuchoice><guimenu>Edit</guimenu><guimenuitem>Preferences</guimenuitem></menuchoice>
- (<menuchoice><guimenu>GnuCash</guimenu><guimenuitem>Preferences</guimenuitem></menuchoice> on Mac OS X).
+ <title>Einstellungen für das Unternehmen</title>
+ <para>Stellen Sie die Optionen im Reiter Geschäft in den
+ <application>&app;</application> Einstellungen ein, auf welche Sie
+ unter <menuchoice><guimenu>Bearbeiten</guimenu><guimenuitem>Einstellungen</guimenuitem></menuchoice>
+ (<menuchoice><guimenu>GnuCash</guimenu><guimenuitem>Einstellungen</guimenuitem></menuchoice>
+ unter Mac OS X).
+ <!--
See Help manual chapter 10.3.3 Business Book Options Tab.
+ -->
</para>
</sect1>
<sect1 id="bus-setupterms">
- <title>Billing Terms</title>
+ <title>Zahlungsbedingung</title>
- <para>Billing Terms can be used to determine the payment due date and be a
- guide for determining discount for early payment of invoices (or vendor bills).
+ <para>Zahlungsbedingungen können genutzt werden, um das Zahlungsziel
+ festzulegen und um eine Richtschnur für die Festlegung des Skontos
+ bei vorzeitiger Zahlung der Ausgangsrechung (oder der Eingangsrechnung
+ des Lieferanten) zu sein.
</para>
<note>
- <para>As of <application>&app;</application> 2.6.7, Billing Terms are only
- partially supported. Date due is calculated using the Billing Terms
- but discount amount is not.
+ <para>Seit <application>&app;</application> Version 2.6.7, werden
+ Zahlungsbedingungen nur teilweise unterstützt. Das Fälligkeitsdatum
+ wird mit Hilfe der Zahlungsbedingungen berechnet, aber nicht der
+ Skontobetrag.
</para>
<para>
- Discount for early invoice payment is not implemented. There are 2 ways this may be done, although neither is recommended, and
- professional advise should be used to confirm that regulations are being complied with:
+ Der Skonto für vorzeitige Zahlung ist nicht umgesetzt. Es gibt Wege
+ wie dies getan werden kann. wenn auch keine davon empfohlen wird und
+ fragen Sie professionelle Berater um Rat, ob diese Bestimmungen
+ mit dem folgenden übereinstimmen:
<itemizedlist>
<listitem>
- <para>After creating and posting a payment which pays the invoice in full, manually edit the payment transaction (usually strongly discouraged)
- and split the payment to reduce it by the amount of the discount and a create a compensating split in an income (discount) account.
+ <para>Nach der Eingabe und der Buchung der Zahlung in voller
+ Höhe wird die Buchung der Zahlung manuell bearbeitet (gewöhnlich
+ dringend abgeraten) und die Zahlung gesplittet, um den Betrag
+ um den Skontobetrag zu reduzieren und eine ausgleichende Splitbuchung
+ auf einem Ertragskonto (Skonto) zu erstellen.
</para>
</listitem>
<listitem>
- <para>Alternatively, after creating and posting a payment for the discounted amount, create a credit note for the discount using a specific negative
- sales income (discount) account for the transfer account.
+ <para>Alternative erstellen Sie nach der Eingabe und der Buchung
+ der Zahlung für den Skontobetrag eine Gutschrift und nutzen ein
+ spezielles negatives Ertragskonto aus Verkäufen (Skonto) als
+ Transfer konto.
</para>
</listitem>
</itemizedlist>
</para>
</note>
- <para>You can specify the billing terms on each invoice/bill.
- Invoice billing terms will default from the customer billing terms.
- Bill billing terms will default from the vendor billing terms.
+ <para>Sie können die Zahlungsbedingungen für jede Eingangs-/Ausgangsrechnung
+ bestimmen. Die Zahlungsbedingungen der Ausgangsrechnung werden durch
+ die Kundenzahlungsbedingungen vorgegeben. Die Zahlungsbedingungen
+ der Eingangsrechnung verden durch die Lieferantenzahlungsbedingungen
+ vorgegeben.
</para>
- <para>Billing Terms are maintained using the Billing Terms Editor which is accessed via menu
- <menuchoice><guimenu>Business</guimenu><guimenuitem>Billing Terms Editor</guimenuitem></menuchoice>.
+ <para>Zahlungsbedingungen werden im Editor für die Zahlungsbedingungen
+ gepflegt, auf den Sie unter <menuchoice><guimenu>Geschäft</guimenu>
+ <guimenuitem>Zahlungsbedingungen…</guimenuitem></menuchoice>
+ zugreifen können.
</para>
<figure pgwide="1">
- <title>Billing Terms Editor</title>
+ <title>Zahlungsbedingungen-Editor</title>
<screenshot id="bus-termsmain">
<mediaobject>
<imageobject role="html">
@@ -332,7 +355,7 @@ Basis Kontenhierarchie für Debitoren- und Kreditorenbuchhaltung:
</imageobject>
<textobject>
- <phrase>Billing Terms Editor</phrase>
+ <phrase>Zahlungsbedingungen-Editor</phrase>
</textobject>
</mediaobject>
@@ -340,7 +363,7 @@ Basis Kontenhierarchie für Debitoren- und Kreditorenbuchhaltung:
</figure>
<figure pgwide="1">
- <title>New Billing Term</title>
+ <title>Neue Zahlungsbedingungen</title>
<screenshot id="bus-termsnew">
<mediaobject>
<imageobject role="html">
@@ -353,7 +376,7 @@ Basis Kontenhierarchie für Debitoren- und Kreditorenbuchhaltung:
</imageobject>
<textobject>
- <phrase>New Billing Term</phrase>
+ <phrase>Neue Zahlungsbedingungen</phrase>
</textobject>
</mediaobject>
@@ -362,48 +385,58 @@ Basis Kontenhierarchie für Debitoren- und Kreditorenbuchhaltung:
<itemizedlist>
<listitem>
- <para><guilabel>Name</guilabel> The internal name of the billing term. For some examples of billing term names and descriptions see
- <ulink url="http://wiki.gnucash.org/wiki/Terms" />.
+ <para><guilabel>Name:</guilabel> Der interne Name der Zahlungsbedingung.
+ Für einige Beispiele der Benennungen und Beschreibungen der
+ Zahlungsbedingungen schauen Sie unter <ulink url="http://wiki.gnucash.org/wiki/Terms" />.
</para>
</listitem>
<listitem>
- <para><guilabel>Description</guilabel> The description of the billing term, printed on invoices</para>
+ <para><guilabel>Beschreibung:</guilabel> Die Beschreibung der
+ Zahlungsbedingungen, wie Sie auf den Rechnungen gedruckt wird.</para>
</listitem>
<listitem>
- <para>There are 2 types of billing terms, with different information to be entered</para>
+ <para>Es gibt zwei Arten von Zahlungsbedingungen, für die verschiedenen
+ Informationen eingegeben werden.</para>
<itemizedlist>
<listitem>
- <para>Type Days</para>
+ <para>Art: Tage</para>
<itemizedlist>
<listitem>
- <para><guilabel>Due Days</guilabel> The invoice or bill is due to be paid within this number of days after the post date</para>
+ <para><guilabel>Fälligkeitsdatum:</guilabel> Die Ausgangs-
+ oder Eingangsrechnung ist zur Zahlung innerhalb der Anzahl
+ dieser Tage nach dem Zugangsdatum.</para>
</listitem>
<listitem>
- <para><guilabel>Discount Days</guilabel> The number of days after the post date during which a discount will
- be applied for early payment
+ <para><guilabel>Skontotag:</guilabel> Die Anzahl der Tage
+ nach dem Zugangsdatum während derer das Skonto für die
+ vorzeitige Zahlung angewendet wird.
</para>
</listitem>
<listitem>
- <para><guilabel>Discount %</guilabel> The percentage discount applied for early payment</para>
+ <para><guilabel>Skonto %:</guilabel> Der Skonto-Pozentsatz,
+ der für die vorzeitige Zahlung angewendet wird. </para>
</listitem>
</itemizedlist>
</listitem>
<listitem>
- <para>Type Proximo</para>
+ <para>Type: Im nächsten Monat</para>
<itemizedlist>
<listitem>
- <para><guilabel>Due Day</guilabel> The day of the month bills are due</para>
+ <para><guilabel>Fälligkeitsdatum </guilabel> Tag des Monats, an dem die Rechnung fällig wird.</para>
</listitem>
<listitem>
- <para><guilabel>Discount Day</guilabel> The last day of the month for the early payment discount</para>
+ <para><guilabel>Stichtag Skonto:</guilabel> Der letzte Tag des Monats für den Skonto für die vorzeitige Zahlung</para>
</listitem>
<listitem>
- <para><guilabel>Discount %</guilabel> The discount percentage applied if paid early</para>
+ <para><guilabel>Skonto %:</guilabel> Der Skonto-Pozentsatz,
+ der für die vorzeitige Zahlung angewendet wird.</para>
</listitem>
<listitem>
- <para><guilabel>Cutoff Day</guilabel> The cutoff day for applying bills to the next month. After the
- cutoff, bills are applied to the following month. Negative values
- count backwards from the end of the month.
+ <para><guilabel>Stichtag Monatswechsel</guilabel> Der
+ Stichtag Monatswechsel gilt für Eingangsrechnungen. Nach
+ dem Monatswechsel werden die Rechnungen im folgenden Monat
+ angewandt. Negative Werte werden vom Ende des Monats
+ rückwärts gezählt.
</para>
</listitem>
</itemizedlist>
diff --git a/guide/de/figures/bus_co_reg.png b/guide/de/figures/bus_co_reg.png
new file mode 100644
index 0000000..60c56b6
Binary files /dev/null and b/guide/de/figures/bus_co_reg.png differ
diff --git a/guide/de/figures/bus_terms_main.png b/guide/de/figures/bus_terms_main.png
new file mode 100644
index 0000000..c66d47d
Binary files /dev/null and b/guide/de/figures/bus_terms_main.png differ
diff --git a/guide/de/figures/bus_terms_new.png b/guide/de/figures/bus_terms_new.png
new file mode 100644
index 0000000..4e9ae3b
Binary files /dev/null and b/guide/de/figures/bus_terms_new.png differ
commit 19262a6cf0c32b29a0696b38e79b41b069a43a19
Author: Mechtilde <ooo at mechtilde.de>
Date: Tue Dec 29 21:20:44 2015 +0100
add the corresponding English screenshots
diff --git a/guide/de/figures/bus_tax_main.png b/guide/de/figures/bus_tax_main.png
new file mode 100644
index 0000000..077237e
Binary files /dev/null and b/guide/de/figures/bus_tax_main.png differ
diff --git a/guide/de/figures/bus_tax_new.png b/guide/de/figures/bus_tax_new.png
new file mode 100644
index 0000000..3683251
Binary files /dev/null and b/guide/de/figures/bus_tax_new.png differ
commit 6287001104e1adb0eb74c5c5959f8349726bdaa8
Author: Mechtilde <ooo at mechtilde.de>
Date: Tue Dec 29 21:17:30 2015 +0100
first part of German translation of chapter bus_setup
diff --git a/guide/de/ch_bus_intro.xml b/guide/de/ch_bus_intro.xml
index b9c9ca8..3e194a7 100644
--- a/guide/de/ch_bus_intro.xml
+++ b/guide/de/ch_bus_intro.xml
@@ -42,7 +42,7 @@
werden in erster Linie dafür genutzt, wenn Sie eine Menge Rechnungen
und lieferscheine haben, die ein und ausgehen, und Sie nicht den
Ãœberblick verlieren wollen, weil Sie nicht rechtzeitig zahlen oder
- bezahlt werden. Für die meisten For most Privatnutzer ist die Debitoren-
+ bezahlt werden. Für die meisten Privatnutzer ist die Debitoren-
und Kreditorenbuchhaltung zu schwierig, um der Mühe wert zu sein.
</para>
diff --git a/guide/de/ch_bus_setup.xml b/guide/de/ch_bus_setup.xml
index de895fd..ea13424 100644
--- a/guide/de/ch_bus_setup.xml
+++ b/guide/de/ch_bus_setup.xml
@@ -1,134 +1,152 @@
<!--
(Do not remove this comment block.)
Version: 1.0.0
- Last modified: Sep 19th 2015
+ Last modified: Sep 19th 2015 (Englisch 20.09.1015)
Maintainers:
Chris Good <chris.good at ozemail.com.au>
Author:
- Chris Good <chris.good at ozemail.com.au>
- updated [FirstName LastName] <name at company.com>
+ Chris Good <chris.good at ozemail.com.au>
+ updated [FirstName LastName] <name at company.com>
Translators:
- (translators put your name and email here)
+ (Mechtilde Stehmann <ooo at mechtilde.de)
-->
<chapter id="chapter_bus_setup">
- <title>Business Setup</title>
+ <title>Einrichtung der geschäftlichen Buchhaltung</title>
- <para>To set up <application>&app;</application> to handle accounts receivable or accounts payable
- for a company, these preliminary steps must be done.
+ <para>Um <application>&app;</application> so einzurichten, Debitoren-
+ und Kreditorenkonten für Unternehmen zu händeln, müssen diese
+ vorbreitende Schritte durchgeführt werden.
<itemizedlist>
- <listitem><para>Build an appropriate Account Hierarchy.</para></listitem>
- <listitem><para>Set up Tax Tables.</para></listitem>
- <listitem><para>Register the company in <application>&app;</application>.</para></listitem>
- <listitem><para>Set Business Preferences.</para></listitem>
- <listitem><para>Set up Billing Terms.</para></listitem>
+ <listitem><para>Erstellen Sie eine sachgemäße Kontenhierarchiey.</para></listitem>
+ <listitem><para>Richten Sie Steuertabellen ein.</para></listitem>
+ <listitem><para>Tragen Sie das Unternehmen in <application>&app;</application> ein.</para></listitem>
+ <listitem><para>Setzen Sie die geschäftlichen Eigenschaften.</para></listitem>
+ <listitem><para>Richten Sie Zahlungsbedingungen ein.</para></listitem>
</itemizedlist>
</para>
<sect1 id="bus-setupacct">
- <title>Account Setup</title>
-
- <para>There are many different ways to set up a business account
- hierarchy. You can start with the Business Accounts setup which is
- available from the New Account Hierarchy assistant, or you could build one
- manually. To access the prebuilt Business Accounts, start <application>&app;</application> and
- click on <menuchoice><guimenu>File</guimenu><guimenuitem>New File</guimenuitem></menuchoice> and
- proceed until you see the list of available accounts, select Business
- Accounts.</para>
-
- <para>The prebuilt Business Account hierarchy will not meet your needs
- exactly. You will need make adjustments for the hierarchy to function
- well with your particular situation. It should be close enough that it
- is recommended you begin with it.</para>
-
- <para>To use <application>&app;</application>’s integrated accounts
- receivable system, you must first set up an account (usually a
- sub-account under Assets) defined with account type
- <emphasis>A/Receivable</emphasis>. It is within this account that the
- integrated A/R system will place transactions.
+ <title>Konteneinrichtung</title>
+
+ <para>Es gibt viele verschiedene Möglichkeiten, eine Geschäftskontenhierarchie
+ einzurichten. Sie können mit der Einrichtung der Geschäftskonten anfangen,
+ die mit dem Neuen Kontenplan erstellen Assistenten zur Verfügung
+ gestellt wird, oder einen Kontenplan händisch erstellen. Um auf
+ die vorgefertigten Geschäftskontenpläne zuzugreifen,
+ starten Sie <application>&app;</application> und
+ klicken auf <menuchoice><guimenu>Datei</guimenu><guimenuitem>Neue Datei
+ </guimenuitem></menuchoice> fahren fort, bis Sie eine Liste der
+ verfügbaren Kontenpläne sehen. Dort wählen Sie
+ den gewünschten Kontenrahmen (z.B. SKR03 und SKR04)aus.</para>
+
+ <para>Die vorgefertigte Geschäftskontenhierarchie wird nicht exakt Ihren Bedürfnissen
+ entsprechen. Sie werden Anpassungen an der Kontenhierarchie durchführen, damit diese Ihre
+ spezielle Situation wiedergibt. Sie sollten aber tauglich genug sein, um zu empfehlen,
+ mit einem von Ihnen zu beginnen.</para>
+
+ <para>Um <application>&app;</application>’s integriertes Debitorenbuchhaltung
+ zu nutzen, müssen Sie zunächst ein Konto (üblicherweise als Unterkonto
+ unter Aktiva) mit der Kontenart <emphasis>Offene Forderungen</emphasis> einrichten.
+ Innerhalb dieses Kontos wird die integrierte Debitorenbuchhaltung Geschäftsvorfälle buchen.
</para>
- <para>To use <application>&app;</application>’s integrated accounts
- payable system, you must first set up an account (usually a
- sub-account under Liabilities) defined with account type
- <emphasis>A/Payable</emphasis>. It is within this account that the
- integrated A/P system will place transactions.
+ <para>Um <application>&app;</application>’s eingebaute
+ Kreditorenbuchhaltung nutzen zu können, müssen Sie zuerst, ein Konto
+ üblicherweise als Unterkonto unter Passiva mit
+ der Kontoart <emphasis>Offene Verbindlichkeiten</emphasis> einrichten.
+ Innerhalb dieses Kontos wird die integrierte
+ Kreditorenbuchhaltung Geschäftsvorfälle buchen.
</para>
<literallayout>
-Basic A/R and A/P Account Hierarchy:
-
--Assets
- -Accounts Receivable
- -Checking
--Expenses
- ...(as required)
--Income
- -Sales
--Liabilities
- -Accounts Payable
- -Tax
- -Tax on Purchases
- -Tax on Sales
+Basis Kontenhierarchie für Debitoren- und Kreditorenbuchhaltung:
+
+-Aktiva
+ -Forderungskonten
+ -Bankkonten
+-Aufwendungen
+ ...(nach Bedarf)
+-Erträge
+ -Verkäufe
+-Verbindlichkeiten
+ -Verbindlichkeiten aus Lieferungen und Leistungen
+ -Steuern
+ -Steuern auf Ankäufe (Vorsteuer)
+ -Steuern auf Verkäufe (Umsatzsteuer)
</literallayout>
- <para>You need to add additional accounts to this hierarchy for it to be useful.</para>
+ <para>Sie müssen zusätzliche Konten dieser Hierarchie hinzufügen,
+ um diese nutzbar zu machen.</para>
<note>
- <para>You do not need to create an individual A/R account for each
- customer. <application>&app;</application> keeps track of customers internally and provides
- per-customer reports based on the internal tracking. The same applies to A/P and vendors.
+ <para>Sie brauchen keine individuellen Konten für Forderungen aus
+ Lieferungen und Leistungen für jeden Kunden anzulegen.
+ <application>&app;</application> behält den einzelnen Kunden
+ intern im Auge und liefert einen Bericht für jeden Kunden auf der
+ Grundlage der internen Verfolgung. Das gleiche gilt für Verbindlichkeiten
+ aus Lieferungen und Leistungen und den Lieferanten.
</para>
<para>
- If you deal with customers in more than one currency you will need a separate
- <emphasis>Accounts Receivable</emphasis> account for each currency.
+ Wenn Sie mit den Kunden in mehr als einer Währung zu tun haben,
+ benötigen Sie für jede Währung ein eigenes Konto
+ <emphasis>Offene Forderung</emphasis>.
</para>
<para>
- If you deal with vendors in more than one currency you will need a separate
- <emphasis>Accounts Payable</emphasis> account for each currency.
+ Wenn Sie mit den Lieferanten in mehr als einer Währung zu tun haben,
+ benötigen Sie für jede Währung ein eigenes Konto
+ <emphasis>Verbindlichkeiten aus Lieferungen und Leistungen</emphasis>.
</para>
- <para>Transactions involving an Accounts Receivable or Accounts Payable account should not be
- added, changed or deleted in any way other than by using
+ <para>Buchungen, an denen die Konten Offene Forderungen oder Verbindlichkeiten
+ beteiligt sind, sollten nicht in irgendeiner anderen Art und Weise hinzugefügt,
+ geändert oder gelöscht werden als unter Nutzung von:
<itemizedlist>
- <listitem><para>post/unpost bill/invoice/voucher or</para></listitem>
- <listitem><para>process payment</para></listitem>
- </itemizedlist>
- </para>
+ <listitem><para>einbuchen/ausbuchen der Eingangs-/Ausgangsrechnung/Gutschrift oder</para></listitem>
+ <listitem><para>Zahlungsvorganges</para></listitem>
+ </itemizedlist>
+ </para>
</note>
</sect1>
<sect1 id="bus-setuptaxtables">
- <title>Tax Tables</title>
+ <title>Steuertabellen</title>
- <para>Tax Tables can used to determine the tax for customer invoices (or vendor bills).
+ <para>Steuertabellen können genutzt werden, um die Steuer für die
+ Ausgangsrechnung an den Kunden (oder die Eingangsrechnung des Lieferanten)
+ zu ermiiteln.
</para>
- <para> A tax table can be assigned to an invoice line or bill line.</para>
+ <para> Eine Steuertabelle can an die Zeile Ausgangsrechnung oder Eingangsrechnung
+ zugewiesen werden.</para>
- <para>Set up distinct tax tables for customers and vendors.</para>
+ <para>Erstellen Sie eine individuelle Steuertabelle für Kunden und
+ Lieferanten.</para>
- <para> The default invoice line tax table can be assigned to each customer and the default bill
- line tax table can be assigned to each vendor.
+ <para>Die Standardausgangsrechnung-Steuertabelle kann jedem Kunden
+ und die Standardeingangsrechnung-Steuertabelle jedem Lieferanten
+ zugewiesen werden..
</para>
- <para>The default tax table for new customers or new vendors can be specified in the <emphasis>Book Options </emphasis>
- window which can be accessed by
- <menuchoice><guimenu>File</guimenu>
- <guisubmenu>Properties</guisubmenu>
- <guimenuitem>Business tab.</guimenuitem>
- </menuchoice>
+ <para>Die Standardsteuertabelle für neue Kunden der neuen Lieferanten
+ kann in dem Fenster <emphasis>Buch-Optionen </emphasis> bestimmt werden,
+ auf dass Sie unter <menuchoice><guimenu>Datei</guimenu>
+ <guisubmenu>Eigenschaften</guisubmenu>
+ <guimenuitem>Reiter Geschäft</guimenuitem>
+ </menuchoice> zugreifen können
</para>
- <para>Tax Tables are maintained using the <emphasis>Sales Tax Table</emphasis> editor which is accessed via menu
- <menuchoice><guimenu>Business</guimenu><guimenuitem>Sales Tax Table</guimenuitem></menuchoice>.
+ <para>Steuertabellen werden durch Nutzung des Editors
+ <emphasis>Steuertabellen</emphasis> genutzt, auf den Sie im Menü unter
+ <menuchoice><guimenu>Geschäft</guimenu><guimenuitem>Steuertabellen
+ </guimenuitem></menuchoice> zugreifen können.
</para>
<figure pgwide="1">
- <title>Tax Tables</title>
+ <title>Steuertabellen</title>
<screenshot id="bus-taxmain">
<mediaobject>
<imageobject role="html">
@@ -141,7 +159,7 @@ Basic A/R and A/P Account Hierarchy:
</imageobject>
<textobject>
- <phrase>Sales Tax Tables Editor</phrase>
+ <phrase>Editor SteuertabellenSales Tax Tables Editor</phrase>
</textobject>
</mediaobject>
@@ -149,7 +167,7 @@ Basic A/R and A/P Account Hierarchy:
</figure>
<figure pgwide="1">
- <title>New Sales Tax Table</title>
+ <title>Neue Steuertabellen</title>
<screenshot id="bus-taxnew">
<mediaobject>
<imageobject role="html">
@@ -162,7 +180,7 @@ Basic A/R and A/P Account Hierarchy:
</imageobject>
<textobject>
- <phrase>New Sales Tax Table</phrase>
+ <phrase>Neue Steuertabellen</phrase>
</textobject>
</mediaobject>
@@ -171,19 +189,19 @@ Basic A/R and A/P Account Hierarchy:
<itemizedlist>
<listitem>
- <para><guilabel>Name</guilabel> This is the tax table name.</para>
+ <para><guilabel>Name</guilabel> Dies ist der NAme der Steuertabelle.</para>
</listitem>
<listitem>
- <para><guilabel>Type</guilabel> Either <guilabel>Percent %</guilabel>
- or <guilabel>Value $
+ <para><guilabel>Typ</guilabel> Entweder <guilabel>Prozent %</guilabel>
+ oder <guilabel>Wert €
</guilabel>.</para>
</listitem>
<listitem>
- <para><guilabel>Value
-</guilabel>This is the percentage or value depending on <guilabel>Type</guilabel>.</para>
+ <para><guilabel>Wert
+</guilabel>Dies ist der Prozentsatz oder der Wert abhängig vom <guilabel>Typ</guilabel>.</para>
</listitem>
<listitem>
- <para><guilabel>Account</guilabel> This is the account to which tax will be posted.
+ <para><guilabel>Konto</guilabel> Dies ist das Konto, aus welches die Steuer gebucht werden wird.
For tax collected from customers, this should probably be a Liability account as it must be payed to the government.
For tax paid to vendors, if tax laws allow tax paid to vendors to offset tax collected from customers, this should probably
also be a Liability account (even though it will usually have a debit balance)
commit 1cc18dbd66d2d339d688d411de3ae3b671dbb6c0
Author: Mechtilde <ooo at mechtilde.de>
Date: Mon Dec 21 16:32:38 2015 +0100
adapt Makefile.am and gnucash-guide.xml to chapter ch_bus_setup
diff --git a/guide/de/Makefile.am b/guide/de/Makefile.am
index 9088155..9eff599 100644
--- a/guide/de/Makefile.am
+++ b/guide/de/Makefile.am
@@ -8,6 +8,7 @@ entities = \
ch_bus_ap.xml \
ch_bus_ar.xml \
ch_bus_intro.xml \
+ ch_bus_setup.xml \
ch_capgain.xml \
ch_cbook.xml \
ch_cc.xml \
diff --git a/guide/de/gnucash-guide.xml b/guide/de/gnucash-guide.xml
index 2ce1e97..6a02ba0 100644
--- a/guide/de/gnucash-guide.xml
+++ b/guide/de/gnucash-guide.xml
@@ -20,11 +20,10 @@
<!ENTITY chapter9 SYSTEM "ch_capgain.xml">
<!ENTITY chapter10 SYSTEM "ch_currency.xml">
<!ENTITY chapter11 SYSTEM "ch_bus_intro.xml">
-<!--
-<!ENTITY chapter12 SYSTEM "ch_bus_setup.xml">-->
+<!ENTITY chapter12 SYSTEM "ch_bus_setup.xml">
<!ENTITY chapter13 SYSTEM "ch_bus_ar.xml">
<!ENTITY chapter14 SYSTEM "ch_bus_ap.xml">
- <!--
+<!--
<!ENTITY chapter15 SYSTEM "ch_bus_pay.xml">
<!ENTITY chapter16 SYSTEM "ch_budgets.xml"> -->
<!ENTITY chapter17 SYSTEM "ch_oth_assets.xml">
@@ -519,12 +518,12 @@
<title>Geschäftliche Finanzen handhaben</title>
&chapter11;
-
&chapter12;
&chapter13;
&chapter14;
<!--
&chapter15;
+
&chapter16;-->
&chapter17;
<!--
commit 63bf83371b64a2637169c759fa36b82d2ab35301
Author: Mechtilde <ooo at mechtilde.de>
Date: Sun Dec 13 18:28:14 2015 +0100
initial commit for German translation of chapter bus_setup
diff --git a/guide/de/ch_bus_setup.xml b/guide/de/ch_bus_setup.xml
new file mode 100644
index 0000000..de895fd
--- /dev/null
+++ b/guide/de/ch_bus_setup.xml
@@ -0,0 +1,398 @@
+<!--
+ (Do not remove this comment block.)
+ Version: 1.0.0
+ Last modified: Sep 19th 2015
+ Maintainers:
+ Chris Good <chris.good at ozemail.com.au>
+ Author:
+ Chris Good <chris.good at ozemail.com.au>
+ updated [FirstName LastName] <name at company.com>
+ Translators:
+ (translators put your name and email here)
+-->
+
+<chapter id="chapter_bus_setup">
+ <title>Business Setup</title>
+
+ <para>To set up <application>&app;</application> to handle accounts receivable or accounts payable
+ for a company, these preliminary steps must be done.
+ <itemizedlist>
+ <listitem><para>Build an appropriate Account Hierarchy.</para></listitem>
+ <listitem><para>Set up Tax Tables.</para></listitem>
+ <listitem><para>Register the company in <application>&app;</application>.</para></listitem>
+ <listitem><para>Set Business Preferences.</para></listitem>
+ <listitem><para>Set up Billing Terms.</para></listitem>
+ </itemizedlist>
+ </para>
+
+ <sect1 id="bus-setupacct">
+ <title>Account Setup</title>
+
+ <para>There are many different ways to set up a business account
+ hierarchy. You can start with the Business Accounts setup which is
+ available from the New Account Hierarchy assistant, or you could build one
+ manually. To access the prebuilt Business Accounts, start <application>&app;</application> and
+ click on <menuchoice><guimenu>File</guimenu><guimenuitem>New File</guimenuitem></menuchoice> and
+ proceed until you see the list of available accounts, select Business
+ Accounts.</para>
+
+ <para>The prebuilt Business Account hierarchy will not meet your needs
+ exactly. You will need make adjustments for the hierarchy to function
+ well with your particular situation. It should be close enough that it
+ is recommended you begin with it.</para>
+
+ <para>To use <application>&app;</application>’s integrated accounts
+ receivable system, you must first set up an account (usually a
+ sub-account under Assets) defined with account type
+ <emphasis>A/Receivable</emphasis>. It is within this account that the
+ integrated A/R system will place transactions.
+ </para>
+
+ <para>To use <application>&app;</application>’s integrated accounts
+ payable system, you must first set up an account (usually a
+ sub-account under Liabilities) defined with account type
+ <emphasis>A/Payable</emphasis>. It is within this account that the
+ integrated A/P system will place transactions.
+ </para>
+
+ <literallayout>
+Basic A/R and A/P Account Hierarchy:
+
+-Assets
+ -Accounts Receivable
+ -Checking
+-Expenses
+ ...(as required)
+-Income
+ -Sales
+-Liabilities
+ -Accounts Payable
+ -Tax
+ -Tax on Purchases
+ -Tax on Sales
+ </literallayout>
+
+ <para>You need to add additional accounts to this hierarchy for it to be useful.</para>
+
+ <note>
+ <para>You do not need to create an individual A/R account for each
+ customer. <application>&app;</application> keeps track of customers internally and provides
+ per-customer reports based on the internal tracking. The same applies to A/P and vendors.
+ </para>
+
+ <para>
+ If you deal with customers in more than one currency you will need a separate
+ <emphasis>Accounts Receivable</emphasis> account for each currency.
+ </para>
+
+ <para>
+ If you deal with vendors in more than one currency you will need a separate
+ <emphasis>Accounts Payable</emphasis> account for each currency.
+ </para>
+
+ <para>Transactions involving an Accounts Receivable or Accounts Payable account should not be
+ added, changed or deleted in any way other than by using
+ <itemizedlist>
+ <listitem><para>post/unpost bill/invoice/voucher or</para></listitem>
+ <listitem><para>process payment</para></listitem>
+ </itemizedlist>
+ </para>
+
+ </note>
+ </sect1>
+
+ <sect1 id="bus-setuptaxtables">
+ <title>Tax Tables</title>
+
+ <para>Tax Tables can used to determine the tax for customer invoices (or vendor bills).
+ </para>
+
+ <para> A tax table can be assigned to an invoice line or bill line.</para>
+
+ <para>Set up distinct tax tables for customers and vendors.</para>
+
+ <para> The default invoice line tax table can be assigned to each customer and the default bill
+ line tax table can be assigned to each vendor.
+ </para>
+
+ <para>The default tax table for new customers or new vendors can be specified in the <emphasis>Book Options </emphasis>
+ window which can be accessed by
+ <menuchoice><guimenu>File</guimenu>
+ <guisubmenu>Properties</guisubmenu>
+ <guimenuitem>Business tab.</guimenuitem>
+ </menuchoice>
+ </para>
+
+ <para>Tax Tables are maintained using the <emphasis>Sales Tax Table</emphasis> editor which is accessed via menu
+ <menuchoice><guimenu>Business</guimenu><guimenuitem>Sales Tax Table</guimenuitem></menuchoice>.
+ </para>
+
+ <figure pgwide="1">
+ <title>Tax Tables</title>
+ <screenshot id="bus-taxmain">
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="figures/bus_tax_main.png" format="PNG"
+ srccredit="Chris Good" width="510px" />
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="figures/bus_tax_main.png" format="PNG"
+ srccredit="Chris Good" />
+ </imageobject>
+
+ <textobject>
+ <phrase>Sales Tax Tables Editor</phrase>
+ </textobject>
+
+ </mediaobject>
+ </screenshot>
+ </figure>
+
+ <figure pgwide="1">
+ <title>New Sales Tax Table</title>
+ <screenshot id="bus-taxnew">
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="figures/bus_tax_new.png" format="PNG"
+ srccredit="Chris Good" />
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="figures/bus_tax_new.png" format="PNG"
+ srccredit="Chris Good" />
+ </imageobject>
+
+ <textobject>
+ <phrase>New Sales Tax Table</phrase>
+ </textobject>
+
+ </mediaobject>
+ </screenshot>
+ </figure>
+
+ <itemizedlist>
+ <listitem>
+ <para><guilabel>Name</guilabel> This is the tax table name.</para>
+ </listitem>
+ <listitem>
+ <para><guilabel>Type</guilabel> Either <guilabel>Percent %</guilabel>
+ or <guilabel>Value $
+</guilabel>.</para>
+ </listitem>
+ <listitem>
+ <para><guilabel>Value
+</guilabel>This is the percentage or value depending on <guilabel>Type</guilabel>.</para>
+ </listitem>
+ <listitem>
+ <para><guilabel>Account</guilabel> This is the account to which tax will be posted.
+ For tax collected from customers, this should probably be a Liability account as it must be payed to the government.
+ For tax paid to vendors, if tax laws allow tax paid to vendors to offset tax collected from customers, this should probably
+ also be a Liability account (even though it will usually have a debit balance)
+ so that the net tax owed to the government can be easily observed.
+ </para>
+ <para>If you set up Tax on Purchases and Tax on Sales as subaccounts of Liabilities:Tax then the net tax will be rolled up
+ and can be seen in the <application>&app;</application> Accounts tab.
+ </para>
+ <para><emphasis>If unsure about tax law requirements, get professional advise. </emphasis></para>
+ </listitem>
+ </itemizedlist>
+ </sect1>
+
+ <sect1 id="bus-setupcname">
+ <title>Company Registration</title>
+
+ <para>After you have built the account structure and defined your tax tables, register the <application>&app;</application>
+ file as belonging to your company. To register your company, select the <guilabel>Business</guilabel> tab
+ in the <guilabel>Book Options</guilabel> window accessible by selecting
+ <menuchoice><guimenu>File</guimenu><guimenuitem>Properties</guimenuitem>
+ </menuchoice>.
+ </para>
+
+ <figure pgwide="1">
+ <title>Company Registration</title>
+ <screenshot id="bus-co-reg">
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="figures/bus_co_reg.png" format="PNG"
+ srccredit="Chris Good" width="510px" />
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="figures/bus_co_reg.png" format="PNG"
+ srccredit="Chris Good" />
+ </imageobject>
+
+ <textobject>
+ <phrase>Company Registration</phrase>
+ </textobject>
+
+ </mediaobject>
+ </screenshot>
+ </figure>
+
+ <para>Here you can:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>Enter the name of your company along with contact information
+ such as your phone number, fax number, e-mail address and website
+ URL.</para>
+ </listitem>
+
+ <listitem>
+ <para>Enter your company’s tax payer id number in the
+ <guilabel>Company ID</guilabel> field.</para>
+ </listitem>
+
+ <listitem>
+ <para>Select default tax tables applicable to your most common
+ customers and vendors.</para>
+ </listitem>
+ </itemizedlist>
+
+ </sect1>
+
+ <sect1 id="bus_setup_pref">
+ <title>Business Preferences</title>
+ <para>Set options on the Business tab of the <application>&app;</application> preferences, which is
+ accessed via <menuchoice><guimenu>Edit</guimenu><guimenuitem>Preferences</guimenuitem></menuchoice>
+ (<menuchoice><guimenu>GnuCash</guimenu><guimenuitem>Preferences</guimenuitem></menuchoice> on Mac OS X).
+ See Help manual chapter 10.3.3 Business Book Options Tab.
+ </para>
+
+ </sect1>
+
+ <sect1 id="bus-setupterms">
+ <title>Billing Terms</title>
+
+ <para>Billing Terms can be used to determine the payment due date and be a
+ guide for determining discount for early payment of invoices (or vendor bills).
+ </para>
+
+ <note>
+ <para>As of <application>&app;</application> 2.6.7, Billing Terms are only
+ partially supported. Date due is calculated using the Billing Terms
+ but discount amount is not.
+ </para>
+ <para>
+ Discount for early invoice payment is not implemented. There are 2 ways this may be done, although neither is recommended, and
+ professional advise should be used to confirm that regulations are being complied with:
+ <itemizedlist>
+ <listitem>
+ <para>After creating and posting a payment which pays the invoice in full, manually edit the payment transaction (usually strongly discouraged)
+ and split the payment to reduce it by the amount of the discount and a create a compensating split in an income (discount) account.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>Alternatively, after creating and posting a payment for the discounted amount, create a credit note for the discount using a specific negative
+ sales income (discount) account for the transfer account.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </note>
+
+ <para>You can specify the billing terms on each invoice/bill.
+ Invoice billing terms will default from the customer billing terms.
+ Bill billing terms will default from the vendor billing terms.
+ </para>
+
+ <para>Billing Terms are maintained using the Billing Terms Editor which is accessed via menu
+ <menuchoice><guimenu>Business</guimenu><guimenuitem>Billing Terms Editor</guimenuitem></menuchoice>.
+ </para>
+
+ <figure pgwide="1">
+ <title>Billing Terms Editor</title>
+ <screenshot id="bus-termsmain">
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="figures/bus_terms_main.png" format="PNG"
+ srccredit="Chris Good" width="510px" />
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="figures/bus_terms_main.png" format="PNG"
+ srccredit="Chris Good" />
+ </imageobject>
+
+ <textobject>
+ <phrase>Billing Terms Editor</phrase>
+ </textobject>
+
+ </mediaobject>
+ </screenshot>
+ </figure>
+
+ <figure pgwide="1">
+ <title>New Billing Term</title>
+ <screenshot id="bus-termsnew">
+ <mediaobject>
+ <imageobject role="html">
+ <imagedata fileref="figures/bus_terms_new.png" format="PNG"
+ srccredit="Chris Good" />
+ </imageobject>
+ <imageobject role="fo">
+ <imagedata fileref="figures/bus_terms_new.png" format="PNG"
+ srccredit="Chris Good" />
+ </imageobject>
+
+ <textobject>
+ <phrase>New Billing Term</phrase>
+ </textobject>
+
+ </mediaobject>
+ </screenshot>
+ </figure>
+
+ <itemizedlist>
+ <listitem>
+ <para><guilabel>Name</guilabel> The internal name of the billing term. For some examples of billing term names and descriptions see
+ <ulink url="http://wiki.gnucash.org/wiki/Terms" />.
+ </para>
+ </listitem>
+ <listitem>
+ <para><guilabel>Description</guilabel> The description of the billing term, printed on invoices</para>
+ </listitem>
+ <listitem>
+ <para>There are 2 types of billing terms, with different information to be entered</para>
+ <itemizedlist>
+ <listitem>
+ <para>Type Days</para>
+ <itemizedlist>
+ <listitem>
+ <para><guilabel>Due Days</guilabel> The invoice or bill is due to be paid within this number of days after the post date</para>
+ </listitem>
+ <listitem>
+ <para><guilabel>Discount Days</guilabel> The number of days after the post date during which a discount will
+ be applied for early payment
+ </para>
+ </listitem>
+ <listitem>
+ <para><guilabel>Discount %</guilabel> The percentage discount applied for early payment</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ <listitem>
+ <para>Type Proximo</para>
+ <itemizedlist>
+ <listitem>
+ <para><guilabel>Due Day</guilabel> The day of the month bills are due</para>
+ </listitem>
+ <listitem>
+ <para><guilabel>Discount Day</guilabel> The last day of the month for the early payment discount</para>
+ </listitem>
+ <listitem>
+ <para><guilabel>Discount %</guilabel> The discount percentage applied if paid early</para>
+ </listitem>
+ <listitem>
+ <para><guilabel>Cutoff Day</guilabel> The cutoff day for applying bills to the next month. After the
+ cutoff, bills are applied to the following month. Negative values
+ count backwards from the end of the month.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </itemizedlist>
+ </sect1>
+
+</chapter>
diff --git a/guide/de/gnucash-guide.xml b/guide/de/gnucash-guide.xml
index 2793e90..2ce1e97 100644
--- a/guide/de/gnucash-guide.xml
+++ b/guide/de/gnucash-guide.xml
@@ -519,8 +519,8 @@
<title>Geschäftliche Finanzen handhaben</title>
&chapter11;
-<!--
-&chapter12; -->
+
+&chapter12;
&chapter13;
&chapter14;
<!--
Summary of changes:
.gitignore | 4 +
guide/C/ch_basics.xml | 2 +-
guide/de/Makefile.am | 11 +
guide/{C => de}/appendixa.xml | 4 +-
guide/{C => de}/appendixb.xml | 3 +
guide/{C => de}/appendixc.xml | 3 +
guide/{C => de}/appendixd.xml | 3 +
guide/de/ch_basics.xml | 6 +-
guide/{C => de}/ch_budgets.xml | 5 +-
guide/de/ch_bus_ap.xml | 86 +-----
guide/de/ch_bus_ar.xml | 117 +-------
guide/de/ch_bus_intro.xml | 2 +-
guide/{C => de}/ch_bus_pay.xml | 4 +-
guide/de/ch_bus_setup.xml | 449 ++++++++++++++++++++++++++++
guide/{C => de}/ch_dep.xml | 4 +-
guide/{C => de}/ch_import_business_data.xml | 5 +-
guide/de/ch_oth_assets.xml | 444 ++++++++++++++++++++++++++-
guide/{C => de}/ch_python_bindings.xml | 3 +
guide/{C => de}/fdl-appendix.xml | 0
guide/{C => de}/figures/bus_ar_jobnew.png | Bin
guide/{C => de}/figures/bus_co_reg.png | Bin
guide/{C => de}/figures/bus_tax_main.png | Bin
guide/{C => de}/figures/bus_tax_new.png | Bin
guide/{C => de}/figures/bus_terms_main.png | Bin
guide/{C => de}/figures/bus_terms_new.png | Bin
guide/{C => de}/figures/dep_assetmain.png | Bin
guide/{C => de}/figures/dep_assetreg.png | Bin
guide/{C => de}/figures/dep_example.png | Bin
guide/de/gnucash-guide.xml | 27 +-
29 files changed, 970 insertions(+), 212 deletions(-)
copy guide/{C => de}/appendixa.xml (99%)
copy guide/{C => de}/appendixb.xml (99%)
copy guide/{C => de}/appendixc.xml (99%)
copy guide/{C => de}/appendixd.xml (99%)
copy guide/{C => de}/ch_budgets.xml (98%)
copy guide/{C => de}/ch_bus_pay.xml (99%)
create mode 100644 guide/de/ch_bus_setup.xml
copy guide/{C => de}/ch_dep.xml (99%)
copy guide/{C => de}/ch_import_business_data.xml (99%)
copy guide/{C => de}/ch_python_bindings.xml (97%)
copy guide/{C => de}/fdl-appendix.xml (100%)
copy guide/{C => de}/figures/bus_ar_jobnew.png (100%)
copy guide/{C => de}/figures/bus_co_reg.png (100%)
copy guide/{C => de}/figures/bus_tax_main.png (100%)
copy guide/{C => de}/figures/bus_tax_new.png (100%)
copy guide/{C => de}/figures/bus_terms_main.png (100%)
copy guide/{C => de}/figures/bus_terms_new.png (100%)
copy guide/{C => de}/figures/dep_assetmain.png (100%)
copy guide/{C => de}/figures/dep_assetreg.png (100%)
copy guide/{C => de}/figures/dep_example.png (100%)
More information about the gnucash-changes
mailing list