View Single Post
Old 6th February 2009, 11:44
till till is offline
Super Moderator
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 37,015
Thanks: 840
Thanked 5,652 Times in 4,461 Posts

I think billing should be implemented as a seperate Module with seperate DB-Tables to keep the ISPC3-core free from billing data.

The recent DB-structure is not very good for billing. One Customer could buy multiple Hosting-Packages. This is not possible with the recent DB.
The hirarchy should be like: Customer -> Account or Contract -> Website
This works very well for me with the current DB structure.

A DB-Table domain should be added where all buyed Domains are stored.
This would also be an important step for implementing domainrobots. To prevent Customers from using the DNS-System only as a Secondary-DNS Server, only domains from the table domain should be selectable in the DNS-System.
I think we need a more general approach where we have recurring and non recirring billing items of several types. And I wont mix up the billing system with the domain robot. And why should customers not be able to order secondary dns services? Thats a common feature.

Now you can add an Order and a Billing-System to ISPC3. The Order and the Billing System should be seperated. The Output of the Billing System should be XML so you can Import the billing data into Lexware. Or you add an additional invoice module which generates invoices as pdf.
ok. XML export can be one option beside pdf.

I would recommend to use the db-tables for the Order and billing-system from oscommerce v3.
I will take a look at their implementation. But most likely it will not fit for waht we need.
Till Brehm
Get ISPConfig support and the ISPConfig 3 manual from
Reply With Quote