[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (UBL-8) Refer to multiple orders in Invoice and Credit Note header
[ https://issues.oasis-open.org/browse/UBL-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43248#comment-43248 ]
Kees Duvekot edited comment on UBL-8 at 8/13/14 2:20 PM:
---------------------------------------------------------
https://lists.oasis-open.org/archives/ubl/201408/msg00016.html
========
Kenneth and others,
Let's work out an example:
Party A has placed 2 orders with each having 2 lines each for BEER and SODA
<code>
Order 1
Line 1.1
6 cases of BEER
Line 1.2
4 cases of SODA
Order 2
Line 2.1
6 cases of SODA
Line 2.2
4 cases of BEER
</code>
These orders have been send to Party B and have been delivered in whole. So 10 Cases each has been delivered.
So now Party B would like to invoice Party A for this
<code>
Invoice 2014-001
Invoice Line 1
10 cases of BEER
OrderLineRef 1.1
OrderLineRef 2.2
Invoice Line 2
10 cases of SODA
OrderLineRef 1.2
OrderLineRef 2.1
<code>
By setting up the invoice like this it gives party A enough information to check what has been delivered and what is being invoiced in his systems.
I would go even further and I would split the invoice in 4 lines each. Because how do you know how many is invoiced on each line of the order? Is it split 5/5 against both orders?
In this case the total equals what has been ordered .. but if there a deviations, or backorders etc .. then how do you know what to check and how to validate?
If the invoice would look like this:
<code>
Invoice 2014-001
OrderRef 1
OrderRef 2
Invoice Line 1
10 cases of BEER
Invoice Line 2
10 cases of SODA
</code>
Then you only have a order reference ... but you know even less.
This is why I feel it is always in everybody's interest to be specific and always reference back to the individual lines.
And when you are dealing with fluctuating prices (between orders, or even between deliveries) then it becomes even more important to have a correct reference or when the price on the invoice is different then what has been agreed on the order etc etc etc
It could also be that the recipient of the invoice is using a different form of inventory valuation that is requiring them to link each and every invoice to the individual receipts. Because you can never be sure, again it would be wise to always reference back to the individual lines.
Also in the systems of Party B both orders are separate orders (otherwise you can now know which ones to invoice) so if they are a copy of the original order you also know exactly what has been delivered on each line and what to charge the customer.
Actually by omitting al these details in the invoice you take away a lot of knowledge from your customer and you increase the rules in the invoicing system (that needs to know if an order is being completely invoiced or not etc etc)
It would also be interesting to see if one of the largest users/processor of UBL Invoices (TradeShift) has found it limiting that on a header level you can only specify one orderreference and not multiple...
Kees
was (Author: kduvekot):
https://lists.oasis-open.org/archives/ubl/201408/msg00016.html
========
Kenneth and others,
Let's work out an example:
Party A has placed 2 orders with each having 2 lines each for BEER and SODA
Order 1
Line 1.1
6 cases of BEER
Line 1.2
4 cases of SODA
Order 2
Line 2.1
6 cases of SODA
Line 2.2
4 cases of BEER
These orders have been send to Party B and have been delivered in whole. So 10 Cases each has been delivered.
So now Party B would like to invoice Party A for this
Invoice 2014-001
Invoice Line 1
10 cases of BEER
OrderLineRef 1.1
OrderLineRef 2.2
Invoice Line 2
10 cases of SODA
OrderLineRef 1.2
OrderLineRef 2.1
By setting up the invoice like this it gives party A enough information to check what has been delivered and what is being invoiced in his systems.
I would go even further and I would split the invoice in 4 lines each. Because how do you know how many is invoiced on each line of the order? Is it split 5/5 against both orders?
In this case the total equals what has been ordered .. but if there a deviations, or backorders etc .. then how do you know what to check and how to validate?
If the invoice would look like this:
Invoice 2014-001
OrderRef 1
OrderRef 2
Invoice Line 1
10 cases of BEER
Invoice Line 2
10 cases of SODA
Then you only have a order reference ... but you know even less.
This is why I feel it is always in everybody's interest to be specific and always reference back to the individual lines.
And when you are dealing with fluctuating prices (between orders, or even between deliveries) then it becomes even more important to have a correct reference or when the price on the invoice is different then what has been agreed on the order etc etc etc
It could also be that the recipient of the invoice is using a different form of inventory valuation that is requiring them to link each and every invoice to the individual receipts. Because you can never be sure, again it would be wise to always reference back to the individual lines.
Also in the systems of Party B both orders are separate orders (otherwise you can now know which ones to invoice) so if they are a copy of the original order you also know exactly what has been delivered on each line and what to charge the customer.
Actually by omitting al these details in the invoice you take away a lot of knowledge from your customer and you increase the rules in the invoicing system (that needs to know if an order is being completely invoiced or not etc etc)
It would also be interesting to see if one of the largest users/processor of UBL Invoices (TradeShift) has found it limiting that on a header level you can only specify one orderreference and not multiple...
Kees
> Refer to multiple orders in Invoice and Credit Note header
> ----------------------------------------------------------
>
> Key: UBL-8
> URL: https://issues.oasis-open.org/browse/UBL-8
> Project: OASIS Universal Business Language (UBL) TC
> Issue Type: New Feature
> Components: Documents and business objects
> Reporter: Ken Holman
> Assignee: Ken Holman
> Priority: Minor
>
> TC member Roberto Cisternino requests a change in the cardinality for order references at the header level of invoices and credit notes:
> https://lists.oasis-open.org/archives/ubl/201408/msg00005.html
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]