|
These functions are accessed via the admin.pl script in the installed directory of LedgerSMB.
LedgerSMB stores its information in locale-specific data sets. When a dataset is created, it sets various defaults such as currency, a basic chart of accounts setup, and so forth. Note that the default setup is for Canada, where the author of the software resides.
Datasets are stored as PostgreSQL databases. The application is designed with the idea that each dataset will represent exactly one company. If a customer is working with multiple companies, he/she must create a dataset to for each.
When creating a dataset, the application asks for both a username and a superusername. If the superuser’s information is not filled in, LedgerSMB will attempt to populate an existing dataset, but if this information is filled in, the program will log into the PostgreSQL cluster with the superusername and password, create the database, and attempt to add Plpgsql to it.
Users are created by going to the admin.pl page and clicking on "Add User." One then fills out the form and when it is saved, the user is created.
The permissions system is not rigorously enforced within LedgerSMB, in the sense that the permissions API is generally not used in the application itself. Instead permissions are used to enable/disable menu options. Setting an enforcement of such permissions would require some custom programming at the present time. Most organizations, however, find that the current system is adequate.
The checkboxes which are marked enable menu entries. Those that are unchecked disable those entries on the menu.
The Chart of Accounts provides a basic overview of the logical structure of the accounting program. One can customize this chart to allow for tracking of different sorts of information.
In order to set up your chart of accounts in LedgerSMB you will need to understand a bit about double entry bookkeeping. This section provides a brief overview of the essential concepts. There is a list of references for further reading at the end.
You don’t want to mix your personal expenses and income with that of the business or you will not be able to tell how much money it is making (if any). For the same reason you will want to keep track of how much money you put into and take out of the business so you will want to set up a completely seperate set of records for it and treat it almost as if it had a life of its own.
Examples:
You need to record both sides of each transaction: thus double entry. Furthermore, you want to organize your entries, recording those having to do with money in one place, value of goods bought and sold in another, money owed in yet another, etc. Hence you create accounts, and record each half of each transaction in an appropriate account. Of course, you won’t have to actually record the amount in more than one place yourself: the program takes care of that.
All other accounts are subdivisions of these. The relationship between the top-level accounts is often stated in the form of the Accounting Equation (don’t worry: you won’t have to solve it):
Assets = Liabilities + Equity + (Revenue - Expense)
You won’t actually use this equation while doing your bookkeeping, but it’s a useful tool for understanding how the system works.
Traditional paper accounting systems used a two-column form in which all increases went in one column and all deceases in the other. For asset and expense accounts increases went in the left column and decreases in the right. For liability and capital accounts decreases went in the left column and increases in the right. Looking at the accounting equation we see that assets are on the left, so it is logical that asset increases would go on the left. Libilities, capital, and revenue are on the right so it is logical that their increase would go on the right. Expenses, however, are on the right, so why do their increases go on the left? Because expenses are subtracted from the right side of the equation and so expense increases decrease the right side of the equation.
Entries in the left column of the traditional form are called debits, while entries on the right are called credits. Neither is "negative".
Examples:
You go to the bank and make a deposit. The teller tells you that he is going to credit your account. This is correct: your account is money the bank owes you and so is a liability from their point of view. Your deposit increased this liability and so they will credit it. They will make an equal debit to their cash account. When you return you will debit your bank deposits account because you have increased that asset and credit cash on hand because you have decreased that one.
Early accounting systems were usually run on a cash basis. One generally did not consider money owed to affect the financial health of a company, so expenses posted when paid as did income.
The problem with this approach is that it becomes very difficult or impossible to truly understand the exact nature of the financial health of a business. One cannot get the full picture of the financial health of a business because outstanding debts are not considered. Futhermore, this does not allow for revenue to be tied to cost effectively, so it becomes difficult to assess how profitable a given activity truly is.
To solve this problem, accrual-based systems were designed. The basic principle is that income and expense should be posted as they are incurred, or accrued. This allows one to track income relative to expense for specific projects or operations, and make better decisions about which activities will help one maximize profitability.
To show how these systems differ, imagine that you bill a customer for time and materials for a project you have just completed. The customer pays the bill after 30 days. In a cash based system, you would post the income at the time when the customer pays, while in an accrual system, the income is posted at the time when the project is completed.
http://www.accounting-and-bookkeeping-tips.com/learning-accounting/accounting-basics-credit.htm
Discussion of debits and credits as well as links to other accounting subjects.
http://www.computer-consulting.com/accttips.htm
Discussion of double entry bookkeeping.
http://www.minnesota.com/~tom/sql-ledger/howtos/
A short glossary, some links, and a FAQ (which makes the "credit=negative number" error). The FAQ focuses
on SQL-Ledger, LedgerSMB’s ancestor.
http://bitscafe.com/pub2/etp/sql-ledger-notes#expenses
Some notes on using SQL-Ledger (LedgerSMB’s ancestor).
http://en.wikipedia.org/wiki/List_of_accounting_topics
Wikipedia articles on accounting.
http://www.bized.ac.uk/learn/accounting/financial/index.htm
Basic accounting tutorial.
http://www.asset-analysis.com/glossary/glo_index.html
Financial dictionary and glossary.
http://www.geocities.com/chapleaucree/educational/FinanceHandbook.html
Financial glossary.
http://www.quickmba.com/accounting/fin/
Explanation of fundamentals of accounting, including good discussions of debits and credits and of
double-entry.
In general, most drop-down boxes in LedgerSMB order the accounts by account number. Therefore by setting appropriate account numbers, one can affect the default values.
A second consideration is to try to keep things under each heading appropriate to that heading. Thus setting an account number for a bank loan account in the assets category is not generally advisable.
These features are listed under System->Chart of Accounts. One can list the accounts and click on the account number to modify them or click on the "add account" option to create new accounts.
One can list the account balances via the Reports->Chart of Accounts report. Clicking on the account number will provide a ledger for that account.
This section covers other (non-Chart of Accounts) aspects to the setup of the LedgerSMB accounting package. These are generally accessed in the System submenu.
One of the new features in 1.2 is the modular sales tax system and the simple sales tax module. This allows one to install different tax modules and then select which taxes are applied by which programming modules. The sales tax module has access to everything on the submitted form so it is able to make complex determinations on what is taxable based on arbitrary criteria.
The tax rules drop-down box allows one to select any installed tax module (LedgerSMB 1.2 ships only with the simple module), while the ordering is an integer which allows one to specify a tax run which occurs on the form after any rules with lower entries in this box. This allows for compounding of sales tax (for example, when PST applies to the total and GST as well).
Sales Tax is collected on behalf of a state or national government by the individual store. Thus a sales tax account is a liability– it represents money owed by the business to the government.
To add a sales tax account, create an account in the Chart of Accounts as a liability account, check all of the "tax" checkboxes.
Once this account is created, one can set the tax amount.
Go to System->Defaults and the tax account will be listed near the bottom of the page. The rate can be set there.
These accounts are the default accounts for part creation and foreign exchange tracking.
The US accounts list this as USD:CAD:EUR. One can add other currencies in here, such as IDR (Indonesian Rupiah), etc. Currencies are separated by colons.
These sequences are used to generate user identifiers for quotations, invoices, and the like. If an identifier is not added, the next number will be used.
A common application is to set invoices, etc. to start at 1000 in order to hide the number of issued invoices from a customer.
Leading zeros are preserved. Other special values which can be embedded using <?lsmb ?> tags include:
Auditability is a core concern of the architects of any accounting system. Such ensures that any modification to the accounting information leaves a trail which can be followed to determine the nature of the change. Audits can help ensure that the data in the accounting system is meaningful and accurate, and that no foul play (such as embezzlement) is occurring.
In paper accounting systems, it was necessary to have a means to authoritatively track corrections of mistakes. The means by which this was done was known as "transaction reversal."
When a mistake would be made, one would then reverse the transaction and then enter it in correctly. For example, let us say that an office was renting space for $300 per month. Let us say that they inadvertently entered it in as a $200 expense.
The original transaction would be:
| Account | Debit | Credit |
| 5760 Rent | $200 | |
| 2100 Accounts Payable | $200 | |
The reversal would be:
| Account | Debit | Credit |
| 5760 Rent | $200 | |
| 2100 Accounts Payable | $200 | |
This would be followed by re-entering the rent data with the correct numbers. This was meant to ensure that one did not erase data from the accounting books (and as such that erasing data would be a sign of foul play).
LedgerSMB has a capability to require such reversals if the business deems this to be necessary. When this option is enabled, existing transactions cannot be modified and one will need to post reversing transactions to void existing transactions before posting corrected ones.
Most accountants prefer this means to other audit trails because it is well proven and understood by them.
You cannot alter a transaction that was entered before the closing date.
This option stores additional information in the database to help auditors trace individual transactions. The information stored, however, is limited and it is intended to be supplemental to other auditing facilities.
The information added includes which table stored the record, which employee entered the information, which form was used, and what the action was. No direct financial information is included.
Departments are logical divisions of a business. They allow for budgets to be prepared for the individual department as well as the business as a whole. This allows larger businesses to use LedgerSMB to meet their needs.
In general business units are divided into cost and profit centers. Cost centers are generally regarded as business units where the business expects to lose money and profit centers are where they expect to gain money. For example, the legal department in most companies is a cost center.
One of the serious misunderstandings people run up against is that LedgerSMB tends to more narrowly define cost and profit centers than most businesses do. In LedgerSMB a cost center is any department of the business that does not issue AR transactions. Although many businesses may have cost centers (like technical support) where customer fees may subsidize the cost of providing the service, in LedgerSMB, these are profit centers.
LedgerSMB will not allow cost centers to be associated with AR transactions. So if you want this functionality, you must create the department as a profit center.
LedgerSMB has the ability to track inventory by warehouse. Inventory items can be moved between warehouses, and shipped from any warehouse where the item is in stock. We will explore this concept more later.
Languages allow for goods and services to be translated so that one can maintain offices in different countries and allow for different goods and service descriptions to be translated to different languages for localization purposes.
One can create types of businesses and then give them discounts across the board. For example, one might give a firm that uses one’s services as a subcontractor a 10% discount or more.
GIFI is a requirement for Canadian customers. This feature allows one to link accounts with Canadian tax codes to simplify the reporting process. Some European countries now use a similar system.
People that don’t otherwise have a use for GIFI can use it to create reports which agregate accounts together.
Standard Industrial Classification is a way of tracking the type of business that a vendor or customer is in. For example, an accountant would have an SIC of 8721 while a graphic design firm would have an SIC of 7336. The classification is hierarchical so one could use this field for custom reporting and marketing purposes.
The templates for invoices, orders, and the like can be edited from within LedgerSMB. The submenus within the System submenu such as HTML Templates, Text Templates and LATEX templates provide access to this functionality.
Although the Year-end functionality in LedgerSMB is very useful, it does not entirely make the process simple and painless. One must still manually enter adjustments prior to closing the books. The extent to which these adjustments are necessary for any given business is a matter best discussed with an accountant.
The standard way books are normally closed at the end of the year is by moving all adjusted1 income and expenses to an equity account usually called "Retained Earnings." Assets and liabilities are not moved. Equity drawing/dividend accounts are also moved, but the investment accounts are not. The reasoning behind this process is that one wants a permanent record of the amount invested in a business, but any dividends ought not to count against their recipients when new investors are brought on board.
LedgerSMB automatically moves all income and expense into the specified year-end/retained earnings account. It does not move the drawing account, and this must be done manually, nor does it automate the process of making adjustments.
Contrary to its name, this function can close the books at any time, though this would likely be of limited use.
The ledgersmb.conf configures the software by assigning site-wide variables. Most of these should be left alone unless one knows what one is doing. However, on some systems some options might need to be changed, so all options are presented here for reference:
The Goods and Services module will focus on the definition of goods and services and the related accounting concepts.
It is possible to set different prices for different groups of customers, or for different customers individually. Similarly, one can track different prices from different vendors along with the required lead time for an order.
Pricegroups are used to help determine the discount a given customer may have.
Groups represent a way of categorizing POS items for a touchscreen environment. It is not fully functional yet, but is sufficient that with some stylesheet changes, it could be made to work.
Labor/overhead is usually used for tracking manufacturing expenses. It is not directly billed to a customer. It is associated with an expense/Cost of Goods Sold (COGS) account.
Services include any labor that is billed directly to the customer. It is associated with an expense/COGS account and an income account. Services can be associated with sales tax.
One approach to dealing with shipping and handling is to add it as a service. Create a service called “Shipping and Handling”, with a sell price $1 per unit, and a 0% markup. Bill it as $1 per unit. This allows one to add the exact amount of shipping and handling as necessary.
A part is any single item you might purchase and either might resell or use in manufacturing an assembly. It is linked to an expense/COGS account, an income account, and an inventory account. Parts can be associated with sales tax.
Manufacturers order parts but they sell the products of their efforts. LedgerSMB supports manufacturing using the concept of assemblies. An assembly is any product which is manufactured on site. It consists of a selection of parts, services, and/or labor and overhead. Assemblies are treated as parts in most other regards.
However, one cannot order assemblies from vendors. One must instead order the components and stock them once they are manufactured.
One stocks assemblies in the Stock Assembly entry on the Goods and Services submenu. When an assembly is stocked the inventory is adjusted properly.
The Check Inventory option will cause LedgerSMB to refuse to stock an assembly if the inventory required to produce the assembly would drop the part below the reorder point.
The All Items report provides a unified view of assemblies, parts, services, and labor for the company, while the Parts report confines it to parts.
Types of reports are:
One can also list these goods by invoice, order, or quotation.
For best results, it is a good idea to enter some AR and AP data before running these reports.
This report is designed to assist managers determine the quantities of goods to order and/or stock. It compares the quantity on hand with the activity in a given time frame and provides a list of goods which need to be ordered and the relevant quantity.
This is similar to the Parts and All Items menu but only supports Active, Obsolete, and Orphaned reports.
This is similar to the Parts and All Items reports but it also provides an ability to list individual items in the assemblies as well.
AP Invoices, Purchase Orders, and RFQ’s are not available on this report.
These reports provide a simple interface for locating groups and pricegroups. The report types are similar to what they are for services.
One can add translations so that they show up in the customer’s native language in the issued invoice.
To issue translations, one must have languages defined. One can then add translations to descriptions and part groups.
Cost of Goods Sold is tracked on a First-In, First-out (FIFO) basis. When a part is purchased, its cost is recorded in the database. The cost of the item is then added to the inventory asset account. When the good is sold, the cost of the item is moved to the cost of goods sold account.
This means that one must actually provide invoices for all goods entered at their actual cost. If one enters in $0 for the cost, the cost of goods sold will also be $0 when the item is sold. We will cover this entire process in more depth after we cover the AP and AR units below.
The Accounts Payable module tracks all financial commitments that the company makes to other businesses. This includes rent, utilities, etc. as well as orders of goods and services.
A vendor is any business that the company agrees to pay money to.
One can enter vendor information under AP->Vendors->Add Vendor. The vendor list can be searched under AP->Vendors->Reports->Search.
Enter start and end-dates for each vendor. This will make searches and drop-down boxes faster when some vendors are no longer actively supporting your company.
A few fields that need explanation are:
AP Transactions are generally used for items other than goods and services. Utilities, rent, travel expenses, etc. could be entered in as an AP transaction.
If the item is paid partially or in full when the transaction is entered, one can add payments to the payment section.
All other payments can and should be entered under cash payment (below).
The PO Number and Order Number fields are generally used to track associations with purchase orders sent to vendors, etc. These fields can be helpful for adding misc. expenses to orders for reporting purposes.
The department drop-down box appears when one has created one or more departments. A transaction is not required to be associated with a department, but one can use this feature for budget tracking.
With AP Transactions, there is no option for internal notes. All notes will appear on any printed version of the transaction.
Note: Printing a transaction does not post it. No data is committed until the invoice is posted.
AP Invoices are used to enter in the receipt of goods and services. Goods and services are deemed entered into the inventory when they are invoiced.
This screen is reasonably similar to the AP Transaction Screen, though the part entry section is a bit different.
The AP Invoice section has a capacity to separate internal notes from notes printed on the invoice. Note, however, that since these are received invoices, it is rare that one needs this ability.
Note that LedgerSMB can search for partial part numbers or descriptions.
Also if you have a group you can use this to select the part.
To remove a line item from an invoice or order, delete the partnumber and click update.
If an invoice is entered improperly, the methods used to correct it will vary depending on whether transaction reversal is enforced or not. If transaction reversal is not enforced, one can simply correct the invoice or transaction and repost. Note, however, that this violates generally accepted accounting principles.
If transaction reversal is in effect, one needs to create a duplicate invoice with exactly opposite values entered. If one part was listed as received, then one should enter a negative one for the quantity. Then one can enter the invoice number as the same as the old one. Add an R to the end to show that it is a reversing transaction. Once this is posted, one can enter the invoice correctly.
It is a bad idea to repost invoices/transactions just to enter a payment. The Cash->Payment window allows one to enter payments against AP invoices or transactions.
The printing capability can be used to print checks. The default template is NEBS 9085, though you can use 9082 as well (as Quickbooks does).
The source field is used to store an identifying number of the source document, such as the check number. One must select the item to have it paid, and then enter the amount. One can then print a check.
One can also use the rapid payment entry screen to print multiple checks. However, this does not allow you to print the multiple checks to the screen as a separate document is created for each check. In this event, one must print directly to a printer as postscript.
This report is designed to help you locate AP transactions based on various criteria. One can search by vendor, invoice number, department, and the like. One can even search by the shipping method.
The summary button will show what was placed where, while the details button will show all debits and credits associated with the transaction.
To view the invoice, click on the invoice number. In the detail view, to view the account transactions as a whole, click on the account number.
Open invoices are ones not fully paid off, while closed invoices are those that have been paid.
The outstanding report is designed to help you locate AP transactions that are not paid yet. The ID field is mostly useful for locating the specific database record if a duplicate invoice number exists.
This report can tell you how many invoices are past due and by how much.
A summary report just shows vendors while a detail report shows individual invoices.
These reports have known issues. It is better to use the GL reports and filter accordingly.
The Vendor Search screen can be used to locate vendors or AP transactions associated with those vendors.
The basic types of reports are:
One can include purchase orders, Requests for Quotations, AP invoices, and AP transactions on this report as well if they occur between the from and to dates.
This report can be used to obtain information about the past goods and services ordered or received from vendors. One can find quantities, partnumber, and sell prices on this report. This facility can be used to search RFQ’s, Purchase Orders, and AP Invoices.
Customers are entered in using the AR->Customers->Add Customer menu.
The salesperson is autopopulated with the current user who is logged in. Otherwise, it looks fairly similar to the Vendor input screen. Customers, like vendors can be assigned languages, but it is more important to do so because invoices will be printed and sent to them.
The credit limit field can be used to assign an amount that one is willing to do for a customer on credit.
The price list button can be used to enter specific discounts to the customer, and groups of customers can be assigned a pricegroup for the purpose of offering specific discounts on specific parts to the customer. Such discounts can be temporary or permanent.
AR Transactions are where one can add moneys owed the business by customers. One can associate these transactions with income accounts, and add payments if the item is paid when the invoice is issued.
The PO number field is used to track the PO that the customer sent. This makes it easier to find items when a customer is asking for clarification on a bill, for example.
AR Invoices are designed to provide for the delivery of goods and services to customers. One would normally issue these invoices at the time when the everything has been done that is necessary to get paid by the customer.
As with AP invoices, one can search for matches to partial part numbers and descriptions, and enter initial payments at this screen.
The Cash->Receipt screen allows you to accept prepayments from customers or pay single or multiple invoices after they have been posted. One can print a receipt, however the current templates seem to be based on check printing templates and so are unsuitable for this purpose. This presents a great opportunity for improvement.
The cash->receipts screen allows you to accept payments on all open customer invoices of all customers at once. One could print (directly to a printer only) all receipts to be sent out if this was desired.
The AR Outstanding report is almost identical to the AP Outstanding report and is not covered in any detail in this document.
This is almost identical to the AP Transactions Report.
If a customer’s PO has been associated with this transaction, one can search under this field as well.
This report is almost identical to the AP Aging report, with the exception that one can print up statements for customer accounts that are overdue. One more application is to calculate interest based on balance owed so that these can be entered as AR transactions associated with the customer.
These reports are almost identical to the AP Vendor reports and are not discussed in these notes.
A project is a logical collection of AR and AP transactions, orders, and the like that allow one to better manage specific service or product offerings. LedgerSMB does not offer comprehensive project management capabilities, and projects are only used here as they relate to accounting.
One can also add translated descriptions to the project names as well.
Timecards allow one to track time entered on specific services. These can then be used to generate invoices for the time entered.
The non-chargeable is the number of hours that are not billed on the invoice.
One can then generate invoices based on this information.
The project field is not optional.
One can select the project id for line items of both AR and AP invoices. These will then be tracked against the project itself.
The Timecard Report allows one to search for timecards associated with one or more projects. One can then use the total time in issuing invoices (this is not automated yet).
The Standard or GIFI options can be used to create different reports (for example, for Canadian Tax reporting purposes).
This report brings up a summary that looks sort of like a chart of accounts. Of one clicks on the account numbers, one can see the transactions associated with the project.
This provides a simple way of searching for projects to edit or modify.
This unit will introduce the business processes that LedgerSMB allows. These processes are designed to allow various types of businesses to manage their orders and allow for rudimentary customer relationship management processes to be built around this software. In this section, we will introduce the work flow options that many businesses may use in their day-to-day use of the software.
Sales orders represent orders from customers that have not been delivered or shipped yet. These orders can be for work in the future, for back ordered products, or work in progress. A sales order can be generated form an AR invoice or from a quotation automatically.
Quotations are offers made to a customer but to which the customer has not committed to the work. Quotations can be created from Sales orders or AR Invoice automatically.
The Shipping module (Shipping->Shipping) allows one to ship portions or entireties of existing sales orders, printing pick lists and packing slips.
One can then generate invoices for those parts that were shipped.
In general, one will be more likely to use these features if they have multiple warehouses that they ship from. More likely most customers will just generate invoices from orders.
A customer contacts your firm and asks for a quote on some services. Your company would create a quotation for the job and email it to the customer or print it and mail it. Once the customer agrees to pay, one creates a sales order from the quotation.
When the work is completed, the sales order is converted into a sales invoice and this is presented to the customer as a bill.
Note that in some cases, this procedure may be shortened. If the customer places an order without asking for a quotation and is offered a verbal quote, then one might merely prepare the sales order.
A customer contacts your firm and asks for a quotation for shipping a part. You would create the quotation and when you get confirmation, convert it to an order. Once the parts are in place you could go to shipping and ship the part.
The billing department can then generate the invoice from the sales order based on what merchandise has been shipped and mail it to the customer.
Note that this requires that you have the part in your inventory.
A customer contacts your firm and asks for a quotation for a number of different parts. You would create a quotation and when you get confirmation, convert it to a sales order. When you go to ship the item, you would select the warehouse in the drop-down menu, and select the parts to ship. One would repeat with other warehouses until the entire order is shipped.
Then the billing department would go to the sales order and generate the invoice. It would then be mailed to the customer.
A request for quotation would be a formal document one might submit to a vendor to ask for a quote on a product or service they might offer. These can be generated from Purchase Orders or AP Invoices.
A purchase order is a confirmation that is issued to the vendor to order the product or service. Many businesses will require a purchase order with certain terms in order to begin work on a product. These can be generated from RFQ’s or AP Invoices.
The Shipping->Receiving screen allows you to track the parts received from an existing purchase order. Like shipping, it does not post an invoice but tracks the received parts in the order.
Your company inquires about the price of a given good or service from another firm. You submit an RFQ to the vendor, and finding that the price is reasonable, you convert it to an order, adjust the price to what they have quoted, and save it. When the goods are delivered you convert the order into an AP invoice and post it.
Your company inquires about the price of a given good or service from another firm, You submit an RFQ to the vendor, and finding that the price is acceptable, you convert it into an order, adjusting the price to what they have quoted, and save it. When some of the goods are received, you open up the purchase order, enter the number of parts received, convert that order into an invoice, and post it. Repeat until all parts are received.
Your company inquires about the price of a given good or service from another firm, You submit an RFQ to the vendor, and finding that the price is acceptable, you convert it into an order, adjusting the price to what they have quoted, and save it. When some or all of the goods are received, the receiving staff goes to Shipping-Receiving, locates the purchase order, and fills in the number of items received.
The bookkeeper can then determine when all items have been received and post the invoice at that time.
The Generation screen allows you to generate Purchase Orders based on sales orders. One selects the sales orders one wants to use, and clicks "Generate Purchase Orders." Then one selects clicks on the parts to order, adjusts the quantity if necessary, and clicks "Select Vendor." This process is repeated for every vendor required. Then the Generate Orders button is clicked.
One can consolidate sales and/or purchase orders using this screen. For the consolidation to work you must have more than one order associated with the relevant customer or vendor.
The reporting functionality in the order management is largely limited to the ability to locate purchase orders, sales orders, RFQ’s, and quotations.
One can transfer inventory between warehouses if necessary by using the Shipping->Transfer Inventory screen.
The HR module is currently limited to tracking employees for and their start and end dates. It has very little other functionality. One could build payroll systems that could integrate with it however.
LedgerSMB 1.2 includes a number of components merged from Metatron Technology Consulting’s SL-POS. Although it is still not a perfect solution, it is greatly improved in both workflow and hardware support. It is suitable for retail establishments at the moment.
The sales screen looks very much like a normal invoice entry screen with a few differences.
As LedgerSMB is a web-based application, the web browser usually does not allow the page to write to arbitrary files. Therefore hardware support for pole displays, etc. is not readily possible from the application itself. LedgerSMB gets around this limitation by using an additional set of network sockets from the server to the client to control its hardware. This naturally requires that other software is also running on the client.
Notes for specific types of hardware are as follows:
The POS->Open screen allows one to find any POS receipts that are not entirely paid off.
The POS->Receipts screen allows one to bring up a basic record of the POS terminals. It is not sufficient for closing the till, however, though it may help for reconciliation.
The till column is the last component or octet of the terminal’s IP address. Therefore it is a good idea to try to avoid having IP addresses where the last octet is the same.
All entries are grouped by date and source in this report.
The General Ledger is the heart of LedgerSMB. Indeed, LedgerSMB is designed to be as close as possible to a software equivalent of a paper-based accounting program (but with no difference between the General Ledger and General Journal).
In order to understand the principle of the General Ledger, one must have a basic understanding of the general process of bookkeeping using double-entry paper-based accounting systems.
Normally when a transaction would be recorded, it would first be recorded in the "General Journal" which would contain detailed information about the transaction, notes, etc. Then the entries from the General Journal would be transcribed to the General Ledger, where one could keep closer tabs on what was going on in each account.
In the general journal, all transactions are listed chronologically with whatever commentary is deemed necessary, while in the general ledger each account has its own page and transactions are recorded in a simple and terse manner. The General Journal is the first place the transaction is recorded and the General Ledger is the last.
At the end of the accounting period, the GL transactions would be summarized into a trial balance and this would be used for creating financial statements and closing the books at the end of the year.
Let us say that John starts his business with an initial investment of $10,000.
This is recorded in the General Journal as follows (in this example, suppose it is page 1):
| Date | Accounts and Explanation | Ref | DEBIT | CREDIT |
| March 1 | Checking Account | 1060 | 10000.00 | |
| John Doe Capital | 3011 | 10000.00 | ||
| John Doe began a business | ||||
| with an investment of | ||||
| $10000 | ||||
This would then be transcribed into two pages of the General Ledger. The first page might be the Checking Account page:
| DATE | EXPLANATION | REF. | DEBITS | DATE | EXPLANATION | REF. | CREDITS |
| March 1 | J1 | 10000.00 | |||||
On the John Doe Capital page, we would add a similar entry:
| DATE | EXPLANATION | REF. | DEBITS | DATE | EXPLANATION | REF. | CREDITS |
| March 1 | J1 | 10000.00 | |||||
The paper-based accounting procedure works well when one is stuck with paper recording requirements but it has one serious deficiency— all of this transcribing creates an opportunity for errors.
Relational databases relieve the need for such transcription as it is possible to store everything physically in a way similar to the way a General Journal is used in the paper-based systems and then present the same information in ways which are more closely related to the General Ledger book.
This is the exact way that the General Ledger is used in LedgerSMB. The actual data is entered and stored as if it was a general journal, and then the data can be presented in any number of different ways.
All modules of LedgerSMB that involve COA accounts store their data in the General Ledger (it is a little more complex than this but this is very close to the actual mechanism).
The simplest form of GL entry in LedgerSMB is the Cash->Transfer screen. This screen shows two transaction lines, and fields for reference, department, description, and notes.
The field descriptions are as follows:
The credit and debit options seem to be the opposite of what one would think of concerning one’s bank account. The reason is that your bank statement is done from the bank’s point of view. Your bank account balance is an asset to you and therefor you show it as having a debit balance, but to the bank it is money they owe you and so they show it as having a credit balance.
Note that in this screen, when an item is updated, it will reduce the number of lines to those already filled in plus an extra line for the new line in the data entry.
The GL Transaction screen (General Ledger->Add Transaction) is identical to the Cash Transfer screen with the exception that it starts with nine lines instead of two. Otherwise, they are identical.
Again, one must be careful with debits and credits. Often it is easy to get confused. It is generally worth while to go back to the principle that one tracks them with regard to their impact on the equity accounts. So expenses are credits because they debit the equity accounts, and income is a debit because it credits the retained earning equity account.
Currently payroll must be done as a GL transaction. The attempts to create a payroll system that would ship with LSMB have largely stalled.
Most customers running their businesses will have an idea of how to do this.
To reconcile an account (say, when one would get a checking account statement), one would go to cash/reconciliation, and check off the items that have cleared. One can then attempt to determine where any errors lie by comparing the total on the statement with the total that LSMB generates.
This can be done for other accounts too, such as petty cash.2
The most flexible report in LedgerSMB is the GL report because it has access to the entire set of financial transactions of a business. Every invoice posted, payment made or received, etc. can be located here.
The search criteria include:
The actual format of the report looks more like what one would expect in a paper accounting system’s general journal than a general ledger per se. A presentation of the data that is more like the paper general ledger is found in the Chart of Accounts report.
The GL reports can be used to do all manner of things. One can determine, for example, which AP invoice or transaction was paid with a certain check number or which invoice by a specific customer was paid by a specific check number.
Any transaction or invoice may be repeated a number of times in regular intervals. To schedule any GL, AR, or AP transaction or invoice, click the schedule button.
In general the reference number should be left blank as this will force LedgerSMB to create a new invoice or transaction number for each iteration. The rest of the options are self-explanatory. Note that a blank number if iterations will result in no recurrences of the transaction.
To process the recurring transactions, click on the Recurring Transactions option on the main menu select the ones you want to process and click "Process Transactions."
Financial statements and reports are a very important part of any accounting system. Accountants and business people rely on these reports to determine the financial soundness of the business and its prospects for the next accounting period.
Financial statements, such as the Income Statement and Balance Sheet can be prepared either on a cash or accrual basis. In cash-basis accounting, the income is deemed earned when the customer pays it, and the expenses are deemed incurred when the business pays them.
There are a number of problems with cash-basis accounting from a business point of view. The most serious is that one can misrepresent the wellbeing of a business by paying a large expense after a deadline. Thus cash-basis accounting does not allow one to accurately pair the income with the related expense as these are recorded at different times. If one cannot accurately pair the income with the related expense, then financial statements cannot be guaranteed to tell one much of anything about the well-being of the business.
In accrual basis accounting, income is considered earned when the invoice is posted, and expenses are considered incurred at the time when the goods or services are delivered to the business. This way, one can pair the income made from the sale of a product with the expense incurred in bringing that product to sale. This pairing allows for greater confidence in business reporting.
The Reports–>Chart of Accounts will provide the chart of accounts along with current totals in each account.
If you click on an account number, you will get a screen that allows you to filter out transactions in that account by various criteria. One can also include AR/AP, and Subtotal in the report.
The report format is similar to that of a paper-based general ledger.
In paper-based accounting systems, the accountant at the end of the year would total up the debits and credits in every account and transfer them onto another sheet called the trial balance. The accountant would check to determine that the total debits and credits were equal and would then transfer this information onto the financial statements. It was called a trial balance because it was the main step at which the error-detection capabilities of double-entry accounting systems were used.
This report is located under Reports –>Trial Balance. One can filter out items by date, accounting period, or department. One can run the report by accounts or using GIFI classifications to group accounts together.
From this report, you can click on the account number and see all transactions on the trial balance as well as whether or not they have been reconciled.
If the trial balance does not balance, get technical support immediately. This usually means that transactions were not entered properly. Some may have been out of balance, or some may have gone into non-existent accounts (believe it or not, LedgerSMB does not check this latter issue).
The trial balance offers a glance at the total activity in every account. It can provide a useful look at financial activity at a glance for the entire business.
By filtering out departments, one can determine what a department earned and spent during a given financial interval. This can be used in preparing budgets for the next accounting period.
The Income Statement is another tool that can be used to assist with budgetary planning as well as provide information on the financial health of a business.
The report is run from Reports–>Income Statement. The report preparation screen shows the following fields:
The report shows all income and expense accounts with activity during the period when the report is run, the balances accrued during the period, as well as the total income and expense at the bottom of each section. The total expense is subtracted from the total income to provide the net income during the period. If there is a loss, it appears in parentheses.
The income statement provides a basic snapshot of the overall ability of the business to make money. It is one of the basic accounting statements and is required, for example, on many SEC forms for publicly traded firms.
Additionally, businessmen use the income statement to look at overall trends in the ability of the business to make money. One can compare a given month, quarter, or year with a year prior to look for trends so that one can make adjustments in order to maximize profit.
Finally, these reports can be used to provide a look at each department’s performance and their ability to work within their budget. One can compare a department or project’s performance to a year prior and look for patterns that can indicate problems or opportunities that need to be addressed.
The balance sheet is the second major accounting statement supported by LedgerSMB. The balance sheet provides a snapshot of the current financial health of the business by comparing assets, liabilities, and equity.
In essence the balance sheet is a statement of the current state of owner equity. Traditionally, it does not track changes in owner equity in the same way the Statement of Owner Equity does.
The Balance Sheet report preparation screen is much simpler than the Income Statement screen. Balance sheets don’t apply to projects, but they do apply to departments. Also, unlike an income statement, a balance sheet is fixed for a specific date in time. Therefore one does not need to select a period.
The fields in creating a balance sheet are:
The balance sheet lists all asset, liability, and equity accounts with a balance. Each category has a total listed, and the total of the equity and liability accounts is also listed.
The total assets should be equal to the sum of the totals of the liability and equity accounts.
Get technical support immediately, This may indicate that out of balance transactions were entered or that transactions did not post properly.
The Statement of Owner Equity is the one accounting statement that LedgerSMB does not support. However, it can be simulated by running a balance sheet at the end of the time frame in question and comparing it to the beginning. One can check this against an income statement for the period in question to verify its accuracy. The statement of owner equity is not as commonly used now as it once was.
LedgerSMB allows most documents to be generated according to a template system. This allows financial statements, invoices, orders, and the like to be customized to meet the needs of most businesses. Company logos can be inserted, the format can be radically altered, one can print letters to be included with checks to vendors instead of the checks themselves, and the like. In the end, there is very little that cannot be accomplished regarding modification of these documents with the template system.
One can define different templates for different languages, so that a customer in Spain gets a different invoice than a customer in Canada.
The only template that uses a text-only format is the POS receipt. This example provides the simplest way to understand the template system.
The first two lines are:
<?lsmb company align=center width=40 ?>
<?lsmb address align=center width=40 ?>
The first line tells LedgerSMB to print the company name as passed to it via a variable, centered, with a page width of 40 characters. The second line does the same thing with the address.
These variables are usually passed to the invoice using form fields (hidden or otherwise) in the submitting web page. The printing script, however, can disable some of these fields or add others via database lookups and the like.
In all types of templates, variable substitution occurs between <?lsmb and ?>. One can optionally specify an alignment or a width but these are really only useful in text templates.
The following templates exist in HTML format:
These templates can be edited by an HTML editor. However, it is generally recommended that one back up templates first. The reason is that some HTML editors will fully re-parse the HTML and save it back without what they see as invalid tags. Most editors, however, will save the variable substitution tags because similar tags are also used by Microsoft’s active server pages.
Finally, some editors are known to mangle formatting, so many problems can be avoided by ensuring that one has a backup of the templates, especially if they have already been customized.
The following templates, by default, are available in LATEX :
LATEX templates allow one to generate PDF and postscript documents and print directly to a postscript-enabled printer or print software (like CUPS).
LATEX templates can be edited using a standard text editor (like vim or emacs), or using a synchronous LATEX implementation such as LY X.
LATEX (pronounced LAY-tech) is an extension on the TEX typesetting system. It largely consists of a set of macros that allow one to focus on the structure of the document while letting the TEX engine do the heavy lifting in terms of determining the optimal formatting for the page. LATEX is used in a large number of academic journals (including those of the American Mathematics Association). It is available at http://www.tug.org and is included in most Linux distributions.
Like HTML, LATEX uses plain text documents to store the formatting information and then when the document is rendered, attempts to fit it onto a page. LATEX supports the concept of stylesheets, allowing one to separate content from format, and this feature is used in many higher-end applications, like journal publication.
Unlike HTML, LATEX is a complete though simple programming language that allows one to redefine internals of the system for formatting purposes.
This document is written in LATEX.
LY X is a synchronous LATEX editor that runs on Windows, UNIX/Linux, and Mac OS X. It requires an installed LATEX-2e implementation and can be obtained at http://www.lyx.org. Like the most common LATEX implementations, it is open source and is included with most Linux distributions.
LATEX requires different formats of logos depending on whether the document is going to be generated as a PDF or as postscript. Postscript requires an embedded postscript graphic, while PDF requires any type of graphic other than embedded postscript. Usually one uses a PNG’s for PDF’s, though GIF’s could be used as well. The logo for a LATEX document resides in the users directory.
HTML documents can have logos in many different formats. PNG’s are generally preferred for printing reasons. The image can be stored anywhere and merely referenced in the HTML.
Note: Always test the an invoice with images to ensure that the rest of the page format is not thrown off by it.
The template directory ("templates" in the root LedgerSMB install directory) contains all the root templates used by LedgerSMB. These follow a naming convention of COAType-templatename.ext where COAType is the type of dataset that was created when the user was created, templatename is the name of the template, and ext is either txt, html, or tex (for text, html, and LATEX respectively).
Inside this directory are one or more subdirectories where the relevant templates have been copied as default language templates for the user. Many users can use the same user directory (which bears the name of the LedgerSMB username). Within this directory are more subdirectories for translated templates, one for each language created.
When LedgerSMB is upgraded, the templates are not replaced. This is designed to prevent the upgrade script from overwriting changes made during the course of customizing the templates.
Occasionally, however, the data model changes in a way which can cause the templates to stop printing certain information. When information that was showing up before an upgrade stops showing up, one can either upgrade the templates by copying the source template over the existing one, or one can edit the template to make the change.
The command-line API will be referred to as the API.
Logging into LedgerSMB (1.2+) updates a row in the users_conf table containing your account configuration defaults and other information. The implication for API users of LSMB is that you must login as part of running API scripts. For security purposes, it is recommended that scripts prompt for a password rather than storing it.
All scripts included in the documentation can also be found in the doc/samples directory.
Consider a simple example:
cd /usr/local/ledgersmb ./ct.pl "login=name&path=bin&password=xxxxx&action=search&db=customer"
The cd command moves your terminal session’s current working directory into the main LedgerSMB directory. Then the LedgerSMB perl script ct.pl is called with one long line as an argument. The argument is really several variable=value pairs separated by ampersands (&). The value for the login variable is the username that LedgerSMB is to use, and the value for the password variable is the plaintext password.
To build our examples we will use a username of "clarkkent" who has a password of "lOis,lAn3".
cd /usr/local/ledgersmb ./ct.pl "login=clarkkent&path=bin&password=lOis,lAn3&action=search&db=customer"
If we execute these commands we will get the html for the search form for the customer database. This result isn’t useful in itself, but it shows we are on the right track.
With a working example, we can start to build reproducible routines that we can grow to do some useful work.
This is a bash script which:
1. sets NOW to the current working directory 2. prompts for and reads your LedgerSMB login 3. prompts for and reads (non-echoing) your LedgerSMB password 4. changes directory to /usr/local/ledgersmb 5. constructs login and logout commands and a transaction command 6. logs into ledgersmb (in a real program, output would be checked for success or failure) 7. executes the transaction 8. logs out of ledgersmb (although this is not necessary) 9. returns to the original working directory 10. exits
Running lsmb01-cli-example.sh produces:
$ lsmb01-cli-example.sh
LedgerSMB login: clarkkent
LedgerSMB password:
<body>
<form method=post action=ct.pl> <input type=hidden name=db value=customer> <table width=100%> <tr> <th class=listtop>Search</th> . . . |
A script like this would work well for simple batch transactions, but bash is not a very friendly language for application programming.
A nicer solution would be to use a language such as perl to drive the command line API.
#!/bin/bash
####################################################################### # # lsmb01-cli-example.sh # Copyright (C) 2006. Louis B. Moore # # $Id: $ # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. # ####################################################################### NOW=‘pwd‘ echo -n ~LedgerSMB login: ~ read LSLOGIN echo echo -n ~LedgerSMB password: ~ stty -echo read LSPWD stty echo echo ARG=~login=${LSLOGIN}&password=${LSPWD}&path=bin&action=search&db=customer~ LGIN=~login=${LSLOGIN}&password=${LSPWD}&path=bin&action=login~ LGOT=~login=${LSLOGIN}&password=${LSPWD}&path=bin&action=logout~ cd /usr/local/ledgersmb ./login.pl $LGIN 2>&1 > /dev/null ./ct.pl $ARG ./login.pl $LGOT 2>&1 > /dev/null cd $NOW exit 0 |
Our second script is written in perl and logs you in but it still uses the API in its simplest form, that is, it builds commands and then executes them. This type of script can be used for more complex solutions than the simple bash script above, though it is still fairly limited. If your needs require, rather than have the script build and then execute the commands it could be written to generate a shell script which is executed by hand.
This script begins by prompting for your LedgerSMB login and password. Using the supplied values a login command is constructed and passed into the runLScmd subroutine. runLScmd changes directory to /usr/local/ledgersmb/ for the length of the subroutine. It formats the command and executes it and returns both the output and error information to the caller in a scalar.
The script checks to see if there was an error in the login, exiting if there was.
Next, the script reads some records which are stored in the program following the __END__ token. It takes each record in turn, formats it then feeds each transaction through runLScmd and looks at the results for a string that signals success.
Once all the transactions are processed, runLScmd is called one last time to logout and the script exits.
#!/usr/bin/perl -w
# # File: lsmb02-cli-example.pl # Environment: LedgerSMB 1.2.0+ # Author: Louis B. Moore # # Copyright (C) 2006 Louis B. Moore # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License # as published by the Free Software Foundation; either version 2 # of the License, or (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. # # Revision: # $Id$ # # use File::chdir; use HTML::Entities; print ~\n\nLedgerSMB login: ~; my $login = <STDIN>; chomp($login); print ~\nLedgerSMB password: ~; system(~stty -echo~); my $pwd = <STDIN>; system(~stty echo~); chomp($pwd); print ~\n\n~; $cmd = ~login=~ . $login . ’&password=’ . $pwd . ’&path=bin&action=login’; $signin = runLScmd(~./login.pl~,$cmd); if ( $signin =~ m/Error:/ ) { print ~\nLogin error\n~; exit; } while (<main::DATA>) { chomp; @rec = split(/\|/); $arg = ’path=bin/mozilla&login=’ . $login . ’&password=’ . $pwd . ’&action=’ . escape(substr($rec[0],0,35)) . ’&db=’ . $rec[1] . ’&name=’ . escape(substr($rec[2],0,35)) . ’&vendornumber=’ . $rec[3] . ’&address1=’ . escape(substr($rec[4],0,35)) . ’&address2=’ . escape(substr($rec[5],0,35)) . ’&city=’ . escape(substr($rec[6],0,35)) . ’&state=’ . escape(substr($rec[7],0,35)) . ’&zipcode=’ . escape(substr($rec[8],0,35)) . ’&country=’ . escape(substr($rec[9],0,35)) . ’&phone=’ . escape(substr($rec[10],0,20)) . ’&tax_2150=1’ . ’&taxaccounts=2150’ . ’&taxincluded=0’ . ’&terms=0’; $rc=runLScmd(~./ct.pl~,$arg); if ($rc =~ m/Vendor saved!/) { print ~$rec[2] SAVED\n~; } else { print ~$rec[2] ERROR\n~; } } $cmd = ~login=~ . $login . ’&password=’ . $pwd . ’&path=bin&action=logout’; $signin = runLScmd(~./login.pl~,$cmd); if ( $signin =~ m/Error:/ ) { print ~\nLogout error\n~; } exit; #******************************************************* # Subroutines #******************************************************* sub runLScmd { my $cmd = shift; my $args = shift; my $i = 0; my $results; local $CWD = ~/usr/local/ledgersmb/~; $cmd = $cmd . ~ \~~ . $args . ~\~~; $results = ‘$cmd 2>&1‘; return $results; } sub escape { my $str = shift; if ($str) { decode_entities($str); $str =~ s/([^a-zA-Z0-9_.-])/sprintf(~%%%02x~, ord($1))/ge; } return $str; } #******************************************************* # Record Format #******************************************************* # # action | db | name | vendornumber | address1 | address2 | city | state | zipcode | country | phone # __END__ save|vendor|Parts are Us|1377|238 Riverview|Suite 11|Cheese Head|WI|56743|USA|555-123-3322| save|vendor|Widget Heaven|1378|41 S. Riparian Way||Show Me|MO|39793|USA|555-231-3309| save|vendor|Consolidated Spackle|1379|1010 Binary Lane|Dept 1101|Beverly Hills|CA|90210|USA|555-330-7639 x772| |
LedgerSMB is a web-based Perl program that interfaces with PostgreSQL using the relevant Perl modules. The code is well partitioned, and the main operation modules are written in an object oriented way.
LedgerSMB runs in a Perl interpreter. I do not currently know if it is possible to run it with Perl2C or other language converters to run in other environments. However, except for high-capacity environments, Perl is a good language choice for this sort of program.
LedgerSMB used to support DB2 and Oracle as well as PostgreSQL. However, currently some of the functionality is implemented using PostgreSQL user-defined functions. These would need to be ported to other database managers in order to make the software work on these. It should not be too hard, but the fact that it has not been done yet may mean that there is no real demand for running the software under other RDBMS’s.
One can substitute other web servers for Apache. Normally LedgerSMB is run as a CGI program but it may be possible to run it in the web server process (note that this may not be entirely thread-safe).
The operating system can be any that supports a web server and Perl (since PostgreSQL need not run on the same system). However, there are a few issues running LedgerSMB on Windows (most notably in trying to get Postscript documents to print properly).
On the client side, any web-browser will work. Currently, the layout is different for Lynx (which doesn’t support frames), and the layout is not really useful under eLinks (the replacement for Lynx which does support frames). Some functionality requires Javascript to work properly, though the application is usable without these features.
Some companies may ask how scalable LedgerSMB is. In general, it is assumed that few companies are going to have a need for a high-concurrency accounting system. However, with all the features available in LedgerSMB, the staff that may have access to some of the application may be senior enough to make the question worthwhile.
This question also becomes more important when companies might look at integrating LedgerSMB with a CRM solution, online store, or other environment. This section looks at a number of the known issues and their solutions.
LedgerSMB is a fairly standard web-based application. However, sometimes the database schema changes during upgrades. In these cases, it becomes impossible to use different versions of the software against the same database version safely. LedgerSMB checks the version of the database and if the version is higher than the version of the software that is running, will refuse to run.
Therefore although one strategy might be to run several front-end web servers with LedgerSMB, in reality this can be a bit of a problem. One solution is to take half of the front-end servers off-line while doing the initial upgrade, and then take the other offline to upgrade when these are brought back online.
The database manager is less scalable in the sense that one cannot just add more database servers and expect to carry on as normal. However, aside from the known issues listed below, there are few performance issues with it. If complex reports are necessary, these can be moved to a replica database (perhaps using Slony-I).
If this solution is insufficient for database scalability, one might be able to move staff who do not need real-time access to new entries onto a PG-Pool/Slony-I cluster where new transactions are entered on the master and other data is looked up on the replica. In certain circumstances, one can also offload a number of other queries from the master database in order to minimize the load. LedgerSMB has very few issues in the scalability of the application.
PostgreSQL uses a technique called Multi-version Concurrency Control (MVCC) to provide a snapshot of the database at the beginning of a statement or transaction (depending on the transaction isolation level). When a row is updated, PostgreSQL leaves the old row in the database, and inserts a new version of that row into the table. Over time, unless those old rows are removed, performance can degrade as PostgreSQL has to search through all the old versions of the row in order to determine which one ought to be the current one.
Due to the way the SQL statements are executed in LedgerSMB, most inserts will also create a dead row.
A second problem occurs in that each transaction is given a transaction id. These id’s are numbered using 32-bit integers. If the transaction id wraps around (prior to 8.1), data from transactions that appear (due to the wraparound) to be in the future suddenly becomes inaccessible. This problem was corrected in PostgreSQL 8.1, where the database will refuse to accept new transactions if the transaction ID gets too close to a wraparound. So while the problem is not as serious in 8.1, the application merely becomes inaccessible rather than displaying apparent data loss. Wraparound would occur after about a billion transactions between all databases running on that instance of PostgreSQL.
Prior to 8.1, the main way to prevent both these problems was to run a periodic vacuumdb command from cron (UNIX/Linux) or the task scheduler (Windows). In 8.1 or later, autovacuum capabilities are part of the back-end and can be configured with the database manager. See the PostgreSQL documentation for treatment of these subjects.
In general, if performance appears to be slowly degrading, one should try to run vacuumdb -z from the shell in order to attempt to reclaim space and provide the planner with accurate information about the size and composition of the tables. If this fails, then one can go to other methods of determining the bottleneck and what to do about it.
The PostgreSQL planner assumes a minimum page size of ten pages for a physically empty table. The reasoning behind this choice is that a table could grow rapidly and one could end up with bad database performance if the planner assumes a very small table.
However, if you end up with joins between a very large table with millions of rows and a physically empty table, one can end up with a very bad query plan. In this case, the planner will choose a nested loop join and run through this loop for every row in the large table. As a result, performance will suddenly drop once the large table becomes too large to effectively do index scans of the join criteria on both tables. This problem most often occurs when people have no warehouses, departments, or projects defined and are running systems with a large number of transactions (such as a point of sale environment).
Last time I saw this problem, the server would wait for thirty seconds to display a new point of sale screen while the server CPU activity would spike to 100%.
One solution is to define one warehouse, department, and project, and then run vacuumdb -z from the shell to force the planner to acknowledge these tables as single-row tables. The other option is to go into the source code and edit the database queries to omit unused tables.
LedgerSMB is designed to be customized relatively easily and rapidly. In general, the source code is well written and compartmentalized. This section covers the basic possibilities involving customization.
LedgerSMB is an application with over 34000 lines of code. While it is not possible to cover the entire application here, a brief overview of the source code is in order.
In the root of the install directory, one will find a setup.pl program, a number of other .pl programs, and a number of directories. The setup.pl program is used to update or install LedgerSMB. The other .pl programs provide a basic set of services for the framework (including authentication) and then pass the work on to the data entry screen file in the bin directory.
The bin directory contains another directory for each terminal type. The main two offered are lynx and mozilla. Lynx would be used for web browsers that do not support frames and is ideal for a text-mode VGA terminal. Mozilla is the terminal type used for most other web browsers. The perl files within these directories provides the user interface of the software.
The css directory in the root install directory contains CSS documents to provide various stylesheets one can select for changing various aspects of the look and feel of the application.
The locale directory contains translation files that LedgerSMB uses to translate between different languages. One could add translations to these files if necessary.
The LSMB directory is where the Perl modules reside that provide the core business logic in LedgerSMB. These modules provide functionality such as form handling, email capabilities, and access to the database through its at least partially object oriented API.
Finally, the sql directory provides the database schemas and upgrade scripts.
One can customize the data entry screens to optimize work flow, display additional information, etc.
We set up hot keys for payment lines, automatically focused the keyboard on the last partnumber field, removed separate print and post buttons to ensure that invoices were always printed and posted together, and removed the ability to print to the screen, and even the ability to scan items in when an invoice was received (using a portable data terminal) and import this data into LedgerSMB. Finally we added the ability to reconcile the till online in a paperless manner.
For another customer, we added the ability to print AR invoices in plain text format and added templates (based on the POS sales template) to do this.
One can add functionality to the Perl modules in the LSMB directory and often add missing functions easily.
For one customer, we added a module to take data from a portable data terminal collected when inventory items were taken and use that to add shrinkage and loss adjustments. We also extended the parts model to add a check id flag (for alcohol sales) and added this flag to the user interface.
For another customer, we added a complex invoice/packing slip tracking system that allowed one to track all the printed documents associated with an order or invoice.
As noted before templates can be modified or extended, though sometimes this involves extending the user interface scripts. Most templates are easy enough to modify.
For one customer we added text-only invoices for AR and AP transactions/Invoices and an ability to use Javascript in them to automatically print them on load.
The fact that all the data is available within the database manager is a huge advantage of LedgerSMB over Quickbooks and the like. The rapid development of reports allows for one to easily develop reports of any sort within LedgerSMB.
For one customer, we developed a report of parts sold and received during arbitrary time frames. The report allows one to go back and look up the invoices involved.
An open database system and programming API allows for many types of integration. There are some challenges, but in the end, one can integrate a large number of tools.
Any reporting tool which can access the PostgreSQL database can be used with LedgerSMB for custom reporting. These can include programs like Microsoft Access and Excel (using the ODBC drivers), PgAccess (A PostgreSQL front-end written in TCL/Tk with a similar feel to Access), Rekall, Crystal Reports, OpenOffice and more.
We have created spreadsheets of the summaries of activity by day and used the ODBC driver to import these into Excel. Excel can also read HTML tables, so one can use PostgreSQL to create an HTML table of the result and save it with a .xls extension so that Windows opens it with Excel. These could then be served via the same web server that serves LedgerSMB.
Various line of business tools have been written using PostgreSQL in large part due to the fact that it is far more mature than MySQL in areas relating to data integrity enforcement, transactional processing, and the like. These tools can be integrated with LedgerSMB in various ways. One could integrate this program with the HERMES CRM framework, for example.
LedgerSMB uses a single ’id’ sequence across many tables. At the same time it is expected that these tables do not have identical id values in their records as they are used as a sort of pseudo-foreign key by the acc_trans table which stores the financial transaction information.
If the integration solution does not keep this in mind, it is possible to create a situation where the account transactions are ambiguously associated with a number of different types of financial transactions. This would lead to a large number of problems.
In general, it is advisable to run all such programs that benefit from integration in the same database but under different schemas. This allows PostgreSQL to become the main method of synchronizing the data in real time. However, sometimes this can require dumping the database, recreating the tables etc. in a different schema and importing the data back into LedgerSMB.
One possibility for this sort of integration is to use database triggers to replicate the data between the applications in real-time. This can avoid the main issue of duplicate id’s. One issue that can occur however relates to updates. If one updates a customer record in HERMES, for example, how do we know which record to update in LedgerSMB? There are solutions to this problem but they do require some forethought.
A second possibility is to use views to allow one application to present the data from the other as its own. This can be cleaner regarding update issues, but it can also pose issues regarding duplicate id fields.
Others have integrated L’ane POS and LedgerSMB in order to make it work better with touch screen devices. Still others have successfully integrated LedgerSMB and Interchange. In both cases, I believe that triggers were used to perform the actual integration.
Often there are requests to integrate LedgerSMB with applications like SugarCRM, OSCommerce, and other applications running on MySQL or other database managers. This is a far more complex field and it requires a great deal more effort than integrating applications within the same database.
Real-time integration is not always possible. MySQL does not support the SQL extension SQL/MED (Management of External Data) that supports non-MySQL data sources so it is not possible to replicate the data in real-time. Therefore one generally resorts to integrating the system using time-based updates. Replication may be somewhat error-prone unless the database manager supports triggers (first added to MySQL in 5.0) or other mechanisms to ensure that all changed records can be detected and replicated. In general, it is usually advisable to add two fields to the record– one that shows the insert time and one that shows the last update.
Additionally, I would suggest adding additional information to the LedgerSMB tables so that you can track the source record from the other application in the case of an update.
In general, one must write replication scripts that dump the information from one and add it to the other. This must go both ways.
While many people write Perl scripts to accomplish the replication, an open source project exists called DBI-Link. This package requires PL/Perl to be installed in PostgreSQL, and it allows PostgreSQL to present any data accessible via Perl’s DBI framework as PostgreSQL tables. DBI-Link can be used to allow PostgreSQL to pull the data from MySQL or other database managers.
DBI-Link can simplify the replication process by reducing the operation to a set of SQL queries.
This section is meant to provide a programmer with an understanding of the technologies enough information to get up to speed quickly and minimize the time spent familiarizing themselves with the software. Topics in this section are listed in order of complexity. As it appeals to a narrower audience than previous discussions of this topic, it is listed separately.
The main framework scripts (the ar.pl, ap.pl, etc. scripts found in the root of the installation directory) handle such basic features as instantiating the form object, ensuring that the user is logged in, and the like. They then pass the execution off to the user interface script (usually in the bin/mozilla directory).
LedgerSMB in many ways may look sort of object oriented in its design, but in reality, it is far more data-driven than object oriented. The Form object is used largely as a global symbol table and also as a collection of fundamental routines for things like database access. It also breaks down the query string into sets of variables which are stored in its attribute hash table.
In essence one can and often will store all sorts of data structures in the primary Form object. These can include almost anything. It is not uncommon to see lists of hashes stored as attributes to a Form object.
Templates are used to generate printed checks, invoices, receipts, and more in LedgerSMB. Often the format of these items does not fit a specific set of requirements and needs to be changed. This document will not include LATEX or HTML instruction, but will include a general introduction to editing templates. Also, this is not intended to function as a complete reference.
Template instructions are contained in tags <?lsmb and ?>. The actual parsing is done by the parse_template function in LSMB/Form.pm.
The first tag one will see with LATEX templates is <?lsmb pagebreak num1 num2 num3 ?>
The pagebreak block is terminated by <?lsmb end pagebreak ?>. Any text within the pagebreak block is ignored by the template.
<?lsmb foreach varname ?>is used to iterate through a list of vars set by the user interface system (usually one of the files under bin/mozilla (or otherwise). The block is repeated for each varname in a list. Block ends with <?lsmb end varname ?>
In LATEX cross-references require two passes with latex to resolve. This is because the type is set page by page and the program really doesn’t know on which page a given reference will fall. This becomes an even larger issue where floats are concerned as they can move between pages for formatting reasons.
In rare cases, cross-references may point at incorrect pages even with two passes (if the inclusion of the cross-reference data moves the object to another page). In this case you will need to use three passes of LATEX in order to have accurate references.
LedgerSMB as of the time of this writing (2.6.8) only makes one pass at the LATEX file. To force it to make more than one pass, open Form.pm with your favorite text editor. Look for the line:
system("latex –interaction=nonstopmode $self->{ tmpfile} > $ self->{ tmpfile} .err");
Duplicate this line for two passes, or add two copies if you need three passes.
The following format is used for variable substitution:
Data entry forms and other user interface pieces are in the bin directory. In LedgerSMB 1.0.0 and later, symlinks are not generally used.
Each module is identified with a two letter combination: ar, ap, cp, etc. These combinations are generally explained in the comment headers on each file.
Execution in these files begins with the function designated by the form->{action} variable. This variable is usually derived from configuration parameters in the menu.ini or the name of the button that was clicked on to submit the previous page. Due to localization requirements, the following process is used to determine the appropriate action taken:
The $locale->getsub routine is called. This routine checks the locale package to determine if the value needs to be translated back into an appropriate LSMB function. If not, the variable is lower-cased, and all spaces are converted into underscores.
In general there is no substitute for reading the code to understand how this can be customized and how one might go about doing this.
The Perl Modules (.pm files) in the LedgerSMB directory contain the main business logic of the application including all database access. Most of the modules are relatively easy to follow, but the code quality leaves something to be desired. The API calls themselves are likely to be replaced in the future, so work on documenting API calls is now focused solely on those calls that are considered to be stable. At the moment, the best place to request information on the API’s is on the Developmers’ Email List (ledger-smb-devel@lists.sourceforge.net).
Many of these modules have a fair bit of dormant code in them which was written for forthcoming features, such as payroll and bills of materials.
One can add a new module through the normal means and connect it to other existing modules.
The $form object provides two methods for accessing the database. The $form->dbconnect(%myconfig) method commits each individual statement as its own transaction. The $form->dbconnect_noauto(%myconfig) method requires a manual commit. Both these functions are thin wrappers around the standard Perl DBI operations.
Louis Moore contributed some SQL-Ledger CLI examples that still work for LedgerSMB. You can find his page at http://www.sql-ledger.org/cgi-bin/nav.pl?page=contrib/moore.html&title=Louis%20B.%20Moore.
There are a couple of relevant sources of information on LedgerSMB in particular.
The most important resources are the LedgerSMB web site (http://www.ledgersmb.org) and the email lists found at our Sourceforge site.
In addition, it is generally recommended that the main bookkeeper of a company using LedgerSMB work through at least one accounting textbook. Which textbook is not as important as the fact that a textbook is used.
Each customer can have a default shipping address. This address is displayed prominantly in the add new customer screen. To change the shipping address for a single order, one can use the ship to button at the bottom of the quote, order, or invoice screen.
The carrier can be noted in the Ship Via field. However, this is a freeform field and is largely used as commentary (or instructions for the shipping crew).
In the event that a customer’s check bounces or a collection requirement is made, one can flag the customer’s account by setting the credit limit to a negative number.
If a debt needs to be written off, one can either use the allowance method (by writing it against the contra asset account of "Allowance for Bad Debts" or using the direct writeoff method where it is posted as an expense.
For purposes of this example we will use a business that assembles computers and sells them on a retail store.
Note, the needs of LedgerSMB are mostly useful for light manufacturing operations (assembling computers, for example). More manufacturing capabilities are expected to be released in the next version.
A custom assembly is a bit difficult to make. One must add the assembly prior to invoice (this is not true of goods and services). If the assembly is based on a different assembly but may cost more (due to non-standard parts) you can load the old assembly using Goods and Services->Reports->Assemblies and then make necessary changes (including to the SKU/Partnumber) and save it as new.
Then one can add it to the invoice.
Version 1.2, November 2002
Copyright ©2000,2001,2002 Free Software Foundation, Inc.
51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
Preamble
The purpose of this License is to make a manual, textbook, or other functional and useful document "free" 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.
This License is a kind of "copyleft", 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.
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.
This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.
A "Modified Version" 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.
A "Secondary Section" is a named appendix or a front-matter section of the Document 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. (Thus, 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.
The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.
The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.
A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document 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, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not "Transparent" is called "Opaque".
Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.
The "Title Page" 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, "Title Page" means the text near the most prominent appearance of the work’s title, preceding the beginning of the body of the text.
A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition.
The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.
You may copy and distribute the Document 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 section 3.
You may also lend copies, under the same conditions stated above, and you may publicly display copies.
If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document’s license notice requires Cover Texts, 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 Document and satisfy these conditions, can be treated as verbatim copying in other respects.
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.
If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. 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.
It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.
You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 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:
If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections 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 Invariant Sections in the Modified Version’s license notice. These titles must be distinct from any other section titles.
You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version 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.
You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. 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 Document 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.
The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.
You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.
The combined work need only contain one copy of this License, and multiple identical Invariant Sections 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.
In the combination, you must combine any sections Entitled "History" in the various original documents, forming one section Entitled "History"; likewise combine any sections Entitled "Acknowledgements", and any sections Entitled "Dedications". You must delete all sections Entitled "Endorsements".
You may make a collection consisting of the Document 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.
You may extract a single document from such a collection, and distribute 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.
A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation’s users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document’s Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.
Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections 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, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.
If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title.
You may not copy, modify, sublicense, or distribute the Document 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.
The Free Software Foundation 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 http://www.gnu.org/copyleft/.
Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" 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.
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:
Copyright ©YEAR YOUR NAME. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License".
If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the "with...Texts." line with this:
with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation.
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 GNU General Public License, to permit their use in free software.
