RE: [ubl-dev] DeliveryPeriod vs InvoicePeriod

Roland,

why can you not use the InvoicePeriod that is available on the InvoiceLine in UBL 2.1 PRD2?
The description for that element in states:
An association to period(s) to which the Invoice Line applies

That is exactly what you are looking for when I read your email correctly.

The first invoice line for the subscription upfront would show an InvoicePeriod/StartDate and EndDate that is one month in advance. (example June 1st - June 30th)
The second line is for the usage charges and that would show an InvoicePeriod/StartDate and EndDate that covers the previous month. (all usage charges upto and including May 31st)

(suggestion: Do not set an StartDate on the usage charges ... in the telecoms business you can always receive call records too late (roaming charges, mediation errors etc ) so they might have a date that is earlier then your expected start date ...)

Kees

Van: Roland Hommes - Rhocon [roland@rhocon.nl]
Verzonden: dinsdag 22 mei 2012 19:31
To: 'Universal Business Language'
Onderwerp: [ubl-dev] DeliveryPeriod vs InvoicePeriod

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

ubl-dev message