[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ubl-psc] Weights and measures in Order documents
All,
If the Statement is for information purposes only, what
does a company do that uses the Statement as the only billing document?. As an
example in the telecommunication industry, some very large well known providers
refuse invoices and only accept statements. This is what they pay from and it
may include allowances and charges. They will not pay from a document that is
for information purposes only. They call this Consolidated Billing. If the
Statement is for a single phone number or department and the allowance or charge
applies to the total amount, it may not be possible or practical to split this
at the line level.
Statement billing is also common in Professional Services
industries. The Statement is sent and no invoice is
generated.
Regards,
Sylvia
From: Peter Larsen Borresen [mailto:plb@itst.dk] Sent: Wednesday, December 14, 2005 3:18 AM To: ubl-psc@lists.oasis-open.org; Mikkel Hippe Brun Subject: SV: [ubl-psc] Weights and measures in Order documents Hi
PSC
Mark
and I had a meeting this morning and we found out that the values could have a
meening in the order response, order response simple and the depatch advide
(perhaps even in the receipt advice). But it they should be packaged into a
RespondedQuantityTotal ABIE (or an other name e.g. document
Measure) so it is more clear what they are used for.
Mark
think that TaxTotal in order response should not be qualified with "proposed".
He does not see the reason for qualifying it in the order either. I would like
it qualified in the order with "expected" in stead of
proposed.
We
also found the need for clearifying that a UBL Statement is for information
purpose only. I can not be used a base for billing purpose like a statemen from
Euro card. Therefore we agree with Mikkel that it is a bad idea to have
AllowanceCahnge on a statement
For
the fore simple issues on Mikkels list we found that
-StatementDocumentReference should be
removed
-Order
change should have a validityPeriod
-OrderChange should have a reference to one and only
one order.
-We
should consider having only one order for a order cancellation or note that this
is best practice.
-SellersOrderId must be changed to SalesOrderId and
BuyersOrderId to ID in Order Response
/Peter
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]