[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ubl-dev] DeliveryPeriod vs InvoicePeriod
Roland, InvoicePeriod as exactly what you say it is, an informative date range that can help the recipient of the invoice to better understand what is
invoiced and what period this charge is covering. And this also means that other invoices might have (different) charges that cover the same period. They way I read these fields you can use these if you want to show a period and is most useful when there
is no reference to a specific goods movement. And if you want to relate a specific invoice(line) to a specific delivery you can use the DespatchLine- or ReceiptLineReference options. It is not meant to be used for Tax related information etc. For that there is the TaxPointDate (available both on header and line level) that can
be used to show what the relevant date is for Taxation purposes. Did you read the “sematisch model e-Factureren” (dutch only) that was created by Logius? You can find it here:
In there they also discuss the relevant legal (dutch) aspects of Tax dates and other element of an electronics invoice and also covers UBL. Kees Van: Roland Hommes - Rhocon
[mailto:roland@rhocon.nl]
Thanks Kees, There is a but … The definition of the InvoicePeriod is different of what my ‘RealizedDeliveryPeriod’ is. You can put any invoiceperiod dates on an invoice and
it doesn’t have anything to do with the deliveries that are being made (past or future). As a consultant I can give my contractor multiple invoices on the period ‘may’. The same goes for payments upfront where delivery is scheduled sometime in the future;
what would be the invoiceperiod in that case? And what if that amount gets combined with something that already has been delivered? Does that change the invoiceperiod dates? For me the invoiceperiod means nothing, they are just some dates which may or may not be overridden or complemented with other invoices. That is
why Dutch tax states that it is the moment of delivery (or agreement to deliver, for future stuff) is the date that serves as the base for when the invoice needs to be sent and the VAT has to be calculated. Sure I can abuse the invoiceperiod as my ‘RealizedDeliverPeriod’, but it’s abuse nevertheless.
Thanks for correcting my overlooking the line/invoiceperiod in 2.1. Cheers, Roland Van: Duvekot, Kees
[mailto:kduvekot@Wehkamp.nl]
Roland, Van: Roland Hommes
- Rhocon [roland@rhocon.nl] I have a semantic issue that you may have dealt with before. On an invoice I’m not really interested in the InvoicePeriod (the period that is covered by the invoice as a whole). What I’m interested in is
the realized delivery period which can occur on Invoice AND/OR on Line and cover a startDate and EndDate. This plays a particular role when dealing with telecom providers. The invoice covers two lines: one for the subscription which is paid upfront and a line
covering the calls and internet consumption made during the month or period before the invoice is being sent. So I’m having a problem with the meaning of InvoicePeriod: I’d rather have ‘RealizedDeliveryPeriod’ and, I need this period to appear on line level which is not the case in both 2.0 and 2.1. Custom Invoice time? Or is there a better solution? Thanks, Roland Logius/NL |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]