Diff for Storing Payment Reference in UBL
Fri, 2018-01-05 07:20 by yingleekit | Fri, 2018-01-05 07:26 by yingleekit | ||
---|---|---|---|
Changes to Body | |||
Line 1 | Line 1 | ||
- | <div>
| ||
- | <br />
| ||
- | </div>
| ||
<div>
| <div>
| ||
Dear guys/gals
| Dear guys/gals
| ||
Line 12 | Line 9 | ||
</div>
| </div>
| ||
<div>
| <div>
| ||
- | <br />
| + | <strong>Invoice/ PaymentMeans / PaymentID</strong>
|
</div>
| </div>
| ||
<div>
| <div>
| ||
- | Invoice/ PaymentMeans / PaymentID
| ||
- | </div>
| ||
- | <div>
| ||
- | <br />
| ||
</div>
| </div>
| ||
<div>
| <div>
| ||
Line 30 | Line 23 | ||
</div>
| </div>
| ||
<div>
| <div>
| ||
- | <br />
| ||
</div>
| </div>
| ||
<div>
| <div>
| ||
- | Currently in my client company, they have a legacy system which also creates/read UBL formatted invoices, <span style="font-size: 12.8px">but they are reading and writting it to </span>
| + | Currently in my client company, they have a legacy system which also creates/read UBL formatted invoices, but they are reading and writting it to
|
</div>
| </div>
| ||
<div>
| <div>
| ||
- | <br />
| ||
</div>
| </div>
| ||
<div>
| <div>
| ||
- | Invoice/ PaymentMeans/ InstructionNote/
| + | Invoice/ PaymentMeans/ InstructionNote/
|
</div>
| </div>
| ||
<div>
| <div>
| ||
Line 45 | Line 36 | ||
</div>
| </div>
| ||
<div>
| <div>
| ||
- | <br />
| ||
</div>
| </div>
| ||
<div>
| <div>
| ||
- | Will it cause any problems, if we stored the Payments Reference to
| + | Will it cause any problems, if we stored the Payments Reference there?
|
</div>
| </div>
| ||
<div>
| <div>
| ||
- | <br />
| + | Or is it a hard rule , that payment reference needs to be stored in "Invoice/ PaymentMeans / PaymentID" only?<span style="font-size: 12.8px"> </span>
|
</div>
| </div>
| ||
<div>
| <div>
| ||
- | Invoice/ PaymentMeans/ InstructionNote/
| + | |
- | </div>
| + | |
- | <div>
| + | |
- | Invoice/ PaymentTerms/ Note?
| + | |
- | </div>
| + | |
- | <div>
| + | |
- | <br />
| + | |
- | </div>
| + | |
- | <div>
| + | |
- | or is it a hard rule , that payment reference needs to be stored in "Invoice/ PaymentMeans / PaymentID" only?
| + | |
- | </div>
| + | |
- | <div>
| + | |
- | <br />
| + | |
</div>
| </div>
| ||
<div>
| <div>
| ||
Line 72 | Line 50 | ||
</div>
| </div>
| ||
<div>
| <div>
| ||
- | For example: If system X get Payment Reference from "Invoice/ PaymentMeans / PaymentID", when reading my client company legacy UBL, they wont get the payment reference.
| + | For example: If system X get Payment Reference from "Invoice/ PaymentMeans / PaymentID", when reading my client company legacy UBL, they wont get the payment reference.
|
</div>
| </div>
| ||
<div>
| <div>
| ||
- | <br />
| + | |
</div>
| </div>
| ||
<div>
| <div>
| ||
- | This brings me to my next question, does all UBL implementor uses "Invoice/ PaymentMeans / PaymentID" to store payment reference?
| + | This brings me to my next question, does all UBL implementor uses "Invoice/ PaymentMeans / PaymentID" to store payment reference?
|
</div>
| </div>
| ||
<div>
| <div>
| ||
Line 87 | Line 65 | ||
</div>
| </div>
| ||
<div>
| <div>
| ||
- | Your reply is greatly appreaciated.<span style="font-size: 12.8px"> </span>
| + | Your reply is greatly appreaciated.
|
</div>
| </div>
| ||
<div>
| <div>
| ||
- | <br />
| + | |
</div>
| </div>
| ||
<div>
| <div>
| ||
- | <br />
| ||
</div>
| </div>
| ||
<div>
| <div>
| ||
- | <br />
| ||
- | </div>
| ||
- | <div>
| ||
- | <br />
| ||
- | </div>
| ||
- | <div>
| ||
- | <br />
| ||
- | </div>
| ||
- | <div>
| ||
- | |||
</div>
| </div>
| ||
Storing Payment Reference in UBL
Dear guys/gals
I am new to UBL and its implementation for invoices.
Would like to clarify if my understanding of the below elements usage is correct or not.
Invoice/ PaymentMeans / PaymentID
I am working on an ERP system which needs to create/read UBL formatted invoices (purchase and Sales).
and i was wondering where i can put my payment reference information. From the UBL specification website (http://www.datypic.com/sc/ubl20/t-ns19_InvoiceType.html)
it seems that the only suitable place is to put it in "Invoice/ PaymentMeans / PaymentID".
Currently in my client company, they have a legacy system which also creates/read UBL formatted invoices, but they are reading and writting it to
Invoice/ PaymentMeans/ InstructionNote/
Invoice/ PaymentTerms/ Note
Will it cause any problems, if we stored the Payments Reference there?
Or is it a hard rule , that payment reference needs to be stored in "Invoice/ PaymentMeans / PaymentID" only?
Am i correct to think that, we can put the payment reference in any elements in the UBL, as long the receiving system can identify from the elements it is a paymente reference.
For example: If system X get Payment Reference from "Invoice/ PaymentMeans / PaymentID", when reading my client company legacy UBL, they wont get the payment reference.
This brings me to my next question, does all UBL implementor uses "Invoice/ PaymentMeans / PaymentID" to store payment reference?
Thank you in advance
Your reply is greatly appreaciated.