Abrechnungszeitraum / Billing period

timo

Stefan_ For me it was very confusing that the invoice date was automatically mapped to BT72

What is the alternative? The only two I can think of is to either not pre-fill the B-72 date picker in the e-invoice dialog or to add another date picker in the main UI for "deliver date".

Stefan_ BT72 and BT73/BT74 are an either/or case, i.e.

There's two parts of this feature request: one for the "normal" UI and for the PDF generation, and one for the invoice dialog. And for the PDF creation, you would certainly need one date picker for the "invoice date" and then two more date pickers for date interval. And then we end up with 5 date pickers:

invoice date
due date
delivery date
delivery interval start
delivery interval end

I might start by focusing on the e-invoice dialog only, just to make sure people can get their delivery interval into their e-invoice, even if it requires manual steps (I'm assuming this is the reason you can currently not use the app?). And I can be less strict when it comes to the amount of UI elements or date pickers in the e-invoicing dialog.
What will be more difficult to accomplish is how to specify the delivery date interval in the database (and the main UI) without adding additional UI elements and/or adjusting the database model. That's why I came up with that idea to specify it in the free text field.

roberting

Hi Timo,
wouldn't it be possible do generate the Leistungsdatum (date of performance/delivery) already in WorkingHours? just as the individual positions can be grouped in different ways, it should be possible to export the date for the positions/grouped positions (or rather a calculated range of date from the first and last task in the selected period).

also, someone in the forum posted that he used placeholders like {date_invoice} in the text fields to achieve some dynamic text. Is there a comprehensive list of these placeholders?

best ragards
Robert

timo

roberting wouldn't it be possible do generate the Leistungsdatum (date of performance/delivery) already in WorkingHours

Yes it would, but one of the main problem I see that adding this would further complicate the UI. Additionally, there might need to be a setting where this feature can be enabled and disabled. As I explained here and in other threads, I am extremely cautious when adding new UI elements.

roberting Is there a comprehensive list of these placeholders

You can see the available placeholders when hovering the "i"-icon on the text fields

roberting

thanks timo
for the reply - I didn't notice the "I" 😅.

I see your point about the UI, but what about widening the range of available {placeholders}? These could be all sorts of parameters from within subtotal and/or imported from workingHours – I am already fantasising about having a 'month' calculated/extracted from the range of all working tasks exported for this invoice from WorkingHours; as in:

"Dear {client},
I hereby invoice you for services rendered in {task_month} {task_year} ..."

Obviously, it would be up to the user to make sure the parameters actually have values (e.g. for users that use subtotal without working hours, some parameters would yield "0" or "undefined"). But this would leave the UI untouched while enhancing the possibilities for those advanced users willing to experiment a little more.

... just some ideas – thanks, and keep up the excellent work!

timo

How exactly would additional placeholders help in the context of this issue (Billing period)?
Have you read the discussion above and my comment here?

I am open to add additional placeholders (e.g. for client), but we would need to discuss this in a different feature request

LXS

Hi Timo,
is this feature request still in consideration? It would be nice to have these two fields (BT-73 and BT-74) available because many of the customers do ask for it.

What about the suggestion from Rickyyy to configure the visibility of the fields in the invoice-template?
So the UI will still be clean for users who do not need these fields.

Thanks!
Alex

timo

Yes it is still under consideration but I currently don't have a lot of time for new features for SubTotal.
As noted above, the main issue I see is how to add the billing period into the UI without overwhelming it

« Previous Page