E-invoicing Glossary

E-invoicing Glossary

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



Acknowledgement (ACK). Signal or message, which states that data sent is received correctly or not. ACK messages can contain detailed information for reason why e.g. invoice is rejected.

Ampersand - & sign. In e-invoicing material this &-sign must be given as entity &


Basware Banking - Basware Banking is the most comprehensive and efficient solution in the market for automating the banking of companies and other organizations and utilizing the data transfer solutions offered by banks. It can be used for retrieving bank statements, reference payments and exchange rates as well as transmitting payment and wages, for instance. The software automatically refines retrieved bank statements further into accounting entries. Due to its modular structure, Basware Banking is suitable for companies and organizations of all sizes. The software works well in a multi-company environment and even as a centralized banking solution in a service center.

BT-monitor - In Basware Business Transactions Monitor you can monitor and search for invoices. If you are an invoice sender, you can view files and invoices you have sent to your customers. In receiver role, you can view received files.   


CENBII - an UBL-based XML format used for the OpenPEPPOL network, it currently exists in a version 1 and version 2. CENBII is meant to be used for international transfers on OpenPEPPOL, whereas domestic transfers will generally use a localized version of CENBII (e.g. EHF, SimpleInvoice).


DTD - The purpose of a DTD (Document Type Definition) is to define the legal building blocks of an XML document. A DTD defines the document structure with a list of legal elements and attributes.


E-invoice - an e-invoice is an electronic invoice that can be processed automatically. Therefore it contains more than just an image of an invoice. An e-invoice also contains data in a format that computers can understand. Note that this means an e-mail with a PDF file attached is not an e-invoice.

E-invoice address - is the ID used to send or receive an e-invoice. The type of ID used differs depending on the country and the format in use. Typical IDs include GLN, DUNS, VAT-ID, IBAN, and OVT. A sender must know a recipient's e-invoice address in order to send an e-invoice. The message is routed to the recipient by any operator along the way using the e-invoice address.

EDI - (Electronic Data Interchange for Administration) The electronic communication of business transactions, such as orders, confirmations and invoices, between organizations. Third parties provideEDI services that enable organizations with different equipment to connect. Although interactive access may be a part of it, EDI implies direct computer-to-computer transactions into vendors'databases and ordering systems.

Electronic signature - An electronic signature, or e-signature, is any electronic means that indicates either that a person adopts the contents of an electronic message, or more broadly that the person who claims to have written a message is the one who wrote it (and that the message received is the one that was sent). By comparison, a signature is a stylized script associated with a person. In commerce and the law, a signature on a document is an indication that the person adopts the intentions recorded in the document. Both are comparable to a seal.

ERP - (Enterprise Resource Planning) An integrated information system that serves all departments within an enterprise. Evolving out of the manufacturing industry, ERP implies the use of packagedsoftware rather than proprietary software written by or for one customer. ERP modules may be able to interface with an organization's own software with varying degrees of effort, and, depending onthe software, ERP modules may be alterable via the vendor's proprietary tools as well as proprietary or standard programming languages.


Finvoice - Xml-format used in e-invoicing. Bank operators accept only finvoice in Finland.




IBAN - International Bank Account Number is an internationally agreed means of identifying bank accounts across national borders with a reduced risk of propagating transcription errors. The IBAN consists of up to 34 alphanumeric characters: first the two-letter ISO 3166-1 alpha-2 country code, then two check digits, and finally a country-specific Basic Bank Account Number (BBAN). The check digits enable a sanity check of the bank account number to confirm its integrity even before submitting a transaction. The BBAN format is decided by each national banking community under the restriction that it must be of a fixed length of case-insensitive alphanumeric characters. It includes the domestic bank account number, branch identifier, and potential routing information.

Intermediator (Operator) - E-invoicing operator which the customer uses to send or receive e-invoices






Negative acknowledgement (NACK). Signal or message, which states that data sent is not received correctly. NACK messages can contain detailed information for reason why e.g. invoice is rejected. See "ACK".

NemHandel - is an open point-to-point network of sending/receiving web services in Denmark, it is mandatory for a Danish public authority to be able to receive via NemHandel. It means "EasyTrade" in Danish. See "Danish e-Invoicing".


OpenPEPPOL - is an open point-to-point network of sending/receiving web services to cover all of Europe, it is currently primarily in use in Finland, Netherlands, Norway, and Sweden. CENBII v1 is the base format, but domestic transfers might use a localized version.

Operator (Intermediator) - E-invoicing operator which the customer uses to send or receive e-invoices

OVT-code - (Organisaatioiden välinen tiedonsiirto) OVT is formed from company code (without hyphen) with 0037 prefix (e.g. 003712345678)





SOAP (Finvoice) - Transmission frame (SOAP) specifies the sender, recipient and service provider data. The service provider routes the message to its recipient on the basis of frame data. File may include several Finvoice messages. Each message must include a transmission frame (SOAP).

SOAP (generic) - Simple Object Access Protocol is a web service protocol or message framework for transfering XML-based messages between web services. BT does not support UBL directly, but it is able to identify and handle an UBL message wrapped in a SOAP-envelope.

SOAP (message) -  SOAP contains the meta-data required to exchange the business document in a secure and reliable manner, while the business payload is attached to the SOAP message.

Svefaktura - Standard e-invoice format in Sweden

SWIFT - Society for Worldwide Interbank Financial Telecommunications. A cooperative society that provides highly secure message communications between banks. It does not transfer money or any other financial materials, but simply provides information. It also standardizes forms between members so as to reduce costs and operational risk. Founded in 1973 and headquartered in Belgium, SWIFT has thousands of members in more than 200 countries worldwide.


TEAPPS- A TEAPPSXML description is a structured method, created by Tieto and based on XML technology, for presenting invoice message. TEAPPSXML has proven to be a contentually comprehensive method of providing a general invoice message description, suitable for all types of invoices. The needs of business processes, economic steering and economic administration are used as the starting point for the message description.

Tieke - (Tietoyhteiskunnan kehittämiskeskus) Administrates the Finnish e-invoicing address book which is updated by e-invoice operators.


UBL Universal Business Language, is an XML-based format with corresponding business processes created by OASIS, it amongst others contains scenarios for Sourcing, Ordering, and Billing. Many newer formats (EHF, CENBII and OIOUBL) are localizations of UBL 2.0.


Validation - e-invoice xml-data is validated usually against schema which means that the structure and content of the data is checked. Failed validation means that the invoice is going to be rejected by the receiving operator which then sends negative acknowledgement to sending operator which forwards the acknowledgement to sender.