Unity for SaaS · SAP Business One

SAP Business One integration for SaaS companies

Your customers run SAP Business One. Unity connects your product to it, syncing Business Partners, A/R Invoices and Incoming Payments in SAP's own terms, under your brand, managed by our team.

How do SaaS products integrate with SAP Business One?

Most modern integrations use SAP Business One's Service Layer, a REST API built on OData that runs on both SAP HANA and Microsoft SQL Server. Unity uses it to read and write SAP objects such as Business Partners, A/R Invoices and Incoming Payments, with SAP's own business rules applied to every write. Where a process needs it, Unity can also work through the DI API. Our team builds the integration, delivers it under your brand and keeps it running through SAP upgrades.

What syncs

SAP Business One objects Unity maps for SaaS products

Each map uses SAP Business One's own objects and rules, so data lands where your customer's finance team expects it.

SAP Business One objectTypical directionWhat it's used for
Business PartnersBoth waysCustomers and vendors kept identical in your app and in SAP, including billing and ship-to addresses
Contact PersonsBoth waysThe people your app emails, bills or supports, linked to their Business Partner
Items and price listsFrom SAPProducts, SKUs and pricing your app quotes or sells against
Sales OrdersTo SAPOrders captured in your app, created in SAP for fulfillment
A/R Invoices and Credit MemosBoth waysInvoices issued in either system, kept in step with SAP's numbering and posting rules
Incoming PaymentsTo SAPPayments collected in your app, applied against the right open A/R Invoices
A/P Invoices and Outgoing PaymentsBoth waysSupplier bills and payouts for AP, spend and procurement platforms
User-defined fieldsBoth waysThe custom fields each SAP customer adds, mapped without code
How Unity connects

Service Layer, HANA or SQL Server, on-premises or cloud

SAP Business One customers run different versions, databases and hosting setups. Unity is built to handle all of them.

Service Layer first

The Service Layer validates every write against SAP's business logic, the same rules a user faces in the SAP client. Unity never writes straight to the SAP database, which keeps your customer's system supported.

SAP HANA and Microsoft SQL Server

Unity supports SAP Business One 9.1 and later, on either database. From version 10.0 the Service Layer runs on both SAP HANA and SQL Server. On earlier SQL Server releases, Unity connects through the DI API.

On-premises or partner-hosted

For on-premises installs, a lightweight Intelligrate agent runs inside your customer's network, so no inbound firewall ports are opened. Partner-hosted SAP Business One Cloud is supported too.

Several companies, one integration

Customers who run more than one SAP Business One company database can connect them all through one Unity integration, with each company's data kept separate.

Integration users need the right SAP Business One license. Your customer's SAP partner can confirm which license type applies to their version and database.

Field notes

SAP Business One problems we've already solved

These are the issues that stall do-it-yourself SAP integrations, and how Unity handles each one.

Missing Business Partner

An invoice arrives before its customer exists

SAP rejects an A/R Invoice whose Business Partner isn't there yet. Unity's dependent maps create the Business Partner first, then post the invoice, with no manual retry.

Locked posting period

Finance closes the month mid-sync

Documents dated in a locked period are refused by SAP. Unity raises a case with SAP's own error message, so the right person can reopen the period or change the posting date.

Approval procedures

A document waits for approval

Customers often route large orders or payments through SAP approval procedures. Unity tracks the draft until it is approved, instead of reporting a failure.

Session limits

Long syncs outlive the login

Service Layer sessions expire after a period of inactivity. Unity manages sessions and throttles requests so long-running syncs finish without dropped records.

Use cases

Which SaaS products connect to SAP Business One?

Payments and accounts receivable

Pull open A/R Invoices into your platform, collect payment, and post Incoming Payments back to SAP so cash application closes itself.

Transportation management (TMS)

Send Sales Orders and Deliveries from SAP to your TMS for load planning, then return carriers, tracking numbers and actual freight costs to SAP so invoices carry the real shipping charge.

AP automation and spend management

Sync vendors as Business Partners, push approved A/P Invoices to SAP, and return Outgoing Payment status to your app.

Ecommerce, CPQ and order management

Read Items and price lists from SAP, then create Sales Orders the moment a customer buys.

Field service and support

Keep customer and equipment records aligned, and send billable work back to SAP for invoicing.

Why Unity

Unity is a managed integration service for SaaS companies, built on the Intelligrate iPaaS. We build your SAP Business One integration, put your brand on it, monitor it, fix errors and handle upgrades. Integration updates can even flow into your own help desk. See how Unity works for SaaS.

500+SAP Business One companies connected
8–12 wkstypical time to go live
350M+records processed on the platform
75+other systems you can add next
FAQ

SAP Business One integration questions

Which SAP Business One versions and databases does Unity support?

Yes. Unity supports SAP Business One 9.1 and later on both databases. From version 10.0 it connects through the Service Layer on either one, and on earlier SQL Server releases it uses the DI API. The same integration works whichever database your customer uses.

Will our customers need an additional SAP license?

The integration signs in to SAP Business One as a user, so it needs an appropriate SAP license. The right type depends on the customer's version, database and contract, and their SAP partner can confirm it. We flag this early in every project so it never delays go-live.

Can Unity map our customers' user-defined fields?

Yes. Most SAP Business One customers add their own fields to Business Partners, documents and items. Unity maps user-defined fields without code, per customer, so each one's setup is respected.

What happens when a posting period is locked or a document needs approval?

SAP's rules always win. Unity records the SAP error or approval status as a case, shows the exact message, and can sync that case to your own help desk. Once finance reopens the period or approves the document, the record is re-run without touching anything else.

Do you support partner-hosted SAP Business One Cloud?

Yes. Unity connects to SAP Business One whether it runs on your customer's own servers or is hosted by their SAP partner.

Does Unity write directly to the SAP Business One database?

No. Unity writes through SAP's supported interfaces, so every document passes SAP's business-logic checks, just as if a user had entered it.

How long does an SAP Business One integration take?

A first SAP Business One integration typically goes live in eight to twelve weeks. Each new customer after that is mostly configuration, since the maps are already built.

Connect, scale, sell more

Selling to SAP Business One customers?

Tell us what your product needs from SAP. We'll show you how Unity connects it, under your brand.