Invoicing

Recurring invoice module.

This invoicing module fills the gap between default Open ERP accounting modules and yourparticular billing data and is suitable for hosting (e-mail, web-hosting etc.), utilities, telecoms,service companies and others.

Designed especially for small to mid sized companies selling different kind of services, whichshould be constantly timely invoiced  on the single invoice. This task allowed us to develop theinvoicing module which employs basic features previously available in other similar ERP/CRMsystems (recurrent invoicing on fixed sums), as well as the features (recurrent invoicing basedon actually consumed amounts) formerly available only in specialized vertical systemsdesignated for single companies or single industries.

The main features include:

- fully automatic creation of analytic journal entries for further invoicing; - optionally full automation of invoice creation; - resulting analytic entries can be combined with manually invoiced items; - definition of various business logic methodologies; - to choose UI code constructor (Python) for fast deployment, manual expressions foradvanced users or to combine both of them; - unlimited count of methodologies per virtual service; - billing on actually used services; - billing on fixed and variable sums; - fully integrated in OpenERP (partners, products, price lists, accounting, financial reporting,invoices, etc.); - fully customizable invoicing schedule; - error prevention and reporting system; - customizable invoicing for every particular partner; - optionally connected to external systems for data collection;

Possible industry coverage:

- telecoms; - hosting companies; - utilities;

1 / 4

Invoicing

- waste management services; - real estate management services;

Three part (Methodology or business logic, service, partner agreement) design approachprovides work delegation:

- where business logic being a part, which is typically created by responsible staff,determines how the prices and discounts should be calculated. This part can be fixed aftercreation and it needs minimum attention after implementation. - service – typically created by senior manager or accountant, defines the schedule ofinvoice creation, specifies, which particular methodologies should be applied to this service,where the analytic entries should be placed, who should be informed on possible errors. Thispart can be fixed after creation too, and needs minimum attention after implementation. - agreement – is the part which is maintained by customer manager, it holds the informationon each particular customer and their subscribed services. Agreements resemble their real lifecounterparts – here one can find the information, when the customer should be invoiced (inadvance or after the period), validity period, prolongation, invoicing history.

This approach ensures the information persistence and responsibility delegation, separates thecomplicated business logic, accounting information from the parts which are typically beingdelegated to a junior staff.

Once the base business logic and services are defined, use the templates system to automatethe repeated information input rendering this process extremely fast. Time spent on eachparticular customer is reduced to the minimum.

Business logic or methodologies are designed to retain the definition process as simple aspossible, however by keeping them powerful allowing to define the advanced models. Businesslogic object oriented constructor can be used for simple tasks or as a base for python codegeneration which then can be modified to employ custom and more complicated models.

Complete integration with other OpenERP information objects and services such as partners,products, price lists, generic and financial accounting, minimizes integration and supportoverhead, bringing the power of business task automation formerly available only to the mid andlarge sized enterprises at the fingertips of small ones.

2 / 4

Invoicing

Screenshots:

Agreement view.

Service view.

Methodology view.

3 / 4

Invoicing

Advanced Methodology.

Agreement template.

 

4 / 4