Hi Matija,
I sympathise that you want to send just those parts of the document
that are either required or can be mapped to your system. I don't think
there is anything technically wrong with combining two bits of the advice
from the others to your question and sending the UBL 2.1 Invoice with
just the subscriber consumption part of the utility statement inside a UBL
extension in the invoice. It depends whether you need to standardise
on using the Utility Statement or whether you just need to send the data
the reciever needs.
Best regards
Steve
---
Stephen D Green
On 19 June 2013 11:17, Matija Tušek <> wrote:
Hello,
I have successfully created UBL 2.1 Invoice and Utility Statement as supplement to that Invoice.
How can I extend UBL Invoice 2.1 with Utility Statement to have one master schema with Invoice and it's supplement?
- -
Do I need to fill parts in Utility Statement like Sender/Receiver/Copy Indicator/Issue Date/Customer etc - because I already have them in main Invoice?
- -
The main part that I need from Utility Statement is - Subscriber Consumption
and I've mapped everything I needed.
-
The main idea is to send to our partner UBL 2.1 Invoice with Utility Statement supplement and attached invoice pdf.
Thanks
