Das Buchhaltungs-System des ÖBB-Konzerns steht am Dienstag den 15.01.2019 von 17:00 - 19:00 Uhr nicht zur Verfügung. Die Bestätigungsmails für - in diesem Zeitraum - eingebrachte E-Rechnungen verzögert sich dementsprechend!

Sa. 19.01.2019 - So. 20.01.2019:

Auf Grund von Wartungsarbeiten kann es zu Netzwerkausfällen kommen. Die Verfahren E-RECHNUNG.GV.AT und TEST.E-RECHNUNG.GV.AT werden daher zeitweise nicht erreichbar sein bzw. können Mitteilungen über eingebrachte e-Rechnungen verzögert, jedenfalls jedoch nach Abschluss der Wartungsarbeiten übermittelt werden!

Desweiteren ist am 19.01.2019 im Zeitraum von 14 bis 24 Uhr keine Rechnungseinbringung möglich, da das USP Portal in diesem Zeitraum nicht zur Verfügung steht und somit keine Authentifizierung möglich ist. Dies betrifft alle Einlieferungskanäle (Formular, Upload und Webservice).

ebInterface

ebInterface Logo

ebInterface is the Austrian XML-standard for e-Invoices specified and standardised by the Austrian Chamber of Commerce (WKO/AUSTRIAPRO) in collaboration with the industry. The official site is available under www.ebinterface.at. Planning to create your e-Invoices with ebInterface it is recommended to use version 4.1, 4.2, 4.3 or 5.0 since it offers the best support for the requirements of an e-Invoice to the public sector. ebInterface sample files can be downloaded from this page.

Note: for testing your ebInterface invoice it is possible to either display it with explanations or upload it for testing purposes in Test Upload.

Deviating from standard ebInterface e-Invoices to the public sector apply following special rules for certain data fields. There are specific XML schemata available, with witch the specific requirements for the public sector can be checked in advance.

Note: for each ebInterface version only the modified main XML schema can be downloaded. The additional XML schemata for each version are available on the official website of ebInterface.

Note: ebInterface 3.0 and 3.02 are unsupported since January 2016 since the formats are deprecated. There are currently no plans to stop supporting ebInterface 4.0 in the near future!

  • Format of the document: ebInterface version 5.0 - official specification
  • The most important differences to the standard ebInterface format are:
    • An e-Invoice may not refer to multiple orders at once.
    • The attribute DocumentType must only be one of the following values Invoice, InvoiceForAdvancePayment, InvoiceForPartialDelivery, FinalSettlement or CreditMemo
    • The element InvoiceRecipient/OrderReference/OrderID is mandatory and has to be filled with the order reference (either to the Federal Government or to the other public sector).
    • If the receiver is a Federal Government agency and the order reference is an order number (10 digits numeric) an appropriate order position number has to be entered in the field InvoiceRecipientsOrderReference/OrderPositionNumber. Federal Government order position numbers are always numeric.
      In this case the element InvoiceRecipientsOrderReference/OrderID must also be used and should be filled with the same value as the header element OrderID.
    • The TradingName element is ignored.
    • All AddressExtension elements are ignored.
    • Within the Biller element at least one Email address must be indicated.
    • The element Biller/InvoiceRecipientsBillerID must contain the supplier number (details for usage by the Federal Government).
    • At last 999 invoice lines are possible.
    • The percentage of cash discount amounts must be greater than 0 and less than 100.
    • An maximum of Discount elements are allowed.
    • When payment method UniversalBankTransaction is used exactly one BeneficiaryAccount element must be provided.
    • The payment methods PaymentCard and OtherPayment are not supported.
    • Invoices must contain a payment method (UniversalBankTransaction, SEPADirectDebit or NoPayment). Credit notes do not require such a field.
    • For payment transfer BIC and IBAN must be provided.
    • The element MinimumPayment is not evaluated
    • The payment method NoPayment may only be used for credit notes or invoices with a payable amount of zero.
    • The element Delivery/Comment may contain at most 500 characters.
    • The element ListLineItem/DiscountFlag is not evaluated.
    • The field below ListLineItem/AdditionalInformation are not evaluated.
    • The attribute BaseQuantity in a ListLineItem cannot be evaluated by E-RECHNUNG.GV.AT. Therefore either the value of the element Quantity or the value of the element UnitPrice is used for division by the value of element BaseQuantity. If in both cases a value with more than 4 decimal digits arise the invoice must be rejected, since it cannot be processed correctly.
    • The element TotalGrossAmount is neither checked nor evaluated. Only the element PayableAmount is validated and processed.
  • For certain values no explicit elements are available. Therefore they have to be put in generic elements as follows:
    • The company headquarters according to section 14 of the UGB (Austrian Commercial Code) must be provided in the element /Invoice/Biller/FurtherIdentification. The attribute IdentificationType must have the value FS (German Firmensitz = headquarters).
      Example: <eb:FurtherIdentification eb:IdentificationType="FS">Wien</eb:FurtherIdentification>
    • The commercial register number according to section 14 of the UGB must be provided in the element /Invoice/Biller/FurtherIdentification. The attribute IdentificationType must have the value FN (German Firmenbuchnummer = commercial register number).
      Example: <eb:FurtherIdentification eb:IdentificationType="FN">12345678</eb:FurtherIdentification>
    • The commercial register court according to section 14 of the UGB must be provided in the element /Invoice/Biller/FurtherIdentification. The attribute IdentificationType must have the value FBG (German Firmenbuchgericht = commercial register court).
      Example: <eb:FurtherIdentification eb:IdentificationType="FBG">Handelsgericht Wien</eb:FurtherIdentification>
  • Format of the document: ebInterface version 4.1/4.2/4.3 - official specification
  • The most important differences to the standard ebInterface format are:
    • An e-Invoice may not refer to multiple orders at once.
    • The attribute DocumentType must only be one of the following values Invoice, InvoiceForAdvancePayment, InvoiceForPartialDelivery, FinalSettlement or CreditMemo
    • The element InvoiceRecipient/OrderReference/OrderID is mandatory and has to be filled with the order reference (either to the Federal Government or to the other public sector).
    • If the receiver is a Federal Government agency and the order reference is an order number (10 digits numeric) an appropriate order position number has to be entered in the field InvoiceRecipientsOrderReference/OrderPositionNumber. Federal Government order position numbers are always numeric.
      In this case the element InvoiceRecipientsOrderReference/OrderID must also be used and should be filled with the same value as the header element OrderID.
    • All AddressExtension elements are ignored.
    • Within the Biller element at least one Email address must be indicated.
    • The element Biller/InvoiceRecipientsBillerID must contain the supplier number (details for usage by the Federal Government).
    • At last 999 invoice lines are possible.
    • The percentage of cash discount amounts must be greater than 0 and less than 100.
    • An maximum of Discount elements are allowed.
    • When payment method UniversalBankTransaction is used exactly one BeneficiaryAccount element must be provided.
    • Invoices must contain a payment method (UniversalBankTransaction, DirectDebit, SEPADirectDebit or NoPayment). Credit notes do not require such a field.
    • For payment transfer BIC and IBAN must be provided.
    • The element MinimumPayment is not evaluated
    • The payment method NoPayment may only be used for credit notes or invoices with a payable amount of zero.
    • The element Delivery/Comment may contain at most 500 characters.
    • The element ListLineItem/DiscountFlag is not evaluated.
    • The field below ListLineItem/AdditionalInformation are not evaluated.
    • The element PresentationDetails is not evaluated.
    • The attribute BaseQuantity in a ListLineItem cannot be evaluated by E-RECHNUNG.GV.AT. Therefore either the value of the element Quantity or the value of the element UnitPrice is used for division by the value of element BaseQuantity. If in both cases a value with more than 4 decimal digits arise the invoice must be rejected, since it cannot be processed correctly.
    • The element TotalGrossAmount is neither checked nor evaluated. Only the element PayableAmount is validated and processed.
  • For certain values no explicit elements are available. Therefore they have to be put in generic elements as follows:
    • The company headquarters according to section 14 of the UGB (Austrian Commercial Code) must be provided in the element /Invoice/Biller/FurtherIdentification. The attribute IdentificationType must have the value FS (German Firmensitz = headquarters).
      Example: <eb:FurtherIdentification eb:IdentificationType="FS">Wien</eb:FurtherIdentification>
    • The commercial register number according to section 14 of the UGB must be provided in the element /Invoice/Biller/FurtherIdentification. The attribute IdentificationType must have the value FN (German Firmenbuchnummer = commercial register number).
      Example: <eb:FurtherIdentification eb:IdentificationType="FN">12345678</eb:FurtherIdentification>
    • The commercial register court according to section 14 of the UGB must be provided in the element /Invoice/Biller/FurtherIdentification. The attribute IdentificationType must have the value FBG (German Firmenbuchgericht = commercial register court).
      Example: <eb:FurtherIdentification eb:IdentificationType="FBG">Handelsgericht Wien</eb:FurtherIdentification>
  • Format of the document: ebInterface version 4.0 - official specification
  • The most important differences to the standard ebInterface format are:
    • An e-Invoice may not refer to multiple orders at once.
    • The attribute DocumentType must only be one of the following values Invoice, InvoiceForAdvancePayment, InvoiceForPartialDelivery, FinalSettlement or CreditMemo
    • The element InvoiceRecipient/OrderReference/OrderID is mandatory and has to be filled with the order reference (either to the Federal Government or to the other public sector).
    • If the receiver is a Federal Government agency and the order reference is an order number (10 digits numeric) an appropriate order position number has to be entered in the field InvoiceRecipientsOrderReference/OrderPositionNumber. Federal Government order position numbers are always numeric.
      In this case the element InvoiceRecipientsOrderReference/OrderID must also be used and should be filled with the same value as the header element OrderID.
    • All AddressExtension elements are ignored.
    • Within the Biller element at least one Email address must be indicated.
    • The element Biller/InvoiceRecipientsBillerID must contain the supplier number (details for usage by the Federal Government).
    • At last 999 invoice lines are possible.
    • The percentage of cash discount amounts must be greater than 0 and less than 100.
    • An maximum of Discount elements are allowed.
    • When payment method UniversalBankTransactionType is used exactly one BeneficiaryAccount element must be provided.
    • Invoices must contain a payment method (UniversalBankTransactionType, DirectDebitType or NoPaymentType). Credit notes do not require such a field.
    • For payment transfer BIC and IBAN must be provided.
    • The element MinimumPayment is not evaluated
    • The payment method NoPaymentType may only be used for credit notes or invoices with a total gross amount of zero.
    • The element Delivery/Comment may contain at most 500 characters.
    • The element ListLineItem/DiscountFlag is not evaluated.
    • The field below ListLineItem/AdditionalInformation are not evaluated.
    • The element PresentationDetails is not evaluated.
  • For certain values no explicit elements are available. Therefore they have to be put in generic elements as follows:
    • The company headquarters according to section 14 of the UGB (Austrian Commercial Code) must be provided in the element /Invoice/Biller/FurtherIdentification. The attribute IdentificationType must have the value FS (German Firmensitz = headquarters).
      Example: <eb:FurtherIdentification eb:IdentificationType="FS">Wien</eb:FurtherIdentification>
    • The commercial register number according to section 14 of the UGB must be provided in the element /Invoice/Biller/FurtherIdentification. The attribute IdentificationType must have the value FN (German Firmenbuchnummer = commercial register number).
      Example: <eb:FurtherIdentification eb:IdentificationType="FN">12345678</eb:FurtherIdentification>
    • The commercial register court according to section 14 of the UGB must be provided in the element /Invoice/Biller/FurtherIdentification. The attribute IdentificationType must have the value FBG (German Firmenbuchgericht = commercial register court).
      Example: <eb:FurtherIdentification eb:IdentificationType="FBG">Handelsgericht Wien</eb:FurtherIdentification>

Implementation

E-RECHNUNG.GV.AT uses the Open Source Java library ph-ebinterface to process ebInterface invoices in a structured way. This library supports reading and writing of all ebInterface versions mentioned above.