Difference between revisions of "Account Hierarchy Template"
(Creating localized Account Hierarchy Templates) |
m (→Motivation: typo) |
||
Line 3: | Line 3: | ||
== Motivation == | == Motivation == | ||
− | Sometimes the standard GnuCash account hierarchy template needs a bigger rework before it fits the requirements of your | + | Sometimes the standard GnuCash account hierarchy template needs a bigger rework before it fits the requirements of your government - special for business purposes. In this case it might be better, to start from scratch. |
== An almost normal Start == | == An almost normal Start == |
Revision as of 21:25, 2 February 2009
Contents
Creating localized Account Hierarchy Templates
Motivation
Sometimes the standard GnuCash account hierarchy template needs a bigger rework before it fits the requirements of your government - special for business purposes. In this case it might be better, to start from scratch.
An almost normal Start
Start with an new empty file. Create the account hierarchy, which according your needs.
FIXME: I am quite not shure, if save file or export hierarchy is the better choice now. One obvisious difference: export saves no transactions, but also other parts will be ignored. E.g. what will happen with taxtables?
Changing the Header
After you saved your template, you must manually adjust the header of your new created file, otherwise the druid does not know, how to handle your template.
<?xml version="1.0" encoding="utf-8" ?> <gnc-account-example xmlns="http://www.gnucash.org/XML/" xmlns:act="http://www.gnucash.org/XML/act" xmlns:addr="http://www.gnucash.org/XML/addr" xmlns:bgt="http://www.gnucash.org/XML/bgt" xmlns:billterm="http://www.gnucash.org/XML/billterm" xmlns:book="http://www.gnucash.org/XML/book" xmlns:bt-days="http://www.gnucash.org/XML/bt-days" xmlns:bt-prox="http://www.gnucash.org/XML/bt-prox" xmlns:cd="http://www.gnucash.org/XML/cd" xmlns:cmdty="http://www.gnucash.org/XML/cmdty" xmlns:cust="http://www.gnucash.org/XML/cust" xmlns:employee="http://www.gnucash.org/XML/employee" xmlns:entry="http://www.gnucash.org/XML/entry" xmlns:fs="http://www.gnucash.org/XML/fs" xmlns:gnc="http://www.gnucash.org/XML/gnc" xmlns:invoice="http://www.gnucash.org/XML/invoice" xmlns:job="http://www.gnucash.org/XML/job" xmlns:lot="http://www.gnucash.org/XML/lot" xmlns:order="http://www.gnucash.org/XML/order" xmlns:owner="http://www.gnucash.org/XML/owner" xmlns:price="http://www.gnucash.org/XML/price" xmlns:recurrence="http://www.gnucash.org/XML/recurrence" xmlns:slot="http://www.gnucash.org/XML/slot" xmlns:split="http://www.gnucash.org/XML/split" xmlns:sx="http://www.gnucash.org/XML/sx" xmlns:taxtable="http://www.gnucash.org/XML/taxtable" xmlns:trn="http://www.gnucash.org/XML/trn" xmlns:ts="http://www.gnucash.org/XML/ts" xmlns:tte="http://www.gnucash.org/XML/tte" xmlns:vendor="http://www.gnucash.org/XML/vendor"> <gnc-act:title> IGAS-2099 </gnc-act:title> <gnc-act:short-description> Inter Galactical Accounting Standard, Stardate 2099 </gnc-act:short-description> <gnc-act:long-description> This is the Base Module of the Inter Galactical Accounting Standard as transmitted on stardate 2099-01-01. You might also need the module "starfleet" or "klingon". ~Cpt. Picard </gnc-act:long-description> <gnc-act:exclude-from-select-all>1</gnc-act:exclude-from-select-all> <gnc:account version="2.0.0"> <act:name>Root Account</act:name> <act:id type="new">e24772da4864456b196be5a6301c6756</act:id> <act:type>ROOT</act:type> <act:commodity-scu>0</act:commodity-scu> </gnc:account>
Annotations:
- Line 1: encoding
- You must save your file in the appropriate encoding.
- Line 2ff: Namespace
- The parser in GC 2.2.x makes no use of it, but future versions might change.
- Some details can be found in [1] or in the source docs
- gnc-act:title
- Enter a short, unique Name, which is usually also part of his filename,
- gnc-act:short-description
- A one line description shown in the selection box
- gnc-act:long-description
- Everything, the user should know about the template.
- gnc-act:exclude-from-select-all
- As your template should usually not be mixed with the private oriented templates, set this flag.
- Root Account
- Only the base module should have exactly one.
- The accounts in the optional modules linked over <act:parent type="guid">...</act:parent>
If you decide, to copy&paste this template, please replace the root guid by a self generated.