This guide covers the integration methods available between a B2B procurement platform and your ERP or accounting system, and how to choose the right approach for your environment.

What Does ERP Integration Do?

Unintegrated, procurement data and finance data live in separate systems. A purchase completes on the procurement platform, then gets rekeyed into the ERP for accounting, which duplicates effort, introduces reconciliation errors and delays spend visibility.

Integration removes the manual link. Requisitions generate purchase orders that flow into the ERP, supplier invoices match against those POs, and spend updates the general ledger in real time: a complete procure-to-pay workflow with no re-entry at any step.

Which Integration Method Is Right for You?

cXML Punchout

Best for organisations with enterprise procurement platforms such as SAP Ariba, Coupa, or Oracle that want users to browse an external marketplace within their existing procurement interface.

Read the Punchout Setup Guide

OCI (Open Catalog Interface)

Best for SAP-based environments. OCI is SAP's native catalog integration standard, supported across SAP ERP, SAP S/4HANA, and SAP Business One. For SAP organisations, OCI typically integrates more cleanly than cXML.

REST API

Best for organisations that need custom back-end data flows, or that have procurement platforms without native punchout support. Supports PO synchronisation, supplier data exchange, invoice matching, and spend reporting.

View API Documentation

Pre-Built Connectors

Best for SMEs and mid-market organisations using common accounting platforms such as SQL Account, AutoCount, Xero, QuickBooks, NetSuite, or Microsoft Dynamics 365. Setup is configuration-based, significantly reducing implementation time.

Platform-Specific Guidance

SAP and SAP S/4HANA — integration via OCI punchout or cXML. For SAP Ariba environments, Borong is configurable as a connected supplier via the Ariba Network.

Oracle and Oracle NetSuite — Oracle supports cXML punchout and API-based data synchronisation. NetSuite uses a pre-built connector for purchase order and invoice data flows.

Microsoft Dynamics 365 — pre-built connector and API integration available. Purchase orders raised in Dynamics 365 can be fulfilled through the procurement marketplace, with invoice and goods receipt data flowing back automatically.

SQL Account and AutoCount — widely used by Malaysian SMEs and mid-market businesses. Pre-built connectors handle purchase order and invoice data synchronisation. Setup typically takes one to three days.

Xero and QuickBooks — connectors sync procurement spend data with the accounting platform, keeping purchase order records and supplier payment data current without manual reconciliation.

Workday and Sage — Workday integration supports enterprise procurement and HR-linked purchasing workflows. Sage integration covers mid-market accounting.

SAP Oracle NetSuite Microsoft Dynamics 365 SQL Account AutoCount Xero QuickBooks Workday Sage Explore all integrations

What to Confirm Before You Start

Confirm the following with your IT or ERP team before beginning integration:

The version of your ERP or accounting platform, and whether your current licence supports the integration method you plan to use.
The data fields that need to flow between systems: which fields in the procurement platform map to which fields in the ERP.
Whether a test or sandbox environment is available for pre-production testing.
The internal IT resource available during setup and testing.

Planning upfront prevents the common failures: field mapping mismatches, currency configuration errors and entity-level routing problems. Most integration failures are configuration problems that planning would have caught.

Multi-Entity and Multi-Country Organisations

Across multiple legal entities or countries, procurement data has to attribute to the right entity, which means matching entity structures in both systems and configuring approval workflows, cost centre assignments and currency at entity level rather than organisation level.

On a multi-entity or multi-country configuration, involve the integration team early. Correcting entity-level misattribution after data has flowed through costs far more than getting it right at setup.

Frequently Asked Questions

Can't find the answer you're looking for? Reach out to our customer support team.

How long does ERP integration typically take?

Pre-built connectors for SQL Account, AutoCount, Xero, and QuickBooks take one to three days of configuration. Enterprise integrations using cXML, OCI, or custom API, such as SAP, Oracle, or Microsoft Dynamics 365, take two to six weeks, depending on ERP environment complexity and internal IT availability.

Does integration require IT involvement?

Yes, for initial setup. Most integration methods require ERP administrator access for configuration and testing. Pre-built connectors for SME accounting platforms such as Xero or QuickBooks can often be configured by a finance or operations team member with admin credentials, with no developer involvement needed.

What if our ERP is an older version without native punchout support?

For older ERP versions that do not support cXML or OCI natively, REST API integration is the recommended approach. This requires development effort on both sides but does not depend on punchout protocol support. Contact integrations@borong.com for a technical consultation if you are unsure which integration path applies to your ERP version.

Can we integrate multiple entities under one Borong account?

Yes. Borong supports multi-entity configurations with separate approval workflows, cost centre structures, and spend reporting by entity. The integration must map entity identifiers correctly between Borong and your ERP to ensure purchase order and invoice data flows to the correct entity. Discuss your entity structure with the integration team before beginning setup.

Not Sure Which Integration
Path Fits Your ERP?

Talk to our integration team for a technical consultation on your specific ERP version and environment.

Contact Integration Team Book a Demo

ERP Integration Guide: Connecting Your Procurement Platform to Your Finance System