LMS makes possible to generate and to store various documents i.e. invoices, receipts and non-financial documents i.e. contracts, protocols and others. Documents can be numbered with numbering plans (patterns) defined in menu Configuration - Numbering Plans.
It's possible to issue invoices in either automatic or manual way. Manual invoices creation is possible in 'New Invoice' module from 'Finances' menu. Automatic issue might be helpful while you have legal contracts with your users. In this case invoices are created by lms-payments script or lmsd daemon.
For proper work of printouts you need to setup custom options in [invoices] section of lms.ini:
header
Seller. Can use string "\n" for lines separation. Default: empty.
Example: header = "SuperNet ISP\nNew Street 15\n12-000 City\n"
footer
Invoice footer - e.g. contact information about seller. Footer will be placed at bottom of an invoice, using small font. Like in header option use "\n" to separate lines. Default: empty
Example: footer = "Internet Service Provider K-27, phone 555-23-23, etc."
default_author
Invoice issuer name. Default: empty
Example: default_author = "invoicing expert"
cplace
Invoice issue location (city). Default: empty.
Example: cplace = Warsaw
Invoices are printed in html format by default using provided template. In [invoices] section you can also configure:
template_file
Invoice template, which should be placed in templates directory. Default: invoice.html.
Example: template_file = invoice-mynet.html
content_type
Invoice content-type. If you enter here 'application/octet-stream' then browser will ask to save file on disk, instead of displaying it. It's useful if you use your own template which generate eg. rtf or xls file. Default: 'text/html'
Example: content_type = application/octet-stream
attachment_name
File name for saving finished invoice printout. WARNING: Setting attachment_name with default content_type will (in case of MSIE) print invoice + prompt for save on disk + bonus browser crash (6.0SP1 on WInXP). Default: empty.
Example: attachment_name = invoice.xls
![]() | Almost every internet browser has printing configuration, where functions like header and footer or URL printing can be disabled. |
It's possible to create invoices as PDF files. Setting option type in [invoices] section to 'pdf' will force invoice being created in PDF instead of html. Option template_file has the same meaning, with one difference, that it might take predefined values: 'standard' - basic invoice (invoice.html equivalent) and 'FT-0100' - invoice adjusted for printing on FT-0100 paper including payment form. You can set template_file option for php file name, but this feature is meant for advanced users as it requires you to create more complicated php file than the one used with html invoices Smarty template.
Data for payment form printouts is stored in [finances] section of lms.ini file. That is:
name - seller name |
shortname - short seller name |
address - seller address |
zip - seller postal code |
city - seller city |
account - banking account number |
Receipts are printed in html format by default using provided template. In [receipts] section you can also configure:
template_file
Cash receipt template, which should be placed in templates directory. Default: receipt.html.
Example: template_file = /mytemplates/receipt.html
content_type
Printout content-type. If you enter here 'application/octet-stream' then browser will ask to save file on disk, instead of displaying it. It's useful if you use your own template which generate eg. rtf or xls file. Default: 'text/html'
Example: content_type = application/octet-stream
attachment_name
File name for saving receipt printout. WARNING: Setting attachment_name with default content_type will (in case of MSIE) print document + prompt for save on disk + bonus browser crash (6.0SP1 on WinXP). Default: empty.
Example: attachment_name = receipt.xls
Documents support is not limited to invoices. You might store virtually any documents you want in LMS, such as contracts, protocols, annexes and others. You can assign any number of documents to each customer in 'Customer documents' tab in 'Customer information' panel. Each document should have defined title, type and additionally you might define it's time span (time until when it's valid) and description. Document files are being stored outside of database (which should be kept in mind while doing backups!) in directory defined with doc_dir in [directories] section of config file.