How we define some key terms in integrations and B2B business message exchange.
B2B
When referring to B2B (Business to Business) in the context of business message exchange, it denotes an external message exchange between two distinct entities. These entities do not have a direct linkage through a unified network, such as subsidiaries or shared systems and/or operators. Typically, B2B signifies that data is transmitted via the Internet, although it may still employ VPNs, shared certificates, etc.
Exchange
While terms like EDI, VAN, and operator might be prevalent in discussions about message exchanges, we will exclusively use the term B2B for external exchanges. A message exchange between two parties, whether B2B or an integration, consists of the Protocol and the Data (the message content). The Protocol serves as the transporter of the message, whereas the message encapsulates the data to be transferred.
Protocols
While Qvalia recognizes several transfer protocols, we expand the technical definition of "protocol" beyond just HTTP and SFTP to encompass API, Peppol, and "Transportprofil Bas", even though they all operate over the HTTP protocol. It's crucial to remember that the protocol functions merely as a conduit. The actual "protocol" typically incorporates security features like passwords, certificates, etc., ensuring a secure connection and transfer.
Integrations
The term "Integrations" encompasses the message exchange between Qvalia's platform and our associated client or partner.
VAN (Value Added Network)
A VAN is broadly utilized to denote the employment of an intermediary or an "Operator" that facilitates message exchange. When using a VAN, the primary Integration is usually with the VAN, which then manages the B2B aspects. This can be analogized to a postal system where messages are handed over for subsequent delivery. Typically, a VAN exchange involves four parties: the sender, the sending VAN, the receiving VAN, and the receiver.
Messages
Standards
Messages can be described in terms of their type or syntax. Sometimes, we refer to established standards for messages. For instance, Qvalia employs the Peppol BIS Billing 3.0 standard for Invoices and CreditNotes. We utilize the Peppol BIS 3 standards as the foundational format for other message types. Additionally, we support several other standard Integration formats, and we can customize transformations to accommodate clients who may not be versed in the Peppol BIS formats. For B2B formats, we natively support various types, with custom configurations available for others.
Syntax
Two primary syntaxes are in widespread use: XML and JSON. Most systems, like ERPs, utilize XML, while web interfaces and APIs often rely on JSON. Through our API, users can send or receive messages in the Peppol BIS format, either as original Peppol XML or its JSON representation.
For more information, visit our API documentation.