SDC Use Case C for papinet. E-Invoicing of Roundwood

Transcription

1 SD Use ase ID 18 December (9) SD Use ase for papinet E-Invoicing of Roundwood A Forest ompany sends an e-invoice and an Invoice Specification for roundwood to a buying company. SD Use ase - E-Invoicing of roundwood doc

2 SD Use ase ID 18 December (9) Table of ontents 1. opyright Document Version History SD Use ase "E-Invoicing of Roundwood Overview MeasuringTicket(InvoiceSpecification) BusinessAcknowledgement of MeasuringTicket Invoice(Invoice) BusinessAcknowledgement of Invoice Invoice(reditNote) Supported variants of the use case Invoicing of several versions of measuring information for the same measured delivery Invoicing of price corrections for products and additions/deductions Invoicing of products when both quantity and price have changed Invoicing when total amount is negative... 9 SD Use ase - E-Invoicing of roundwood doc

3 SD Use ase ID 18 December (9) 1. opyright opyright SD ekonomisk förening, which is opyright Owner below. All rights reserved by the opyright Owner under the laws of the United States, Sweden, the European Economic ommunity, and all states, domestic and foreign. This document may be downloaded and copied provided that all copies retain and display the copyright and any other proprietary notices contained in this document. This document may not be sold, modified, edited, or taken out of context such that it creates a false or misleading statement or impression as to the purpose or use of the specification. Use of this Standard, in accord with the foregoing limited permission, shall not create for the user any rights in or to the copyright, which rights are exclusively reserved to the opyright Owner. SD, papinet, IDEAlliance, and the members of all papinet Groups (collectively and individually, "Presenters") make no representations or warranties, express or implied, including, but not limited to, warranties of merchantability, fitness for a particular purpose, title, or noninfringement. The presenters do not make any representation or warranty that the contents of this document are free from error, suitable for any purpose of any user, or that implementation of such contents will not infringe any third party patents, copyrights, trademarks or other rights. By making use of this document, the user assumes all risks and waives all claims against Presenters. In no event shall Presenters be liable to user (or other person) for direct, indirect, special or consequential damages arising from or related to any use of this document, including, without limitation, lost profits, business interruption, loss of programs, or other data on your information handling system even if Presenters are expressly advised of the possibility of such damages. Use of Documents in papinet Implementations Documents may be used as templates for a papinet implementation. The Presenters grant the right to modify and edit them to fit an actual implementation project provided all copies display the copyright and any other proprietary notices contained in this document. Such modified documents must not be distributed beyond the trading partners implementing or maintaining a papinet connection. SD Use ase - E-Invoicing of roundwood doc

4 2. Document Version History SD Use ase ID 18 December (9) A change to the version history requires an update of date and version in the page header. The numbering format is Revision.Version, where Revision is an official document release and Version exceeding 0 is an internal work document. Please note that only if the document version has suffix 0 it is an official SD version, e.g. 1.0, 2.0, 3.0, but NEITHER 0.1, 1.2 nor The version suffix is initialized for each new revision level. Version Date Description Signature Initial public version JeNo SD Use ase - E-Invoicing of roundwood doc

5 SD Use ase ID 18 December (9) 3. SD Use ase "E-Invoicing of Roundwood 3.1 Overview This use case describes the scenario E-Invoicing of Roundwood. The Forest ompany invoices roundwood to a buying company. Deliveries of roundwood are measured and both the Forest ompany and the buying company have received measuring tickets for the deliveries from SD. SD has calculated price and amounts for measured products as well as additions and deductions when applicable. This information is supplied in the measuring tickets. Measuring information can be updated and recalculated, for example by correction of the physical measurements of the products, by price changes or by statistical adjustments. SD generates and distributes new versions of the measuring information after such changes. The invoicing process of the Forest ompany has to handle that many versions of the measuring information might exist. The Forest ompany can also add special additions and deductions during the invoicing process depending on their contract with the buyer. The Forest ompany creates an e-invoice and a detailed Invoice Specification which are both sent to the buying company as separate e-documents. The Invoice Specification contains a specification of each measuring information for all invoiced measured deliveries as well as the invoiced versions of the measuring information. The e-invoice is a papinet Invoice(Invoice) e-document and the Invoice Specification is a papinet MeasuringTicket(InvoiceSpecification) e-document. An invoice with negative total amount must be created as a papinet Invoice(reditNote) e-document. The buying company responds by sending a papinet BusinessAcknowledgement for both the Invoice(Invoice) and the MeasuringTicket(InvoiceSpecification). The Business Acknowledgement confirms if the received e-document has been validated OK and stored correctly into the receiving system database or if there are any errors in the received e- document causing processing errors. The buying company can automatically reconcile if all versions of measuring information are correctly invoiced by comparing the content of the Invoice Specification with the recieved measuring tickets from SD. Sample xml-files are provided for MeasuringTicket(InvoiceSpecification), Invoice(Invoice) and Invoice(reditNote). A printout in PDF-format of the e-document is provided for each xml-file to show the content of the xml-file. All papinet e-documents must be acknowledged by sending a papinet BusinessAcknowledgement to secure that the e-document is received and can be processed by the receiver. Examples of BusinessAcknowledgement are only provided for MeasuringTicket(InvoiceSpecification) and Invoice(Invoice) in section 3.3 and 3.5. The principle is the same for all other e-documents. In this use case the Forest ompany is the supplier as well as the legal seller. papinet e-documents must be wrapped into a papinet Envelope before they are sent. The xmlfile that is sent to the receiving partner consists of the papinet Envelope and the papinet e-document. Routing and processing of e-documents are much easier to implement in a consistent way by using the papinet Envelope. Attachments to the e-document can also be wrapped and sent in the papinet Envelope. Additional transmission envelopes can be used by the message service when transmitting the message. SD Use ase - E-Invoicing of roundwood doc

6 SD Use ase ID 18 December (9) 3.2 MeasuringTicket(InvoiceSpecification) The Forest ompany creates an Invoice Specification with measuring information for all measured deliveries that will be invoiced to a buying company for a specific time period. Invoiced versions of measuring information are specified. The Invoice Specification has a reference to the invoice number of the e-invoice. Forest ompany sends a MeasuringTicket(InvoiceSpecification) to the buying company. Scope: The Invoice Specification contains a specification of measuring information for deliveries to two ship-to locations. It is the first version of the Invoice Specification (TransactionHistoryNumber = 1). Only original versions of measuring information exist. PDF- file: 3.2 Invoice Specification IS yyyy-mm-dd.pdf XML-file: 3.2 MeasuringTicket(InvoiceSpecification) IS yyyy-mm-dd.xml 3.3 BusinessAcknowledgement of MeasuringTicket The buying company responds to the sender of the MeasuringTicket with a BusinessAcknowledgement as a system acknowledgement for the received papinet e-document MeasuringTicket(InvoiceSpecification). The Business Acknowledgement confirms if the received e-document has been validated OK and stored correctly into the receiving system database or if there are any errors in the received e-document causing processing errors. The sender of the MeasuringTicket e-document should have in place an error resolution process that routes the errors to the correct organisation for resolution. Scope: Acknowledgement of the received Invoice Specification in section 3.2. Status is Success. XML-file: 3.3 BusinessAcknowledgement of MeasuringTicket(InvoiceSpecification) IS yyyy-mm-dd.xml 3.4 Invoice(Invoice) The Forest ompany creates an Invoice for all measured deliveries that will be invoiced to a buying company for a specific time period. An Invoice Specification specifies all invoiced versions of measuring information for all measured deliveries. The Invoice has a reference to the document number and the version of the Invoice Specification. Forest ompany sends an Invoice(Invoice) to the buying company. Scope: Deliveries to two ship-to locations are invoiced. The content of the Invoice is specified in detail by the Invoice Specification in section 3.2. PDF- file: 3.4 Invoice yyyy-mm-dd.pdf XML-file: 3.4 Invoice(Invoice) yyyy-mm-dd.xml 3.5 BusinessAcknowledgement of Invoice The buying company responds to the sender of the Invoice with a BusinessAcknowledgement as a system acknowledgement for the received papinet e-document Invoice(Invoice). The Business Acknowledgement confirms if the received e- document has been validated OK and stored correctly into the receiving system database or if there are any errors in the received e-document causing processing errors. The sender of the Invoice e-document should have in place an error resolution process that routes the errors to the correct organisation for resolution. Scope: Acknowledgement of the received Invoice in section 3.4. Status is Success. XML-file: 3.5 BusinessAcknowledgement for Invoice(Invoice) yyyy-mm-dd.xml SD Use ase - E-Invoicing of roundwood doc

7 3.6 Invoice(reditNote) SD Use ase ID 18 December (9) An invoice is cancelled by issueing a redit Note. The Forest ompany creates a redit Note to cancel an Invoice that was issued incorrectly. The redit Note has to contain a reason for issueing the redit Note. The amounts credited are positive in the redit Note. The redit Note must have a reference to the invoice number of the original Invoice. Forest ompany sends an Invoice(reditNote) to the buying company. Scope: The Invoice in section 3.4 is credited. There is no Invoice Specification when a whole invoice is credited. PDF- file: 3.6 reditnote yyyy-mm-dd.pdf XML-file: 3.6 Invoice(reditNote) yyyy-mm-dd.xml SD Use ase - E-Invoicing of roundwood doc

8 SD Use ase - E-Invoicing of roundwood doc SD Use ase ID 4. Supported variants of the use case 18 December (9) 4.1 Invoicing of several versions of measuring information for the same measured delivery The Forest ompany is invoicing measured deliveries for a specific time period. There are two new versions of measuring information for an already invoiced delivery. Quantities have changed for the already invoiced delivery. The first new version has negative quantities and amounts that cancels earlier invoiced version. The second new version has the updated quantities and current amounts that is invoiced. Both versions are specified on the Invoice Specification. The Invoice has a reference to the document number and the version of the Invoice Specification. The Forest ompany sends a MeasuringTicket(InvoiceSpecification) and an Invoice(Invoice) to the buying company. Scope: Invoiced are two versions of measuring information for an already invoiced delivery and a new original version of measuring information for another measured delivery. There are two ShipTo locations. Quantities have changed for the already invoiced delivery. PDF- file: 4.1 Invoice Specification IS yyyy-mm-dd.pdf PDF- file: 4.1 Invoice yyyy-mm-dd.pdf XML-file: 4.1 MeasuringTicket(InvoiceSpecification) IS yyyy-mm-dd.xml XML-file: 4.1 Invoice(Invoice) yyyy-mm-dd.xml 4.2 Invoicing of price corrections for products and additions/deductions The price list is updated and price has changed for products and additions/deductions. New versions of measuring information are created for already invoiced deliveries that are affected by the new prices. The new versions for this price change contain only the billable difference to earlier invoiced amounts. The invoiced quantities are not changed. The Forest ompany sends a MeasuringTicket(InvoiceSpecification) and an Invoice(Invoice) to the buying company. Scope: Invoiced are new versions of measuring information for three already invoiced deliveries because of price changes. The new versions contain only the billable difference to earlier invoiced amounts. The invoiced quantities are not changed. There are two ShipTo locations. PDF- file: 4.2 Invoice Specification IS yyyy-mm-dd.pdf PDF- file: 4.2 Invoice yyyy-mm-dd.pdf XML-file: 4.2 MeasuringTicket(InvoiceSpecification) IS yyyy-mm-dd.xml XML-file: 4.2 Invoice(Invoice) yyyy-mm-dd.xml 4.3 Invoicing of products when both quantity and price have changed Both quantities and prices have changed for already invoiced deliveries, for example caused by statistical adjustments. New versions of measuring information are created for already invoiced deliveries that are affected by the changes. The new versions contain only the billable difference to earlier invoiced quantities and amounts. The Forest ompany sends a MeasuringTicket(InvoiceSpecification) and an Invoice(Invoice) to the buying company. Scope: Invoiced are new versions of measuring information for three already invoiced deliveries because of quantity and price changes. The new versions contain only the billable difference to earlier invoiced quantities and amounts. There are two ShipTo locations. PDF- file: 4.3 Invoice Specification IS yyyy-mm-dd.pdf PDF- file: 4.3 Invoice yyyy-mm-dd.pdf XML-file: 4.3 MeasuringTicket(InvoiceSpecification) IS yyyy-mm-dd.xml XML-file: 4.3 Invoice(Invoice) yyyy-mm-dd.xml

9 SD Use ase ID 4.4 Invoicing when total amount is negative 18 December (9) Both price corrections for an already invoiced delivery and an original version of measuring information for a measured delivery are invoiced. The total amount in the Invoice Specification is negative. A redit Note is then issued instead of an Invoice, since an Invoice may not have a negative total amount. redited amounts are positive in the redit Note. The Forest ompany sends a MeasuringTicket(InvoiceSpecification) and an Invoice(reditNote) to the buying company. Scope: The total amount in the Invoice Specification is negative. A redit Note is issued. Two versions of measuring information are invoiced. The version of the measuring information for the price correction contains only the billable difference to earlier invoiced amounts. The original version of measuring information for the measured delivery contains two products. There is one ShipTo location. PDF- file: 4.4 Invoice Specification IS yyyy-mm-dd.pdf PDF- file: 4.4 Invoice yyyy-mm-dd.pdf XML-file: 4.4 MeasuringTicket(InvoiceSpecification) IS yyyy-mm-dd.xml XML-file: 4.4 Invoice(Invoice) yyyy-mm-dd.xml SD Use ase - E-Invoicing of roundwood doc