@simxware This is open source, if the features you want are not going to be developed and you really need them, you can always do it by yourself (or hire somebody who knows how to do it).
If you do so, would be great to share your code with the rest of the community.
unfortunately I do not have the programming skills to do it alone.
thanks to the work that I do, in the field of management software precisely, I have experience with respect to how it works, the necessary items, headings and db tables that could be used, but are not able to implement them in invoiceplane.
being the base of this project very valid implement the various types of documents used in various fields would make it one of the best.
I could still help by creating, knowing tables and items to be used in advance of the report that I would use it myself and then share them with the community
Continuing the discussion from I will stop developing on v1 after 1.4.0 is released:
But still, there’s a chance your requests are not developed by anybody. We have no right to demand features, as the community colaborating with this project are not getting any reward.
Maybe if you don’t know any developer to help with requests, you can use BountySource.
PS: I’m just saying this because I know an open source project without revenue and strong community is destined to die (as Fusion Invoice died to be reborn here).
I hope we can make this project strong and long-term sustainable.
The possibility of donations may be taken more into consideration.
I don’t find request of donation anywhere.
Is a valid project.
You may create threads of “interest” implementations with surveys … where anyone could provide material aid and who can and could “create” function.
But they are just thoughts …
Go to the main page and scroll down. You’ll see. 
Hello,
thankyou for this nice piece of software.
I had to change the configuration of PDF output, which I did in the related files. Would be nice to have a possibility to keep these changes after updates.
Hello,
As was said it’s very nice piece of code.
Thanks a lot for this work.
My project where I’ll plan to use InvoicePlane for invoices probably will be release
similar to IP in fall 2015 in Alpha state.
I’ll add some not trivial features to code like separate admin-user logins (to see
their own invoices only), translations to polish, better PDF generation, etc …
And will be developing & maintaining in the future.
My situation is maybe similar to @simxware but I’m freelancer - know CI and Laravel.
So @kovah do you suggest use a V1 code (CodeIgniter) or better V2 (Laravel) now?
@pauluz Im not sure if I understand what you trying to say.
Do you want to develop a completely new software on base of InvoicePlane or do you want to implement the features into the project itself?
Hi Kovah,
Thanks a lot for this information. When we are using now R1.4, can we easily upgrade to 2.0 with our existing Database?
Bye,
Simon
Yes the upgrade will be possible without problems.
@Kovah, Dank für den Reply. Wir möchten als Startup gerne invoiceplane nutzen. Wir würden dann quartalsweise gerne für das Projekt spenden, sofern sich das System bewährt. 
Sehr genre! 
So this is it 
1.4 has been released so that means V2 is just around the corner. Quite exciting to see this kind of speedy development. Well done and I’m looking forward to future versions. Have a great day!
Well v2 is not around the corner.
The setup is not even finished.
Doesn’t matter, at least now full focus can be invested in v2 because we don’t have any inbetween-versions anymore.
Wait, didn’t i read wrong? When someone else develops some changes there can be several later iterations of v1? I mean looking at the developer road it states that 1.4.1 is planned in 2 weeks, 1.5.0 should come with a completed tasks function e.t.c.?
Yes that’s right.
But I will not work on new features on my own. For example the task / project feature is developed by @cz_vilda
Just wanted to let you know: I got 1.4 running on IIS w/ SqlServer. Had to jump through some hoops, but it can be done and I’m actually using it right now.
I understand that this is not a high priority prerequisite, but you might bear in mind that some constructs will obstruct this possibility, like literal dbqueries. I saw you moved from CodeIgniter to Laravel, which also facilitates sqlsrv.
So I’m looking forward to v2