Apprentice
|
I second this request -- I'm just starting up a new client and it is strange that their first invoice will be #33
|
| |
|
Marketcircle Team

|
There are 2 problems here:
1) The minor one: If you send an invoice numbered "1" to a client, they will assume they are your first client - not good! The bigger the invoice number, the better.
2) The major one: In some jurisdictions, you have to have sequential invoice numbers - globally. It is the law. If you have holes in your sequences, you can be heavily fined.
|
| |
|
Apprentice
|
[AJ]
1] as an architect that has been in business for years, my clients DO NOT want to wonder why they got an invoice from me numbered 22 than the very next one numbered 28. we keep different invoice numbers for our clients projects, which also helps in adding up how much they have paid towards their contract fee. that is the one thing billings does not do so well, most of my projects have a contract fee and we bill towards that fee amount which is divided up accordingly into the different project phases. we charge hourly towards that phase total, anything left over is profit.
2] we do work globally and have never heard of any type of fine, who would have jurisdiction to be fining us, other than the US federal government? we do have to have sequential invoice numbers for each contract, with each client, hence the request for project numbered invoices.
so my request is for project related sequential invoices, that would make life easier for us architects.
|
| |
| Posts: 6 | Location: los angeles | Registered: June 20, 2007 |  
IP
|
|
Apprentice
|
Obviously nothing is happening with this, or has it been addressed already?
I totally agree with other posters on this issue and I'm surprised it's not a much more prominent request.
I really don't see the problem with creating an option to allow invoicing by project or client. If it's the law to have sequential invoices in some jurisdictions, then surely it's the user that has the responsibility to ensure their invoicing complies - not the software's responsibility to take away the choice from all users.
In my situation, my invoices are generally numbered sequentially per client (occasionally per project on big projects). Like jbech above, my clients expect their invoices to be sequential. My invoice numbering generally includes the client number (or a project ref) so a client's invoices might be numbered 86001,86002,86003 and so on. Another client will have invoices 74001,74002 etc.
I think AJ's suggestion that 'The bigger the invoice number, the better' is completely off the mark. I think my clients are intelligent enough to realise that the invoice number is specific to them, and that they're not my first client. If I really want to pad out my numbers then I could simply use a bigger starting number, but this really doesn't achieve much.
The lack of per client or per project invoice numbers is proving to be a massive stumbling block and I don't like having to create crazy workarounds in order to maintain consistent invoicing for my clients.
|
| |
|
Apprentice
|
I have to support this suggestion fully! In fact, I cannot use Billings until something like this is implemented or I can find a way to work around it. I've already been using a certain invoice numbering style for a while, and cannot simply change it now randomly, or my clients will get confused.
My current numbering scheme is as follows (and I have many associates from other companies who use a similar scheme): <ClientID>-<InvoiceCounterForThisClientOnly> (ie 1504-001, 1504-002, 1504-003, etc) or similarly: <ClientID>-<ProjectID>-<InvoiceCounterForThisProjectOnly> (ie 1504-01-001, 1504-01-002, 1504-02-001, 1504-02-002, etc)
|
| |
|
Apprentice
|
... what is the current status of this very common problem? my invoices also are generally numbered sequentially per client. please add this important frequently asked function.
|
| |
|