In addition to the year and running invoice number that Billy supports, my typical invoice numbering scheme also includes a slot for the month: #YYYY-MM/NN.
I use this to encode either the service period, like this:
#2026-01/01 // First invoice for services rendered in January
#2026-01/02 // Second January invoice (for another client)
— or the date of issue:
#2026-06/10 // Tenth invoice, issued in June
#2026-07/11 // Eleventh invoice, issued in July
I see there's a Prefix field I could use, but no corresponding suffix option, and the same separator character is used between prefix & year, as well as between year & number, so it seems I can't replicate my usual format with the options Billy currently provides.
(I realize it's hard to anticipate the myriad of formats users might expect — and present that complexity clearly in a simple UI.)
I can certainly consider changing my number format to fit what Billy supports, but there may be others who require a different syntax, so a bit more flexibility here might be useful.
In addition to the year and running invoice number that Billy supports, my typical invoice numbering scheme also includes a slot for the month:
#YYYY-MM/NN.I use this to encode either the service period, like this:
— or the date of issue:
I see there's a Prefix field I could use, but no corresponding suffix option, and the same separator character is used between prefix & year, as well as between year & number, so it seems I can't replicate my usual format with the options Billy currently provides.
(I realize it's hard to anticipate the myriad of formats users might expect — and present that complexity clearly in a simple UI.)
I can certainly consider changing my number format to fit what Billy supports, but there may be others who require a different syntax, so a bit more flexibility here might be useful.