OASIS Universal Business Language (UBL) TC

Dear TC


During the review process of OIOUBL we found out that we are missing payment information on a statementline. There are no place to specify where to place what has been payed and when it has been payed. And to my mind this is a fundamental requirement for a Statement.

There are ways that this can be worked out, like using a document reference to specify the date of payment, applying an extension for this or specifying a new documenttype, localy used. Since the problem is global, the same for all usage of UBL I would like the UBL TC to suggest a solution for this, so every one does not using their own fixes. 

Kind regards


Peter

Peter


It’s a bit convoluted, but you could

for the date

use the PaymentDueDate in associated PaymentMeans; you’d have to include a PaymentMeansCode also

for the amount

link the associated PaymentTerms vie the PaymentMeansID (in PaymentTerms)
use the PaymentTerms.Amount



It may be simpler just to use the amounts in StatementLine itself as we have talked about already if a paid amount is all that’s required.


M




Mark Leitch

Director - Tritorr Ltd

tel.:       +44 1932 821112

cell.:      +44 7881 822999

mail:      ml@tritorr.com

skype:    wmarkle

site:       www.tritorr.com




From: Peter Borresen <PLB@itst.dk>

Date: Tue, 7 Nov 2006 14:26:28 +0100

To: <ubl@lists.oasis-open.org>

Conversation: Missing information in Statement and reminder document

Subject: [ubl] Missing information in Statement and reminder document


Dear TC


During the review process of OIOUBL we found out that we are missing payment information on a statementline. There are no place to specify where to place what has been payed and when it has been payed. And to my mind this is a fundamental requirement for a Statement.



There are ways that this can be worked out, like using a document reference to specify the date of payment, applying an extension for this or specifying a new documenttype, localy used. Since the problem is global, the same for all usage of UBL I would like the UBL TC to suggest a solution for this, so every one does not using their own fixes.



Kind regards


Peter