4 1. General information 1.1. Preface Electronic invoicing is a significant step towards the wider use and knowledge of electronic business. An e-invoice is a modern, reliable, secure, cost-efficient, and practically paperless method of handling and processing invoices for goods, services, and other expenses. E-invoicing is a solution for invoicing electronically, which suits both large and small companies. Both companies and private consumers can receive invoices in electronic format. This document describes Swedbank Latvia e-invoice format, which is based on Estonia E-invoice format, with small adoptions needed for Latvia market. The recipients can receive e-invoices through their e-banking accounts. An e-invoice is graphically presented on the computer screen so that its appearance is similar to that of an invoice printed on paper. This facilitates invoice archiving, distribution, approval and payment procedures. XML: 1.2. References Legislation: W3C XML Schema recommendation W3Schools XML Tutorial Value Added Tax Act Accounting Act Electronic Documents Act Estonia E-invoice description: Estonian Bank association web page Page 4 of 38

6 2.3. Header Header contains file specific elements, <Header> <Date> </Date> <FileId>66488</FileId> <AppId>EINVOICE</AppId> <Version>1.0</Version> </Header> Tag Description Type / Value list Mandatory Displayed using standard template Date Determines the date when the DateType Info is not for displaying file is generated. FileId Unique identification of the file ShortTextType Info is not for displaying given by the system. Used to prevent double-processing the same file. AppId Apllication identifier. EINVOICE EInvoiceType Info is not for displaying is used for e-invoice to internet bank. Version The version of the standard. ShortTextType Info is not for displaying Notes Page 6 of 38

9 2.5. InvoiceParties InvoiceParties defines different companies/persons involved with this invoice (the seller and buyer, the recipient of the invoice, the recipient of the goods/services and the payer of the invoice) <InvoiceParties> <SellerParty> </SellerParty> <BuyerParty> </BuyerParty> <RecipientParty> </RecipientParty> <DeliveryParty> </DeliveryParty> <PayerParty> </PayerParty> <FactorParty> </FactorParty> </InvoiceParties> Tag Description Type / Value list Mandat ory SellerParty Describes the seller (name, SellerPartyReco address, etc). See rd SellerPartyRecord Record for details [on page 29] BuyerParty Describes the buyer of the invoice (name, id code etc.). See BillPartyRecord for details [on page 26]. RecipientParty This invoice group is used when the invoice recipient is not the buyer but for example, an accounting firm or other agent acting on the buyer s behalf. See BillPartyRecord for details [on page 26]. DeliveryParty Delivery party details are used when the delivery to be invoiced is addressed to someone other than the buyer. See BillPartyRecord for details [on page 26]. PayerParty This invoice group is used when the payer of the invoice is not the buyer. See BillPartyRecord for details [on page 26]. FactorParty Party to whom SellerParty is selling its accounts receivable invoices [on page 26]. Remark: Factoring information can be used only after separate agreement with bank Displayed using standard template * BillPartyRecord * BillPartyRecord * BillPartyRecord * BillPartyRecord BillPartyRecord Notes Page 9 of 38

13 VAT TotalVATSum TotalSum TotalToPay Currency Accounting Extension Describes value-added tax. See VATRecord for details [on page 30]. VAT elements have to be presented for each VATRate. Value of VAT elements has to be equal to InvoiceItemGroup/ItemEntry/VAT amounts. Describes the total sum of the all value-added tax sums. Invoice total sum with taxes. Remark: Amount must be the same as in PaymentInfo block in tag PaymentTotalSum Total to pay sum. In credit invoices the sum has to be Three-character currency code as specified in the ISO 4217 standard. Accounting element describes information needed to automate accounting transactions. See AccountingRecord for details [on page 23]. Describes additional elements that are needed to present in this section. See ExtensionRecord for details [on page 28]. VATRecord * 0-n Decimal2Fractio ndigitstype Decimal2Fractio ndigitstype Decimal2Fractio ndigitstype CurrencyType AccountingReco rd ExtensionRecor d * 0-n Page 13 of 38

21 2.11. Footer Footer element shows the total number of the invoices and the total sum of all the invoices in a file. <Footer> <TotalNumberInvoices>143</TotalNumberInvoices> <TotalAmount> </TotalAmount> </Footer> Tag Description Type / Value list TotalNumberInvoices TotalAmount Number of invoices in the file. Used for error detection. Count of Invoice elements in the file. Sum of PaymentTotalSum elements of all the invoices in the file. Different currencies are not taken into account. Used for error detection. xs:positiveinte ger Decimal2Fracti ondigitstype Manda tory Displayed using standard template Info is not for displaying Info is not for displaying Notes Page 21 of 38

28 ExtensionRecord ExtensionRecord type allows presentation of additional information. For example some elements which have not been defined in the e-bill structure, but are needed to describe necessary information. <Extension extensionid="licencenumber"> <InformationName> Licenze </InformationName> <InformationContent> MAM118045A </InformationContent> </Extension> Tag Description Type / Value list extensionid The identification code of the ShortTextT extension element. When ype defining values to this element it is recommended to follow XML naming conventions. InformationName Name of the presented NormalTex information. ttype Mandatory Displayed using standard template Info is not for displaying * InformationContent Information. LongType * CustomContent The <any> element. The <any> element enables us to extend the XML document with elements not specified by the schema. * It is different in different invoice blocks Notes Attrib ute XML naming conventions In order to enforce a consistent capitalization and naming convention across all XML specifications "Upper Camel Case" (UCC) and "Lower Camel Case" (LCC) Capitalization styles SHALL be used. UCC style capitalizes the first character of each word and compounds the name. LCC style capitalizes the first character of each word except the first word. All names are in English. Element names SHALL be in UCC convention (example: <UpperCamelCaseElement/>). Attribute names SHALL be in LCC convention. (example: <UpperCamelCaseElement lowercamelcaseattribute="whatever"/>). Acronyms SHOULD be avoided, but in cases where they are used, the capitalization SHALL remain (example: XMLSignature). Underscore ( _ ), periods (. ) and dashes ( - ) MUST T be used (don't use: header.manifest, stock_quote_5, commercial-transaction, use HeaderManifest, stockquote5, CommercialTransaction instead). All complextype definitions use suffix Record. All simpletype definitions use suffix Type. Page 28 of 38

This business document is used when invoicing delivered and returned trade items. One invoice corresponds to one delivery or one return. The transaction is also used when crediting. If a calloff has been

ebinterface 4.0 The Austrian e-invoice standard Note: This documentation is a translation of the German documentation of the ebinterface standard 4.0, available on http://www.ebinterface.at. This documentation

May 2016 Please note: The SIX Trade Repository (SIX TR) has not yet been registered with FINMA. It is therefore not yet an authorized Swiss trade repository. The content of this documentation is without

Invoice Entity name: Invoice Comment: This transaction is used to invoice goods or services which have been supplied. One invoice corresponds to one delivery. If a calloff has been split into several deliveries,

S.2 STRUCTURE OF AN EDIFACT TRANSMISSION This section is substantially based on the ISO 9735 document: EDIFACT application level syntax rules, first released on 1988-07-15, amended and reprinted on 1990-11-01,

Secure Envelope specification for Corporate Access File Transfer 2/13/2015 Version 1.0.3 This document defines how a file (e.g. a payment file) which will be sent to the bank is digitally signed by the

Message Containers and API Framework Notices Copyright 2009-2010 Motion Picture Laboratories, Inc. This work is licensed under the Creative Commons Attribution-No Derivative Works 3.0 United States License.

HansaWorld University Point Of Sales (POS) Training Material HansaWorld Ltd. February 2010 Version 6.1 Table Of Contents INTRODUCTION...5 What is Point Of Sales?...5 THE 4 DIFFERENT WAYS OF USING POS...6

IS-XML Structure and Interface Specification for September 2014 1 / 23 30-Oct-14 This document may not be disclosed, reproduced, copied, recast, reformatted or transmitted in any form by any means electronic

Merchandising Firms Principles of Accounting Created 2005 By Michael Worthington Elizabeth City State University INVENTORY Traditional bookkeeping uses separate accounts for different types of transactions

INTERNET BANKING FOR BUSINESS Information you need to know about importing transaction files into Internet Banking for Business For more info bnz.co.nz Internet Banking for Business. This guide provides

SAP Business One How-To Guide PUBLIC How to Define Authorizations Applicable Release: SAP Business One 8.8 All Countries English September 2009 Table of Contents Introduction... 3 Authorizations Window...

Accounts Receivable (A/R) is money owed to an entity by customers (individuals or corporations) for goods and/or services that have been delivered or used, but not yet paid for. The intention of this guidance

Welcome to the topic on Master Data and Documents. In this topic, we will look at master data in SAP Business One. After this session you will be able to view a customer record to explain the concept of

This courseware is the property of Sage Software Sdn. Bhd., and is prepared for training purposes at Sage Training Centre (STC). It covers GST features available in Sage UBS 2015 [Version 9.9.1.0] onwards.

Ministry Of Finance VAT Department VAT Rules 2015-010 for Content of Invoices and Receipts Version: December 22-2014 A. Authority This Rule is made under Section 17 of the Value Added Act, 2014. B. Legislation

EDI INVOICE Fona Page 0 of 43 HANCOM DESCRIPTION F GROUP INVOICE Content This document describes the requirements to an EDIFACT INVOIC from a supplier to. The message can be generated in version D93A or

QUICK REFERENCE GUIDE Reporting Tools for Purchase Orders October 31, 2015 Reporting Tools for Purchase Orders When there are questions about the status or details of purchase orders, SWIFT provides several

in Version 3.8, June 14 th, 2015 Contents 0. Background... 3 1. General notes... 4 2. Information about the functions of the EDI Web Services.... 5 2.1 Using the RequestHeader... 6 2.2 Using the ResponseHeader...

Polska THE INVOIC MESSAGE EAN97/EDIFACT D.96A Issue 1.0, 12.2013 agreed-upon by EDI Working Group of ECR Poland The document contains only these segments and data elements that were agreed and accepted

AP INTEGRATION Serengeti Managed Web Service Overview This document overviews the process of integrating Serengeti Tracker with an accounts payable (A/P) system through a Serengeti Managed Web Service.

PDF MAKER FOR VTIGER CRM Introduction The PDF Maker is extension tool designed for vtiger CRM. There is already possibility of the export to pdf format in vtiger CRM functionality but it covers just few

GETTING STARTED MANUAL POS Module Only TABLE OF CONTENTS SET UP... 3 SET UP USERS... 3 SET UP COMPANY PROFILE... 4 SET UP GENERAL LEDGER... 5 SET UP TAXES... 7 SET UP MISC. CHARGES... 8 SET UP SUPPLIERS...

8th SEACEN-CPSS Advanced Course on Payment and Settlement Systems For Emerging Economics The Importance of Modern and International Retail Payment Standards Harry Leinonen 23 March 2010 The views expressed

Using Ecwid to Build an Online Store Ecwid provides all you need for a one-stop online shop, including a built-in 'drag and drop' shopping cart, the recording of customer registration details, destination

e-invoicing Fundamental Concepts and Introduction to e-signatures Beograd, 9. Oktobar, 2015 Belgrade, October 9th, 2015 e-invoicing, What is it? Invoicing" or Billing e-invoicing, What is it? It is a concept,