HubBroker iPaaS Network and Trading Partner Integration
HubBroker iPaaS enables organisations to connect ERP, finance, e-commerce, procurement, logistics and other business applications with customers, suppliers, trading partners and external networks.
Business documents and structured data can be validated, transformed, enriched, routed and monitored through the HubBroker integration platform using supported protocols and document standards.
Integration scenarios
When planning integrations between customers' on-premise systems, the HubBroker iPaaS Network, and other trading partners then it´s important to have a clear understanding of the integration scenario that needs to be supported. Click here to see a short introduction to the main scenarios of self-service procurement based on SAP SRM.
See HubBroker iPaaS - SAP SRM Integration scenarios.
Supply network collaboration on the other side can become quite complex depending on the level of globalization and outsourcing. Various business processes between trading partners (buyers and suppliers) may involve different systems and third parties (e.g. service providers). Direct B2B integrations supporting instant electronic communication replacing older methods, such as phone, fax, or e-mail usually speed up goods delivery and payments which is true business value for both parties.
See HubBroker iPaaS - Supply network collaboration - Integration scenarios.
Integration process
The process of integrating customer's ERP, eProcurement or Finance & Accounting systems with the HubBroker iPaaS Network is usually handled in form of scheduled integration projects with predefined scope and time frame. With help from experienced integration consultants, the interfaces are first configured in a test environment where connectivity and certain scenarios reflecting different business processes and error cases are tested.
See HubBroker iPaaS - Integration process.
Standard protocols for integration
HubBroker supports secure integration protocols appropriate to the connected system and business requirement. Depending on the integration scenario, supported methods may include HTTPS APIs, SFTP, FTPS, AS2 and other agreed protocols.
Secure transport should use current TLS configurations or protocol-specific encryption and authentication mechanisms. Authentication may include API credentials, tokens, certificates, SSH keys or other supported methods depending on the endpoint and protocol.
See HubBroker iPaaS - Protocols.
Document types
The main business document types reflecting the Procure-To-Pay business processes are Order, ChangeOrder, OrderResponse and Invoice/CreditNote. HubBroker iPaaS trading partners are exchanging these documents via the HubBroker iPaaS transaction hubxml where they are mapped to the different formats depending on the receiver's capabilities.
See HubBroker iPaaS - Document Types.
Formats
Inbound as well as outbound various XML and flat file formats are supported such as SAP IDoc / IDoc XML, Peppol BIS document profiles, xCBL 3.0 and 3.5, UBL 2.x, cXML, EDIFACT, ANSI X12, CSV, JSON, PDF. Detailed specifications are provided on demand.
See HubBroker iPaaS - Formats.
Interoperability
The HubBroker iPaaS Network is hosting a certified PEPPOL access point providing a gateway to the European PEPPOL Transport Infrastructure. Via the HubBroker iPaaS Service Metadata Publisher (PEPPOL-SMP) trading partners can be registered in the PEPPOL network with their individual capabilities in terms of supported document types and business collaboration profiles. See CEN BII - PEPPOL. HubBroker iPaaS is the further member of the European eInvoice Service Provider Association and together with other members working on standards for interoperability agreements between service provides to support the wide adoption of e-invoicing and its benefits.
See the official EESPA website.
Category: GDPR
Last date of update: 26.08.2026
