Description of Swedbank electronic invoice format



Similar documents
Business Document Specification Issue date: Version: 1.61 Invoice Belonging message specification: MS 35

ebinterface 4.0 The Austrian e-invoice standard

ebinterface 4.1 The Austrian e-invoice standard

E-invoice BGC Invoice 1.3.5

Book Industry Communication

810 Invoice ANSI ASC X12 Version 4010

CHAPTER 6: SALES TAX SETUP

ANSI X12 version Remittance Advice

Hal E-Bank Foreign payments (Format of export/import files)

SIX Trade Repository AG

Virginia Department of Taxation Specifications for Web Upload Server to Server Processing for Virginia Department of Taxation Forms

SKF Requirements for Invoices and Delivery Notes

Merchant Returns Service International

Business Document Specification Issue date: Version: 1.52 Invoice

Format description XML SEPA Credit Transfer. Format Description

Format Description. SWIFT MT103 Single Customer Credit Transfer

UK Standard for CDRs. November 12. Version 1.5. Copyright: UK Billing Vendors Forum

Impreso: 22/02/2011 Página 1 de 19. Origen: FSC Versión: 2011-v3 EBILLING FAQ

UNIT 3 CALCULATIONS in MS EXCEL

VERSION: ANSI X

Invoice. Transaction Set (810) (Outbound from TI)

Secure Envelope specification

S.2.2 CHARACTER SETS AND SERVICE STRING ADVICE: THE UNA SEGMENT

850 Purchase Order. X12/V4030/850: 850 Purchase Order. Version: 1.0 Draft

ADOBE ANSI X Version: 1.0

Electronic Data Transmission Guide For International Mailers

Hella EDIFACT INVRPT

e2b Invoice Format Message Description Version: 3.4

Total Order Plus Integrated Accounting Series Accounts Receivable

Three Step Redirect API V2.0 Patent Pending

INVENTORY. Merchandising Firms COST OF GOODS SOLD. Traditional bookkeeping uses separate accounts for different types of transactions

IS-XML Structure and Interface Specification for Caterers. September 2014

The Great Atlantic & Pacific Tea Co., Inc. Imaging and Workflow Automation (IWA) Vendor Guide to Electronic Invoicing

CHAPTER 7: CASH AND BANK MANAGEMENT SETUP

OUTGOING PAYMENTS ISO APPLICATION GUIDELINE

Search invoice API. Version 5.1

E-invoicing (EBPP) today and future trends in Nordic countries

ANZ TRANSACTIVE FILE FORMATS WEB ONLY Page 1 of 118

2009, AdventNet Inc. All rights reserved. Product Customization

Wire Transfer. Business Link. Creating a Wire Transfer Template. Wire Transfer Types. Wire Transfer Templates and Transactions

810 Invoice ANSI X.12 Version 5010

GUIDE ON GST ACCOUNTING SOFTWARE FOR SOFTWARE DEVELOPERS IN MALAYSIA UNIT TUGAS-TUGAS KHAS GST JABATAN KASTAM DIRAJA

Tieto Business Information exchange Portal

Business Online Transaction Import & Export (Download) File Formats REFERENCE DOCUMENT

Virtual Fax API User Guide

F o r e i g n p a y m e n t i n P o l a n d Page 1 of 6 B u s i n e s s O n l i n e

Welcome to the topic on Master Data and Documents.

Message Containers and API Framework

Internet Banking for Business

Customer EDI Guidelines United States 810 Invoice

ERPLY Accounting user guide

Service description. Corporate Access Payables

Microsoft Dynamics GP. Field Service Service Call Management

A/R INVOICING EXTERNAL CUSTOMERS

How to Define Authorizations

Sage Careline is open between 8am to 8pm, Monday to Friday, excluding public holiday Phone Support Hotline : SAGE (7243)

LOST? Follow these signs on the road to e-invoicing.

CHAPTER 9: ACCOUNTS PAYABLE SETUP

Version 3.8, June 14th, 2015

Groupon Goods Global GmbH VENDOR INVOICE GUIDE. This Guide Applies to:

February Are You Ready for E-invoicing?

846 Inbound Inventory Advice WITH VENDOR DIRECT (TO CONSUMER) ORDERS Macy s VICS Version 4010 VICS Document Mapping Effective 08/27/2007

EDI F GROUP A/S INVOICE. Fona. Document: EDIFACT UserGuide GB-INVOIC_IBM-draft1 Date: 5/ Version: V1.0.0A Page 0 of 43. ecommerce ServiceCenter

E-Invoicing Supplier Manual

RANDOM HOUSE. EDI Implementation Guide. 850 Purchase Order X12 Version 4010

ISO PAYMENT GUIDE. Messages: Pain Pain

Extracting Your Company s Data with the New Audit Data Standard

Enable Tax to Calculate on Invoices Originating in Oracle R12 Projects

Payment Status Report

February 2010 Version 6.1

Ariba einvoicing Supplile i r r P O F lilp i T ra r in i in i g

Digital Data & Image Format Guidelines For School Photography and Yearbook Publication Version

PURCHASE ORDER RESPONSE

Electronic foreign currency payments, LUM2

Merchant Returns Service

Content. Document no: D# Version: 4/16/2014

EDI 210 Invoice. Motor Freight 210 Invoice with Stop Offs. Version: 1.0 ANSI X Draft

Format description of MT103 (Multicash PLA) foreign payment file.

E-invoices in Baltic retail: requirements, progress, challenges

810 Invoice Revised 01/26/15

How To Use Danske Internet Bank

820 ANSI X12 Version

ORDERS 92.1 EDI GUIDELINE. for. Message Type ORDERS, ORDCHG Version 1 Release 921. ORDERS, ORDCHG Version /2011 Page 1

Accounts and bank transfers

THE INVOIC MESSAGE EANCOM97/EDIFACT D.96A

Betalingsservice, Automatic card payment and payment slips Guidelines for Data Suppliers

Receivables & Payables

Overview: FedPayments Reporter Interface to Online Banking Cash Management Systems

PDF MAKER FOR VTIGER CRM

The Importance of Modern and International Retail Payment Standards

Big Fish ecommerce. BF Import Mapping.doc

A mixed e-invoice format (PDF + a set of few datas): the best compromise between suppliers and buyers for a fast adoption of e-invoicing

ECommerce Online Store Solution

Ministry Of Finance VAT Department. VAT Rules for Content of Invoices and Receipts Version: December

SWIFT Certified Application Payments

Merchant Service Provider Guide for Mobilpenge Based Acquiring

QUICK REFERENCE GUIDE

Transcription:

Description of Swedbank electronic invoice format Version 1.0 In English 30.09.2014 Page 1 of 38

Document status: Initial version Document version history Date Version Description Author 01/12/2013 0.1 The first draft version (Estonian 1.2 version) 14/04/2014 0.5 Version 0.5. Swedbank 30/05/2014 0.9 Changes compared to version 0.5 : Swedbank Changed attribute serviceid2 -> additionalserviceid Changed tag ServiceId2 ->AdditionalServiceId Added tag -> CancelPreviousInvoice Added to standard Template displaying following Tags/Attributes (serviced, additionalserviceid, ContractNumber, TotalVATSum, TotalToPay ) Increased length (and changed name) for Decimal5FractionDigitsType (previous Decimal4FractionDigitsType) 30/09/2014 1.0 Fixed attribute sellerregnumber -> sellerregnumber Tag AppId must be always presented in E_invoice file header Fixed tag EmailAddress -> E-mailAddress Removed attributes senderid and receiverid from e-invoice application root element Defined more in details some of data types and they usage Updated information for tags descriptions Swedbank Page 2 of 38

Table of Contents 1. GENERAL INFORMATION...4 1.1. PREFACE...4 1.2. REFERENCES...4 2. E-INVOICE DESCRIPTION...5 2.1. GENERAL...5 2.2. E_INVOICE...5 2.3. HEADER...6 2.4. INVOICE...7 2.5. INVOICEPARTIES...9 2.6. INVOICEINFORMATION... 10 2.7. INVOICESUMGROUP... 12 2.8. INVOICEITEM... 14 2.8.1. ITEMENTRY... 16 2.8.2. GROUPENTRY... 18 2.9. ADDITIONALINFORMATION... 19 2.10. PAYMENTINFO... 20 2.11. FOOTER... 21 2.12. COMPLEX TYPE DEFINITIONS... 22 2.12.1. ACCOUNTDATARECORD... 22 2.12.2. SELLERPARTYACCOUNTDATARECORD... 22 2.12.3. ACCOUNTINGRECORD... 23 2.12.4. ADDITIONRECORD... 24 2.12.5. ADDRESSRECORD... 25 2.12.6. BILLPARTYRECORD... 26 2.12.7. CONTACTDATARECORD... 27 2.12.8. EXTENSIONRECORD... 28 2.12.9. SELLERPARTYRECORD... 29 2.12.10. VATRECORD... 30 3. E-INVOICE APPLICATION... 31 3.1. ROOT ELEMENT... 31 3.2 APPLICATION RECORD... 32 4. SIMPLE TYPE DEFINITIONS... 34 5. SAMPLE FILES... 36 5.1. SIMPLE E-INVOICE (INCLUDE ALL MANDATORY FIELDS)... 36 5.2. E-INVOICE APPLICATION EXAMPLE (3 APLICATION)... 38 Page 3 of 38

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 http://www.w3.org/tr/xmlschema-1/ W3Schools XML Tutorial http://www.w3schools.com/xml/ Value Added Tax Act http://likumi.lv/doc.php?id=253451 Accounting Act http://www.likumi.lv/doc.php?id=66460 Electronic Documents Act http://www.likumi.lv/doc.php?id=68521 Estonia E-invoice description: Estonian Bank association web page http://www.pangaliit.ee/et/arveldused/e-arve Page 4 of 38

2. E-Invoice description 2.1. General Encoding of XML files is UTF-8 XML specific characters must be escaped: & & &apos; > > < < " For example name Dainis & Gatis SIA be: <Name>Dainis & Gatis SIA</Name> 2.2. E_Invoice E_Invoice is the root element of electronic invoice <E_Invoice> <Header> </Header> <Invoice invoiceid="a1122" serviceid ="1111" regnumber="010101-11111" channelid ="HABALV22" channeladdress="lv00haba0000000000002" presentment= invoiceglobuniqid= A1122-1 sellercontractid= 87654321 sellerregnumber="40000000000"> </Invoice> <Invoice invoiceid="a1123" serviceid ="1111" channeladdress="lv00haba0000000000001" regnumber="010101-11111" channelid ="HABALV22" presentment= invoiceglobuniqid= A1122-2 sellercontractid= 87654321 sellerregnumber="40000000000"> </Invoice> <Footer> <TotalNumberInvoices>2</TotalNumberInvoices> <TotalAmount>29768.04</TotalAmount> </Footer> </E_Invoice> Tag Description Type / Value list Header Specifies file specific elements [on page 6]. Invoice Contains information about one invoice [on page 7]. This element is repeated for every invoice. Footer Shows the total number of the invoices and the total sum of all the invoices in a file [on page 21]. Mandatory Displayed using standard template Notes Info is not for displaying * 1-n Info is not for displaying Page 5 of 38

2.3. Header Header contains file specific elements, <Header> <Date>2014-04-03</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

2.4. Invoice Invoice contains information about one invoice. <Invoice invoiceid="a1122" serviceid ="1111" regnumber="010101-11111" channelid ="HABALV22" presentment= invoiceglobuniqid= A1122-1 sellercontractid= 87654321 sellerregnumber="40000000000"> </Invoice> <InvoiceParties></InvoiceParties> <InvoiceInformation></InvoiceInformation> <InvoiceSumGroup></InvoiceSumGroup> <InvoiceItem></InvoiceItem> <AdditionalInformation></AdditionalInformation> <PaymentInfo></PaymentInfo> Tag Description Type / Value list Mandat Displayed using Notes ory standard template invoiceid Unique id of the invoice (on NormalTextType Attribute the scope of one file). Used to prevent double processing. serviceid Client identification number (reference number, client number, department id etc.) in sellers system / factoring contract number. ShortTextWithou tspacestype Attribute additionalserviceid regnumber channelid channeladdress 2 nd Client identification number (reference number, client number, department id etc.) in sellers system / factoring contract number. (used only if needed) Personal ID/registration code of the invoice receiver. The id of the channel to where the invoice must be routed [on page 35]. Remark: Must be presented when Invoice is sent to Bank The address in the channel of the invoice receiver. Used for finding the customer to whom this invoice is sent bank account number; Remark: Must be presented when Invoice is sent to Bank ShortTextWithou tspacestype Attribute RegType Attribute EncodingType Attribute IBAN2007Identif ier Attribute factoring Indicates whether this is a YesNoType Attribute factoring invoice or not. templateid Id of the invoice s design NormalTextType Attribute template. languageid Id of the invoice s language. LanguageType Attribute presentment Represents invoice's presentation method in internet bank. Remark: field optional in Estonia. YesNoType Attribute invoiceglobuniqid Invoice s unique identifier in NormalTextType Attribute Page 7 of 38

sellercontractid sellerregnumber InvoiceParties InvoiceInformation InvoiceSumGroup InvoiceItem AdditionalInformation PaymentInfo sender s invoicing process. Remark: field optional in Estonia. Seller s/operator contract number. Used in invoice sending to internet bank. Remark: field optional in Estonia. Seller s/operator registration number. Describes the sender and receiver of the invoice [on page 9]. Contains general information about the invoice [on page 10]. Contains total sum of the invoice [on page 12]. Contains detailed information about the invoice rows [on page 14]. Contains free information which is shown on the invoice (ex: marketing information or info concerning services etc.) [on page 19]. Information needed to generate payment order [on page 20]. NormalTextType Attribute RegType Attribute * * * 1-2 * * 0-n Page 8 of 38

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

2.6. InvoiceInformation InvoiceInformation contains general invoice specific information about the invoice. <InvoiceInformation> <Type type="deb"> <SourceInvoice>440</SourceInvoice> </Type> <FactorContractNumber> L8574-14 </FactorContractNumber> <ContractNumber>15-58/2</ContractNumber> <DocumentName>Rēķins</DocumentName> <InvoiceNumber>129592-2</InvoiceNumber> <InvoiceContentCode> SPO5 </InvoiceContentCode> <InvoiceContentText> Komunālie pakalpojumi </InvoiceContentText> <PaymentReferenceNumber>30253234017 </PaymentReferenceNumber> <PaymentMethod> veicot rēķina apmaksu norādiet klienta numuru </PaymentMethod> <InvoiceDate>2014-04-01</InvoiceDate> <DueDate>2014-04-15</DueDate> <PaymentTerm> Maksājumu termiņš 14 dienas </PaymentTerm> <FineRatePerDay>0.2</FineRatePerDay> <Period> <PeriodName>Marts </PeriodName> <StartDate>2014-03-01</StartDate> <EndDate>2014-03-31</EndDate> </Period> <InvoiceDeliverer> <ContactName>Jānis Bērziņš</ContactName> </InvoiceDeliverer> <Extension id="regname"> <InformationName>Imanta </InformationName> <InformationContent/>Imantas parvaldes kontaktinformācija </InformationContent> </Extension> </InvoiceInformation> Tag Description Type / Value Mandat Displayed using list ory standard template Type Invoice type. Notes type DEB debit invoice, CRE credit invoice xs:nmtoken DEB / CRE * Attribut e SourceInvoice Reference to the source ShortTextType invoice. FactorContractNumber Factoring contract number NormalTextTy (contract between client and crediting institution). pe ContractNumber Contract number between NormalTextTy buyer and seller. Basis for the invoice. pe DocumentName Name of the document (ex: NormalTextTy Invoice, Credit Note etc). pe InvoiceNumber Number of invoice. NormalTextTy pe Page 10 of 38

InvoiceContentCode InvoiceContentText PaymentReferenceNu mber PaymentMethod Invoice content code, agreed between parties to help automate processing. Description about the invoice content. Payment reference number. Same as in PaymentInfo/PaymentRefId. Free text describing payment method and terms, used only when printing the invoice on paper. ShortTextType NormalTextTy pe ReferenceTyp e NormalTextTy pe InvoiceDate Invoice date. DateType DueDate Invoice due date. DateType PaymentTerm Free text describing payment terms (ex: The payment term 14 days). NormalTextTy pe FineRatePerDay Period Fine rate per day. Shown in percent. If invoice concerns some kind of period-related service for example energy consumption on given period, then the period can be specified. Decimal2Fracti ondigitstype PeriodName Name of the period. NormalTextTy pe StartDate Starting date of the period. DateType EndDate End date of the period. DateType InvoiceDeliverer Contact information of the person, who wrote out the invoice (phone number, address, e-mail, name). See ContactDataRecord for details [on page 27]. ContactDataR ecord Extension Describes additional elements that are needed to present in this section. See ExtensionRecord for details [on page 28]. ExtensionRec ord * * 0-n Page 11 of 38

2.7. InvoiceSumGroup InvoiceSumGroup contains the payment and balance total information. <InvoiceSumGroup> <Balance> <BalanceDate>2014-03-01</BalanceDate> <BalanceBegin>3.14</BalanceBegin> <Inbound>3.14</Inbound> <Outbound>3.14</Outbound> <BalanceEnd>3.14</BalanceEnd> </Balance> <InvoiceSum>101.10</InvoiceSum> <PenaltySum>0</PenaltySum> <Addition addcode="dsc"> <AddContent> Senioru atlaide </AddContent> <AddRate>-5</AddRate> <AddSum>-5.055</AddSum> </Addition> <Rounding>0.005</Rounding> <VAT> <SumBeforeVAT>96.04</SumBeforeVAT> <VATRate>21</VATRate> <VATSum>20.17</VATSum> <Currency>EUR</Currency> </VAT> <TotalSum>116.21</TotalSum> <Currency>EUR</Currency> <Accounting> </Accounting> <Extension extensionid=" "> </Extension> </InvoiceSumGroup> Tag Description Type / Value list Mand Displayed using Notes atory standard template Balance Describes balances on the beginning and end of invoicing period. BalanceDate The date on which the balance is DateType calculated. BalanceBegin Balance start value. Decimal2Fractio ndigitstype Inbound The sum paid by the invoice receiver to invoice sender in the balance period. Decimal2Fractio ndigitstype 0-n Outbound The sum paid by the invoice sender to invoice receiver in the balance period. Decimal2Fractio ndigitstype BalanceEnd Balance end value. Decimal2Fractio ndigitstype InvoiceSum Amount of the invoice without tax. Decimal5Fractio Total of ndigitstype InvoiceItemGroup/ItemEntry/Item Sum elements. 0-n PenaltySum Amount of the penalty. Decimal5Fractio ndigitstype Addition Describes additions to the sum (ex: discounts or charges). See AdditionRecord for details [on page 24]. AdditionRecord * 0-n Rounding Invoice total rounding. Decimal5Fractio ndigitstype Page 12 of 38

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 0.00. 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

2.8. InvoiceItem InvoiceItem contains information about Invoice rows. <InvoiceItem> <InvoiceTotalGroup groupid="kopsavilkums"> <ItemEntry>... </ItemEntry> <GroupEntry>... </GroupEntry> </InvoiceTotalGroup> <InvoiceItemGroup groupid="zīmuļi"> <ItemEntry>... </ItemEntry> <GroupEntry>... </GroupEntry> </InvoiceItemGroup> <InvoiceItemGroup groupid="papīrs"> <ItemEntry>... </ItemEntry> <ItemEntry>... </ItemEntry> <GroupEntry>... </GroupEntry> </InvoiceItemGroup> <InvoiceItemTotalGroup> <InvoiceItemTotalDescription>... </InvoiceItemTotalDescription> <InvoiceItemTotalSum>... </InvoiceItemTotalSum> </InvoiceItemTotalGroup> </InvoiceItem> Tag Description Type / Value list InvoiceTotalGroup Group of invoice items totals (by items). groupid ID of the invoice rows group. ShortTex ttype ItemEntry Describes one specific invoice row entry [on page 16]. GroupEntry Describes group total [on page 18]. InvoiceItemGroup The main group on invoice rows. Group of invoice items or invoice rows. groupid ID of the invoice rows group. ShortTex ttype ItemEntry Describes one specific invoice row entry [on page 16]. GroupEntry Describes group total [on page 18]. InvoiceItemTotalGroup Total of all of invoice items totals. InvoiceItemTotalDescripti Description of total. NormalT on exttype Mandat ory Displayed using standard template Notes * Attribut e * 0-n * * 1-n Attribut e * 1-n * * Page 14 of 38

Extension Accounting Describes additional elements that are needed to present in this section. See ExtensionRecord for details [on page 28]. Accounting element describes information needed to automate accounting transactions. See AccountingRecord for details Extensio nrecord Accounti ngrecor d [on page 23]. InvoiceItemTotalAmount The Total amount of items. Decimal5 Fraction DigitsTyp e InvoiceItemTotalSum Addition VAT InvoiceItemTotal The total sum of items without taxes. Describes additions to the sum (ex: discounts or charges). See AdditionRecord for details [on page 24]. Describes value-added tax. See VATRecord for details [on page 30]. The total sum of items with taxes. Decimal5 Fraction DigitsTyp e Addition Record VATReco rd Decimal5 Fraction DigitsTyp e 0-n 0-n Page 15 of 38

2.8.1. ItemEntry ItemEntry element describes detailed info about Invoice row. <ItemEntry> <RowNo>1</RowNo> <SerialNumber>A74875547751124</SerialNumber> <SellerProductId>Prod123</SellerProductId> <BuyerProductId>123prod</BuyerProductId> <TaricCode>CODE123456</TaricCode> <Accounting>... </Accounting> <CustomerRef>pasūtījums 457</CustomerRef> <Description>Pildspalvas</Description> <EAN>3272513030707</EAN> <ItemReserve extensionid="prectip"> <InformationName>Preces tips</informationname> <InformationContent>L5870</InformationContent> </ItemReserve> <ItemDetailInfo> <ItemUnit>gab</ItemUnit> <ItemAmount>10</ItemAmount> <ItemPrice>1.36</ItemPrice> </ItemDetailInfo> <ItemSum>13.60</ItemSum> <Addition addcode="dsc"> <AddContent>Akcija10%</AddContent> <AddRate>-10</AddRate> <AddSum>-1.36</AddSum> </Addition> <VAT> <SumBeforeVAT>12.24</SumBeforeVAT> <VATRate>21</VATRate> <VATSum>2.57</VATSum> <Currency>EUR</Currency> </VAT> <ItemTotal>14.81</ItemTotal> </ItemEntry> Tag Description Type / Value list Mandatory Displayed using standard template RowNo Row number of the product. NormalTextTy pe SerialNumber Serial number of the product. ShortTextType SellerProductId Item/product ID code in seller s ShortTextType system. BuyerProductId Item/product ID code in buyer s ShortTextType system. TaricCode TARIC (Integrated Tariff of the EncodingType European Communities) code. See EncodingType for details [on page 35]. Accounting Describes information needed to AccountingRe * automate accounting transactions. cord See AccountingRecord for details [on page 23]. CustomerRef Reference related to a specific product/service mentioned in this row. Reference to order, contract made by buyer. NormalTextTy pe Description Item/product/article name. LongTextSingl etype EAN International Article Number (Barcode NormalTextTy number). pe Notes Page 16 of 38

InitialReading FinalReading ItemReserve Related to the periodical invoicing. Situation in the beginning of the period. For example water consumption. Related to the periodical invoicing. Situation at the end of the period. For example water consumption. Additional information, in case more fields are needed to describe item/row. See ExtensionRecord for details [on page 28]. ShortTextType ShortTextType ExtensionRec ord 0-n ItemDetailInfo Invoiced item s detailed info. * 0-n ItemUnit Name of unit (e.g kg, sec, kwh). ShortTextType ItemAmount Quantity of the product or service. Decimal5Fracti ondigitstype ItemPrice Price of one product or service Decimal5Fracti (without taxes). ondigitstype ItemSum Total amount without taxes and Decimal5Fracti discount. ondigitstype Addition Describes additions to the sum (ex: discounts or charges). See AdditionRecord for details [on page 24]. AdditionRecor d * 0-n VAT ItemTotal Describes value-added tax. See AdditionRecord for details [on page 30]. Total Row amount (ItemSum minus discounts plus taxes). VATRecord * Decimal5Fracti ondigitstype Page 17 of 38

2.8.2. GroupEntry GroupEntry element sums different Item rows into one logical group. <GroupEntry> <GroupDescription>Papīrs</GroupDescription> <Extension extensionid=" "> </Extension> <Accounting> </Accounting> <GroupAmount>50</GroupAmount> <GroupSum>125.00</GroupSum> <Addition addcode="dsc"> <AddContent>Piegades izmaksa</addcontent> <AddSum>5.00</AddSum> </Addition> <VAT> <SumBeforeVAT>130.00</SumBeforeVAT> <VATRate>21</VATRate> <VATSum>27.30</VATSum> <Currency>EUR</Currency> </VAT> <GroupTotal>157.30</GroupTotal> </GroupEntry> Tag Description Type / Value list Mandatory Displayed using Notes standard template GroupDescription Free text describing the group. NormalTextType Extension Additional information, in case ExtensionRecord 0-n more fields are needed to describe group total. See ExtensionRecord for details [on page 28]. Accounting Describes information needed to AccountingRecord automate accounting transactions. See AccountingRecord for details [on page 23]. GroupAmount Total quantity of items described in the rows in this group. (Sum of ItemAmount elements). Decimal5Fraction DigitsType GroupSum Addition VAT GroupTotal Total sum related to the rows in this group. (Sum of ItemSum elements). Describes additions to the sum (ex: discounts or charges). See AdditionRecord for details [on page 24]. Describes value-added tax. See VATRecord for details [on page 30]. Total Group amount. (Sum of ItemTotal elements). Decimal5Fraction DigitsType AdditionRecord * 0-n VATRecord * Decimal5Fraction DigitsType Page 18 of 38

2.9. AdditionalInformation AdditionalInformation element describes of additional free-text information on the invoice. For example information related to marketing messages. <AdditionalInformation id="note"> <InformationName> Piezīme </InformationName> <InformationContent> Veicot rēķina apmaksu pārliecinieties par saņēmēja konta numuru. </InformationContent> </AdditionalInformation> Tag Description Type / Value list AdditionalInformation Additional information which Extension is shown on the invoice. See Record ExtensionRecord for details [on page 28]. Mandatory Displayed using standard template * Notes Page 19 of 38

2.10. PaymentInfo PaymentInfo element describes the information used for generating payment order form from the invoice. <PaymentInfo> <Currency>EUR</Currency> <PaymentDescription>Rēķins nr. 340925 </PaymentDescription> <Payable></Payable> <PayDueDate>2014-04-15</PayDueDate> <PaymentTotalSum>54.21</PaymentTotalSum> <PaymentId>340925</PaymentId> <PayToAccount>LV00XXXX0000000000000</PayTo Account> <PayToName>AS Saņēmējs</PayToName> <PayToBIC>XXXXLV22</PayToBIC> </PaymentInfo> Tag Description Type / Value list Currency Three-character currency code as specified in the ISO 4217 standard. PaymentDescription This description will be used PaymentDescr PaymentRefId Payable as a payment detail. Payment reference number. B2B is forwarded as structured reference Weather this bill needs to be paid or not. Invoice needs to be paid. (PayDueDate is mandatory). Invoice is for information purposes only and does not need payment (PayDueDate is optional). Mandatory Displayed using standard template CurrencyType iptiontype ReferenceTyp e YesNoType PayDueDate Payment due date. DateType PaymentTotalSum Total amount of the payment. Remark: Amount must be the same as in InvoiceSumGroup block in tag TotalSum Decimal2Fracti ondigitstype PaymentId Same as InvoiceNumber. NormalTextTy pe PayToAccount The beneficiary s account IBAN2007Iden number. tifier PayToName The beneficiary s name. NormalTextTy pe PayToBIC The beneficiary s bank s BIC code. BICType Notes Descripti on OR Referenc e must be filled. Page 20 of 38

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>29768.04</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

2.12. Complex Type Definitions 2.12.1. AccountDataRecord AccountDataRecord defines the elements used to describe bank account information. <AccountInfo> <AccountNumber>LV00XXXX0000000000000 </AccountNumber> <BIC>XXXXLV22</BIC> <BankName>BANK</BankName> </AccountInfo> Tag Description Type / Value list Mandatory Displayed using standard template AccountNumber Account number in local AccountType banking system. BIC Bank identification code BICType (SWIFT code). BankName The name of the bank. NormalTextType Notes 2.12.2. SellerPartyAccountDataRecord <AccountInfo> <AccountNumber>LV00XXXX0000000000000 </AccountNumber> <BIC>XXXXLV22</BIC> <BankName>BANK</BankName> </AccountInfo> Tag Description Type / Value list Mandatory Displayed using standard template AccountNumber Account number in local IBAN2007Identifier banking system. BIC Bank identification code xs:string( Max: 11) (SWIFT code). BankName The name of the bank. NormalTextType Notes Page 22 of 38

2.12.3. AccountingRecord AccountingRecord describes information needed to automate accounting transactions. Vendor and buyer can agree on information needed to automate invoice (row) processing in buyers accounting system. This information can be used as a seller side proposal as to how this invoice should be described in buyers accounting system. <Accounting> <Description> Elektrības maksājums nr 345 </Description> <JournalEntry> <GeneralLedger>4106</GeneralLedger> <GeneralLedgerDetail> </GeneralLedgerDetail> <CostObjective></CostObjective> <Sum>5000</Sum> <VatSum>900</VatSum> <VatRate>20</VatRate> </JournalEntry> <PartnerCode></PartnerCode> <BusinessCode></BusinessCode> <SourceCode></SourceCode> <CashFlowCode></CashFlowCode> <ClassificatorCode></ClassificatorCode> </Accounting> Tag Description Type / Mandat Displayed using Notes Value list ory standard template Description Description of the journal NormalTex entry. ttype JournalEntry Describes one journal entry. 1-n GeneralLedger General Ledger number (conforming to the short chart of accounts). ShortTextT ype GeneralLedgerDet ail CostObjective Sum General Ledger number (conforming to detailed chart of accounts). Cost centre/dimension identifier (optional information, if the vendor can define the dimension, which can be a cost centre, profit centre, project code, identifier of a person, etc). Shows the amount which will be credited/debited to the ledger account. Positive amount debit. Negative amount credit. ShortTextT ype ShortTextT ype Decimal5F ractiondigit stype VatSum Value added tax (0 if none). Decimal5F ractiondigit stype VatRate Value added tax rate. Decimal2F ractiondigit stype PartnerCode The code of the partner. See EncodingType for details [on page 35]. EncodingT ype BusinessCode The code of the business area. EncodingT ype SourceCode The code of the source. EncodingT ype CashFlowCode The code of the cash flow. EncodingT ype ClassificatorCode The classificator of the state s NormalTex budget. ttype Page 23 of 38

2.12.4. AdditionRecord AdditionRecord element describes additions and subtractions on specific amount. This element is used to describe charges and discounts. <Addition addcode="dsc"> <AddContent>Akcijas atlaide</addcontent> <AddRate>-15</AddRate> <AddSum>-25.48</AddSum> </Addition> Tag Description Type / Value list Mandat Displayed using Notes ory standard template addcode DSC Discount. xs:nmtoken Attribute CHR Charge. DSC / CHR AddContent Name of the addition (ex: NormalTextType * Customer loyalty program). AddRate Rate of the Decimal2FractionDigit * addition/discount (in percent). stype AddSum Amount of the addition. Decimal5FractionDigit stype * It is different in different invoice blocks Page 24 of 38

2.12.5. AddressRecord AddressRecord defines the elements used to describe the address. <MailAddress> <PostalAddress1>Kalna iela 1</PostalAddress1> <PostalAddress2> Upes iela 20 </PostalAddress2> <City>Rīga</City> <PostalCode>LV1044</PostalCode> <Country>Latvija</Country> <Extension id="roomnumber"> <InformationName> Kabinets </InformationName> <InformationContent> 3 stāvs, 2 kabinets </InformationContent> </Extension> </MailAddress> Tag Description Type / Value list Mandat Displayed using Notes ory standard template PostalAddress1 Street, House, Apartment. NormalTextType PostalAddress2 Village, Postal office, etc. NormalTextType City City or County. NormalTextType PostalCode Postal code. xs:string (Max: 10) Country Country. NormalTextType Extension Describes additional elements that are needed in this section. See ExtensionRecord for details [on page 28]. ExtensionRecord 0-n Page 25 of 38

2.12.6. BillPartyRecord BillPartyRecord defines different parties involved with the invoice (the buyer, the recipient of the invoice and recipient of the goods/services). <SellerParty> <GLN>1234567891234</GLN> <UniqueCode>987654</UniqueCode> <Name>Tirgotājs SIA</Name> <DepId>Iepirkumu daļa</depid> <RegNumber>40000000000</RegNumber> <VATRegNnumber>LV40000000000 </VATRegNumber> <ContactData> </ContactData> <AccountInfo> </AccountInfo> <Extension id="licencenumber"> <InformationName> Licenzes numurs </InformationName> <InformationContent> MAM118045A </InformationContent> </Extension> </SellerParty> Tag Description Type / Value list Mandat ory Displayed using standard template GLN Party s GLN-code (Global Location GLNType Number). UniqueCode Unique code of the party (ex: client ShortTextType number in the senders bookkeeping system). Name Name of the party of the invoice. NormalTextTy pe DepId Department identificator (ex: sales). NormalTextTy pe RegNumber Registration number of the party. RegType VATRegNumber VAT registration number of the RegType party. ContactData Contact information of the party ContactDataR * (phone number, address, e-mail, ecord contact person). See ContactDataRecord for details [on page 27]. AccountInfo Extension * Only Legal Address information Describes the accounts of the party. See AccountDataRecord for details [on page 22]. Describes additional elements that are needed in this section. See ExtensionRecord for details [on page 28]. AccountDataR ecord ExtensionRec ord Notes 0-n 0-n Page 26 of 38

2.12.7. ContactDataRecord ContactDataRecord defines the elements used to describe the sender or receiver of the invoice <ContactData> <ContactName>Juris Kalninš</ContactName> <ContactPersonCode>010101-11111 </ContactPersonCode> <PhoneNumber>67654321</PhoneNumber> <FaxNumber>67123456</FaxNumber> <URL>www.bank.lv</URL> <E-mailAddress> info@bank.lv </E-mailAddress> <LegalAddress> </LegalAddress> <MailAddress> </MailAddress> <ContactInformation id="saleagent"> <InformationName> Pārdošanas aģents </InformationName> <InformationContent> Līga Lejiņa </InformationContent> </ContactInformation> </ContactData> Tag Description Type / Value list Mandat Displayed using Notes ory standard template ContactName Name of the contact person. NormalTextType ContactPersonCode Personal ID-code of the RegType contact person. PhoneNumber Contact phone of the party. NormalTextType * FaxNumber Fax number of the party. NormalTextType * URL Web address. NormalTextType * E-mailAddress Email address of the party. xs:string * pattern.+@+.+ LegalAddress Describes the legal address AddressRecord of the party. See AddressRecord for details [on page 25]. MailAddress Describes the postal address AddressRecord of the party. See AddressRecord for details [on page 25]. ContactInformation Describes additional ExtensionRecor 0-n elements that are needed in this section. See ExtensionRecord for details [on page 28]. d * Only in Seller block Page 27 of 38

2.12.8. 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