Abrechnungszeitraum

Micha1909

Moin Timo,

ich habe heute von meinem Kunden als Rückmeldung auf meine neue SubTotal-Rechnung das Feedback erhalten, dass ich doch bitte weiterhin den Abrechnungszeitraum angeben soll. Das kann ich gut nachvollziehen, so ist es ja gerade zum Jahreswechsel relevant für die Steuer.

Auch in der XRechnung-Doku habe ich folgende Felder gefunden:
BT-73 Abrechnungszeitraum (von) Wählen Sie hier das Startdatum des Abrechnungszeitraums aus.
BT-74 Abrechnungszeitraum (bis) Wählen Sie hier das Enddatum des Abrechnungszeitraums aus.

Ich würde mich also freuen, wenn du diese Felder vielleicht ähnlich wie {date_invoice} und {date_due} aufnehmen und im Text verwendbar machen könntest.

Idealerweise kommen die Werte sogar aus dem WorkingHours-Export.

Today I received feedback from my customer on my new SubTotal invoice, asking me to please continue to specify the billing period. I can understand that, as it is particularly relevant for tax purposes at the turn of the year.

I also found the following fields in the XRechnung document:
BT-73 Billing period (from) Select the start date of the billing period here.
BT-74 Billing period (to) Select the end date of the billing period here.

I would be happy if you could perhaps include these fields in a similar way to {date_invoice} and {date_due} and make them usable in the text.

Ideally, the values even come from the WorkingHours export.

SubTotal version: 1.5.61.0
Operating system: Windows

timo

Please post Feature Requests in English language: *** PLEASE READ BEFORE POSTING ***
I have edited your post and added an English translation.

I am considering adding such fields to the e-invoice dialog, but I don't think that I will add them to the normal invoice UI. It can also be a bit tricky to create a good UI in the e-invoicing dialog so the user can choose between a single billing date (which is the current behavior) and a billing period.
In the meantime you can enter the billing period in the salutation text field (which will also be added to the e-invoice XML, just not in the BT-73/BT-74 fields, but in a note field)

I dient fully understand what you mean with the suggestion about {date_invoice} and {date_due}. Maybe you can elaborate?

Micha1909

Thank you for considering!

I don't get your idea of choosing between single billing date and a billing period.
Do you mean "Rechnungsdatum" / date_invoice as billing date?
In that case I may have to describe my request a little bit more.
The "Abrechnungszeitraum" (billing period) describes the period of time when the service that you want to charge was provided. If this range is just one day, than it might be the "Lieferdatum" (BT-72).
For me as an IT-Freelancer it's usually the previous month (f.e. 01.12.2024 - 31.12.2024).
The invoice date was the 02.01.2025, but it could be months later.
In my opinion there is no choice, the billing period is an additional information. The invoice date is mandatory.

My suggestion was, that these two new fields (from&to) should be usable as placeholders like {date_invoice} as well, so that I can integrate them f.e. in the salutation text without any layout change.

And as a bonus these two new fields could be preloaded with the selected export range from WorkingHours.

timo

Micha1909 Right, I mixed up the wording. I was referring to BT-72. I assume it wouldn't make sense to specify both BT-72 and also BT-73 and BT-74 - or would it in certain situations?
Currently the billing date (BT-72) is set to the same date as the invoice's invoice date.

Micha1909 My suggestion was, that these two new fields (from&to) should be usable as placeholders like {date_invoice} as well, so that I can integrate them f.e. in the salutation text without any layout change.

I am considering adding fields for the e-invoice dialog, but I am not sure about the "normal" invoice UI (for the PDF), which I want to keep as minimalistic as possible. Placeholders for the billing period placeholders wouldn't work if the billing period option is only on the e-invoicing dialog but you are creating plain non-einvoice PDFs. Adding those fields would require adding a lot of additional UI elements to the screen: 2 time picker elements, plus a checkbox to enable/disable the billing period, plus perhaps a toggle to switch between billing interval and billing date. It would make the screen a lot more complex

Micha1909

timo Currently the billing date (BT-72) is set to the same date as the invoice's invoice date.
This could be technically incorrect imo.
A product may have been delivered (or a service provided) on a different day than that invoiced.

I can understand your UI-struggling very well, but I am not sure if it's only necessary in the e-invoice-dialog. At least I would prefer these information on the PDF as well.
I think you need only two (not very prominent placed) date-pickers (from&to), pre-filled with the invoice-date (or from WorkingHours-Export). When set to the same value, it could be BT-72, otherwise BT-73 & BT-74.

[maybe off-topic]
On the other hand it took me a while to understand your current layout at all. I would have oriented it to a usual paper invoice layout. F.e. the text block in the middle, which will be displayed under the invoice positions could be placed in the UI under the positions as well.

Just my two cents in a five-minutes-drawing...

timo

Micha1909 When set to the same value, it could be BT-72, otherwise BT-73 & BT-74

Good suggestion. But what if the user doesn't want to specify any delivery date?

Micha1909 Just my two cents in a five-minutes-drawing...

thanks for the drawing. Having the dates stacked is a good idea.
The mobile app (iOS/Android) would have to have all the fields stacked, which can make the screen very long when adding two more fields.
Maybe it could make sense to combine this feature request with this one and offer just one additional button for "adding additional data" and one area to display it

Micha1909

timo Good suggestion. But what if the user doesn't want to specify any delivery date?

Good point! Then it should be not prefilled and cleanable/resetable. Neither BT-72 nor BT-73/74 are mandatory.

But maybe my suggestion was not a good idea, because with that you can't have both: BT-72 and BT-73/74.
Finally it might be the best solution to have all 3 fields. That would be specific and clean. And solve the previous mentioned (wrong highlighted) differentiation between delivery and invoice dates.

timo Maybe it could make sense to combine this feature request with this one and offer just one additional button for "adding additional data" and one area to display it

I expect it similar to the e-invoice dialog ("Mehr Felder anzeigen"), which would be fine for me - especially for these optional fields.
As another feature it's maybe possible to define, which fields a user wants under additional. (or maybe dynamic for used/unused fields) ¯_(ツ)_/¯

timo

Micha1909 Good point! Then it should be not prefilled and cleanable/resetable

While this is possible with the Windows, iOS and Android, it is not on macOS (that's why the "due date" date picker has a checkbox along with it). So that would mean another UI element...

Micha1909 because with that you can't have both: BT-72 and BT-73/74

Do you think there is a need to have both a delivery date and interval? In what case would this be required?

Micha1909

timo While this is possible with the Windows, iOS and Android, it is not on macOS (that's why the "due date" date picker has a checkbox along with it). So that would mean another UI element...

oh wow, I did not know. I never developed a macOS software.

timo Do you think there is a need to have both a delivery date and interval? In what case would this be required?

To be honest: I don't know. But there could/might be a reason to have both in the XRechnung specification.
I just thought that it would be difficult or confusing to label a combined field like "Lieferdatum oder Abrechnungszeitraum".

Rickyyy

Hi Timo,

chiming in, as I am also looking for fields specifying the time frame when a service was carried out aka "Leistungszeitraum" (afaik in Germany this is mandatory for most invoices). I do understand there is a potential struggle when adding fields and still keeping the UI as simple as possible. My suggestion would be to enable the "Leistungszeitraum" via the invoice-template setup screen so that users that don't need the functionality can simply not use it in their invoice-templates.