From: Sonia Guerci
iSolutions s.n.c.
Noceto, PARMA (ITALY)
Dear Mr. Chiusano,
monitoring the UBL
LCSC mail archive I’ve found that you speak Italian, so I’m taking
the liberty to pose a few questions.
We are trying to develop a UBL compliant Web Service for
electronic invoicing.
Basically we want to export and import invoice data in XML
format validating the files with the UBL_Invoice.xsd
schema
We’re experiencing problems fitting the fields of the
typical Italian invoice in the XML elements.
Mainly we don’t know exactly where to place Payment
Due dates.
If I got it right the Invoice should contain the Seller’s
instructions that the buyer needs in order to trigger payment.
The problem with the actual schema is that in the Italian invoice
we usually have more than one “payment due date”. Buyers have the
chance to pay a determined percentage of the ToBePaidTotalAmount by each due
date.
We are now coping with this matter putting the entire
description in the element PaymentTerms/Note
A typical PaymentTerms/Note that we use
is “RI.BA. 30/60gg” which translates to
“Bank Receipt 30/60days”.
If the Invoice/IssueDate
was 2003/01/15 the buyer could pay, say, 50% of the ToBePaidTotalAmount
by the end of February 2003 and the remaining percentage by the end of
March 2003.
Or the buyer could pay 100% of the taxable amount by one
date and 100% of
the tax amount by the other.
To effectively use the Schema we would need, for example, a
cardinality 0..n of SettlementPeriod and additional
elements to contain the percentages of ToBePaidTotalAmount
and TotalTaxAmount
(ToBePaidTotalAmount
- LineExtensionTotalAmount) due (or directly
the Amounts due).
Something like this:
<cat:PaymentTerms>
<cat:ID />
<cat:Note>RI.BA. 30/60gg FINE MESE</cat:Note>
<cat:FromEventCode>InvoiceIssueDate</FromEventCode >
<cat:SettlementPeriod>
<cat:DurationMeasure unitCode="DAYS">30</cat:DurationMeasure>
<cat:TaxTotalAmountPercentRateNumeric>50</cat:TaxTotalAmountPercentRateNumeric >
<cat:LineExtensionTotalAmountPercentRateNumeric>50</cat:LineExtensionTotalAmountPercentRateNumeric>
</cat:SettlementPeriod
>
<cat:SettlementPeriod>
<cat:DurationMeasure unitCode=" DAYS ">60</cat:DurationMeasure>
<cat:TaxTotalAmountPercentRateNumeric >50</cat:TaxTotalAmountPercentRateNumeric >
<cat:LineExtensionTotalAmountPercentRateNumeric >50</cat:LineExtensionTotalAmountPercentRateNumeric >
</cat:SettlementPeriod
>
</cat:PaymentTerms>
This would be great but increasing the cardinality of
SettlementPeriod should suffice.
My question is:
Is there a chance that the schema in the final release will
allow more that one payment due date? If not, do you see an alternative to the
use of the unstructured Note element?
We would really appreciate any help you could give us.
Sincerely,
Sonia Guerci