SAP Business One integrations: APIs, connectors and how to scope them

When a UK finance director asks for a SAP Business One connector, the real question is rarely about software. It is about a flow: orders from the web shop landing in sales, payments reconciling against the bank, VAT data reaching HMRC, payroll figures reaching the ledger. SAP Business One is designed as a core that other systems plug into, so the answer is almost always a combination of an API, a packaged add-on and a little configuration.

This page explains what the platform offers, how the main connection routes differ, which families of integration a British SME typically needs and how to scope a flow so that someone clearly owns it afterwards. For the wider picture of the product, start with the SAP Business One overview.

How SAP Business One is built to connect

SAP describes Business One as an ERP core designed to be extended, enriched with AI, machine learning and the cloud services of SAP Business Technology Platform (BTP). Automation templates are available through the Business Accelerator Hub and SAP Build. In practice, that means three layers you will hear about in any project:

• an API layer for developers, the Service Layer and the older DI API;
• an integration layer that orchestrates scenarios between Business One and other systems, the Integration Framework;
• a catalogue of extensions from SAP partners, covering sectors and countries.

SAP reports a large partner ecosystem, with 850 partners and more than 500 sector and country extensions (SAP, December 2025), and a product used in more than 170 countries with 50 country localisations. For a buyer, the useful reading is simple: before commissioning anything bespoke, ask whether an extension already exists for your need.

The Service Layer: the API most projects start from

The API SAP Business One developers use most today is the Service Layer. SAP defines it as a REST extension API built on HTTP and OData, with data exchanged in JSON. According to the guide dated 27 July 2026, it accepts OData v3 through /b1s/v1/$metadata and OData v4 through /b1s/v2/$metadata.

A few technical points matter to non-developers because they affect cost and hosting:

• It runs on SUSE Linux Enterprise and on Microsoft Windows (from 10.0 PL01).
• It relies on the Apache server as a load balancer and can be deployed in an embedded or a distributed mode.
• It shares object definitions with the DI API through the DI Core component, so a business rule behaves the same whichever route is used.
• It supports Basic and OAuth authentication and is intended to make web and mobile applications easier to build.

Why does this matter? Because the Service Layer is the doorway a web shop connector, a mobile sales app or a customer portal will use. How it is deployed influences performance under load and the security model, which you should discuss with the team handling your hosting and cloud choices.

The Integration Framework: orchestrating scenarios

SAP presents the Integration Framework as part of SAP Business One, usable on premise and in the cloud, and as an environment to develop and run integration scenarios. Its documented use cases include dashboards, mobile applications, outsourced payroll, automated price requests, SAP Customer Checkout, web services and both SAP and non-SAP applications.

Think of it as the plumbing for flows where something must be transformed, queued or retried, rather than a single call. If an integrator proposes it, ask which scenarios will run on it, who monitors them and how failures are reported.

Choosing between a packaged add-on and a custom flow

Most disputes in integration projects come from choosing the wrong route. This comparison helps frame the discussion.

Neither route is inherently better. A good integrator will start with the add-on and only build what the add-on cannot do, then document the boundary. Our guide to choosing an ERP integrator lists the questions to ask, and the page on choosing a SAP Business One partner applies them to this product.

The integration families a UK business typically needs

E-commerce and marketplaces

Online selling is the most common reason for an intégration SAP Business One project. The flow to specify covers product and price publication, stock levels, order import, customer matching, shipping status and refunds. Decide who is the master for each data item. If the shop owns product descriptions and the ERP owns stock, say so explicitly. Check how the connector handles VAT treatment, discount codes and partial shipments, because these are where manual rework creeps back in. The e-commerce ERP guide goes deeper on these choices.

Banks and payments

Bank feeds and payment services feed reconciliation and cash-flow reporting. Ask which UK banks and payment providers the chosen extension supports, whether statements are imported automatically, and how unmatched items are presented to the accounts team. Payment-run files, supplier payments and card settlement fees each need a clear route into the ledger. Day-to-day finance behaviour is covered on the accounting and finance page.

Making Tax Digital, payroll and statutory flows

British businesses have obligations that a generic connector will not cover. VAT records must support Making Tax Digital, and payroll must report through Real Time Information. Neither is something to assume. Request a live demonstration using your own VAT scheme and pay calendar. Our guides on Making Tax Digital and your ERP and on payroll software and RTI set out what to verify, and the payroll and HR page shows how Business One typically handles people data. If you also issue structured invoices to customers, read about e-invoicing and ERP.

Office tools

SAP Learning lists several office integrations: export to Microsoft 365 OneDrive in Excel and Word, collaboration with Microsoft Teams and integration with Outlook 365. These suit finance teams who live in spreadsheets and sales teams who live in their inbox. Test them on a realistic report or quote, since the comfort of a user matters more than a feature list.

Business intelligence and reporting

Reporting tools usually read from the database or call the API. Agree early on which dashboards are essential, who builds them and how often the data refreshes. Avoid letting each department create its own version of revenue or margin. A single agreed definition prevents arguments in the board meeting.

EDI, signatures and sector tools

Some customers, particularly in retail and distribution, require electronic data interchange. Others require electronic signature on contracts or delivery proofs. These are normally supplied by a specialist publisher through the extension catalogue or by a bespoke flow. Ask for a reference conversation with a company of similar size and sector, without relying on a name supplied by the vendor alone. The industry pages for SAP Business One show where sector needs tend to arise.

How to scope an integration flow

A clear brief saves weeks of rework. Use this checklist when you write the requirement, or adapt our ERP requirements template.

1. Name the business event. For example, a paid web order or a goods receipt.
2. Name the systems and the master. Which one holds the truth for each field?
3. Define direction and timing. One way or both, real time or scheduled.
4. List the exceptions. Unknown customer, out-of-stock item, rejected payment, duplicate order.
5. Define the volume in words. Quiet, seasonal peaks, promotion spikes. Your integrator can then size it.
6. Agree the test data. Real anonymised cases, not tidy samples.
7. Decide the monitoring. Who sees a failed message, and how soon?
8. Name the owner. One person on your side, one company on the supplier side.

Write each flow on a single page. If a flow cannot be summarised that way, it is probably two flows.

Who maintains an integration after go-live

Integrations break at the edges: a web platform changes its interface, a bank updates a format, SAP Business One moves to a new release. Three arrangements are common:

• Publisher-maintained add-on. The publisher fixes its product; your integrator handles set-up and configuration.
• Integrator-maintained custom flow. A support agreement covers fixes and adaptation after upgrades.
• In-house maintained flow. Only sensible if you employ people who understand the Service Layer and will still be there next year.

Whichever you choose, put the arrangement in the support contract and link it to your plans for support and maintenance. Keep a short document listing every flow, its owner, its credentials location and its monitoring routine. When you later consider an upgrade or a migration, that register becomes the most valuable page in the project.

Common pitfalls

• Treating the connector as the project. The connector moves data; the project is agreeing what the data means.
• Duplicated masters. Two systems both editing customer addresses will drift apart.
• No error queue. Silent failures are worse than loud ones.
• Customisation by default. Bespoke code raises the future cost of every upgrade; see the customisation page for the trade-offs.
• Ignoring licensing and hosting. Some routes need extra components or licences, so ask for them to be listed in the quotation. Our SAP Business One pricing page explains how to read an offer.

Next step

If you already know which systems must connect, write the list of flows using the checklist above and bring it to your first conversation. ERP Integrator is free to use: we put you in touch with a certified integrator suited to your project, and the integrator, not us, designs and delivers the work.

For a broader view of how integrations fit into a full rollout, see the implementation guide, and if you are still weighing products, the alternatives page puts them side by side.

Software names mentioned are trademarks of their respective publishers and are referred to for information only. This site is independent and is not affiliated with any software publisher.