|
2 registered users in last 24 hours FI Creating Financial Documents using API'sThe following documentation explains how to create financial documents (i.e. customer invoices, quotes, purchase orders, delivery notes
The documentation covers the creation of financial documents via:
Financial Documents and Financial Document ItemsA financial document (customer invoice, quote, purchase order, provider bill, ...) consists of an object of type financial document,which is a sub-type of cost item (please note that the object type for financial documents is called "im_invoice" for historical reasons). The cost item is responsible of storing generic financial information include the customer and provider of the financial item and the amount. The financial document extends this common financial information with information on the accounting contact and the accounting office of the customer and the invoice template. In addition, the financial document assumes that there is at least one financial document item or "line" containing information about amount and type of product or service delivered or requested. Financial Document Lines Consistency ConstraintA consistency constraint exists linking the sum of the financial document items with the financial document: The subtotal of the financial document should be equal to the sum of its lines. This constraint is enforced on the application level:
Multiple Projects per Financial DocumentsThe ]po[ finance module data-model supports multiple projects per financial document. This feature basically allows companies to include several (typically small) projects into a single invoice, greatly reducing administrative effort in some usage cases.Relationship Projects - Financial DocumentsIn order to implement this features, ]po[ defines a generic N:M relationwhip between projects and financial documents, implemented via a [[object_type_acs_rels|acs_rels]]. The following three cases are important in practice:
|
