E-invoice Technical Standard Version 1.1.0
Table of contents 2. General information... 3 2.1. Introduction... 3 2. Description of the e-invoice XML structure... 3 2.1. General technical requirements... 3 2.2. E-invoice root element structure (E_Invoice)... 4 2.3. Structure of the header (Header)... 4 2.4. Structure of the invoice (Invoice)... 5 2.5. Invoice Parties (InvoiceParties)... 7 2.6. Invoice information (InvoiceInformation)... 8 2.7. Invoice sum group (InvoiceSumGroup)... 10 2.8. Invoice item (InvoiceItem)... 12 2.8.1. Item (itementr)... 13 2.8.2. Group entr (GroupEntr)... 16 2.9. Additional information (AdditionalInformation)... 17 2.10. Attached file (AttachmentFile)... 17 2.11. Pament information (PamentInfo)... 18 2.12. Footer (Footer)... 19 2.13. Complex data ts... 19 2.13.1. Account detailed description (AccountDataRecord)... 19 2.13.2. Accounting records (AccountingRecord)... 19 2.13.3. Additional records (AdditionRecord)... 21 2.13.4. Address record (AddressRecord)... 21 2.13.5. Attached document (AttachmentRecord)... 22 2.13.6. Invoice data (BillPartRecord)... 22 2.13.7. ContactDataRecord... 23 2.13.8. Extension record (ExtensionRecord)... 24 2.13.9. SellerPartRecord... 25 2.13.10. VATRecord... 26 2.14. Data set / t description... Error! Bookmark not defined. 2.15 Description of the errors of an incorrect e-invoice file... 30 3. E-invoice request ordering b electronic channels... 33 3.1 E-invoice ordering b electronic channels... 33 3.2 E-invoice ordering b electronic channels... 34 4. Informing of a new service provider... 36 4.1 Informing the PSP or the Orator... 36 2
4.2 Examples of informing the PSP or the Orator... 40 4.3 Error codes of the repl to the message on the new service provider... 40 2. General information 2.1. Introduction This document describes the e-invoice data format to be presented to the credit institution. On the basis of these messages, electronic invoices are generated and presented to clients of the credit institution for review and pament. The presented messages are structured and described b XML t. Section Two will deal with possible fields in the XML file. This file consists of several ke elements, which are the header, invoice, and footer. Each of them has resctive fields, which are mandator or optional for indicating when sending e-invoices to a Member of the scheme. The description of each of the root and separate element is presented graphicall, with explaining it in the resctive section. 2. Description of the e-invoice XML structure 2.1. General technical requirements In XML files, UTF-8 encoding is used. The whole possible set of smbols: a b c d e f g h i j k l m n o p q r s t u v w x z A B C D E F G H I J K L M N O P Q R S T U V W X Y Z 0 1 2 3 4 5 6 7 8 9 / -? : ( )., + space ą č ę ė į š ų ū ž Ą Č Ę Ė Į Š Ų Ū Ž. Scial smbols are indicated in the table presented below: & & ' > > < < " For example, the name of the service provider Įmonė & co. should be written as Įmonė & co.. If the presented tables contain the sign [1..n], it means that the number of such elements ma be greater than one; if the box is empt, it means that the element can be used onl once in a single file. 3
2.2. E-invoice root element structure (E_Invoice) E_Invoice is the root element of an electronic invoice. <E_Invoice> <Header> </Header> <Invoice invoiceid="9200303961940" regnumber="38712144544" channelid="ndealt2x" channeladdress="lt11121212121212122" presentment="yes" invoiceglobuniqid="122183712837ndea" sellercontractid="10004252ndea01" sellerregnumber="10004252"> </Invoice> <Invoice invoiceid="920030396140" regnumber="38712144543" channelid="ndealt2x" channeladdress="lt11121212222212122" presentment="yes" invoiceglobuniqid="122183712837ndea" sellercontractid="10004252ndea01" sellerregnumber="10004252"> </Invoice> <Footer> <TotalNumberInvoices>2</TotalNumberInvoices> <TotalAmount>29768.04</TotalAmount> </Footer> </E_Invoice> Tag Description T/value Header It indicates the parameters of the header of the XML file. For more detail, see Section 2.3 Invoice It describes the information of one [1..n] invoice. This element should be reated for each invoice separatel. For more detail, see Section 2.4 Footer It indicates the total number of invoices and their sum in the XML file. For more detail, see Section 2.12 Mandator tes 2.3. Structure of the header (Header) The header describes the scific elements of the file. <Header> </Header> <Date>2015-04-01</Date> <FileId>66488</FileId> <AppId>EINVOICE</AppId> <Version>1.1</Version> <SenderId>NDEAB</SenderId> <ReceiverId>OCLT</ReceiverId> 4
Tag Description T/value Date It indicates the time of generating the DateT file. FileId It is the unique file identifier assigned ShortText in the sstem of the service provider in order to avoid the duplication of files. AppId Application identifier. EINVOICE will be used for sending the e-invoice to internet banking Version E-invoice Standard Version v1.1 ShortText SenderId File sender identifier ShortText ReceiverId File receiver identifier ShortText Mandator tes ShortText Onl uprcase letters 2.4. Structure of the invoice (Invoice) This group of elements describes individual electronic invoices intended for the client of the credit institution. <Invoice invoiceid="9200303961940" regnumber="38711314543" channelid="ndealt2x" channeladdress="lt11121212121212122" presentment="yes" invoiceglobuniqid="122183712837ndea" sellercontractid="10004252ndea01" sellerregnumber="10004252"> <InvoiceParties>...</InvoiceParties> <InvoiceInformation>...</InvoiceInformation> <InvoiceSumGroup>...</InvoiceSumGroup> <InvoiceItem>...</InvoiceItem> <PamentInfo>...</PamentInfo> </Invoice> Tag Description T/value Mandator tes Invoice invoiceid Unique e-invoice identifier in the file. It is rmaltext Attribute used in order to prevent double processing. serviceid It is the unique identifier assigned b the service provider to the agreement with the service receiver or paer (e.g. the client code in the information sstem of the service provider). ShortText Attribute If this field is not used, limitations are possible in using the automatic e- invoice 5
pament functionalit of the PSP. regnumber E-invoice receiver rsonal/compan RegT Attribute code channelid It is the identifier according to which the BICT Attribute destination of the file is determined. The receiver code of the financial institutions. It is possible to use, e.g. BIC, SWIFT code for ensuring the receiver channel. channeladdress It is the e-invoice receiver channel rmaltext Attribute address to which the message should be directed. IBAN code factoring It indicates whether or not it is a factoring Attribute invoice. templateid It is the e-invoice template ID to be rmaltext Attribute shown to the receiver. languageid E-invoice template language LanguageT Attribute presentment It defines the t of presentment to the Attribute e-invoice receiver. Whether the full e- invoice information, which is the invoice, or information onl for making the pament is presented. If the value of this field is, then, irresctive of the submitted fields, onl information intended for pament will be presented. invoiceglobuniqid It is the unique identifier of the e-invoice rmaltext Attribute in the accounting sstem of the sender. sellercontractid The number of the contract of the paee with his PSP. It is used in order to rmaltext Attribute If several prorl displa the e-invoice to the contracts are concluded paer in internet banking. with the Bank, then it is necessar to indicate the contract number in this field. sellerregnumber Paee rsonal/compan code RegT Attribute InvoiceParties The parties to the e-invoice. It describes the sender and the receiver. For more detail, see Section 2.5 InvoiceInformatio General information on the e-invoice For n more detail, see Section 2.6 InvoiceSumGroup It describes the total sum of the e- invoice. For more detail, see Section 2.7 InvoiceItem It describes the detailed information of each item of e-invoices. For more detail, see Section 2.8 AdditionalInforma tion AttachmentFile Additional information to be displaed to the e-invoice receiver. For more detail, see Section 2.9 E-invoice in PDF format, encoded b BASE64 method. For more detail, see [0..n] 6
PamentInfo Section 2.13.5 Information necessar for creating the pament order according to the information of the e-invoice. For more detail, see Section 2.11 2.5. Invoice Parties (InvoiceParties) The description of the parties of the rsons/companies related to the purchase and sale. The paer and goods receiver ma be different rsons/companies. <InvoiceParties> <SellerPart> </SellerPart> <BuerPart> </BuerPart> <RecipientPart> </RecipientPart> <DeliverPart> </DeliverPart> <PaerPart> </PaerPart> <FactorPart> </FactorPart> </InvoiceParties> Tag Description T/value SellerPart It describes the sender of the e-invoice SellerPartReco (name, address, etc.). For more detail, rd see Section 2.13.9 BuerPart It describes the paer (name, address, BillPartRecord etc.). For more detail, see Section 2.13.6 RecipientPart This document structure is used when the BillPartRecord e-invoice receiver is not the final service receiver, e.g. when paing invoices for children/parents, or when the e-invoice is paid b accounting firms representing their clients. For more detail, see Section 2.13.6 DeliverPart Deliver data are used when the invoice BillPartRecord receiver is different from the paer. For more detail, see Section 2.13.6 PaerPart This document structure is used when the BillPartRecord paer and service receiver do not coincide. For more detail, see Section Mandator tes 7
FactorPart 2.13.6 The part to which SellerPart indicates invoices. For more detail, see Section 2.13.6 BillPartRecord 2.6. Invoice information (InvoiceInformation) This element describes the general items contained in the invoice. <InvoiceInformation> <T t="deb"> </T> <FactorContractNumber> L8574-14 </FactorContractNumber> <ContractNumber>15-58/2</ContractNumber> <DocumentName>ESASK</DocumentName> <InvoiceNumber>129592-2</InvoiceNumber> <InvoiceContentCode>SPO5</InvoiceContentCode> <InvoiceContentText>Goods</InvoiceContentText> <PamentReferenceNumber>30253234017</PamentReferenceNumber> <PamentMethod>Order </PamentMethod> <InvoiceDate>2015-04-01</InvoiceDate> <DueDate>2015-04-15</DueDate> <PamentTerm>Pament within 14 das </PamentTerm> <FineRatePerDa>0.2</FineRatePerDa> <Period> <PeriodName>For a month</periodname> <StartDate>2015-05-01</StartDate> <EndDate>2015-05-30</EndDate> </Period> <InvoiceDeliverer> <ContactName>Trainer Jonaitis</ContactName> </InvoiceDeliverer> <Extension id="gmname"> <InformationName>Sportuok UAB</InformationName> <InformationContent/>Monthl pament</informationcontent> </Extension> </InvoiceInformation> Tag Description T/value Mandator tes T E-invoice t t DEB debit e-invoice, to be paid xs:nmtoken Attribute CRE credit e-invoice DEB / CRE SourceInvoice Link to the previousl issued e- ShortText Attribute invoice. It is used with the CRE t. FactorContractNumber The factoring contract number (the rmaltext contract between the sender and financial institution). ContractNumber The number of the contract between rmaltext the paer and service provider. DocumentName The document name or serial number rmaltext (e.g. e-invoice) InvoiceNumber E-invoice number rmaltext InvoiceContentCode The e-invoice content code agreed ShortText upon between the sender and paer InvoiceContentText E-invoice content description rmaltext 8
PamentReferenceNum Pament number. The same as ReferenceT ber PamentInfo/PamentRefId PamentMethod Text with free contents to displa rmaltext when describing the pament t. It is used when a par invoice is sent. InvoiceDate E-invoice presentation date DateT DueDate The date b which the e-invoice must DateT be paid PamentTerm Free text describing the pament rmaltext information. (e.g. Please pa the invoice within 14 das from its receipt) FineRatePerDa The expression of the late pament Decimal2Fra interest r da ctiondigitst Period It indicates that the e-invoice shall be paid for a certain riod. PeriodName Period name rmaltext StartDate Period start date DateT EndDate Period end date DateT InvoiceDeliverer Extension It indicates the contact information of the rson who issued the invoice (phone number, address, e-mail, and name). For more detail, see Section 2.13.7 It describes the additional elements which ma be displaed. For more detail, see Section 2.13.8 ContactData Record ExtensionRec ord [0..n] 9
2.7. Invoice sum group (InvoiceSumGroup) The tag describes the sum values of the invoice and balance <InvoiceSumGroup> <Balance> <BalanceDate>2015-04-01</BalanceDate> <BalanceBegin>3.14</BalanceBegin> <Inbound>3.14</Inbound> <Outbound>3.14</Outbound> <BalanceEnd>3.14</BalanceEnd> </Balance> <InvoiceSum>1277.5678</InvoiceSum> <PenaltSum>0</PenaltSum> <Addition addcode="dsc"> <AddContent> Packing fees </AddContent> <AddRate>-5</AddRate> <AddSum>-6.3878</AddSum> </Addition> <Rounding>0.01</Rounding> <VAT> <SumBeforeVAT>1271.19</SumBeforeVAT> <VATRate>20</VATRate> <VATSum>254.24</VATSum> <Currenc>EUR</Currenc> </VAT> <TotalSum>1525.43</TotalSum> <Currenc>EUR</Currenc> <Accounting> </Accounting> <Extension extensionid=" "> </Extension> </InvoiceSumGroup> Tag Description T/value Mandator Balance It indicates the balance between the beginning and end riods BalanceDate Balance calculation date DateT BalanceBegin Balance beginning value Decimal2Fra ctiondigitst Inbound The amount paid b the e-invoice Decimal2Fra receiver to the invoice sender ctiondigitst [0..n] Outbound The amount paid b the e-invoice sender to the invoice receiver Decimal2Fra ctiondigitst [0..n] BalanceEnd Balance end value Decimal2Fra ctiondigitst tes 10
InvoiceSum PenaltSum Addition The total sum of the invoice exclusive of taxes. The sum of the values in InvoiceItemGroup/ItemEntr.ItemSu m The sum of the nalt for unpaid charges It describes other components of the sum (e.g. discounts or extra charges). Decimal5Fra ctiondigitst Decimal5Fra ctiondigitst AdditionRec ord [0..n] Rounding The rounding of the invoice sum Decimal5Fra ctiondigitst VAT Value added tax (VAT). The values VAT and InvoiceItemGroup/ItemEntr/VAT must be equal VATRecord [0..n] TotalVATSum The total sum of value added tax Decimal2Fra ctiondigitst TotalSum The e-invoice sum including taxes Decimal2Fra ctiondigitst TotalToPa Total pament sum In the credit invoice, the sum must equal to 0.00 Decimal2Fra ctiondigitst Currenc Three-letter ISO 4217 currenc code CurrencTp e Accounting Accounting elements necessar in AccountingR order to automate the invoice on the ecord sender side Extension It indicates the additional elements which ma be used in the invoice ExtensionRec ord [0..n] 11
2.8. Invoice item (InvoiceItem) This element describes the information on the items contained in the invoice. <InvoiceItem> <InvoiceTotalGroup groupid="summar"> <ItemEntr>... </ItemEntr> <GroupEntr>... </GroupEntr> </InvoiceTotalGroup> <InvoiceItemGroup groupid="pens"> <ItemEntr>... </ItemEntr> <GroupEntr>... </GroupEntr> </InvoiceItemGroup> <InvoiceItemGroup groupid="par"> <ItemEntr>... </ItemEntr> <ItemEntr>... </ItemEntr> <GroupEntr>... </GroupEntr> </InvoiceItemGroup> <InvoiceItemTotalGroup> <InvoiceItemTotalDescription>... </InvoiceItemTotalDescription> <InvoiceItemTotalSum>... </InvoiceItemTotalSum> </InvoiceItemTotalGroup> </InvoiceItem> Tag Description T/value Mandator tes InvoiceTotalGroup The group of items contained in the invoice gruopid ID ShortText Attribute ItemEntr It describes the entr of one invoice [0..n] item GroupEntr It describes the common entr of the group InvoiceItemGroup The group of invoice items [1..n] groupid ID ShortText Attribute ItemEntr It describes the entr of one invoice [1..n] item GroupEntr It describes the common entr of the group InvoiceItemTotalGroup The general element of all common items InvoiceItemTotalDescripti on The general description of items rmaltext 12
Extension Accounting It describes the additional elements which ma be displaed. For more detail, see Section 2.13.8 The additional elements which ma be used in the accounting of the paee. For more detail, see Section 2.13.2 ExtensionRec ord [0..n] AccountingR ecord InvoiceItemTotalAmount The total amount of all items. Decimal5Fra ctiondigitst InvoiceItemTotalSum The total sum exclusive of taxes. Decimal5Fra ctiondigitst Addition VAT It describes additional information, e.g. discounts or charges. For more detail, see Section 2.13.3 The field of value added tax. For more detail, see Section 2.13.10 AdditionRec ord [0..n] VATRecord InvoiceItemTotal The total sum including taxes. Decimal5Fra ctiondigitst 2.8.1. Item (itementr) The description of each individual item in the invoice. 13
<ItemEntr> <Row>1</Row> <SerialNumber>SPORT36015841</SerialNumber> <SellerProductId>RT360</SellerProductId> <BuerProductId>nxo07</BuerProductId> <TaricCode>CODE123456</TaricCode> <Accounting>... </Accounting> <CustomerRef>JONAS360</CustomerRef> <Description>Monthl ticket</description> <EAN>3272513030707</EAN> <InitialReading>0</InitialReading> <FinalReading>2</FinalReading> <ItemReserve extensionid="klubas"> <InformationName>SPORTII</InformationName> <InformationContent>L5870</InformationContent> </ItemReserve> <ItemDetailInfo> <ItemUnit>mėn.</ItemUnit> <ItemAmount>12</ItemAmount> <ItemPrice>467.36</ItemPrice> </ItemDetailInfo> <ItemSum>934.72</ItemSum> <Addition addcode="dsc"> <AddContent>Nuolaida 10%</AddContent> <AddRate>-10</AddRate> <AddSum>-93.472</AddSum> </Addition> <VAT> <SumBeforeVAT>841,248</SumBeforeVAT> <VATRate>20</VATRate> <VATSum>168.24</VATSum> <Currenc>EUR</Currenc> </VAT> <ItemTotal>1009.49</ItemTotal> </ItemEntr> Tag Description T/value Mandator Row Entr number. rmaltext SerialNumber Product/service serial number ShortText SellerProductId Product/service ID in the information ShortText sstem of the service provider BuerProductId Product/service ID in the information ShortText sstem of the paer TaricCode TARIC code. It is used in the customs EncodingT sstem of the Euroan Union. Accounting The additional elements which ma be AccountingRe used in the accounting of the paee. For cord more detail, see Section 2.13.2 CustomerRef The code to be assigned to the paee rmaltext Description Product/service description LongTextSIngl et EAN Product/service barcode number rmaltext InitialReading It is used for riodic invoices, e.g. for ShortText the readings of water and electricit meters. Beginning of the reading. FinalReading It is used for riodic invoices, e.g. for ShortText the readings of water and electricit meters. End of the reading. tes 14
ItemReserve It can be used for additional information. For more detail, see Section 2.13.8 ExtensionRecor d ItemDetailInfo Invoice item detailed information [0..n] ItemUnit Invoice item measuring unit ShortText ItemAmount Invoice item amount. Decimal5Fract iondigitst ItemPrice Invoice item amount r unit exclusive Decimal5Fract of taxes. iondigitst ItemSum Item total sum exclusive of taxes or Decimal5Fract discounts iondigitst Addition It describes additional information, e.g. AdditionRecor discounts or charges. For more detail, see Section 2.13.3 d [0..n] VAT The field of value added tax. For more VATRecord detail, see Section 2.13.9 ItemTotal Item total sum Decimal5Fract iondigitst 15
2.8.2. Group entr (GroupEntr) Group entr is used for summing up various different entries into a single logic group simplifing the presentment of the invoice to the paer. <GroupEntr> <GroupDescription>Total</GroupDescription> <Extension extensionid=" "> </Extension> <Accounting> </Accounting> <GroupAmount>4.5</GroupAmount> <GroupSum>6355.8667</GroupSum> <Addition addcode="dsc"> <AddContent>Suma</AddContent> <AddRate>-40</AddRate> <AddSum>-2542.3467</AddSum> </Addition> <VAT> <SumBeforeVAT>3813.52</SumBeforeVAT> <VATRate>20</VATRate> <VATSum>762.71</VATSum> <Currenc>EUR</Currenc> </VAT> <GroupTotal>4576.22</GroupTotal> </GroupEntr> Tag Description T/value GroupDescription Free information text describing the rmaltext group. Extension It describes the additional elements ExtensionRe which ma be displaed. For more cord detail, see Section 2.13.8 [0..n] Accounting GroupAmount GroupSum Addition VAT GroupTotal The additional elements which ma be used in the accounting of the paee. For more detail, see Section 2.13.2 The total amount of items describing the group. (The sum of ItemAmount elements) The total sum of Item sums (the sum of ItemSum elements) It describes additional information, e.g. discounts or charges. For more detail, see Section 2.13.3 The field of value added tax. For more detail, see Section 2.13.9 Group total sum. (The sum of ItemTotalelements elements) AccountingR ecord Decimal5Fra ctiondigitst Decimal5Fra ctiondigitst AdditionRec ord [0..n] VATRecord Decimal5Fra ctiondigitst Mandator tes 16
2.9. Additional information (AdditionalInformation) The additional information field can be used for indicating relevant but not mandator information in the invoice, e.g. for scial offers or ongoing promotion actions. <AdditionalInformation id="te"> <InformationName> Dear Jonas, </InformationName> <InformationContent> If ou phone the common number 1234 this month and order the M Guide service, ou will be granted a discount of 10% from the invoice for the next month. </InformationContent> </AdditionalInformation> Tag Description T/value AdditionalInformation Additional information element. It is ExtensionRe shown on the invoice. For more cord detail, see Section 2.13.8 Mandator tes 2.10. Attached file (AttachmentFile) <AttachmentFile> <FileName></FileName> <FileBase64></FileBase64> <FileSize></FileSize> </AttachmentFile> Tag Description T/value AttachmentFile Description of the attached PDF file AttechmentR ecord Mandator tes 17
2.11. Pament information (PamentInfo) The Pament information describes the required data fields for the formation of a pament order. <PamentInfo> <Currenc>EUR</Currenc> <PamentDescription>Pament of Invoice 6592 </PamentDescription> <Paable>YES</Paable> <PaDueDate>2015-04-22</PaDueDate> <PamentTotalSum>5925.21</PamentTotalSum> <PamentId>12345</PamentId> <PaToAccount>LT12121231231311121</PaToAccount> <PaToName>AB ELEKTRA</PaToName> <PaToBIC>NAAALT2X</PaToBIC> </PamentInfo> Tag Description T/value Currenc ISO currenc code CurrencTp e PamentDescription The description to be indicated in the pament transfer order PamentDes criptiont PamentRefId The number identifing the item(s) ReferenceT being paid for, e.g. the invoice number, service code, pament code, etc. Paable It indicates whether or not the invoice is paable YES means that the invoice must be paid and the PaDueDate field must be filled in. indicates that the invoice is intended for information onl. PaDueDate Paable until the indicated date DateT PamentTotalSum Pament order sum Decimal2Fra ctiondigitst Mandator tes Onl the EUR value is possible At least one of the fields must be filled in PamentId Pament number. It usuall coincides ShortText with the invoice number. It is the identifier which will be seen b the paee in the statement. PaToAccount Paee account number AccountT PaToName Paee name rmaltext PaToBIC Paee BIC Code BICT 18
2.12. Footer (Footer) The footer indicates the total sums and the number of invoices. <Footer> <TotalNumberInvoices>3</TotalNumberInvoices> <TotalAmount>29768.04</TotalAmount> </Footer> Tag Description T/value TotalNumberInvoices The total number of e-invoices in the Xs:positiveIn file. It is used for rechecking teger TotalAmount It is the total amount of all Decimal2Fra PamentTotalSum elements. ctiondigitst Mandator tes 2.13. Complex data ts 2.13.1. Account detailed description (AccountDataRecord) The fields used to describe the bank account. <AccountInfo> <IBAN>LT12121231231311121</ IBAN > <BIC>NAAALT2X</BIC> <BankName>Bank N</BankName> </AccountInfo> Tag Description T/value Mandator IBAN IBAN account number AccountT BIC BIC Code of the credit institution BICT BankName The name of the credit institution rmaltext tes 2.13.2. Accounting records (AccountingRecord) The present information required in automating paments. The paee and the paer can agree that information necessar for the automatic processing of invoices in the accounting sstem of the paer will be provided. 19
<Accounting> <Description> Electronic Invoice 2153 </Description> <JournalEntr> <GeneralLedger>4106</GeneralLedger> <GeneralLedgerDetail> </GeneralLedgerDetail> <CostObjective></CostObjective> <Sum>5000</Sum> <VatSum>900</VatSum> <VatRate>20</VatRate> </JournalEntr> <PartnerCode></PartnerCode> <BusinessCode></BusinessCode> <SourceCode></SourceCode> <CashFlowCode></CashFlowCode> <ClassificatorCode></ClassificatorCode> </Accounting> Tag Description T/value Mandator Description Journal entr description rmaltext JournalEntr [1..n] GeneralLedger ShortText The main journal entr code (it can be used as additional information for the financial entr) tes <GeneralLedgerDetai l> CostObjective Sum Detailed journal entr code Additional information used in order to identif the order centre and project code The sum which will either debit (+) or credit (-) is indicated VatSum VAT (0 not applicable). VatRate VAT rcentage expression PartnerCode Partner code BusinessCode Business area code SourceCode Source code CashFlowCode Cash flow code ClassificatorCode State budget identification code 20
2.13.3. Additional records (AdditionRecord) It describes the addition or deduction of scific amounts. It is used for the description of paable charges and discounts. <Addition addcode="dsc"> <AddContent>Loal client discount</addcontent> <AddRate>-5</AddRate> <AddSum>-6.3878</AddSum> </Addition> Tag Description T/value addcode DSC Discount. xs:nmtoken CHR Charge. DSC / CHR AddContent The name of the additional record rmaltext (e.g. Loal client discount ) AddRate The rcentage expression of the discount/charge AddSum The sum expression of the discount/charge Mandator tes Attribute 2.13.4. Address record (AddressRecord) <MailAddress> <PostalAddress1>Savanorių pr.</postaladdress1> <PostalAddress2> 100 </PostalAddress2> <Cit>Vilnius</Cit> <PostalCode>LT-03212</PostalCode> <Countr>Lithuania</Countr> <Extension id="roomnumber"> <InformationName> Reg </InformationName> <InformationContent> 17 </InformationContent> </Extension> </MailAddress> Tag Description T/value PostalAddress1 rmaltext Street name, building number, apartment number. PostalAddress2 Village, district, post box. rmaltext Cit Cit. rmaltext PostalCode Postal code. xs:string (Max: 10) Countr Countr. rmaltext Mandator tes 21
Extension Additional address information ExtensionRec ord [0..n] 2.13.5. Attached document (AttachmentRecord) <FileName></FileName> <FileBase64></FileBase64> <FileSize></FileSize> Tag Description T/value Mandator FileName The name of the attached document rmaltext FileBase64 BASE64 encoding of the attached xs:base64bina r document. FileSize The size of the attached document for xs:positiveinte ger checking. tes 2.13.6. Invoice data (BillPartRecord) It defines different parties to the invoice (it can be used for describing the service provider, service receiver, or paer). <BillPart> <GLN>1234567891234</GLN> <UniqueCode>348149</UniqueCode> <Name>AB ELEKTRA</Name> <DepId>Sales Dpt.</DepId> <RegNumber>6310130</RegNumber> <VATRegNnumber>LT1000127874 </VATRegNumber> <ContactData> </ContactData> <AccountInfo> </AccountInfo> <Extension id="licencenumber"> <InformationName> Windows Antivirus </InformationName> <InformationContent> MAM118045A </InformationContent> </Extension> </SellerPart> Tag Description T/value Mandator tes 22
GLN Global Location Number. The field is used in accordance with ISO 6523 standard. GLNT UniqueCode Unique identifier (e.g. Order Number) ShortText Name Supplier name rmaltext DepId Department name (e.g. Sales Department, Accounting Department). rmaltext regnumber Registration number RegT VATRegNumber VAT code RegT ContactData AccountInfo Extension Contact data (phone number, contact rson name). See ContactDataRecord (Section 2.13.7). Account description See AccountDataRecord (Section 2.13.1). Additional required information See ExtensionRecord (Section 2.13.8) ContactDataR ecord AccountDataR ecord [0..n] ExtensionRec ord [0..n] 2.13.7. ContactDataRecord Elements describing the invoice sender and receiver. <ContactData> <ContactName>John Smith</ContactName> <ContactPersonCode>47606140231 </ContactPersonCode> <PhoneNumber>+370 5 212348</PhoneNumber> <FaxNumber>+370 5 258741</FaxNumber> <URL>www.test.lt</URL> <EmailAddress> John.Smith@testastestas.eu <EmailAddress> <LegalAddress> </LegalAddress> <MailAddress> </MailAddress> <ContactInformation id="agentname"> <InformationName> Seller </InformationName> <InformationContent> Petras </InformationContent> </ContactInformation> </ContactData> Tag Description T/value Mandator ContactName Contract rson name. rmaltext ContactPersonCode Contract rson code. RegT PhoneNumber Contract rson phone number. rmaltex FaxNumber Contract rson fax number. rmaltext URL Internet site address. rmaltext tes 23
EmailAddress Contract rson e-mail address. xs:string pattern:.+@.+ LegalAddress Detailed legal address. See AddressRecor AddressRecord (Section 2.13.4). d MailAddress Detailed address where it does not AddressRecor coincide with the legal address. d AddressRecord (Section 2.13.4). ContactInformation Additional contact information. See ExtensionRecord (Section 2.13.8). ExtensionRec ord [0..n] 2.13.8. Extension record (ExtensionRecord) The structure enabling provision of additional information. <Extension extensionid="linktopdf"> <InformationName> text</informationname> <InformationContent> http://www2.lesugavejopuslpais.lt/saugivieta/einvoice=123405xcjdfunewf&tim esptamp=2015010101 </InformationContent> </Extension> Tag Description T/value extensionid InformationName Extension record code. If it is used, it is recommended to use standard XML sntax and name. The information name is provided Mandator tes ShortText Attribute In order to transmit a link to the own PSP as well as to other Members, use the LinkToPDF identifier. rmaltext InformationContent Information LongT It is used for transmitting a link to the PDF document located at the paee s server. If extensionid is filled with the value LinkToPDF, then the full link to the document is provided here. CustomContent Detailed description. ShortText 24
2.13.9. SellerPartRecord <SellerPart> <GLN>1234567891234</GLN> <TransactionPartnerCode>111111 </TransactionPartnerCode> <UniqueCode>348149</UniqueCode> <Name>UAB PARDUODU</Name> <DepId>Sales Dept.</DepId> <RegNumber>6310130</RegNumber> <VATRegNnumber>LT1000705445 </VATRegNumber> <ContactData> </ContactData> <AccountInfo> </AccountInfo> <Extension id="licencenumber"> <InformationName> Windows Antivirus </InformationName> <InformationContent> MAM118045A </InformationContent> </Extension> </SellerPart> Tag Description T/value GLN The global location number of the GLNT paee. The field is used in accordance with ISO 6523 standard. TransactionPartnerCode The code assigned b the responsible organisation survising the e- invoice. PartnerCode T UniqueCode Unique code (e.g. order code) ShortText Name The name of the seller or paee. rmaltext DepId The identifier of the department (e.g. rmaltext Sales Department) regnumber Registration code. RegT VATRegNumber VAT code. RegT ContactData ContactData Record AccountInfo Extension Contact data (phone number, contact rson name). See ContactDataRecord (Section 2.13.7). Account description See AccountDataRecord (Section 2.13.1). Additional required information See ExtensionRecord (Section 2.13.8). AccountData Record [0..n] ExtensionRec ord [0..n] Mandator tes 25
2.13.10. VATRecord <VAT vatid="tax"> <SumBeforeVAT>100.10</SumBeforeVAT> <VATRate>21</VATRate> <VATSum>21.02</VATSum> <Currenc>EUR</Currenc> <SumAfterVAT>121.12</SumAfterVAT> <Reference extensionid="string"> <InformationName>Text</InformationName> <InformationContent>Text</InformationContent> <CustomContent> <an/> </CustomContent> </Reference> </VAT> Tag Description T/value Mandator tes vatid VAT t NOTTAX VAT is not applicable TAXEX VAT is not applicable in this case, there are reservations TAX VAT is applicable. VatCodeT Attribute SumBeforeVAT The amount from which VAT is calculated. Decimal5Fra ctiondigitst VATRate Applicable VAT in rcentage expression Decimal2Fra ctiondigitst VATSum Calculated VAT sum Decimal5Fra ctiondigitst Currenc Currenc in accordance with ISO 4217 CurrencTp standard e SumAfterVAT Reference The total calculated sum including VAT, i.e. paable sum Additional required information See ExtensionRecord (Section 2.13.8). Decimal5Fra ctiondigitst ExtensionRec ord 2.14. Data set / t description AccountT t xs:string It is a text-t window which can have smbols, spaces, entries, and tabs restrictions maxlength 35 Maximum 35 smbols are allowed pattern ([0-9 A-Z])* Onl numerals from 0 to 9 and upr-case letters from A to Z inclusivel 26
are allowed BICT t xs:string It is a text-t window which can have smbols, spaces, entries, and tabs restrictions maxlength 11 Maximum 11 smbols are allowed CurrencT t xs:string restrictions pattern It is a text-t window which can have smbols, spaces, entries, and tabs [A-Z][A-Z][A-Z] 3 upr-case letters from A to Z DateT t xs:date Date t window According to the CCYY-MM-DD format, where: CC centur YY ear MM month DD da DateTime t xs:datetime Date and time t window According to the YYYY-MM-DDThh:mm:ss format, where: YYYY ear MM month DD da T separator indicating the beginning of the time link hh two-digit numeral indicating the hour value from 00 to 23 mm two-digit numeral indicating the minute value from 00 to 59 ss two-digit numeral indicating the hour value from 00 to 59 Decimal2FractionDigitsT t xs:decimal Decimal t window For example: 999.50 or +999.54 or -999.52 or 0. 27
restrictions fractiondigits 2 Maximum 2 digits are allowed Decimal5FractionDigitsT t xs:decimal Decimal t window For example: 9.99510 or +999.54 or -9.93952 or 0. restrictions fractiondigits 5 Maximum 5 digits are allowed EncodingT t xs:string It is a text-t window which can have smbols, spaces, entries, and tabs restrictions maxlength 10 Maximum 10 smbols are allowed GLNT t xs:string restrictions length pattern 13 \d+ It is a text-t window which can have smbols, spaces, entries, and tabs Maximum 13 smbols are allowed Onl integer numbers LanguageT t xs:string It is a text-t window which can have smbols, spaces, and entries. Language codes in accordance with ISO 639-1. 136 two-smbol codes are used for identifing the main languages used in the world. For example, the English language is denoted b en. restrictions pattern [a-z][a-z] 2-smbol lower-case letter box LongTextT t xs:string It is a text-t window which can have smbols, spaces, entries, and tabs restrictions maxlength 500 Maximum 500 smbols are allowed LongTextSingleT t xs:string It is a text-t window which can have smbols, spaces, entries, and tabs 28
restrictions minlength maxlength 1 500 Minimum 1 smbols are allowed Maximum 500 smbols are allowed rmaltext t xs:string It is a text-t window which can have smbols, spaces, entries, and tabs restrictions maxlength 70 Maximum 70 smbols are allowed PartnerCodeT t xs:string restrictions length pattern 6 ([0-9 A-Z])* It is a text-t window which can have smbols, spaces, entries, and tabs Mandator 6-smbol sequence. The first smbol must be a numeral; the next upr-case letter; others not restricted PamentDescriptionT t xs:string It is a text-t window which can have smbols, spaces, entries, and tabs restrictions maxlength 140 Maximum 140 smbols are allowed RegT t xs:string It is a text-t window which can have smbols, spaces, entries, and tabs restrictions maxlength 15 Maximum 15 smbols are allowed ReferenceT t xs:string It is a text-t window which can have smbols, spaces, entries, and tabs restrictions maxlength 20 Maximum 20 smbols are allowed pattern ([0-9])* Onl numerals 0 to 9 are allowed 29
ShortText t xs:string It is a text-t window which can have smbols, spaces, entries, and tabs restrictions maxlength 35 Maximum 20 smbols are allowed VatCodeT t xs:nmtoken It is a text-t window which can have smbols, spaces, entries, and tabs restrictions pattern NOTTAX n-vat paer pattern TAXEX VAT is not applicable in this case, there are reservations pattern TAX VAT paer t xs:nmtoken Onl smbols are allowed; spaces, tabs, and entries are not allowed. Text box NMTOKEN, attribute XML (to be used onl with the scheme attributes). restrictions pattern YES The possible value is onl either YES or NO. pattern NO Built-in data ts xs:integer Integer number t xs:positiveinteger Onl positive integer number used t (1, 2...) xs:string xs:nmtoken It is a text-t window which can have smbols, spaces, entries, and tabs It is a text-t window which can have smbols, spaces, entries, and tabs 2.15 Description of the errors of an incorrect e-invoice file Error code The PSP or the Orator will alwas check the integrit of the data being sent in several was: The agreed XML file structure will be checked with the presented XSD file Checking business and information logic For an e-invoice repl file, it is not necessar to send one repl file. Several repl files can be sent with indication of the file the repl is provided (infileid) 30
Error Cause code Errors related to the file structure 51 Incorrect file structure 62 Oversized file is being sent (the biggest rmissible file 100 MB) 59 reference to the DTD or XSD file 85 The file sender or receiver is indicated incorrectl 64 A file with the same ID has alread been received 56 The total amount of the e-invoices does not coincide with the TotalAmount element available in the Footer. 61 The total sum of the e-invoices does not coincide with the TotalNumberInvoices available in the Footer. 81 The AppId field is filled in incorrectl 63 The file name does not compl with the standard Header errors 82 The file does not scif the e-invoice address (ChannelAddress) 10 The indicated client address does not exist 22 The e-invoice address is not intended for sending 20 The e-invoice is temporaril unavailable (e.g. blocked user, blocked internet banking agreement) 76 The e-invoice address is incorrect (ChanelId) 87 The e-invoice with the same invoiceglobuniqid value from the same supplier alread exists 80 The serviceid field is indicated incorrectl (the service provider did not find a paer with such ID in his sstem) E-invoice content errors 14 The data required for the processing of factoring are incorrect Possible paee errors 11 The service provider information in the e-invoice is indicated incorrectl 57 The agreement between the paee and the bank receiver has not been found 70 The paee does not have the right to send e-invoices 25 The combination Presentmen= and Paable= is not allowed Errors related to the e-invoice pament order 6 Incorrectl indicated PamentRefId field (the reference number is inaccurate or inappropriate) 50 The pament order fields do not have the pament order number and description PamentRefId=, PamentDescription= ) 9 An impror pament sum in the PamentTotalSum box 7 The currenc indicated in the Currenc box is incorrect 49 The e-invoice pament date is illogical (the PaDueDate is in the past) 12 The e-invoice with the same PamentId from the same paee alread exists 48 The PamentId box is not indicated 54 Incorrectl indicated receiver account PaToAccount 55 The paee s name PaToName is indicated incorrectl 88 The PaToBIC is indicated incorrectl 85 Incorrect paee data 90 An incorrect TemplateId parameter its format was not agreed upon with the bank 31
91 debit invoice which could be linked with the credit invoice 92 The debit invoice linked with the credit invoice is alread paid or pament has alread been made 93 A credit invoice ma not be Paable= 94 InvoiceGlobUniqId ma not be empt 96 paer name 97 paee name 98 InvoiceDate is not filled in Repl File Tag Description T/value Mandator tes Header appid It scifies the message t ShortText The FEI value is possible. Attribute date Message forming date DateT Attribute receiverid File receiver identifier ShortText Attribute senderid File sender identifier ShortText Attribute fileid It is the unique file identifier ShortText Attribute assigned in the sstem of the sender in order to avoid the duplication of files. infileid The name of the file to which the ShortText repl is sent has been received. filefailereason The attribute to be sent in case when it is impossible to read the contents of the file or the whole file is incorrect xs:integer Attribute Invoice InvoiceId The structure which is intended for If the identifing the e-invoice and presents data on the reasons for its rejection [1..n] filefailreason value is provided in the header, it is allowed not to send this structure in the message. ChannelId The identifier which indicates the BICT PSP that found errors in the e- invoice being sent The code of the financial institution. It is possible to use, e.g. the BIC, SWIFT code. InvoiceGlobUniqId It is the unique identifier of the e- rmaltext invoice in the accounting sstem of the sender of the e-invoice. ServiceId It is the unique identifier assigned b the paee to the paer or service receiver (e.g. the client code in the information sstem of the service provider). ShortText 32
SellerContractId The number of the agreement concluded b the paee and the paee s PSP. rmaltext It is mandator if it was indicated in the e- invoice. SellerRegNumber Paee rsonal/compan code RegT FailReason Error code. xs:integer [1..n] Footer totalnr The total number of the e-invoices whose information is being sent in the file. xs:integer Attribute If the file was accepted successfull, no repl to it is sent. An example of the repl of the bank to an e-invoice file when it contains errors: <?xml version="1.0" encoding="utf-8"?> <FailedInvoice xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" > <Header appid="fei" date="2015-07-01" receiverid="receiver" senderid="sender" fileid="fei1233214" infileid="einvoice123144.xml"/> <Invoice> <ChannelId>ABCDLT2X</ChannelId> <InvoiceId>1234</InvoiceId> <InvoiceGlobUniqId>123456</InvoiceGlobUniqId> <ServiceId>1234</ServiceId> <SellerContractId>1234</SellerContractId> <SellerRegNumber>12345678</SellerRegNumber> <FailReason>33</FailReason> <FailReason>12</FailReason> </Invoice> <Footer totalnr="1"/> </FailedInvoice> Below is an example of a repl when it is impossible to read the contents of the file or the whole file is incorrect: <?xml version="1.0" encoding="utf-8"?> <FailedInvoice> <Header appid=" FEI " date="2015-07-01" receiverid="receiver" senderid="sender" fileid="file id" infileid= input file id filefailreason= 51 /> <Footer totalnr="0"/> </FailedInvoice> 3. E-invoice request ordering b electronic channels 3.1 E-invoice ordering b electronic channels If the beneficiar and his PSP agree so, then the PSP can present orders for e-invoices b his electronic channels. repl on the successful ordering of an e-invoice shall be sent. 33
The appid field has onl one value EIA. 3.2 E-invoice ordering b electronic channels When ordering the sending of e-invoices, the following data are provided: Tag Description T/value Mandator tes Header appid It scifies the message t EIA ShortText Attribute date Message forming date DateT Attribute receiverid File receiver identifier ShortText Attribute senderid File sender identifier ShortText Attribute fileid It is the unique file identifier assigned in the sstem of the sender in order to avoid the duplication of files. ShortText Attribute Application The structure describing the request for receiving e-invoices. [1..n] SellerRegNumber Paee rsonal/compan code RegT SellerContractId The number of the agreement rmaltext concluded b the paee and the paee s PSP. Action The attribute scifing the action to be rformed with the request being presented. ServiceId It is the unique identifier assigned b the paee to the agreement with the service receiver or paer (e.g. the client code in the information sstem of the service provider). ChannelId The paer s PSP to which e-invoices shall be directed. The code of the financial institution. It is possible to use, e.g. the BIC, SWIFT code. ChannelAddress It is the e-invoice receiver channel address to which the message should be directed. IBAN code PresentmentT It defines the form of sending of e- invoices to the receiver, i.e. whether the receiver will see the full e-invoice, which is the invoice, or onl information necessar to make pament. ShortText BICT Possible field values: ADD new or updated request for receiving e- invoices; DEL terminated request for receiving e- invoices. rmaltext Attribute ShortText Possible values: FULL if full information of the presented e- invoice 34
CustomerIdCode CustomerName CustomerEmail CustomerPhone TimeStamp The code/registration number of the rson submitting the request for receiving e-invoices. The name and surname/compan name of the rson on whose behalf the request is being sent. The e-mail address of the paer being transmitted to the paee. The phone number of the paer being transmitted to the paee. The request submission time in YYYY- MM-DDThh:mm:ss format should be presented to the paer; PAY if onl information necessar to make pament should be presented to the paer. RegT Attribute rmaltext rmaltext rmaltext DateTime 3.3 Example of an e-invoice order Example of an e-invoice order file: <?xml version="1.0" encoding="utf-8"?> <ApplicationBank appid="eia" date="2015-11-01" receiverid="receiver" senderid="sender" fileid="eia123456" xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" > <Application> <SellerRegNumber>987654321</SellerRegNumber> <SellerContractId>S56789</SellerContractId> <Action>ADD</Action> <ServiceId>AZ0123</ServiceId> <ChannelId>CBAAAT2X</ChannelId> <ChannelAddress>LT012345678901234567</ChannelAddress> <PresentmentT>FULL</PresentmentT> <CustomerIdCode>36002291111</CustomerIdCode> <CustomerName>Johin Smith</CustomerName> <CustomerEmail>john@smith.lt</CustomerEmail> <CustomerPhone>+37061111111</CustomerPhone> <TimeStamp>2015-05-30T09:00:00</TimeStamp> </Application> </ApplicationBank> Example of a repl to the received erroneous e-invoice order file: <?xml version="1.0" encoding="utf-8"?> <FailedApplication> <Header appid="feia" date="2015-11-01" receiverid="receiver" senderid="sender" fileid="feia123321" infileid="eia123456.xml" FailReason="51"/> </FailedApplication> 35
3.4 Description of the errors of an e-invoice order file Error code The PSP or the Orator will alwas check the integrit of the data being sent in several was: The agreed XML file structure will be checked with the presented XSD file. Checking business and information logic Error Cause code Errors related to the file structure 51 Incorrect file structure 62 Oversized file is being sent (the maximum rmissible file size 100 MB) 59 reference to the DTD or XSD file 85 The file sender or receiver is indicated incorrectl 64 A file with the same ID has alread been received 81 The AppId field is filled in incorrectl 63 The file name does not compl with the standard Header errors 82 The file does not scif the e-invoice address (ChannelAddress) 10 The indicated client address does not exist 80 The serviceid field is indicated incorrectl (the service provider did not find a paer with such ID in his sstem) 18 The e-invoice receiver does not have the right to receive a full a e-invoice. 4. Informing of a new service provider 4.1 Informing the PSP or the Orator Information on the new paee is exchanged b the PSP and/or Orators in the format presented below. Onl SCNew and SCRemove are possible in AppId. To modif a new service provider, a new SCNew message, which has the data of the previous service provider written on top of it, is used. The format of a message to be sent b the Orator or the bank to another PSP: Tag Description T/value Mandator tes Header appid It scifies the message t ShortText Possible values: SCNew when a new paee is started; SCRemove 36
when an existing paee is to be deleted from the paee. In the case of data updating, a SCNew t message is sent. Attribute date Message forming date DateT Attribute receiverid File receiver identifier ShortText Attribute senderid File sender identifier ShortText Attribute fileid It is the unique file identifier assigned in the sstem of the sender in order to avoid the duplication of files. ShortText Attribute SellerContract The structure describing the data of the paee with whom a new e- invoice submission agreement is concluded. DestinationChann el SellerOrator The paee s PSP to be informed of the new paee. The code of the financial institution. It is possible to use, e.g. the BIC, SWIFT code. The code of the Orator through which the paee sends e-invoices to the PSP. The paee s name to be shown to the paer. BICT Receiver Channel Id ShortText SellerName rmaltext It not necessaril should coincide with the paee s legal name SellerRegNumber Paee rsonal/compan code RegT Attribute GlobalSellerContra ctid TemplateId The number of the agreement concluded b the paee and the paee s PSP. The value of the field must correspond to TemplateID if the paee and the paee s PSP have agreed to use a non-standard e- invoice template. rmaltext The algorithm for generating the number contract number is assigned + prefix ( e.g.1234567ab). Prefixes are published officiall on the website www.lba.lt. rmaltext LimitedPresentme nt The value indicating whether the limited presentment of the e-invoice is possible, i.e. whether or not it is possible to indicate the PAY value in the PresentmentT field of the Possible values: YES if the limited presentment of information intended for the 37
Ordering OrderInBank NameOfServic eid minlength MaxLength CheckDigit PamentPeriod FirstDa LastDa ContractComment EIA request. The YES value must be indicated at all times. The acceptance of e-invoice requests in the bank. If the field is not presented, then the Member allows ordering e-invoices at his internet channels. The value of the name of the field of the paer code in the information sstem of the service provider The minimal number of digits in the ServiceId field. The maximal number of digits in the ServiceId field. The attribute envisages whether or not the field value is digital or smbolic. The interval of date for the automatic pament for the service to be sent b the paee. The first da of the month from which the invoice can be paid. The laste da of the month b which the invoice can be paid. Additional information can be indicated in the paer s PSP if the paee concludes with the PSP a bilateral agreement on the use of this field. paer is possible. Onl the YES value is possible. Possible values: YES if it will be possible to present e-invoice requests through e-banking or at bank offices; NO if the paee will accept requests onl when the are submitted through channels supported b him. rmaltext If no value is indicated, the standard internetbank field name is seen xs:integer xs:integer Possible values: YES field check applies the code must comprise onl of digits; NO a smbolic value is possible. xs:integer xs:integer LongTextT The structure of the repl to the new message of the service provider: Tag Description T/value Mandator tes Header addid It scifies the message t ShortText The SCAcc value is possible. Attribute 38
date Message forming date DateT Attribute receiverid File receiver identifier ShortText Attribute senderid File sender identifier ShortText Attribute fileid It is the unique file identifier assigned ShortText Attribute in the sstem of the sender in order to avoid the duplication of files. infileid The file to which the repl is being sent ContractAccepted The structure confirming the acceptance or rejection of the information on the new paee. ChannelId Accepted SellerName The identifier PSP confirming or rejecting the received information on the new paee. It is possible to use, e.g. BIC, SWIFT code for ensuring the receiver channel. The attribute showing whether or not the request was accepted. The paee s name to be shown to the paer. BICT Attribute Possible values: YES information on the new paee has been received and confirmed; NO information on the new paee has been rejected. rmaltext It not necessaril should coincide with the paee s legal name SellerRegNumber Paee rsonal/compan code RegT Attribute SellerContractId The number of the agreement rmaltext Attribute concluded b the paee and the paee s PSP. Comment Comment. Error description. rmaltext It is used if the resistration of a new service provider was rejected 39
4.2 Examples of informing the PSP or the Orator <?xml version="1.0" encoding="utf-8"?> <SellerContractNew appid="scnew" date="2015-11-01" receiverid="receiver" senderid="sender" fileid="scnew123456" xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" > <SellerContract> <DestinationChannel>DCBAEE2X</DestinationChannel> <SellerOrator>OPERATOR_1</SellerOrator> <SellerName>TESTSELLER</SellerName> <SellerRegNumber>1234</SellerRegNumber> <GlobalSellerContractId>123456789</GlobalSellerContractId> <TemplateId>1</TemplateId> <Ordering> <OrderInBank>YES</OrderInBank> <NameOfServiceId>Contract number</nameofserviceid> <MinLength>5</MinLength> <MaxLength>6</MaxLength> <CheckDigit>NO</CheckDigit> </Ordering> <PamentPeriod> <FirstDa>10</FirstDa> <LastDa>20</LastDa> </PamentPeriod> <ContractComment>comment</ContractComment> </SellerContract> </SellerContractNew> Repl forming: <?xml version="1.0" encoding="utf-8"?> <SellerContractAccepted appid="scacc" date="2015-11-01" receiverid="receiver" senderid="sender" fileid="scacc123456" xmlns:xsi="http://www.w3.org/2001/xmlschema-instance" > <ContractAccepted> <ChannelId>ABCDLT2X</ChannelId> <Accepted>YES</Accepted> <SellerName>Seller s name Ž </SellerName> <SellerRegNumber>1234</SellerRegNumber> <SellerContractId>123456789</SellerContractId> <Comment>comment</Comment> </ContractAccepted> </SellerContractAccepted> 4.3 Error codes of the repl to the message on the new service provider Error code The PSP or the Orator will alwas check the integrit of the data being sent in several was: The agreed XML file structure will be checked with the presented XSD file. Checking business and information logic Error Cause code Errors related to the file structure 51 Incorrect file structure 62 Oversized file is being sent (the maximum rmissible file size 100 MB) 40
59 reference to the DTD or XSD file 85 The file sender or receiver is indicated incorrectl 64 A file with the same ID has alread been received 56 The total amount of the e-invoices does not coincide with the TotalAmount element available in the Footer. 61 The total sum of the e-invoices does not coincide with the TotalNumberInvoices available in the Footer. 81 The AppId field is filled in incorrectl 63 The file name does not compl with the standard Header errors 82 The file does not scif the e-invoice address (ChannelAddress) 10 The indicated client address does not exist 41