Clean Integration. No Manual Entry. Data Where It Needs to Be.
IT and ERP owners are asked to connect a new procurement platform to existing financial systems without creating data integrity issues, security gaps, or a manual reconciliation burden. Borong is built to make that straightforward. Standard integration protocols, supported ERP systems, SSO, and strict data isolation. No custom builds required.
What IT Teams Are Usually Asked to Solve
When a new procurement platform is introduced, IT and ERP owners face a predictable set of problems. The platform needs to connect to the ERP without manual data transfer between systems. User access needs to be managed through existing identity providers, not a separate login system. And the data the platform processes needs to stay isolated, secure, and inaccessible to other organisations on the same infrastructure.
These requirements are standard. The problem is that many procurement platforms treat integration as an afterthought, requiring custom development work, manual reconciliation steps, or data exports that introduce errors at every transfer point. Borong is built differently.
What Borong Provides for IT and ERP Teams
cXML and OCI Punchout Integration
Borong supports industry-standard cXML and OCI punchout protocols, the same standards used by major enterprise procurement platforms globally. Users access Borong's supplier catalogue directly from within their ERP using a single sign-on link. When they are ready to order, the basket is transferred back to the ERP as a structured purchase requisition automatically. No screen-switching. No manual data entry. No format mismatches.
Single Sign-On (SSO)
Borong supports SSO integration, so users access the platform through your existing identity provider. There is no separate Borong login to manage, no additional credential provisioning process, and no risk of orphaned accounts when staff leave. User access is managed centrally through the same identity management system you already use.
Bi-Directional Data Sync
The integration runs in both directions. Purchase requisitions flow from the ERP into Borong when a punchout session is initiated. Approved purchase orders flow from the ERP back to Borong to trigger fulfilment. Invoice records, delivery confirmations, and transaction status updates flow back into the ERP automatically. Your master financial ledger stays accurate without any manual intervention.
Multi-Tenant Data Encryption and Isolation
Borong operates on a multi-tenant architecture where each organisation's data is encrypted and isolated at the infrastructure level. Your organisation's spend data, contract terms, supplier pricing, and user activity are inaccessible to other organisations on the platform. There is no shared data layer between tenants. Borong is a platform facilitator that does not buy or resell products, meaning there is no commercial incentive to access or aggregate your procurement data.
Sandbox Environment for Testing
Borong provides a dedicated test environment for integration validation before production go-live. Your team can verify data flows, test punchout sequences, confirm SSO configuration, and validate approval routing without any risk to live transactions or financial records.
Supported ERP and Financial Systems
Borong has tested and supported integrations with the following systems:
- SAP and SAP Ariba: full support for complex multi-entity and public sector environments
- Oracle Procurement Cloud: native data mapping for enterprise and government workflows
- Oracle NetSuite: real-time transaction sync for high-growth commercial organisations
- Coupa Business Spend Management: direct cXML integration for indirect spend programmes
- Microsoft Dynamics 365: integration for mid-market and enterprise Microsoft ecosystem users
- SQL Account, AutoCount, and Xero: supported for SME and growing organisations
If your system is not on this list, contact our integration team to discuss compatibility.
Implementation Timeline
Standard cXML punchout integrations for supported ERP systems typically take two to four weeks. This includes technical configuration, catalogue mapping, SSO setup, user acceptance testing, and go-live support. Borong provides a dedicated integration engineer for the implementation period.
More complex integrations involving custom ERP configurations, multiple legal entities, or parallel system running take longer. We scope the timeline during the technical discovery call.
Frequently Asked Questions
Can't find the answer you're looking for? Reach out to our customer support team.
Does Borong support multi-factor authentication?
Borong supports MFA through your existing identity provider when SSO is configured. Your organisation's MFA policies apply to Borong access automatically. Standalone MFA options are available for organisations not using SSO.
What security certifications does Borong hold?
Borong's security posture covers multi-tenant data encryption, role-based access controls, and data isolation at the infrastructure level. Contact our integration team for current certification documentation.
Can we use Borong's data in our own BI tools or custom reporting dashboards?
Borong's data layer supports integration with external BI tools and reporting infrastructure. Spend data, transaction records, and approval logs can be surfaced through your existing analytics stack. Raise this requirement during the technical discovery call and our integration team will confirm the supported connection methods for your environment.
What is Borong's uptime SLA and how are incidents communicated?
Speak to our integration team for current SLA documentation. Borong maintains a status page and communicates system incidents directly to nominated technical contacts at your organisation.
What happens to our data if we stop using Borong?
Your organisation's data, including transaction records, audit logs, supplier agreements, and spend history, remains yours. On offboarding, Borong provides a full data export in structured format. Data is retained in Borong's system for a defined period in accordance with applicable data retention requirements, then deleted. You are not locked in to retain access to your own records.
Ready to Scope
the Integration?
Speak with a Borong integration specialist about punchout configuration, SSO setup, sandbox testing, and the timeline for your ERP environment.